![]() |
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 May 5, 7:56*am, jcarlyle wrote:
The older Cambridge recorders (10, 20, 25) do use circular recording, writing over the oldest data with the latest data without a hitch. If you really want to erase all of the flight data, though, simply change something like the Pilot Name or Comp ID. I'd be surprosed if that erases any data although it may make it inaccessible by the user. Typically "erasing" just moves a "pointer" and all the data is still remains stored in memory. Of course, as you say, there is no reason to "erase" these loggers. Unlike some others they never fill up and they have no issues when looping back to the start of memory. The only issue I know with these loggers is that they produce an inaccurate pressure altitude record when the voltage drops below spec. Don't transmit at 17,400 ft during a contest or you may have to explain an airspace violation. (the recorded altitude increases as the voltage reduces). Andy |
#2
|
|||
|
|||
![]()
On May 5, 10:06*am, Andy wrote:
On May 5, 7:56*am, jcarlyle wrote: The older Cambridge recorders (10, 20, 25) do use circular recording, writing over the oldest data with the latest data without a hitch. If you really want to erase all of the flight data, though, simply change something like the Pilot Name or Comp ID. I'd be surprosed if that erases any data although it may make it inaccessible by the user. *Typically "erasing" just moves a "pointer" and all the data is still remains stored in *memory. Of course, as you say, there is no reason to "erase" these loggers. Unlike some others they never fill up and they have no issues when looping back to the start of memory. The only issue I know with these loggers is that they produce an inaccurate pressure altitude record when the voltage drops below spec. *Don't transmit at 17,400 ft during a contest or you may have to explain an airspace violation. (the recorded altitude increases as the voltage reduces). Andy Only issues... Lets add they are not approved for word records. A (usually slight) hassle of dealing with .CAI files. And they have a horrible design feature that if you update a declaration you update all the declarations for existing flights--oops you probably did not want to do that. So if you had a record badge flight sitting in the logger too bad... (that's burnt a few people). And the memory is tiny compared to modern flight recorders. Outside of wanting one for the specific features for use with a GPS-NAV something a few decades more modern like a Nano logger is much more friendly and capable. Darryl |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
[US] Seniors Flight Logs | PMSC Member | Soaring | 0 | April 5th 09 04:35 PM |
looking for flight logs from Cordele, '07 | John Bojack[_2_] | Soaring | 1 | February 27th 08 03:27 PM |
Transfering Garmin flight logs | Dan Luke | Piloting | 0 | August 5th 06 01:18 AM |
2003 Region 2 Flight logs | Udo Rumpf | Soaring | 0 | February 27th 06 03:11 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 |