Advanced Search

Just showing some of the features in Flex GUI. The latest one in version 0.8.0 is MDI buttons.
gnipsel.com/linuxcnc/flexgui/controls.html#mdi-buttons

Also, I've added a feature for HAL buttons that can prevent them from being enabled if all the joints are not homed. This is useful if the HAL button runs a MDI command from the ini file. This is simply enabled by adding a Dynamic Property to the HAL button.
gnipsel.com/linuxcnc/flexgui/hal.html#homed-required

JT

There's no G64, but theres G61, which disables G64. It means "exact travel mode", i.e. hit every point exactly, no tolerance.

Ah, yes. I missed that.

The RS274NGC_STARTUP_CODE is executed on first start of LinuxCNC machine, but the G61 setting is lost after "soft-cycling" power following the steps I explained above.

I remember an issue where an estop reset the G64 setting but testing on version 2.9.2 seems to work just fine for me. G61 set in the STARTUP_CODE and neither estop nor machine ON/OFF change it.
What version of linuxcnc are you running?
 

1. How does HAL know where to find the subroutine, i.e. the path to the gcode z_touch?

in the [RS274NGC] section of your ini file add the location of your subroutines to the entry 'SUBROUTINE_PATH ='
linuxcnc.org/docs/html/config/ini-config.html

2. Does this go in custom_postgui.hal ?

Since the hal pins related to the button are created with the gui you need to add the corresponding HAL lines to the 'POSTGUI_HALFILE'

That should be all.

I have LinuxCNC 2.9.2 here and have never seen anything called "tandem items" in the Stepconf tool.

JT

Yes, the 7I80HDT is basically the same as the 7I80HD except that
it uses different firmware. You should be able to use a hal/ini file
set created for a 7I80HD on a 7I80HDT.

You should not change any hardware names as this will make it
much more likely to write the wrong firmware to the card.

I copied the ini files from a setup that was already working - but that PC has a built-in parallel port. So that should be the only difference between the two. I'm sure that caused the issue

This component should now allow selection of custom or standard homing as Dewey intended
github.com/rodw-au/cia402_homecomp

I finally got around to ordering some hardware to let me set up a homing test bench.
When it turns up, I have some work to do!

 Hello my friend, I haven't managed to solve it yet.
 Searching the forum, there were posts with links to some isos with other Linux distributions (Mint etc) x86/x32 with Linuxcnc newer than Debian Wheezy, but the links are down. Would anyone have a link to indicate where I can download these isos so I can test and see if it works?

I have figured out making a touchoff button on my Pyvcp panel. What I'm not sure about (despite hours of reading examples and looking at the 2.8 documentation) is how to make it actually do anything, which I think is a HAL question (let me know if I'm in the wrong place).

I'm using LinuxCNC/AXIS version 2.8.4-76 etc.
In Stepconf, there is a page for custom HAL commands, where I have entered (as the first and only MDI command):
   MDI_COMMAND = o<z_touch>call

1. How does HAL know where to find the subroutine, i.e. the path to the gcode z_touch?

Here is the xml corresponding to the touch off button:
        <button>
          <font>("Helvetica",14)</font>
          <width>3</width>
          <halpin>"z-zero"</halpin>
          <text>"Z"</text>
        </button>
I need to connect the 'z-zero' button to my touch off subroutine. I think I need a line like this:
net do-z-touchoff halui.mdi-command-00 <= pyvcp.z-zero

2. Does this go in custom_postgui.hal ?
3. Is that all I need?

I also want to use a spinbox to input the touch plate thickness, but I'll leave that question for the next round.

Thank you,
Steve
 

In Mesa CT 2.1.4 having a malformed ini file with no value is no longer an error it is ignored.

JT

M.adams9093 wrote:

Hello there, 
I have a problem with my Mesact 2.1.3  when I click to launch the tool, it gives me multiple errors with a message that says to remove and reinstall a new package. The problem I am currently having unable to delete it from the file manager. Every time I right-click on the.deb file and select remove, it won't do anything. my question is how can I delete it from the terminal so I can install the new version 2.1.4. 

thank you 
 

I have figured out what is causing the error you have an entry in the ini file with no value ie:
JT

I have a question regarding the 7i80HDT. Is it basically the same as the 7i80HD? For example the 7i80HD is supportet by the Mesa Configuration Tool and the 7i80HDT is not. I've seen somewhere the possibility to change the name of the card with setname. So if I would change the name it should work with Mesa CT?

Thanks,
Adrian

I haven't started tackling the JOG yet - except that I have turned on keyboard jogging (which didn't work properly with the VTK error). Jogging is probably next - and cutting the control panel. I am using an ATC, I think I have the toolchange pretty well worked out now. For an MPG I'm using a generic 100ppr mpg, and I have 3 encoders for spindle, rapid, and feedrate overrides. I haven't started tackling those on the machine yet.

Multicore on with ISOLCPU=1 did the trick I think we are all sweet now.

Base thread max jitter with 5 GLXgears was 7300 when I opened a youtube video and let it play for a bit it only got up to 12200
I think.... I HOPE that is good enough for my little milling machine. Thanks again for all your help guys

 

The Mesa Configuration Tool is here:
gnipsel.com/linuxcnc/mesact/index.html

With this tool you can read and flash a Mesa board, build your configuration files with no preset machine types.

If you just have an A axis Mesa CT will build that.

 

If you encounter an error use the issue tracker if you can or report it here.

JT