I have a setup as follow,
Comm. Resource Name | Device name | Type | Physical Comm. Resource Name |
Rack 1 |
|
| 192.168.1.1 |
| Slot0 | NI-9149 | 192.168.1.1 |
| Slot1 | NI-9208 | 192.168.1.1 |
| Slot2 | NI-9208 | 192.168.1.1 |
| Slot3 | NI-9208 | 192.168.1.1 |
| Slot4 | NI-9208 | 192.168.1.1 |
| Slot5 | NI-9208 | 192.168.1.1 |
| Slot6 | NI-9208 | 192.168.1.1 |
| slot7 | NI-9361 | 192.168.1.1 |
| slot8 | NI-9361 | 192.168.1.1 |
Rack 2 |
|
| 192.168.1.2 |
| Slot0 | NI-9149 | 192.168.1.2 |
| Slot1 | NI-9361 | 192.168.1.2 |
| Slot2 | NI-9361 | 192.168.1.2 |
| Slot3 | NI-9425 | 192.168.1.2 |
| Slot4 | NI-9425 | 192.168.1.2 |
| Slot5 | NI-9476 | 192.168.1.2 |
Our Architecture is to communicate the IO with Kepware KEPServerEX 6 via Modbus TCP. In the older IO we could do this via MAX once configured we can already assign address, however now we have added the IO via LabView (image below) but can’t seem to get it on KEPWARE over MODBUS TCP.
New setup MAX
New setup LABView
Clarifications:
- Is there anything else required for us to configure?
- Do we need FPGA or all can work on Scan Interface? As for NI9361 would indicate not supported in Scan Interface (image below)
- Is there a Modbus Master or Slave (server or client) built into the NI 9149?