Advanced Search

Is the 7I90  "BOOT" jumper (W3) set to P?

How long is the parallel cable?

Have you tried it? It should work but you need to share sdos, pdos and configgen xml

Hi, i have motherboard asrock n100dc-itx, setup Parallel port to ecp+epp v1.9 but start lunuxcnc i get error invalid cookie, got 0xffffffff, expected 0x55aacafe, please help me. Thanks.

forum.linuxcnc.org/38-general-linuxcnc-q...ird-behaviour#347456

Duplicate post removed.

If 2.9.8 works for you:
github.com/LinuxCNC/linuxcnc/releases/do...8_amd64_bookworm.deb
Download, double click, open and install with gdebi.

Looks OK, so test with the Mesa attached and a running config.

This are the results
for what i understand are good for mesa Ethernet boards
Now i´m gonna try to make connection to the board
its that okay?
 

After a moment's reflection I do get it. The 2.9.9 bug is serious because it could result in existing gcode not only not working but causing damage. So the 2.9.9. code had to be removed, and as the upgrade process still sees 2.9.9 as the "current" version, update attempts are going to fail.

But I would still like to get away from the 2.9.5 bug, and so my question remains. Is there an easy way in which I can upgrade to a subsequent version that does not suffer from this bug?

Hi everyone,
Could you please advise what to do in this situation:

When reading the PDOs, I see CiA402 indices.

But when reading the SDOs, I get indices mapped at 0x1600 and 0x1A00, which belong to the hardware interface (AIF). This mapping seems to be specific to Lenze.

Previously, the drive worked under CiA402 on a dismantled machine controlled by TwinCAT.

Now, when I try to automatically generate the XML via lcec_configgen, the XML is created with the hardware-specific indices instead of the CiA402 ones.

Has anyone dealt with this mismatch between CiA402 and Lenze’s AIF mapping? Is there a way to force or configure the XML generation so it uses CiA402 indices instead of the hardware-specific ones?

Thanks in advance for your help!

But I'm already dealing with a a bug in 2.9.5, and not being able to specify an offset when touching off the Z axis is a lot more relevant to me than the 2.9.9 bug appears to be.

I presume that I should in fact be aiming for 2.5.6, or perhaps 2.5.7 or 2.5.8. How do I go about upgrading to one of these versions?

Thank You all, for reply and taking care of this. I wrote already, why this update leads to problems with my workflow.
Sorry it's me, sometimes complaining after a new release, but i like the system running rocksolid and safe - then i have a relaxed time, operating the machine.
About new releases, its always great work with all that fixes and improvements.



 

Do not update/upgrade unless you explicitly need to.
2.9.9 is removed due to a bug sneaking in.

I would like to thank everyone that replied to this thread. PCW your suggestion did the trick. Iam now able to ping 10.10.10.10.

I've tried to follow the steps listed in the hope of getting from 2.9.5 to 2.9.9, but the upgrade fails with the following error message:

Failed to fetch www.linuxcnc.org/dists/bookworm/2.9-uspa...pace_2.9.9_amd64.deb 404 Not Found [IP: 69.163.143.134 443]

What do I need to do?