
AN00174-001 Modbus TCP Fieldbus Option for MotiFlex e100.doc
22
2222
22 of
of of
of 22
2222
22
The ‘Save Device Configuration File…’ button can be used to save the DCF file to PC disk should
you need to save this for future use. Check the ‘Download device configuration to the controller’
and ‘Reset controller after download’ boxes and click on ‘Finish’ to transfer the DCF file to the
NextMove e100 and force it to restart.
Once the NextMove e100 has restarted you are ready to test if the client/PLC is able to read/write
data on the NextMove.
Testing the Exchange of Process Data
Whilst connected to the NextMove e100 use WorkBench v5.5 to select the ‘Net Data’ tab within
the Spy Window on the right hand side of the Edit & Debug area.
Click on the Add… button and add a Watch to NetData Channel 1 (Data Type Float). Repeat this
for NetaData Channel 2 (Float), NetData Channel 3 (Float) and NetData Channel 4 (Float).
Your Net Data Watch Window should look something like this…
Now poke some values into NetData Channels 3 and 4 on the NextMove (we entered 12.34 and
56.78 as you can see above).
Ask the Modbus client/PLC to read Modbus registers 256 and 258 and you should receive the
values entered for these two NetData channels.
Now using the Modbus/TCP client/PLC, write some Float data to Modbus registers 0 and 2 (i.e. the
first two floats). You should see these appear in the NextMove’s NetData Watch Window (as you
can see from above, we wrote the values 1.11 and 2.22).
Congratulations! You have now completed this Application Note. You can now see how simple it is
to exchange data in either direction between a Modbus/TCP client device and a NextMove e100
using the MotiFlex e100 with Modbus/TCP Fieldbus Option Card.
DeviceNet is a trademark of the Open DeviceNet Vendors Association
Commenti su questo manuale