Which version of the Etherlab master are you using? Out of the box, FoE does not work – you need to use the unofficial patchset version.
Having said that, where possible I’d still recommend using TwinCAT to update the firmware of Beckhoff slaves. Gavin Lambert Senior Software Developer [cid:logo_compac_5dcf97ef-52f5-498c-8b9b-728410ddffaf.png] [cid:compacicon_82e8a8c7-154a-4a32-9720-a5badb6258e0.png]<http://www.compacsort.com> [cid:facebook_fa85b924-53b9-45cc-8162-0564f64ec3a3.png] <https://www.facebook.com/Compacsort> [cid:linkedin_4ec016ad-84fa-443c-85a3-b9615a4ccef8.png] <https://www.linkedin.com/company/compac-sorting-equipment/> [cid:youtube_32142163-fc27-4aed-b14d-e8a377f98a6d.png] <https://vimeo.com/compacsort> [cid:twitter_d89338d8-98c8-4b65-9a9e-7b1333160b0d.png] <https://twitter.com/compacsort> [cid:insta2_1cd85de9-b3a2-4971-9904-52b2481a7c82.png] <https://www.instagram.com/compacsort/> COMPAC SORTING EQUIPMENT LTD | 4 Henderson Pl | Onehunga | Auckland 1061 | New Zealand Switchboard: +64 96 34 00 88 | tomra.com<http://www.tomra.com> The information contained in this communication and any attachment is confidential and may be legally privileged. It should only be read by the person(s) to whom it is addressed. If you have received this communication in error, please notify the sender and delete the communication. From: Pierre Kurkdjian Sent: Thursday, 28 May 2020 05:20 To: etherlab-users@etherlab.org Subject: [etherlab-users] foe_write returns error Hello Etherlab Ethercat community, I am trying to update the ethercat firmware of a Beckhoff slave using the command “ethercat foe_write”. I set the ethercat slave to the right state (BOOT state) and then I run the command “ethercat foe_write”. Unfortunately I get an error message (“Failed to write via FoE: FOE_TIMEOUT_ERROR”) and I don’t know whether the firmware has been updated or not. This is what I do: $ ethercat -p0 state INIT $ ethercat -p0 state BOOT $ ethercat foe_write -p0 -o ECATFW__ the_new_firmware.hex Failed to write via FoE: FOE_TIMEOUT_ERROR Notice: the file named “the_new_firmware.hex“ really exists. If I enter the name of a non-existing file then I get a different error message. Did someone get the same issue. Thank you for your help. Best, Pierre
_______________________________________________ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
