Advanced Search

Forgive my silly questions, I downloaded 
(LinuxCNC 2.9.2  Debian 12 Bookworm PREEMPT-RT ISO )

and when I look at the one below it marked RTAI

(LinuxCNC 2.9.2 Debian 12 Bookworm RTAI)

There is no hyperlink to download it like there is with the PReempt one am I missing something? I have a list of the older builds is it one of those? sorry again for the dumb questions just super new and don't want to mess it up. Also when I'm actually in the bios selecting the OS to install am I clicking the one marked (live) or just the regular install, On the current set up I just ran the regular install because I assumed the LIVE would just be running the OS of the USB drive for testing? 

Thanks again, included photos of the pages I'm looking at.

I already have this in the ini file:

RS274NGC_STARTUP_CODE = G17 G21 G40 G49 G61 G80 G90 G94 G97 G98

The problem is, this isn't executed when turning the machine on in Gmoccapy.

In the ini filenotice the G64 P0.025
0.025 is the amount in mm the machine cad deviate from the original path.
Adjust accordingly if using inches.

for all those who know their way around a little better,
here is the rewrite from RIO.
Not all configurations are available, but the system offers a few improvements to the old one.

I think it's time for tests with the new one,
I won't be making any more major changes to it

github.com/multigcs/riocore
github.com/multigcs/riogui

Zu den halui.axis.l.plus / .minus gehört noch der pin 'halui.axis.jog-speed' mit dem wird die Verfahrgeschwindigkeit gesetzt.

opi5p@orangepi5-plus:~$ halcmd show param *.tmax
Parameters:
Owner Type  Dir Value     Name
36 s32  RW  965109          hm2_7i90.0.read.tmax
36 s32  RW  3890184        hm2_7i90.0.write.tmax
29 s32  RW  1459              motion-command-handler.tmax
29 s32  RW  11958            motion-controller.tmax
39 s32  RW  584                pid.s.do-pid-calcs.tmax
39 s32  RW  1458              pid.x.do-pid-calcs.tmax
39 s32  RW  583                pid.y.do-pid-calcs.tmax
39 s32  RW  583                pid.z.do-pid-calcs.tmax
30 s32  RW  4029890        servo-thread.tmax

This is the result of "halcmd show param *.tmax" command. is it mean that my spi doesn't support realtime? or I can make it better by manipulating the os kernel?

Have you fixed it yet?

Guten Morgen Gemeinde,
Ich habe gestern damit verbracht externe Taster mit Komponenten der Halui zu verbinden, unter anderem auch die Achs-Tasten, das hat soweit auch geklappt, allerdings sehe ich auf der Oberfläche keine Bewegung wenn ich die Taster drücke, aber wenn ich die Tasten auf der Bedienoberfläche drücke dann bewegt es sich. Das ganze mache ich zZ noch auf dem Schreibtisch bevor ich es an der Drehmaschine verbauen.

So sieht das ganze aus:
net taster-z-minus  halui.axis.z.minus  <=  hm2_7i92.0.7i76.0.0.input-18
net taster-z-plus  halui.axis.z.plus  <=  hm2_7i92.0.7i76.0.0.input-19
net taster-x-minus  halui.axis.x.minus <=  hm2_7i92.0.7i76.0.0.input-20
net taster-x-plus  halui.axis.x.plus <=  hm2_7i92.0.7i76.0.0.input-21

#net jog-x-pos      halui.axis.x.plus
#net jog-x-neg      halui.axis.x.minus
#net jog-z-pos      halui.axis.z.plus
#net jog-z-neg      halui.axis.z.minus

Die habe ich ausdokumentiert weil sonst Fehlermeldung

  

Wo liegt mein Fehler?

Danke und Gruß 
Olli

helical motion. g2/3 circle with a z component. normally you tell the post processor to turn that into lines cause not all controls handle helical motion.

If its based on a Asix AX99100 (which came up on google searches), you maybe able to read the chip, or the above command may identify it, the is thread my help, forum.linuxcnc.org/16-stepconf-wizard/46...-card-ax99100#245645

@Grotius do you mean similar to a boring operation where it's interpolation of xyz like a thread? 

What mpg are you using? And are you using an atc?

One thing you probably want to change is the following line in your ini file:INCREMENTS = .1in .05in .01in .005in .001in .0005in .0001in

To
INCREMENTS = JOG .01in .001in .0001in

Found a solution: in my main hal file, I took out everything that wasn't axis or spindle and moved it to post-gui at the end. Now the error is gone. I just forgot to check if it backplots and if the offset is checked. I'll check that tomorrow.

Typically you don't need a manufacturers driver if
the low level hardware is standard.

Does Linux detect the parallel port?

lspci | grep -i par may give a hint