Modbus Connection Issue

I’ve run into an odd one here. I have a project I’m migrating from FPMI/FSQL. The old system was using Kepserver, but I’m switching it over to the Ignition Modbus driver. The controller is a Horner Electric QX451. If I set the project up using the Modbus v1 driver, it connects, I can pull data, and everything is fine. If I set the project up using the Modbus v2 driver (which is what’s licensed currently) it will connect, but then drop out after a few seconds, and I can’t pull any data. Anyone seen behavior like this before? Are there any solutions other than get the license modified to add the v1 driver and use that? Thanks!

Joe

Can you send in your log files, or better yet, call support and let them poke around? There shouldn’t be any reason v1 would work and v2 wouldn’t.

OK, never mind. I walked away for a while to work on something else, came back, re-created the device, and it’s working now. My assumption is that is was too early on a rainy morning, and I lost the ability to spell correctly or something. :blush:

Several questions:

Should a Modbus v1 coniguration and addressing work with a Modbus v2 driver?

Can both drivers coexist in the same gateway talking to the same PLC?

Should exporting the addressing from v1 and importing in v2 result in a working system?

Thanks for the help.

Dennis

Should a Modbus v1 coniguration and addressing work with a Modbus v2 driver?

Yep!

Can both drivers coexist in the same gateway talking to the same PLC?

Yep! But as of 7.3 you can’t add new Modbus v1 devices.

Should exporting the addressing from v1 and importing in v2 result in a working system?

The addressing is exactly the same. The only thing to watch out for is poorly named prefixes, i.e., any prefix that could also be interpreted as an address. This makes things like HR*, IR*, C*, and DI* poor choices for prefixes.

I currently have a Panel Edition that was at 7.2.9.

It had Modbus v1 with one device defined with some address ranges defined.

I got the CD Key upgraded to 7.3.

Since it had Modbus v1, that is now running in demo mode. It still works but times out.

I exported the addresses and imported them into a modbus v2 instance of another device. This device was given the same ip address as the modbus v1 device.

I tried disabling one and enabling the other, while swapping the names of the devices.

So only one modbus device is active at once.

This procedure did not produce identical results. I don’t understand why.

Help!

Dennis

Can you call support and have them take a look?

Kevin, I finally got around to looking at the installation again.

I have one Modbus v1 running talking to the machine.

I have one Modbus v2 running talking to the same machine.

I got it to work. I had to check check the swap words box in the Modbus v2.

The Modbus v1 instance does not have it checked.

Does that sound right to you? Doesn’t to me.

Thanks,

Dennis

Doesn’t sound right to me either. They should behave the same…