Graphics pages dosent show data

Hi,

I am making an upograde of our SCADA and migrating graphics pages from the older project to the new project. To do so I open de pages.dbf file in the old project and copy the data for the pages that I needed in the new project and pasting it to the pages.dbf file of the new one. Next I copy the files (ctf, rdb, ctg) associate with each pages.

I made an update pages in active and included projects, pack the project, compile (no incremental). For most of it, everything is working fine, but I noticed that some pages will display only graphic element such as piping, rectangle, button, but all the data will not display. I have to open the page in the graphic builder, then save it and compile again. Now I can see all data in the page, but since I have a lot of pages I would prefer not to open/save all those pages... Someone have an idea ?

Example: Pipe1 ----------- (Text displaying a value) -----------

The pipe display but value isnt.

Thanks !

  • I strongly recommend letting Citect do the hard work. A Tools -> Update Pages will open and resave every page, so you don't need to do it manually. 

    You could also look at the Graphics Builder Automation API, if something as simple as Update Pages doesn't work for your needs..

  • You didn't mention what version you're using. I believe in the PlantSCADA 2023 documentation (readme) it specifically says you can no longer move pages by just moving the ctg and running Update Pages. You could use GBA like Mark suggested, or manually open and resave each page to update the files, or open the page from the old project and choose File | Save As to properly save it into the new project.

    To automate that, you could use the Page Bulk Copy tool from the Plant SCADA Toolbox. It's simply an Excel sheet with macros that connect to the GBA interface to Open/Save As for a whole list of pages.

  • As mentioned I already made an update pages. I'm using plant scada 2020 and planning to update soon. I'll have a look at GBA !

    thanks

  • Hi Jonathan,

    Your only solution will be automation as Eric and Mark have mentioned.

    A bit of background. From Citect/Plant SCADA 2018 and later you can no longer perform an activity of just copying data around manually. (See Readme note). You need to use the product features (Save As, Copy project, GBA Automation to do that). From 2018 onwards we made a significant change to the page update mechanism to increase its performance significantly by only updating absolutely what it needs to based upon a version ID in the graphic entity itself.

    That change means doing activities like deleting all the PG*dbf's in a project and running update project won't do anything. From an update mechanism, GB determines that all the graphics are linking to the latest version of everything else. So making changes to the dbf's (manual edits or replaces) is outside the rules and therefore ignored.

    bradley

  • Hi Bradley,

    It's great that you do something on the page update mechanism that not been working perfect all the times..

    I've noticed that after adjusting a genie, and then updating pages sometimes don't work. Even copying and pasting a genie(s) on a page don't always work.. In rare cases, I need to delete the old genie & insert the adjusted genie again..
    I believe that still can happen in version 2018 R2, but I'm not sure..

    'Regular' super-genies, that create own page haven't I been using at all for many years since it almost never updates when adjusted. Instead I've using 'system pages'  for super-genies that I can adjust direct for many years..
    That Issue is perhaps solved now, but I thinks it's faster to use system-pages, so that's not really an issue for me..

    The same thing goes for incremental compile, That I never use..
    ** Sometimes on New projects, or when working on projects made by other I forget to uncheck, So I believe it's still an issue..
    But, I'm not sure since the first thing I normally do is to uncheck to not use incremental compile..
    and I'm almost always pack before compiling to be sure everything works out, and I always use systempages for supergenies, etc..

    making things go fast is good, but do things fast and miss something is an issue..
    So, even if it's faster, I still prefer that it's stable and that page update everything, and that every made adjustment compiles..

    Keep up the good work to make this great SCADA even better!!

    // Michael