IOGet()

IO * IOGet

(

int32_t

nodeNumber

)

Description:

IOGet returns a pointer to an IO object using its node number and initializes its internals.

Parameters

nodeNumber

The reference number of the node the IO is on. The first I/O node is the 0th Node. Non-I/O Nodes are not considered for this numbering schema.

Returns

(IO*) A pointer to the IO specified.

Note

The RMP assigns a logical number to each network node that it encounters during initialization. This number starts with 0 and will be incremented for each node discovered...

Creation Methods Info

Part of the Create and Initialize RapidCode Objects method group.

🔔 Important Usage Instructions

All creation methods, such as Create(), AxisGet(), NetworkNodeGet(), etc. Each return valid pointers to RapidCode objects. These pointers are never null, even when there is an error during object creation.

🔔 API Differences (C# vs. C++)

In the C# API, the pointers are replaced by references due to differences between C++ and C#. The creation methods return a reference to the object instead of a pointer. However, the method calls and error handling procedures remain the same. Null references are not returned by the creation methods in C#. Always check for errors after object creation, as described above.

⚙️ Error Checking After Creation

Immediately after the creation of a RapidCode object, you need to check if there were any errors during its creation. You do this by calling the ErrorLogCountGet() method on the created object. If ErrorLogCountGet() returns a value greater than zero, it means there were errors during the object creation.

⚙️ Handling Errors

To handle the errors, you call the ErrorLogGet() method once for each error on the created object to retrieve an RsiError object. You can then inspect the RsiError object to understand more about the error.

⚙️ Helper Functions

RapidCode also provides helper functions in both C++ and C#, like HelperFunctions::CheckErrors(), that work with all RapidCode objects. These helper functions operate on RapidCodeObject, hence they are compatible with all RapidCode objects. For example:

⚙️ Object Cleanup

Any and all objects created by RapidCode creation methods will be cleaned up by calling MotionController::Delete(). This should be done when your application is finished using RapidCode objects.

See also

ErrorLogCountGet, ErrorLogGet, Delete, HelperFunctions.CheckErrors

Deprecated

Use MotionController::NetworkNodeGet instead.

Examples

SingleAxisSyncOutputs.cpp, Template.cpp, UserLimitDigitalInputAction.cpp, and VelocitySetByAnalogInputValue.cs.