AeroScript Equivalents of AeroBasic Commands for the A3200

Replaced by AnalogOutputGet() and AnalogOutputSet().

Replaced by AnalogInputGet().

Replaced by DigitalOutputGet() and DigitalOutputSet().

Replaced by DigitalInputGet().

Replaced by VirtualBinaryOutputGet() and VirtualBinaryOutputSet().

Replaced by VirtualBinaryInputGet() and VirtualBinaryInputSet().

Replaced by VirtualRegisterOutputGet() and VirtualRegisterOutputSet().

Replaced by VirtualRegisterInputGet() and VirtualRegisterInputSet().

Removed. To read output bits, use DigitalOutputGet(). To retrieve the outputs as a 32-bit bitmask, use StatusGetAxisItem() with AxisStatusItem.DigitalOutput. To set outputs as individual bits, use DigitalOutputSet().

Removed. To read individual input bits, use DigitalInputGet(). To retrieve the inputs as a 32-bit bitmask, use StatusGetAxisItem() with AxisStatusItem.DigitalInput.

Removed. This command was used to set and get the bidirectional I/O on the Nservo. Automation1 drives do not have bidirectional I/O.

Removed. This AeroBasic command changed all axis or task settings back to the values stored in the Default axis or task parameters. Default parameters have names that start with Default, such as DefaultCoordinatedRampRate. You can use Default parameters to configure the default motion settings that will have an effect on a controller after you reset that controller. Thus, Aerotech recommends that you use Automation1 Studio to change the values of Default parameters. Do not change the values of these parameters from your AeroScript program.

In AeroScript, you can do functionality that is almost the same as the APPLYDEFAULTS command on the A3200. During runtime, when the controller is running, you can call the ParameterGetAxisValue() or ParameterGetTaskValue() function to get the active Default parameter value of a specified axis or task. Then you can call a corresponding motion configuration function in AeroScript to set the active value at runtime.

For example, to change the active value on the controller to the value stored in the DefaultAxisRampRate Parameter, you must do the steps that follow. First, use the ParameterGetAxisValue() function to retrieve the value of the DefaultAxisRampRate Parameter. Then call the SetupAxisRampValue() function in AeroScript to set the active value that the motion will use.

For information about which configuration functions correspond to the Default parameter settings, see Motion Setup Functions.

Replaced by ParameterGetAxisStringValue(). See Parameter Functions.

Replaced by ParameterGetAxisValue(), ParameterGetTaskValue(), and ParameterGetSystemValue(). See Parameter Functions.

You cannot read parameters from a configuration file on the controller. Use Machine Setup to examine the parameter configuration of the controller. To read the active value of a parameter during runtime, use the ParameterGet*() functions. See Parameter Functions.

You cannot read parameters from a configuration file on the controller. Use Machine Setup to examine the parameter configuration of the controller. To read the active value of a parameter during runtime, use the ParameterGet*() functions. See Parameter Functions.

Removed. AeroScript does not have an equivalent. To set the maximum current clamp, see MaxCurrentClamp Parameter.

Replaced by ParameterSetAxisValue() and ParameterSetAxisStringValue(). See Parameter Functions.

Replaced by ParameterSetAxisValue(), ParameterSetTaskValue(), and ParameterSetSystemValue(). See Parameter Functions.

You cannot write parameters to a configuration file on the controller. Use Machine Setup to change the parameter configuration of the controller. To change the active value of a parameter during runtime, use the ParameterSet*() functions. See Parameter Functions.

Replaced by var keyword. You can declare single variables and arrays of variables. Each array can have a maximum of three dimensions. If you do not specify the variable type, then the variable uses the default type. The default variable type is real. Refer to the example that follows:

Code Example

// Single variables for all the fundamental variable types.
var $oneReal as real
var $oneInt as integer
var $oneHandle as handle
var $oneString as string

// Arrays of variables.
// Each array can have a maximum of three dimensions.
var $oneDimArray[7] as axis
var $twoDimArray[4][2] as integer
var $threeDimArray[3][2][2] as real

Renamed to goto.

Removed. You can declare functions using the function keyword and then call them by name.

Removed. You can use libraries to package code and make it usable by other programs. See Libraries example program.

Removed. You can use libraries to package code and make it usable by other programs. See Libraries example program.

Replaced by the onerror() statement. See Error Handling example program.

Removed. As an alternative, you can write a dedicated AeroScript program that monitors your conditions. Refer to the example that follows:

Code Example

CriticalSectionStart()
while (true)
        // AeroBasic: ON $global[0] == 1.0 SET $global[1], 5.0, -5.0
        if ($rglobal[0] == 1.0)
            	$rglobal[1] = 5.0
        else
            	$rglobal[1] = -5.0
        end
	
        // Dwell to prevent a task starvation and to make sure
        // that the conditions are monitored once per millisecond.
        Dwell(0.001)
end
CriticalSectionEnd()

Renamed to return.

Renamed to if.

Renamed to while.

Renamed to for.

Renamed to repeat.

Replaced by end keyword.

Removed. For an equivalent functionality, you can use the sync keyword to do a synchronized function call.

Removed. For an equivalent functionality, you can use the sync keyword to do a synchronized function call.

Replaced by function keyword.

Replaced by end keyword.

Replaced by sync keyword. The sync keyword does a synchronized function call.

Removed. As an alternative, you can write AeroScript functions or AeroScript libraries that save a copy of the modes or settings of a task and restore them. For information about how to retrieve task settings that you want to restore, refer to the StatusGetTaskItem() function in Controller Status Functions. To restore a setting, you can issue the corresponding AeroScript function that enables or disables the setting.

Renamed to ProgramStart(). See Task and Program Functions.

Renamed to ProgramStop(). See Task and Program Functions.

Renamed to ProgramPause(). See Task and Program Functions.

Replaced with ProgramStepInto(), ProgramStepOver(), and ProgramStepOut(). See Task and Program Functions.

Replaced with ProgramStepInto(), ProgramStepOver(), and ProgramStepOut(). See Task and Program Functions.

Removed. To load a program from the controller file system onto a task, use the ProgramLoad() function. See Task and Program Functions.

Replaced with the ProgramLoad() function. This function operates only on a compiled version of an AeroScript program. The AeroBasic command, PROGRAM LOAD, did the operations that follow: Compiled an AeroBasic program from the Windows file system, loaded the program into controller memory, and associated it with a task.

In Automation1, you cannot compile programs from an AeroScript command. But you can do the options that follow:

• In Studio or the .NET or C API, you can compile programs and put the compiled AeroScript programs into the controller file system. Then in AeroScript, you can use the Task and Program Functions to load or run those programs.

• Use Program Automation to load AeroScript programs into memory when the controller resets.

• Get the AeroScript code that you want to use and put it into an AeroScript library. Then use Program Automation to load the AeroScript libraries into memory when the controller resets so that the library functions are available to all tasks.

Replaced with the ProgramRun() function. This function operates only on a compiled version of an AeroScript program. The AeroBasic command, PROGRAM RUN, did the operations that follow: Compiled an AeroBasic program from the Windows file system, loaded the program into controller memory, and ran the program on a task.

In Automation1, you cannot compile programs from an AeroScript command. But you can do the options that follow:

• In Studio or the .NET or C API, you can compile programs and put the compiled AeroScript programs into the controller file system. Then in AeroScript, you can use the Task and Program Functions to load or run those programs.

• Use Program Automation to load AeroScript programs into memory when the controller resets.

• Get the AeroScript code that you want to use and put it into an AeroScript library. Then use Program Automation to load the AeroScript libraries into memory when the controller resets so that the library functions are available to all tasks.

In Automation1, Command Queue has almost the same functionality. Refer to the Executing Custom AeroScript From a File section in the Command Queue in the .NET API or the Command Queue in the C API page to learn how to run a large AeroScript program using the Command Queue.

Removed. This AeroBasic command compiled an AeroBasic program from the Windows file system and loaded it into controller memory.

In Automation1, you cannot compile programs from an AeroScript command. But you can do the options that follow:

• In Studio or the .NET or C API, you can compile programs and put the compiled AeroScript programs into the controller file system. Then in AeroScript, you can use the Task and Program Functions to load or run those programs.

• Use Program Automation to load AeroScript programs into memory when the controller resets.

• Get the AeroScript code that you want to use and put it into an AeroScript library. Then use Program Automation to load the AeroScript libraries into memory when the controller resets so that the library functions are available to all tasks.

Removed. In Studio or the .NET or C API, you can remove compiled programs from the controller file system. When you reset the controller, it clears all the AeroScript programs that were previously loaded into memory.

Replaced with AeroScript equivalents. You can use the program and end keywords to define your program in AeroScript. If you want your program to exit early, you can issue the ProgramExit() function.

Replaced with the CriticalSectionStart() function.

Replaced with the CriticalSectionEnd() and CriticalSectionEndAll() functions. See Task and Program Functions for more information.

Renamed to MoveRapid(). You can also use G0 syntax.

Renamed to MoveLinear(). You can also use G1 syntax.

Renamed to MoveCw(). You can also use G2 syntax.

Renamed to MoveCcw(). You can also use G3 syntax.

Renamed to MovePt().

Renamed to MovePvt().

Renamed to MoveAbsolute().

Renamed to MoveIncremental().

Currently not available. If you generate your motion programs with CADFusion or a different CAD/CAM tool that is compatible with the Automation1 controller, you can configure CADFusion or the CAD/CAM tool to approximate BEZIER curves. To do this, you must use the MoveLinear(), MoveCw(), and MoveCcw() functions.

Renamed to MoveFreerun().

Renamed to MoveToLimitCcw() and MoveToLimitCw().

Renamed to MoveOutOfLimit().

Renamed to Dwell().

Renamed to MoveDelay().

Replaced by wait keyword.

Replaced by WaitForMotionDone().

Removed. You can change the BacklashDistance Parameter to get the same functionality. Set the parameter to 0 to turn the feature off for that axis.

Removed. Available as G9.

Removed. Available as G8.

See Motion Setup Functions.

Replaced by SetupTaskTargetMode(). Pass TargetMode.Absolute or TargetMode.Incremental.

Replaced by SetupTaskTimeUnits(). Pass TimeUnits.Seconds or TimeUnits.Minutes.

Removed. Available as G120/G121.

Renamed to VelocityBlendingOn().

Removed. Available as G70. As an alternative, you can use the SetupTaskDistanceUnits() function to set the distance units to primary or secondary mode.

Removed. Available as G71. As an alternative, you can use the SetupTaskDistanceUnits() function to set the distance units to primary or secondary mode.

Replaced by SetupTaskDistanceUnits(). Use DistanceUnits.Primary.

Renamed to Callback().

Removed. This AeroBasic command let you call into a Windows DLL from the controller.

Because of security precautions with Automation1, you cannot access the Windows file system or execute Windows DLL and EXE files from AeroScript. But you can do the options that follow:

• As an alternative to sequencing all controller and Windows operations from AeroScript, write a .NET or C application that sequences the necessary DLL or EXE functionality in Windows and uses the Automation1 .NET or C API to communicate with the controller.

• If you want to continue sequencing operations from AeroScript, write a .NET or C application that registers for custom callbacks. Then in response to the custom callback, write code in your .NET or C application that triggers all the necessary Windows-side operations. From your AeroScript program, issue the Callback() function in all the locations where you previously would use OPENDLL, CALLDLL, CLOSEDLL, EXE, or EXEMODAL.

Removed. This AeroBasic command let you close a Windows DLL file that was previously opened with the OPENDLL AeroBasic command.

Removed.

Removed.

Replaced by DataCollectionAddAxisSignal(), DataCollectionAddTaskSignal(), and DataCollectionAddSystemSignal().

Renamed to DataCollectionReset().

Renamed to DataCollectionStart().

Renamed to DataCollectionStop().

Removed.

Removed. This AeroBasic command let you execute a Windows EXE file from the controller.

Because of security precautions with Automation1, you cannot access the Windows file system or execute Windows DLL and EXE files from AeroScript. But you can do the options that follow:

• As an alternative to sequencing all controller and Windows operations from AeroScript, write a .NET or C application that sequences the necessary DLL or EXE functionality in Windows and uses the Automation1 .NET or C API to communicate with the controller.

• If you want to continue sequencing operations from AeroScript, write a .NET or C application that registers for custom callbacks. Then in response to the custom callback, write code in your .NET or C application that triggers all the necessary Windows-side operations. From your AeroScript program, issue the Callback() function in all the locations where you previously would use OPENDLL, CALLDLL, CLOSEDLL, EXE, or EXEMODAL.

Removed. This AeroBasic command let you execute a Windows EXE file from the controller.

Because of security precautions with Automation1, you cannot access the Windows file system or execute Windows DLL and EXE files from AeroScript. But you can do the options that follow:

• As an alternative to sequencing all controller and Windows operations from AeroScript, write a .NET or C application that sequences the necessary DLL or EXE functionality in Windows and uses the Automation1 .NET or C API to communicate with the controller.

• If you want to continue sequencing operations from AeroScript, write a .NET or C application that registers for custom callbacks. Then in response to the custom callback, write code in your .NET or C application that triggers all the necessary Windows-side operations. From your AeroScript program, issue the Callback() function in all the locations where you previously would use OPENDLL, CALLDLL, CLOSEDLL, EXE, or EXEMODAL.

Renamed to FileClose().

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Renamed to DirectoryFileExists().

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Renamed to FileOpenBinary() and FileOpenText().

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Replaced by FileTextReadLine(), FileTextReadString(), and FileBinaryRead*() functions.

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Replaced by the FileBinaryRead*Array() functions.

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Replaced by FileIniReadValue().

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Renamed to FileSize().

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Replaced by the FileTextWriteString() and FileBinaryWrite* functions. To specify a new-line character to a text string, append "\n" to the text string before you call FileTextWriteString().

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Removed. You can get functionality that is almost the same by calling FileTextWriteString() in a while, for, or repeat loop.

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Replaced by FileBinaryWrite*Array().

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Replaced by FileIniWriteValue().

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Removed. To prevent a new-line character from being written to file, make sure to not specify "\n" in your text strings.

In Automation1, the File and Directory Functions operate directly on the controller file system. You cannot specify Windows directories from within AeroScript. To configure the controller file system, use the Controller Files module of the Configure workspace from within Studio.

Removed. This command let you compile and execute an immediate command on a task by passing the AeroBasic command as a text string. But you cannot compile text strings in AeroScript. To do functionality that is almost the same, specify a synchronized function in your AeroScript program or in an AeroScript library. Then use the sync keyword to execute a synchronized function call on a different task.

Replaced by CalibrationLoad().

Renamed to SocketTcpServerAccept().

Removed. In Automation1, SocketWrite*() functions automatically flush all data that you write. See Socket Functions.

Renamed to SocketClose().

Renamed to SocketTcpClientCreate().

Removed. In Automation1, SocketWrite*() functions automatically flush all data that you write. See Socket Functions.

Renamed to SocketTcpServerCreate().

Renamed to SocketTcpServerIsClientPending().

Renamed to SocketGetReadBytesAvailable().

Replaced by SocketRead*().

Renamed to SocketSetDataReadTimeout() and SocketSetDataWriteTimeout().

Replaced by SocketWrite*().

Removed. This AeroBasic command let you open a Windows DLL file.

Because of security precautions with Automation1, you cannot access the Windows file system or execute Windows DLL and EXE files from AeroScript. But you can do the options that follow:

• As an alternative to sequencing all controller and Windows operations from AeroScript, write a .NET or C application that sequences the necessary DLL or EXE functionality in Windows and uses the Automation1 .NET or C API to communicate with the controller.

• If you want to continue sequencing operations from AeroScript, write a .NET or C application that registers for custom callbacks. Then in response to the custom callback, write code in your .NET or C application that triggers all the necessary Windows-side operations. From your AeroScript program, issue the Callback() function in all the locations where you previously would use OPENDLL, CALLDLL, CLOSEDLL, EXE, or EXEMODAL.

Removed. Controller configurations, such as parameter and calibration files, are stored internally on the controller at this time. They are not available for you to access in the Windows file system. To save a copy of the active controller configuration, download a Machine Controller Definition file (MCD file) from Studio or the .NET API. You can also overwrite the configuration on the controller. To overwrite the configuration, find an MCD file that is stored in Windows. Then upload it to the controller from Studio or the .NET API.

In AeroScript, you can see the active values of all the parameters. See Parameter Functions.

In AeroScript, you can see the active state of calibration or power correction on an axis:

• 1D or 2D axis calibration - Use the StatusGetAxisItem() function to retrieve AxisStatusItem.AxisStatus. Then make sure that you have the AxisStatus.CalibrationEnabled1D or AxisStatus.CalibrationEnabled2D bit.

• Galvo 2D Axis Calibration - Use the StatusGetAxisItem() function to retrieve AxisStatusItem.DriveStatus. Then make sure that you have the DriveStatus.GalvoCalibrationEnabled bit.

• Galvo Power Correction - Use the StatusGetAxisItem() function to retrieve AxisStatusItem.DriveStatus. Then make sure that you have the DriveStatus.GalvoPowerCorrection bit.

You can trigger a Frequency Response directly from Studio. See Application Frequency Response Functions.

See Math Functions.

Removed. You can get this functionality by left-shifting 0x1 by the index:

function IndexToMask($index as integer) as integer
        return 0x1 << $index
end

Removed. You can get this functionality by right-shifting the mask to compute the index:

function MaskToIndex($mask as integer) as integer 
       var $index as integer = -1
       var $testMask = $mask

       while ($testMask != 0)
              $index = $index + 1
              $testMask = $testMask >> 1
       end
       return $index

end

Removed. To change an axis variable to its integer whole number that represents the axis index, use the AxisToInteger() function.

See Utility and Conversion Functions.

See String Functions.

Renamed to CornerRoundingSetAxes().

Renamed to CornerRoundingOn().

Renamed to CornerRoundingOff().

Renamed to CornerRoundingSetTolerance().

See Transformation Functions.

Renamed to Abort().

Currently not available. You can do functionality that is almost the same by reading an analog input signal at 1 kHz from AeroScript. Then you can generate motion each millisecond by using the MovePvt() or MovePt() function with a 1 millisecond update time. When you use this method, an approximate 10 milliseconds of latency occurs between analog input changes and the corresponding position that is sent to the servo loop. Make sure that the latency does not prevent you from using this method correctly based on your project requirements.

Replaced by AutofocusOn() and AutofocusOff().

Removed. To prevent motion from entering a dangerous area, you can use safe zones. See Safe Zone Functions.

Replaced by DriveBrakeOn() and DriveBrakeOff().

Replaced by CammingOn() and CammingOff().

Renamed to Disable().

Renamed to Enable().

Renamed to GearingSetLeaderAxis().

Renamed to GearingOn().

Renamed to GearingOff().

Renamed to GearingSetRatio().

Removed. You can use Gearing functions to get an equivalent functionality. See Camming and Gearing Functions.

Removed. You can use Gearing functions to get an equivalent functionality. See Camming and Gearing Functions.

Renamed to Home().

Removed. To get this functionality, write an AeroScript function that homes axes that are not already homed.

function HomeConditional($axes[] as axis)
	CriticalSectionStart()
	foreach var $axis in $axes
		if (StatusGetAxisItem($axis, AxisStatusItem.AxisStatus, AxisStatus.Homed) != AxisStatus.Homed)
			HomeAsync($axis)
		end
	end
	CriticalSectionEnd()
	WaitForMotionDone($axes)
end

Renamed to HomeAsync().

Renamed to JoystickAxisGroupAdd().

Renamed to JoystickRun().

Renamed to JoystickAxisGroupRemoveAll().

Removed. This AeroBasic command tried to compensate for the 5 - 10 millisecond communication delay that occurred between the leader axis and follower axis when the GearingSource or CammingSource is set to PositionFeedback or AuxiliaryFeedback. You can prevent the communication delay by setting the GearingSource or CammingSource to PositionCommand.

Replaced with the $tableOffset argument to the CammingLoadTableFromArray() function.

Replaced by GalvoLaserOutput().

Renamed to GalvoWobbleSetConfiguration().

Replaced by GalvoWobbleOn() and GalvoWobbleOff().

Renamed to GalvoConfigureLaserMode().

Replaced by GalvoConfigureLaserDelays().

Replaced by GalvoConfigureLaserDelays().

Renamed to GalvoConfigureLaserOutputPeriod().

Renamed to GalvoConfigureLaser1PulseWidth().

Renamed to GalvoConfigureLaser2PulseWidth().

Renamed to GalvoConfigureStandbyPeriod().

Renamed to GalvoConfigureStandbyPulseWidth().

Renamed to GalvoConfigureSuppressionPulseWidth().

Renamed to GalvoEncoderScaleFactorSet().

Replaced by GalvoProjectionOn() and GalvoProjectionOff().

Renamed to GalvoProjectionSetCoefficients().

Renamed to IfovSetAxisPairs().

Replaced by IfovOn() and IfovOff().

Renamed to IfovSetSize().

Renamed to IfovSetSyncAxes().

Renamed to IfovSetTime().

Renamed to IfovSetTrackingAcceleration().

The PSO API was reorganized. See More PSO Functions.

Renamed to PositionOffsetSet().

Renamed to PositionOffsetClear().

Replaced by DriveArrayWrite(), DriveArrayRead(), and DriveArrayReadFast().

Removed. To operate in step mode, you can use Studio to step through your AeroScript program. As an alternative, you can use the ProgramStep*() functions.

Replaced by TaskFeedholdOn() and TaskFeedholdOff().

Renamed to TaskMfo().

Renamed to TaskMso().

Replaced by TaskInterruptMotionOn() and TaskInterruptMotionOff().

Replaced by TaskInterruptMotionOff().

Replaced by TaskRetraceOn() and TaskRetraceOff().

Renamed to AcknowledgeAll().

Renamed to FaultAcknowledge().

Renamed to FaultThrow().

Renamed to TaskSetError().

Renamed to TaskSetWarning().

Currently not available. As an alternative, you can use the AppMessageDisplay() function and use MessageSeverity.Error for the severity. The message that you specify shows in Studio but does not cause a task error and does not stop the task from executing. See Application Message Functions for more information. If you must stop the program, you can use this method with the ProgramExit() function.

Removed.

Removed.

Removed.

Replaced by the AppMessageDisplay() function.

Replaced by the AppMessageDisplayDismiss() function.

Replaced by the AppMessageFileOpen() and AppMessageFileSave() functions.

Renamed to AppMessageInputBox().

Renamed to AppMessageBox().

Replaced by AnalogOutputConfigureVectorTrackingMode().

Replaced by AnalogOutputConfigureVectorTrackingMode().

Removed.

Replaced by AnalogOutputConfigureAxisTrackingMode().

Removed. AeroScript does not have an equivalent. For information about how to use temperature compensation, see ThermoComp™ Functions.

Removed. If you generate your motion program with CADFusion or a different CAD/CAM tool that is compatible with the Automation1 controller, you can also use these tools to generate barcodes.

Removed. To enable or disable 1D Axis Calibration, 2D Axis Calibration, Galvo 2D Axis Calibration, or Galvo Power Correction, use the Calibration module of the Configure workspace from within Studio.

Removed.

Renamed to DriveGetItem().

Replaced by DriveEncoderOutputConfigureInput(), DriveEncoderOutputOn(), DriveEncoderOutputOff(), and DriveEncoderOutputConfigureDivider().

Currently not available. As an alternative, you can do Fiber Alignment routines in AeroScript by reading an analog input signal and issuing the necessary MoveLinear(), MoveCw(), and MoveCcw() moves in velocity blending mode (which is VelocityBlendingOn()).

Renamed to CammingFreeTable().

Renamed to CammingLoadTableFromArray().

Removed. At this time, the controller does not specify a camming table file format. As an alternative, you can use the File* functions to read from a file that contains the camming data and then pass that data to the CammingLoadTableFromArray() function.

Removed. This AeroBasic command was removed because when lookahead is active, the controller always operates in a fast lookahead mode.

Renamed to TuningSetMotorCurrent().

Renamed to TuningSetMotorAngle().

Renamed to TuningCommutationInitialize().

Replaced by NormalcyOn() and NormalcyOff().

Replaced by NormalcySetAxes() and NormalcySetTolerance().

Removed.

Removed.

Removed. As an alternative, you can use Drive Data Capture to do functionality that is almost the same. See the Drive Data Capture section of Device Functions for more information. After the position is captured, you can issue the Abort() function.

Removed. As an alternative, you can use Drive Data Capture to do functionality that is almost the same. See the Drive Data Capture section of Device Functions for more information. After the position is captured, you can issue the Abort() function.

Removed. As an alternative, you can use Drive Data Capture to do functionality that is almost the same. See the Drive Data Capture section of Device Functions for more information. After the position is captured, you can issue the Abort() function.

Currently not available. You can try to prevent a background AeroScript program from being stopped. To do this, set the TaskTerminationAxes parameter to a value of 0. You must set the parameter that is on the task.

Replaced by SafeZoneOn() and SafeZoneOff().

Replaced by SafeZoneBoundaryAdd().

Renamed to SafeZoneSetType().

Replaced by SafeZoneBoundaryRemove() and SafeZoneBoundaryRemoveAll().

Replaced by AppDataCollectionSnapshot() and AppDataCollectionStop().

Currently not available. To set the servo on or servo off state of a piezo axis, set the PiezoInitialServoState axis parameter from Studio. Then reset the controller.

Replaced by TuningSetServoLoopGains() and TuningSetFeedforwardGains().

Renamed to DriveSetAuxiliaryFeedback().

Renamed to DriveSetPositionCommand().

Renamed to DriveSetPositionFeedback().

Renamed to SignalLogTrigger().

Removed. You can do a raster scan with the Move functions in AeroScript. For example, you can command the two axes of motion (X and Y) directly. For the scan move, issue one or more MoveLinear(), MoveCw(), or MoveCcw() moves in velocity blending mode (which is VelocityBlendingOn()). For the step move, use the MoveRapid(), MoveLinear(), MoveCw(), or MoveCcw() function before the next scan.

Replaced by TimerRead() and TimerClear().

Removed.

Renamed to SetupTaskWaitMode().

Replaced by DrivePulseStreamConfigure(), DrivePulseStreamOn(), and DrivePulseStreamOff().

Replaced by ThermoCompOn() and ThermoCompOff().

Currently not available.

Renamed to StatusGetAxisItem().

Renamed to StatusGetTaskItem().

Renamed to StatusGetSystemItem().

Renamed to StatusGetAxisItemFast().

When you pass arguments to the G4 G-code in Automation1, Aerotech recommends that you use the P command. For backward compatibility to the A3200, you can continue to use the F command. But the documentation on the G-Code Programming page shows the P command as the only applicable command for the G4 G-code.

When you pass arguments to this G-code in Automation1, you must use the P command. In A3200, you can pass arguments with the F or P command.

Removed. In A3200, this G-code disabled polar coordinates. For information about transformations, refer to Transformation Functions.

Removed. In A3200, this G-code enabled polar coordinates. For information about transformations, refer to Transformation Functions.

Removed. In A3200, this G-code specified the axes that were used with polar coordinates. For information about transformations, refer to Transformation Functions.

Removed. In A3200, this G-code enabled touch-probe monitoring.

Removed. In A3200, this G-code specified the polar and cylindrical axes. For information about transformations, refer to Transformation Functions.

When you pass arguments to this G-code in Automation1, you must specify axes. In A3200, you can specify axis points (pairs consisting of an axis and a numeric expression). For more information about work offsets, refer to Motion Functions.

When you pass arguments to this G-code in Automation1, you must specify axes. In A3200, you can specify axis points (pairs consisting of an axis and a numeric expression). For more information about work offsets, refer to Motion Functions.

When you pass arguments to this G-code in Automation1, you must specify axes. In A3200, you can specify axis points (pairs consisting of an axis and a numeric expression). For more information about work offsets, refer to Motion Functions.

When you pass arguments to this G-code in Automation1, you must specify axes. In A3200, you can specify axis points (pairs consisting of an axis and a numeric expression). For more information about work offsets, refer to Motion Functions.

When you pass arguments to this G-code in Automation1, you must specify axes. In A3200, you can specify axis points (pairs consisting of an axis and a numeric expression). For more information about work offsets, refer to Motion Functions.

When you pass arguments to this G-code in Automation1, you must specify axes. In A3200, you can specify axis points (pairs consisting of an axis and a numeric expression). For more information about work offsets, refer to Motion Functions.

When you pass arguments to this G-code in Automation1, you must use the P command. In A3200, you can pass arguments with the F or P command.

When you pass arguments to this G-code in Automation1, you must use the P command. In A3200, you can pass arguments with the F or P command.

When you pass arguments to this G-code in Automation1, you must use the P command. In A3200, you can pass arguments with the F or P command.

When you pass arguments to this G-code in Automation1, you must use the P command. In A3200, you can pass arguments with the F or P command.

Removed. In A3200, this G-code enabled the mirror-image transformation. For information about transformations, refer to Transformation Functions.

Removed. In A3200, this G-code enabled the parts rotation transformation. For information about transformations, refer to Transformation Functions.

Removed. In A3200, this G-code set the circular interpolation mode (G2/G3/G12/G13) to normal interpolation.

Removed. In A3200, this G-code set the circular interpolation mode (G2/G3/G12/G13) to inverse interpolation.

Removed. In A3200, this G-code enabled block delete mode.

Removed. In A3200, this G-code disabled block delete mode.

Cutter offsets and tool tables are not available in Automation1 at this time.

Cutter offsets and tool tables are not available in Automation1 at this time.

Cutter offsets and tool tables are not available in Automation1 at this time.

When you pass arguments to this G-code in Automation1, you must use the P command. In A3200, you can pass arguments with the F or P command.

When you pass arguments to this G-code in Automation1, you must use the P command. In A3200, you can pass arguments with the F or P command.

Removed. In A3200, this G-code enabled block delete 2 mode.

Removed. In A3200, this G-code disabled block delete 2 mode.

Removed. In A3200, this G-code configured Spindle 1 to use feedrates specified as units/spindle revolution.

Automation1 supports one spindle per task. Use the G95 G-code.

Removed. In A3200, this G-code configured Spindle 1 to spin at the tangential speed. The tangential speed is a constant velocity on the surface of the spindle.

Automation1 supports one spindle per task. Use the G96 G-code.

Removed. In A3200, this G-code configured Spindle 1 to use feedrates specified as a velocity.

Automation1 supports one spindle per task. Use the G97 G-code.

Removed. In A3200, this G-code configured Spindle 2 to use feedrates specified as units/spindle revolution.

Automation1 supports one spindle per task. Use the G95 G-code.

Removed. In A3200, this G-code configured Spindle 2 to spin at the tangential speed. The tangential speed is a constant velocity on the surface of the spindle.

Automation1 supports one spindle per task. Use the G96 G-code.

Removed. In A3200, this G-code configured Spindle 2 to use feedrates specified as a velocity.

Automation1 supports one spindle per task. Use the G97 G-code.

Removed. In A3200, this G-code configured Spindle 3 to use feedrates specified as units/spindle revolution.

Automation1 supports one spindle per task. Use the G95 G-code.

Removed. In A3200, this G-code configured Spindle 3 to spin at the tangential speed. The tangential speed is a constant velocity on the surface of the spindle.

Automation1 supports one spindle per task. Use the G96 G-code.

Removed. In A3200, this G-code configured Spindle 3 to use feedrates specified as a velocity.

Automation1 supports one spindle per task. Use the G97 G-code.

Removed. In A3200, this M-code moved Spindle 0 to the zero position and then disabled the spindle.

Removed. In A3200, this M-code enabled Spindle 1 in the clockwise direction.

Automation1 supports one spindle per task. Use the M3 M-code.

Removed. In A3200, this M-code enabled Spindle 1 in the counterclockwise direction.

Automation1 supports one spindle per task. Use the M4 M-code.

Removed. In A3200, this M-code disabled Spindle 1.

Automation1 supports one spindle per task. Use the M5 M-code.

Removed. In A3200, this M-code enabled Spindle 2 in the clockwise direction.

Automation1 supports one spindle per task. Use the M3 M-code.

Removed. In A3200, this M-code enabled Spindle 2 in the counterclockwise direction.

Automation1 supports one spindle per task. Use the M4 M-code.

Removed. In A3200, this M-code disabled Spindle 2.

Automation1 supports one spindle per task. Use the M5 M-code.

Removed. In A3200, this M-code enabled Spindle 3 in the clockwise direction.

Automation1 supports one spindle per task. Use the M3 M-code.

Removed. In A3200, this M-code enabled Spindle 3 in the counterclockwise direction.

Automation1 supports one spindle per task. Use the M4 M-code.

Removed. In A3200, this M-code disabled Spindle 3.

Automation1 supports one spindle per task. Use the M5 M-code.

Removed. In A3200, this M-code stopped a critical section. (The CRITICAL END command is the AeroBasic equivalent.)

In Automation1, you can use the function CriticalSectionEnd() or function CriticalSectionEndAll() function to stop a critical section.

Removed. In A3200, this M-code let you specify the number of times that you called a local function.

In Automation1, you can do this by using a repeat loop that contains a local function call.

Removed. In A3200, this M-code let you specify the number of times that you called a function from a different program.

In Automation1, you can do this by using a repeat loop that contains a dynamic function call.

Removed. In A3200, this M-code enabled Spindle 1 in the clockwise direction asynchronously.

Automation1 supports one spindle per task. Use the M103 M-code.

Removed. In A3200, this M-code enabled Spindle 1 in the counterclockwise direction asynchronously.

Automation1 supports one spindle per task. Use the M104 M-code.

Removed. In A3200, this M-code enabled Spindle2 in the clockwise direction asynchronously.

Automation1 supports one spindle per task. Use the M103 M-code.

Removed. In A3200, this M-code enabled Spindle 2 in the counterclockwise direction asynchronously.

Automation1 supports one spindle per task. Use the M104 M-code.

Removed. In A3200, this M-code enabled Spindle 3 in the clockwise direction asynchronously.

Automation1 supports one spindle per task. Use the M103 M-code.

Removed. In A3200, this M-code enabled Spindle 3 in the counterclockwise direction asynchronously.

Automation1 supports one spindle per task. Use the M104 M-code.

Removed. In A3200, this M-code started a critical section. (The CRITICAL START command is the AeroBasic equivalent.)

In Automation1, you can use the CriticalSectionStart() function to start a critical section.

Removed. In A3200, this M-code moved Spindle 1 to the zero position and then disabled the spindle.

Removed. In A3200, this M-code moved Spindle 2 to the zero position and then disabled the spindle.

Removed. In A3200, this M-code moved Spindle 3 to the zero position and then disabled the spindle.