|
Property |
Description |
Default Value |
Valid Values/Format |
|
Alerts
|
Alerts are used to raise CSM machine-local alerts that can be logged to file. These alerts are not intended to provide alerting services, but are used for advanced diagnostic purposes. The use of alerts is not recommended for the end user. These alerts are written to the CSMEvents.txt file in the service’s \dbg path.
|
Empty (Disabled) |
Each alert is defined on a new line. Each alert operates in a logical OR fashion while line items operate in a logical AND fashion. Each line must be formatted as follows: AlertName, Condition1, Condition2, Condition3, … where: AlertName is the name of the alert. Condition1,2,3… are conditions that can be defined as follows: ConditionType Comparator Value where: ConditionType can be DA, SA, DSAP,SSAP,FC,PDU,FS1,FS2,DLEN Comparitor can be <, >, =, or !
|
|
Audible |
Enabling this setting causes CSM PROFIBUS to provide audible status and alarm alerts using the PC speaker. |
Enabled |
Enabled, Disabled |
|
Automatic Slot Rebuilding |
Dynamically rebuilds the IDX statistics slots per station such that only detected stations have a set of slots. This minimizes the number of slots in the database but will make data transport difficult as IDX currently does not dynamically create/remove tags |
Enabled |
Enabled/Disabled |
|
Automatic Reconfiguration |
When CSM detects a change in the number of devices connected to the network, it will reconfigure it’s tag database such that all active stations have statistics available. It is generally desirable to leave this value as enabled. |
Enabled |
Enabled/Disabled |
|
Automatic Reconfiguration Interval |
Specifies the interval, after which, and automatic reconfiguration is forced. |
3600 (1 hour) |
0 = disabled, all other values in seconds. |
|
BaudRate |
This value can be used to force the PROFIBUS interface to a particular baud rate. In general this should not be changed as the baud rate is automatically detected, even if the baudrate on the master changes. |
10 = automatic |
Valid values: 0=9.6 Kb/s 1=19.2 Kb/s 2=45.45 Kb/s 3=93.75 Kb/s 4=187.5 Kb/s 5=500 Kb/s 6=1.5 Mb/s 7=3.0 Mb/s 8=6.0 Mb/s 9=12.0 Mb/s 10=automatic detection
|
|
dbgOn |
Controls debug file logging (advanced users only) |
0 = minimal logging |
0=minimal logging 255=full logging |
|
Disk Logging |
Controls whether captured network frames are written to a file. If enabled, all incoming frames are written to a log file, or choice (advanced users only). NOTE: disk logging can introduce significant processor overhead at higher network baud rates (>1.5Mb/s) |
0=disable |
0=disabled 1=enabled |
|
Filters |
Filters work in conjunction with Disklogging and allows for the filtering of specific packets to be written to the log (advanced users only) |
Empty (disabled) |
Each filter is defined on a new line. Each filter operates in a logical OR fashion while line items operate in a logical AND fashion. Each line must be formatted as follows: FilterName, Condition1, Condition2, Condition3, … where: FilterName is the name of the alert. Condition1,2,3… are conditions that can be defined as follows: ConditionType Comparator Value where: ConditionType can be DA, SA, DSAP,SSAP,FC,PDU,FS1,FS2,DLEN Comparitor can be <, >, =, or !
|
|
Force Data Update |
This toggle forces a once-off, unscheduled update of selected configuration properties and rebuilds the IDX tag configuration based on the devices detected by CSM. This is useful after making changes to the module configuration or after adding devices to the monitored network. |
0=not toggled |
Setting this value to 1 causes a once-off data refresh. This value will revert to 0 when the refresh is complete. |
|
Log Days |
Specifies the number of days worth of packets to log to the log file before starting a new file. If logFileSize is exceeded before this value, a new file is created. |
1=1 day |
A value greater than 0 that specifies the number of days to log to a file. |
|
Log File Size |
Specifies the log file size, in Megabytes, before creating a new log file. If logDays is exceeded before this value, a new file is created |
25 = 25 MB |
Any value, greater than 0, that specifies the file size in MB. |
|
Logging |
Controls the logging system, which includes disk and tag logging. |
0=disabled |
0=disabled, 1=enabled |
|
LogName |
The base name of any log file created when logging. |
NewLog |
Any string (max 255 characters) |
|
LogPath |
Specifies the path where log files are to be created |
C:\ |
A path string (max 255 characters) |
|
ProfiCore Serial Number |
Controls which hardware interface to which this IDX CSM will attempt to bind itself. |
0=first free interface |
0=first free interface, xxxx= the last four digits of the serial number displayed on the PROFICore interface. |
|
Retrigger |
When used in conjunction with logging, controls if a trigger can re-occur after TriggerCount number of packets have been logged. |
0=disabled |
0=disabled, 1=enabled |
|
Segment Name |
Specifies the name of the segment that is being monitored. |
NewSegment |
Any string that specifies the segment name (up to 255 characters) |
|
Slot Packet Writing |
(Experimental) Allows for PROFIBUS data to be written into IDX slots on a real-time basis. This is useful for transporting, specifically, select PROFIBUS packets to other systems for storage, analysis etc. NOTE: This feature is experimental and is not guaranteed to capture all data due to the variable, high speed data rates possible on PROFIBUS. In addition, slot packet writing can introduce significant processor overheads at higher (>1.5Mb/s) baudrates. |
0 |
0=disabled, 1=enabled. |
|
Startup Delay |
Specified a time, in milliseconds, for the module to wait before loading. |
0=no delay |
0=no delay, else any value, in milliseconds. |
|
Stats Update Interval |
Specifies the interval between tag data updates, in milliseconds. Increasing this value lowers processor overhead and reported data network traffic but increases the delay time between events and events in CSM Management Console or other statistics-dependent systems. NOTE: Setting this value to real-time (0) is not recommended due to the unnecessary high processor usage overhead introduced. |
2000 (2 seconds) |
0=real-time updates (not recommended) Any other value specifies the time in milliseconds between updates. For most applications, 1000ms should be sufficient and can usually be relaxed further. |
|
Trigger Count |
The number of packets to log after a trigger event has occurred. |
0=none |
Any integer value |
|
Triggers |
Used to control whether logging commences when a specific type of packet or condition is captured (advanced users) |
Empty (disabled) |
Each trigger is defined on a new line. Each trigger operates in a logical OR fashion while line items operate in a logical AND fashion. Each line must be formatted as follows: TriggerName, Condition1, Condition2, Condition3, … where: TriggerName is the name of the alert. Condition1,2,3… are conditions that can be defined as follows: ConditionType Comparator Value where: ConditionType can be DA, SA, DSAP,SSAP,FC,PDU,FS1,FS2,DLEN Comparitor can be <, >, =, or !
|