Advanced Search

Thanks for the help, it loaded after changing lcec name to D1 and D2, and after I commented out several lines.

ethercat slaves shows both are on OP mode, but I am sure I don't currently have enough pins defined for motion control.

I need to work out what those line problems are, some are just not defined and some are type mismatch, but I may be able to work that out.

This is a really annoying bug from Debian. This fixes it.
This was in Debian 12.1 their initial Bookworm Release and fixed in Debian 12.2 a month or so later.
But they never updated the code in thie Debian Live installer. Debian must have used a fork of this to build their images and never bothered to correct the Debian Live system.
Its not something we can fix in our ISO. We did tell the builder to exclude it and it works but as soon as you do an apt upgrade, it comes back.

 

Lcec isn't ethercat it is just an interface to ethercat, at the most a driver to use ethercat.
How well do you think your method works in this case?
Maybe if there was a detailed guide on how to set this up, and what to do in case of problem?
More than once I have wished to refer to RTFM but there isn't one.

fixed it somehow, here is what i did:

the way I connect to the mesa is from network connections I edit the network connection IPv4 setting and add a static address there 10 10 10 100, previously it had a gateway which I removed ( my other PC has this and works with it)

then I read that there is an error with the gvcp-panel.ui HAL_table.rows. I simply removed the tick for this during the pncConf wizard,

I am now able to open linuix cbc from the Launch fle on my desktop. I don't know what the gvcp does and why its buggy. but seems to be okay for now. will post later if something pops up.

PCW wrote:

Yes, a fairly ancient version of mesaflash (3.4.9)  is included with the
LinuxCNC 2.9.4 ISO, this is supposedly fixed for later releases.

I don't think mesaflash is included in V 2.9.4 in our ISOs because it is seperate to Linuxcnc and has its own Deb file.
If that is the case, 2.9.4 will just get the very early version in the Bookworm repo.
Perhaps Our Debian build system should be modified to  make mesaflash so it gets stored in our repos

Hakan wrote:

Maybe not ethercat as such but an lcec issue.
 

lcec is Ethercat (the Linuxcnc ethercat hal driver)

following the troubleshooting I outlined would unearth it all.

xlordofpainx wrote:

i get command not found on many of the commands from the text tutorial

Most of them are installed on our ISOs and IMGs on the downloads page. If you use another install method, you need to install them.

Maybe not ethercat as such but an lcec issue.
There are so many places this can go wrong, syntax mistakes.
Now I saw another thing. There is a name="D1" in the client line.
Then you should use lcec.0.D1 instead of lcec.0.0

Can you post your hal/ini files?

Might help with more eyes looking at them
 

I am trying to get my machine to run for the first time on a new PC here is my post: www.forum.linuxcnc.org/38-general-linuxc...inated-with-an-error

I can ping the mesa, I can run the motors during pnc conf, but I can't start the launch after that. Thanks in advance

Ethercat needs a master. Your linuxcnc computer can act as that master. Refer the forum stickies under the Ethercat section. The software is free.
EK1100 is not a master and it is not required unless you want to use backhoff modules attached to it.
Intel NICs are preferred as typically that have better performance but not mandatory.

You should also look at the Mesa cards as an alternative to Ethercat. The exact card will depend on your hardware choice.

This is not an Ethercat issue. Its your syntax error in hal
Use standard debugging.
Run Linuxcnc from the command line so errors are reported in the console.
Read the error message, Comment out the offending line (line 50) with a #
Continue to comment out errors until the config loads.
Use Halshow to review pin names. Work out what the correct pin name is and correct your hal file.
easy!
 

good to know.i currently am not using internet and mesa at the same time. but I am stuck on this error still on my other computer everything is the same besides the linux cnc is from 3 years ago and it works. :}

We need more info, pictures, video, smoke signals...

You can NOT have internet and Mesa on the same ethernet port.
Mesa should be wired directly to the PC, no switches or hubs or routers.
Add a USB WiFi or network card if you need internet.