Advanced Search

unknown wrote:

I believe that can implemented in a web browser via careful implementation of bookmarking.

+1

Oh yeah, forgot to add, modules 1631 and probably 1632 have data values ​​output to port 2^16, so you'll need a bitslice conversion, not individual bit values ​​for input/output in your *.hal file

I believe that can implemented in a web browser via careful implementation of bookmarking.

For the RPi I created a topic that has links to various solutions to issues with the RPi.

Or copying and pasting links to a local html file. One could even create a GitHub repo for this purpose, organising links of similar topics into folders.

Or even a simple database on one's home computer, which would give you the ability to search by keywords. Or you could get real fancy and use PHP to connect to the database and have a browser based solution GUI for searching and returning the results as a direct link.

Look the current version of the forum software has a barely usable editor, anyways this kind of feature would be best suggested to the authors of the forum software.

Start with the configuration with the lpt port, then make changes to the *.hal file linuxcnc, if there is no physical lpt, then just comment out the lines using it... Attached is xml for 1631 and aq0810 from amsamotion
 

I've tried to run your config. Firstly corrected

BASE_PERIOD = 1000000
SERVO_PERIOD = 5000000

to

BASE_PERIOD = 0
SERVO_PERIOD = 1000000

You config also seems to be setup for imperial yet using mm?

I can jog with that above correction without following errors.

For your DRV8825 have you added the micro stepping jumpers? The DRV8825 wont enable without this, which I tried on my SKR3EZ. I unfortunately killed my normal SKR3 so cannot test with that board.

This may sound dumb as I am no gcode expert, but is there a way to "push" the current gcode settings
and restore them later?

ini values can be changed using the 'ini.*' hal pins. Changes can be made while a program is running but will only become active after a queue buster command (eg M66 E0 L0) which will restart the motion planner with the updated ini values.

I have found that I often stumble across interesting topics while searching for info on the forum site that I would like to go back to at a future date.  It would be awesome if posts could be tagged and saved to a user's account list for easy retrieval in the future.  The list should be editable to remove old links that are no longer needed.

Kind Regard,

Big thanks Chris, that was a really quick fix from you!

Fixing the bug in the normal uses cases is what's most important as probing errors are not that common once you get used to the various probing functions.

The abort handling seems tricky to solve indeed. I went through the documentation in search for a solution. I was looking for a hook to detect when a program has been halted but I came up with nothing.

Maybe some of the more experienced LinuxCNC gurus here on the forum has some input on how this could be solved.

Any update?

thanks Royka for the kernel.
I rebuilt the system today with Armbian Trixie and rt-kernel 6.1.115. I couldn't get the 3D accelerator to work. I think something was not set when the kernel was created.
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 19.1.7, 128 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 25.0.7-2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5 (Compatibility Profile) Mesa 25.0.7-2
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.0.7-2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Linuxcnc 2.10 won't start.
~$ linuxcnc
LINUXCNC - 2.10.0~pre0
Machine configuration file is 'gmoccapy.ini'
Starting LinuxCNC...
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(REL): ./core_sim.hal
rtapi_task_start(): Operation not permitted
HAL_LIB: could not start task for thread base-thread: -1
MOTION: failed to create 100000 nsec base thread
MOTION: init_threads() failed
motmod: rtapi_app_main: Operation not permitted (-1)
./core_sim.hal:7: waitpid failed /usr/bin/rtapi_app motmod
./core_sim.hal:7: /usr/bin/rtapi_app exited without becoming ready
./core_sim.hal:7: insmod for motmod failed, returned -1
Shutting down and cleaning up LinuxCNC...
USRMOT: ERROR: command 30 timeout (seq: 1)
emcMotionInit: emcTrajInit failed
USRMOT: ERROR: command 3 timeout (seq: 2)
Note: Using POSIX realtime
LinuxCNC terminated with an error. 

What do you think?

In my gladevcp panel I have configured two buttons to set the jog rate. One to set to the lowest value that I use for positioning my crosshair laser, the other to set to the max value that I use. I have tried both ACTION.SET_JOG_RATE(rate) and GSTAT.set_jog_rate(rate), but neither affect the jog rate display in AXIS.  The documentation for GSTAT.set_jog_rate(rate) mentions that after setting the jog rate, the jograte-changed signal is emitted which I would expect to update the AXIS display but there is no feedback indicating that the rate has changed. Is this a known issue or am I doing something wrong?

FYI - I also have a combo box to select the current system offset system which does change the AXIS display after a new offset is selected, so I would expect these two functions to work the same.

Kind Regards,

glad you got it working. If you feel like sharing you could go to your cloned folder and post the output of:

Might help somebody in the future.

Hi! And.. success!!!!!!

I found some issues in my ngc!

Later i make a video and upload! Then i show how to get a working toolchanger with the carousel.comp!

I made 3 failures...
Debounce-Modul wrong CAP!
Timing placing in the ngc
Order of handle stuff in the ngc


I collect later everything and show it.

Thanks to andypugh to show the right way.

Its not so fast like original Emco but its everytime done a correct Toolchange!

As PCW mentioned those I/O should have some conditional motion safeties in hal, also anything critical that needs to stop immediately should also be wired to a power disconnect contactor to ensure absolute motion halting in the event of a estop. for mine my mushroom button halts both linuxcnc and all drives and motors. for the screen estop its just halting in software. this way i only press the danger mushroom if it is imperative everything must cease STAT!