- Posts: 11
- Thank you received: 0
Ethercat HAL driver
- mfalcon
- Offline
- New Member
-
sirop wrote:
mfalcon wrote:
sirop wrote:
Code:[ 133.613219] EtherCAT ERROR 0 0:1: PDO entry 0x6000:01 is not mapped. [ 133.613226] LCEC: master 0 PDO entry registration failed
That's the point to research.
thanks for help.
but I searched over here and in internet and still and I could not figure out what is the cause or remedy of this problem. I used the example xml file by sascha, so where is the mistake?
one more question too: Am I supposed to be connected online to all devices that are defined in xml file during start up of linuxcnc with hal driver?? may be this what causes error ?
Which xml file by sascha is that?
this one:
github.com/sittner/linuxcnc-ethercat/blo.../ethercat-conf_X.xml
Please Log in or Create an account to join the conversation.
- sirop
- Offline
- Elite Member
-
- Posts: 193
- Thank you received: 57
Please Log in or Create an account to join the conversation.
- narogon
- Offline
- Senior Member
-
- Posts: 43
- Thank you received: 14
sirop wrote: Do you get this
before starting the threads of the HAL script?Code:[ 6342.761973] EtherCAT WARNING 0: 124 datagrams TIMED OUT! ... [ 6352.575153] EtherCAT ERROR 0-14: Failed to set SAFEOP state, slave refused state change (PREOP + ERROR). [ 6352.579146] EtherCAT ERROR 0-14: Unknown AL status code 0x002E.
No, I get that after start HAL script.
sirop wrote:
Do you seealso if you use less slaves?Code:EtherCAT WARNING 0: 124 datagrams TIMED OUT!
That doesn't appears always. Here is other test:
sirop wrote:
AL status code 0x002E is indeed unknown.
Besides all that:lists.etherlab.org/pipermail/etherlab-dev/2016/000553.html0055-fsm_slave_config_scan-to-fsm_slave.patch
...
The motivating case was a network of about 100 slave devices; while scanning
is fast (under a second, after prior SII patches), the configuration process
to bring the slaves from PREOP to OP took about 80 seconds (and you could
see the lights coming on each slave in sequence). After the patch it takes
about 20 seconds.
I'm going to read the last link, test it and comment the results.
BR
Please Log in or Create an account to join the conversation.
- mfalcon
- Offline
- New Member
-
- Posts: 11
- Thank you received: 0
currently EK1100 coupler, but I did not connect it during starting of linuxcnc , because i was thinking that xml file will be used to check the slaves when I press "run" button in linuxcnc gui.
Please Log in or Create an account to join the conversation.
- sirop
- Offline
- Elite Member
-
- Posts: 193
- Thank you received: 57
No, I get that after start HAL script.
A quick test would be not to start the threads immediately, but wait 30 seconds
and check the logs.
Please Log in or Create an account to join the conversation.
- sirop
- Offline
- Elite Member
-
- Posts: 193
- Thank you received: 57
mfalcon wrote: @sirop
currently EK1100 coupler, but I did not connect it during starting of linuxcnc , because i was thinking that xml file will be used to check the slaves when I press "run" button in linuxcnc gui.
Connect your EK1100 and use this XML file:
linuxcnc-ethercat does not check the status of a slave if the master could not configure this slave before because this slave was off-line.
Please Log in or Create an account to join the conversation.