[foxboro] AW: Modbus FBM, was "Back to forcing an ABSCAN to

Daren,

for non redundant integration of Modbus to CP40 nodes we also used =
"nacked"
Micro I/A as shown in PSS 21H - 7C1 B3.

Regards

Heinz Maurer
Vertriebsbuero Duesseldorf

Invensys Systems GmbH
Heerdter Lohweg 53-55
40549 Duesseldorf
Germany

Tel.:     +49 (0) 211 5966 -333
Fax.:    +49 (0) 211 5966 -300
Mob.:   +49 (0) 173 25 32 515
Email:   heinz.maurer@xxxxxxxxxxxx
http://www.invensys-process-systems.de




> -----Urspr=FCngliche Nachricht-----
> Von:  Daren Bishop [SMTP:dbisho@xxxxxxxxxxxx]
> Gesendet am:  Mittwoch, 11. Dezember 2002 19:04
> An:   foxboro@xxxxxxxxxxxxx
> Betreff:      Re: [foxboro] Modbus FBM, was "Back to forcing an ABSCAN to=20
>=20
>=20
>      Marcel,
>     =20
>     =20
>      *************************************************************
>     =20
>      Smaller....OK. Point?
>     =20
>      Cheaper....OK. How much?
>     =20
>      Faster(etc)OK. So can/is Modbus Plus (1.5MB/s).. but that got =
canxed.
>     =20
>      Many manufacturers are now moving away from the RS232 and RS485
> serial=20
>      links as standard features, and you have to buy a additional =
comm
> card=20
>      to handle this.  There went your price reduction, you just had =
to=20
>      spend the money somewhere else.
>     =20
>      I understand that the new FBM is better than the old
> integrator(that's=20
>      fine and good).. but you can only use it with CP60's which kills =
it's
>=20
>      usefulness. (Saying I have CP40B's and need to integrate =
Modbus.) Now
>=20
>      one has to buy a CP60???? No price break there.
>     =20
>      To the point... What is and has been needed for some time now is =
a=20
>      "Integrator" or FBM that works with ANY AND ALL CP combinations =
that=20
>      talks Modbus over TCP/IP!!!
>     =20
>      Regards,
>     =20
>      ______________________________ Reply Separator=20
>      _________________________________
>      Subject: [foxboro] Modbus FBM, was "Back to forcing an ABSCAN to =
writ
>      Author:  <foxboro@xxxxxxxxxxxxx> at INTERNET-MAIL
>      Date:    12/11/02 11:44 AM
>     =20
>     =20
>     =20
>      Hi,
>     =20
>      > I thought one of the new Modbus FBM's was Modbus/TCPIP..=3D20 =
> which
>=20
>      is still "serial" but at a greater throughput?=3D20
>     =20
> No, it supports serial links (RS232 and RS485) with up to 115kBit/s =
as =3D=20
> far
> as I know.
>     =20
> > If not.. the ONLY advantage would be the flexability of=3D20=20
> > locations that the device could be installed,=3D20
>     =20
> No, it's much smaller than an integrator 30, cheaper, faster and =3D=20
> supports
> direct transmission of floating point values in a 4-Byte format =3D=20
> (compatible
> to the Triconex Modbus implementation), so that no conversion loss=20
> (float-integer-float) is existing anymore.
>     =20
> That's cool. ;-)
>     =20
> Best regards -
>     =20
> Marcel Sieling
> Systems Technologies
>     =20
> Invensys Systems GmbH
> Heerdter Lohweg 53 - 55
> 40549 Duesseldorf
> Germany
> Tel.:  +49 (0)30-267-15542
> Tel.:  +49 (0)211 5966-171
> Fax:  +49-(0)172-50-2673077
> Mobile:  +49-(0)172-2673077
> Email: <mailto:msieling@xxxxxxxxxxx>=3D20=20
> Homepage: <http://www.foxboro-deutschland.de>=3D20
> Visit my private (german) homepage: <http://www.powerslider.de>=3D20
>     =20
>     =20
>     =20
> > -----Urspr=3DFCngliche Nachricht-----
> > Von: Daren Bishop [mailto:dbisho@xxxxxxxxxxxx]=20
> > Gesendet: Dienstag, 10. Dezember 2002 19:30
> > An: foxboro@xxxxxxxxxxxxx
> > Betreff: [foxboro] Re[2]: Back to forcing an ABSCAN to write, =
etc=3D20=20
> >=3D20
> >=3D20
> >=3D20
> >      Alex,
> >     =3D20
> > I thought one of the new Modbus FBM's was Modbus/TCPIP..=3D20=20
> > which is still "serial"
> > but at a greater throughput?=3D20
> >=3D20
> > If not.. the ONLY advantage would be the flexability of=3D20=20
> > locations that the=3D20
> > device could be installed, and all we have is the old=3D20=20
> > "Mountain and Mohammed"=3D20
> > scnenario! In other words.. if you don't move forward, it's a=3D20=20
> > waste of time and=3D20
> > money. Just another device that doesn't improve performance.=20
> >=3D20
> > Hopefully for David's sake the AB Integrator FBM will be=3D20=20
> > ethernet or DH+ direct.
> >=3D20
> >=3D20
> >=3D20
> > ______________________________ Reply Separator=3D20=20
> > _________________________________
> > Subject: Re: [foxboro] Back to forcing an ABSCAN to write, etc=3D20 =

> > Author:  <foxboro@xxxxxxxxxxxxx> at INTERNET-MAIL
> > Date:    12/10/02 1:00 PM
> >=3D20
> >=3D20
> >     =3D20
> > Well, there's a Modbus FBM coming shortly for CP-60s under=3D20=20
> > V6.5. Still it is=3D20
> > only serial and only Modbus.
> >     =3D20
> >     =3D20
> > FBMs for other PLCs and physical layers are in the mill, but ...=20
> >     =3D20
> >     =3D20
> > Regards,
> >     =3D20
> > Alex Johnson
> > Invensys
> > 10707 Haddington
> > Houston, TX 77063
> > 713.722.2859 (office)
> > 713.722.2700 (switchboard)
> > 713.932.0222 (fax)
> > ajohnson@xxxxxxxxxxx <mailto:ajohnson@xxxxxxxxxxx>=3D20=20
> > For the latest information on ArchestrA, go to=3D20
> > www.invensys.com/Archestra.html
> > <http://www.invensys.com/divisions/Archestra.html> .=20
> >     =3D20
> >     =3D20
> >         -----Original Message-----
> >         From:        David Johnson [SMTP:DRJohn@xxxxxxxxxx]=3D20=20
> >         Sent:        Tuesday, December 10, 2002 11:43 AM=3D20
> >         To:        foxboro@xxxxxxxxxxxxx
> >         Subject:        [foxboro] Back to forcing an ABSCAN=3D20=20
> > to write, etc
> >     =3D20
> >     =3D20
> >     =3D20
> >     =3D20
> >     =3D20
> >         If there is not a way to force a write of the data=3D20=20
> > table in event
> > driven=3D20
> >         mode, there should be!
> >     =3D20
> >         I can save a tremendous amount of my serial bandwidth=3D20=20
> > between I/A
> > and the=3D20
> >         KF2 if I only write values to the PLC when they=3D20=20
> > change.  I may have
> > a set=3D20
> >         of timer values that change once a week or less.  The=3D20=20
> > longest period
> > listed=3D20
> >         in the book is 1024 seconds.  That would be OK in a=3D20=20
> > polled situation
> > except=3D20
> >         if the operator changes a setpoint from an I/A screen=3D20=20
> > it might take
> > more=3D20
> >         than 16 minutes for the change to be reflected in the=3D20=20
> > system.  Not
> > good.
> >     =3D20
> >         So we go look at event driven mode.  Values are=3D20=20
> > written to the PLC
> > only if=3D20
> >         a change is made to the input side of the data.  Changes =
are=20
> > transferred to=3D20
> >         the PLC at the time that the operator makes the=3D20=20
> > changes.  Very good.
> > BUT,=3D20
> >         suppose the PLC reboots, or fails in some other way=3D20=20
> > that changes our
> >     =3D20
> >         values.  Unless we change the input side of the=3D20=20
> > block, no write will
> >     =3D20
> >         occur.  So what we want to do is check a heartbeat=3D20=20
> > signal and when=3D20
> >         communication resumes after any absence force a write=3D20=20
> > of all the
> > data in=3D20
> >         the event driven tables.  Then everything will be=3D20=20
> > synced up.  I
> > can't find=3D20
> >         a mechanism to do this.
> >     =3D20
> >         I suppose one could code a method that would=3D20=20
> >         a)read the PLC outputs back to I/A
> >         b) compare these to the values of the inputs that we think =
=3D=20
> I/A
> > should write
> >         c) if there is a difference
> >             1) change the input value (to what is in the PLC,=3D20=20
> > to be most
> > bumpless)
> >             2) change the value back to the correct value=20
> >     =3D20
> >         This seems to be way too much work for a problem this =
simple.=20
> >     =3D20
> >         Assuming there is not a good way to force a write, what are =
=3D=20
> my
> > options?
> >     =3D20
> >         RANT MODE ON
> >         I HATE serial communications to PLCs! PLEASE get an=3D20=20
> > FBM or CP based=3D20
> >         ethernet solution out soon!  And yes I know about=3D20=20
> > integrator 50s and
> > 70s,=3D20
> >         and yes Alex, I saw some promising things in Orlando,=3D20=20
> > but I NEED an
> > AB=3D20
> >         integrator FBM NOW!
> >         RANT MODE OFF
> >     =3D20
> >         Thanks,
> >     =3D20
> >         David
> >     =3D20
> >     =3D20
> >     =3D20
> >     =3D20
> >     =3D20
> >     =3D20
> >     =3D20
> >     =3D20
> > ______________________________________________________________=20
> > _________
> >         This mailing list is neither sponsored nor endorsed=3D20=20
> > by Invensys
> > Process
> >         Systems (formerly The Foxboro Company). Use the info=3D20=20
> > you obtain here
> > at
> >         your own risks. Read
> > http://www.thecassandraproject.org/disclaimer.html=20
> >     =3D20
> >         foxboro mailing list:
> > http://www.freelists.org/list/foxboro=20
> >         to subscribe:
> > mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin=20
> >         to unsubscribe:
> > mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave=20
> >     =3D20
> >     =3D20
> >     =3D20
> > ______________________________________________________________=20
> > _________=3D20
> > This mailing list is neither sponsored nor endorsed by=3D20=20
> > Invensys Process=3D20
> > Systems (formerly The Foxboro Company). Use the info you=3D20=20
> > obtain here at=3D20
> > your own risks. Read=3D20
> > http://www.thecassandraproject.org/disclaimer.html=20
> >     =3D20
> > foxboro mailing list:            =3D20=20
> http://www.freelists.org/list/foxboro=3D20=20
> to subscribe:         =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin=3D20=20
> to unsubscribe:      =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
>     =3D20
>     =3D20
>     =20
> =3D20
> =3D20
> =
_______________________________________________________________________ =

> This mailing list is neither sponsored nor endorsed by Invensys =
Process=20
> Systems (formerly The Foxboro Company). Use the info you obtain here =
at=20
> your own risks. Read =
http://www.thecassandraproject.org/disclaimer.html=20
> =3D20
> foxboro mailing list:             =
http://www.freelists.org/list/foxboro=20
> to subscribe:         =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin=20
> to unsubscribe:      =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave=20
> =3D20
>     =20
>     =20
> =
_______________________________________________________________________ =

> This mailing list is neither sponsored nor endorsed by Invensys =
Process=20
> Systems (formerly The Foxboro Company). Use the info you obtain here =
at=20
> your own risks. Read =
http://www.thecassandraproject.org/disclaimer.html
>     =20
> foxboro mailing list:             =
http://www.freelists.org/list/foxboro=20
> to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin=20
> to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>     =20
>     =20
>=20
> =20
> =20
> =
_______________________________________________________________________
> 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
> =20
> foxboro mailing list:             =
http://www.freelists.org/list/foxboro
> to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
 
 
_______________________________________________________________________
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: