Advanced Search

Starting a new thread about this specific problem I'm having (I no longer have the original problem described here ). I have a routine I invoke from my VCP to vacuum the table. It's a bit of Python code that invokes an NC subroutine. You can see the Python code and NC routine on Github.

When I click the button on the VCP to run the routine, it starts, but then stops a few seconds into execution. Where and when it stops is random. However, the code completes execution without any indication of error. The Python code prints this to stdout:

It was suggested to insert lots of `M66 L0 E0` statements in the Gcode, but this strikes me as an unreliable way to ensure code is run. Surely `linuxcnc.command().wait_complete()` should be enough to ensure the code runs to completion?

I think you may be missing the subroutines folder from your machine's config directory. Many UI buttons are linked to such subroutines.

Hi Cakeslob,

The stepgen "PID" was adopted from the PID component. There is some auto tuning code in there but I've not looked closely at it.

github.com/LinuxCNC/linuxcnc/blob/master...hal/components/pid.c

Hello. I'm using probe basic on a parallel port milling machine.
On the one hand I have a problem with changing tools. I use the buttons on the interface but they don't do anything. If I enter the commands via MDI they change correctly.

I also have a problem with the 3D touch probe, basically it doesn't do anything when I try to calibrate it or do anything. In probe basic it shows true and false when I activate it by hand.

I'm attaching my configuration files in case it's of any use.

Hard to know with such limited info, so:
-does jogging the axis work properly or is it inverted also?
-does the nc file contain negative values for Z axis?
-does the machine have homing switch on Z axis?

You are getting the hang of it pretty good, so not "new user" anymore !

Actual debs are still here:
linuxcnc.org/dists/lucid/linuxcnc2.5/binary-i386/

Those are full images with LinuxCNC included, they have to be burned to a USB then installed on the PC.
-
If the old hal files do not have any special added functionality, they should work in new versions of LinuxCNC and there is an included wizard that does the modifications automatically when you first run the old configs.

I cut a bunch of parts out using "sudo ethtool -C enp0s25 rx-usecs 0" and I did not get a single error when cutting this time. Everything worked how it was supposed to now I just need it to be permanent.

I had a fairly simple .nc file that I ran successfully a couple weeks ago. Today, when i load it, the Z axis is inverted. What could I possibly have done to cause this?  Running LinuxCNC 2.9.2.  I haven't changed any of my .ini or config files. could I have received some update automatically that flipped my Z axis?

I will try
I uploaded 4 separate pages to this location and now all 4 separate pages are working without any problems.
The only problem now is that they are not permanent.
 

Thanks Chris!

hi...new user here...trying to add an axis..copied/pasted /edited...still something not right....not sure what I am doing wrong..

Thanks for any help

Rick

Sorry....just found the error...missed one b reference...Thanks!!!

Gentlemen, 
    I was wondering if someone could assist me with a tool height setter issue that I'm having.  

Problem description:
I'm trying to set the tool height by using the machine coordinate system.   I use the tool height sensor to measure the gauge height of the spindle.  I put the measured value in my AXYZ_Router.ini file.   Then I measured all my tools and subtracted the gauge height of the spindle from the INI file.   This set all the tool heights correctly as far as I could tell. 

Then I ran into a problem.   I reset my G54 to a different part on my router and then measured a tool again, and then measured the height of my tool.   The tool height is totally incorrect.   It's not based off of the G53 (Machine Coordinate System), it's using the current coordinate system.   
So, when I check the tool height after resetting my G54, I have to reset the spindle gauge height in the INI file. 
I tried to look up how to fix the issue, but it looks like most people aren't setting the tool height like I am.  

Any assistance is appreciated.  I have attached my current configuration. 

Here is my tool setter logic:

o<tool_setter> sub  
    
    ; Position at Tool Height sensor clearance position
    G53 G0 Z[#<_ini[AXIS_Z]MAX_LIMIT>-0.1] 
    G1 G53 Y#<_ini[HEIGHT_SENSOR_CLEARANCE]Y>     F#<_ini[HEIGHT_SENSOR]SEEK_VELOCITY>
    G1 G53 X#<_ini[HEIGHT_SENSOR_CLEARANCE]X>     F#<_ini[HEIGHT_SENSOR]SEEK_VELOCITY>

    ; Position above Tool Height sensor
    G53 G0 Z[#<_ini[AXIS_Z]MAX_LIMIT>-0.1] 
    G1 G53 Y#<_ini[HEIGHT_SENSOR]Y> F#<_ini[HEIGHT_SENSOR]SEEK_VELOCITY>
    G1 G53 X#<_ini[HEIGHT_SENSOR]X> F#<_ini[HEIGHT_SENSOR]SEEK_VELOCITY>

    ; Start of probing routine
    F#<_ini[HEIGHT_SENSOR]SEARCH_VELOCITY>
    G49
    G91

    ; Probe down in Z
    G38.2 Z-8

    ; Move  up till probe looses contact
    G38.4 Z0.1

    ; Probe slowly
    F#<_ini[HEIGHT_SENSOR]PROBE_VELOCITY>
    G38.2 Z-0.1

    (print, _current_Tool=#<_current_tool>)
    (print, 5063=#5063)
    (print, GaugeHeight=#<_ini[HEIGHT_SENSOR]GAUGE_HEIGHT>)
    ; Set the tool table value
    G10 L1 P#<_current_tool> Z[#5063 - #<_ini[HEIGHT_SENSOR]GAUGE_HEIGHT>]
    
    G90
    G53 G0 Z[#<_ini[AXIS_Z]MAX_LIMIT>-0.1]
    G1 G53 Y#<_ini[HEIGHT_SENSOR_CLEARANCE]Y> F#<_ini[HEIGHT_SENSOR]SEEK_VELOCITY>
    G1 G53 X#<_ini[HEIGHT_SENSOR_CLEARANCE]X> F#<_ini[HEIGHT_SENSOR]SEEK_VELOCITY>

    ;G43

o<tool_setter> endsub  
m2
 

Maybe I formulated the question badly.
The value of refClock, for example, at 5 ms, represents in ms the frequency of data update on the ethercat bus?
Increasing the value of RefClock, the speed of writing the positions by LNCNC in the drive, also increases or is this managed by the value appTimePeriod