Advanced Search

Search Results (Searched for: )

  • Aciera
  • Aciera's Avatar
17 May 2025 15:10

G53 not ignoring tool length offset after a Python M6 remap

Category: Advanced Configuration

At least my understanding about emccanon.USE_TOOL_LENGTH_OFFSET() is that it's supposed to be the equivalent of G43, as it issues the same EMC_TRAJ_SET_OFFSET message. Apparently, it does not fully update the initial state.


note that 'G43' reads the tool-offset values from the tool table:
github.com/LinuxCNC/linuxcnc/blob/6c4303...erp_convert.cc#L6202

and calls emccanon.USE_TOOL_LENGTH_OFFSET() in line 6280:
  USE_TOOL_LENGTH_OFFSET(tool_offset);


BUT it also sets 'tool-offsets' in line 6299:
 settings->tool_offset = tool_offset;

So it seems that you will have to handle this in the remap.
  • Muftijaja
  • Muftijaja
17 May 2025 15:02

Two switches/sensors for tool length and 3d touching into motion-probe-in? Howto

Category: General LinuxCNC Questions

PCW, thanks a lot for the advice with the smaller resistor! I found one 2.2k with 1W in my boxes and used that today and voilá, it works as it should. Problem solved, I hope. (Don't know if I need noise reduction)Guys, I have no idea how to use sth like mux or mux_generic. I wouldn't even be able to use two inputs - but just out of curiosity , how would you do that in a HAL file if i would use an OR2:
 loadrt or2 count=1
net probe-in     <=  hm2_7i76e.0.7i76.0.0.input-08-not    
net probe-in     =>  motion.probe-input
and the second input hm2_7i76e.0.7i76.0.0.input-09 ? my programming scills are beginner level...
(Yes, I read the example in the LCNC HAL Examples to OR2 but I cannot convert that for my problem.)

Thanks and best regards!
Hanno

 
  • DonatasO
  • DonatasO
17 May 2025 14:53

G53 not ignoring tool length offset after a Python M6 remap

Category: Advanced Configuration

My guess would be that your change of tool-length is possibly not reflected in 'tool_offset.tran.z'.

You're right, it's not updated. Setting `self.tool_offset = pose` manually resolves the issue.

Am I missing some call to auto-update it, or does it have to be handled in the remap?
  • Roguish
  • Roguish's Avatar
17 May 2025 14:46
Replied by Roguish on topic QTDragon and DTG readout

QTDragon and DTG readout

Category: Qtvcp

thanks Chris.
I will try 'em both.
Buildbot2 has a new master deb yesterday.
looks like your changes are included...

* qtvcp -action tool button: add dro/dtg/large font controls
* qtvcp -gcode graphics: add dro on/off view signals
* qtvcp -qt5_graphics: add enable dro functions
* qtvcp -qt_action: fix dro view keyword, add DTG keyword
  • zz912
  • zz912's Avatar
17 May 2025 14:32
Replied by zz912 on topic Gmoccapy 3.5.0 - opinions needed

Gmoccapy 3.5.0 - opinions needed

Category: Gmoccapy

Hello Hans,

I tested 3.5.0
Is there any reason why "G-code properties" is also displayed in manual and mdi mode?
I think it's unnecessary, that "G-code properties" should be displayed in program mode. My opinion.


Wouldn't it be better to name "G-code properties" "Program properties"?
  • DonatasO
  • DonatasO
17 May 2025 14:31

G53 not ignoring tool length offset after a Python M6 remap

Category: Advanced Configuration

Thanks for the reply.

I can't use self.execute() as using INTERP_EXECUTE_FINISH is unavoidable in my procedure, and no MDI commands can be sent after it. I made it possible to switch between ATC and manual tool change (like drop tool, ask to insert a new one).

At least my understanding about emccanon.USE_TOOL_LENGTH_OFFSET() is that it's supposed to be the equivalent of G43, as it issues the same EMC_TRAJ_SET_OFFSET message. Apparently, it does not fully update the initial state.

Calling USE_TOOL_LENGTH_OFFSET() multiple times before moving does not resolve the problem.
  • Aciera
  • Aciera's Avatar
17 May 2025 13:44 - 17 May 2025 13:48

G53 not ignoring tool length offset after a Python M6 remap

Category: Advanced Configuration

Not sure but I think that 'emccanon.USE_TOOL_LENGTH_OFFSET(pose)'
might actually not be a good approach here.

 Note that 'G53' will actually use the 'tool_offset' values to calculate the target coordinates:

if(block->z_flag) {
            *pz = block->z_number - s->origin_offset_z - s->axis_offset_z - s->tool_offset.tran.z;
        } else {
            *pz = s->current_z;
        }
github.com/LinuxCNC/linuxcnc/blob/1b8867.../interp_find.cc#L197
My guess would be that your change of tool-length is possibly not reflected in 'tool_offset.tran.z'.

Generally I've become very cautious about using 'emccanon' commands to manipulate offset values  in remaps. I've had a similar issue setting work offsets this way.
I changed to using 'self.execute(..' instead (although that has its own pitfalls).

See the mentioned issue with work offsets:
forum.linuxcnc.org/20-g-code/48199-chang...-self-execute#264285
  • langdons
  • langdons
17 May 2025 13:32
Replied by langdons on topic Install Probe Basic

Install Probe Basic

Category: QtPyVCP

Apt dependency hell meets python's plethora of dependencies.

This is why I love SDKMan!

It's independent of the rest of the system, so you don't need to worry about annoyingness.

(But it only works with Java and its variants :( )
  • MarkoPolo
  • MarkoPolo
17 May 2025 13:12
Replied by MarkoPolo on topic Error in tool_offsetview.py

Error in tool_offsetview.py

Category: Qtvcp

I noticed that after starting it doesn't load the 'true' state
in radiobuttons .

I modified this logic a bit and now it works:
rabiobutton with "radiotrue/true/radiofalse/false'
checkbox with 'checktrue/checkfalse'

What do you think about this?
  • epineh
  • epineh
17 May 2025 13:05

LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

Category: Computers and Hardware

Hmm so I had checked the datasheet earlier, never actually looked at price and availability, I see what you mean.

The main idea was to save pins, they run out quickly on the tang nano. I guess the simplest solution is to step up to the spartan 6.
There is OctoQuad by DigitalChickenLabs for the pi pico that will do a similar thing for 8 encoders via I2C but as you say it would also require a new plugin.

Cheers.
Russell.
  • meister
  • meister
17 May 2025 12:47

LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

Category: Computers and Hardware

Hi Russell,
the LS7366 are no longer manufactured and you would have to write a new plugin. The ones you can still get are also quite expensive.

can't you just make a plug-in board (on the top) and route all the encoder pins to the top via pin headers?

Cheers, Olli
  • DonatasO
  • DonatasO
17 May 2025 12:21 - 17 May 2025 12:33

G53 not ignoring tool length offset after a Python M6 remap

Category: Advanced Configuration

Hi,

I'm writing an M6 remap in Python and encountered strange and dangerous behavior. After the first M6 call, G53 G0 takes into account the tool length offset, which should not be happening.
I'm unsure if I'm doing something wrong or if this is a bug in LinuxCNC. I hope you can help me clarify and resolve it.

LinuxCNC version: 2.9.4
UI (probably irrelevant): qtdragon_hd

This is a minimal working code to reproduce the issue:
# REMAP=M6 modalgroup=6 prolog=change_prolog python=is_this_a_bug epilog=change_epilog
def is_this_a_bug(self):
    if self.task == 0:  # ignore the preview interpreter
        return INTERP_OK

    emccanon.CHANGE_TOOL_NUMBER(self.selected_pocket)
    yield INTERP_EXECUTE_FINISH
    pose = EmcPose()
    pose.z = -50
    emccanon.USE_TOOL_LENGTH_OFFSET(pose)
    yield INTERP_OK

Steps to reproduce the issue:
  • Turn on and home the machine
  • T6 M6: the tool is loaded and offsets are set correctly.
  • G53 G0 Z0: the spindle rapids down to -50mm. This is not expected.
  • G49: cancel tool length compensation.
  • G43: enable tool length compensation
  • G53 G0 Z: the spindle rapids back up to zero. This is expected.
The issue can no longer be reproduced by issuing T6 M6, everything works correctly.

Attaching debug logs for each command:

T6 M6
Warning: Spoiler!


G53 G0 Z0
Warning: Spoiler!


G49
Warning: Spoiler!


G43
Warning: Spoiler!


G53 G0 Z0
Warning: Spoiler!
  • JT
  • JT's Avatar
17 May 2025 11:54

linux cnc keeps bending shortcutting to the next line.

Category: General LinuxCNC Questions

It's important to understand how Linuxcnc follows the programmed path.
linuxcnc.org/docs/stable/html/user/user-concepts.html

Note that G64 Blend Without Tolerance Mode is the default

A good preamble should always be the first line of any nc code program.
gnipsel.com/linuxcnc-old/g-code/gen01.html

JT
  • Sternfox
  • Sternfox
17 May 2025 11:38 - 17 May 2025 11:49
Mill as lathe with probebasic was created by Sternfox

Mill as lathe with probebasic

Category: QtPyVCP

Hey peeps.

I have A couple of questions. I want to use my mill as a cnc lathe.

Can I have pb turn and mill on seperate profiles? 
And can pb turn utilise 3 axis? I need the third to line up the work and to change tools which I will have in the vice.

The other option is using a custom post in fusion but im guessing thats way more complicated.

Thoughts? 

Much appreciated 
  • rodw
  • rodw's Avatar
17 May 2025 11:28
Replied by rodw on topic Linuxcnc wood lathe insufficient torque

Linuxcnc wood lathe insufficient torque

Category: General LinuxCNC Questions

48 volt power supply and DM542A stepper drivers would almost quadruple torque you have now with your same Nema 23's
Displaying 3706 - 3720 out of 24608 results.
Time to create page: 0.272 seconds
Powered by Kunena Forum