AB over Ethernet

J

Thread Starter

Jack Gallagher

In order to write software for the AB over Ethernet, you have to purchase the SDK for RSLynx. I think this is the only way to do this type of
communication.

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On
> Behalf Of Lynn Linse
>
> Send me details of Allen-Bradley protocols under Ethernet & I'll
> happily do
> some AB/TCP work for you. I have lots of bits & pieces begged and borrowed
> from various sources. But AB is both disorganized (ie too many DIFFERENT
> protocols) & very hush-hush on how they really work with Ethernet.
>
> The only exception is for the ControlNet CIP, which only has value if you
> have ControlNet application layer's already written.
>
> > -----Original Message-----
> > From: Stan Brown [mailto:[email protected]]
> > Sent: Friday, January 07, 2000 1:42 PM
> >
> > First the minor one. I'm not thrilled with your I/O
> > choices, as someone
> > pointed out lot's of us have millions of dollars of
> > existing I/O that
> > we are very happy with. In our case A/B

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
L
Which means - I think - the SDK just uses DDE or another Win9X/NT mechanism to talk to the Win9x/NT RSLinx application. That's how Wonderware's ABCIP driver works at least. If someone was really desperate for AB connectivity,
we could always use DF1 encapsulated in TCP from the Linux/PLC to some VB application running on a second Win9X/NT computer to act as a gateway thru
DDE to RSLinx!

regards
- Lynn Linse


_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo
 
L
> Take a look at the traffic from/to port 2222, I think you will find it interesting.<

I have, but since my only host is a SLC5/05, the traffic is rather uninspired (see below). I assume it starts with some form of "negotiation"
which I don't know how to reply to, so the connection is reset and I get no further. I've been told the 2222 port is mainly PCCC (DF1 commands) encapsulated in TCP. (I've also been told by the RA network folk that the official scheme is to force all older Ethernet products to firmware upgrade to the single standard up on port 0xAF12 used by ControlNet and ControlLogix to unify on one interoperable protocol - now can they swing that 'forced migration' or not ... ?)

Below are the dumps I did (almost a year ago) from the SLC5/05 when a MSG block is set up to try a write to a remote. I'd be pleased if you can enlighten me as to how to by-pass this first step. Reply in private if you prefer.

Regards
- Lynn

When remote is config as "SLC500"
01 01 00 00 00 00 00 00 00 00 00 00 00 04 00 28 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

When remote is config as "485IF"
01 01 00 00 00 00 00 00 00 00 00 00 00 04 00 28 00 00 00 00 00 00 00 00 00
00 00 00 00 20 4A 92 D4 DA 00 A0 24 A5 9A 43 08 00 45 14 00 28 62 07 40 00
80 06 17 46 C0 A8 00 02 C0 A8 00 1C 04 0A 0B B9 00 58 E5 A1 00 00 90 34 50
10 16 9D 91 D7 00 00 00 00 00 00 00 00 00 00 40 00 00 20 4A 92 D4 DA 00 A0
24 A5 9A 43 08 00 45 14 00 28 63 07 40 00 80 06 16 46 C0 A8 00 02 C0 A8 00
1C 04 0A 0B B9 00 58 E5 A1 00 00 90 35 50 10 16 9C 91 D7 00 00 00 00 00 00
00 00 00 00 40 00 00 20 4A 92 D4 DA 00 A0 24

When remote is config as "PLC5"
01 01 00 00 00 00 00 00 00 00 00 00 00 04 00 28 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


Best Regards;

Lynn August Linse, [email protected].org http://www.linse.org/lynn
258 Santa Barbara, Irvine CA 92606
Ph: 949-387-4830 Fx: 612-677-3253

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
J

Jack Gallagher

I have dealt with this problem in the past. Basically the problem was that we wanted our application to talk directly to an Ethernet SLC 5/05. What it finally came down to was that to make this work we had to purchase both the
RSLinx OEM driver package and the RSLinx C SDK to connect our application to the processor. The other option was to connect directly to their socket interface and try to figure out the UNPUBLISHED protocol that was embedded in the packets. I am unsure if it is just DF1 or some other protocol. These answers came directly from one of the software engineers involved in
the RSLinx development.


_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
Top