AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: dumpty on August 26, 2009, 07:13:14 AM
-
Dear Airnav
Is version 3.02 a bugless(hopefully) version of 3.01 or are there any new features to look forward to.
Keep up the good work
Simon
-
hello
were is the link do download the new version 3.02
thank you
itzik
-
It is not available for public download because it is final beta testing.
It won't be too long now.
-
itzik, v3.02 is in closed beta testing, so not currently available to the public. Simon, It is a bug-fix of v3.01.
-
itzik, v3.02 is in closed beta testing, so not currently available to the public. Simon, It is a bug-fix of v3.01.
And are you happy with the degree of bug fixes in 3.02? Personally I have seen little wrong with 3.01 beta (don't use the network much) and seem to have working alerts in the main.
I was wondering if these problems have been fixed OK.
If you can't say anything, no problem.
-
Those two have been fixed. We are waiting for 3 minor corrections to be done so we can release V3.02 to the public.
-
Hi Support,
Are problems like you can see below also been fixed? As you can see the given route-information can not be correct.
Exemples like this I see verry much, and every time when I am running RadarBox.....
For your information: the network was switched off all the time!
(http://i393.photobucket.com/albums/pp18/Bierboum/Screenshots/15131908-29-2009.jpg)
-
Hi John
That route information looks good to me - granted that it's picking it up from the Flight ID.
Could it be that the Piper is wrongly broadcasting that ID?
Rod
-
Hi Rod,
Are you serious or are you joking? This ridiculous information I showed in the above screenshot is not an isolated case.
It swarm with.
I am verry surprised until sofar that nobody noticed problems like this.
-
John - I'm not joking - RadarBox is correct in that KLM1115 IS EHAM - ESSA, and PH-PAD is the Piper Archer. I see that Airframes.org has the same information as RB is displaying for you - PH-PAD doing flight KLM1115 (don't know where they get their info from, though).
So either RB is mixing up two flights, or PH-PAD is transmitting the callsign in error. Anyone else out there with a different explanation?
I've certainly never seen anying similar in RadarBox myself.
Rod
-
That route information looks good to me - granted that it's picking it up from the Flight ID.
Could it be that the Piper is wrongly broadcasting that ID?
It's not the Piper. According to my database, KLM B737 PH-BGG is intermittently sending the code that belongs to PH-PAD.
RadarBox is innocent, on this occasion :-)
-
Thanks, Dave - I was hoping you were around :-)
Rod
-
I've certainly never seen anying similar in RadarBox myself.
OK Rod, thank you for your reaction.
As I reported before: the route information on the screen and in the Interface as well are in much cases NOT correct.
I am verry sorry to say.
-
KLM PH-BGG = ModeS 484966
Piper PH-PAD = ModeS 484967
Would suggest that one of the transponders on the KLM jet has it's ModeS hex code out by one!!
It's always worth checking airframes.org when you see funny's like this. Many times RB is correct, it's the aircraft transmitting wrong information.
-
Ok Tarbat,
Thank you for your explanation. I must have sleep all the time. I always have thought that a ModeS-code was unique.
It still "swarm with it" over here.
-
I always have thought that a ModeS-code was unique.
When they are correct, they are.
-
The issue of 'crossed' flight ID's has been noted in Auckland, New Zealand on many occasions as well. It seems to occur when the hex code of 2 different aircraft are similar (i.e. only a few digits apart). Unlike the above replies - it is most certainly not the aircraft using the wrong hex code. According to a local aircraft engineer, the hex code is set in the avionics bay of an airliner and cannot be changed by the crew. It does appear to be a problem with the software where the flight ID is transposed to the wrong aircraft. I am using version 3.01B and am hoping it will be resolved in 3.02.
-
Hi All,
Thank you all for your reactions! It is clear to me now what the cause of problems like I showed to you can be.
-
The issue of 'crossed' flight ID's has been noted in Auckland, New Zealand on many occasions as well. It seems to occur when the hex code of 2 different aircraft are similar (i.e. only a few digits apart). Unlike the above replies - it is most certainly not the aircraft using the wrong hex code. According to a local aircraft engineer, the hex code is set in the avionics bay of an airliner and cannot be changed by the crew. It does appear to be a problem with the software where the flight ID is transposed to the wrong aircraft. I am using version 3.01B and am hoping it will be resolved in 3.02.
This is intriguing, and not something I have personal experience of.
Could you provide a couple of examples of what you have described ?
-
It seems to occur when the hex code of 2 different aircraft are similar (i.e. only a few digits apart).
Probably caused by not being able to parity check the transmissions, and bit-errors causing wrong hex-codes to be received. See:
http://www.airnavsystems.com/forum/index.php?topic=1641.msg28677#msg28677
http://www.airnavsystems.com/forum/index.php?topic=3052.msg28434#msg28434
-
Tarbat, help, have just downloaded the 3.0 and I dont have the airport outlines. Can you point me in the right direction please. Colin.
-
Tarbat, help, have just downloaded the 3.0 and I dont have the airport outlines. Can you point me in the right direction please. Colin.
See the Downloads section of the RadarBox Utilities website
http://radarbox.gofreeserve.com/index.html
-
Thanks for that Allocator. I could not remember where I could find it, thanks. Colin.
-
Allocator, I have down loaded the outlines on the above website but they dont appear on the ANRB when I put it on. Im running it on my laptop on Vista and 64 bit(dont know if that makes any difference?) Colin.
-
Colin, in which folder did you install ANRB? If you installed in C:\Program Files, then you'll need to put the outlines in Vista's Virtual Store.
-
Airnav a bit of an update on 3.02 please thanks
-
Its been a beta testing, the last final version had some issues (which is good they were caught) and hence we are fixing them as we type.
-
Hi Support,
Are problems like you can see below also been fixed? As you can see the given route-information can not be correct.
Exemples like this I see verry much, and every time when I am running RadarBox.....
For your information: the network was switched off all the time!
(http://i393.photobucket.com/albums/pp18/Bierboum/Screenshots/15131908-29-2009.jpg)
OMG! 334 Myflights? :O
when i get 30 its amazing....
-
The issue of 'crossed' flight ID's has been noted in Auckland, New Zealand on many occasions as well. It seems to occur when the hex code of 2 different aircraft are similar (i.e. only a few digits apart). Unlike the above replies - it is most certainly not the aircraft using the wrong hex code. According to a local aircraft engineer, the hex code is set in the avionics bay of an airliner and cannot be changed by the crew. It does appear to be a problem with the software where the flight ID is transposed to the wrong aircraft. I am using version 3.01B and am hoping it will be resolved in 3.02.
This is intriguing, and not something I have personal experience of.
Could you provide a couple of examples of what you have described ?
Here's a screenshot of 2 dupe flight ID's. In past experience it has happened when the Hex code of the 2 aircraft is similar. In this case this is not the case....
This was never a problem in version 2. I am hoping it will be resolved with the new version when it does come out.
-
Airnav any update on the progress of V3.02 please
-
Airnav any update on the progress of V3.02 please
Hi Marc,
Yeah..sure...it's called v3.04 now :-)
<ducking>
Regards,
-=Glyn=-
-
There is a lot of testing going on by the beta testers (closed testing). We should be there soon.
-
I saw a post from Airnav Development that said you were waiting on GlynH to post the 3 whatever release from the closed beta!
-
3.02 , 3.03 or 3.04 who knows, the closed beta group including GlynH does I guess!
-
Does it really matter what the Beta version is called? I remember that some people seemed to get really wound up about the version number - lol
It doesn't matter if I'm writing software or a text document, I always stick a 'V' number on the end as well as a date/time group so that I make sure that I can find the latest version and have a copy of the old versions.
For example
20090912-Test_Document_V101.txt
-
This scenario happens occasionally here in Bombay but occurred very frequently on my recent trip to China, usually when the false contact had been genuinely picked up/timed out recently.
At the moment I'm showing 8001EE KFR ATR and 8001E6 JLL 737 at the same level and in the same place. 8001EE is the genuine one and E6 it's shadow which will eventually time out and disappear. (Just gone).
On another note re China. At both Guangzhou and Shanghai despite being in very close proximity, and picking up and tracking all aircraft down to ground level not one appeared on the map (not even the ones you'd expect European/US). The occasional one popped up when between 30-50 miles away but this was very infrequent. At Pudong, the distance was not even indicated.
Are these signals able to be blocked?
Steve
-
Technically - Yes, but you would need to ensure that your own jamming signal did not prevent your own reception of the data.
An array of directional receiving aerials, and an omni for transmission would seem to do the trick, with the omni inside of the shielded directional receiving array.
It would also be neccessary to ensure that aircraft could receive the data from other aircraft, so that the in-aircraft collision preventation system still worked.
-
I saw a post from Airnav Development that said you were waiting on GlynH to post the 3 whatever release from the closed beta!
Hey...don't blame me - I did reply via pm! ;^)
Work continues apace...
Regards,
-=Glyn=-
-
I think we should have a 'pick on Glyn' night and take the pressure off Airnav!!
-
You'll have to join the queue Jeremy! :-)
Regards,
-=Glyn=-