Replies: 1 comment
-
|
Hi Gianfranco. The gantry at UNL initially had an issue where the Dell PC that had been purchased was incompatible with the real-time kernel used by A3200 which led to communication errors. In the end a new PC was purchased which fixed the issue. This required working with Aerotech technical support to to identify the problem. I recommend opening up a ticket with them so they can help you figure out where these errors are coming from. You may also consider going through their optimization guide to see if any of the recommendations there can help. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
Myself and some other gantry users at Cornell have been running into a somewhat transient/non-replicable error regarding the gantry connection. I attached a screenshot of the error thrown. When this happens, any running Motion Composer or GScript program immediately stops and the Motion Composer requires us to reset the controller to use the Gantry again.
I myself have seen it occur on various occasions when using GScript. However, other gantry users have seen it occur when running only the Motion Composer.
We were wondering if anyone else has seen this particular error being thrown as it is difficult for us to replicate. From my own experience, it seems to only occur after using the gantry for ~1-2 hours, but that's really the only baseline I have for this...
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions