Baldor MN1274 06/2001 B.2.9.2 Analog I/O Access, B.2.9.3 Extra Analog I/O Functionality

Similarly:

REMOTEOUT.1.2 = 255 will set the state of all of the outputs on node 2 to 255 decimal.

The second method uses the REMOTEINX and REMOTEOUTX keywords and accesses individual inputs or outputs. Each input/output can either be ON (1), or OFF (0).

For example:
? REMOTEINX.1.2.0	will read the state of input 0 on node 2.
The command:
? REMOTEOUTX.1.2.0	will read the state of output 0 on node 2.
Similarly,
REMOTEOUTX.1.2.0 = 1	will set the state of output 0 on node 2 to ON (‘1’).

B.2.9.2 Analog I/O Access

Analog inputs and outputs can have any value between 0 and 100. This value will represent a voltage equal to the specified percentage of the full-scale voltage; please see the manufacturer’s instructions.

For example:
? REMOTEADC.1.2.0	will read the value of analog input channel 0, on node 2.
The command:
? REMOTEDAC.1.2.3	will read the value of analog output channel 3, on node 2.
Similarly,
REMOTEDAC.1.2.3 = 100	will set the value of analog output channel 3, on node 2, to 100.

B.2.9.3 Extra Analog I/O Functionality

Mint provides some extra functionality with analog input nodes. The value of an analog input will often change constantly. This can cause a lot of CAN ‘traffic’ to be generated if the node is event driven because the node will generate a CAN message every time the input changes. The REMOTEMODE keyword is provided in Mint to allow the user to set the analog node to either Event (0) or Cyclic (1) mode. Setting it to Cyclic mode will force the node into generating CAN messages on a cyclic basis, in synchronization with a SYNC message that is generated by the network manager. This will help reduce CAN traffic and also allow the user to predict the level of activity on the CAN bus more easily.

The following example will set the analog input channels of node 2 to Cyclic mode:

REMOTEMODE.1.2 = 1

Running in Event mode will cause a CAN message to be generated every time the input changes.

116