Citect 2018 to Plant Scada 2020R2 Upgrade - strange behavior ?

Alan 25 days ago

I'm working though an upgrade Citect 2018 to Plant Scada 2020R2 Upgrade (end goal is 2023R2).

i have my primary server on 2020R2 and secondary server on 2018, i have noticed a few write functions from clients on 2018 are not working, if i shut my 2020R2 runtime down they work fine?

this only occurs when i have both servers (old and new) in runtime.

i can confirm [LAN]earliestlegacy is set as 8100 as it should be.

seems to be some issue between servers, what do i look for?

0 Jacky Lang 25 days ago

Hi Alan

Can you confirm if a tag is writable from the 2018 client while the 2020R2 server is at present? You should take a look at 2020R2 server's I/O syslog as well as the 2018 client's syslog and see if there is any error logged. The write functions are written in Cicode, try the launch Cicode debugging on the 2018 client. Alternatively, add DebugMsg in lines before, during and after writes in a questioned Cicode function, which should help narrow down the problem.

Also 2020R2 server should be configured to run in the mixed mode in order to communicate with the 2018 subsystem if PCS SMS is configured.

~Jacky
0 Alan 24 days ago in reply to Jacky Lang

Thanks Jacky, i will look into the write issue, can you explain the following please

Also 2020R2 server should be configured to run in the mixed mode in order to communicate with the 2018 subsystem if PCS SMS is configured

i can confirm 2020R2 server is in mixed mode (encryption in configurator) what do you mean by PCS SMS ( the client pc's system management server ?) on 2020R2 server the runtime is not running as service does this matter?

also have issues with alarm database, when 2020R2 server is running alarm handling is not operating correctly for the 2020R2 server or the clients even though the 2018 server is duty (running before 2020R2 starts up)