Cherokee 96 said:
...Got in touch with RA, found out that firmware 4.015 has issues...
Geospark said:
...If there is "some" anomaly with using a 1747-SDN at firmware revision 4.015 for DeviceNet pass through...
I found this and thought I'd add it here...
49940 - Safety Alert - 1747-SDN Series A or B with firmware 4.001 and 4.015 - Outputs may turn on unexpectedly (200011004)
Access Level: Everyone
However, the firmware anomaly mentioned there is related to a mix up in I/O data within the scanner. This could result in erroneous and potentially dangerous data at the controller. I don't think that firmware anomaly would have prevented you downloading a program to the SLC 5/04 via DH+, that had only the M Files edited. Something else is going on there. But, with a potential mix up in I/O data, and only "if" this anomaly is currently present, then this could create issues if or when you get to the point of attempting DeviceNet pass through proper. Either way, it would be best advice again to flash upgrade the scanner module's firmware. On that topic...
Cherokee 96 said:
RA advised not to upgrade unless I had all the data for the drives which I didn't...
If you have not already - Now that you have a 1784-U2DN interface adapter you should be able to go online and save a copy of the scanner configuration in RSNetWorx for DeviceNet (DNT file). Once you have this you should be able to flash upgrade the scanner module's firmware and then download the scanner configuration from the offline backup DNT file.
Cherokee 96 said:
...They did recommend to download the modified program via serial port, which I haven't. Will try that and update...
My, and Rockwell's, suggestion to try the download via the serial port has also now made me consider more what exactly you are attempting here. I just want to be sure that everything will play nicely here. Remember though, now that you have the 1784-U2DN adapter, you probably don't really need a DeviceNet pass through setup. So if all this is not of interest to you then just say the word and I'll leave it there. Also, I'm usually conscious of other readers who this may help now or in the future.
If you do get DeviceNet pass through "ready to go" i.e. the M Files edited and the change downloaded into the SLC, then which port on the SLC were you considering using for DeviceNet pass through?
Either way, the following is a quick cross reference on which SLC ports support pass through to each other, in general (not just DeviceNet), and which minimum processor OS FRN is required to do so...
993071 - SLC Processor OS Firmware Passthru Capability
Access Level: Everyone
Example 1 for the SLC 5/04 - If processor = OS
400 A FRN
1
To use "DeviceNet" pass through from the Channel 0 serial port, using either DF1 Full Duplex or DH-485 to a 1747-SDN, you would require OS400 A FRN 1 minimum - OK.
To use "DeviceNet" pass through from the Channel 0 serial port, using DF1 Half Duplex to a 1747-SDN, you would require OS400 A FRN
5 minimum - NOT OK.
To use "DeviceNet" pass through from the Channel 1 DH+ port, you would require OS400 A FRN 1 minimum - OK.
Example 2 for the SLC 5/04 - If processor = OS
401 A FRN
5
To use "DeviceNet" pass through from the Channel 0 serial port, using either DF1 Full Duplex or DH-485 to a 1747-SDN, you would require OS401 A FRN 5 minimum - OK.
To use "DeviceNet" pass through from the Channel 0 serial port, using DF1 Half Duplex to a 1747-SDN, you would require OS401 A FRN 5 minimum - OK.
To use "DeviceNet" pass through from the Channel 1 DH+ port, you would require OS400 A FRN 1 minimum - OK.
The latest firmware available for the 1747-L542 = OS401 C FRN 11 (2008). It's worth you double-checking the SLC OS FRN just in case but most likely it is high enough?
This is just to point out another easily overlooked but necessary criteria to achieving such pass through communications and that there is more to it than just scanner firmware and M Files. There are also software limitations like minimum version of RSLinx Classic and also certain possible issues with the pass through driver itself. Also, which Windows OS the pass through is being attempted under, and so on.
But, one hurdle or brick wall at a time!
G.