tx_event_ctrlr RCC Worker

Detail

When writing a value to the txen property that is different from its current value, there will be some finite delay before that write action’s correspond ZLM is sent to the output port. Because the value read from the txen property is indicative of the current state (i.e. the last ZLM sent), the readback value of txen may differ from the value previously written until some amount of time has passed. If multiple property writes somehow occur before their corresponding ZLMs can be sent, they are queued for processing. The following table gives an example.

Table 100: txen write / readback example

Action

Time

write txen=false

0 sec

txOff ZLM sent

0.1 sec

readback value of txen is false

1 sec

write txen=true

2 sec

readback value of txen is false

2.1 sec

txOn ZLM sent

2.1 sec

readback value of txen is true

2.2 sec

readback value of txen is true

2.4 sec

readback value of txen is true

2.6 sec

readback value of txen is true

2.8 sec

Worker Properties

  • ocpi_buffer_size_out

    • Type: ushort

    • Access:

      • Parameter: False

      • Writable: False

      • Initial: True

      • Volatile: False

      • Read back: False

    • Default value: 0

Worker Ports

    Outputs:

  • out

    • Protocol: tx_event

    • Optional: False

Utilization

Utilization reporting is not currently implemented.