Irinos EC Users Manual > Troubleshooting & First Aid

Each Irinos box has a central event handler. As soon as a special event occurs in the firmware, it is reported to the event handler. Depending on its configuration, the event is

osignalled to the use/application,

ostored in the diagnostic memory.

No event should occur during normal operation.

In order to distinguish between the events, there are different event types which are distinguished by the event number.

With the appropriate configuration, the occurrence of an event is indicated via the status LED of the Irinos Box. The event can also be read out via the software interface.

The Irinos system has a very detailed error handling strategy to ensure reliable operation. Most events triggered by an error are hypothetical in nature. These are therefore not documented. Contact support if such an event occurs.

The following is a list of those events that are relevant to practice:

Event 1: „System“
Description	Common system event
Type	Information
Cause	oSystem has been started oDiagnostic memory has been cleared
Forwarding to user/application	No, cannot be activated
Entry in diagnostic memory	Yes, cannot be changed

Event 4: „MscDll communication error“
Description	A problem was detected in the communication between the Irinos system and the MscDll.
Type	Error
Cause	oAn invalid opcode has been used (Event text in diagnostic memory: „Invalid opcode in RX packet“) -> Use only valid opcodes oThe send an receive buffer size if too small (Event text in diagnostic memory: „Too much TX data“) -> Use the port number and buffers sizes given in the reference manual in the file Msc.cfg
Forwarding to user/application	Yes, cannot be de-activated
Entry in diagnostic memory	Yes, can be changed

Event 12: „EC-Link module detection error“
Description	A problem with the recognition or termination of the slave box(s) occurred when starting the Irinos system.
Type	Error
Cause	oInvalid EC-Link-wiring or broken EC-Link-cable -> Check EC-Link wiring oMultiple master boxes in one Irinos system -> Only one master-box is allowed oIrinos-Box broken -> Replace the Irinos-Box
Forwarding to user/application	For Irinos systems with multiple slave boxes: Test the system first with 1, then with 2, then with 3, and so on slave boxes to find out where the problem occurs.
Entry in diagnostic memory	Yes, can be de-activated
Eintragung in Diagnose-Speicher	Yes, can be changed

Event 13: „EC-Link communication error“
Description	Communication via the EC-Link interface is faulty.
Type	Error
Cause	oInvalid EC-Link-wiring or broken EC-Link-cable -> Check EC-Link wiring oImproper power supply (e.g. short voltage drops) -> Use an appropriate power supply.
Forwarding to user/application	The link communication has an integrated data check as well as a packet repetition in case of an error. If the packet retry fails multiple times, this event is triggered.
Entry in diagnostic memory	Yes, can be de-activated
Eintragung in Diagnose-Speicher	Yes, can be changed

Event 15: „Sine-oscillator“
Description	The sine oscillator for the inductive probes has been overloaded (short circuit).
Type	Error
Cause	oDefect of a probe -> Replace the probe oMeasuring probe incorrectly connected, e.g. when using an extension cable -> Check wiring / pin assignment
Notes	It is checked cyclically whether the oscillator short-circuit is still present. As soon as it is no longer present, the event is automatically deleted. ➔To find the cause, remove the probes one after the other. Wait 10s after removing a probe. As soon as the event is no longer active (indicated by the red error LED), the defective probe has been removed.
Forwarding to user/application	Yes, can be de-activated
Entry in diagnostic memory	Yes, can be changed

Event 24: „Inc. encoder power error“
Description	The power supply of one or more incremental encoder channels was switched off due to overload / short circuit.
Type	Error
Cause	oDefect of an incremental encoder or an incremental encoder cable -> Replace incremental encoder oIncorrect connection of an incremental encoder. -> Check wiring / pin assignment oIncremental encoder power consumption too high -> Observe permissible connected loads.
Notes	oIn the event of an overload / short circuit at a single incremental encoder input, only the input itself is deactivated. All other inputs remain functional. As soon as the overload or short-circuit has been removed, the event is automatically deleted. oIn the event of a total overload, the power supply for the incremental encoder inputs is permanently switched off. The incremental encoder inputs can only be used again after the Irinos system has been restarted.
Forwarding to user/application	Yes, can be de-activated
Entry in diagnostic memory	Yes, can be changed

Event 25: „Inc. encoder application error“
Description	The input signals of an incremental encoder input were / are outside the permissible range.
Type	Error
Cause	oIncremental encoder connector has been removed during operation. oIncremental encoder connector not fitted properly (loose contact). -> Use connector screws for proper fixation. oInput frequency of the incremental encoder too high -> Reduce speed of incremental encoder / avoid mechanical shock oIncremental encoder cable too long -> Use short cable oImproper wiring of the incremental encoder -> Check pin assignment oEncoder signals out of specification -> Check signals with Irinos Tool
Notes	oThe incremental encoder signals can be checked with the Irinos Tool (only 1Vpp). oSee application notes for incremental encoders. oThe incremental input channel can be reset via the software interface (see reference manual for detailed information). Using NmxDLL: NMX_ChannelSetParameter Using MscDLL: Opcode opcSP
Forwarding to user/application	Yes, can be de-activated
Entry in diagnostic memory	Yes, can be changed

Event 27: „Firmware update error“
Description	An error occurred during the execution of the firmware update.
Type	Error
Cause	oInvalid firmware file -> Use valid firmware file oTransmission error -> Repeat the firmware update
Notes	After a failed firmware update, the "old" firmware version is still active.
Forwarding to user/application	Yes, can be de-activated
Entry in diagnostic memory	Yes, can be changed

Event 28: „Firmware update successful“
Description	A firmware update was successfully performed.
Type	Information
Forwarding to user/application	No, cannot be activated
Entry in diagnostic memory	Yes, cannot be changed

Event 36: „Digital I/O error“
Description	The output driver for the digital outputs was overloaded (thermal overload).
Type	Error
Cause	oToo high continuous load of the digital outputs. -> Adapt maximum output load to specification.
Notes	As soon as the output driver has cooled down, the outputs are automatically enabled again and the event is deleted.
Forwarding to user/application	Yes, can be de-activated
Entry in diagnostic memory	Yes, can be changed

Event 43: "NMX sampling configuration invalid"
Description	The configuration of the real-time sampling is invalid.
Type	Error
Cause	oInvalid sampling period
Notes
Forwarding to user/application	Yes, can be de-activated
Entry in diagnostic memory	Yes, can be changed

Event 44: "NMX sampling error"
Description	Error during execution of real-time sampling.
Type	Error
Cause	oInternal buffer overflow / measurement values have not been readout in-time. oCommunication error between multiple boxes (e.g. cable broken).
Notes
Forwarding to user/application	Yes, can be de-activated
Entry in diagnostic memory	Yes, can be changed

Diagnostic events

Diagnostic events