Start a topic
With the exception of Windchill, The PTC Community is on read-only status until April 6 in preparation for moving our community to a new platform. Learn more here
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

ThingWorx Navigate is now Windchill Navigate Learn More

Translate the entire conversation x

Communicating to a AB PLC5/250 Pyramid Integrate

DF_14499676
3-Newcomer

Communicating to a AB PLC5/250 Pyramid Integrate

We need to pull data out of an old 5/250 but Kepware is preventing us from entering the address as they need to be.  the PLC5 architecture is "N7:40" for example but in the PLC5/250 it requires a leading digit to identify which module the address is in so "N7:40" in a 5/250 would be "0N7:40". 

 

Has anyone had any experience with this?

 

THank you,

Dean

ACCEPTED SOLUTION

Accepted Solutions
MKhatri
15-Moonstone
(To:DF_14499676)

Greetings!!

A simple way to handle PLC‑5/250 addressing in Kepware is to remember that each data table must include its module prefix, so instead of using N7:40,
you must enter it with the required slot identifier like 0:N7:40, which tells Kepware which logical module the address belongs to within the 5/250 chassis.

Regards,
Mohit

View solution in original post

2 REPLIES 2

I address them as N7:4 etc. I don't need a leading digit.

Are you using 'Allen Bradley Ethernet' as the driver?

MKhatri
15-Moonstone
(To:DF_14499676)

Greetings!!

A simple way to handle PLC‑5/250 addressing in Kepware is to remember that each data table must include its module prefix, so instead of using N7:40,
you must enter it with the required slot identifier like 0:N7:40, which tells Kepware which logical module the address belongs to within the 5/250 chassis.

Regards,
Mohit

Announcements


Top Tags