Automatically generate custom product data and associated documentation for engineering, manufacturing and sales. Automatically send emails and bulk process orders.
Learn where DriveWorks Autopilot is typically placed in a multi-application deployment.
Check system requirements, learn how to install and license DriveWorks Autopilot.
When DriveWorks Autopilot is first launched a Group must be opened using the Open Group Wizard.
Each Group opened using the wizard will subsequently become available in the Recent List of the DriveWorks Today task.
To allow DriveWorks Autopilot to begin listening for Specifications to process it must have a Group open and be set to Start.
DriveWorks Autopilot can perform all or any of the following functions:
When a single Autopilot machine is employed all of the above queues should be enabled.
When multiple Autopilot machines are in use the required function can be chosen by enabling or disabling the required queue.
Multiple DriveWorks Autopilot machines can be deployed to balance the load on each machine.
This is done by enabling or disabling the required queue on each machine.
Learn moreEmploying multiple DriveWorks Autopilot machines also gives the ability to prioritize the processing of generated information.
This is done by defining tags for each Autopilot to include or exclude from its priority list.
Learn moreWhen integrating with SOLIDWORKS PDM Professional the vault name and credentials are required to be applied to each DriveWorks Autopilot machine.
Additional settings may also be required depending on if the option to Store settings in the group is checked.
DriveWorks Autopilot can automate the creation of new specifications or modify existing specifications.
This is done by creating a Connector that attaches to a source of data.
A connector can also be set to run a DriveWorks project on a schedule.
When Autopilot is running each task Autopilot performs is logged in the main screen.
Typically DriveWorks Autopilot is left to run on its own dedicated machine, constantly processing the information created from each specification.
DriveWorks Administrator provides the ability to remotely control each DriveWorks Autopilot connected to the same shared group.
DriveWorks Autopilot gives you the freedom to work on other tasks while it generates all SOLIDWORKS data.
The time it takes to generate parts, assemblies and drawings is dependent on SOLIDWORKS.
However, there are some settings that can be applied that will help to make model generation as performant as possible.
When continually generating lots of models, memory can get overworked and occasionally SOLIDWORKS may become unresponsive.
DriveWorks Autopilot will nurse these situations by restarting SOLIDWORKS at set intervals.
DriveWorks Autopilot will give generation priority in the following order:
When Autopilot is connected to a Shared Group (through DriveWorks Pro Server) and a network connection issue occurs, the following message will be displayed:
This message will be displayed if Autopilot cannot reconnect after 10 seconds.
Any Autopilot functionality that requires connection to Pro Server will be unavailable until connection is restored.
Click Retry to attempt to re-establish connection.
If connection cannot be re-established clicking Quit will close the application.
If connection is re-established during display of the message, Autopilot will continue as usual.
This is designed to indicate network disconnects are occurring.
The following troubleshooting topics will help to resolve the most common issues: