Re: [foxboro] Integrator 30 for Modbus quirk
- From: "Loudermilk, Virgil:" <Virgil.Loudermilk@xxxxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 5 Feb 2009 07:13:22 -0500
We do have the MDSCAN period and phase matching the blocks, but stopping
scanning when period and phase is changed sounds familiar and
unfortunate if true. We did move it to a more unloaded phase. Would
delete/undelete fix that?
Currently we are going to try a real Modicon PLC on our test drop, with
Heartbeat set to 1 in the ECB16. The GSC said that Heartbeat is
important for multidrop, and we are set up with heartbeat configured on
all the other drops, so this sounds hopeful. But what's odd is that I
saw no heartbeat commands in the data analyzer - but I guess there's a
possibility that the parser we use might miss heartbeat commands, I
might go back and look at the REALLY raw data, painful as it is,
unparsed and in hex. I did find out that Wintech Modsim32 does not
support heartbeat.
On another note, FBM224 or 230/231/232/233 for a replacement? It seems
like the 224 is very reliable and straightforward, but will go obsolete
sooner than the 230 series, which sounds like a real pain as far as
security concerns from what very little I have heard about it here.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of William C Ricker
Sent: Thursday, February 05, 2009 12:54 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Integrator 30 for Modbus quirk
Seem to remember something about the importance of matching period and
phase
in the blocks talking to a slave. Maybe the MDSCAN had to match the ECB
or
something like that.
We saw problems when tried to adjust phasing to level the load. We
found
that scanning stopped when periods and/or phases were shifted. Problem
now is that it's been a couple of years since the last time we
programmed
one of those and we can't remember the exact details.
William C Ricker
FeedForward, Inc.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Loudermilk, Virgil:
Sent: Wednesday, February 04, 2009 8:47 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Integrator 30 for Modbus quirk
We are trying to commission a new drop on an RS485 Modbus network on an
MG30. We can't get the Integrator to poll this new device. We've
deleted and undeleted the ECB, and the compound with the MDSCAN. But
when looking at the traffic, we never see a poll for the new device.
The thing is pretty loaded with 27 Modbus devices at a 4 second scan. A
data analyzer still shows some gaps of a few hundred milliseconds where
it SHOULD be able to fit in just one more. Any ideas? Thanks.
_______________________________________________________________________
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:
