Advanced Search

I don't know, with the latest Windows 11 update screwing up SSD's and such " Artificial Incompetence " may
be Windows epitaph.

Ok thanks for the tip. I tried to setup the spindle via pncconf but it didn't run. I have a screenshot below of what I tried. In the TB1/TB2 tab I selected spindle PWM as you can see. Is this the wrong place to setup the spindle?

Thanks for the reply PCW. I was going through pncconfs and I couldn't find anything like discovery(Im new to LinuxCNC). While going through pncconfs I was a little confused because I flashed the 7i96s_5abobd.bin file but I couldn't find this as an option in pncconf as you can see in the image below. Anyways, I tried all three of the options that were there and none of them gave me the option of adding the BoB. Thank you for your help

Hi,

I'm trying to get my toolsetter to work, but i'm running into "Probe tripped during non-probe move" just as the probe is tripped. I've been though a lot of the usual stuff i found on the forum, like electrical noise, debouncing and so on....I'm fairly new to gcode, macros and stuff, so bear with me on this...

I'm using all the standard stuff that comes with Probe Basic, but looking at the "default" tool-touch-off macro here: 
github.com/kcjengr/probe_basic/blob/0490...ol_touch_off.ngc#L59
(And again later in line 69 with the slow probe retract)

I think that this G1-move might be the one causing my issue? I'm trying to understand why this isn't a G38.5 move instead? Then it would be a probe-movement which allows the probe to be triggered while moving...at least as far as i've understod...or maybe a combination of a G38.5 first and then a G1 move, since G38.5 stops after untripping the probe per the documentation...am i completely off here?

I've been really hesitant to post this, because a lot of people use this macro(i guess?) and i assume it work for all of these people, so chances are very high that I'm mistaken and something else is going on...

Any input will be highly appreciated! Thanks!

/Thomas

Hi Im Switching to Mesa7i96S and Clearpath SDSK Servos. Did u end up wiring each EN separately as was recommended by ClearPath?. And please can u share your final diagram

I figured out how to make it work the axis alignment
But on 2.8.4 LCNC my code hangs out the LCNC when i uncomment the:
O100 do
O100 while [#_<ValueABS> GT 0.007]
The whole code in the attachment.

I want to combine 3 measurings in one file (also in attachment), but the same result - The LCNC freezes out without errors.

The decimal test code works fine
Maybe the global parameters makes the issue?
Can anyone tell how to solve this?

Hello, I just started working on the linuxcnc esp32 W5500 setup and I ran into some issues.
1. Hardware: Rpi4 8gb with linuxcnc 2.8.4, W5500, Esp32 Wroom 
2. Esp firmware: hal2udp pwm
3. Motion: open loop stepper with TB6600 Driver

Issues
1. activation of spindle or flood no voltage change on esp32 pins 4 or 25.
2. joint follow error all axis3. My stepper is enable without the enable pin connection (I'm not even sure what pin to use for enable/disable on the esp32-the pin out from the read file doesn't show what pin to use.
3. udp.stepgen.1.enable (error doesn't exsist) (My assumption is that because the udp.comp file doesnt show the param or pin) maybe I'm missing something
4. is the Pid function only used for closed loop steppers to accurately determine movement
I attached my hal and ini files

thanks for the help

That was some great info, must be useful for the next guy using this module.
You should probably also have the -m flag to the siitool command to get the pdos mapping to the eeprom.
Just an idea, check to see if any of the sdos can permanently save the config.

I use a script to start linuxcnc. It downloads a few values for some sdos and then starts linuxcnc.

Hallo karlhe,

wie im Screenshot zu sehen funktioniert das nicht so richtig bei dir.

Probiere doch mal:
flatpak remote-add --user --if-not-exists flathub dl.flathub.org/repo/flathub.flatpakrepo

und wenn keine Fehlermeldung mehr kommt nach einem Neustart die Installation mit:
flatpak install flathub org.freecad.FreeCAD

oder du gehst gleich den anderen Weg weg von der Konsole mit Discover.
zuerst noch auf der Konsole:
sudo apt install plasma-discover plasma-discover-backend-flatpak
Dann unter Einstellungen schauen ob flatpak tatsächlich aktiviert ist. Nach einem Neustart werden dann auch die Pakete gefunden.

Viele Grüße

Michael