AirNav RadarBox
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 


Author Topic: Range rings - accuracy thereof  (Read 4734 times)

0 Members and 1 Guest are viewing this topic.

Deadcalm

  • Sr. Member
  • ****
  • Posts: 381
Range rings - accuracy thereof
« on: February 25, 2008, 04:56:40 PM »
Hello, all.  Received my RadarBox last week, courtesy of Wimo (they forgot to include the flylead from the external antenna pre-amp to the RadarBox - they have sent one, and I await its arrival).

I'm just fiddling with the unit having switched it on for the first time, using the supplied antenna.

I'm a bit puzzled by the range rings.  I know I'm about 98 statute miles from Limoges (LFBL), yet the range ring display suggests that LBFL is only about 45 nm away.  Even allowing for the conversion, this appears to be way out.

My position on the map is about right, and the distance to Brive (LFBV) is also about right-ish.  Anyone have any ideas or comments about this apparent discrepancy?

Otherwise, first impressions are more than favourable, and I'm having lots of fun!

DC
« Last Edit: February 25, 2008, 04:58:31 PM by Deadcalm »
Go around, I say again go around...

davis

  • Jr. Member
  • **
  • Posts: 93
  • RANGE
Re: Range rings - accuracy thereof
« Reply #1 on: February 25, 2008, 06:00:43 PM »

Deadcalm

  • Sr. Member
  • ****
  • Posts: 381
Re: Range rings - accuracy thereof
« Reply #2 on: February 25, 2008, 06:39:12 PM »
Blimey - you're right.  I should have done my own homework (and have now...)
I've looked at my airways map and extrapolated - It's probably nearer 60 nm, though.
Just goes to show that when you jump to conclusions, you're invariably in error.  With my background I should have known better!!



DC

Go around, I say again go around...

AirNav Development

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 2545
    • AirNav Systems
Re: Range rings - accuracy thereof
« Reply #3 on: February 25, 2008, 07:17:38 PM »
Thanks for reporting. That problem is corrected for V1.4. We getting closer and closer (a few days only) to V1.4 release!