Git update: 1.14.3
- pippin88
- Offline
- Elite Member
Less
More
- Posts: 260
- Thank you received: 45
03 Feb 2024 11:42 - 03 Feb 2024 11:50 #292303
by pippin88
Replied by pippin88 on topic Git update: 1.14.3
ethercat.xmlBased on linuxcnc-ethercat.github.io/linuxcnc-ethercat/deasda.html
I have managed to fix up (maybe) my key issue and get apt going again. Will see if I've borked future updates.
But finally worked out there is a problem / in the example doc
Note the / after "x-axis"
Changed to:
Now get slightly further:
I do have a cia402 driver with generic / manual config xml that starts linuxCNC, and the encoders register fine with that.
<?xml version="1.0" encoding="UTF-8"?>
<masters>
<master idx="0" appTimePeriod="1000000" refClockSyncCycles="5">
<slave idx="1" type="DeASDA3" name="x-axis"/>
<modParam name="opmode" value="CSP"/>
</slave>
</master>
</masters>
I have managed to fix up (maybe) my key issue and get apt going again. Will see if I've borked future updates.
But finally worked out there is a problem / in the example doc
<slave idx="1" type="DeASDA3" name="x-axis"/>
<modParam name="opmode" value="CSV"/>
</slave>
Changed to:
<slave idx="1" type="DeASDA3" name="x-axis">
<modParam name="opmode" value="CSV"/>
</slave>
Now get slightly further:
Failed to execute SDO download: Invalid argument
LCEC: slave 0.x-axis: Failed to execute SDO download (0x6060:0x00, size 1, byte0=8, error -22, abort_code 00007f97)
LCEC: fail to configure slave 0.x-axis sdo to op mode 8
I do have a cia402 driver with generic / manual config xml that starts linuxCNC, and the encoders register fine with that.
Last edit: 03 Feb 2024 11:50 by pippin88.
Please Log in or Create an account to join the conversation.
- pippin88
- Offline
- Elite Member
Less
More
- Posts: 260
- Thank you received: 45
04 Feb 2024 09:20 - 04 Feb 2024 09:20 #292364
by pippin88
Replied by pippin88 on topic Git update: 1.14.3
Please to say I have made progress.
Stupid mistakes were causing some of my issues.
I had <slave idx="1"
But on my test bench with single ethercat device, should be <slave idx="0"
Now have LinuxCNC opening, and can see encoder values, and digital input status in halshow
Don't have power wired to test actual motor movement tonight
Stupid mistakes were causing some of my issues.
I had <slave idx="1"
But on my test bench with single ethercat device, should be <slave idx="0"
Now have LinuxCNC opening, and can see encoder values, and digital input status in halshow
Don't have power wired to test actual motor movement tonight
Last edit: 04 Feb 2024 09:20 by pippin88.
The following user(s) said Thank You: rodw
Please Log in or Create an account to join the conversation.
- bob8020
- Visitor
05 Feb 2024 04:58 #292484
by bob8020
Replied by bob8020 on topic Git update: 1.14.3
Thanks for reporting on Delta with latest driver. I have a Delta B3 arriving on Wednesday and am super happy that it will be fully supported.
So far we have Beckhoff EL1xxx and EL2xxx devices along with one LeadShine EtherCAT stepper. But the real goal is three Delta B3 drives...
I think I'm going to like EtherCAT, it feels a lot like traditional Wago & Beckhoff K bus modules from olden days: you have to read every page of the manual, dot your i's and cross your t's and then it "just works".
Small favor... once you have a clean working bench top single axis for Delta A3, could you show your hal and ini files? Sometimes that allows the rest of us to find that last little typo we made
So far we have Beckhoff EL1xxx and EL2xxx devices along with one LeadShine EtherCAT stepper. But the real goal is three Delta B3 drives...
I think I'm going to like EtherCAT, it feels a lot like traditional Wago & Beckhoff K bus modules from olden days: you have to read every page of the manual, dot your i's and cross your t's and then it "just works".
Small favor... once you have a clean working bench top single axis for Delta A3, could you show your hal and ini files? Sometimes that allows the rest of us to find that last little typo we made
Please Log in or Create an account to join the conversation.
- GuiHue
- Offline
- Premium Member
Less
More
- Posts: 103
- Thank you received: 36
05 Feb 2024 09:25 - 05 Feb 2024 10:52 #292496
by GuiHue
Replied by GuiHue on topic Git update: 1.14.3
I am sorry to read that you have encountered problems. I'll get that documentation fixed and added to a PR.
With regard to sample configs:
My own testing configs are in this repo (careful, this is my working folder and not a documentation extension).
github.com/GuiHue/linuxcnctests/tree/main/ethercattest
You are interested in the ethercattest-A3-new-CSx.xxx files
Update: scottlaird has already fixed the documentation issue
With regard to sample configs:
My own testing configs are in this repo (careful, this is my working folder and not a documentation extension).
github.com/GuiHue/linuxcnctests/tree/main/ethercattest
You are interested in the ethercattest-A3-new-CSx.xxx files
Update: scottlaird has already fixed the documentation issue
Last edit: 05 Feb 2024 10:52 by GuiHue.
Please Log in or Create an account to join the conversation.
- pippin88
- Offline
- Elite Member
Less
More
- Posts: 260
- Thank you received: 45
05 Feb 2024 09:40 #292497
by pippin88
Replied by pippin88 on topic Git update: 1.14.3
A lot my fault for trying to do this when tired and not checking properly!
Thanks for sample configs
Thanks for sample configs
Please Log in or Create an account to join the conversation.
- scottlaird
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 136
- Thank you received: 155
05 Feb 2024 19:13 #292551
by scottlaird
Replied by scottlaird on topic Git update: 1.14.3
First, it looks like you probably have multiple entries in /etc/apt/* for the opensuse repository. Maybe take a quick look in there? You could probably delete all of the build.opensuse.org entries and re-create them using the shell script from above.
*DON'T* delete everything in /etc/apt, though. That'll be messy to recover from.
As for the "modParam" error--there was a bug in the documentation. It looks like you reported that over the weekend and it should be fixed now.
Are things still broken?
*DON'T* delete everything in /etc/apt, though. That'll be messy to recover from.
As for the "modParam" error--there was a bug in the documentation. It looks like you reported that over the weekend and it should be fixed now.
Are things still broken?
Please Log in or Create an account to join the conversation.
Time to create page: 0.077 seconds