Advanced Search

Thank you, i will check this when i am at home

With loops 100 I easily got a crash.
Unfortunately it dídn't recover. Same old libusb debug message.
This is on the "new" N100 mini pc.

I understand your point about motion being the proper authority for movements.

My current focus is strictly on validating a clean and deterministic CiA402 semantic layer in isolation, before going into deeper motion integration discussions.

As suggested earlier, I think a dedicated thread about motion/motmod integration would be better for that architectural direction.

For now, I will proceed with the next step: extending this modular CiA402 stack toward dual-axis gantry/squaring validation in SIM.

Once the semantic layer is stable and multi-axis behavior is validated, it should be easier to explore tighter motion integration if needed.

It seems that's a missing piece at the end of the file.

Let's try the attached ngc file.
Load in LinuxCNC and see if it works.
It has been generated using your ncam xml project.

Maybe you could compare it with the file which gives you the error.

Regards
Giovanni
 

 

This is what i see and where the problem code accurs , could be something Wrangler with my linuxcnc or Couleur you give me some advise ?   

Hi JRC,Thanks for sharing your spindle configuration — it was really helpful. I’ve also replaced the original spindle motor with a 1000W servo from StepperOnline, and I’m  pleased with how it’s performing so far - machine has its limitations but for aluminium it seems good so far. I’ve nearly completed my enclosures; I just need to install a  coolant system and add the chip tray and filtration underneath to separate the swarf properly.I’m running the Probe Basic interface as well, which I find very intuitive and easy to use.I have the ATC fitted to my machine but haven’t configured it yet. Do you have an ATC installed on yours? If so, would you be willing to share your configuration files (INI, HAL, etc.)? That would be a huge help.Also, I’d really appreciate a bit more detail on the cylinders you’re using to counterbalance the spindle weight.I’m currently designing a 3D-printed cover for the ATC and would be happy to share it once it’s finished.Thanks again Will 
 


 

Standard vanilla Gmoccapy 2.9.4, 3-axis turret mill, no internet connection,
Has operated fine, no problems, no faults, for quite some time,

Now it powers up with a blue screen devoid of icons,
Can still launch with/Applications/Accessories/LinuxCNC/drop-down-dialog-box/Gmoccapy/.

Web search tells me the absence of desktop icons is normal for Debian 12 Gnome desktop.
Also found a Gnome extension, "desktop-icons-ng", that can be applied to add the icons.

Will I break something if I attempt to apply this extension ?

Is there a better way ?

Thanks,
John.

@andrax
You are right, the encoders are absolute and have batteries. Perhaps, the homing may be needed for squaring the gantry.

I changed all the cables with CAT6 and there are no loops. Attached are the terminal outputs for "ethercat master", "ethercat slaves" and "sudo dmesg". The synchronization errors seem to be disappeared. There is still some errors but I am not sure if they influence the EtherCAT synchronization.

When I try to execute "dmesg | grep ethercat" it does not output anything, just moves to a new row in the terminal.

EDIT 1: After I ran LinuxCNC and executed "sudo dmesg", it showed a warning that says 'Slave did not sync after 5000ms'. Attaches is a new file - dmesg_new.txt. It contains the warning for synchronization.

EDIT 2: Something weird happens to my system. After playing with LinuxCNC with different configuration, the same syncronization error appears again. It seems that the cable did not help. Attached is the lates "sudo dmesg" output - dmesg_last.txt
 

I know it's a step to include motion/motmod.
Linuxcnc should be in charge of the movements, that's the whole point.
Motion should do the the homing, and control it (as best as it can).
Motion should also make possible to switch an joint from axis to spindle. 
Or make possible to use EtherCAT probing.
We don't need to invent crazy situations, but the common ones.

What we do now with these components, homecomp, etc and I have done one myself
for Profile Velocity for spindle, is to have the component decouple the real position from motion
and then re-couple it. The right thing to do would be to have motion handle all motions.

I don't expect you to go that route. I just raise the thought.

 

IKEmaster wrote:

I need 1 card, 1 rpm sensor, 1 accelerometer + cable.

I can sell 1 card, 1 rpm sensor and 1 piezo for 210Usd included shipping to Hungary.
More info This email address is being protected from spambots. You need JavaScript enabled to view it.
 

Quick progress update on this project.

The CiA402 semantic layer has now been fully validated in pure HAL + AXIS SIM.

Current validated behavior:

- Clean separation between PDS state machine and opmode modules
- Deterministic controlword composition (no 6040 ambiguity)
- 6060/6061 handshake confirmed
- Mask/value based statusword evaluation
- Operation Enabled gating exposed as a hard industrial gate
- Fault injection during active homing:
-> immediate abort
-> op-enabled cleared
-> no false “done”
-> clean fault-reset return to OE

All of this is transport-agnostic and does not depend on LCEC or EtherCAT internals.

The next planned step is extending this architecture to dual-axis gantry / squaring validation in SIM, keeping CiA402 logic fully modular.

At this stage I do not have EtherCAT hardware available.
If someone with LCEC + CiA402 hardware would be willing to test the modular stack on real drives, I can prepare:

- Clean HAL example configuration
- Minimal README
- Reproducible test steps
- Fault and homing test scenarios

The goal is to validate that the semantic layer behaves identically when replacing the stub with real PDOs.

Feedback on the gantry direction is also welcome before I proceed further.

Ja, war direkt mit den Glasmaßstäben, weil ich sowieso den Umbau auf 3-Achs-CNC vorhatte.
Hast du den Original-Vorschubmotor/Scheibenläufer schon gegen einen Servo getauscht? Der Scheibenläufer hat nur einen Tacho und keinen Encoder.
Falls du schon einen Servo hast, sollte das auch via Servo-Encoder machbar sein. Das Nachregeln könnte man allerdings durch entsprechende Reglereinsteellungen auch verhindern (Deadband). Gibt zwar bestimmt einiges an Umkehrspiel durch die ganzen Getriebe, weiß aber nicht, ob das bei den Trapezspindeln noch groß ins Gewicht fällt.

Here it seems to work as expected.
Could you describe the error, or attach a screenshot?

Regards
Giovanni

Ich habe es gerade auf der Arbeit probiert, auf einem anderen PC, und auch dort kann ich in die Themen nichts mehr antworten, ohne die Fehlermeldung zu erhalten.
Warum kann ich das in diesen Themen?
=>  400V Servo (51 Nm) mit EtherCAT / CiA402 in LinuxCNC – bezahlbarer Drive gesucht - LinuxCNC
und 
=>  Umstieg von LinuxCNC + Mesa auf EtherCAT (Leadshine EL8 / Beckhoff) – Erfahrunge - Page 2 - LinuxCNC