Skip to content

Replaces legacy event logging with tracing system#132

Open
FlorianSiBeckhoff wants to merge 7 commits into
developfrom
Tracing2
Open

Replaces legacy event logging with tracing system#132
FlorianSiBeckhoff wants to merge 7 commits into
developfrom
Tracing2

Conversation

@FlorianSiBeckhoff

@FlorianSiBeckhoff FlorianSiBeckhoff commented Apr 1, 2026

Copy link
Copy Markdown

New Features:

  • Throttle trace messages based on cycle time and ADS capacity
  • Trace in different severity levels
  • Ability to turn trace levels off after commissioning
  • Unify the display of messages

Introduces a flexible and configurable tracing system to enhance diagnostics and monitoring.

  • Replaces existing FB_TcMessage event logging with a new tracing framework.
  • Provides configurable trace levels (Verbose, Info, Warning, Error, Critical) via global parameters.
  • Supports multiple log outputs, including TwinCAT Event Logger and ADS Logger.
  • Updates mover and mediator logic to utilize the new tracing methods for improved message granularity.
  • Simplifies project network configuration by removing specific target network IDs.

Florian Simmel added 3 commits March 30, 2026 14:54
Introduces a standardized tracing system to the XTS base project, supporting both ADS and TwinCAT Event Logger outputs. The system uses a publisher-subscriber architecture with configurable severity levels and throttling to manage diagnostic message flow.
Standardizes tracing naming conventions and extracts event definitions to a dedicated TMC file. Updates the Mover function block to use the centralized tracing system instead of direct event calls and fixes a parameter ordering bug in the ADS logger.
Removes the dependency on TwinCAT Event Logger and the associated TMC file. Updates Mover, Mediator, and PositionTrigger to use the centralized Trace system for diagnostic messaging. The LogUserEvent method has been removed from the iMover interface as part of this transition.
@netbymatt

Copy link
Copy Markdown
Collaborator

This is a great upgrade! I did notice that the ErrorMover object needs to be converted to the new event logging structure for consistency.

Also, I don't know if this can be resolved at this point, but there is a lot of whitespace diff churn.

@FlorianSiBeckhoff

Copy link
Copy Markdown
Author

This is a great upgrade! I did notice that the ErrorMover object needs to be converted to the new event logging structure for consistency.

Also, I don't know if this can be resolved at this point, but there is a lot of whitespace diff churn.

I did update the ErrorMover - good catch!
Ill message you on the side for the white spaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants