RemoteConnect Oject Database / Logic Editor inconsistencies mus be resolved before writing to the SCADAPack x70

[AlbertoArdila]

Hi,

I have the message: “Object Database / Logic Editor inconsistencies must be resolved before writing to the SCADAPack” when I try to write my program from RemoteConnect to a RTU 474.

When I build the program, the Process succeeded: 0 Error(s), 0 Warning(s)

I don’t see any error in the Object browser.

Is there someone that can tell me how I can solve this problem?

Thank you

[BevanWeiss]

My recollection is that there is something under the Advanced options in RemoteConnect to essentially force a resynchronisation of the Object Database with the Logic Editor.

You definitely want to have a backup of your project before doing this of course, since otherwise it could break everything..

I haven't seen your exact issue before however, but I have seen mismatches that had to be resolved through the full push from Object Database -> Logic Editor.  and these generally did break some of hte Logic Editor linkages (since variables did get deleted / renamed outside)

[AlbertoArdila · Accepted solution]

Hi BevanWeiss.  Thanks for the answer

This error was that I created some objects in RemoteConnect and after those objects was loss but SCADAPack X70 Logic was unable to detect those missing object whit the Rebuild.

I tried update & Build Logit, Unlock Variable and Replace Variables but didn’t work.

My solution:

I exported the configuration from RemoteConnect, additional functions, export to Excel File, and then imported it from Excel to RemoteConnect, additional functions, Import from Excel File. After that, SCADAPack x70 Logic showed me lost objects.

At the end I needed to write all the Objects lost (+- 20).

[BevanWeiss]

Hopefully you still have the RemoteConnect project from when it had issues.

You should sent this to your local Schneider Tech Support.  They should investigate and ideally fix the issue within the RemoteConnect environment that caused the problem.

If Schneider don't know about, and have an example bad file to work with, then they can't fix the issue, and it's likely to happen again for others (or you when you've forgotten how you fixed it this time).