2 Jul
2018
2 Jul
'18
2:33 p.m.
On Monday 02 July 2018 08:44:39 William Morder wrote:
I would not go so far as to say that, because I am forever twiddling the
lcnc configs. Adding a function or expanding the gui. But thats not the
os, its an app, so if I screw it up, the machine keeps on keeping on.
And I see the errors so I can fix it.
Going off-topic a bit:
For instance, when doing "rigid tapping" where you are threading a hole
by driving the tap into the hole at the same rate as the pitch of the
tap. You tell the code how deep to drive the tap, and when that depth is
reached, it reverses the spindle and unscrews it from the hole, staying
with the pitch as it backs out of the hole. But there is mechanical
inertia in the spindle drive that prevents an instant reversal.
Depending on the machine it may take 3 or 4 turns of the spindle to get
stopped, and 3 or 4 turns to get back to normal speed in reverse and
might be typical of a lathe turning a 40 lb chuck at 300 rpms. This
means the tap is driven further into the hole than intended, and a
broken tap if it hits the bottom of the hole. So I've added some stuff
to the lathes hal file to measure it and to show both turns of the
spindle and actual distance traveled, visible in the gui so by cutting
air, capturing those measurements and adjusting the code accordingly, a
broken tap from hitting the bottom of the hole should be a thing of the
past.
I intend to make that functional on the mill, but the initial capture is
in encoder counts, which unlike the lathe and the way I'm getting those
counts there, the mill has 2 separate scales to deal with depending on
the backgear status. So that code is a bit more complex and unfinished
just yet. But it will be in due time. Its also not as big a problem
since the mill can go from 2500 revs fwd, to 2500 revs in reverse, in a
fraction of a second. FWIW this is something that no pricy commercially
sold software can do.
On Monday 02 July 2018 03:07:16 Gene Heskett wrote:
Don't forget that the rock64 is NOT an armhf like the pi's, its a full
arm64. I don't think the compiler is quite ready for a full 64 bit 4
core arm. In any event, the login screen becomes locked if not logged in
within 10 seconds of its appearance. If the screen locker and its pw
requirement could be nuked, that would help since ones pw is no good
with the screen locker, once it kicks in, its power button time to get
back into it. I'd a lot druther it just turned the monitor off in 10 to
20 minutes of inactivity. Barring a prowler in the night, I am the only
one that will ever make new fingerprints on any of these keyboards here.
The paranoid security, as if all this was sitting on a kiosk in Grand
Central Station is extremely anti-productive. In a single user
environment, its very poor quality BS because it only grows resentment.
On Sunday 01 July 2018 21:48:27 William Morder
wrote:
Yup, I remember that hangup from running Debian with systemd. Once I
changed to Devuan, it no longer hangs on reboot. However, changing
over to Devuan is not necessarily smooth and easy - although some here
would disagree. I think it all depends on what one already has
installed.
On Sunday 01 July 2018 18:03:13 Gene Heskett
wrote:
It might be a good idea, and it may not. But the fact is that I
have 5 machines here still running wheezy and one jessie, which
wheezy is now officially EOL even for security stuff. Until the lcnc
crew have made up a jessie or stretch installer, So the likelyhood
of my playing with this is quite low.
The jessie install is quite stable, but I have a rock64 running
stretch that while its 20x faster than a pi, has problems with the
login screen that in 6+ months, has not been fixed, so there is no
way I could honestly say stretch is stable. Reboots after an update
are a try this and see if it works, then try that, each one taking a
full 10 second powerdown to get it to even try to reboot. On Sunday 01 July 2018 20:47:58 William Morder
wrote:
> On Sunday 01 July 2018 17:23:52 Gene Heskett wrote:
> > On Sunday 01 July 2018 19:58:34 Gene Heskett wrote:
> > > On Sunday 01 July 2018 19:16:01 dep wrote:
> > > > /home/dep/trinity/share/config/ etc....
> > >
> > > I have that file, its owned by me:me and is rw only for
> > > me. And contains:
> > > DVI-I-1=
> > > DefaultProfile=
> > > EnableICC=false
> > > HDMI-1=
> > > VGA-1=
> > >
> > > No clue what could have sneezed and screwed it up, but
> > > there it is.
> > >
> > > No clue of the effect of setting some of those options
> > > might be. And no manpage. So your guess is likely better
> > > than mine.
> >
> > Oh, I just found one thing that has not been fixed, I have
> > audio during boot until tdm starts after I log in. After
> > login, I still have to do an "alsactl restoreRETURN" before
> > I have any sound. Can this be fixed?
>
> I use ALSA, and it starts when I boot up.
>
> Have you messed with this toy?
> sudo sysv-rc-conf
That is not findable on this wheezy machine.
You should be able to get it by installing through apt:
sudo apt-get install sysv-rc-conf
Then I will send you a screenshot of my own run levels, or
somebody else can do so; or you can do some research on how to set
the run levels in sysv-rc-conf.
I seem to recall that you could make some of these changes through
the Trinity Control Center, but sysv-rc-conf is much easier, so
long as you are careful. A lot of things can slow down your
machine, because they are configured to run at startup when you
don't need them; while other things that you want, like your sound
system, might be disabled.
Bill Until you
finally get the ducks in order and a successful login can
be done. That same rock64 runs jessie perfectly from power
restoration to the next power failure. That I'd call stable.
> > > Be careful, if you haven't used that before; although I
> > > suspect that you know it. Don't make changes there unless you
> > > know what to do.
> > >
> > > Also, look in
> > > Trinity Control Center / Sound & Multimedia / Sound System
> > > Both parts,
> > > General / Hardware
> > > ought to be examined.
On the whole, I agree with your approach, I think, which seems to be:
take it slow, and don't mess with a working system. Even when my
system is not running quite perfectly, it's still better than one that
doesn't run at all, and time wasted with reinstallation. Right now I have a lot of little glitches that keep
building up, but I
have a feeling that most are somehow related, as I've never had them
before; and all are new since installing Devuan. So I mostly just keep
trying to trace the source (or sources) of these issues, waiting until
the inevitable reinstallation ... which could be another month or two.
That shouldn't be the case, Bill.
Bill
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>