1756-DHRIO Active Nodes

I'm porting a PLC5-V80 program to CLX 1756-L63 (due to obsolescence issue) but am stuck with how to emulate S:3-S:6 (Active Nodes) registers.

I tried searching the RA Knowledgebase but almost all of the Tech Notes are locked and we haven't yet finalized budgeting for the needed Tech Support contract.

Can anybody share their code fragments to check the active nodes attached to the DHRIO? Thanks in advance.

Do a generic CIP message to the slot that the DHRIO is in:
Service Type: Get attribute single
Service Code: E
Instance: 1 (DHRIO channel A) or 2 (B)
Class: a5
Attribute 8

Destination needs to be a SINT[9]
[0] - number of active nodes
[1].0 - [1].7 represents nodes 0 - 7
[2].0 - [2].7 nodes 10 - 17
~
[8].0 - [8].7 nodes 70 - 77

AnswerID 24538

BTW, Answer ID 24538 is an index to all of the CIP type msg's. It's awsome what you can do with the CIP msg.

Steve,

Thanks for the reply. I will try it out as soon as I can setup a test rig.

Do you happen to have a copy of the Answer ID 24538?

*** The CIP MSG needs a Source Element; what should it be?

I tested it and it works, leave the source blank. Sorry, but the Answer ID 24538 is just a bunch of links to other Answer ID's.

Working:

Here's a list of topics in 24538. If your interested in, I'm sure people here will help you out:

DH+ / RIO
DH+ Diagnostics 18310
DHRIO remote rack retry counters 20185
DHRIO DH+ node address 17743
DHRIO DH+ active node table 17690
DHRIO rio status object 17747
Getting and Clearing Diagnostic Counters 29909

ControlNet
Flex Module Info 19092
Node Number 19053
CPU Utilization 18645
LED Status 18423
CNB node address 25592
Cnet diagnostic and cable redundancy status 16584
Cip messages to 1747SCNR 19612
Resetting PLC5 diags counters on ControlNet 21834
Resetting ControlNet Diagnostic Counters 41650
Serial Number (all modules) 52870
Module Reset to Factory Defaults (all Modules) 55362

1756-DH485
Active DH485 Nodes 60810

EtherNet
ENET IP Information 18606
ENET diagnostic counters 18181
ENBT Diagnostic Counters 22421
ENBT Media Counters 31234
ENBT Baud and Duplex 21751
ENBT Forcing Baud and Duplex 24540
ENBT CPU utilization 26893
ENBT IP Information 26779
ENBT Host Name 31238
ENBT Change to Static, BOOTP or DHCP 55369
EN2T version 2 CPU 62758
Serial Number (all modules) 52870
Module Reset to Factory Defaults (all Modules) 53362

DeviceNet
DNB explicit message example 16568
DNB Explicit message to Panelview example 17384

Processor
Firmware Level 23386
Serial Number (all modules) 52870
Program Edits 23378
Program Download 23376
Program Name 23341
Date and Time 20055
Mode Change (Run / Program) 19395
Change the periodic task execution interval 19591
Clear controller faults (major) 19971
Retrieve controller free memory 19706
Get controller run/prog mode status 21989
CPU backplane counters 20156
Change or increase the CPU's unconnected buffers 21192
Obtaining the controller FW level 20938
Change the serial port from user to system 20247
Logix unconnected Buffer 19993
OK LED status, Keyswitch position 26924
Changing the Serial Port Control Line Programmatically 27150
Obtaining the keyswitch position 28917

I/O Modules
1794VHSC CIP messages 20318
Flex with LGX, Cnet and no profiles before 11.xx 20057
Resetting diagnostic latch bits 25103
Resetting electronic fusing 19639
Obtaining Calibration Data (1756-IR6I/IT6I) 27136
Obtaining Calibration Data (1756-IF16) 25620

SERCOS Modules
Current Ring Phase 26687

Steve,

Tried the CIP message as detailed in your posts but I'm getting Error Code 16#0013, Configuration Data too short when the "Connected" check box is off in the Communication Tab of the Message Configuration screen.

If "Connected" is enabled, no error but I'm not getting any data in the destination SINT tags.

The nodes are active since I can see them connected to the DHRIO module via RSLinx.

Is there any other setup I should do? Thanks.

Is your destination an array of 9 SINT's? Does the destination specify Destination_SINT[0]? Is your path set up correctly?

Steve,

Thanks for taking the time to answer my queries. The fault cleared by itself and I'm able to get the active nodes. What I did was just to access the Routing Table tab in the RSLinx module configuration screen (right clicked on the DHRIO module) which initiated a rescan. Not sure if this was really what cleared the error. Thanks again for the help.