• State Verified Answer
  • Replies 1 reply
  • Subscribers 584 subscribers
  • Views 102 views
  • Users 0 members are here
Options
Related

CITECT.INI and Event History Log

Minerva Martin

Hi,

Asking about CITECT.INI, is there any risk that I should know about before changing this and if I do change it, how is the INI file rolled out? Do I have to restart the server that holds the CITECT server? or compiling then run is enough? I wanted to change the INI file for report. For some reason, the ALARM log files that gets generated have tagnames cut into 8 characters only. I know the default should be 

"{LocalTimeDate,23} {Tag,32} {Desc,80} {Category,16} {LogState,16} {State,16} {State_Desc,16} {Type,16}"...but for some reason, I think 32 characters is for timedate and tag.

II can definitely see 23 characters for Time and Date, but the tags have only 8 characters in it.

Also, we have 2 servers at site, will I have to change the INI file in the secondary server or is the INI file automatically updated in the secondary server?

And I would also like to do a sort of Event History Log, when I research, all I find is ALARM Logs. Is there any way to do this the same as Alarm Logs (ALARM.001 to ALARM.xxx)

I apologise for these questions, I am new in the company and there is no one to ask as there is no one else :( No team, new position, the system was done by EPC who no longer exist in the company without any handover Disappointed ...it's not their fault though. Company took too long to decide that they need someone in this position by the time, EPC no longer exist.

I don't even know if it is a backup server or secondary server hahaha, no network design document as well...i am learning as i go through...the hardway hehehe. One thing is for sure, there are 2 servers!

Parents
  • 0

     Hi  ,

    Which version of Plant SCAD are you using?

    Each Plant SCADA node has its own default Citect.ini and you have to run Computer Setup to run a compiled project. However, citect.ini can be rolled out in Profiles if the deployment system is used for distributing the compiled project to the nodes in the Plant SCADA system. Some of parameters in Citect.ini are online changeable, which doesn't require to restart, and you should refer to the online help for usage of a particular parameter. Computer Setup Editor is a great tool for this purpose as it is linked with Help, and it is very easy to find out the parameter usages. 

    As for the truncated tag names in Alarm Log files, you need to check the format of the configured log device. The format defined in citect.ini is for display only.

    Changing citect.ini on one server will not automatically update the file on another server. You have to manually update it.

    For the event history, why not use the SOE feature available in Plant SCADA? You can configure a condition as either alarm or event, and it is also possible to perform sorting in the SOE display page.

    Please refer to I/O Server Redundancy, which may also apply to other types of servers, such as alarm and trend.

    Hope I haven't missed anything here.

    Regards,

    Jacky

Reply
  • 0

     Hi  ,

    Which version of Plant SCAD are you using?

    Each Plant SCADA node has its own default Citect.ini and you have to run Computer Setup to run a compiled project. However, citect.ini can be rolled out in Profiles if the deployment system is used for distributing the compiled project to the nodes in the Plant SCADA system. Some of parameters in Citect.ini are online changeable, which doesn't require to restart, and you should refer to the online help for usage of a particular parameter. Computer Setup Editor is a great tool for this purpose as it is linked with Help, and it is very easy to find out the parameter usages. 

    As for the truncated tag names in Alarm Log files, you need to check the format of the configured log device. The format defined in citect.ini is for display only.

    Changing citect.ini on one server will not automatically update the file on another server. You have to manually update it.

    For the event history, why not use the SOE feature available in Plant SCADA? You can configure a condition as either alarm or event, and it is also possible to perform sorting in the SOE display page.

    Please refer to I/O Server Redundancy, which may also apply to other types of servers, such as alarm and trend.

    Hope I haven't missed anything here.

    Regards,

    Jacky

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