Re: [foxboro] FDSI driver AB CSP or FDSI Driver Ethernet/IP
- From: "Boulay, Russ" <Russ.Boulay@xxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 30 Sep 2010 00:01:08 -0400
I don't know much about the subject ,..but does this FAQ confirm or help your
situation?
In a migration project from an MG30 to an FDSI, how can I connect a legacy MCIN
to a DCI PAKIN block?
March 26, 2010
Question
In a migration project from an MG30 to an FDSI, how can I connect a legacy MCIN
to a DCI PAKIN block?
Answer
For this migration, a customer is using an FDSI Modbus driver hosted by a
CP270. The existing MG30 database must be modified because the existing I/O
blocks must have a layer of DCI blocks between them and the FBM to pass data to
and from the driver. The existing legacy I/O blocks must have their IOM_ID set
to "blank" and their IOMOPT set to 0. In addition, the Input blocks, such as
AIN, MCIN and CIN, would require their inputs to be connected to the outputs of
their respective DCI blocks.
Here is an example of an MCIN/PAKIN block and the parameters that are needed to
be changed:
PAKIN Configuration:
IOM_ID= ECB201_LetterBug
PNT_NO = 40,001 (Reading address 40,001 of Holding registers)
MCIN Changes:
IOMOPT = 0;
IOM_ID = blank;
INPUTS = Cmpnd:PAKIN.PAKCIN
Supporting Information
B0193AX - X
MCIN Parameters:
IOMOPT - FBM Option is a short integer specifying the type of input connection
to the block and the order of the bits in parameter PACKIN:
0 = The MCIN block obtains input values from either the INPUTS parameter if it
is linked, or the parameters II01 and II02 if not.
1 = The block obtains its input values from the FBM, FBC or Integrator
specified by IOM_ID.
For Modbus Integrators, the 32 discrete points read by the block are mapped to
the block inputs in the order they are received; the lowest numbered bit is
stored in CIN_1 and the highest numbered bit is stored CIN_32.
Storage in the PAKCIN parameter is a byte-wise mapping with the high order
(leftmost) bit numbered 1:
CIN_1 to CIN_8 values are stored in PAKCIN bits 8 to 1,
CIN_9 to CIN_16 values are stored in PAKCIN bits 16 to 9,
CIN_17 to CIN_24 values are stored in PAKCIN bits 24 to 17,
CIN_25 to CIN_32 values are stored in PAKCIN bits 32 to 25.
2 = The block obtains its input from the Modbus Integrator specified by IOM_ID.
The 16 discrete points read by the block are mapped to the block inputs in the
order they are received; the lowest numbered bit is stored in CIN_1 and the
highest numbered bit is stored CIN_16.
The block stores the 16 CIN values in parameter PAKCIN in reverse order with
the high order (leftmost) bit numbered 16:
CIN_1 to CIN_16 are stored in PAKCIN bits 16 to 1.
IOM_ID: Fieldbus Module Identifier is a configurable string that specifies the
pathname of the ECB for the FBM or FBC to which the block is connected.
INPUTS: Inputs is a packed long integer which contains the block's input values
when there is no connected FBM or FBC, and INPUTS is linked. When there is a
connected FBM or FBC, INPUTS contains the same value as
PAKCIN, except that bypassing is not honored.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Tadeo Armenta
Sent: Wednesday, September 29, 2010 11:42 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FDSI driver AB CSP or FDSI Driver Ethernet/IP
Hi, its me again!
Bought the CSP driver and the connection is fool-proof... BUT!!!!
Now, Im in a weird dream. all my existing digital inputs, that belonged to a
MCIN block, have to be connected now to a PAKIN and then to an MCIN. Thats not
so weird for now... but in the second level of the dream, I find out that, all
the PAKIN bring the data backwards... but not a good backwards, like I set a
"3"
in de Pkopt parameter... nooooo, cause that 3 backflips the 32 bit and what i
need is something that flips the first 16 bits, and then flips the second 16
bits... sigh!... but then i fall into a 3rd stage of dreaming and discover I
had
some MCINs pointing to PLC address I:XXX ans O:XXX and voila! PAKIN cant read
this addresses... so I have to use IINs, actually for each MCIN I had before, I
have an array of 2 IIN to a MCIN that goes to 2 MCOUTs and finish in the
original MCIN alll that to rearange the bits the way it was before. Shall I
note
that all the animations and alarms depend on this MCIN receiving the data the
way it did before.
So... I need to fill my CPs with a lot of cr*p... just to get the data the way
I
did before or go to the freaking limbo and chevk all the connections and change
them, displays, etc, etc... just in time for the plant commisioning and startup
kicks...
Please, someone tell me that this is a freaking inception, and Im filling my
head with this crazy ideas and the solution is waaay easier than I am
describing
here...
Hope you enjoyed the inception metaphore
And really hope you have a good answer jejeje
Best regards!
________________________________
De: The Automation Man <automationman@xxxxxxxxxxxxx>
Para: foxboro@xxxxxxxxxxxxx
Enviado: dom, agosto 1, 2010 5:55:15 PM
Asunto: Re: [foxboro] FDSI driver AB CSP or FDSI Driver Ethernet/IP
Tadeo,
I believe there was a thread in the list a few month back about this
subject, but I think the discussion was slightly misleading. You are
correct, you will need to change to the CSP driver for PLC5. That is the
only thing you should need different from using the Ethernet/IP driver. The
hardware is the same.
Rockwell added the capability of "explicit" messaging using Ethernet/IP
communication to ControlLogix on PLC5/E (Ser./Rev.) C/N, D/E, & E/D or later
processors in 1999. The exception here is that it uses Ethernet/IP with
encapsulated PCCC (DH+) commands to access Tag data that has been mapped to
"compatibility files" as opposed to CIP used with direct, symbolic
addressing of Tag data in "native" mode. The AB Ethernet/IP driver for FDSI
accesses data in ControlLogix native mode. The AB CSP driver access data in
PLC5 and SLC using CSP/PCCC over Ethernet.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Tadeo Armenta
Sent: Thursday, July 29, 2010 10:14 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FDSI driver AB CSP or FDSI Driver Ethernet/IP
Hi list,
I was planning on using FDSI Driver Ethernet/IP to communicate with Allen
Bradley PLC5 with a 1785ENET card.
After some reading i realized FDSI Driver Ethernet/IP does not work for
PLC5,
only Control Logix, so aparently I have to stick with FDSI driver AB CSP
that
uses CSP protocol over Ethernet.
2 Questions,
Do I have to change to CSP driver for PLC5?
Do I have to buy anything different (driver/hardware) for the PLC5 for a CSP
communication with it?
Thanks in advance,
Regards
_______________________________________________________________________
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
*** 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 email comes from a division of the Invensys
Group, owned by Invensys plc, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.
You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
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:
