Advanced Search

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

A few questions:
1) Does pid tuning apply to open-loop stepper control (ie no encoders)? Where is it getting the error/difference signal from if I don’t have encoders or any other sensors?

 Yes. the feedback is from the stepgen position counter

2) why do these oscillations only occur periodically?

No idea, might actually be a bug in the tuning routine, so I would check motion with a real LinuxCNC setup.

A few questions:
1) Does pid tuning apply to open-loop stepper control (ie no encoders)? Where is it getting the error/difference signal from if I don’t have encoders or any other sensors?
2) why do these oscillations only occur periodically?

The auto-tuning function of the A6 series servo motors is limited to basic gain adjustment. In most cases, manual tuning based on actual operating conditions is required (refer to Chapter 6 of the manual).
What you might be looking for is a one-click auto-tuning feature similar to [other systems], but this functionality is currently still under development. The tuning interface in the software can only automatically identify inertia - all other parameters need to be manually adjusted.

Hello! My team and I have been setting up a cnc using a raspberry pi 5 running remora to an octopus pro with spi, this then uses 4 Ext motor v1.1 to generate the steps using stepgen in the octopus config to generate movement with some DM556 drivers these are wired directly to the steppers. We have been having issues, when we boot LinuxCNC an error appears, raspberry pi 5 using rp1 driver. We belive this to be a warning to tell show that the rasp5 got recognized.

We haven't been able to enable the stepper drivers, the e-stop is working. We can enable but the moment we try to jog we get a joint following error this, caused by  the drivers not getting enabled and not getting any movement. 

Any ideas on what we could do?

Made some progress on reproducing the issue:
forum.linuxcnc.org/qtvcp/57033-basic-pro...ails-on-latch-return

I have, what I think, the same problem. I'm able to reproduce this, posted a new thread that I hope get going for the issue: forum.linuxcnc.org/qtvcp/57033-basic-pro...ails-on-latch-return

So, this is going to be a lengthy post. I'm having trouble with qt_dragon_hd and probing via the "Basic Probe" interface. Sometimes, probing fails sporadically for no reason. What happens is that when I probe towards Z- (towards the work piece), when the probe tip hits the target, it stops there and does not retract for a slow probe.

Up until yesterday, I had not been able to reproduce this error consistently. But now I can, and it might be easier to track this issue down.

I'm on 2.9.4, running a MESA card for my router. I have been able to reproduce it and have taken status dumps in between every action I do to reproduce the fault and actually resetting the fault so I can make one probe action again, instead of restarting LinuxCNC.

I have seen other people having similar problems that I think are related to this:
Thread #1: forum.linuxcnc.org/qtvcp/54027-retract-n...-works-after-a-while
Thread #2: forum.linuxcnc.org/49-basic-configuratio...e-with-qtdragon-hang

So, the first procedure for me to reproduce the issue:

• 1: Start LinuxCNC and home all axes.
• 2: Load the 3D probe and issue an "M61 T99" in MDI.
• 3: I can now probe several times without issues.
• STATUS FILE SAVE: A3-4_status_after_homing_and_several_successful_probes.txt
• 4: Issue an "S6000 M3" to start the spindle.
• 5: Issue an "M05" to stop the spindle.
• STATUS FILE SAVE: A5-6_status_after_M05.txt
• 6: Issue an "M02" to end the program (should not matter for testing, just in MDI mode).
• STATUS FILE SAVE: A6-7_status_after_M02.txt
• 7: Try to probe, fails.
• STATUS FILE SAVE: A7-_status_after_failed_probe.txt

To "reset" the issue, this works:

• 1: Issue a probing action that is bound to fail.
• STATUS FILE SAVE: B1-2_status_during_retract_halt_probe_fail.txt
• 2: Wait for the 30 sec delay to get the error message "latch return failed" (row 1508 in probe_routines.py, I think).
• STATUS FILE SAVE: B2-3_status_after_retract_halt_probe_fail.txt
• 3: Issue a "G1 Z1 F200" (the same as the probe routine that failed) in MDI. Z will not move after this command.
• STATUS FILE SAVE: B3-4_status_during_MDI_G1Z1F200_after_probe_fail.txt
• 4: Press the "STOP" button in the UI.
• STATUS FILE SAVE: B4-5_status_after_pressing_stop_button_after_probe_fail.txt
• 5: Reissue the "G1 Z1 F200"; now Z is moved to Z1.
• STATUS FILE SAVE: B5-6_status_after_successful_MDI_G1Z1F200_after_probe_fail.txt
• 6: Do a probe; this succeeds.
• STATUS FILE SAVE: B6-7_status_after_successful_secondary_probing.txt
• 7: Try a second time; this fails.

Here is my config: github.com/hmunktell/printNC/tree/dustshoe

If I run the sim.qtdragon_hd_xyz on the same machine as my CNC, probing is working fine and I have not been able to get the issue. Also, on my desktop, in a virtualbox, running the same sim, everything is fine.

I can not really read out anything else from the status files other than that the probing routine tries to do the latch return, but motion is not up to this task. It almost feels like a race condition somewhere, or a flag that is set after the first probe that is then locked from clearing when starting the spindle. But it works fine in the sim environment; it might be that the internals in LinuxCNC are not handled the same.

Unfortunately, I have no other computer to test this on right now. I'm attaching the status log files. If I can assist with further testing, I'm willing to, as this is rather cumbersome.

Best regards, Henrik