010 - Implementation guidelines for product integration

Owned by Torsten Bitterlich
Last updated: Oct 18, 2021
3 min read

Following document gives hints regarding labelling and indication for a customer product incorporating field-bus protocols as EtherCAT, PROFINET and EtherNet/IP.

Labelling and Indication

EtherCAT 

For EtherCAT the following LEDs are required:

  • either a green LEDRUN and a red LEDERR

  • or one 2-colored (RED/GREEN) LEDSTERR

  • one green LINKACT LED per port

The LEDs need to be labelled according to the EtherCAT specification.

For a generic product based on software stacks a customer is on the safe side regarding EtherCAT conformance if the EtherCAT specific LED signals of the ESC for control of LEDs are used. In the data sheet of the ESC respectively the RZN1D all information are available.

The LINKACT LED should ideally be placed relative to the port, therefore the Activity LED of the Ethernet port is recommended here. The LINKACT LED should also be controlled directly by the hardware (signals CAT_LINKACT0, CAT_LINKACT1) The signal CAT_LINKACT2 is for the third EtherCAT port, which mostly is not used.

For our SoM product it’s best to use the mapped LED signals (Led1 green, Led1 red, Led2 green, Led2 red) as two bi color LEDs. Labelling and position requirements apply as well.

 

Source: ETG1300_V1i1i1_S_R_IndicatorLabelingSpecification.pdf

 

EtherCAT has the most strict requirements regarding labeling and indication. Please consider the specification not only regarding required leds (1 red led AND 1 green led OR 1 bi-color red/green led, link/activity led for each port) but also regarding labelling and positioning of the LEDs.

PROFINET

For PROFINET any LED is sufficient for signalling the WINK command. Additionally, information can be shown using other LEDs.

Quelle: TCS_00000016_DCP_V2.35.0.pdf

 

However, there is a recommendation from the PNO, which again comes down to 2 bi-color LEDs:

 

Source: PROFINET_Field_Devices_eng_2018.pdf

 

PROFINET only requires a way to signal the DCP WINK command. This can be a LED. Other LEDs optionally can display additional status information.

EtherNet/IP

 

For EtherNet/IP 2 dual-color LEDs are highly recommended. However, these are currently not mandatory here. However, if the LEDs are marked as such, they must meet the requirements of the specification:

Source: EtherNet/IP Test Record

 

EtherNet/IP recommends two bi-color (red/green) LEDs, a MS led and a NS led. If available and labelled as such, the LEDs need to comply to the specification behaviour. Either one or both of the LEDS can be available.

Conclusion

The table linked here shows which LED signals are reported by the communication module (SoM):

If you implement it this way, you are on the safe side. Therefore we always recommend 2 bi-color LEDs (each red/green). However labelling and positioning of the LEDs needs to be considered.

Disclaimer

This information is only provided for as initial idea. This idea may fit you for a specific scenario or – not. Please refer to the corresponding trade organisations of the fieldbus technologies (PNO, ETG, ODVA) as they specify requirements for fieldbus devices. These organisations can provide binding answers and may advise whether there is an exception possible. Please keep your customer in mind – what would the installing person on site need and expect? Applying for an exception should be the very last resort.

We summarised our experiences here. We do believe these information are true and backed-up by actual and up-to-date standards – however; we do not assume any responsibility for the here provided information – not direct and not indirect; not expressed and not implied either. Use any piece of information at your own risk.