Adding a Module in RSLogix500

Help! I am trying to setup a new control logix processor in RSLogix5000. I have a 1756-L61B processor but when I go to choose the processor in RSLogix the only option available is 1756-L61. I have the same problem with my DH+/RIO scanner module. The one I purchased is a 1756-DHRIO D and the only choices available in RSLogix is 1756-DHRIO B or C. When I go online with the closest matches (1756-L61B or 1756-DHRIO /C) it appears to work but every now and then it gives a communication error. I also have a little exclamation point showing on the DHRIO module and it says there is a device mismatch error. I would appreciate any ideas.

Thanks

You have a series (Edit) D of the Control Logix5561 processor this has some enhancements

see page 3 of this manual

http://literature.rockwellautomation.com/idc/groups/literature/documents/rn/1756-rn603_-en-e.pdf

As far as i know you just choose 1756-L61 Rev 13 from Logix 5000 and this should work with the processor you have....
(Although i may be corrected here!)

See this manual in particular for battery use on a series B L61

http://literature.rockwellautomation.com/idc/groups/literature/documents/ap/1756-ap014_-en-e.pdf

See this manual for DHRIO Series D

http://literature.rockwellautomation.com/idc/groups/literature/documents/rn/1756-rn569_-en-p.pdf

It states that is is fully compatible with series B & C modules and can be configured as one, however if you want to configure as a series D you need V15 of logix 5000

This is where you can download an eds file for the series D modules for Linx which may be your problem with comms

http://www.ab.com/networks/eds/cgi-bin/detail.pl?file=XX/0001000C00120600.eds

Thanks Bloke. I tried everything you said with no luck. I finally ended up powering everything down, rebooting and reloading. It seems to work fine now however I still get a minor fault. I think it may be an RSLinx issue rather than Logix.

drawson,

Are you using the DHRIO module for remote I/O? If both channels are set for DH+, then it doesn't need to be in the I/O tree. Take it out of the I/O tree, and the error goes away.

mellis,

Okay I'll try it later in the week. Thanks