Skip to end of banner
Go to start of banner

ECS Firmware Update over FoE Example

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

1. Base Example

As a base for this Example, the ECS CustomOD Example can be used:

netXStudio_ECSV5_simpleConfig_V2.1.0.0\netX 90 - EtherCAT Slave - simpleConfig V2.1.0.0\Components\cifXApplicationDemoECS\Sources

2. netX90 Use Case A

Before an update can be done, the netX90 needs to be flashed with a maintenance firmware (MFW) and the *.mwc file.

For Use Case A the MFW V1.2.0.0 (File MFW-netX90_flash.mxf) is used.

ECS V5.1.0.4

and as Update ECS V5.1.0.5

3. Create Zip file for update

Take the firmware V5.1.0.5 and create the folder structure inside the zip file like this:

VAR0\XIP\FWUPDATE.NXI

Now create FWUPDATE.ZIP. The name of the zip file must be exactly FWUPDATE.ZIP .

More information can be found here: Firmware update. For example the settings for the zip archive.

4. Change the source code of the customOD Example

After downloading the zip archive, a trigger is necessary to send the packet HIL_FIRMWARE_RESET_REQ to the stack and to start the update.

For that the "Hello Word" object of the customOD example can be used.

In the Write Object Indciation, the AppECS_StartUpdateReq can be placed:


Details to this Request can be found here:

netX Dual-Port Memory packet-based services - netX 90/4000/4100 - Packet API (Revision 3)

Maintenance Firmware (netX 90/4000)

6. ESI file

Add FoE to ESI file:

5. TwinCAT

Start TwinCat. Change the device state to PREOP and select "Download...":

Do not forget to add .Zip:

Wait for download:

Till this message openes:

Go to CoE

After a click on "OK", the netx will reset and update to the new firmware.





  • No labels