Update: [B]Solved![/B] Turns out there was a line of code missing in the function 15 subroutine. The developers are aware of the issue and will be implementing the fix in the next release. Thanks for all of your help!
I’ve been working with the Modbus integration kit for the last few days and I still can’t get it working with my slave device.
The general behavior is that the slave device responds to Modbus commands from a standalone utilty, but doesn’t respond as expected to Pac Control. More specifically, I’m turning on a digital output (coil) from the standalone utility and the PAC Control routine is turning off the output unexpectedly. Autostepping through the main chart (Modbus_Master_M1) shows that it’s being turned off when it enters the sub “PACModbusMaster15_Force_Multiple_Coils”. I’m watching the default watch-window for that sub and it indicates that the connection is open, the status is “OK” and the number of successful messages transmitted increments each time through the main loop.
At this point I think it must be an offset issue, but the standalone doesn’t seem to require any unusual offsets. Perhaps there’s something else that I haven’t initialized?