Advanced Search

Here is a way to check pin names without modifying the hal file.
Use the halrun command (linuxcnc off), load lcec and lcec_config. The start halshow in another window and explore names.

debian@plasma:~/linuxcnc/configs/QtPlasma$ halrun
halcmd: loadusr -W lcec_conf ethercat-conf.xml
halcmd: loadrt lcec
Note: Using POSIX realtime
halcmd:

 

with just one drive, the cia402 is probably numbered 0. Your 3. is coming from these lines in your hal. If in doubt, comment them all out so LinuxCNC ipens, then use halshow to work out the correct pin names# ethercat to cia402 driver
net x-statusword lcec.0.3.cia-statusword => cia402.0.statusword
net x-opmode-display lcec.0.3.opmode-display => cia402.0.opmode-display
net x-drv-act-pos lcec.0.3.actual-position => cia402.0.drv-actual-position

# cia402 driver to ethercat
net x-controlword cia402.0.controlword => lcec.0.3.cia-controlword
net x-modes-of-operation cia402.0.opmode => lcec.0.3.opmode
net x-drv-target-pos cia402.0.drv-target-position => lcec.0.3.target-position

any .Deb distributed by apt needs to be signed by a gpg key and that key needs to be from a trusted source.

when code changes are sent to the LinuxCNC repositories in git hub, a series of run time tests are triggered. If the tests all pass, the buildbot is triggered and fesh debs are built automatically for a number of distributions and then become available in our apt repository. To access these you also need the gpt key.  The original LinuxCNC buildbot  could no longer do its thing from about Debian 10 due to changes in the Linux/Debian way so it stopped and could never be jumpstarted to life for neweer distros....

A new buildbot in training  was created but to this day it has never grown up into the official LinuxCNC buildbot but you can find it here.
buildbot2.highlab.com.

This workflow is different to the Debian way. To get into Debian, you need to upload the source to Debian's buildbots manually into unstable (sid) branch. As long as it works well, it is pushed to Debian testing and when a new Debian  release is made, testing is promoted to stable (currently Trixie). Trixie is basically locked for the duration of the Debian version but there may be an opportunity to push bug fixes (eg 2.9.7) to a point release of Debian Trixie. pheww!

Hallo,

linuxcnc bootet nicht mehr. ich habe mit linuxnx vom stick den rechner gestartet. Die Daten sind noch alle da, der mbr scheint nicht zu
funktionieren. Ich alter mann brauche hilfe. Mit der live linuxcnc ist die ami tastatur eingeschaltet. kann grub nicht richtig einsetzen.

danke wie immer für eure hilfe

Current state of Trixie:
Images build fine & boot, with non rt kernel.

6.12.47 kernel crashes
6.12.47 headers cant' be installed due to gcc version issues

6.12.34 kernel is good
6.12.34 headers can't be installed due to gcc version issues

Issues installing Linuxcnc built from image below wont install due to version issues with a lot of packages.

Using Trixie image downloads.raspberrypi.com/raspios_arm64/...-trixie-arm64.img.xz can have 6.12.34 kernel & headers installed.

I'll have to do some greater investigation.

Wanna know a secret, I did a big stupid, didn't realise the image was armf instead of arm64.

Current state of Bookworm.
All appears to be good, build process needs some tweaks, login screen and having xfce the default desktop plus a few little more odds and sods. Basically it works, just would like it a little more user friendly. Good thing regarding this build system is you can set your OS settings when using RPi-Imager, something that was not possible with the earlier build system.

Non necessary stuff (eyecandy), would like to have a linuxcnc themed splash screen (plymouth theming), login background (lightdm config) and desktop background. Just some Linuxcnc "branding".

How close are you, and how can I help? It's been three or four years since I worked on an ST ARM core, but I do work in the embedded world all the time, and I'm happy to be of assistance. With a little bit of digging, I can probably even find my old ST background debug dongle and the tools to support it.

I presently have a strong interest in seeing this project through to completion. I have been standardizing my computer controlled systems on a Bigtreetech Manta M8P board, which basically is a breakout board for a Raspberry Pi CM4 with an ST32H723ZET6 on it to run the lower-level stuff. I've had very good luck with it using it for Klipper/Mainsail/Crowsnest to run a 3D printer. And since the stepper drivers I want to use to drive the motors on my milling machine drop right in, I'd like to bridge LinuxCNC to it. The higher current drivers (like variants of the TMC5160) use SPI, so I'd need that driver. And it'd be nice to be able to poll a few GPIO's so I can move the mill bed with a joystick for setup. But it shouldn't be *that* difficult, I don't think.

Just let me know if/how I can contribute.

Yes you are almost there.
Just the pins are named lcec.0.0.something I would think. Second zero refers to ethercat slave id.
It's a bit catch 22. Easiest way to check pin names is with halshow and for that linuxcnc need to run and for that you need the pin names.
One can possibly temporarily comment out all reference to lcec.0.everything to use halshow to check the names.
Or use the name="X" in the slave line i  ethercat-conf.xml and refer to lcec.0.X.something.

hi there,

I think you have to check if drivers is running at FHPP or Cia402 protocol shape .. It is configurable and it should be hidden pain...

then you have to setup the SDOs and then PDOs  for Cia402 

If you are familiar with twincat 3 I can recommend it for you to jog motor from scratch... if it will jog over them just swap yout master to lcec

regards 

 

ok, i used your file, added your tools to the tool library, ran PB, homed, loaded your file, moved to a spot and set G54 using G10 L2 P1 X Y Z, then did the same for G55 and G56 and no error here,, im not near my machine with the actual probe to set things that way so can you test by the method above and see if you get the same backplot error that way? if not i will have to test next im at the shop near the machine.

Is QEI working ?
I have a RPI 4 SPI connected to a BLACK_407VE and an encoder with index connected to PE9, PE11, PE13. All works well except QEI, remora.PV.2 never changes, always = 0. Am I missing something ?
config txt :
    {
    "Thread": "Servo",
    "Type": "QEI",
            "Comment":                      "Spindle encoder",
            "PV":                        2,
            "Data Bit":                     7,
            "Enable Index":                 "True"
    }
Debug output:
Servo thread object                                                             
Spindle encoder                                                                 
Creating QEI, hardware quadrature encoder interface                             
  Encoder has index                                                             
                                                                                
Creating a std module                                                           
  Initialising hardware QEI module     

im not probing but i can set 54 55 56 work offsets with mdi in the same command in the probe routine and am getting no error in the develop version, let me go back through your post and read the triggering description again to see if i missed something.

did you try fixing the missing parenthesis and retesting?

In the upper bar where the dimensions are, set it to whatever you are using, mm or inch, before working on the drawing.
You can open a new empty file, set the mm or inch, and save that as a template, so you open that file first then paste whatever you are working on.
Reminds me of another tip you wont find on the net, when opening any other file type, like PDF, CDR, DXF, HPGL etc, always, always select the drawing with select all (CTRL+A) and open a new Inkscape (CTRL+N) then paste on the new instance with (CTRL+V).
Most of those file types do not contain dimensional info, so makes a mess when exporting them to gcode, the above will save you a lot of headache.

Ethercat explanation.
www.ethercat.org/default.htm

Obviously parameters will be machine\ethercat hardware dependant. The question is quite expansive.

There is quite a good thread getting into setting Ethercat on Linuxcnc.

Good luck with your assignment.

BipinBabu wrote:

Is there any readymade package with LinuxOS+RTKernel+Ethercat Master prebuilt.?
 

No, but the LinuxCNC ISO should already have everything needed for installing EtherCAT, see on of the pinned topic on this section.
EtherCAT can not be distributed in any ISO due to licensing issues, as far as i know.