Advanced Search

Can you run your gcode and when stalled then

run (in a terminal)  :

halcmd show all motion. > motion.txt

( Note the . after motion )

and post motion.txt here

 

No spindle anything at the moment.
I have parts ready to install but I hoped to see the motion system working first.
(power relay, reversing relay and the pwm to 0-10V parts for the speed controller)
For the G0 neither of my Spindle CW or CCW outputs are setting which seems reasonable.

I was surprised to discover spindle.0.at-speed was set but it must be some sort of default as there is nothing wired.
Are there any other 'must have' items you can think of?
(I only set the S code in case it wanted it when I was starting to get desperate.)

I can reproduce that. Yes it happens only on a touch screen. Very annoying.
Thanks for reporting this!

Does it have any spindle feedback?
Is the spindle.at-speed set to true?
Use the "show hal configuration" from the "machine" menu to watch the pins.

Thanks! You're a legend. Got it to work and the jitter dropped to about 12000ns.

I've tried to edit the grub file so it loads the RTAI kernel by default as a quality of life improvement. Unfortunitely, editing GRUB_DEFAULT didn't work because the kernal options are in the "advanced options" menu. I'd love to know how to get the system to boot using the RTAI kernal without having to intercept the GRUB menu every time.

If it helps here is the User Manual for the Logitech Dual Action F310 Controller

sudo apt update
sudo apt install linuxcnc-uspace
No idea if it works on Ubuntu 24 but it did on 22 or 23.
The above also works on Linux Mint Debian Edition 6, should also work on Debian 13.

Leave them in breaks cleaning fluid for a night, should unclog... hopefully
Use an LED and a resistor on a parallel port pin and gnd, look at them turning on and off while joging in LinuxCNC.

To get the Logitech Dual Action F310 controller to work as a Pendant for the Scorbot-ER-3 using LinuxCNC 2.9.2, after making previous changes mentioned earlier in this forum, do the following:

Open the "scorbot-er-3.hal" file in the /linuxcnc/configs/by_machine.scorbot-er-3/ folder and add these 2 lines (after the "loadrt differential" line);
loadusr -W hal_input -KRAL Logitech
loadrt mux16 names=jogspeed

then add (after the "addf differential.0 servo-thread" line):
addf jogspeed servo-thread

save and close the file.

next open the pyvcp.hal file and add the following (at the bottom):

#******************************
# connect miscellaneous signals
#******************************

# ---HALUI signals---

net axis-select-x halui.axis.x.select
net jog-x-pos halui.axis.x.plus
net jog-x-neg halui.axis.x.minus
net jog-x-analog halui.axis.x.analog
net x-is-homed halui.joint.0.is-homed
net axis-select-y halui.axis.y.select
net jog-y-pos halui.axis.y.plus
net jog-y-neg halui.axis.y.minus
net jog-y-analog halui.axis.y.analog
net y-is-homed halui.joint.1.is-homed
net axis-select-z halui.axis.z.select
net jog-z-pos halui.axis.z.plus
net jog-z-neg halui.axis.z.minus
net jog-z-analog halui.axis.z.analog
net z-is-homed halui.joint.2.is-homed
net axis-select-a halui.axis.a.select
net jog-a-pos halui.axis.a.plus
net jog-a-neg halui.axis.a.minus
net jog-a-analog halui.axis.a.analog
net a-is-homed halui.joint.3.is-homed
net axis-select-b halui.axis.b.select
net jog-b-pos halui.axis.b.plus
net jog-b-neg halui.axis.b.minus
net jog-b-analog halui.axis.b.analog
net b-is-homed halui.joint.4.is-homed
net jog-selected-pos halui.axis.selected.plus
net jog-selected-neg halui.axis.selected.minus
net spindle-manual-cw halui.spindle.0.forward
net spindle-manual-ccw halui.spindle.0.reverse
net spindle-manual-stop halui.spindle.0.stop
net machine-is-on halui.machine.is-on
net jog-speed halui.axis.jog-speed
net MDI-mode halui.mode.is-mdi


# ---USB device jog button signals---

# connect selectable mpg jog speeds
net jog-speed-a => jogspeed.sel0
net jog-speed-b => jogspeed.sel1
net jog-speed <= jogspeed.out-f
setp jogspeed.in00 150.000000
setp jogspeed.in01 300.000000
setp jogspeed.in02 600.000000
setp jogspeed.in03 1200.000000
net jog-speed-a <= input.0.btn-base
net jog-speed-b <= input.0.btn-base2
net jog-x-pos input.0.abs-hat0x-is-pos
net jog-x-neg input.0.abs-hat0x-is-neg
net jog-y-pos input.0.abs-hat0y-is-neg
net jog-y-neg input.0.abs-hat0y-is-pos
net jog-z-pos input.0.abs-rz-is-neg
net jog-z-neg input.0.abs-rz-is-pos
net jog-a-pos input.0.abs-y-is-neg
net jog-a-neg input.0.abs-y-is-pos
net jog-b-pos input.0.abs-x-is-pos
net jog-b-neg input.0.abs-x-is-neg
net Pgm-run <= halui.program.run <= input.0.btn-thumb
net Pgm-stop <= halui.program.stop <= input.0.btn-thumb2
net Pgm-pause <= halui.program.pause <= input.0.btn-top
net Pgm-resume <= halui.program.resume <= input.0.btn-trigger
net Pgm-step <= halui.program.step <= input.0.btn-base4
net Estop-activate <= halui.estop.activate <= input.0.btn-base3

save the file.

Special note: The Pendant will not work until you home the Scorbot-ER-3. After Homing the coordinates will change to cartesian coordinates (X,Y,Z,A,. After you make these changes the pendant will work as follows:

The left joy stick controls X, and Y axis.
The right joy stick controls the Z axis.
The D-Pad controls the rotation and turning of the gripper A, and B axis.
The bottom finger triggers control the rate of movement;
nothing 150
left only 300
right only 600
both 1200

Last is the buttons:
Button 9 is estop, if pressed you have to use the keyboard to reset
Button 2 is run G-Code
Button 4 is pause program, press Button 1 to Resume
Button 3 Stop program if if press Button 2 it goes back to beginning and starts
over again
Button 10 you must first press Button 4 this will run the code one line at a time
Button 1 Resume (after Button 4, or Button 10)

I have not yet figured out how to open and close the gripper through the G-Code file or the Logitech F310 Pendant. Only the GUI interface (+ -) works for the gripper.
I hope someone smarter then me can help to figure this out, and add a replay.
Thank You all

I've been automating a small Mill.
I keep running into problems and people here have helped - thank you.
Mesa 7i95t et al.
I've got to the point where I can click the home icons on my Gmoccapy screen and it homes all three axes.
Then I move the head onto the middle of the bed with the on screen jog buttons and load a piece of program
that is basically just a set to G54 mode and do a G0 X20 rapid flip 20mm positive on the model hence the bed should move left.
Once I have that it's just relearning g code time.
But nothing happens.
I add a growing number of lines to set things up.
Still nothing. It gets to that line, highlights it and just sits there probably waiting for something or feeding at 0 so it will never end.
I've spent most of the day trying new ideas.
This is where I've got to. What do I try next? What do I take out? What obvious thing have I missed?
What do I have to do to make it move?
Is it my code? My configuration? Is it offended at my accent? Does it just hate me? (it feels a bit like that)

G1 changed back to G0, I was trying G1 as a test and it didn't help

So, es läuft jetzt, vielen Dank Aciera, ist genauso wie ich es haben wollte, alle 2 min einen Intervall ohne viel drumherum.

Die Verknüpfungen haben mir das Leben noch etwas schwer gemacht, den interval.enable habe ich mit machine-is-enabled verknüpft, ging problemlos.

Beim interval.out kam immer der Fehler, dass der Pin nicht vorhanden ist, letztendlich habe ich Hilfe von Sven die Verknüpfungen in die Postgui_call_list geschrieben, damit ging das dann auch.

In LinuxCNC 2.8x läuft das ganze wenn man in der Interval.py aus python3 python macht.


Grüsse
Steffen


 

Yeah, that's what I though, the direction signal going to 0 at every step is dubious at best. Especially looking at your older posts which clearly show a logic analyser graph with the expected step dir behavior.

I made a short video so we can all better understand what's happening, would you mind taking a look ?

(Keep in mind, these are differential signal, the dir pulse is not going in the other direction between step pulse, it's just going to the mid point, 0v)

Thanks, that works perfectly!

Yes it seems I have mistakenly used qtpy instead of PyQt6, and so needs qtpy installed. I'll align with flexgui on QT6.

Are you sure the blue trace is the Dir pin. It should only change from high to low on a direction change. I doubt you are changing direction every step pulse.

The LinuxCNC component does not control the setup and hold times. This is done in the firmware.

hi
will this version from your repository control an real machine with ethercat servos?
it already works with linuxcnc 2.9.3, its a cutting machine with XYA axis, A is tangential to the path. today it has very jerky moves as linuxcnc doesnt blend rotary axis. i would like to test the blend features you developed. in the previous videos there was an tool direction that i could use to control the tangencial axis, is this avaliable in this version?