Advanced Search

I managed to get the addressing working for the spindle analogout but spindle doesn't work still. Keep plugging away.
Address is hm2_7i76e.0.7i77.0.3. I never thought of a three until I asked for a error report and it showed me the pins.

It's not only on Orange Pi, also on x86, both mainline Linux so it would be nice if you could set the title back again.

Changed the tittle to reflect the Orange PI in use.

I think the analog sserial channel will be 3

To check:

mesaflash --device 7i76e --addr [card_ip_address] --dbname2 7i77 --readhmid
 

I've compiled Linux 6.12 with Full real-time enabled, but somehow it's not detected as real-time by LinuxCNC. When I set the priority manually at RT via "sudo htop" and press I, the latency is low so I'm sure that it's compiled correctly.
Perhaps the detection method need to be changed?

Thanks for your help, I really appreciate it!

In the qt_auto_probe_tool.ngc script, I read the following:

The following workflow assumes using both a XYZ probe and a Z Toolsetter:
1 - Initial Setup: Before beginning the program, setup the Probe Tool as
having a zero z-offset in the tool table. (Non-zero tool lengths
for the probe tool can be made to work, but have multiple extra
steps required, and it is easy to have the tool offset interfere with
the remap coding and cause incorrect adjustments to your offsets.
This procedure assumes a zero length.)

It sounds as if the script documentation may be incorrect or perhaps previous codes changes have impacted the script?

Do you mean "G43 H99" ?? 
"G43.1" doesn't have an H parameter according to the online docs.

I have finally managed to get my 4 step/dir axis working, but still having trouble with the analog servo spindle drive. I get errors for addressing for the output
hm2_7i76e.0.7i77.0.1.analogout5 I have tried with .5. I have tried 7i77.0.2.
it keeps saying anything with that address doesn't exist,

  É possível conectar um codificador de alta frequência a esta placa nvem v5? para torno ou algo assim? orientação do fuso Não sei nada sobre esta placa

So I had some time to actually look at this:

#<_x>, #<_y>, #<_z> are relative positional values so your start position depends on whether you have g43 tool offset active or not.
The routine is set up to always return to the start position with G43 active so if your start position was stored in G49 then your spindle will always have to travel further up by the measured tool offset then where it started. This is why you are getting limit violation errors.

Just calling G43 is not the right way to go about it. If you have no tool set then the offset will just be zero and you'll be no better off.
Basically you need to start out by setting up your probe length in the tool table (ie Z offset for tool #99) and then do 'T99 M6 G43'  or, if your probe length has to be measured after each startup, you may want to use 'G43.1 H...'
linuxcnc.org/docs/html/gcode/g-code.html#gcode:g43

So really the same the others have already pointed out but it has taken me a long time to catch on.