Advanced Search

I have the latest version. Post the files, I'd love to try it out.

Why if I want Run-from-line It make all the tool changes up to the starting point?   
Linuxcnc 2.9.2
 

github.com/LinuxCNC/linuxcnc/issues/2966

Yes, I can see the encoder data in the show hal congratulations menu
Can you explain in detail how to do this?

Except physical and soft limit switches
a usable function will be to set a list of safe areas in ini file. These areas will be unreachable so g code interpreter of mdi/auto must filter the comands that reach these areas in cartesian space.

Yes ,GRBL is famous ,but not very suitable for my situation .I 'll develop a mathine with both lathe and 4 axis milling ,so GRBL board not completely satisfied

I'm looking for free cam software / g code generators for up to 5 axes cnc that works with linux cnc on a raspberry pi 5 for free or under $100. 

When you pick up the last pushed work (your layout) then let me know I'll post some files to try.

I can add INI defaults for rapid and max override.

Thanks for the explanation. I'll try this and report back.

I received the following reply from Marcus Freimanis. I believe he's the designer. Based on this information I believe the following 110% values should be the g540 defaults.

DIRSETUP   = 220
DIRHOLD    = 220
STEPLEN    = 1100
STEPSPACE  = 2200

---

Thank you for contacting Geckodrive technical support. I apologize for missing your email when it first came in.                 There is zero advantage to a much longer signal being sent; the G540 will only pay attention to the minimum timing (e.g.: the first 2uS of a 10mS signal, essentially wasting 9.998mS). If it is six-in-one and half-dozen in the other it is always wise to err on the side of a longer signal as there is no explicit downside as long as you can output the frequency you need with that pulse timing.                 The only reason you would NEED a very specific and very short signal would be if you were driving the motor to run at a high step pulse frequency, which would result in what would likely be a speed beyond the stall speed of the motor. A safety margin of 10% will take into account component tolerances across multiple devices.                 The timing on all revisions is identical and they all use the same circuit, with an HCPL2531 optoisolator.                 Again, my apologies for missing your email! Marcus Freimanis Geckodrive, Inc.1540 S Grand AveSanta Ana, CA 92705 P: (714) 832-8874F: (714) 832-8082  www.geckodrive.com

You will need another custom python file that runs later. The file name can be anything you wish and it is named in the ini file as [DISPLAY]USER_COMMAND_FILE = 

linuxcnc.org/docs/devel/html/plasma/qtpl...#_custom_python_code


 

Glad that it worked for you.

I am also looking for a way to touch-off without using the keyboard.
I'm trying to build a remote pendant and want a button for touch-off.
I'm not using a USB/keyboard interface for my pendant, so I need to go thru HAL (I think).

I have looked at the previous reply, and don't really understand it. I am unfamiliar with python. I'm hoping to find a way to work with halcmd.

When you add a tool, the tool table with this error is reset to zero. The Linuxcnc version is the latest, the error began to appear regularly weeks 2 ago

 

Hi all-

I'm trying to enable qtplasmac to allow a safe_height smaller than 0.75 inches. I followed the basic gist of the advice at forum.linuxcnc.org/plasma-laser/51568-in...xcnc?start=10#297618 which suggests something like the following in a file named qtplasmac_custom.py in the config directory:with my specific line in the qtplasmac_custom.py file being:
I have customized a label in the same qtplasmac_custom.py file, so I think that shows that the qtplasmac_custom.py file is being processed via github.com/LinuxCNC/linuxcnc/blob/56e137...smac_handler.py#L365.

However, I see that the self.set_spinbox_parameters() call happens in that same method but later:

github.com/LinuxCNC/linuxcnc/blob/56e137...smac_handler.py#L380

and it is in the the set_spinbox_parameters method where the regular setting of the safe_height setRange happens: self.w.safe_height.setRange(0.75, int(self.maxHeight))

github.com/LinuxCNC/linuxcnc/blob/56e137...mac_handler.py#L3238

I am wondering due to this call sequence if actually is possible to override the safe_height.setRange(), or if I'm doing something wrong.

Thanks!

Scott