Tag definitions (5034-UB8F)

The 5034-UB8F module has configuration, input, output, event input, and event output tags.
Configuration Tags
Name
Data Type
Definition
Valid Values
PtxxPowerSource
SINT
Indicates the power source that is used for the point.
  • 0…7 = Point number of the Power Supply mode point that is used as SSV to the Ptxx input.
  • -1 = External power supply
  • -2 = Module SSV power
Counterxx.InputOffOnFilter
SINT
The amount of time that a signal must be in the On state before the input data indicates the On state.
The amount of time is indicated using an enumeration.
  • 5 = 0 μs
  • 6 = 5 μs
  • 7 = 10 μs
  • 8 = 20 μs
  • 9 = 50 μs
  • 10 = 100 μs
  • 11 = 200 μs
  • 12 = 500 μs
  • 13 = 1 ms
  • 14 = 2 ms
  • 15 = 5 ms
  • 16 = 10 ms
  • 17 = 20 ms
  • 18 = 50 ms
Counterxx.InputOnOffFilter
SINT
The amount of time that a signal must be in the Off state before the input data indicates the Off state.
The amount of time is indicated using an enumeration.
  • 5 = 0 μs
  • 6 = 5 μs
  • 7 = 10 μs
  • 8 = 20 μs
  • 10 = 100 μs
  • 11 = 200 μs
  • 12 = 500 μs
  • 13 = 1 ms
  • 14 = 2 ms
  • 15 = 5 ms
  • 16 = 10 ms
  • 17 = 20 ms
  • 18 = 50 ms
Counterxx.RolloverAtPreset
BOOL
Determines whether the simple counter will rollover to 0 at the Preset value.
  • 0 = No rollover at the Preset value
    When the counter counts to the Preset value, the Done bit is set.
    When the counter reaches maximum DINT (2,147,483,647) and continues counting, it rolls over to 0 and the Rollover bit is set.
  • 1 = Rollover at the Preset value
    When the counter reaches Preset-1 and continues counting, it rolls over to 0 and the Rollover bit is set. The Done bit is always 0.
Counterxx.ProgramToFaultEn
BOOL
Determines if the counter transitions to the Communication Fault Mode if the connection faults while in Program Mode.
  • 0 = Stay in Program Mode state
  • 1 = Go to Communication Fault Mode state
Counterxx.FaultMode
SINT
Selects the behavior that the counter takes if a communication fault occurs. FaultValue defines the value to go to when set to user-defined value.
  • 0 = Continue counting
  • 1 = Hold counting
  • 2 = Set to a user-defined value
Counterxx.FaultValue
DINT
Defines the value that the counter assumes when a communication fault occurs if FaultMode is set to user-defined value.
All values
Counterxx.ProgMode
SINT
Selects the behavior that the counter takes when transitioned into Program Mode or Inhibit mode. ProgValue defines the value to go to when set to user-defined value.
  • 0 = Continue counting
  • 1 = Hold counting
  • 2 = Set to a user-defined value
Counterxx.ProgValue
DINT
Defines the value that the counter assumes when the connection transitions to Program Mode or Inhibit mode if ProgMode set to user-defined value.
All values
Ptxx.InputOffOnFilter
SINT
The amount of time that a signal must be in the On state before the input data indicates the On state.
The amount of time is indicated using an enumeration.
  • 5 = 0 μs
  • 6 = 5 μs
  • 7 = 10 μs
  • 8 = 20 μs
  • 10 = 100 μs
  • 11 = 200 μs
  • 12 = 500 μs
  • 13 = 1 ms
  • 14 = 2 ms
  • 15 = 5 ms
  • 16 = 10 ms
  • 17 = 20 ms
  • 18 = 50 ms
Ptxx.InputOnOffFilter
SINT
The amount of time that a signal must be in the Off state before the input data indicates the Off state.
The amount of time is indicated using an enumeration.
  • 5 = 0 μs
  • 6 = 5 μs
  • 7 = 10 μs
  • 8 = 20 μs
  • 10 = 100 μs
  • 11 = 200 μs
  • 12 = 500 μs
  • 13 = 1 ms
  • 14 = 2 ms
  • 15 = 5 ms
  • 16 = 10 ms
  • 17 = 20 ms
  • 18 = 50 ms
Ptxx.ChatterTime
INT
A value from 1…10,000 ms in whole ms increments
1…10,000
Ptxx.ChatterCount
SINT
The number of input changes that are considered Chatter
  • 0 = Disabled
  • 2…127 = Enabled
Ptxx.CaptureOffOnEn
BOOL
Enables capturing Off to On timestamps. If cleared, the point does not record Off to On timestamps.
  • 0 = Capture disabled for Off to On input transitions
  • 1 = Capture enabled for Off to On input transitions
Ptxx.CaptureOnOffEn
BOOL
Enables capturing On to Off timestamps. If cleared, the point does not record On to Off timestamps.
  • 0 = Capture disabled for On to Off input transitions
  • 1 = Capture enabled for On to Off input transitions
Ptxx.TimestampLatchEn
BOOL
Determines whether timestamps latching is enabled.
  • 0 = Timestamps are overwritten with each successive transition
    The new timestamp overwrites the reported timestamp immediately, even if the controller has yet to extract that data.
  • 1 = Timestamps are latched until acknowledged
    The reported timestamp is not overwritten until acknowledged. All subsequent transitions on that point are ignored until acknowledged/reset.
Timestamp is acknowledged by copying the value from input tag TimestampOffOnNumber/TimestampOnOffNumber to output tag TimestampOffOnNumberAck/TimestampOnOffNumberAck.
The acknowledgment also clears TimestampOverflowOffOn/TimestampOverflowOnOff.
Ptxx.FaultMode
BOOL
Determines the behavior that the output point takes if a communication fault occurs. FaultValue defines the value to go to when set to user-defined value.
IMPORTANT: When Ptxx.FaultModeLocalControl tag exists and is set to 1, this configuration is ignored.
  • 0 = Go to a user-defined value
  • 1 = Hold last state
Ptxx.FaultValue
BOOL
Defines the value that the discrete output assumes if a communication fault occurs when FaultMode = 0.
  • 0 = Off
  • 1 = On
Ptxx.ProgMode
BOOL
Determines the behavior that the output point takes when transitioned into Program Mode or Inhibit mode. ProgValue defines the value to go to when set to user-defined value.
IMPORTANT: When Ptxx.ProgModeLocalControl tag exists and is set to 1, this configuration is ignored.
  • 0 = Go to a user-defined value
  • 1 = Hold last state
Ptxx.ProgValue
BOOL
Defines the value that the output takes when the connection transitions to Program Mode or Inhibit mode if the ProgMode bit is set to user-defined value.
  • 0 = Off
  • 1 = On
Ptxx.FaultFinalState
BOOL
If FaultValueStateDuration is nonzero, determines the final Output state after the configured FaultValueStateDuration time out occurs.
  • 0 = Off
  • 1 = On
Ptxx.ProgramToFaultEn
BOOL
Determines output action if a connection faults while the module is in a Program state.
The output can remain in a Program mode or transition to a safe state for Fault mode.
If the output remains in a Program mode, the Final Fault State parameter is ignored.
  • 0 = Stay in Program Mode state
  • 1 = Go to Communication Fault Mode state
Ptxx.FaultValueStateDuration
SINT
Determines the length of time the Communication Fault Mode state is held before the FaultFinalState is applied.
  • 0 = Hold forever
  • 1, 2, 5, or 10 seconds
Ptxx.FaultModeLocalControl
BOOL
Indicates whether the output continues to operate when communication fault occurs.
  • 0 = FaultMode is applied to the output state.
  • 1 = In Communication Fault mode, the output continues to operate as configured for this point.
Ptxx.ProgModeLocalControl
BOOL
Indicates whether the output continues to operate when transitioning to Program or Inhibit mode.
  • 0 = ProgMode is applied to the output state.
  • 1 = In Program or Inhibit mode, the output continues to operate as configured for this point.
Pwmxx.Enable
BOOL
Determines whether the output is Pulse Width Modulation or Digital Output.
  • 0 = Point is used as Digital Output
  • 1 = Point is used as Pulse Width Modulation Output
Pwmxx.CycleCountEn
BOOL
Indicates whether to stop generating pulse cycles after a defined number or continue generating pulse cycles until stopped.
  • 0 = Continue generating pulse cycles until stopped
  • 1 = Generate a defined number of pulse cycles
Pwmxx.ExecuteAllCycles
BOOL
Determines the PWM action when O.Ptxx.Data transitions to 0.
Only applicable when C.Pwmxx.CycleCountEn = 1.
  • 0 = Stop generating pulses immediately
  • 1 = Continue generating pules until O.Pwmxx.CycleCountLimit is reached
Pwmxx.EnforcePTODutyCycle
BOOL
Indicates whether to enforce the PTO specific duty cycle, which is fixed at 50%.
  • 0 = O.Pwmxx.DutyCycle is used
  • 1 = 50% duty cycle is used. O.Pwmxx.DutyCycle is ignored.
Pwmxx.IdleState
BOOL
Determines the state of the output when PWM is idle.
  • 0 = When PWM is idle, the output is Off. It also means that when PWM is running, the active state per O.Pwmxx.DutyCycle is the output in On state.
  • 1 = When PWM is idle, the output is On. It also means that when PWM is running, the active state per O.Pwmxx.DutyCycle is the output in Off state.
Ptxx.OrPt[yy]Select
BOOL
Indicates whether Pt[yy].Data participates in the logic OR calculation.
The state of the output point is determined by the logical OR of the selected points in the OR table, combined with logical AND of the selected points in the AND table.
  • 0 = Pt[yy] does not participate in the logic OR calculation.
  • 1 = Pt[yy] participates in the logic OR calculation.
Ptxx.AndPt[yy]Select
BOOL
Indicates whether Pt[yy].Data participates in the logic AND calculation.
The state of the output point is determined by the logical OR of the selected points in the OR table, combined with logical AND of the selected points in the AND table.
  • 0 = Pt[yy] does not participate in the logic AND calculation.
  • 1 = Pt[yy] participates in the logic AND calculation.
Ptxx.TriggerSelect
SINT
Specifies the input that triggers the pulse function.
  • -1 = No external trigger
    You can only use the O.Ptxx.Trigger tag to initiate the output pulse.
  • 0...7 = Point 00...Point 07
    Other point is selected as trigger to initiate the output pulse.
Ptxx.InvertTrigger
BOOL
Indicates whether the output pulse is triggered on the rising or falling edge of the input.
  • 0 = Output pulse is triggered on the rising edge.
  • 1 = Output pulse is triggered on the falling edge.
FIFOLatchEvents
BOOL
Indicates whether the FIFO event latching is enabled.
  • 0 = FIFO event latching is disabled.
    When the internal buffer is full, new timestamps detected on the input point overwrite the oldest timestamps stored in the internal buffer.
  • 1 = FIFO event latching is enabled.
    When the internal buffer is full, new timestamps detected on the input point are discarded.
Input Tags
Name
Data Type
Definition
Valid Values
RunMode
BOOL
The module's operating state
  • 0 = Idle – 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.
    • Module is not applying new output tag data because the controller is in Program Mode.
  • 1 = Run – It means the following:
    • Connection is up.
    • Module is producing data for the connection.
    • Output tag data is being applied or there is no output tag data for the connection (For example, all points configured as digital input without timestamp).
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.
  • 0 = CIP Sync is not available.
  • 1 = CIP Sync is available.
CIPSyncTimeout
BOOL
Indicates that the module was once synced 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 for each time a distinct diagnostic condition is detected, and when a distinct diagnostic condition transitions from detected to not detected.
-128…+127
The value of 0 is skipped except during module powerup.
EventsQueuedCount
DINT
Specifies the number of unacknowledged timestamp events that are queued in the module’s buffer. This includes events that are stored in the internal FIFO buffer and produce FIFO buffer.
0...276
Counterxx.Data
BOOL
Indicates the current digital input value.
  • 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 = Good
  • 1 = Bad, causing fault
Counterxx.Uncertain
BOOL
Indicates that the 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 bit transitioning from 0 to 1 clears this bit.
  • 0 = Counter has not rolled over from Preset -1 to 0
  • 1 = Counter counted up to Preset -1 and continued counting from 0
Counterxx.Count
DINT
The number of rising edge of input signal counted by the counter
All values
Ptxx.Data
(Input mode)
BOOL
Indicates the current digital input value.
  • 0 = Off
  • 1 = On
Ptxx.Data
(Output mode)
BOOL
Indicates the current digital output value applied at the screw.
  • 0 = Off
  • 1 = On
Ptxx.Fault
BOOL
Indicates that point 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 the point 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.TriggerMissed
BOOL
Indicates that at least one trigger is missed.
  • 0 = No trigger is missed
  • 1 = At least one trigger is missed. Possible causes are:
    • The output pulse triggered by the previous trigger is already active (not completed) or in the delay period (waiting).
    • An invalid PulseDelay or PulseActiveTime.
Ptxx.EventOverflow
BOOL
Indicates whether the timestamp is discarded after the internal buffer is full.
  • 0 = No timestamp is discarded.
  • 1 = At least one Timestamp is discarded.
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.
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.
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.
  • 0 = CIP Sync is not available.
  • 1 = CIP Sync is available.
Ptxx.CIPSyncTimeout
BOOL
Indicates that the module was once synced 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.
Ptxx.TimestampOffOnNumber
INT
An Off to On timestamp identifier for the currently produced timestamp
All values
Ptxx.TimestampOnOffNumber
INT
An On to Off timestamp identifier for the currently produced timestamp
All values
Ptxx.TimestampOffOn
LINT
64-bit timestamp corresponding to when a change of state Off to On was recorded at the input
All values
Ptxx.TimestampOnOff
LINT
64-bit timestamp corresponding to when a change of state On to Off was recorded at the input
All values
Schedule[x].State
SINT
Current state of the schedule tags at index x
  • 0 = Inactive
  • 1 = Active – Schedule is next to be applied to the output
  • 2 = Queued – Schedule is queued after the Active schedule
  • 3 = Expired – Schedule has been applied
  • 4 = Discarded – One of the following:
    • The requested schedule was late (received after its scheduled application time) and a more recent schedule has already been applied to that output.
    • The output point does not exist or scheduling is not enabled on the output point.
  • 5 = Late – Schedule is received after the time scheduled (schedule is applied immediately)
Schedule[x].ScheduleNumber
SINT
Echo of SequenceNumber from the output tag
All values
LateScheduleCount
INT
Count of schedules that arrive late. That is, the arrival time is after scheduled time. Counter rolls over every 65,535 late updates.
The output is still being driven to new state if this is the most recent schedule for that point. Useful in indicating that network delays/losses are causing scheduling issues.
All values
LostScheduleCount
INT
Increments whenever the schedule sequence number in the output tag skips a value, which can indicate a lost schedule. Counter rolls over every 65,535 lost updates.
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.
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.
  • 0 = CIP Sync is not available.
  • 1 = CIP Sync is available.
EventStatus[x].CIPSyncTimeout
BOOL
Indicates that the module was once synced 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.
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
Pwmxx.Active
BOOL
Indicates whether the output is generating PWM pulses.
  • 0 = The output is not generating pulses
  • 1 = The output is generating pulses
Pwmxx.Error
BOOL
Indicates whether there is an error with generating the PWM pulse.
  • 0 = There is no error present
  • 1 = One of the following errors is present:
    • O.Pwmxx.CycleTime < minimum cycle time
    • O.Pwmxx.CycleTime > maximum cycle time
    • O.Pwmxx.DutyCycle * cycle time < minimum pulse width
    • (100% - O.Pwmxx.DutyCycle) * cycle time < minimum pulse width
FIFO[x].CIPSyncTimeout
BOOL
Indicates the time sync timeout status when the timestamp event is captured.
  • 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.
FIFO[x].CIPSyncValid
BOOL
Indicates the time sync status when the timestamp event is captured
  • 0 = CIP Sync is not available.
  • 1 = CIP Sync is available.
FIFO[x].Data
BOOL
Indicates the state of the input when the timestamp event is captured.
  • 0 = Off
  • 1 = On
FIFO[x].EventNumber
DINT
A running count of events, which increment by one for each new event. Write this EventNumber into the output data field EventNumberAck to acknowledge receipt of the event. If the EventNumber reaches its maximum value, it rolls over to 1 instead of 0.
0…4,294,967,296
FIFO[x].Fault
BOOL
Indicates that point data is inaccurate and cannot be trusted for use in the application when the timestamp event is captured.
If the tag is set to 1, you must troubleshoot the module to correct the cause of the inaccuracy.
  • 0 = Good
  • 1 = Bad, causing fault
FIFO[x].Point
SINT
Indicates the point at which the event is recorded.
0...7
FIFO[x].TimeStamp
LINT
Indicates the timestamp of the captured event.
All positive values
FIFO[x].Uncertain
BOOL
Indicates that the point data can be inaccurate but the degree of inaccuracy is not known when the timestamp event is captured.
If the tag is set to 1, you must troubleshoot the module to correct the cause of the inaccuracy.
  • 0 = Good data
  • 1 = Uncertain data
Output Tags
Name
Data Type
Definition
Valid Values
Counterxx.Reset
BOOL
When this bit transitions from 0 to 1, Count and Rollover are set to zero.
  • 0 = Count and Rollover values are not set to 0
  • 1 = Count and Rolloever values are set to 0
Counterxx.RolloverAck
BOOL
Clears the Rollover bit in the input tag when it transitions from 0 to 1.
  • 0 = Rollover bit is not cleared
  • 1 = Rollover bit is cleared
Counterxx.Preset
DINT
  • If RolloverAtPreset is set, when the counter reaches Preset-1 and continues counting, it rolls over to 0 and the Rollover bit is set. The Done bit is always 0.
  • If RolloverAtPreset is not set, when the counter counts to the Preset value, the Done bit is set.
    When the counter reaches maximum DINT (2,147,483,647) and continues counting, it rolls over to 0 and the Rollover bit is set.
0…2,147,483,647
Ptxx.ResetTimestamps
BOOL
Erases all recorded timestamps for the input point when it transitions from 0 to 1.
  • 0 = Timestamps are not erased
  • 1 = Timestamps are erased
Ptxx.TimestampOffOnNumberAck
INT
An Off to On timestamp identifier that the controller writes to indicate that the identified timestamp has been seen and acted on.
When Latching is enabled and the Timestamp Number that is received from the controller matches the most recent timestamp that is produced, the module is then allowed to produce a new timestamp.
All values
Ptxx.TimestampOnOffNumberAck
INT
An On to Off timestamp identifier that the controller writes to indicate that the identified timestamp has been seen and acted on.
When Latching is enabled and the Timestamp Number that is received from the controller matches the most recent timestamp that is produced, the module is then allowed to produce a new timestamp.
All values
Ptxx.Data
BOOL
Current digital output data to be applied
  • 0 = Off
  • 1 = On
Ptxx.ScheduleEn
BOOL
Specifies the use of normal output data or scheduled data.
  • 0 = Normal output data
  • 1 = Scheduled data
Ptxx.OverrideDataEn
BOOL
Enables the output state to be overridden by the OverrideDataValue tag.
  • 0 = Output operates as configured.
  • 1 = Output state is controlled by Ptxx.OverrideDataValue.
    IMPORTANT: If you reset the OverrideDataEn tag to 0 (disabled) later, the output does not continue from its previous state.
Ptxx.OverrideDataValue
BOOL
Indicates the forced output state when the OverrideDataEn tag is set to 1.
  • 0 = Off
  • 1 = On
Ptxx.PulseActiveTime
REAL
Specifies the active duration in seconds for the generated output pulse.
All positive values
Ptxx.PulseDelay
REAL
Specifies the delay time in seconds between the trigger event and the start of the output pulse.
All positive values
Ptxx.ResetTriggerMissed
BOOL
Resets I.Ptxx.TriggerMissed bit.
A rising edge of ResetTriggerMissed bit clears the I.Ptxx.TriggerMissed bit.
Ptxx.Trigger
BOOL
Triggers the output pulse.
A rising edge of this bit triggers the output pulse. The Ptxx.PulseDelay and Ptxx.PulseActiveTime still apply.
TimeBase
LINT
Indicates the TimeBase for all schedule times.
When a new schedule entry is received, the module uses TimeBase + Schedule[n].TimeOffset to determine the time for the schedule entry.
Once the schedule entries that are based on the current TimeBase are echoed back by the module, a new TimeBase can be set to incorporate new schedule entry creations.
Any positive value
Schedule[x].ID
SINT
Indicates which hardware scheduler to use. Typically, you set the ID to the schedule index x + 1.
If you use an ID but a previous schedule entry that uses the same ID is not yet complete, the new schedule entry overwrites the previous schedule.
The schedule is considered complete when the schedule state is reported as Expired, Late, or Discarded.
  • 0 = No schedule
  • 1…32 = Valid hardware scheduler ID
Schedule[x].SequenceNumber
SINT
For every new schedule of Schedule[x], the sequence number is increased.
The expected sequence to request the module to perform a new schedule is:
  1. Set all other Schedule[x] members properly in the output tag.
  2. Increase the sequence number after step 1 is completed.
Once the module receives a new sequence number of Schedule[x], it starts processing it.
All values
Schedule[x].OutputPointSelect
SINT
Selects the output point that this schedule applies to.
0xFF means no output point selected.
0…7
Schedule[x].Data
BOOL
Output data to be applied at time that is specified in schedule
0 or 1
Schedule[x].TimeOffset
DINT
Offset from schedule base time. For more information, see the definition for TimeBase.
All values
Pwmxx.CycleTime
REAL
Indicates the period in seconds of one pulse cycle.
10 μs…30 s
Pwmxx.DutyCycle
REAL
Indicates in percentage of the pulse cycle time when output is in the active state.
0…100%
Pwmxx.CycleCountLimit
DINT
Determines the number of pulse cycles to be generated when there is a rising edge in the data.
Only applicable when C.Pwmxx.CycleCountEn = 1.
0…2,147,483,647
FIFO.EventNumberAck
DINT
Acknowledges all events with EventNumber less than or equal to this number.
IMPORTANT: If EventNumberAck does not match any event in the FIFO produce buffer, no event is acknowledged.
All values
FIFO.ResetEvents
BOOL
Erases all recorded timestamped events.
A rising edge of this bit clears all the timestamp events in the internal buffer and FIFO produce buffer, and resets I.Ptxx.EventOverflow bit.
Event Input Tags
Name
Data Type
Definition
Valid Values
RunMode
BOOL
The point's operating state
  • 0 = Idle – 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.
    • Module is not applying new output tag data because the controller is in Program Mode.
  • 1 = Run – It means the following:
    • Connection is up.
    • Module is producing data for the connection.
    • Output tag data is being applied or there is no output tag data for the connection (for example, all points configured as digital input without timestamp).
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.
DiagnosticSequenceCount
BOOL
Increments for each time a distinct diagnostic condition is detected, and when a distinct diagnostic condition transitions from detected to not detected.
-128…+127
The value of 0 is skipped except during module powerup.
Eventxx.Fault
BOOL
Detects whether the signal is good data. The fault is set to 1 by the originator when the connection is lost.
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
Eventxx.Uncertain
BOOL
Indicates that the point 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
Eventxx.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
Eventxx.EventRising
BOOL
Indicates whether an event triggered when an input transition results in an event pattern being matched.
  • 0 = Event is not triggered
  • 1 = Event is triggered
Eventxx.EventFalling
BOOL
Indicates whether an event triggered when an input transition resulted in an event pattern no longer being matched.
  • 0 = Event is not triggered
  • 1 = Event is triggered
Eventxx.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.
  • 0 = CIP Sync is not available.
  • 1 = CIP Sync is available.
Eventxx.CIPSyncTimeout
BOOL
Indicates that the module was once synced 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.
Eventxx.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
Eventxx.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
Eventxx.EventTimestamp
LINT
The time that the event occurred
All positive values
Eventxx.PtxxData
BOOL
Indicates the data value of input Ptxx when event was triggered.
  • 0 = Off
  • 1 = On
Eventxx.CounterxxDone
BOOL
Indicates the Done status of Counterxx when event was triggered.
  • 0 = Not done
  • 1 = Done
Eventxx.PtxxFault
BOOL
Indicates the fault status of input Ptxx when event is triggered.
  • 0 = No fault
  • 1 = Faulted
Eventxx.CounterxxFault
BOOL
Indicates the fault status of Counterxx when event is triggered.
  • 0 = No fault
  • 1 = Faulted
Event Output Tags
Name
Data Type
Definition
Valid Values
Eventxx.En
BOOL
When set, the corresponding event trigger definition is active and events are triggered when conditions match the definition.
  • 0 = Event trigger definition is not active and events are not triggered when conditions match the definition
  • 1 = Event trigger definition is active and events are triggered when conditions match the definition
Eventxx.EventRisingEn
BOOL
Triggers an event each time a condition change results in conditions that match the event trigger definition.
Values (EventRisingEn, EventFallingEn) represent:
  • (0, 0): Event trigger is disabled.
  • (1, 0): Event triggers on input transitions to matching the configured pattern.
  • (0, 1): Event triggers on input transitions to not matching the configured pattern.
  • (1, 1): Event triggers on input transitions to either matching or not matching the configured pattern.
Eventxx.EventFallingEn
BOOL
Triggers an event each time a condition change results in conditions that do not match the event trigger definition.
Eventxx.LatchEn
BOOL
When set, events are latched until acknowledged.
When not set, new events overwrite old events.
  • 0 = Event is not latched
  • 1 = Event is latched
Eventxx.ResetEvent
BOOL
A transition from 0 to 1 resets all events and clears the event queue on the Eventxx.
  • 0 = Do not reset
  • 1 = Reset
Eventxx.IndependentConditionTriggerEn
SINT
Determines whether an input state change or a pattern of input state changes triggers an event.
  • 0 = Event is triggered when all participating inputs in the event trigger achieve their configured values
  • 1 = Event is triggered when any participating input in the event trigger achieves their configured value
Eventxx.EventNumberAck
DINT
The controller writes back EventNumber into EventNumberAck to indicate receipt of the event.
All values
Eventxx.PtxxDataSelect
BOOL
Determines whether the input participates in the event trigger.
  • 0 = Does not participate in event trigger
  • 1 = Participates in event trigger
Eventxx.CounterxxSelect
BOOL
Determines whether the counter participates in the event trigger.
  • 0 = Does not participate in event trigger
  • 1 = Participates in event trigger
Eventxx.PtxxDataValue
BOOL
Determines the state of the input to match after the transition.
  • 0 = Off
  • 1 = On
Eventxx.CounterxxDataValue
BOOL
Determines the done state of the counter to match after the transition.
  • 0 = Not done
  • 1 = Done
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal