Just as an aside, you /can /get rid of the 'dithering digit' problem if
you use a counter which employs a reciprocal counting technique.
I use a Thandar Thirlby TF830 locked to a 10MHz reference derived from a
Tbolt, but I'm sure there must be others.
David Bobbett, G4IRQ
On 24/11/2011
So its just 'dB' relative to a circular polarised isotropic radiator -
never knew that before!
On 03/11/2011 13:18, Chuck Harris wrote:
Here, try this link:
http://lmgtfy.com/?q=dbic+gain+definition
-Chuck Harris
David Kirkby wrote:
I've noticed a few GPS antennas give a gain in units of
Hi David,
I found it possible to compare down to the mHz region for the 1kHz
tones, but of course it requires good propagation, hanging around for
the continuous carrier periods of RWM and a disproportionate level of
patience!
A GPSDO is certainly the way to go for a quick, reliable and
David,
I'm 70km north of London and have used the French 162kHz high stability
signal as well as RWM (Moscow) on 4.996, 9.996 and 14.996MHz for
frequency measurement and calibration before I got my Thunderbolt. RWM
is particularly good because part of the schedule involves sending
continuous
The problem with all of these comparative techniques is that you are
always dealing with relative error vs finite error. However the result
is usually well in excess of that needed for ham ops.
Another trick is to load one memory with a 1kHz RWM offset in USB and
another with a 1kHz offset in
Apols for hijacking the topic, but does anyone have info on another
Nixie based frequency counter? It's a Venner TSA6636/2M and uses early
Fairchild Micrologic ICs, it's rather ill at the moment, so any info
would be gratefully received.
Fingers crossed and thanks in advance!
David, G4IRQ
Steve,
The two lines of text are what the iCruze will display when it thinks it
doesn't have any data. The RS232 input on my system can be unplugged and
that is exactly what is shown on the display in those circumstances.
Personally, I would start with the simple stuff, just continuity check
will do shortly.
I thought it would be useful if I let other 'sufferers' know what is
happening, in case somebody has something to add to the information.
Please feel free to contact me off list if you prefer.
David Bobbett, G4IRQ
___
time-nuts mailing
Now that is interesting! I was beginning to wonder whether the problem
lay with not being able to decode negative DAC values, but I had no way
of testing it. Clearly, as the data is processed correctly in other
programs - and the monitor works in all other respects - that does
rather point to
Well just in case this helps, the DAC on my Tbolt is currently reading
-0.056013V. As before, it shows up OK on Tboltmon.exe and Lady Heather,
reads all zeroes on the LCD monitor.
And just in case it is of any use, my Tbolt details from LH are:
App: 3.0 27 Jun 2002
GPS: 10.2 14 Nov
Didier,
I suspect that the negative voltage issue might be something of a blind
alley as I would expect more people to be affected than have reported an
issue - nevertheless it's worth a try. Just let me know when you have an
opportunity to use the data and I can provide it. The host PC here
That info would certainly increase the chances of it being an issue with
handling -ve numbers. I wonder if anybody on time-nuts has an LCD
monitor which can display negative values?
David, G4IRQ
On 12/05/2011 16:58, Jim Hall Sr. wrote:
I have the same symptoms. Two Thunderbolts, #1 has
Further to this discussion, my fluke.l monitor has never decoded the
Tbolt oscillator voltage, although all other data is displayed
successfully. I contacted fluke.l regarding the problem and he promised
to look into it - that was over a year ago and I have heard nothing
since. As a
Further to this discussion, my fluke.l monitor has never decoded the
Tbolt oscillator voltage, although all other data is displayed
successfully.
I contacted fluke.l regarding the problem and he promised to look into
it - that was over a year ago and I have heard nothing since.
As a
Hi Chris,
Re: 1)
The Tbolt is a bit 'deaf' by modern standards and ideally needs a 26dB
aerial for best performance. I could only source an 18dB aerial when I
initially installed my Tbolt and the lower signal level can be seen when
running Lady Heather.
The 26dB units are available from time
Mark is absolutely right about this Peter, the Tbolt receiver is
'deaf' by modern standards. In fact I seem to remember the Tbolt
documentation specifically mentions the use of a +26dB aerial. I use a
+16dB Lucent unit on top of the TV pole here in Central England and
although there is enough
/2010 16:58, Brooke Clarke wrote:
Hi David:
What power supply voltage are you using?
http://www.prc68.com/I/ThunderBolt.shtml#iCruze
Have Fun,
Brooke Clarke
http://www.PRC68.com
David Bobbett wrote:
Hi Didier,
No - the display reads DAC V: 0. on the iCruse LCD, all the
other data
.
On 19/08/2010 08:22, David Bobbett wrote:
Hi Brooke,
I know what you are thinking! Sadly the supply is 12.1v so there's
plenty of regulator headroom, very interesting page though. I'm
beginning to think that Didier's suggestion of corrupted firmware in
the iCruse is the most probable
values for DAC V, c) my
iCruse is faulty. I've pretty much run out of ideas on this one, so any
suggestions would be greatly appreciated!
Regards,
David Bobbett, Milton Keynes, UK.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go
stream with a scope may help diagnose such problem.
Didier KO4BB
-Original Message-
From: time-nuts-boun...@febo.com [mailto:time-nuts-boun...@febo.com] On
Behalf Of David Bobbett
Sent: Wednesday, August 18, 2010 4:23 AM
To: time-nuts@febo.com
Subject: [time-nuts] Tbolt and iCruse readout
20 matches
Mail list logo