• Replies 3 replies
  • Subscribers 585 subscribers
  • Views 131 views
  • Users 0 members are here
Options
Related

UNITE protocol communications with TSX PLCs after migrating from 6.1 to 2018R2

Vin

Hello,

I am having issues with updating tags in TSX PLCs using the UNITE protocol. I am using the version of the UNITE driver that installs with 2018R2 (v2.02.00.000) and this is on Windows 10.  This is in an application that I have migrated from v6.1 to 2018R2. I have a few specific questions:

1. Should one be setting the Force1Dot1 parameter in [Unite] to 1 or not specifying it which will let it default to 0 in citect.ini? The older Citect application I am upgrading from was v6.1 and I cannot find what version of UNITE that would have been using and am wondering if this parameter setting might help?

2. The v6.1 app did not have a PollTime setting for the Unite protocol in citect.ini which means the driver was running in interrupt mode. Does interrupt mode work reliably with PLC tags that are written to from Cicode or Genies or should one be specifying a PollTime value? Again trying to locate causes for why things are not updating in the PLC. Looking at the driver details in the Kernel, I am not seeing any errors.

3. Do I need to install any other driver or software separately for UNITE to work?

Thanks

Parents

  • If you mean that, after upgrading, you cannot write to PLC tags, but reading works fine, then the issue might be that you are not logged in. This is a security enhancement for Client side code in the later Citect versions, but applies to all functions if running in Single Process mode.

    You might consider running your application in Multi Process mode, if not already, and run your tag-writing script on a server process. In Multi Process mode all server processes have write privilege without being logged in.

    Be aware of other drawbacks though when enabling this, like the fact that all Citect processes are isolated, just like they would be as they were running on separate machines. For ecample, Cicode variables are local to each process.

    If Single Process mode is more convenient for your upgraded application then you could create a dummy user linked to a role without privileges or areas and log into that account from a startup script and also when a normal user logs out. This will enable Client side tag writing rights.

    Regards,

    Patrick

  • in reply to Patrick

    Hi.

    For that purpose we have a user called "Login" so the operators see "Login" instead of their names and they think nobody is logged in. 

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