Re: [foxboro] FBM232 Modbus Setup Issues

  • From: "Brown, Stanley" <stan.brown@xxxxxxxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Fri, 6 Mar 2015 15:17:29 +0000

If I am not mistaken, the reason ModBus is so widely used to is that Modicon 
chose to not make it proprietary. An early example of why Open Source is so 
successful. Other's such as AB with their DF1 protocol, did I think enforce IP 
restrictions.

-----Original Message-----
From: Stan Brown [mailto:stanb@xxxxxxxxx] On Behalf Of McQuaid, Paul
Sent: Friday, March 06, 2015 03:48 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FBM232 Modbus Setup Issues

I was once told, many many years ago, in a galaxy far far away.... oops getting 
carried away....

That there was a protocol called JBUS it wasn't Modbus but, I understand was an 
early attempt to get past IPR. An "almost" identical protocol as Modbus but 
incremented by 1 Some manufacturers at one time mistakenly used JBUS addressing 
but called it Modbus......so I was led to believe anyway.....

Best Regards

Paul McQuaid

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Kinsinger, Matthew R
Sent: 05 March 2015 14:44
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FBM232 Modbus Setup Issues

There are plenty of free Modbus and Modbus TCP readers you can install to test 
communication to the device from your PC. ModPoll or something to that affect I 
remember working well when I needed it. Try a register in the middle of 3 
registers you think exist. I've found far too many devices you have to shift 
the register number by 1 in either direction to match up with the stated 
register number.

Matt Kinsinger
mkinsinger@xxxxxxx
330-825-1208 office
330-472-1454 ppg cell

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Badura, Tom
Sent: Thursday, March 05, 2015 9:38 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FBM232 Modbus Setup Issues

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



_______________________________________________________________________
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


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________

*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person.


_______________________________________________________________________
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



________________________________

The information contained in this message and any attached files may be 
privileged and/or confidential and protected from disclosure. If you are not 
the intended recipient, any disclosure, copying, distribution or use of any of 
the information contained in or attached to this transmission is strictly 
prohibited. If you have received this transmission in error, please so notify 
the sender immediately without reading it. Also, please promptly destroy the 
original transmission and its attachments. Any views or opinions presented in 
this message or attachments are those of the author and do not necessarily 
represent those of KapStone Paper and Packaging Corporation or its subsidiaries.
 
 
_______________________________________________________________________
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

Other related posts:

  1. Home
  2. foxboro
  3. Archive
  4. 03-2015