Re: [foxboro] FBM232 Modbus Setup Issues

  • From: "Johnson, David" <David.Johnson@xxxxxxxxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Thu, 5 Mar 2015 16:15:35 +0000

Maks,

To expound on what the others have already said, the FDSI driver not only 
expects the registers you ask for to be there, but all of the intervening 
registers.  Based on our lab testing, the FDSI will attempt to maximize 
throughput by using one read request if it would be more efficient to do so.  
So if I build IINs for registers 30001 and 30004 the driver will send one 
command asking for 30001 for 4 bytes (30001, 30002, 30003, 30004) . This is 
fine as long as the slave will respond to this.  Some slave devices do not 
implement all the registers (this is not compliant with the Modbus "standard", 
if there is such a thing) . So, even if 30001 and 30004 exist, the driver will 
fault if 30002 or 30003 fail to respond to a read request.  If this happens you 
have to use the xml files that the FDSI supports and build "transaction files" 
(FBM224 lingo) for each contiguous data segment.  FireEye devices, Alstom 
BlueLine, and many others require this type of work around.

Does that make sense?

Regards,
David

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Maks Wilde
Sent: Wednesday, March 04, 2015 11:01 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FBM232 Modbus Setup Issues

Dear List,
I am setting up an FBM232 using Modbus TCP. The ECB200 and ECB201 blocks are 
both showing good in system manager and all good green in FoxView.

As soon as I build an IIN or BIN block to try to read from the device my
ECB201 block fails and reads:
DVC FAIL (red)
OFF SCAN (grey)
DCI READY (cyan)
DVC ENABLD (cyan)
DVC FAIL (cyan)

To get back online I have to delete the IIN/BIN block and disable then 
re-enable communication on the ECB201. I've set up the ECBs the same way I have 
for other working ones but the device I'm talking to is different.

Any suggestions as to what could be wrong? How can I determine if the problem 
is on the Foxboro end or the slave device?

Many thanks,

Maks Wilde

--
Confidentiality Warning: This message and any attachments are intended only for 
the use of the intended recipient(s), are confidential, and may be privileged. 
If you are not the intended recipient, you are hereby notified that any review, 
retransmission, conversion to hard copy, copying, circulation or other use of 
this message and any attachments is strictly prohibited. If you are not the 
intended recipient, please notify the sender immediately by return e-mail, and 
delete this message and any attachments from your system.




_______________________________________________________________________
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


________________________________

Confidentiality Notice:

The information contained in this message is private and confidential. This 
information is intended only for the individual or entity named above. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any use, review, dissemination, distribution, copying or action taken 
based on this message or its attachments, if any, is strictly prohibited. If 
you are not the intended recipient, please contact the sender by reply email 
and delete or destroy all copies of this message and any attachments. Thank you.
 
 
_______________________________________________________________________
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