Oh Ken...the plot thickens...
Rob S said:
I have a faulted DeviceNet Scanner module....flashing 20,21,22,23,24 & 78.
Why didn't you say so?
I would recommend you put back in the first 1747-SDN module. There is a good chance that it is not at fault here, at all. I would then set about figuring out what devices are actually configured on this scanner's scanlist and what devices are actually assigned to the node addresses 20 through 24.
If it is continuously displaying...
78 - 20 - 78 - 21 - 78 - 22 - 78 - 23 - 78 - 24
...then this scanner has at a minimum these 5 non communicating devices added to its scanlist. I cannot see how it suddenly just started trying to communicate with more node addresses than you reckon it's scanlist should have?
If you are positive that their is physically only the two PowerFlex drives wired to this scanner's network, then hmm???....
Unless they made more swaps than you think?
Perhaps they had swapped out the original SDN module, that was displaying "some" error(s), with some other, already used, module that had a scanlist configured with the node addresses above. This would explain the module trying to communicate with more nodes than the expected two?
Then, when that did not work, they swapped out again for another, out-of-the-box new module, which subsequently displayed error 75 - 63, which as Ken points out would be the expected error for a new and unconfigured scanner module.
That's just an "out there" theory on why you're seeing what you expect not to see. But what are you basing your assessment of their being only the two PowerFlex drives on that one specific scanner?
You originally mentioned that this chassis has two DeviceNet scanner modules. I would figure out first the physical layout of both DeviceNet networks and which devices are on which scanner's network.
If you have them, are you looking at offline configuration files for these networks in RSNetWorx for DeviceNet?
If so, how many nodes are shown between the two networks and what are the devices and their addresses?
Do the node addresses 20 through 24 show up anywhere?
You might be past some or all of this fault finding by now, but if you are still struggling, then updating us with this info will greatly help us understand what might be going on here.
EDIT: On the swapping...
Because it was thought that the modules could simply be swapped out plug-and-play style, it may also be possible that they swapped the two scanner modules around in this same chassis? The module displaying the 20-24 errors "could" belong to the "other" network?
Worth considering, I feel?
Regards,
George