Advanced Search

Could you could use some Halui MDI commands?

'P0' will set the currently active offsets, while 'P1','P2' ... will set the values of a particular offset system.
You could also stay in G54 and use different G52 offsets.

Wenn es bereits läuft, ist es natürlich wurscht.
Ich suche eher was fürs Bedienpanel und die Aliexpresskarte schien mir brauchbar. Habe sogar ein PDF bekommen, wo was zur Einrichtung steht, aber nichts von einem Bitfile o.Ä.
Wenn den Chinesen keiner testen will, werde ich mir wohl eine 7i73 kaufen. Hab gerade eben herausgefunden, dass Portugal doch in der EU ist und deswegen kein Zoll zu zahlen ist.

I think what you experienced is expected behaviour. Once an axis is homed, it can't be homed again unless its unhomed. I did notice recently in a axis sim that the unhomed menu was not enabled...

Hi,
i modified the  mesa-smartserial-device-template a little bit
and put it on a cheap ESP32 8ch-Relay board for extra Outputs.

i used platformio as buildsystem for easy use, i have also test the code on raspberry-pico,

github.com/multigcs/SmartSerial-ESP32RelayX8Board/tree/main

www.youtube.com/shorts/6ZKBH5xW8OQ

Relay-Board: www.amazon.de/dp/B0FNRH8QSN

Optional: www.amazon.de/TECNOIOT-Two-Way-Transfer-...tional/dp/B081J5R35N

Works fine with 7i92, but have still problems with 7c81 SmartSerial connector, not shure why,
maybe my pinout is wrong or problems with the TX_en stuff.


my Board with RS422 mod:
 

We have ESI files and many examples,
But, of course a driver is better than ever

I have added the Material Thickness parameter option for Ohmic Probe with Material Height.

The updated files are in the attached qtvcp folder. It needs to be placed into your working machine config directory.
Also the attached custom_postgui.hal must also be in your machine config folder.

The qtplasmac-imperial_material.cfg file has the material thickness added, it has the settings for a Hypertherm Powermax 85.

Snowgoer, I'm not sure if the custom_postgui file is the proper place to do the hal pin linking. If you have time to review the changes and add it to the source code, I would appreciate it. Otherwise I can try to figure out git and do a pull request.

For probe basic non of that is required, the existing rack atc is fully setup for configuring the atc in the gui once the correct ini settings and var file parameter numbers have been added. It uses random tool change and tracks pockets the same as random carousel. Looks for the first open pocket for storing the tool and finds the tool by its tool number and the parameter number its stored in. We made it super easy to setup with only a few user entries in the ui itself to determine where the rack is on the machine and the direction of ascending pocket order . Then the first pocket coordinate and the pocket spacing is entered and the drop off and pickup heights and clearance distance and its ready to rock and roll!

I wasn't good with my phrasing. I touch off G54, and explicitly set G10 L20 P1 X0 Y0 Z0 to force G54 (I may not need to do this? because it's what automatically happens when I touch off if I have the popup set to G54?), but don't ever use that except for touchoff/part location. (I *think* this is how I should be doing this?) Then I subsequently set up G10 P2, G10 P3, and so forth, and only machine at the work offsets referenced by those.

Is this for probe basic? If so the docs here have the information on how the rack atc should be setup in configs:

kcjengr.github.io/probe_basic/

On the Fujitsu also make sure that if it has the AMT feature
(common in corporate desktops), that it is disabled.

Also disable EEE and any PCIE power saving  in grub.

When you get to about the stepper motor section of pncconf check out "tandem" axis... like this:

 

Also, depending on your machine you may or may not need to invert the direction of one of the motors. There's a few ways to do that but this is one way:

 

attached are my config files. I have been trying for over a week to get the remap to work, I don't know what am I doing wrong. thank you!

I don't really know but have a look here:
github.com/LinuxCNC/linuxcnc/blob/bd96ca...tion/control.c#L2023

Thanks for your feedback. I'm not so worried about the first issue above as much as the second issue that I describe above.

The second problem has persisted for a long time and many have tried their luck at resolving it. I continue to see problems being discussed
that may be probable causes for this subroutine. 

Honestly, I think that the documentation around what I have described is perhaps incorrect or simply doesn't provide enough information
for the operator to make the subroutine work as expected. A good example of this is line number 31, the instructions indicate the following:

  31;  4 - Workpiece Measure: Use the button under the Probe Screens for "Probe Z height
  32 ;        of material:" this will set and display on the Probe Settings screen the
  33 ;        "Block Ht" = #<_hal[qtversaprobe.blockheight]> value in ABS coordinates.

What is missing is is there should be a "Jog to a coordinate" in order to measure the work piece height which will determine the "Block Ht" .

I am curious if there are any other steps involved that are not documented?