how do i get multiple tcp/ip modbus to work together

[Timmar]

UncleBump,

Good Idea, Already tried it.

I use real time controllers so messing with the ethernet port isn't an option.

I am using a cRIP-9081 at the moment, it has 2 Ethernet ports.

I trialled setting up the secons one but alas, you can't set Slave affinity to an ethernet port/IP address, so you are still looking at the same library just through a different window.

This would be great if I could only have 1 Modbus Master.

[JimMacD]

iTim,

You are not alone in your frustration. I was trying to setup a test environment where a cRIO "simulated" multiple modbus devices, so I could have a full network of devices, without actually purchasing them.

I'm going to use the Serial IO servers (masters on one cRIO, slaves on the simulation cRIO) instead for the bench-test environment, and just use a null-modem cable from COM1. When I go to deploy to the actual machine/system, I will reconfigure the IO servers (masters) to be ethernet.

Could you use a MODBUS serial to ENET gateway in your application?

[Timmar]

It's a good idea but not right for me.

I was trying to use the method to simplify the my layered architecture and as a workaround to Labview's incessent need to modify files even when they haven't been modified (Modbus & NPSV Libraries seem to bind themselves to a project, so if you want to use them in multiple projects and use source control it becomes a real pain).

I develop products, so sprinking extra hardware is not a good economics. I would need extra serial cards and converters to achieve this.

iTm.