R
Rick C
Guest
On Thursday, March 26, 2020 at 11:10:17 PM UTC-4, Tom Del Rosso wrote:
I still haven't seen the definition of "booted" yet. That would seem to be a fairly important part of this.
One way to make sure the NUC is booted is for it to control power to everything else so it has to boot before anything else even turns on... for some values of "NUC is booted".
--
Rick C.
+ Get 1,000 miles of free Supercharging
+ Tesla referral code - https://ts.la/richard11209
mpm wrote:
It's a complex box. There are something like (30) different things
that power-up. The problem is a particular module has a nasty
tendency to glitch (with "improper power-up/down") but could
(allegedly) be completely eliminated if we can guarantee the NUC is
fully booted before all the shit happens in the box.
Sorry, it isn't 100% clear if the power controller is the NUC or
separate, or if you have access to run your own code on the NUC. (Maybe
it was clear to everyone but me.)
That said, we did discuss the idea of using an LMC567 tone decoder
and the speaker-out from the NUC. It's kudgey as all hell, but might
work a little better (i.e., less wasted time) than the timer
approach. IDK.
Relying on the Windows sound theme doesn't seem too reliable.
I still haven't seen the definition of "booted" yet. That would seem to be a fairly important part of this.
One way to make sure the NUC is booted is for it to control power to everything else so it has to boot before anything else even turns on... for some values of "NUC is booted".
--
Rick C.
+ Get 1,000 miles of free Supercharging
+ Tesla referral code - https://ts.la/richard11209