Re: [foxboro] FDSI driver AB CSP or FDSI Driver Ethernet/IP
- From: Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 30 Sep 2010 13:32:19 +0900
Russ,
Migrating an MG30 is quite a bit different than migrating an AB30. The KB
example doesn't really apply.
Tadeo,
You are correct in your description of some of the problems. Have you read
the migration guide, "Allen Bradley® Integrator 30 to FDSI Migration",
DI700BS?
Regarding your problem with the bit ordering, one possibility we looked at
was using each PAKIN to read one word instead of two using the /U2 suffix.
Then you can reverse the bit order in each word.
At my plant we decided that it was easier in most cases to add a ModbusTCP
module to each Rack0 and use the ModbusTCP FDSI driver than to use the CSP
driver (for a number of reasons), so that is the direction we're heading
now. This still requires inverting bit order.
Regards,
Kevin FitzGerrell
On Thu, Sep 30, 2010 at 1:01 PM, Boulay, Russ <Russ.Boulay@xxxxxxxxxxxx>wrote:
> I don't know much about the subject ,..but does this FAQ confirm or help
> your situation?
>
> -----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!
>
>
_______________________________________________________________________
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:
