• Replies 16 replies
  • Subscribers 586 subscribers
  • Views 635 views
  • Users 0 members are here
Options
Related

Errors migrating project from CitectSCADA 7.10r0.28 to PlantSCADA 2023 (update 06)

Tiago Angelo

Good evening, I'm a new user of the PlantSCADA/CitectSCADA and I have been tasked with migrating and merging two existing SCADA systems, both made on the same older Citect version 7.10r0.258.

One of them the migration was done sucessfully and I have started to make changes to it and so far it works fine in the simulator (I have not tested the communication with a PLC yet, will do so this week).

The other project is giving me an error that seems to be like an internal exception of the PlantSCADA since the text is very generic and in my OS language even though I have installed PlantSCADA in english.

I can attach the .ctz files if such is allowed..

The error that I get is the following:

The text in the message box translates more or less to: "Invalid chain of characters"/ "Invalid character chain"

This text box appears dozens of times while doing the project import, specifically when this action is being executed:

It reaches around 4000 tags analyzed, throws the error in the PlantSCADA main window and starts again, I can abort it, and I can run the imported SCADA in simulation mode, but I don't even know if I'm losing tags or not, since after aborting that step no more errors are generated. This is a project with 4000-4500 tags, so validating one by one with is not a feasible option.

Any idea on why this is happening, and what can I try to fix it?

Best regards and thanks for your time.

Parents

  • It sounds like that project has one or more I/O devices that are linked to an external tag database, such as the PLC project. Every time you compile, it tries to import the external database and refresh the tag list in your project.

    Go to the I/O Device properties as shown above. Set Automatic Refresh: FALSE and compile again. The error should not appear. You still have the full list of tags in the Plant SCADA Variable Tags list from the last successful refresh. You just won't get automatic tag definition updates from changes made in the external database. If you can fix the problem in the external database, you can manually trigger a refresh by clicking Refresh Tags in the toolbar.

    If the format of the external database has changed and is no longer compatible with the Citect import filter, you may have to export the database to an Excel file and manually copy that into Citect's tag list when you need to get updates.

Reply

  • It sounds like that project has one or more I/O devices that are linked to an external tag database, such as the PLC project. Every time you compile, it tries to import the external database and refresh the tag list in your project.

    Go to the I/O Device properties as shown above. Set Automatic Refresh: FALSE and compile again. The error should not appear. You still have the full list of tags in the Plant SCADA Variable Tags list from the last successful refresh. You just won't get automatic tag definition updates from changes made in the external database. If you can fix the problem in the external database, you can manually trigger a refresh by clicking Refresh Tags in the toolbar.

    If the format of the external database has changed and is no longer compatible with the Citect import filter, you may have to export the database to an Excel file and manually copy that into Citect's tag list when you need to get updates.

Children
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.