Advanced Search

When I create multiple “keys=” entries one below the other, LinuxCNC no longer starts:

Preparing LinuxCNC2MQTT info: Publishing MQTT message (devices/linuxcnc/machine): {"halui.axis.x.pos-relative": -84.95, "halui.axis.y.pos-relative": -92.95, "halui.axis.z.pos-relative": 24.496, "halui.joint.0.is-homed": false, "halui.joint.1.is-homed": false, "halui.joint.2.is-homed": false, "mqtt-publisher.period": 10} qtdragon_hd_postgui.hal:30: Unknown command 'keys=halui.estop.is-activated,halui.tool.number,halui.machine.is-on,halui.program.is-running,halui.mode.is-auto,halui.mode.is-manual,halui.mode.is-mdi,halui.mode.is-teleop' info: MQTT connected: Connection Accepted. Shutting down and cleaning up LinuxCNC... task: 526 cycles, min=0.000012, max=0.011844, avg=0.009461, 0 latency excursions (> 10x expected cycle time of 0.010000s) Note: Using POSIX realtime LinuxCNC terminated with an error.
 
My configuration:

loadusr -W mqtt-publisher \
--mqtt-broker=[MQTT]BROKER --mqtt-user=[MQTT]USERNAME \
--mqtt-password=[MQTT]PASSWORD \
keys=halui.axis.x.pos-relative,halui.axis.y.pos-relative,halui.axis.z.pos-relative,\
halui.joint.0.is-homed,halui.joint.1.is-homed,halui.joint.2.is-homed

keys=halui.estop.is-activated,\
halui.tool.number,\
halui.machine.is-on,\
halui.program.is-running,\
halui.mode.is-auto,halui.mode.is-manual,halui.mode.is-mdi,halui.mode.is-teleop

setp mqtt-publisher.period 1
setp mqtt-publisher.enable 1

Peter

FYI after struggling with the files not working for a while, I did find just using http: instead of https: works

Did you notice the bit where each token is limited to 255 characters and to get sound this you can use multiple "keys" entries ?

It's hidden in under the examples heading.
If you have no further luck it may be of interest to raise an issue on the GitHub page.

The only concern I have is why my hip has been so sore this week.
On a serious note it's great to see someone getting involved and fixing the stuff that can fall through the cracks.

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!