Maks, A few items we ran into when getting or ModbusTCP started. The symptoms sound like you are trying to access a bad address in the device. Do you have DCI READY (on ECB201 display and System Management) prior to connecting the DCI blocks? As stated in a few other replies, you need to verify that all addresses (registers, coils, etc.) requested by the FBM232 ModbusTCP driver actually exist in the device. Note that the driver will by default issue one command for all contiguous registers where possible. I.E. if you create a DCI block for Modbus register 1 (40001) and another for Modbus register 100 (40100) the FBM will issue a read/write multiple register command for all 100 registers (40001 through 40100). If not all 100 registers actually exist in the device it will respond with an error. The way around this is to create and load a Device File that specifies the specific addresses available in the device (DVOPTS = MODBUS+XML). Note also that some devices have an offset of +/-1 in the address specified in Foxboro verses the address in the device. One other item we ran into is that by default the Foxboro ModbusTCP driver uses Unit ID 255 which should specify any/all units. We have one brand of PLC that did not like this and we had to specify Unit 1 (DVNAME = IP.Address/1). As I recall this should up as a problem even before trying to connect DCI blocks. Tom Badura Plastics Engineering Company tbadura@xxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Maks Wilde Sent: Thursday, March 05, 2015 8:12 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] FBM232 Modbus Setup Issues Normand/Dirk, Thank you for your replies. The device I'm trying to communicate with is a Smith Meter Accuload III. Not sure if anyone has experience with these. They have a lot of options on the device end of things and we're trying to see if maybe something is not set right for the FDSI to communicate with it. At this point I can't even read a single coil from it without faulting the ECB201 block. Any other suggestions are very welcome :) Maks Wilde _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave