Re: [foxboro] FBM230 configuration

Hi list,

Brian wrote:
> Has anybody on this list configured a FBM230 yet?

We're just using in our current project six pairs of FBM231, (which is just
the redundant version of the FBM230) yes.

> I am trying to stage a connection to a GE Fanuc PLC via 
> rs-232 (modbus), with no luck so far. The transmit led 
> flashes every few seconds (with a heartbeat) but even if I 
> loop back pin 2&3 the receive led on the FBM will not flicker.
> I suspect a problem with the .xml configuration files.

Well, we had RS485 Modbus and also some problems, most were with polarity,
termination and pinouts of plugs. You can't make too much wrong with the XML
files. But you must be careful to install the FBM in the right order. First
check, if you have the latest EEPROM version. Then create the XML file in
the right location and check, if the latest FDSI Modbus Driver (Modbus.ziph)
is there as well. Install the ECB200 (ECB202 on FBM231) and check all
settings with the documentation. Now download the Software to the FBM with
SMDH and reboot. After that install the database, which actually loads the
XML file to the FDSI. Check all displayed information in SMDH under
Equipment Info. Do you see correct Driver name, XML File name, Ports
enabled, ROM and Software Versions?

Get documentation of all pinouts and plugs on the way of the link. Draw a
hardware loop of the whole link with all information from Pin numbers, cable
colors etc. and check, if everything is OK. When Using RS485, check with and
without termination on both sides of the link. Set all DIP-Switches on the
TS of the FBM230/231 to the OPEN position when using RS485. When using
RS232, check carefully the settings of all DIP switches. Ask someone who
really knows the meaning of all these, if you don't. ;-) If all electric
stuff is definetely OK, start communication with a single integer and a
single bit and test if that works.

If you spent more than 8 hours until here, stop work and get a Modbus
Protocol Analyzer in the line and someone, who really knows about all the
bits and bytes in the Modbus protocol. 

We are currently working on a project with 13 different serial modbus links,
we tested already four of them and three of them had issues with the Modbus
implementation on the other side. Either it was Float values not properly
packed into Modbus integers or swapped Bits and Bytes in the Registers. We
solved all issues with the Analyzer and a good expert in house.

From my experience, 99% of all problems have their reasons on the other
party's side, if all electrical stuff is OK, and I'm not kidding.

Good success!

Best regards -

Marcel Sieling
Senior Application Consultant

Invensys Systems GmbH
Emanuel-Leutze-Str. 11
40547 Duesseldorf
Germany
T: +49-211-5966-302
F: +49-163-99-5966302 
M: +49-163-5966302
Skype:  marcel.sieling
mailto:marcel.sieling@xxxxxxxxxxxxxxxx
http://www.foxboro-deutschland.de


> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx 
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Brian Bates
> Sent: Thursday, February 16, 2006 3:44 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] FBM230 configuration
> 
> 
> 
> Good morning all.
> 
> Has anybody on this list configured a FBM230 yet?
> 
> I searched the Cassandra archive, and have found no hits. 
> .....I suspect that we are on the bleeding edge with this one.
> 
> I am trying to stage a connection to a GE Fanuc PLC via 
> rs-232 (modbus), with no luck so far. The transmit led 
> flashes every few seconds (with a heartbeat) but even if I 
> loop back pin 2&3 the receive led on the FBM will not flicker.
> 
> I suspect a problem with the .xml configuration files.
> 
> 
>       -Regards, Brian Bates.
> 
> 
> --------------------------------------------------------------
> ----------------
> 
> Confidentiality Message
> This e-mail message is confidential and is intended for the 
> exclusive use of the addressee. Any other person is strictly 
> prohibited from disclosing, distributing or reproducing it. 
> If the addressee cannot be reached or is unknown to you, 
> please inform the sender by return e-mail immediately and 
> delete this e-mail message and destroy all copies. 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:             http://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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: