Compiling

There are sources missing at the Synergy e2studio project

To compile the Synergy e2studio examples, please make sure that you opened the project "configuration.xml" file and generated the BSP code with the "Generate" button. This will create missing BSP source and header files.

Running

SoM does not start after Firmware Downgrade

In certain circumstances a firmware downgrade can lead to inconsistent data sizes of CM variables at the non-volatile memory. In this case, remove the application controller and delete CM variable GOAL_ID_PNIO:PDPORTDATA (and in case it does not work, every other variable of ‘Type’ Generic) with the help of the Industrial Communication Explorer - Configuration Manager.

SPI connection can not be established

Please ensure proper state of the Reset Pin of the SoM, controlled by the application controller. Also check the SPI communication using a logic analyzer or oscilloscope for valid CS and CLK. The SPI settings for the SoM are configurable - the default values and the timing are described here.

Timeouts occur during Debugging

If the application is paused (due to a breakpoint) while RPC requests occur, RPC timeouts will happen. Those are signaled with return value 0x800000AB (GOAL_ERR_TIMEOUT). Possibilities to disable the peer-loss detection, on both the SoM and the application controller, are described here.

Cyclic connection can not be established

Please make sure you use the correct device description file fitting to the used application. Profinet uses provided GSD and EtherNet/IP uses EDS files. Usually, each provided application uses a separate file.

Additionally, EtherCAT devices must be flashed with the provided EEPROM image.

Protocol Data Objects are missing at cyclic connection

The Application configures the SoM and creates the needed data objects (or submodules/assemblies) via time-consuming Remote Procedure Calls. The SoM may accept incoming traffic, even if not all objects are created, leading to incorrect connection attempts with a connected PLC. To avoid this, a connection may not be accepted until the setup of the application controller is done.

Profinet IO Module Consumer State stays bad

The Consumer States of plugged modules stay bad until setting an initial value. This is done using the API goal_pnioDataInputSet(...) after plugging the submodule.

Industrial Communication Explorer does not find the device

Please check the requirements for the Industrial Communication Explorer and the choosen protocol. A direct connection between ICE and device will also eliminate potential issues.

For EtherNet/IP devices, the connected interface must be located at the same subnet as the device.

For EtherCAT devices, the EtherCAT PLC at the ICE must be started.