Supported platforms: CODESYS 2.3, CODESYS 3.5, CODESYS 3.5 SAFETY

 

Creating download image

Before downloading of the binary (projectname.BIN), a programmer must create the binary file with CODESYS. The binary can be created by choosing from CODESYS online menu Create Boot Project. CODESYS must be offline when creating boot projects. As a result there should be one binary file ({Project name}.BIN) in the project folder.

Downloading the binary

Step	CANopen data	Description
1	To login to the control unit, write 1 to index 1025h sub-index 1h	Login
2	To stop, write value 4 to index 1025h sub-index 1h	Stops the PLCopen application.
3	Set the first byte of the binary to 64h	File header
4	Download binary file ({Projectname}.BIN) to index 1F50h sub-index 1h.	Downloads the application binary to the control unit.
5	Check the file download status, read RTS metrics (196 bytes) from index 1025h sub-index 3h	Download reply
6	Save to flash, write 83h to index 1025h sub-index 1h.	Saves the application to the flash.
7	Power reset the control unit.	Power reset the control unit.

Creating download images

Before downloading of the binaries (*.PRG and *.CHK), a programmer must create them with CODESYS. Binaries can be created by choosing from CODESYS online menu Create Boot Project. CODESYS must be offline when creating boot projects. As result there should be two binary files ({Project name}.PRG and {Project name}.CHK) in the project folder.

Downloading binaries

Step	CANopen data	Description
1	Write value 4 to index 1025h sub-index 1h	Stops the PLCopen application.
2	Download binary file ({Project name}.PRG) to index 1F50h sub-index 3h	Downloads the application binary to the control unit.
3	Download binary file ({Project name}.CHK) to index 1F50h sub-index 4h	Downloads the check binary to the control unit.
4	Download data {FFh,5h,0h,55h,AAh,55h,AAh} to index 1F50 sub-index 1h	Starts the new PLCopen application.

Creating download images

The binary (*.APP) to be downloaded must be created with CODESYS. The Binary can be created by choosing from CODESYS Online > Create Boot Project. CODESYS must be offline when creating boot projects. As result the binary file Application.app should be in the project folder. The file name and folder can be selected when created with the command Create Boot Project.

Downloading binaries

Step	CANopen data	Description
1	Download binary file (Application.app) to index 1F50h sub-index 3h	Stops unit and downloads the application binary to the control unit Unit stays stopped state after download. New application is taken use in next boot-up.

To download an application using USB memory:

1. Copy the application zip file named userapp_6000*.zip to a USB memory stick.

2. Remove all other USB devices, then attach the USB memory containing the zip file to the unit.

3. Boot-up the unit. The application is updated automatically during the boot-up.

4. Shut down the unit and remove the USB memory.

5. Boot-up the unit. The new application is now in use.

 

To download application using file system:

1. Copy the application zip file named userapp_6000*.zip to a unit's userapp (/opt/user/userapp) folder. For more information about generating the zip file, see Creating USB Memory for Updating Application (6000 Series).

2. Boot-up the unit. The application is updated automatically during the boot-up.

3. Shut down the unit.

4. Boot-up the unit. The new application is now in use.

 

 

 

To download an application using USB memory: See chapter Creating USB Memory for Updating Application (6000 Series)

 

To download application using file system:

1. Copy the application zip file named userapp_6000*.zip to a unit's userapp (/opt/user/userapp) folder. For more information about generating the zip file, see Creating USB Memory for Updating Application (6000 Series).

2. Boot-up the unit. The application is updated automatically during the boot-up.

3. Shut down the unit.

4. Boot-up the unit. The new application is now in use.

An application can be downloaded using USB memory.

 

To download application using USB memory:

1. Save the application file named user<1-9>_egscore_<version>.tar.gz, the checksum file user<1-9>_egscore_<version>.tar.gz.md5 to USB memory. If more than one packet is installed at the same time, user1 is installed first and then user2, etc. Runtime uses user3.

2. Connect the USB memory to the display.

3. Connect the operating voltage to Serv_EN connector (pin no. 23)

4. Boot-up the unit and after a few seconds installation starts. Then disconnect Serv_EN connector from the operating voltage. The application is updated and then the unit is automatically rebooted.

 

The application file user<1-9>_egscore_<version>.tar.gz must contain the following structure: Project/PlcLogic/Application/Application.app Project/PlcLogic/Application/Application.crc Project/PlcLogic/visu

 

Creating download images

The binary (*.APP) to be downloaded must be created with CODESYS. The Binary can be created by choosing from CODESYS Online > Create Boot Project. CODESYS must be offline when creating boot projects. As result the binary file Application.app should be in the project folder. The file name and folder can be selected when created with the command Create Boot Project.

 

 

SW protection

 

Control unit updating is protected by password. Protection must be unlocked before application download is possible.

For more information and necessary steps, follow the Unlocking SW protection guide to enable updating through CAN before downloading application binary.

Downloading binaries

Step	CANopen data	Description
1	Download binary file (Application.app) to index 1F50h sub-index 3h	Stops unit and downloads the application binary to the control unit. Unit stays stopped state after download (reboot required). New application is taken use in next boot-up.

 

 

The S/E series supports CANopen block download for firmware and applications. CRC is not supported for download.

 

See also

•  How to update S series and E series FW/SW with SWDownload

Source file Topic000281.htm

Last updated 21-Feb-2025