pickerel
Member
I'm having an issue communicating between an AB CompactLogix DeviceNet Scanner module and custom slave devices over DeviceNet.
The issue is whenever I first boot up the system (plc, hmi, scanner) or when the system has been idle for some time (slave devices powered down), the scanner and the first slave that I power up fail to communicate with each other.
Basically in our product's application (new product), all the slave devices remain powered off until they are required to be on.
Using RSNetWorx for DeviceNet, I commissioned the scanner with a node address of 00 and configured its scanlist with all slave devices (nodes 11,12,13,14,21,22,23,24,31,32) in my network and downloaded the configuration to the scanner. I'm using RSNetWorx version 5.00.00 (build 81) and scanner's firmware version is 2.2. The compactlogix processor I have is a 1769-L35E with firmware version 13.21.
In my PLC applications logic I have an unconditional rung that sets the scanner's command register's run bit.
When I first boot up the system, the devicenet scanner reports an error code of 79 (transmit failure). This sounds about right since all the slave devices (10 in total) are powered down.
When I request only one slave to be on and apply mains power to the device, the scanner reports the following error codes: first 79 (mentioned above), then 76 for node 00, 76 for node 00, 76 for node 00, then 78 for each slave node, and 75 for node 00. At this point the scanner continues to scroll through the 78 for each slave followed by 75 for node 00. For some reason the scanner and slave device fail to establish communications with each other and I don't know why. The communication issue persists until I power the slave device done and then re-apply power to it, at this time communications is established.
Interesting thing is if I then power up another slave device while the communication problem is active with the first, communications is not only established between the scanner and the second device but also between the scanner and the first device.
I have reviewed the DeviceNet cable and system planning documents from AB and check the cabling installed in my system and every looks ok to me.
The total trunk line from scanner is only about 3 meters in length. Termination resistors are installed at both ends, measured 60.3 ohms across the Can_H and Can_L at the scanner. I have a dedicated 24VDC power supply for the devicenet network. The trunkline cable's shield and drain are only connected to earth at one end, the scanner end. V-from the power supply is also connect to earth at this point.
Thanks for your help in advance.
The issue is whenever I first boot up the system (plc, hmi, scanner) or when the system has been idle for some time (slave devices powered down), the scanner and the first slave that I power up fail to communicate with each other.
Basically in our product's application (new product), all the slave devices remain powered off until they are required to be on.
Using RSNetWorx for DeviceNet, I commissioned the scanner with a node address of 00 and configured its scanlist with all slave devices (nodes 11,12,13,14,21,22,23,24,31,32) in my network and downloaded the configuration to the scanner. I'm using RSNetWorx version 5.00.00 (build 81) and scanner's firmware version is 2.2. The compactlogix processor I have is a 1769-L35E with firmware version 13.21.
In my PLC applications logic I have an unconditional rung that sets the scanner's command register's run bit.
When I first boot up the system, the devicenet scanner reports an error code of 79 (transmit failure). This sounds about right since all the slave devices (10 in total) are powered down.
When I request only one slave to be on and apply mains power to the device, the scanner reports the following error codes: first 79 (mentioned above), then 76 for node 00, 76 for node 00, 76 for node 00, then 78 for each slave node, and 75 for node 00. At this point the scanner continues to scroll through the 78 for each slave followed by 75 for node 00. For some reason the scanner and slave device fail to establish communications with each other and I don't know why. The communication issue persists until I power the slave device done and then re-apply power to it, at this time communications is established.
Interesting thing is if I then power up another slave device while the communication problem is active with the first, communications is not only established between the scanner and the second device but also between the scanner and the first device.
I have reviewed the DeviceNet cable and system planning documents from AB and check the cabling installed in my system and every looks ok to me.
The total trunk line from scanner is only about 3 meters in length. Termination resistors are installed at both ends, measured 60.3 ohms across the Can_H and Can_L at the scanner. I have a dedicated 24VDC power supply for the devicenet network. The trunkline cable's shield and drain are only connected to earth at one end, the scanner end. V-from the power supply is also connect to earth at this point.
Thanks for your help in advance.