Advanced Search

Search by Keyword Keywords:

Search Options

Find Posts from

Sort Results by

Search at a specific date

Jump to Result Number

Search in Categories Also search in sub-categories

Search Results (Searched for: )

DonatasO
DonatasO

17 May 2025 12:21 - 17 May 2025 12:33

G53 not ignoring tool length offset after a Python M6 remap was created by DonatasO

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!

Issuing EMC_TASK_SET_MODE --      ( +504,+24,    +6,    +3,)
NML_INTERP_LIST(0x55561aff7b10)::clear(): discarding 0 items
NML_INTERP_LIST(0x55561aff7b10)::append(nml_msg_ptr{size=24,type=EMC_TASK_PLAN_SYNCH}) : list_size=1, line_number=0
emcTaskPlanSynch() returned 0
NML_INTERP_LIST(0x55561aff7b10)::get(): {size=24, type=EMC_TASK_PLAN_SYNCH}, list_size=0
emcTaskPlanLevel() returned 0
Issuing EMC_TASK_PLAN_SYNCH --      ( +516,+24,    +0,)
emcTaskPlanSynch() returned 0
Issuing EMC_TASK_PLAN_EXECUTE --      ( +509,+280,    +7,t6\032m6\n,)
emcTaskPlanLevel() returned 0
NML_INTERP_LIST(0x55561aff7b10)::append(nml_msg_ptr{size=280,type=EMC_OPERATOR_DISPLAY}) : list_size=1, line_number=0
NML_INTERP_LIST(0x55561aff7b10)::append(nml_msg_ptr{size=24,type=EMC_TOOL_PREPARE}) : list_size=2, line_number=0
NML_INTERP_LIST(0x55561aff7b10)::append(nml_msg_ptr{size=24,type=EMC_TOOL_SET_NUMBER}) : list_size=3, line_number=0
emcTaskPlanExecute(t6 m6
) returned 2
emcTaskPlanLevel() returned 1
emcTaskPlanSetWait() called
NML_INTERP_LIST(0x55561aff7b10)::append(nml_msg_ptr{size=24,type=EMC_TASK_PLAN_SYNCH}) : list_size=4, line_number=0
NML_INTERP_LIST(0x55561aff7b10)::get(): {size=280, type=EMC_OPERATOR_DISPLAY}, list_size=3
emcTaskPlanLevel() returned 1
Issuing EMC_OPERATOR_DISPLAY --      (   +13,+280,    +0,    +0,\032in\032prepare\032tool=6.000000\032pocket=6.000000,)
NML_INTERP_LIST(0x55561aff7b10)::get(): {size=24, type=EMC_TOOL_PREPARE}, list_size=2
emcTaskPlanLevel() returned 1
Issuing EMC_TOOL_PREPARE --      ( +1104,+24,    +0,    +6,)
NML_INTERP_LIST(0x55561aff7b10)::get(): {size=24, type=EMC_TOOL_SET_NUMBER}, list_size=1
emcTaskPlanLevel() returned 1
Issuing EMC_TOOL_SET_NUMBER --      ( +1109,+24,    +0,    +6,)
NML_INTERP_LIST(0x55561aff7b10)::get(): {size=24, type=EMC_TASK_PLAN_SYNCH}, list_size=0
emcTaskPlanLevel() returned 1
Issuing EMC_TASK_PLAN_SYNCH --      ( +516,+24,    +0,)
emcTaskPlanSynch() returned 0
emcTaskPlanClearWait() called
NML_INTERP_LIST(0x55561aff7b10)::append(nml_msg_ptr{size=280,type=EMC_TASK_PLAN_EXECUTE}) : list_size=1, line_number=0
NML_INTERP_LIST(0x55561aff7b10)::get(): {size=280, type=EMC_TASK_PLAN_EXECUTE}, list_size=0
emcTaskPlanLevel() returned 1
Issuing EMC_TASK_PLAN_EXECUTE --      ( +509,+280,    +0,\255,)
emcTaskPlanLevel() returned 1
NML_INTERP_LIST(0x55561aff7b10)::append(nml_msg_ptr{size=168,type=EMC_TRAJ_SET_OFFSET}) : list_size=1, line_number=0
emcTaskPlanExecute((null)) returned 0
emcTaskPlanLevel() returned 0
NML_INTERP_LIST(0x55561aff7b10)::get(): {size=168, type=EMC_TRAJ_SET_OFFSET}, list_size=0
emcTaskPlanLevel() returned 0
Issuing EMC_TRAJ_SET_OFFSET --      ( +223,+168,    +0,0.000000,0.000000,-50.000000,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000,)
mdi_execute_hook: MDI command 't6 m6
' done (remaining: 0)
tool_result(id=6, xoffset=0.0, yoffset=0.0, zoffset=-50.0, aoffset=0.0, boffset=0.0, coffset=0.0, uoffset=0.0, voffset=0.0, woffset=0.0, diameter=6.0, frontangle=0.0, backangle=0.0, orientation=0)

G53 G0 Z0

Warning: Spoiler!

G49

Warning: Spoiler!

G43

Warning: Spoiler!

G53 G0 Z0

Warning: Spoiler!

17 May 2025 11:54

Replied by JT on topic linux cnc keeps bending shortcutting to the next line.

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

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

Hakan
Hakan

17 May 2025 11:14

Replied by Hakan on topic el5151 reseting counts

el5151 reseting counts

Category: EtherCAT

Yes that would be a problem. Linuxcnc asks the encoder to reset the counter to zero and count continuously up/down from there. I don't know any details of this encoder so I guess it is reading the manual to find how that can be done. Luckily Beckhoff has ok manuals.
For velocity you can try the ddt hal function, generate velocity as the derivative of the position. Taking the encoder pin values is limited by the servo loop time and EtherCAT cycle time, anything faster than some hundred Hz will fail.

Displaying 16051 - 16055 out of 16055 results.

Time to create page: 0.497 seconds

All Categories
LinuxCNC
- LinuxCNC Announcements
- General LinuxCNC Questions
- Installing LinuxCNC
- LinuxCNC Documents
Configuring LinuxCNC
- Configuration Tools
- - StepConf Wizard
- - PnCConf Wizard
- Basic Configuration
- Advanced Configuration
- - ClassicLadder
- - EtherCAT
- HAL
- - HAL Examples
User Interfaces
- AXIS
- Gmoccapy
- Plasmac
- pyVCP
- GladeVCP
- Other User Interfaces
- - PathPilot
- - QtPyVCP
- - Flex GUI
- Qtvcp
GCode and Part Programs
- G&M Codes
- O Codes (subroutines) and NGCGUI
- - Mill Library
- - Lathe Library
- - Plasma Library
- CAD CAM
- - Post Processors
- - - Fusion 360
- - - MasterCAM
- - - MecSoft
- - NativeCAM
Hardware & Machines
- Computers and Hardware
- Driver Boards
- CNC Machines
- - Milling Machines
- - Turning
- - Plasma & Laser
- Pick and Place
- Additive Manufacturing
Other Stuff
- Show Your Stuff
- Forum Questions
- User Exchange
- Off Topic and Test Posts
- - BeagleBone
International LinuxCNC Users
- Français
- Español
- Deutsch
- Other Languages
- - Russian
- - Polski