The RMP Motion Controller APIs

◆ Delete()

void Delete ( void  )
Delete the MotionController and all its objects. This includes all of the first-class RapidCode objects (Axis, MultiAxis, NetworkNode, IO, IOPoint, etc.). After a MotionController and all its objects have been deleted, you can use Create() again.

Every single first-class object pointer will now be pointing to free'd memory. You will get access violation exceptions (or worse). We suggest setting the MotionController pointer to null after this is called.

Sample Code:
// -- C++ -- //
MotionController *controller = MotionController::Create();
RapidCode object destructors are private. Delete() provides users a method to clean up all RapidCode objects. This method is required if you are planning to re-create the MotionController or to fully destroy (and free) all objects when you application closes.
See also
CreateFromSoftware, Create
ControllerInterrupts.cpp, HardwareLimits.cpp, HelperFunctions.cs, Memory.cpp, MotionHoldReleasedBySoftwareAddress.cpp, MultiaxisMotion.cpp, PathMotion.cpp, PVTmotionMultiAxis.cpp, SingleAxisSyncOutputs.cpp, StreamingMotionBufferManagement.cpp, SyncInterrupt.cpp, SyncOutputWithMotion.cpp, Template.cpp, Template.cs, UpdateBufferPoints.cpp, and UserLimitDigitalInputAction.cpp.
static MotionController * Create()
Initialize and start the RMP EtherCAT controller.