Advanced Search

Hi all,
I experimented with the mqtt-publisher on a trial basis. It works well so far, but I can't publish more than 10 HAL pins. Even if there are more than 10 parameters under keys=, only the first 10 are transmitted. Does anyone know if I'm doing something wrong? I followed the mqtt-publisher instructions exactly.
Thanks for help
Peter
 

Thanks about the gedit thing, I can add the repo for Ethercat same way all the other ones are done.

ok, first things, i had the values for controlword and statusword reversed. sigh. haha.

This is aggravating. I am seeing some "blip" on the statusword periodically, but i'm not able to capture it.

i did determine that when i power off and power on the servos, they read 0. so if i physically move the machine to the right spot the machine can safely home with motion so it wont crash...

so individually we will record a bunch of pins during homing.

statusword
controlword
opmode

ill be doing this after lunch. what other pins should i scope?

Thank you @Aviera and @Hakan! I will try that.

rodw wrote:

All the Sims work on 2.97 so I suspect the issue is in your hal file. share it and we can look or compare with one of the Sims.
 

Thank you, attached is my HAL file.

'motion' is not a hal component so you cannot and need not load it in hal.

Also I just remembered. Linuxcnc out of the box uses gedit to edit gcode files and I don't install it in my images. Please add it.
Man, I am getting confused. I just remembered you are using a different build tool. so take my last post with a grain of salt on the implementation stuff

The name is motmod.so
 

All the Sims work on 2.97 so I suspect the issue is in your hal file. share it and we can look or compare with one of the Sims.

unknown wrote:

I'm not too sure if this may help
github.com/MichaIng/DietPi/issues/6577

The power saving feature shouldn't be kicking whilst there is traffic, but stranger things do happen. And I know the RPi is on a later kernel.
Actually that reminds me I'll have to talk to Rod about Ethercat repos for the new image.

Hmm, that puts the kybosh on the kernel.org docs saying EEE is disabled by default. Always disable it!

I have installed LinuxCNC ver 2.9.7 including linuxcnc-uspace. LinuxCNC seems to be running fine.

I'm trying to learn HAL and coded "loadrt motion" in my playground HAL file.

When I open my playground config in LinuxCNC, I keep getting the error: "motion: dlopen: /usr/lib/linuxcnc/modules/motion.so: cannot open shared object file: No such file or directory"

When I run "dpkg -l | grep linuxcnc", I see: "ii  linuxcnc-uspace  1:2.9.7  amd64 motion controller for CNC machines and robots"

When I view the "/usr/lib/linuxcnc/modules" directory there is a "motmod.so" file but no "motion.so" file.

It is my understanding that motmod.so was part of LinuxCNC v2.8 and older and motion.so is part of LinuxCNC v2.9 and up.

I am a new to and just learning LinuxCNC as I prepare for a manual lathe CNC conversion.

Am I doing something wrong? Is there an issue with my LinuxCNC install?

Thanks!

unknown wrote:

I'll need your advice regarding setting up Ethercat repos Rod, and whether a 6.12.34 kernel is supported. As I kept to the RPi rt kernel from their repo. And one kernel supports both the 4 and 5.

I think it should be pretty easy. I did raise an issue about Trixie support and they actioned it.
Download this script,
forum.linuxcnc.org/ethercat/53785-instal...thercat-repositories
change the Debian_12 to Debian_13 and run it in the main user script that installs our custom stuff.

We don't install anything, just set up the repository apt update will tell you if there is any error. You will see warnings about the key will expire in 12 months which is not our problem



 

If you are already here, you should really watch this, it is by far the most comprehensive video for complicated and parametric stuff.

Do you have the drive manual?

Is this a 5V push-pull output?

 

Dank Hilfe aus diesem Forum bin ich jetzt ein Stückchen weiter.
Den I/O-Bereich meine 7i76eu (TB1) habe ich an einen 12V Ausgang meines ATX-Netzteiles angeschlossen. Ebenso den P4 (mit 5V).
Die Näherungssensoren für „Home“ liefern entsprechend ein verwertbares „True“ auf der Karte.
Ein SSR, dass das 48V-Netzteil für die Schrittmotoren einschaltet funktioniert auch.
(Netter Nebeneffekt ist, das ich mir das Enabled der Motoren sparen kann)
Jetzt stehe ich vor der Frage, wie ich das Alarmsignal der geplanten Closed-Loop-Schrittmotoren (die ja nur 5V liefern) in die Software bringe.
Die „Input’s“ der Karte scheinen nur auf die 12V zu reagieren.

=11.0ptMuss ich da einen Transistor zwischenschalten, der mir aus den 5V ein 12V Signal macht?
=11.0ptWenn ja, was sollte ich da am besten nehmen (Transistor/Schaltung)=11.0ptOder gibt es noch eine andere Möglichkeit?

Grüße, 2tinker