Tips on how to convert CAD property to glTF to be used with AWS IoT TwinMaker

Prospects typically have present 3D CAD (Laptop-aided Design) property that they want to use with AWS IoT TwinMaker. CAD recordsdata are both proprietary codecs optimized to be used in proprietary functions or interchange codecs designed for transferring CAD knowledge from one software to a different. They aren’t often suitable with realtime WebGL viewports like these utilized in AWS IoT TwinMaker, which helps the glTF format. Prospects might want to convert their CAD property to the glTF format earlier than importing these property to AWS IoT TwinMaker.

On this submit, I’ll reveal a workflow for utilizing Pixyz Situation Processor to transform a CAD file within the STEP format to a realtime 3D file within the glTF format. Pixyz Situation Processor is an answer supplied by Pixyz that’s obtainable in AWS Market. It may be configured for a number of totally different eventualities. On this instance, I can be utilizing the GenericPolygonTarget state of affairs. This state of affairs makes use of the commonest settings for changing CAD property to realtime property to be used in recreation engines and WebGL views. It has choices for setting the specified polygon depend, figuring out if objects ought to be merged collectively, and figuring out if hidden objects ought to be deleted.

Overview of resolution

On this walkthrough, you’ll setup Amazon Elastic Container Service (ECS) to run the Pixyz Situation Processor on a file saved in Amazon Easy Storage Service (Amazon S3).

You’ll create an Amazon S3 bucket and add your CAD file for conversion. Additionally, you will create and run an AWS Fargate Job that makes use of the Pixyz Situation Composer container picture to transform the CAD file to glTF. After working the duty, you’ll obtain the ensuing file from Amazon S3 to examine it in a glTF suitable viewer.

Walkthrough

On this walkthrough I’ll reveal the creation of an AWS Fargate Job that may seize a CAD file from an S3 bucket, convert it to a GLB (binary glTF format) file and retailer it again in that S3 bucket. The Fargate Job will use the Pixyz Situation Processor from the AWS Market. This requires adjusting the default IAM coverage for working duties on Amazon ECS to permit for metering utilization of the AWS Market resolution.

We are going to run by way of the next steps:

1. Add the supply recordsdata to an S3 Bucket
2. Create an IAM Function for working Amazon ECS Duties with the Pixyz Situation Processor
3. Create the Community Solely Cluster
4. Create the Job Definition
5. Run the Fargate Job
6. Study the Logs
7. (Non-obligatory) Obtain the glTF file and consider it

Stipulations

For this walkthrough, the next are conditions:

• An AWS account
• Amazon S3 to retailer your CAD file
• AWS IAM
• Amazon ECS and AWS Fargate
• A subscription to Pixyz Situation Processor on AWS Market.
  • For this instance, you may be charged for utilizing Pixyz Situation Processor with utilization based mostly pricing. Present pricing info is accessible on the AWS Market product web page for Pixyz Situation Processor. Estimated price of finishing this train is $0.25 – $1.00.
• A CAD file to transform. I can be utilizing the file, Waste_Container.step, however you need to use your individual visible property.

Rendering of Waste_Container.step

Step 1: Add the supply recordsdata to an S3 Bucket

1. Navigate to the Amazon S3 Console.
2. Create a brand new bucket to make use of. I can be utilizing the us-west-2 area for this instance.
   My bucket identify is: pixyz-example-20211117.
3. Create an enter and an output folder contained in the bucket.
4. Add the CAD file you need to convert into the enter folder.
   I’m utilizing a STEP file: Waste_Container.step.

Waste_Container.step uploaded to Amazon S3

Step 2: Create an IAM Function for working Amazon ECS Duties with the Pixyz Situation Processor

1. Navigate to the AWS IAM Console Web page.
2. Select the Roles part and press the Create Function button.
3. Choose Elastic Container Service, then Elastic Container Service Job, then choose the Subsequent:Permissions button.
4. Connect the next Permissions:
   1. AWSMarketplaceMeteringRegisterUsage (permits AWS Market to Meter utilization)
   2. AmazonS3FullAccess (permits Amazon ECS to entry the S3 bucket)
   3. AmazonECSTaskExecutionPolicy (permits Amazon ECS to execute Duties)
5. Choose the Subsequent:Tags button.
6. Choose the Subsequent:Evaluate button.
7. Title the position, I used pixyz-example-role-20211117.
8. Add an outline, I used “Function created for Pixyz Situation Processor instance.” Choose the Create position button.

It is best to now have a job that appears much like:

Permissions insurance policies utilized to IAM Function pixyz-example-role-20211117

Step 3: Create the Community Solely Cluster

1. Navigate to the Amazon ECS console.
2. Navigate to the Clusters part and choose the button to Create Cluster.
3. Choose Networking Solely after which the Subsequent step button.
4. Configure the Cluster with:
   1. identify: pixyz-example-cluster
   2. Allow Create a brand new VPC for this cluster.
   3. Use default CIDR and subnet blocks.
   4. Allow Cloudwatch Container Insights.
5. Choose the Create button.

Step 4: Create the Job Definition

1. Navigate to the Amazon ECS console.
2. Navigate to the Job Definition part and choose the button to Create new Job Definition.
3. Select the Fargate choice and choose the Subsequent step button.
4. Configure the Job:
   1. Give it a reputation, I used: pixyz-example-task
   2. For Job position, use the IAM position you created above: pixyz-example-role-20211117
   3. Working system household: Linux.
   4. For Job Execution position, once more, use the IAM position you created: pixyz-example-role-20211117
   5. Job Reminiscence: 4 GB
   6. Job CPU (vCPU): 1 vCPU
   7. Create a container with the Add container button and configure with:
      1. identify: pixyz-example-container
      2. picture url: 709825985650.dkr.ecr.us-east-1.amazonaws.com/pixyz-software/scenario-processor:2021.1.0.79
      3. take away port-mappings
      4. Surroundings Command:

         GenericPolygonTarget,s3File_with_arguments,"pixyz-example-20211117","us-west-2","enter/Waste_Container.step",False,"pixyz-example-20211117","us-west-2","output/Waste_Container.glb",10000,False,False,False

         The command template supplied within the Pixyz Situation Processor Fast-Begin is:

         GenericPolygonTarget,s3File_with_arguments,"my-input-bucket-name", "my-input-bucket-region", "enter/inputFile.step",False,"my-output-bucket-name","my-output-bucket-region","outputFolder/resultFile.xxx",10000,False,False,False

         In our model we’ve changed:
         my-input-bucket-name with pixyz-example-20211117
         my-input-bucket-region with us-west-2
         enter/inputFile.step with enter/Waste_Container.step
         my-output-bucket-name with pixyz-example-20211117
         my-output-bucket-region with us-west-2
         outputFolder/resultFile.xxx with output/Waste_Container.glb

Step 5: Run the Fargate Job

1. Navigate to the Amazon ECS console.
2. Navigate to the Job Definition part.
3. Choose the Job Definition and from the Actions button choose Run Job.
4. Configure the Run Job with:
   1. Launch Kind: Fargate
   2. Working System Household: Linux
   3. Cluster: pixyz-example-cluster
   4. Add the each of the obtainable Subnets to the Cluster VPC.
5. Press the Run Job button to run the duty.

Step 6: Study the Logs

You need to use the Amazon CloudWatch Console to observe the Fargate activity in progress. Because the Pixyz Situation Processor runs it outputs logs to a CloudWatch Log Group.

1. Navigate to the Amazon CloudWatch Console.
2. Navigate to the Log Teams part and select the ecs/pixzy-example-task log group.
3. Choose the Log Stream that may look much like ecs/pixyz-example-container…
4. Learn by way of the logs generated by the duty.

Widespread errors are:

1. Register error: AccessDenied Exception. The IAM position used doesn’t have the suitable insurance policies. The duty is utilizing an autogenerated ecsTaskExecutionRole as a substitute of the IAM position we created above. You’ll must replace the Job Definition with the right position.
2. Bucket Not Discovered. There’s a typo within the Surroundings Command the place the buckets and recordsdata outlined within the command string don’t exist. You’ll must replace the Job Definition with the right bucket names an enter and output folder/filenames.

Step 7: (Non-obligatory) Obtain the glTF file and consider it

1. Navigate to the Amazon S3 Console.
2. Navigate to the bucket pixyz-example-20211117 and folder output.
3. Choose the file generated by the duty, for me that is Waste_Container.glb, and press the Obtain button.

To view glTF and GLB recordsdata on my native pc, I exploit Visible Studio Code with the glTF Instruments extension.

Waste_Container.glb rendered in Visible Studio Code.

Cleansing up

To keep away from incurring ongoing storage fees for objects in Amazon S3 or logs in Amazon CloudWatch, it is best to delete the assets created on this walkthrough. You must also take away the IAM position, AWS Fargate Job Definition and Cluster. Lastly, unsubscribe from the Pixyz Situation Processor to complete cleansing up from this walkthrough.

Take away the S3 bucket, folders, and recordsdata

1. Navigate to the Amazon S3 Console and the bucket, pixyz-example-20211117.
2. Delete the S3 objects enter/Waste_Container.step and output/WasteContainer.glb.
3. Delete the folders enter and output.
4. Delete the S3 bucket, pixyz-example-20211117.

Take away the IAM position

1. Navigate to the AWS IAM Console.
2. Select the Roles part and delete pixyz-example-role-20211117.

Take away the AWS Fargate Job Definition and Cluster

1. Navigate to the Amazon ECS console.
2. Within the Job Definitions part, use the Actions button to de-register the Job, pixyz-example-task.
3. Within the Clusters part, use the Delete Cluster button to delete your cluster, pixyz-example-cluster.

Take away the Logs from Amazon CloudWatch

1. Navigate to the Amazon CloudWatch Console.
2. Within the Log Teams part, use the Actions button to Delete log group(s), ecs/pixzy-example-task.

Unsubscribe from the Pixyz Situation Processor subscription

1. Navigate to the AWS Market Console.
2. Choose the Pixyz Situation Processor and use the Actions button to Cancel subscriptions.

Conclusion

On this walkthrough you used the Pixyz Situation Processor to transform a CAD asset to a glTF file that is able to use with AWS IoT TwinMaker. You possibly can modify the AWS Fargate Job to transform another CAD recordsdata you want to use with AWS IoT TwinMaker.

Now that you’ve got a glTF asset, you need to use it with AWS IoT TwinMaker to create digital twins of real-world programs to optimize operations.

In regards to the creator

Jeremiah Habets is a Sr. Spatial Marketing consultant with Amazon Net Companies (AWS) Skilled Companies. Jeremiah helps prospects resolve issues in AR/VR, Simulation, Visualizations utilizing realtime 3D know-how.