Advanced Search

@Otis,
Your link to github is not working, try posting it on a new post as editing usually messes things.
Thank you.

ah yes you have a slightly older version i did notice that after an edit and resolved it already, if you are apt installed a simple sudo apt update sudo apt upgrade will install the latest fixes, no need to reinstall everything.

Any conversational subroutine, such as Turning. I enter the parameters, and when I press the Turning button, nothing happens.

I always use the screen in full-screen mode, but if you look at the image I uploaded, the bottom part is cut off. This doesn’t happen in Probe Basic Mill.

Tomorrow I’m going to uninstall and reinstall the latest version and replace the files again.

glad you got it sorted out!!

what subroutines?

for reference i just installed the latest version on my test pc clean and everything is working as expected in all of the sims. which tells me the build is good. so this is likely a configuration error. but i would want some verification in the sims from you before we discount an installation error.

as for the screen size mode, probe basic is designed to be run full screen only to take advantage of every square mm or screen space for machine use. that will not change in the main branch as that is how i use my machines in their dedicated form and how i setup PB to be used. you could modify it but that will mean you are on your own or will have to remodify things any time you run an update.

In simulation mode, the screen looks the same, the subroutines don’t work, and I honestly haven’t tried the movement with the arrow keys.

Hallo,
und danke für die Antwort, es geht langsam aber stetig, ich habe jetzt als nächstes Problem das ich nicht weiß ob die Standardkonfiguration der Firmware nach dem Laden nicht bereits alle Variablen für alle Achsen plus Ein/Ausgänge enthält.
Meine Frage dazu ist, wenn die Achsen plus E/A im NVEM bereits vorhanden sind aber in der HAL nicht definiert, ist das ein Problem? Mir fehlt noch ein wenig das Verständnis zwischen der Firmware des NVEM und der HAL.
Ich wollte als nächsten Schritt einmal die Notauskette testen, daher wäre es interessant ob es da schon etwas konfiguriertes gibt.

Gruß
Mario

how about in sim mode?

Hello all, 

my goal is get my stepper motors to respond to movement commands.

Long time Machinist here, I am ok at computer science, but only self trained. I am new to linuxcnc, but not to Cnc I Have aquired a Gryphon gantry router with Leadshine MX4660. I have an older pc with 5v parallel port. I used stepconf to configure my control. I have downloaded and installed linuxcnc in october 2025, yet.with everything plugged in and up and running, my steppers are locked solid, and when i command a move, the control registers movement, but the machine remains stationary.

I have the bios set to EPP and the address is shows for the parallel port is 378h. the charge pump on the MX4660 is set to Off ( which I have read that counterintuitively means on the MX4660 that it is set to look for the 10khz signal ).I set the set/dir pins to the MX4660 manual using pin 2-9 as step/dir for x,y,z,tandem x. I have  tried a few configs with enable on pin 1, charge pump on pin 16, parport 0, parport 0x378, parport 378h, parport 0x378h, parport 378h. I have tried swapping the step/dir pins. i have not confirmed if my parallel port cable is good, I may test that here in a bit.

Seems like the control isn't communicating with the drivers. i am not sure how my hal file is configured for the parport settng.  I plan on posting my .ini and .hal files soon, next time I go out to the shop I will grab a copy of each.

I am just curious if there's something simple I have over looked, or even unaware of, and if anyone has any insight on this.

Thank you in advance if you have the time to help out.

The Probe Basic Lathe screen in full-screen mode is cut off and doesn’t display completely, which is a bit annoying.

Another issue I’m seeing is that the on-screen keys stop working after referencing the machine, and I have to home it again to get them working.
Also, the arrow keys only respond when clicking with the mouse in certain specific areas.To have the spindle rotate at a default speed of X RPM, I set, but without success. When I press the Forward button, it spins by default at a very low RPM.
Finally, for some reason, the subroutines don’t work at all.I’m running the latest update and have replaced the Probe Basic Lathe folders.
 

Hi,

we worked with the hal scope today.
 

Many thanks for the guide @rodw and the people in the forum!
Spend a some hours getting my setup online on the bench and it its now running only with minor issues that were a result from me not knowing what I was doing!And those were fixable with a bit of Forum reading and LLM help.

Could not be happier! 
Setup is:
- Beckhoff (EK1100 EtherCAT-Coupler EL1008 8K. Dig. In EL2008 8K. Dig. Out EL2624 4K. Relais Out EL3102 2K. Ana. In /-10V, DIFF EL4022 2Ch. Ana. Out 4-20mA, 12bit) for coolant/fans and also analog communication for the VFD with current feedback
- And a Stepperonline A6 Servo (now that i works, I will order the missing 2 servos)

Spend some time during the setup to take detailed notes and put them together here if someone plans on doing something simmilar: Github

Used the mpg today, sadly it crashed again. Loops = 10.

I actually opened an issue on github now over two years ago github.com/LinuxCNC/linuxcnc/issues/2237
No resolution. I never made a serious attempt to understand the code structure of the component.
Just looked at what was going on around the triggered assert() and made some more or less random changes.

Where is the blocking call? I'll see if I can do some ... tests.

Finished the mod for qtdragon, which adds HAL pin encoders for all sliders, jog on all axes, increments, and MPG.

Add HAL pins for XYZABC axis jog:

qtdragon.jog.axis.x.plus
qtdragon.jog.axis.x.minus
qtdragon.jog.axis.y.plus
qtdragon.jog.axis.y.minus
qtdragon.jog.axis.z.plus
qtdragon.jog.axis.z.minus
qtdragon.jog.axis.a.plus
qtdragon.jog.axis.a.minus
qtdragon.jog.axis.b.plus
qtdragon.jog.axis.b.minus
qtdragon.jog.axis.c.plus
qtdragon.jog.axis.c.minus

For example, following pins are available for feedrate slider:

qtdragon.feed.override.count-enable = HAL_BIT, IN must be TRUE to enable feedrate counts
qtdragon.feed.override.counts = HAL_S32, IN encoder input for change feed override
qtdragon.feed.override.btn-100 = HAL_BIT, IN reset to feed override to 100%
qtdragon.feed.override.step = HAL_S32, IN increase/decrease step as a % of the maximum value

For sliders JOG_RATE and ANGULAR_JOG add pins to toggle between fast and slow jogging:

qtdragon.jog.override-linear.turtle = HAL_BIT IN decrease jogging in 10 times
qtdragon.jog.override-linear.turtle-led = HAL_BIT, OUT indicated slow mode is on
qtdragon.jog.override-angular.turtle = HAL_BIT IN decrease angular jogging in 10 times
qtdragon.jog.override-angular.turtle-led = HAL_BIT, OUT indicated angular jogging slow mode is on

Add HAL pins for MPG:

qtdragon.mpg.mpg-enable = HAL_BIT, IN must be TRUE to enable MPG counts

Jog increments pins, used first 3 INCREMENTS from ini file:
qtdragon.mpg.mpg-inc.1 = HAL_BIT, IN
qtdragon.mpg.mpg-inc.2 = HAL_BIT, IN
qtdragon.mpg.mpg-inc.3 = HAL_BIT, IN

For angular axis used next pins, also first 3 value from ini:
qtdragon.mpg.mpg-angular-inc.1 = HAL_BIT, IN
qtdragon.mpg.mpg-angular-inc.2 = HAL_BIT, IN
qtdragon.mpg.mpg-angular-inc.3 = HAL_BIT, IN

Pins for axis selected:
qtdragon.mpg.axis.x = HAL_BIT, IN
qtdragon.mpg.axis.y = HAL_BIT, IN
qtdragon.mpg.axis.z = HAL_BIT, IN
qtdragon.mpg.axis.a = HAL_BIT, IN
qtdragon.mpg.axis.b = HAL_BIT, IN
qtdragon.mpg.axis.c = HAL_BIT, IN

MPG encoder pin:

qtdragon.mpg.encoder-count = HAL_S32, IN MPG encoder input

Add a pins to cycle change increments:
qtdragon.mpg.mpg-inc.cycle = HAL_BIT, IN
qtdragon.mpg.mpg-angular-inc.cycle = HAL_BIT, IN

Put this file into <YOUR CONFIG FOLDER>/qtvcp/screens/qtdragon_hd/. Tested on qtdragon_hd, but should be working on qtdragon too.

I think to that there are some mistakes what I have done.