You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

A3200 throws one of the following errors during runtime or upon attempting to connect. Click on the error to view more troubleshooting information. This list is not exhaustive and is intended to be a supplement to the information included in the A3200 help file.


"An attempt to allocate memory on the SMC Failed: The controller was unable to allocate the memory required for a specific operation"

"An unexpected error occurred: An error occurred in the SelfID format."

"An error occurred while processing a calibration file"

"Drive communications were interrupted."

"A Communication Service error occurred"

"A Firmware Loader error occurred"

  • This error most commonly occurs because the galvo drive (Nmark or GL4) is not recognized by A3200.

    • The FireWire cable, HyperWire cable, or one or more drive cables are not connected correctly. Ensure that the wiring follows the System Interconnect drawing provided with the system (for integrated TAS systems).

    • Ensure that the communication channels of the galvo drive in the system are correct. The galvo drive communication channels must correspond to galvo axes in the currently active parameter file. Review the Nmark hardware manual for details on the communication channel dipswitches. The GL4 has software configurable communication channels. See Controller > Drive Configuration in A3200 Configuration Manager.
    • If the galvo axes are virtual (a yellow "V" in A3200 Motion Composer), see Virtual Axes.

  • You issued a command that requires a GL4 or an Nmark axis, but the axis that you specified is not a galvo axis.

  • In A3200 Configuration Manager, you defined a 2D galvo calibration file on an axis that is not a galvo axis.

"An error occurred during HyperWire communication"

"An initialization error occurred in the Communication Service : The service failed to create a real-time event."




  • No labels