• Replies 7 replies
  • Subscribers 585 subscribers
  • Views 260 views
  • Users 0 members are here
Options
Related

Citect events problem

Charles

I have a project running 29 global events to store Maximum values in a DSK device. This configuration has worked great for years. Recently I have tried to add 8 more identical (except for tag names) global events, and I cannot get them to work. I have gone as far as to export the events to a csv, delete them all, and restart the system without events. then import them back in and restart the system with events. the old events go right back to working, and the new events still don't work. Any suggestions are appreciated.

Parents
  • You deleted an event, compiled, and restarted the runtime and it is still executing that event?

    Do you have multiple clients or servers that may be running the event (global events run on the client process of all clients and servers that have the event system enabled). Maybe one of them didn't get restarted or isn't getting project updates.

    Make sure you don't have the [CTEdit] Copy citect.ini parameter set or the runtime will be overwriting the runtime project files with the version from the Copy path. That could be overwriting the changes you're making to the local project. Using the deployment feature would cause a similar problem where the runtime will run the last deployed project from the deployment server, not the local project. Run the Computer Setup Wizard to select to run the project from 'Local Engineering Environment'.
Reply
  • You deleted an event, compiled, and restarted the runtime and it is still executing that event?

    Do you have multiple clients or servers that may be running the event (global events run on the client process of all clients and servers that have the event system enabled). Maybe one of them didn't get restarted or isn't getting project updates.

    Make sure you don't have the [CTEdit] Copy citect.ini parameter set or the runtime will be overwriting the runtime project files with the version from the Copy path. That could be overwriting the changes you're making to the local project. Using the deployment feature would cause a similar problem where the runtime will run the last deployed project from the deployment server, not the local project. Run the Computer Setup Wizard to select to run the project from 'Local Engineering Environment'.
Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.