Devicenet Help - Rockwell SLC 5/04

Gmitran

Member
Join Date
Aug 2023
Location
MI
Posts
4
Machine has existing DN devices that are connected to SLC 5/04. All communication is working fine now. Supplier wants to remove some DN devices from the network. Do I need to modify PLC program in order to continue communicating with those devices that are left on network? I have no idea on DN setup/programming. Network was setup years ago before my time. Thanks!
 
You have to use RSNetworx in order to remove devices from your DN network.
I would prefer to modify the PLC program in order to erase all the rungs related to the devices that were removed.
 
Last edited:
So I must remove the devices no longer on machine via RSNetworx in order to keep communicating with those devices still on machine? I prefer to not do any communication modification if I don't have to.

I have no issue w/ modifying program to remove excess program that are related to the removed devices. I'm concern with communicating with those devices left.
 
Welcome to the PLCTalk forum community !

The removal of a couple of slave I/O devices will have a negligible effect on performance; there will be a couple milliseconds of reconnection attempt traffic every few seconds. DeviceNet does not pause and retry before moving on to the next configured slave device like some protocols like Modbus do. Ordinary DeviceNet configurations have enough "interscan delay" time between polling cycles to easily accommodate that traffic.

If you want to minimize that effect on a super-tightly tuned network, or you don't want to be annoyed by the error messages on the 1747-SDN for the missing nodes, you could go online with RSNetworx for DeviceNet, upload the Scanlist, un-check the scanlist Active box for the entries for those devices (without deleting the device entries or mapping), then re-download the scanlist.

If you aren't familiar with the software, and don't have archives or descriptions, it's probably best to either hire in an integrator to do that change, or leave the scanner alone.
 
Last edited:
TY Ken.

Speed doesn’t really matter on this network. There just be couple DN nodes left (PB station and digital I/O). I will leave network As-Is and ignore the DN module error. I can go back to update network w/o removed devices down the road, I just need to re-start machine for now (other contractors are involve with this maint and don’t want to hold them up).
 
What KEN say is correct, there is a small time wasted and It´s used to look for missing devices.
Removing unused rungs or disabling them must be done for the sake of clarity.
 

Similar Topics

Hi Just wondering has anyone had anything like this happen to them? I have just split a safety cct which previously used a single safety relay...
Replies
14
Views
12,436
Hello, I have a device with 68 words input. But one block on the Devicenet Scanner is only 61 words. I am trying to map this device to 2...
Replies
3
Views
536
Hello, I am setting up for practice and I am having trouble seeing the 1771 Scanner in RsLinx as well as Rsnetworx My setup: slot 0 : PLC-5/40E...
Replies
3
Views
981
Hey everyone, I'm pretty new here, but have been working lightly with AB PLCs for a while now. I've recently hit a stumbling block that I'm hoping...
Replies
4
Views
1,356
I have a 1769 sdn scanner on one panel and a 1769 adn i/o module on another panel, this module got burned and replaced but after replacement...
Replies
10
Views
3,396
Back
Top Bottom