Technical FAQs

Ask a Question

I/O scanning Momentum Ethernet nodes with Unity Pro.

Goals and Symptoms


This resolution is designed to outline the steps to configure the Ethernet connection on a Quantum HE controller 140-CPU-651-50 to poll a Momentum mixed base.

Facts and Changes


The controller that will be used in the Quantum HE 140-CPU-651-50.
The controllers onboard Ethernet port will have the I/O scanning functionality enabled, and it will be configured to poll the Momentum node.
The Momentum analog and discrete mixed input / output base is the 170-AMM-090-00.
The Momentum base uses the Ethernet top-hat 170-ENT-110-00 to enable TCP/IP communication.

Causes and Fixes


Open Unity and create a new application, selecting the 140-CPU-651-50 controller.
Expand the Communication folder in the project browser, and right click on Networks to add a new network.



Select an Ethernet type network, give said network a name, and click OK.



The newly created network will appear in the project browser; double click on the network name to open it configuration screen.



Being that the controller chosen for this application is the 651-50 and we are configuring the onboard ethernet port select the TCP/IP 10/100 Extended connection.
Enable I/O Scanning clicking on the drop down arrow and selecting YES.
Enter the IP address, Subnet mask, and Gateway the controllers Ethernet port will be using.
Choose the Ethernet ll framing type, for most the ENT 110 00 tophat does not support 802.3 framing.



Click on the IO Scanning tab to configure the table.
In the I/O scanner node table enter in the IP address of the ENT top-hat.
Specify a read and write both of which will have a length of 5 words. (The length of 5 for the read / write message will be explained later)

Note: You will notice in this example the read and write address of the slave node is the same Index0. This was intentional entry and necessary to read and write to the ENT tap-hat and intern the AMM-090 I/O base. When an ENT top-hat is used it has no %MW's (4X) registers to read and write from. Rather the ENT top hat is intelligent enough to know that when a Modbus Ethernet request is received to read and write registers both with a length of 5 to accept the message and parse the appropriate information to the desired memory location.

It is important to specify different Master addresses for read and write to ensure there is no overlap in the controllers memory addresses.



From the Project Browser open the Local Quantum Drop I/O map and double click on the onboard Ethernet port.


Click the drop down arrow and select the created Ethernet network.




The image below is from page 484 in the TSX Momentum I/O Base User Guide Rev 5.0 (PN: 870-USE-002-00); outline the 5 registers that will are be read and written to the ENT top-hat and intern the I/O base.



In the image below you will see an Animation Table from Unity Pro showing actual values being read and written to the 170-AMM-090-00 base.


Was this helpful?
What can we do to improve the information ?