Re: [foxboro] FBM230/Modbus slave too fast problem

  • From: Pablo Lioi <plioi@xxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Thu, 12 Mar 2015 15:00:48 +0000

Scott,
As I stated before, my driver is version 1.1 and I am using B0700BG-C.
Supported device counters are Good Messages Sent, Good Messages Received and 
Timeouts.
I suppose I should upgrade the driver...
Regards
Pablo Lioi
> From: Scott.Landry@xxxxxxxxxxxxxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Date: Thu, 12 Mar 2015 08:51:55 -0400
> Subject: Re: [foxboro] FBM230/Modbus slave too fast problem
> 
> 
> 
>     Pablo,
> 
> 
>     Latest Modbus driver is V2.3.4   (B0700BG-J document)
> 
>     If you are using RS-422 or RS-485;
> 
> Set the RS-232 switches for the channel such that the C5 and C6 switches are 
> in
> the CLOSED position and the rest of the switches are in the OPEN position (see
> Figure 4-15 on page 39).
> 
> 
> 
>     Something else I do when I set a FDSI interface up is configure all the 
> port and device counters, possible.
>     I also have a graphic I re-use so they are easy to see (depends on the 
> driver)  some drivers
>     have a script to build the blocks and graphic(s).  Although not Modbus 
> driver.
> 
> 
> Port Counters:
> 1. Number of good messages sent
> 2. Number of good messages received
> 3. Number of parity errors
> 4. Number of framing errors
> 5. Number of checksum errors
> 6. Number of transmit errors
> 7. Port Scan Time
> 8. Reset Counters
> 
> Device Counters:
> 1. Number of good messages sent
> 2. Number of good messages received
> 3. Response timeout
> 4. Number of Modbus Device Exception responses
> 5. Number of Modbus gateway exception responses
> 6. Last Error message received from the gateway
> 7. Configured Options
> 8. Number of Over Scans
> 9. Over Scan time high
> 10. Group Scan time
> 
> 
>    Regards,
> 
> 
>     Scott
> 
> ________________________________________
> From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf 
> Of Landry, Scott [Scott.Landry@xxxxxxxxxxxxxxxxxxxxxx]
> Sent: Thursday, March 12, 2015 7:14 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] FBM230/Modbus slave too fast problem
> 
>     Pablo,
> 
> 
>     Try playing with the driver scan rate, slower and faster.  See what 
> difference it makes, if any.
> 
>     Are you using an xml  device config file ?
> 
> 
>     Regards,
> 
> 
>     Scott
> 
> ________________________________________
> From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf 
> Of Pablo Lioi [plioi@xxxxxxxxxxx]
> Sent: Thursday, March 12, 2015 5:10 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] FBM230/Modbus slave too fast problem
> 
> I'm using RTU, but my communication is not a radio link. The FBM230 and the 
> slave are inside the same cabinet.
> 
> > From: dmarc-noreply@xxxxxxxxxxxxx
> > Subject: Re: [foxboro] FBM230/Modbus slave too fast problem
> > Date: Wed, 11 Mar 2015 15:18:10 -0400
> > To: foxboro@xxxxxxxxxxxxx
> >
> > Are you using Modbus rtu or ASCII? On radio units I have had better luck 
> > with Modbus ASCII.
> >
> > Sent from my iPhone
> >
> > > On Mar 11, 2015, at 1:28 PM, Pablo Lioi <plioi@xxxxxxxxxxx> wrote:
> > >
> > > Hi everybody,
> > > I'm sending this again because for some reason carriage returns seem to 
> > > have been lost and the post was difficult to read.
> > > In the past I had a serious problem with an FBM230 with Modbus protocol 
> > > communicating with a slave using RS-232, in RTU mode.
> > > When the slave response to any query from the master arrived too fast, 
> > > the FBM would ignore the response and retry. I finally worked around the 
> > > problem delaying the response from the slave a few milliseconds using a 
> > > setting (at the slave device) that was meant for radio communication (RTS 
> > > to TxD delay).
> > > I am now facing the same problem again, with another slave device. The 
> > > problem is that this time I have no way to delay the slave response. I 
> > > tried using RTS/CTS handshake on the RS-232 line, but the problem 
> > > remains. I know for sure that cable and switch settings at the TA are ok 
> > > because I'm looking at the line with a protocol analyser and see correct 
> > > query and response messages.I would like to know if somebody else has 
> > > experienced this problem too.
> > > Regards
> > > Pablo Lioi
> > > TOTAL AUSTRAL S.A.
> > > Tierra del Fuego - Argentina
> > >
> > >
> > >
> > > _______________________________________________________________________
> > > 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 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
> 
> 
> ______________________________________________________________________
> 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
>  
                                          
 
 
_______________________________________________________________________
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: