Right on the page at adafruit there is a downloads link. This gets you to
software read data from the board. It uses SPI
Use one of those $3 arduino nanos to talk spi to the sensor and USB to a
computer. The linked software does that
> On Jan 4, 2017, at 11:32 AM, Dan Kemppainen wrote:
>
If you use plastic then paint it. UV light from the sun makes it brittle.
Plastic electrical conduit however is UV proof
I used larger size metal with a 3/4 x 1 fiting
How to ground a plastic mast? You'd need a ground block like the cable TV
guys use. But with steel mast you put a clamp on
You might be better off scanning than wide band. Even with a slow scanner you
can cover the entire RF range every few meters of car travel. But I would
sample as fast as you can. Hundreds of millions per second. This gives best
sensitivity and noise
Use gnu radio software and Their SDR radio
I remember the 91. The MG Produced 400Hz power. It is easier to build a linear
power supply as it would use smaller transformers and need less filtering
The chilled water cooling was not the best idea because when they had to power
down water would condense on the insides and they would have to
To answer about how they get good timing. Many times you run a loop that runs
off a timer at say exact 1000 times per second. Having something like a 1KHz
loop gives very deterministic timing. Lots of ways to do it. One is to run some
RTOS. I had to make all the axis of a machine tool move at ex
A common error is to have pps flipped. The leading edge should fall on the
second. Fix it with a NOT gate or in a configure file
> On Jul 16, 2016, at 1:58 PM, Hal Murray wrote:
>
>
> how...@leadmon.net said:
>> I have also run ppstest, and show a pps stream, granted the weird thing is
>> it s
If you use enough transmitters as in sampling the entire RF band then you don't
need to know ALL the telescope and transmitter locations. Most of the locations
can be found from the data you collect. Or to be clearer if you use gps to
survey 3 or 4 of the telescope location you can find the othe
You don't care about the lag in cron. You care about the variation of the lag.
Then again. The main cause of lag in a fog horn is the speed of sound
You set cron to fire at T minus the average lag time.
> On May 2, 2016, at 2:36 PM, Nick Sayer via time-nuts
> wrote:
>
>
>> On May 2, 2
NMEA spec says only that seconds in the sentence need to apply the second in
which they appear this means there could be half or even full second error they
need not be synchronized with the second tick.
Most GPS receivers do better then the standard that they don't have to
The generic NMEA G
Is the code someplace where we can see it, like github or source forge? Hard
to get help if not.
How does it work? I would guess it's all event driven.
One debug technique is to rethink the design. I just read here that there
exists a tboltd that is a multiplexer for the serial port. Mayb
Seems like you don't have to write much. Put you commands in a text file then a
cron job copies the file to the serial port and send any data coming back to
stdout. Gets piped to script that dumps that and current time to sql database.
I bet a dozen lines of code total.
> On Apr 6, 2016, at 3:
11 matches
Mail list logo
