Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

G-Code error when attempting to touchoff. #269

Closed
phillc54 opened this issue May 15, 2017 · 5 comments
Closed

G-Code error when attempting to touchoff. #269

phillc54 opened this issue May 15, 2017 · 5 comments
Assignees

Comments

@phillc54
Copy link
Collaborator

## Here are the steps I follow to reproduce the issue:

  1. run axis sim
  2. E-Stop off
  3. Power on
  4. press Home All
  5. press Touch Off
  6. press OK

## This is what I expected to happen:
Zero X axis in G54 coordinate system

## This is what happened instead:
The following error message:
G-Code error in axis.ngc
Near line 0 of
/home/phill/blah/blah/blah/axis.ngc:
Line with G10 does not have L1, L10, L11, L2, L20

## Information about my hardware and software:

  • Debian 7.11 (wheezy) in a VMware Fusion virtual machine:
  • 3.4-9-rtai-686-pae use Tcl_SetResult and Tcl_GetStringResult #1 SMP PREEMPT Debian 3.4.55-4linuxcnc
  • v2.8.0-pre1-3125-gd63aca6 as a rip build
  • AXIS gui
  • sim configs only - axis, lathe, historical_lathe, gantry, ldelta and rdelta all behave the same

Issue first appears in commit 001eb00, last working commit was 596363b.

@SebKuzminsky
Copy link
Collaborator

I confirm this happens on the tip of master (d63aca6).

@TurBoss
Copy link
Contributor

TurBoss commented May 15, 2017

I'm on master too and the "regular offset" button up to "touch off" causes this problem too

Linux cnc28 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc i686 GNU/Linux

The following error message:
G-Code error in axis.ngc
Near line 0 of
/path/to/file.ngc:
Line with G10 does not have L1, L10, L11, L2, L20

@jepler jepler self-assigned this May 15, 2017
@jepler
Copy link
Contributor

jepler commented May 15, 2017

@phillc54 thanks for the detailed bug report. based on this, it's pretty clear I introduced the problem, so I'll try to resolve it soon. For now you can probably just git revert the offending commit for local use.

@jepler
Copy link
Contributor

jepler commented May 15, 2017

The problem stems from how after G10 L2 ..., G10 appears in the list of "active gcodes" (stat.gcodes[2]); then the new code added at 001eb00 tries to issue a G10 code as a part of preview generation.

@cradek cradek closed this as completed in cb74ca8 May 15, 2017
@TurBoss
Copy link
Contributor

TurBoss commented May 15, 2017

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants