SCADAPack 474 Device application and logic editor: Different

[BrownH]

Hello, I am trying to load a program and do an I/O test on a a SCADAPack 474 RTU. I connected via USB-C to the RTU and wrote the program to the device with no errors. When I open the x70 logic editor and attempt to connect it does not work. It returns DIFFERENT NOCONF in the bottom status bar of the Logic Editor. The remoteconnect application seems to work fine/communicate fine with the 474 but the logic editor does not.

I have attempted to update and build logic, export/import from an excel file, and rebuild logic in the editor. 

[BrownH]

Under status tab>diagnostics>System status code: Code: 5000
The logic application could not be loaded into the device.

This is after writing the program to the RTU and trying to mode>connect within the x70 logic editor.

[BrownH]

[Joel_Weder]

I'm not sure of a solution, and most likely you should contact our Global Support team. I can make a couple of comments though:

- RemoteConnect is suggesting you check the battery. Have you enabled the backup battery? It arrives disabled to avoid discharging it when not needed. There's a little switch visible thru the side grillwork, just beside the 11...30 volt power connector. 

- The firmware is older - version 3.0.3. Once you get your issues sorted out you'll want to update that. The current RemoteConnect version is 3.3.3

- But the main issue is why you can't load the application. I can see the RTU is reporting system status code 5000. In the Operations Technical Reference the table states "To resolve a system status code 5000:

  1. Delete all files except the .prj file from the project folder.

  2. Open the prj file in RemoteConnect version 3.3.1 or newer  (again, 3.3.3 is current)

      A default logic project for the device type is automatically generated.

Beyond this I'm not sure what to suggest. If the above suggestions don't help, contact Support:

1-888-226-6876 

SupportRO@se.com

[Steven2000]

I had this exact same problem myself last week and found a work around.   I didn't have this issue until upgrading to RemoteConnect v3.3.3.  If you notice, the run light on the PLC blinks instead of staying solid with this issue. So what I believe is going on is the logic is getting corrupted.  So what I ended up doing is exporting the remoteconnect side to excel then on the logic side I exported all subroutines as an xml one at a time. 

Create a new project, import the remoteconnect excel then on the logic side import the xml files.  It now compiles and is able to push out to PLC. 

I believe the corrupt logic happens when clicking the save button on the logic side and before the logic finishes saving click save on the remoteconnect side.  I hate that the logic side has 2 save dialog windows pop up when saving, it causes confusion making me think it's done saving only to see another save dialog window pop up a few seconds later.  

I reported this to tech support who forward this problem to their engineers.