![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
On Jul 18, 7:05*am, BB wrote:
Why am I so paranoid? No you are not paranoid John, just justifiably concerned. I have twice had the security fail issue with my 302. The first time I sent it back to Cambridge, the second time I just waited for the problem to go away. I still don't understand it and I know it will bite me again. So far the security issue hasn't cost me a flight but if I ever get back to Nationals flying I suppose it could. I did lose a Regional day though due to a utility date math error that prevent the log from being downloaded. There is a lot to be said for dissimilar redundancy. Andy |
#2
|
|||
|
|||
![]()
On Jul 18, 9:23*am, Andy wrote:
*The first time I sent it back to Cambridge, the second time I just waited for the problem to go away. * That probably wasn't very clear. My recollection is that the problem is only seen on some, perhaps one, log. Later logs will have good security even if no corrective action is taken. I have never erased my 302. I record at 2 second period and have recorded over 500 hours of flights. I think I have seen the security issue twice. Andy |
#3
|
|||
|
|||
![]()
Per the IGC GNSS specs
2.5.4. Date of flight - the date used in the file name and in the H- record (DTE code) is the UTC date of the first valid fix in the flight log transferred after flight. That is, the date applicable to the time in the first line in the B (fix) record, not the date at the time of switching on, or of take-off. This is particularly important for recorders operated in time zones where they are switched on close to midnight UTC. (AL6) Therefore, one would conclude that there must be some fix form the 8th on the log. But, interestingly the "B" records (flight gps fix points) only have UTC Time in them. So the question would be: Did you power up your 302 on the 8th? (maybe, just to do a new flight declaration) Also, is there a big gap in the first few "B" record times? (i.e. a few points from the 8th followed by times from the 12th) "B" record format (in part) B H H M M S S D D M MM MM N D D D M MM MM E V P P P P P G G G G G CR LF Time UTC 6 bytes HHMMSS Latitude 8 bytes DDMMmmmN/S Longitude 9 bytes DDDMMmmmE/W Or, for you conspiracy theorists: This is a result of some secret military test on the GPS system meant to test for gaps in the space time continuum ;-) |
|
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Cambridge Model 20 Flight Recorder WANTED | N6TU | Soaring | 1 | May 28th 08 07:14 PM |
FSDO enforcement- GPS before effective date - which date to put in Aircraft Log for Part 43? | Ron A. | Instrument Flight Rules | 18 | March 15th 06 02:30 PM |
Date of effect now 1 October 2004 for revised IGC-approvals for certain legacy types of GNSS flight recorder | Ian Strachan | Soaring | 0 | March 15th 04 02:32 PM |
Date of effect now 1 April 2004 for revised IGC-approval for certain legacy types of GNSS flight recorder | Ian Strachan | Soaring | 56 | December 2nd 03 08:08 AM |
Cambridge 302 problem: "Could not get FAT.(A)" while trying to download flight logs | Jason Armistead | Soaring | 5 | July 13th 03 02:36 PM |