Search:

Even better, since the various cases are mutually exclusive, would be
o1 if [#5400 EQ 516]
G52 X 1.2129 Y -1.0493 Z 0.4972 (Position Tool #516)
o1 elseif [#5400 EQ 502]
G52 X 1.0592 Y...

Each if needs a matching endif, where oh-numbers are used for the matching. Your code should be something like

o1 if [#5400 EQ 516]
G52 X 1.2129 Y -1.0493 Z 0.4972 (Position Tool #516)
o1...

I glanced at toplevel.py, but I didn't pay attention to the ATC-related stuff. I'll leave that digging to people with ATCs.

OK, I've finally got around to looking through Tormach's python code. The only relevant file seems to be
~/tmc/configs/common/namedparameters.py.

Possibly other parameters are defined...

I read it, but I haven't yet had a chance to fire up my 770 to check out those files.

Yes; read posts #6 & #7 above. I was looking for PathPilot-specific ones, like _spindle_rpm_max , _spindle_rpm_min, _pi, and _epoch_time

Thanks. _pi will be useful.

Right. What I said was that I have no other LinuxCNC engine.

I discovered #<_spindle_rpm_min> and #<_spindle_rpm_min> inside a .NGC program that appeared on my 770 after a PathPilot upgrade, but I don't know how that bears on whether those parameters are...

I wasn't hoping for a complete list. I thought that members of the forum could contribute whatever parameters they'd happened upon, and that the list could grow here over time.

@Mountaindew said
Does the Linux cnc website not detail named parameters?


It does, but there are some not in the lists in Sections 3.4 & 3.5 of G Code Overview

I've assumed that those...

Can we use this thread to build such a list? The only ones (not in the PP manual or in the G Code Overview) I know about are

the spindle-speed limits (#<_spindle_rpm_min> and...

Where is a list of the PathPilot named parameters?

Is there a maintained list of PathPilot's built-in named parameters, more inclusive than the one at G Code Overview?

I had been maintaining two different warm-up routines for my 770, one to use...

Mine is in the attached zip file. It is big & wordy, because it is part of a big set of subroutines.

My experience is like that of @kstrauss and @popspipes.

I have had some problems, and Tormach has solved them promptly. For example, when my 770 first arrived, I realized that by a few...

It may be worthwhile to expand on this:

Values that gCode can set, but cannot read. These can't therefore be saved, temporarily changed (say, in a subroutine), and then restored. The M80/M81...

I looked through that link and found nothing useful. Someone in one comment said he thought that Python-to-gCode communication wasn't actually possible, but all I take from that comment is that it...

response to #25
I'm still missing something. Among the lines generated by admin halcmd show there are a few whose interpretation would seem to be straightforward. For example, there are lines that...

I'd be happy to do it, but there's various necessary lore that I have no pointers to. In particular, where can I find out about (a) HAL pins and (b) the namespace in which you found...

I had never heard of those M codes before; they are not documented by Tormach, and a cursory Web search turns up some unrelated uses of them in some gCode implementations. Should we rely on Tormach...

My meta-wish for PathPilot is that any status known to the engine should be accessible in gCode.

For example, PathPilot doesn't automatically know when I have shifted the belt to change my...

It depends what you call clumsy. Here is the subroutine that I've used for drilling for the past few years. Its logic should be evident, but I'll help anyone who has questions.


o <hole_drill>...

Ken
There's more to Step 6 than that caution, because (see post #1 of this thread) I'd been through all the steps of the process before (but omitting the unplugging), and I then couldn't escape...

Various experiments had got me to the point where turning power on would give me the splash screen, a pause, and then the screen that says it's safe to turn the power off again. This loop appeared...

I was running 2.7 without problems for a week or so before the boot failure yesterday, so the 2.7 Mesa firmware upgrade was at least initially OK. That recent upgrade might be relevant, if it could...

Ctl-Alt-X (held during boot or pressed at freeze) toggles between the splash screen and the text torrent. It never gets me to a command prompt.

I've tried the various combinations held down through booting, or pressed from the frozen splash screen, Esc triggers a text torrent that is similar or identical to that elicited by Alt-X. It is in...

Shift-Alt doesn't do it; neither does Shift-Ctrl or Ctrl-Alt.

Alt-X, entered at the frozen splash screen, triggers a text torrent but does not lead anywhere useful.

Thanks; I'll try that. Unfortunately, I didn't take note of what caused the system to come up with that 3-choice text screen. Now, it goes straight to the splash-screen freeze every time. Are...