Open search

Q&A with Infoteam

Questions to software specialists

Christopher Schemm answered five questions about Infoteam's PLCopen runtime system. The software includes a third-party CANopen protocol stack and supports CiA 405.

Christopher Schemm, Key Account Manager Industrie at Infoteam (Photo: Infoteam)

Q: Do you supply a CANopen protocol stack with your PLCopen runtime system? Which CiA 301 version does the stack comply with?

A: Yes, OpenPCS (optionally) includes the CANopen stack from Systec electronic. This complies with CiA 301, version 4.2.

Q: Does your CANopen protocol stack feature additional functionality as specified in CiA 302 series (e.g. Flying NMT master, SDO manager) or CiA 305 (Layer Setting Services)?

A: Yes. OpenPCS includes an SDO manager and a Configuration Manager. A Flying Master is optionally available.

Q: Does your CANopen protocol stack support the CANopen-Safety protocol? Which Safety Integrity Level does it comply with?

A: Yes, the CANopen stack in OpenPCS does support the CANopen Safety protocol. Currently we do not control this Safety Functionality from IEC 61131-3.
The CANopen stack is currently not certified for IEC 61508 (or similar), but we have successfully used it in projects for SIL 2 (certifications pending), and with modifications, in one application for SIL 3.

Christopher Schemm, Key Account Manager Industrie at Infoteam (Photo: Infoteam)

Q: Which CANopen profiles do you provide for CANopen slave implementations?

A: CANopen can be transparently controlled by IEC 61131-3. Using Network Variables (PDOs) and SDOs (controlled by IEC 61131 function blocks), the PLC can talk to any device profile.

OpenPCS can act as a CANopen Slave, if desired. Then it will, by default, not follow any specific device profile. Instead, transparently using network variables, the IEC61131 application can use networks variables from area A000h to AFFFh in the Object Dictionary (CiA 405). These can be mapped to PDOs, if required.

Q: Do you offer PLCopen function blocks for CANopen services? Do they comply with CiA 405 or are they proprietary?

A: OpenPCS supports Function Blocks compliant to CiA 405. In addition, we have function blocks WRITE_PDO, READ_PDO, RECV_BOOTUP, SEND_SYNC, and function blocks for CAN Layer 2 services: INIT, SHUTDOWN, RESET, DEFINE_CANID, MESSAGE_READ, MESSAGE_WRITE, MESSAGE_UPDATE.

Interviewer: Annegret Emerich