• Delete application or download a new application (for more information, see sections Removing PLCopen Application and Downloading PLCopen Application)

 

 

 

• Check if one of the values defined as a condition for G_SystemOk variable is exceeded. The definitions are done using MultiTool Creator's Diagnostic tab. For more information, see MultiTool Creator manual (available in Epec Extranet).
• Check if there is another device defined to be monitored. The definition is done using MultiTool Creator. G_SystemOk is FALSE if the monitored device is not connected to the network.
• Check what is causing the G_SystemOk status to be set FALSE. Go to CODESYS > Online. Check at the end of PLC_PRG > Epec_In > Diag action what is causing the FALSE state.

 

 

• Use closed loop wiring. Supply the sensor with an output (DO) of Epec device.

 

 

Check that the output pin's (connected to valve) resistance is 10 kΩ. Resistance is 10 kΩ in HW revisions 3724DX and 4602B01. Check the HW revision using Epec CANmoon software. See also the products technical manual (available in Epec extranet).

 

 

 

 

 

 

• Check that CANopen for CAN2 is initialized

• Check that there is an NMT master on the bus

 

 

• Check that external termination resistor (120 Ω) is connected at both ends between CAN H and CAN L.
• Check that all the devices have the same bus speed (bit rate).
• Logging in with CODESYS requires CODESYS node-ID, duplicate node-IDs are not allowed.
  
   

 

 

 

• For 3606, 3724 and 4602 control units, see section Using Interrupt Functionality with J1939

• For 5050 units, see section Sending J1939 Message with Fixed Interval

 

 

 

 

Supported platforms CODESYS 2.3.

 

Check that the gateway's DLL files are in the correct location:

• 32-bit Windows: C:\Windows\System32
• 64-bit Windows: C:\Windows\SysWOW64

or

• copy gateway's DLL files to a folder (for example %Program Files%\Epec\DLL) and add the folder path to Windows' environmental variables (System > Advanced System Settings > Environment Variables)

 

 

 

 

Logging in with CODESYS requires CODESYS node-ID, duplicate node-IDs are not allowed.

 

 

• Configuration has been aborted for some reason. Check that the configured indexes are not read-only.
• Check that the transmission type is correct. Synchronous type requires SYNC protocol messages.
• Check that the slave is sending heartbeat messages. The heartbeat interval can be configured in index 1017h.

 

 

 

• Check that i_Enable is set to TRUE
• Check that there is no parameter error or AI voltage error
• Check that i_Control has value 0 when i_Enable is set to TRUE

• If PVC_CurrentValvePairController is used and a common FB pin is used for both directions, i_CommonCurrentMeasure must be set TRUE

• Check that the value for operating voltage is taken from the variable called SUPPLY_Volt (scaled supply voltage 0,01 V)

 

 

• Check that i_Enable is set to TRUE before the joystick is deviated from center
• Check that there is no parameter error or AI voltage error
• Controlling is disabled, until the error is fixed and the joystick has been centered (AI value has been within dead band range)

 

 

• By default, the application is downloaded directly to flash memory. Create boot project is not needed.

 

 

• Re-install Epec MultiTool Creator Installer using 'run as administrator'

   

• Re-install Epec MultiTool Creator Installer using 'run as administrator'

 

 

 

Supported platforms CODESYS 2.3.

 

If there are problems in target deleting, the old targets can be removed from Windows' registers. Problems can be for example corrupted Windows' file paths.

The installed targets can be found in Windows' registry keys as follows:

 

	Name of the register key
32 bit	HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AutomationAlliance\
64 bit	HKEY_LOCAL_MACHINE\SOFTWARE\AutomationAlliance\

 

 

Deleting targets from here removes them from the CODESYS target list. Removing a target in register doesn’t remove the files which are installed to the computer. Before removing a registry entry, check under the entry to which folder the target files, libraries and helps are installed for current target and remove them if necessary (entry Location).

 

 

 

 

 

 

• In MultiTool Creator Library Manager, unselect unused libraries, for example ISOBUS libraries if you are not using ISOBUS. For more information, see MultiTool Creator manual.

 

or

 

• In CODESYS IDE, go to to Resources > Target Settings and increase the Maximum number of POUs to be larger than 1200:

 

 

 

 

To use CODESYS debug functionality, set the target settings so that PLCopen application is run from RAM. If the application is run from flash, debugging can be done one POU at a time if the POU size is under 4 kBytes. For more information, see 3724 Target Settings for Memory Layout and 3606/4602 Target Settings for Memory Layout.

 

 

 

 

SDO block transfer can be used with CODESYS 2.3 IDE to download an application faster.

However, block transfer has problems in 3000/4000 series units when using CODESYS online monitoring (the project stays online for a while but then disconnects).

 

It is recommended to use CODESYS IDE's block transfer only for application download and then turn block transfer OFF when using CODESYS online monitoring.

 

Block transfer setting can be changed from Online > Communication Parameters... > Enable BlockTransfer.

 

Source file topic000796.htm

Last updated 21-Feb-2025