I have two identical systems that operate independently of each other. Both are CompactLogix systems with DeviceNet networks using the 1769-SDN Series B module. I designed the systems myself and ordered hardware for both at the same time. However, only one system got built initially. That first system has been working for over six months without any issues. Last week, I completed assembling the 2nd system (identical hardware, software, wiring, panel layout etc., etc.) but could not establish comms between 1769-SDN and the DeviceNet network. In trying to troubleshoot it, I pulled the SDN card from system #1 and used it on system #2. System #2 worked like a charm. That is Until I returned that borrowed 1769-SDN back to system 1. Both cards were set up with using identical scan list (same RSnetworx .dnt file and the PLC program was identical on both systems) Digging deeper.......I came to found out that 1769-SDN card that was working without any issues had Rev 4.1 Firmware installed on it and the module I couldn’t get to work, had a newer Firmware version (rev. 4.4) installed on it. So I did what every panicking individual normally does by frantically attempting to downgrade it to 4.1. The Decision was swift. Had a delay time of ZERO.
But than half way thru the process, it timed out.
Several repeat tries......yielded the same results.
Then I Power cycled. The 1769-SDN had traveled back in time to rev 1.0
Sooooo, in order to further complicate things and to slowdown RsLinx to frequent pauses and wait times exceeding 4 times that of an TRS-80 boot-up cycle with a 5 1/4 inch floppy running Microsoft Dos 0.000001, I decided to invite my 1770-KFD to the party. Much to my surprise, it did dance well with all of my DeviceNet nodes except for one. Yes. The pompous 1769-SDN.
The Primadonna is now complaining
99 (NO. I DON"T WANT TO CALL THE FACTORY. I NEVER WANT TO CALL THE FACTORY)
Err
C1
C2
I can’t re-flash it thru the backplane. (Or, can I with a different PLC Firmware rev?)
My 1770-KFD wants nothing to do with it. (Obviously, I figured it can’t flash something it can’t talk to)
RSNetworx won’t go online with it. When drilling down thru the comms path, It sees the 1769-SDN, but SDN won’t show it’s comm port to RSnetWorx. (No [+] sign next to 1769-SDN to drill down further to activate the “OK” button on RSnetWorx)
Is there any other way to Flash this thing or is the module Toast?
Rest assured that any help that I receive in resolving this matter will directly benefit the Local Microbrewery by me donating to it.
Cheers!
But than half way thru the process, it timed out.
Several repeat tries......yielded the same results.
Then I Power cycled. The 1769-SDN had traveled back in time to rev 1.0
Sooooo, in order to further complicate things and to slowdown RsLinx to frequent pauses and wait times exceeding 4 times that of an TRS-80 boot-up cycle with a 5 1/4 inch floppy running Microsoft Dos 0.000001, I decided to invite my 1770-KFD to the party. Much to my surprise, it did dance well with all of my DeviceNet nodes except for one. Yes. The pompous 1769-SDN.
The Primadonna is now complaining
99 (NO. I DON"T WANT TO CALL THE FACTORY. I NEVER WANT TO CALL THE FACTORY)
Err
C1
C2
I can’t re-flash it thru the backplane. (Or, can I with a different PLC Firmware rev?)
My 1770-KFD wants nothing to do with it. (Obviously, I figured it can’t flash something it can’t talk to)
RSNetworx won’t go online with it. When drilling down thru the comms path, It sees the 1769-SDN, but SDN won’t show it’s comm port to RSnetWorx. (No [+] sign next to 1769-SDN to drill down further to activate the “OK” button on RSnetWorx)
Is there any other way to Flash this thing or is the module Toast?
Rest assured that any help that I receive in resolving this matter will directly benefit the Local Microbrewery by me donating to it.
Cheers!
Last edited: