A one-bit error ...
Phil Pilgrim (PhiPi)
Posts: 23,514
... probably from a cosmic particle, but a 26-hour debug turnaround time:
news.discovery.com/space/nasa-finds-cause-of-voyager-glitch.html
And I used to think that waiting for windowed EEPROMS to erase before they could be reprogrammed was bad!
-Phil
news.discovery.com/space/nasa-finds-cause-of-voyager-glitch.html
And I used to think that waiting for windowed EEPROMS to erase before they could be reprogrammed was bad!
-Phil
Comments
Many years ago I was accosted by the corporate IT department who were hell-bent on "taking over" the administration of the PLC's and other controllers on the manufacturing equipment.
This same guy could not understand how "just a single bit" being wrong could have any effect on the machinery involved.
Thankfully, cooler heads prevailed and the electrical guys stayed in control.
Cheers,
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Tom Sisk
http://www.siskconsult.com
·
Application dependent, I have realized the value (no pun) of finding a 'fractional bit value' or bias of the LSB rather than truncation.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Beau Schwabe
IC Layout Engineer
Parallax, Inc.
If I understand you correctly, what you are saying is that sometimes rocket science should be left to rocket scientists?
Rich
I'm sorry at this bias juncture I need more bits to give a valid deterministic result.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Beau Schwabe
IC Layout Engineer
Parallax, Inc.
- wow
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- Rick
"Hello, IT support? Yeah, my ping has suddenly blown out to 26 hours. It makes my ssh sessions hell"
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
"Are you suggesting coconuts migrate?"
It gets even uglier if you start expanding to "compliance".· Who keeps the sofware licenses and media?· The guys who actually "use" it, or the guys responsible for answering the questions from BSA and/or the US Marshals?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
John R.
Click here to see my Nomad Build Log
-Phil
Toyota has been quietly "debugging" (below the radar) their one-bit glitch for about 26 months now. Of course, that bit is the accelerator control, full off or full on...
What a difference a bit makes!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·"If you build it, they will come."
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Beau Schwabe
IC Layout Engineer
Parallax, Inc.
Yes, that's true. But the S/N is going to be so low in this case that a fast baud rate is just not practical for error-free comms. If it's more than a few bps, I'd be very surprised.
-Phil
True, the number of samples required just to detect the presence or non-presence of a signal will kill the throughput (See the Audio Spectrum analyzer I put together <-- A similar technique is used to increase the signal to noise ratio in space, only in a form similar to spread spectrum using multiple frequency bands.)
http://forums.parallax.com/showthread.php?p=663985
... Still though, you have to admit, this 'bit' error in the memory screams that it was human error and they are trying to make an excuse for it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Beau Schwabe
IC Layout Engineer
Parallax, Inc.
voyager.jpl.nasa.gov/spacecraft/index.html
Uplink rate is 16 bits per second, downlink at 160 bits/sec for most, 1.4 kbit/sec for some data. The radios operate at 8 GHz, Voyager itself has a 3.7 meter dish and the Earthside dish is 34 meters. Voyager's transmitter puts out 23 watts.
13hrs away at light speed.
It would be interesting to see what sort of signal is
sent back to the Earth from Voyager. I would guess a simple
system of turning the transmitter on/off and making slow pulses
to form a code. Must be very very slow. Data rate up to the
craft might be faster since they could generate a huge signal
going that direction.
And I thought wifi connections from a few miles away were exciting.
May we all end up in low-pressure positions as technically significant and rewarding!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·"If you build it, they will come."