On 3/12/24 16:35, gene heskett wrote:
On 3/12/24 13:49, gene heskett wrote:
On 3/11/24 12:31, andy pugh wrote:
On Mon, 11 Mar 2024 at 00:11, gene heskett <ghesk...@shentel.net> wrote:
Since no one has commented I updated to todays build, no help there.
lcnc refuses to move the machine by my code more than once per startup.
It sounds like the code leaves a parameter in a state that causes the
code to skip.
If it isn't error-ing then it is probably running to completion, but
not doing what you expect.
Try running through it in single-block mode.
I got tired of looking at all the screaming qt was doing trying to get
my camera to work, so I commented it out. Another and2 fixed the
false atspeed indicator saying its at speed when stopped. But what I
set for MIN_VELOCITY in the spindle_0 section of the ini has no
effect. I still have to click the + button to start the spindle at
about 105 revs. So now its warmed up, I'll go play.
Cheers, Gene Heskett, CET.
More of the same, might be a little more stable w/o all the qt screaming.
It will Single Step to the end of the first
hole while I fine tune some of the presets for the first hole, And as
the center of x or y is found. I mam updating the 3 vars that the hole
finder routine uses to recenter before starting the next measurement.
But my run once per restart of linuxcnc continues. It will not restart
the spindle on the 2nd try. This "first move" is in the o<z_check> sub.
The s<_searck_revs> command is a few lines prior to the M4, works the
first time every time, very occasionally works 2nd time.
When I know it should have spun up the spindle to around 1000 revs to
find the linear rails top, the spindle hasn't turned and the atspd led
is still red. No debug statements elsewhere in the code ever exec.
No response at all to the step button but the stop button works fine.
All indications are that atspeed is the culprit. I can debug the
#<_search_revs> var, and it reads just fine. But an M4 on the mdi line
does zip.
I sure could use a clue. Latest, probably messy code attached.
Thanks Andy. Take care & stay well.
I found it, I think. When it fails, the speed signal value is being fed
to pid.s.commamd, but pid.s.enable isn't being switched on, and I've
located it in my hal, but I'm not visualizing it well since its nearly
10 yo code I've not modded since. Tracing backwards I'm getting lost in
how I check the boot module for the pico-pwm-servo for an output of 5 at
the state pin. I originally did a servo reboot at every spindle start.
Its possible that I have lost the trigger signal in my mods to do the
spindle turnaround as quick as I am. The idea is to delay the pid's
output until the servo had been booted. I'll find it but its going to
take more coffee. Which I've got to make. So call the St Bernards back
in, its not LCNC's fault. It's mine and I'll own it. Thanks Andy.
Cheers, Gene Heskett, CET.
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
