On 4/26/2015 3:51 AM, Bryan _ wrote:
All:
P
I was looking at the project from David partridges web site
http://www.perdrix.co.uk/FrequencyDivider/index.html
-=Bryan=-
___
This is a comparator based
Should be fun when it becomes available... they claim they can get accurate
carrier phase info using a cheap antenna in the phone... and in real time.
It should also be able to get accurate time.
http://www.eurekalert.org/pub_releases/2015-05/uota-ncg050415.php
Hi,
It's not that simple. First, it's not 20 years, but 1024 weeks (19.6 years).
And not UTC weeks (which may have leap seconds) but GPS weeks (which do not,
and are always 604800 seconds long). etc
Don't think it's _that_ much code though. There's some open source ACM date
algorithms,
HI
For what you are doing, RG-6 Quad Shield is fine. Save the LMR-400 for other
things.
Get a pigtail that will connect to the GPS board. It needs to be pretty
flexible. That connector
is not very study. Don’t bother with an adapter. Been there / done that, not a
good idea. You
need the
Bob,
I'm sure much more qualified nuts will chime in, but a few thoughts of mine.
Over the years, I've collected enough GPS antennas from hamfests, online
vendors and who-knows-where, all for prices from free to tens of dollars.
Most of them came with anywhere from 3' to 10+meters of cable. Most
Hi
Ok, all of these receivers are designed to work with an amplified antenna. The
typical antennas have between 20 and 30 db of gain.
They allow a cable loss of ~ 10 db between the antenna and the receiver. A 3 db
splitter would come out of the “cable loss” budget.
The receivers put out 5V
Hi
The point is that the company likely has newer products that are based on the
same
code concepts. Not all software ideas are covered by copyright or a patent.
Once you
give away copies of the code, the world can base products off that code. You now
have a competitor who has a *much* lower
For reasons unknown to me, the body of the message was missing on the first
attempt.
Hi Bob,
While we debug your mail problem, here is your post.
/tvb
- Original Message -
From: Bob Fleming
To: time-nuts@febo.com
Sent: Tuesday, May 05, 2015 3:36 PM
Subject: The low budget UT+
Hi
I think I’d bet on L1/L5 (with similar accuracy) showing up cheap on the market
first.
Bob
On May 5, 2015, at 6:01 PM, Mark Sims hol...@hotmail.com wrote:
Should be fun when it becomes available... they claim they can get accurate
carrier phase info using a cheap antenna in the
On 2015-05-05 11:47, Hal Murray wrote:
cfhar...@erols.com said:
Surely the receiver is still producing correct frames that identify the
future leapsecond, and those frames could be read, and used to set a little
routine that wakes up at the appropriate second, and adjusts the overall
offset?
Don't think it's _that_ much code though. There's some open source ACM date
algorithms, and it would be easy enough to implement a quick and dirty fix,
adding a number of days offset, while the rest of the algorithm is tested.
Will the next time this problem reoccurs be another 20 years?
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Seems to me that the obvious simple answer works this way:
Since the GPS must use an RS232 connection to communicate
its information to the other devices in the telescope, all
that need be done is to write a fairly trivial program to
run on a PIC, or Arduino, that when presented with the date,
p...@heypete.com said:
Is there a list of other common time-nut devices that are susceptible to
similar issues? Lots of time-nuts use surplus equipment that's no longer
supported and it'd not be fun to have them stop working.
We should make a list of good/bad units.
The Z3801A does the
Hi Chuck,
It's not that simple. First, it's not 20 years, but 1024 weeks (19.6 years).
And not UTC weeks (which may have leap seconds) but GPS weeks (which do not,
and are always 604800 seconds long).
So you have to convert the incorrect UTC date and time back to GPS date and
time, then apply
Hi
The simple list of devices susceptible to this problem is:
Almost all of them from before 1998, many of them after that.
The issue is inherent in the design of the GPS coding and un-aided
recovery of that coding. The need to address it only was apparent to
most marketing departments after
Thanks to Vlad, Bob, and Chris for the responses so far - and for the helpful
suggestions/advice.
Since the focus of the answers to my (I suppose, dual-headed) question has been
on the splitting/sharing aspect, rather than on actual antenna type/model, I'm
guessing that the actual antenna used
Joe and I discovered some component value errors in the schematic I
posted yesterday. I uploaded a corrected schematic to Didier's
site. The filename of the corrected schematic is:
HP_53132-60011_Timebase_Support_Board_schematic_redrawn.pdf
When it comes off quarantine, you will be able to
Hi all,
The problem is not the 2100. It is the Trimble Ace III receivers inside
of it. There is a company in France, Heol Design, that makes what is
essentially a replacement for the Ace III, they call it an N024 model. I
am currently in contact with them to see if their units will correct
Hi Tom,
One of the first words I taught my precocious kid when he was
less than a year old was balderdash. It seemed appropriate for
him to know that word if I was going to be his father. Hard
for me to believe that little boy graduates from CMU with his
BS in physics this month
The
Hi Sean,
Thanks much for that information.
And now I guess we can't blame Trimble either since their 15-year old Ace
documentation [1] says:
ACE III GPS
System Designer Reference Manual
Part Number: 41265-00
Revision: A
Date: June 2000
Firmware: 8.08
3.5.1
Hi,
You can claim that software costs nothing once you write the first copy. In the
next breath we all expect
to get ongoing customer support for that software and (e ) patches for this
and that. When a vendor
charges us by the year for that support we are unhappy.
Would I love to
Hello Magnus,
It was a baud rate issue. Time Monitor defaults to 9600 and Time Lab
uses 19200. Changed the counter and time monitor to use 19.2k and every body is
happy.
Now I have to figure out how to use time lab. My TIE plots just show as
a strait line, I can zoom in to
cfhar...@erols.com said:
Surely the receiver is still producing correct frames that identify the
future leapsecond, and those frames could be read, and used to set a little
routine that wakes up at the appropriate second, and adjusts the overall
offset?
Is there any leap-warning info in
I think the lowest cost GPSDO frequency reference has to be one made
from these parts. You can get up and running for under $50.
1) the UT+
2) a patch antenna
2) the Lars Walenius Arduino based controller, using the $3 version of
the Arduino
3) An eBay OCXO for about $20. (this is the most
Lincoln,
Did you configure the coulder to use RS232 rather than GPIB?
It's in the manual.
Cheers,
Magnus
On 05/04/2015 07:28 AM, lincoln wrote:
Hello,
I've taken a first pass at using TimeLab over the weekend. I wasn't able to get
it to work with my SRS sr 620 over RS232. I know
On Tue, May 5, 2015 at 2:42 AM, Andrew Cooper acoo...@keck.hawaii.edu wrote:
We also ran into the TS2100 1995 bug this weekend. For us the consequences
are a bit more severe... The telescopes will not point to the right location
in the sky without accurate time!
Ouch. I have some friends
The 58535A splitter has been spoken for.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
28 matches
Mail list logo
