I have 8 devices conected via modbus tcp and I can read tags correctly out of 7 of them with the same address structure. The one not working just sets the value to Bad
Since they are all the same device I know that I am connecting propperly so the problem should be on this one speciffically. Yet when I check the IP outside of Ignition, the data shows fine.
I tryed making a new device changing names, settings... doesn't work. Also the Gateway can't read the value, only returns null.
Show the rest of your tag properties, of the broken one and a working one.
Here is for a working one:
Here one not working:
This OPC Item Path syntax means you've chosen to set up an "Address Map" on the driver.
Does the device that isn't working have an address map set up and is it the same as the others?
Yes, all have the same address map. Same devices showed before, first the working one:
And the one not working:
if I go to the Gateway:
Are there errors in the gateway logs from this device?
Is zero-based addressing enabled for this device?
the log only shows this:
INFO | jvm 1 | 2025/02/05 15:45:55 | E [d.M.ReadInputRegistersRequest ] [15:45:55.088]: Received response with ExceptionCode: 0x0B (GatewayTargetDeviceFailToRespond). unitId=1, startAddress=0, quantity=64 device-name=SS_IBI1_SOLA_INVE1_2
yes, zero-based addressing is enabled:

The Modbus gateway device you're communicating with is returning that ExceptionCode. There doesn't appear to be anything wrong on the Ignition side.
Those two mappings are pointing at the same registers. Is that intended? (I'm not sure the driver can handle that.)
Consider not using mappings. Just use items paths like [device]1.IRUS0
through [device]1.IRUS63
.
I assumed those mappings were for separate devices / IP addresses, but if that's not the case, and they are pointing at the same gateway device, then yes they are.
1 Like