Search Results (Searched for: )

  • onceloved
13 Jul 2026 21:43
Replied by onceloved on topic Every time I boot LinuxCNC, the Xg54 position reading increase 256
ini配置中注释或删除这行试试POSITION_FILE = position.txt
具体作用http://linuxcnc.org/docs/stable/html/config/ini-config.html#sub:ini:sec:traj
  • Ismacr63
13 Jul 2026 21:01
Replied by Ismacr63 on topic calling all probe basic lathe users!
As you probably know, I’ve been using Probe Basic Lathe for quite some time on a 200x400 mini-lathe.
  • Ismacr63
13 Jul 2026 20:59
Replied by Ismacr63 on topic Probe Basic widgets missing
Solved! In the old configuration, I had those 7 increments and it displayed correctly. I'm not sure if it's something related to the Trixie version. Thanks a lot!
  • Ismacr63
13 Jul 2026 20:23
Bearing replacement advice for PM-25MV mill (spindle and pulley shaft) was created by Ismacr63
I'm about to replace the bearings in my PM-25MV style mill. I've got a 1.8kW AC servo motor on the spindle that runs up to 4500 rpm.

Two questions:

For the bearings on the pulley shaft (the intermediate shaft that drives the spindle belt), should I go with C3 clearance or standard clearance?

What tapered roller bearings would you recommend for the spindle itself? 

Any advice from people who've already done this would be great. Thanks!
  • Lcvette
13 Jul 2026 20:12
Replied by Lcvette on topic Probe Basic widgets missing
too many jog increments no more than 4 should be used + jog
  • Ismacr63
13 Jul 2026 19:18
Probe Basic widgets missing was created by Ismacr63
I've been using Probe Basic for quite a while, both for my mill and lathe, always with a parallel port until now. I've just finished migrating both machines to Mesa.The mill is up and running fine, but the lathe is giving me some trouble after moving to Mesa and Debian Trixie. I'm running the dev version of Probe Basic, and the problem is that not all widgets show up.The sim config displays everything correctly, but as soon as I load my own config, some widgets are just missing. I've been around the Probe Basic file structure long enough to feel comfortable with it, but there's clearly something I'm overlooking.
  • PCW
13 Jul 2026 19:09
Replied by PCW on topic Ethernet connection to Mesa 7i76e disconnecting on its own after one minute
I should note that I have a HP EliteDesk 800 G1 that could never run Ethernet cards reliably
 for more than an hour or so UNTIL I upgraded the kernel to 7.x

It also requires:

disabling irq coalescing
isolcpus=3
and pinning the Ethernet IRQ to CPU 3

With these changes, I never get dropped packets even after months of uptime
with a PC used for compiling, youtube etc etc
  • scsmith1451
13 Jul 2026 17:54
Unable to Jog When HAL_ToggleBtn Active was created by scsmith1451
I have a standalone gladevcp panel that has a HAL_ToggleBtn configured and hooked up. The button activates an output that turns on my X/Y laser crosshair for locating program X/Y start. When the button is activated, the laser turns on as expected, however, I cannot jog while the button is active.  As soon as I deactivate the toggle button, I can jog.

I know it is not related to the laser itself as I have an override switch on my machine that allows me to turn the laser on. When the switch is on, I can jog just fine.

This issue occurs with both AXIS and GMOCCAPY interfaces, so it is something in the bowels of LCNC.  

Anyone have any insight on this issue or a workaround?
  • tuxcnc
13 Jul 2026 17:05 - 13 Jul 2026 17:08
Replied by tuxcnc on topic manual tool change with tool length probe
When you remap M6 to ngc, you can use standard M6 in it (I don't know why, but it works).
Bellow is code I use (no python or so, pure g-code), but I give no warranty, check carrefully.
Code:
O<tool-change> SUB (file tool-change.ngc) (--- header ---) (tuxcnc 2021) (manual tool change with automatic measurement) (replaces M6 g-code) (we assume that, toolsensor is permanently mounted) (and Z parameters of TOOL_CHANGE_POSITION and TOOLSENSOR ZPOS) (are maximum upper, otherwise you may get collision) (you must have the following in your INI file) (without semicolons and you can change parameters) ;[RS274NGC] ;FEATURES = 4 ;REMAP=M6 modalgroup=6 ngc=tool-change ;[EMCIO] ;TOOL_CHANGE_QUILL_UP = 1 ;TOOL_CHANGE_POSITION = 230 0 0 ;[TOOLSENSOR] ;XPOS = 192 ;YPOS = 0 ;ZPOS = 0 ;APOS = 0 ;BPOS = 0 ;CPOS = 0 ;UPOS = 0 ;VPOS = 0 ;WPOS = 0 ;FEED1 = 500 ;FEED2 = 100 ;TRAVEL =100 ;DISTANCE = 71 (--- end of header ---) #<tool> = #<_selected_tool> #<previous_tool> = #<_current_tool> O100 if [#<_task> EQ 0]    ( only run the subroutine in milltask interpreter )         (debug, Task ist Null) O100     return [999] O100 endif o200 IF [ #<tool> EQ 0 ]    ( check if tool zero selected and end routine ) (MSG, No Tool Selected ) O200     return [999] o200 ENDIF (---  store existing parameters  ---) #<g30x> = #5181 #<g30y> = #5182 #<g30z> = #5183 #<g30a> = #5184 #<g30b> = #5185 #<g30c> = #5186 #<g30u> = #5187 #<g30v> = #5188 #<g30w> = #5189 #<absolute> = #<_absolute>  (remember in local variable if G90 was set)  #<mist> = #<_mist>         (remember in local variable if M7 was set) #<feed> = #<_feed>         (remember feed value) #<flood> = #<_flood>        (remember in local variable if M8 was set) #<tool_offset> = #<_tool_offset> G49             ( cancel tool length compensation ) M9             ( coolant off ) M6                 ( run normal M6 operation ) G91             ( incremental distance mode ) (---   prepare g30     ----) #5181 = #<_ini[TOOLSENSOR]XPOS> #5182 = #<_ini[TOOLSENSOR]YPOS> #5183 = #<_ini[TOOLSENSOR]ZPOS> #5184 = #<_ini[TOOLSENSOR]APOS> #5185 = #<_ini[TOOLSENSOR]BPOS> #5186 = #<_ini[TOOLSENSOR]CPOS> #5187 = #<_ini[TOOLSENSOR]UPOS> #5188 = #<_ini[TOOLSENSOR]VPOS>  #5189 = #<_ini[TOOLSENSOR]WPOS> (--------------------------)                         G30 ( go to toolsensor ) #<PlaneOffset> = [#5183 - #5422]  ( get the current plane Z offset )     G38.2 Z-[#<_ini[TOOLSENSOR]TRAVEL>] F[#<_ini[TOOLSENSOR]FEED1>]  ( fast touch ) G38.4 Z1 F[#<_ini[TOOLSENSOR]FEED2>] G10 L1 P#<tool> Z-[-#<PlaneOffset> - #5063 - #<_ini[TOOLSENSOR]DISTANCE>] ( store offset in tooltable ) G30 ( go to safe position ) #<previous_tool> = #<tool> (--- restore parameters ---) #5181 = #<g30x> #5182 = #<g30y> #5183 = #<g30z> #5184 = #<g30a> #5185 = #<g30b> #5186 = #<g30c> #5187 = #<g30u> #5188 = #<g30v>  #5189 = #<g30w> O<restore_abs> if [#<absolute>]     G90 (restore only if it was set on entry:) O<restore_abs> endif O<restore_mist> if [#<mist>]     M7 (restore only if it was set on entry:) O<restore_mist> endif O<restore_flood> if [#<flood>]     M8 (restore only if it was set on entry:) O<restore_flood> endif O<restore_tool_offset> if [#<tool_offset>]     G43 (restore only if it was set on entry:) O<restore_tool_offset> endif F #<feed> (restore previous feed value) (--------------------------) O<tool-change> ENDSUB M2
  • tuxcnc
13 Jul 2026 16:52
Replied by tuxcnc on topic Recommended way to implement spindle enable conditions?
Lut5 is the best solution, especially when condition is type of "if a=true and b=false".
BTW. Beware situations when your spindle turns off when axis moved. It is more dengerous than continue when something fails.
  • tuxcnc
13 Jul 2026 16:39 - 13 Jul 2026 16:40
Replied by tuxcnc on topic Linux_Mint_22.1_LinuxCNC_2.10.iso
Mint is based on Ubuntu, Ubuntu is not Debian.
They are similar, but have important differences.
You can install some packages from Debian in Ubuntu (and vice versa), but not all, and in this case, soon or later, something become not works...
Making hybrid distro is bad way and prayer for troubles.
Linuxcnc is Debian based, so we have to stay with Debian, even if we dont't like them.
  • tommylight
13 Jul 2026 14:04
Replied by tommylight on topic Linux_Mint_22.1_LinuxCNC_2.10.iso
I just checked the NAS, i do not have the headers.
You can install a new RT kernel and headers, or older one, but do not use 6.1 as it had some nasty latency issues (no idea what exact version it was).
Should be 6.17 by now so give that a try.
  • spumco
13 Jul 2026 13:36
Replied by spumco on topic C axis milling cycles. Anyone written any?
An alternative to consider would be using polar interpolation combined with a 'standard' set of macros for XY-type milling.

As I mentioned earlier, polar interpolation is not in main-line LCNC but there is a working configuration available on the forums:

forum.linuxcnc.org/10-advanced-configura...oling?start=0#225787

Nojo's implementation works, but I think the hurdle for anyone else to use it is that Nojo hard-coded the live tool offsets to match his particular machine.  I'd think some editing of the comp would be required to make it a universal component/scheme.  (i.e. use the currently loaded tool offset, not a fixed offset)

If you found an existing 'conversational' configuration/GUI you liked, polar interpolation should permit programming using that conversational system.

However, it's understandable if you're not interested in falling down the comp file development rabbit-hole and just want some working macros.
  • Sascha H.
13 Jul 2026 12:28
Replied by Sascha H. on topic Recommended way to implement spindle enable conditions?
I used lut5 to check for various conditions.

Here is my HAL on Github:  github.com/shallerbach/endchen_rack_atc/...3f0/endchen.hal#L124
  • rodw
13 Jul 2026 11:14
Replied by rodw on topic Linux_Mint_22.1_LinuxCNC_2.10.iso
I might be wrong as I have only used Debian for years because Mint let me down a few years ago when Python 3 became mandatory for Linuxcnc and have not researched this for you.
I have a feeling that 6.13 is not a standard kernel used by Debian and therefore its derivatives. I believe that 6.12 was a release version.
So if it was not released, there won't be a readymade set of headers so you would need to compile the kernel to a Deb file which will output the headers as a Deb to install.

Debian is a much easier path. Just install the Cinamon desktop on install and you'll hardly miss Mint.
Displaying 2641 - 2655 out of 11911 results.
Time to create page: 0.264 seconds
Powered by Kunena Forum