Quote:
Originally Posted by Dockhead
My best sailing friend studied astrophysics as an underground and is a master of celestial nav. I'm hoping to not be too busy the next time we cross an ocean together to take his classes.
I think with the widespread jamming and disruption of GPS we are seeing these days, these skills are more relevant than they were before. I note that the US Navy has re-introduced celestial nav.
Meanwhile I was thinking about how to solve the time problem in a robust way, so that you can do celestial even after a bad lightning strike etc. which wipes out your electronics.
I was discouraged to find out that mechanical chronometers are exorbitantly expensive to service and adjust.
So I'm looking at quartz marine chronometers, like the Seiko QM-10 and QM-11, which is not that expensive and readily available.
It has electronics so would be vulnerable to EMP but maybe could simply be kept in a metal box.
The accuracy looks like 60 seconds a year, but I don't know how crystal aging affects that -- these are decades old by now.
I also don't know if that's accurate enough -- 5 seconds a month?
There are HAQ watches available which are accurate to 10 seconds a year or even 5 seconds a year, which I guess could likewise be kept in a metal box.
Or maybe it's not all that important if you reset it to GPS time once a week.
With that process, maybe even a mechanical one would be OK.
Views?
|
As I understand it the USNavy never stopped performing CelNav, they stopped teaching it at the Academy. Then they realized there was a whole range of threats to GPS (Jamming, hacking, ASat weapons, CMEs, ....), so they started teaching it again at the Academy; they realized their officers needed to know enough to effectively manage the enlisted actually doing to
work.
I wish they hadn't shut down the LORAN system. It was costing $35M/yr in 2003(?) to maintain. It would take better part of $1B to
rebuild at this point. And it would be worth it because it is a lot harder to jam and you can't shoot them down.
Water under the bridge.
Accuracy, precision and error rate are 3 different things.
Precision is about how close a group of measurements are around their average. If you are only taking 1 reading then you want as high a precision as possible. With electronic and mechanical watches, you can more or less ignore precision, you need precision around 1sec and the second to second precision wanders by milliseconds or less. You ability to read the timepiece to 1sec is way worse than the precision of the timepiece itself.
Accuracy is about how close the average of a group of measurements is to the target/reality. Even if you have a wide spread of data, with averaging the result is likely to be close to reality with some caveats.
Error rate is the rate at which the measurements drifts from reality. This is the important value. For timepieces if you know the watch error on a given date and know the error rate and the error rate is consistent you can determine time at some future date without reference to outside sources.
The key here is knowing the error rate and that the error rate is consistent over time (weeks).
How do you measure the error rate? By checking error over an extended period (1-3mo).
So for each timepiece check the error every 7 or 10 days. I prefer 10d as it makes the math easier.
I would reset the watch at the start of checking the error rate and not reset it again until you check the error rate again.
At the start of checking the error rate reset the timepiece and error is 0 on that date.
Every 10d check the error. Then calculate the error (+/-sec) since the previous check AND since the first check. And calculate the error rate +/-sec/day) since last check and first check.
Having a low error rate is nice because there is less math to do to get corrected time, but it doesn't matter whether the error rate is 60s/d or 2s/d. A consistent 60.0s/d is actually better than the 2s/d if it varies from 1.8s/d to 2.2s/d because in 10d you know the correction will be 600s for the 60.0s/d whereas the correction for 2s/d might be 18s or 22s.
So how consistent do we need the error rate to be?
Near the equator 4sec time error results in 1nm longitudinal error. Further up or down the planet the position error is less. Let's say you want to keep longitude error due to time error to 1nm. That's 4sec.
What's the longest you will need to travel to reach some place where you can confirm time or replace damaged electronics? Lets say 30days. So over 30d you want to make sure all the 10d errors don't vary by more than 1sec each.
So if the 10d errors are 24s, 20s, 22s, 18s, 20s, 21s, ... you have a problem, the error rate is going up and down inconsistently.
If the 10d errors are 601s, 600s, 601s, 601s, 600s, ... the corrections are larger but the rate of error is consistent over time.
If I were going
offshore and wanted CelNave as a backup I would take 5
cheap Casio watches. Their error rates are usually consistent enough to count as Chronometers (that's the distinction between regular watches and chronometers, consistent error rate, not the magnitude of the rate.) Quartz oscillators are mostly but not completely temperature independent. The one on your wrist may be more consistent than the ones in the sextant box. Apparently error rate is not dependent on
battery condition/voltage.
Use a Rite-in-the-Rain notebook to track error for each watch over time and keep it updated every 7-10d.
I also have a Molinja pocket watch I got off of Ebay for $35 and couple mechanical watches of my father's from the 1970s. I have not checked their error rates. If I ever get serious about
offshore I will check their rates.
Mechanical watches need to be wound daily. Error rate varies with position, temperature, vibration and spring tension. I would store them in the sextant box to minimize both vibration and temperature variation, with the box in the the same position every day and the watches in the same position in the box every time (cut a slot in foam for each watch).
When the watch is first wound the instantaneous error rate is different than just before winding it 24hr later. However by winding it every day at the same time, the average DAILY error rate is the same from day so from day to day you can treat it as consistent. I would suggest that if you are 1/2 late winding one day winding it 1/2hr early the next may correct the net error. I have no info to back this up though.
Automatically wound watches are a special case. They have a weight in them that is jostled by hand and arm movements. The jostling of the weight winds the watch. I have no info on whether error rate is consistent or not. Spring tension is usually maintained near full winding and being worn means temperature variation is minimized. On average position is consistent thru the day so the only question is how much vibration is affecting error rate and how good the movement is.
Once you leave the
dock sailing, once a day at 1100-1130
wind the mechanical watches. Once per week shoot 1 line of position of the sun. (using a sextant is not exactly a perishable skill but it does degrade) and update the errors for each watch against an external source (GPS,
cell phone, broadcast time on shortwave) and check that the error rates remain consistent.
Dave Burch has a nice writeup on determining error rate:
https://davidburchnavigation.blogspo...atch-rate.html
To accurately keep track of elapsed days since starting an error record I would suggest a scheduling
wheel:
https://www.amazon.com/Scheduling-Wh...ab3c66184794d1
If accurate time is
lost and needs to be reestablished without outside reference there are 2 methods described in “Self-contained celestial navigation with H.O. 208” by John S Letcher. This can be found as a PDF for free and bought for a modest amount.
Here are some posts I've made on CelNav and related topics
https://www.cruisersforum.com/forums...ml#post2850485
https://www.cruisersforum.com/forums...ml#post2852228
https://www.cruisersforum.com/forums...ml#post2723304
https://www.cruisersforum.com/forums...ml#post2733360
https://www.cruisersforum.com/forums...ml#post2922991
https://www.cruisersforum.com/forums...ic-219989.html