Advanced Search

Mayby this could help
forum.linuxcnc.org/24-hal-components/53990-button-toggle

Hello,
I would like to add a hardware button for cooling, for example.
Currently, my *.hal entry looks like this:
This allows me to switch the coolant on and off via the GUI.

How can I add the hardware button (push button)?
I want to be able to continue switching it on and off in the GUI and see that the cooling is switched on. 

Thanks   

Well yesterday and this morning before work I was able to not only correct the wiring for the encoders which works now, but also figured out my issue with the 2x20 pin header wiring issue. I now realize a note I read on another document that the output is not alternating between the top and bottom row but is straight across the top then the bottom. Now that the wiring is squared away I just need to figure out the gearbox shifting logic to make the machine in theory functional. Well that and build the operating panel which the screen is on its way.

The mill has continued to work great but as I started to mill larger parts and use the full 50 cm z-height of the machine my existing chip cover proved to be inadequate with chips ending up all over my garage.

I had already increased the size of the polycarbonate chip guard once before because of this reason so this time I decided to do "the final chip guard". In all honesty a full enclosure would probably be the way to go but I don't have space for that which is why I'm sticking to chip guards that sit on the table instead.

To get started I ordered a large sheet of 4 mm polycarbonate.

 

I then started a very analog process of designing the actual size and shape using the cardboard box that the polycarbonate sheet was delivered in.

 

Once I hade the decided size and shape I purchased some aluminum extrusions which I cut slightly too long and then milled to size in order to get square corners.

 

 

 

While at it I decided to add some more polycarbonate on each side of the column to protect everything behind the machine from chips. They attach with magnets so that they can be removed just by pulling them off.

 

Here is how it looks all assembled.

 

 



The door took a bit of thought to figure out what would be the best solution so that it wouldn't be in the way for operations which don't require it to be in place.

In the end I decided to go with this design so that it's very easy to remove. When removed I just set it down on the floor in front of the machine leaning against the stand.







 

Yep too true.

What sort of tool changer do you want to build?
A rack toolchanger can work well with a gantry-style machine, but not so well on a knee mill, so the choice does depend to an extent on the base machine.

(and very much on if it's a mill or a lathe, you haven't said)

What spindle do you have? It's a lot easier to set up an ATC with a pneumatic drawbar, for example. (If it's any help I converted my threaded drawbar 1960s mill to a pneumatic pull-stud type drawbar, but was lucky that the mill had a fairly generous drawbar bore)

I have seen some fairly clever hacks to change tools on an ER-collet spindle, though, its not impossible.
hackaday.com/2016/06/20/hackaday-prize-e...omatic-tool-changer/
This one rather cleverly uses a circular move to apply more torque to the collet nut than the spindle can provide.

unknown wrote:

Yeah I could but I'd like to have a Trixe & Bookworm base image to work off. I'll get that going tomorrow (doesn't take too long)

One advantage of the Pi is that you can switch OS as simply as swapping the SD card. 

 

tommylight wrote:

Multi extruders are a real pain to setup and adjust, and this has to be done any time you change the nozzles.

The Prusa XL has load-cells in the extruders. You just take off the build-plate, put the calibration pin in the hole for that purpose and select "calibrate extruders" (or similar) and it taps each extruder in turn against the pin from 4 sides a few times (just like a probing macro with LinuxCNC). 

Admittedly it's not the cheapest of printers, but I don't regret buying it. 

rodw wrote:

Andy, if this is tested as working, can you build an official 2.9.7 release and put it on our repo for bookworm and Trixie?
temp folder does not sound very permanent 

I plan on doing so, but I will have to build all the variants by hand on a selection of VMs and RPis as Buildbot2 seems to be broken. It stalls at the end of the RIP builds: buildbot2.highlab.com/buildbot/#/grid
00-checkin has been running for 1 day and 15 hours at the moment, the previous two builds were killed by me from the IRC interface after similar times stalled. 

 

Led was easily solved with oneshot to qtplasmac.ohmic_led_in.
It works pretty well now. Time to wrap up this project.
The goal was ohmic sensing with the IPTM-60 (and IPTM-80) torch
without modification to the plasma cutter. I think it came out really nice.

A new box was made, needed to measure on what we call the ground lead.
 

The box tucked away
 

Schematics.


All schematics, code etc are available on github
github.com/MetalMusings/MyOwnEtherCATDevice
specifically the Kicad files for the THCLIP board are here
github.com/MetalMusings/MyOwnEtherCATDev...n/Cards/THCLIP/Kicad


 

bnet wrote:

So does this mean that the BLDC module doesn't output commutation before/during the startup indexing procedure? If commutation outputs are suppressed before index pulse is found I may have a problem. I was thinking that it could output them, even if they were off by a little, and hopefully it wouldn't jostle the motor around too much.

I think you are suggesting that you could supply "fake" commutation signals from LinuxCNC to the drive, and that might be enough to persuade the drive to start working?

That might actually work.

If the motor has little enough load on it at startup to magnetically align so that the "fake" commutation becomes true, just long enough for the drive to see the encoder index, then start running off that, you might be able to get things working.

I suppose it's worth a try, it's an hour's work and 3 wires.

So, Parallel Hat ist da, die Mesa Karte noch im Zulauf.

Komme gerade vom ersten Testlauf aus dem Keller - Grundsätzlich positiv, ein paar Dinge laufen aber noch nicht richtig:
- die X-Achse läuft immer nur in eine Richtung, egal welchen Pfeil ich auf der Tastatur drücke (Ich nehme an da passt der DIRX Pin nicht, der war am alten PC invertiert "setp parport.0.pin-03-out-invert 1")
- Alle 3 Achsen laufen zu schnell (gefühlt immer im Schnellgang den man sonst nur mit Shift+Pfeil aktiviert)
- Die Spindelsteuerung fehlt komplett in der Axis GUI

Ich nehme an da muss ich in den .hal und .ini Dateien nochmal nachbessern. Ich habe vieles von der alten Config übernommen, vermutlich gehört da noch was angepasst.

 
 
 

I realized that I forgot to mention which version and branch I'm running.

LinuxCNC: 2.9.4
ProbeBasic: stable branch

Hello,
i already created 4 Gladevcp buttons. X, Y, Z and Home all.

Now i need to know what do to activate them. I guess i need to change may machine.ini or hal.

Thanks

Noticed that the code tags in the editor completely mangled the stack traces, here they are in a more readable form.

Error 1:

[qtpyvcp.widgets.input_widgets.gcode_text_edit][INFO]  File encoding: ascii (gcode_text_edit.py:538)
[qtpyvcp.widgets.display_widgets.vtk_backplot.vtk_backplot][INFO] 

---

Draw time 1.4562861919403076 seconds --- (vtk_backplot.py:762)
[qtpyvcp.app.launcher][CRITICAL]  Unhandled exception in vtk_backplot.py line 849 (launcher.py:37)
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/qtpyvcp/widgets/display_widgets/vtk_backplot/vtk_backplot.py", line 849, in load_program
    point_01_pos = self.path_offset_start_point[prev_wcs_index]
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
KeyError: 1


Error 2:

[qtpyvcp.widgets.input_widgets.gcode_text_edit][INFO]  File encoding: ascii (gcode_text_edit.py:538)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7081, resource id: 8480708, major code: 40 (TranslateCoords), minor code: 0
[qtpyvcp.app.launcher][CRITICAL]  Unhandled exception in vtk_backplot.py line 1174 (launcher.py:37)
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/qtpyvcp/widgets/display_widgets/vtk_backplot/vtk_backplot.py", line 1174, in on_offset_table_changed
    self.rotate_and_translate()
  File "/usr/lib/python3/dist-packages/qtpyvcp/widgets/display_widgets/vtk_backplot/vtk_backplot.py", line 1289, in rotate_and_translate
    self.offset_change_start_actor[wcs_index].SetUserTransform(actor_transform)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
KeyError: 2