TcoDiagnosis - diagnosis of software and hardware

TcOpenGroup / TcOpen

Application framework for industrial automation built on top of TwinCAT3 and .NET.

https://docs.tcopengroup.org/

MIT License

280 stars 47 forks source link

TcoDiagnosis - diagnosis of software and hardware #153

Closed philippleidig closed 2 years ago

philippleidig commented 3 years ago

Are there already ideas for the implementation of a consistent diagnosis for software and hardware in the PLC?

I am of the opinion that especially in these areas, a detailed diagnosis is considered to be very useful.

IPC / Hardware e.g. CPU usage, ...
TwinCAT e.g. licensing, realtime info, ...
EtherCAT / Fieldbus e.g. simple and in-depth
Motion / Axes

Every EtherCAT slave with CoE can send messages to the TcEventLogger. Only by checking this box. However, these messages are only in German and English. It might be possible to use these messages for diagnostics as well.

PTKu commented 3 years ago

This is would be extremely valued @philippleidig. Is there a way to set the 'enable sending Emergency' programmatically?
It would be good if we have a clear idea, and maybe some default implementation of #140 (to see if/how we can integrate messaging in general etc.) @philippleidig when you feel like it you can create a branch for this issue and sketch some prototype... I will certainly join the effort :)

philippleidig commented 3 years ago

@PTKu, the "enable sending emergency" - flag can be activated for example from the PLC via CoE - Write at runtime ( 0x10F3:05 )

I would prefer an EtherCAT diagnosis, for example, without linking variables to the hardware. Or a generic axis diagnosis for CoE and SoE purely based on AXIS_REF. I will give it some thought :)

PTKu commented 2 years ago

Hi @philippleidig I would leave this open... there have been other priorities but I would like to return to this at some point....

PTKu commented 2 years ago

@TomKovac this would be nice to consider for the HW diagnostics, would you mind having a look at it?