Markus Mueller
Murrelektronik GmbH
new comX-CA-RE device: Invalid sync manager configuration ??
Hello everybody,
i have a problem with an new comX-CA-RE device (firmware 2.2 Build 4, 30.03.2009) as an slave .
The EtherCAT Master is TwinCAT and i´m getting the following error message:
Error (65535) 03.06.2010 11:10:29 421 ms 'Box 1 (comX RE ECS)' (1001): CoE - Emergency (Hex: a000, 00, '11 08 00 08 8a').
Error (65535) 03.06.2010 11:10:29 421 ms 'Box 1 (comX RE ECS)' (1001): state change aborted (requested 'SAFEOP', back to 'PREOP').
Error (65535) 03.06.2010 11:10:29 421 ms 'Box 1 (comX RE ECS)' (1001): 'PREOP to SAFEOP' failed! Error: 'check device state for SAFEOP'. AL Status '0x0012' read and '0x0004' expected. AL Status Code '0x0017 - Invalid sync manager configuration'
With an older comX device and firmware from 2008 the error doesn´t occur and the communication works fine!
I don´t understand why the the newer one doesn´t work?!
regards
markus
Markus Mueller
Murrelektronik GmbH
Hi Johnny,
Thank you for your description, but it doesn´t work.
I explain you my proceeding to create an new connection Twincat->comX
I downloaded the lastest ECS file from the hilscher webpage (Hilscher COMX RE ECS V2.2.X.xml)
After that, i create an new project in TwinCAT and import a new box with the hilscher ECS file.
After reload and start in config mode i´m getting the following error message:
Error (65535) 04.06.2010 11:36:41 921 ms 'Box 1 (COMX RE/ECS)' (1001): state change aborted (requested 'PREOP', back to 'INIT').
Error (65535) 04.06.2010 11:36:41 921 ms 'Box 1 (COMX RE/ECS)' (1001): 'INIT to PREOP' failed! Error: 'check vendor id'. Comparison '0x00000044' == '0xe0000044' failed.
Then i change the vendor id in the xml file i´m getting an other error message:
Error: 'check ProductCode'. Comparison '0x00000001' == '0x00000003' failed.
And at last after changing the product code i´m getting the error message from my first post. :-(
Markus
Hello Markus,
this description shows me, that the comX module must be configured with wrong settings. The vendorID changed from 0x44 to 0xE0000044 in the past. (Was necessary because of some specification/certification stuff). The Product Code 0x1 is assigned to the Hilscher CIFX Hardware (not comX!). Please check again the configuration of your comX slave. It is done with the netX Configuration Utility or Sycon.net or cifxSetup or by a warmstart message from your host. I guess that the length settings in this configuration does NOT MATCH the settings in the device description file that you downloaded from the Hilscher Homepage.
It is important to understand, that the data length limitations has changed in the past.
first: up to 64 bytes per direction (comX)
second: up to 200 bytes per direction (comX)
currently: up to 256 bytes per direction (comX)
The "Hilscher COMX RE ECS V2.2.X.xml" says to TwinCAT: This slave has a default size of 200 bytes per direction. I bet your slave configuration provides a lower value.
Johnny
Markus Mueller
Murrelektronik GmbH
Good morning Johnny,
thank you for your help.
I´ve tried your tips with the data lenght and your right, the data lenght was to short. I set the data lenght in the warmstart message to 0x000000C8 (200 Bytes) per direction, but i´m getting the same error message in Twincat.
Then i´m setting the data length greater 200 Bytes, e.g. to 256 Bytes (0x00000100) the response of the warmstart message is 0xC04C0007. I´m didn´t find anything about this error code at the actual Slave API Manual.
grettings,
Markus
Andreas Jacob
Hilscher Gesellschaft fuer Systemautomation mbH
Hi Markus,
the error message "0xC04C0007" stands for TLR_E_ECAT_DPM_INVALID_IO_SIZE_4 and means "Invalid I/O size has been tried to be configured." This can be found in the TLR_Results.h header file.
Regards
AJ
Hello Markus,
several thoughts:
1.) The version V2.2.4 is released and used in several applications in the field. So in general: it works. Anyway I suggest to get the newest available version. V2.5.9 is released now and this version supports up tp 256 bytes data per direction. Also a lot of issues have been fixed.
2.) TwinCAT allows to search for slaves (scan the complete bus). I always use this feature, because it is very easy. If TwinCAT found a slave which reports a different revision comparing to Device description files, a configuration UPLOAD is possible.
3.) The behaviour of the EtherCAT Slaves changed in the past to make all netX bases slave firmwares mor equal. I dont know the version number. Since this change it is necessary to make a CHANNELINIT (or softreset) after sending the Warmstart message. But this may only explain your problem if there is an alternative configuration in the flash.
4.) Please post your wamstart message here.
Johnny
Johnny
Hello Markus,
its not the problem that the comX reports an error. The problem is, that you configured it the wrong way.
The slave reports this error code if you configured it the process data length of N bytes and TwinCAT assumes a length of M bytes. First please check whether the process image configuration is really ok. Afterwards check TwinCAT: have you imported the correct device description file? The file may be different to an older version. Afterwards check whether the TwinCAT displays the correct amount of process data.
Anyway: life goes an and specifications are corrected and extended. Please check whether there is still a newer ECS Firmware available.
Best Regards
Johnny