Input Tag Definitions

IO-Link Master Module Input Tags
Name
Data Type
Definition
Valid Values
RunMode
BOOL
Indicates the operating state of the input.
0 = Idle
1 = Run
When the value is 0, it means one of the following:
  • Connection is not up.
  • Connection has been opened but the module has not started producing data for the connection.
  • Because the controller is in Program Mode, the module is not applying output tag data but is applying the Program Mode states of Output channels instead.
When the value is 1, it means the following:
  • Connection is up.
  • Module is producing data for the connection.
  • Output tag data is being applied.
ConnectionFaulted
BOOL
Indicates if a connection to the target is running.
The module always returns a zero in this member. The controller overwrites the zero with a one when the connection is not up.
0 = Connection is running
1 = Connection is not running
DiagnosticActive
BOOL
Indicates if any diagnostics are active or if the prognostics threshold is reached.
0 = No diagnostics are active
1 = One or more diagnostics are active or the prognostics threshold is reached.
CIPSyncValid
BOOL
Indicates whether the module is synced with a 1588 master.
A set bit alone cannot indicate that it is synced to the same master clock of the owner controller.
You must compare the Grandmaster Clock ID of both the module and the owner controller. For more information, see PointMax IO-Link Master Module User Manual, publication 5034-UM004.
0 = CIP Sync is not available
1 = CIP Sync is available
CIPSyncTimeout
BOOL
Indicates if the module was previously synchronized with a 1588 master but the module is not synced now due to a timeout.
0 = A valid time master has not timed out
1 = A valid time master was detected on the backplane, but the time master has timed out.
The module is using its local clock and can be drifting away from the last known master time.
DiagnosticSequenceCount
SINT
Increments each time that a distinct diagnostic condition is detected, and each time a distinct diagnostic condition transitions from detected to not detected.
-128…+127
The value of 0 is skipped except during module powerup.
Counterxx.Data
BOOL
Indicates the state of the input.
0 = Off
1 = On
Counterxx.Fault
BOOL
Indicates that counter data is inaccurate and cannot be trusted for use in the application.
If the tag is set to 1, you must troubleshoot the module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the tag to change to 1 is removed, the tag automatically resets to 0.
0 = No fault exists
1 = Fault exists
Counterxx.Uncertain
BOOL
Indicates that counter data can be inaccurate but the degree of inaccuracy is not known.
If the tag is set to 1, you must troubleshoot the module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the tag to change to 1 is removed, the tag automatically resets to 0.
0 = Good data
1 = Uncertain data
Counterxx.Done
BOOL
If RolloverAtPreset is set, indicates if Count ≥ Preset.
If RolloverAtPreset is not set, always 0.
0 = Counter has not reached the Preset value
1 = Counter has reached the Preset value
Counterxx.Rollover
BOOL
The counter counted up to Preset -1 and continued counting from 0.
The RolloverAck bit transitioning from 0 to 1 or the Reset transitioning from 0 to 1 clears this bit.
0 = Counter has not counted up to Preset -1
1 = Counter counted up to Preset -1 and continued counting from 0
Counterxx.Count
BOOL
The number of input transitions counted by a counter.
All values
IOLinkxx.Fault
BOOL
Indicates that IO-Link data is inaccurate and cannot be trusted for use in the application.
If the tag is set to 1, you must troubleshoot the module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the tag to change to 1 is removed, the tag automatically resets to 0.
0 = Good
1 = Bad, causing fault
IOLinkxx.Uncertain
BOOL
Indicates that IO-Link data can be inaccurate but the degree of inaccuracy is not known.
If the tag is set to 1, you must troubleshoot the module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the tag to change to 1 is removed, the tag automatically resets to 0.
0 = Good data
1 = Uncertain data
Ptxx.Data
BOOL
Indicates the state of the input or echo of the digital output state applied.
0 = Off
1 = On
Ptxx.Fault
BOOL
Indicates that channel data is inaccurate and cannot be trusted for use in the application.
If the tag is set to 1, you must troubleshoot the module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the tag to change to 1 is removed, the tag automatically resets to 0.
0 = Good
1 = Bad, causing fault
Ptxx.Uncertain
BOOL
Indicates that channel data can be inaccurate but the degree of inaccuracy is not known.
If the tag is set to 1, you must troubleshoot the module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the tag to change to 1 is removed, the tag automatically resets to 0.
0 = Good data
1 = Uncertain data
Ptxx.Chatter
BOOL
Indicates if the input is chattering per the ChatterTime and ChatterCount settings.
0 = Normal
1 = Input is chattering
Ptxx.TimestampOverflowOffOn
BOOL
Indicates an Off to On timestamp was lost.
A timestamp can be lost when TimestampLatchEn is set but the reported timestamp is not acknowledged in time.
If TimestampLatchEn is clear, a timestamp was overwritten.
0 or 1
Ptxx.TimestampOverflowOnOff
BOOL
Indicates an On to Off timestamp was lost.
A timestamp can be lost when TimestampLatchEn is set but the reported timestamp is not acknowledged in time.
If TimestampLatchEn is clear, a timestamp was overwritten.
0 or 1
Ptxx.CIPSyncValid
BOOL
Indicates whether the module is synced with a 1588 master.
A set bit alone cannot indicate that it is synced to the same master clock of the owner controller.
You must compare the Grandmaster Clock ID of both the module and the owner controller. For more information, see PointMax IO-Link Master Module User Manual, publication 5034-UM004.
0 = CIP Sync is not available
1 = CIP Sync is available
Ptxx.CIPSyncTimeout
BOOL
Indicates if the module was previously synchronized with a 1588 master but the module is not synced now due to a timeout.
0 = A valid time master has not timed out
1 = A valid time master has timed out
Ptxx.TimestampOffOnNumber
INT
An Off to On timestamp identifier for the currently produced timestamp.
All values
Ptxx.TimestampOnOfNumber
INT
An On to Off timestamp identifier for the currently produced timestamp.
All values
Ptxx.TimestampOffOn
LINT
64-bit timestamp that corresponds to when a change of state Off to On was recorded at the input.
All values
Ptxx.TimestampOnOff
LINT
64-bit timestamp that corresponds to when a change of state On to Off was recorded at the input.
All values
EventStatus[x].EventDropped
BOOL
Indicates when an event has been discarded because events are occurring faster than they are being acknowledged.
0 = An event status has not been dropped
1 = An event status has been dropped
EventStatus[x].CIPSyncValid
BOOL
Indicates whether the module is synced with a 1588 master when the event occurred.
A set bit alone cannot indicate that it is synced to the same master clock of the owner controller.
0 = CIP Sync is not available
1 = CIP Sync is available
EventStatus[x].CIPSyncTimeout
BOOL
Indicates if the module was previously synchronized with a 1588 master but the module is not synced now due to a timeout when the event occurred.
0 = A valid time master has not timed out
1 = A valid time master has timed out
EventStatus[x].EventReset
BOOL
When Eventxx.ResetEvent transitions from 0 to 1, EventStatus[x].EventReset transitions to 1 to indicate that the reset was received and completed.
It stays 1 until Eventxx.ResetEvent transition to zero.
0 = Do not reset
1 = Reset
EventStatus[x].EventsPending
SINT
The number of events currently queued in the module. A value greater than zero indicates that the controller is not currently keeping up with the rate of events.
All positive values
EventStatus[x].EventNumber
DINT
Running count of events, which increments by one for each new time event.
The originator sets Eventxx.EventNumberAck to Eventxx.EventNumber to acknowledge receipt of the event.
When the number of events reaches its maximum value and rolls over, it rolls over to 1, not 0.
All values
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal