AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: BlinkNFG on June 01, 2010, 07:36:55 AM
-
Hi,
I have noticed some bizarre entries in mylog file and wondered if this was a general bug with the software or if something has gone wrong with my box/software. I'm located south-east England (near Stansted and Luton).
It seems that information from one flight ID is being merged into another flight ID. Here are a couple of examples from yesterday (31st May)
4CA258
RYR28QL. First detected 16:10 (UK time) at 27,00ft. Last detected at 18:02 (seems very unlikely) at 23,300ft.
RYR3GT first detected at 18:02 (same time RYR28QL last picked up) at 23,300ft and last detected at 18:08 at 4,000ft.
400C4E
EZY266. First detected at 22:20 (UK time) at 10,700ft. Last detected at 23:17 (again seems unlikely) at 6,00ft.
EZY265 First detected at 23:17 at 6,000ft. Last seen at 23:30 at 26,000ft.
Not seen any strange behaviour on the screen just in the mylog info. Any idea what is going on?
thanks
Jon
-
I have noticed some bizarre entries in mylog file and wondered if this was a general bug with the software or if something has gone wrong with my box/software. I'm located south-east England (near Stansted and Luton).
It seems that information from one flight ID is being merged into another flight ID. Here are a couple of examples from yesterday (31st May)
4CA258
RYR28QL. First detected 16:10 (UK time) at 27,00ft. Last detected at 18:02 (seems very unlikely) at 23,300ft.
RYR3GT first detected at 18:02 (same time RYR28QL last picked up) at 23,300ft and last detected at 18:08 at 4,000ft.
400C4E
EZY266. First detected at 22:20 (UK time) at 10,700ft. Last detected at 23:17 (again seems unlikely) at 6,00ft.
EZY265 First detected at 23:17 at 6,000ft. Last seen at 23:30 at 26,000ft.
Not seen any strange behaviour on the screen just in the mylog info. Any idea what is going on?
If it helps with the diagnosis, I logged RYR28QL (inbound BHX from Krakow) from 15:55 to 16:22 on SBS-1 and 16:17 to 17:01 on RadarBox. RYR3GT (BHX to Malaga) was on SBS-1 17:59 to 18:23 and RB 18:01 to 18:15 (all times BST).
Likewise EZY266 (BFS-STN) 22:17 to 22:30 and EZY265 (STN-BFS) 23:18 to 23:36, both on SBS-1, neither flight registered on RadarBox.
It's possible, though unlikely, that the crews on the respective outbound flights forgot to set the correct flight number until after you first picked up the departing aircraft in the climb. Unfortunately I wasn't running my packet monitor yesterday, or I'd have been able to confirm either way. Or, as you say, it could be a bug.
HTH
Dave
-
thanks for the reply and the logs. The log timings are similar to what I would have expected (but didn't get) from mine.
As you say crew error is unlikely - also I noticed more than those 2 examples over the last day or so.
I might email Radarbox suport and ask them to investigate. Has anyone else noticed this in their own logs?
-
thanks for the reply and the logs. The log timings are similar to what I would have expected (but didn't get) from mine.
As you say crew error is unlikely - also I noticed more than those 2 examples over the last day or so.
I might email Radarbox suport and ask them to investigate. Has anyone else noticed this in their own logs?
OK, I've been doing a bit more investigation.
Out of just over 1000 flights logged so far today in MyFlights, 152 show a duration in MyLog (StartTime to EndTime) of over 90 minutes.
Since most of what I pick is either arrivals/departures from the London area airports or high-level overflights, clearly that's nonsense. Apart from the odd loitering ASTOR or Islander, or VFR flight pottering about locally, nothing is going to remain within range of my RadarBox for an hour and a half.
Closer examination of the log reveals the same problem you have experienced - arriving flights, instead of timing out when the aircraft drops out of coverage, are being artificially extended (sometimes by several hours) until the same aircraft departs on a subsequent flight.
For example I have BAW565, inbound to Heathrow from Milan, on my SBS-1 for 20 minutes (12:01-12:21 local), but in MyLog in RadarBox BAW565 is showing as having been tracked for 147 minutes, from 12:15 to 14:02 (i.e. until after the same aircraft's subsequent departure as BAW908N to Frankfurt).
Same with overflights - RadarBox shows RYR4KA (Hahn-Dublin) tracking OTT at FL400 for the best part of 3 hours (07:28-11:09), by which time the aircraft in question was well on its way back to Germany again after a turnround at DUB.
Looks like one more entry for the bug-list, I fear ...
-
thanks for the detailed research ... very thorough. Hopefully the bug will be addressed at some point.
Jon
-
One random example from me too:
-
One random example from me too:
OK, you win - I can't beat your record of an aircraft airborne for 9 months :-)
-
Dave - where do you get your route information from? You seem to have a lot more information about the routes of alphanumeric flight IDs than I do
thanks
Jon
-
Dave - where do you get your route information from? You seem to have a lot more information about the routes of alphanumeric flight IDs than I do
I run a Flight Route lookup server at www.flightroutelookup.com/FlightRoute/
Lest I get accused (again) by AirNav of ugly commercialism, I would point out that this is a free service, open to all :-)
-
This kind if posts are more than welcome.
-
Dave - where do you get your route information from? You seem to have a lot more information about the routes of alphanumeric flight IDs than I do
I run a Flight Route lookup server at www.flightroutelookup.com/FlightRoute/
Lest I get accused (again) by AirNav of ugly commercialism, I would point out that this is a free service, open to all :-)
many thanks for the link
Jon
-
thanks for the detailed research ... very thorough. Hopefully the bug will be addressed at some point.
Any progress on this, AirNav ? It has yet to appear on the official bug-list, do you need any more supporting evidence ?
-
We need a bit more info to track this down. Its on the bug list as being marked as closed but a question mark remains on it. That fact it was signed off by beta testers as being fixed and hasn't been mentioned for a while means its probally some unusual condition.
The more info we get the better.
Edit - It is on the bug list and has been for a while, as awaiting more customer info.
-
Edit - It is on the bug list and has been for a while, as awaiting more customer info.
OK - I'm not sure what I can usefully add to the results from the investigation I did a few weeks ago.
Is anyone else (other than those who have already reported the bug) seeing entries in MyFlights with flight durations of hours/days/weeks/months ?
-
Is anyone else (other than those who have already reported the bug) seeing entries in MyFlights with flight durations of hours/days/weeks/months ?
Yes, all the time. Reported during beta testing(s), but never completely fixed. I NEVER rely on the flight start date/time. I have always assumed this problem is caused by putting the PC into standby whilst running Radarbox (which I regularly do).
(http://farm2.static.flickr.com/1250/4720161303_e815bdc608_b.jpg)
-
DaveReid,
We noted what you found and have stations close by to Heathrow as well but they don't exhibit the same behaviour all the time, but it does happen once in a while.
We are just trying to work out what causes that once in a while.
-
Is anyone else (other than those who have already reported the bug) seeing entries in MyFlights with flight durations of hours/days/weeks/months ?
Yes, all the time. Reported during beta testing(s), but never completely fixed. I NEVER rely on the flight start date/time. I have always assumed this problem is caused by putting the PC into standby whilst running Radarbox (which I regularly do).
(http://farm2.static.flickr.com/1250/4720161303_e815bdc608_b.jpg)
Hello
I agree with the standby idea. when we first got radarbox we used to put the computer on standby and got this problem however once we got more of an interest in keeping track on what had been when we weren't watching we made sure it never went to standby and never experienced it again.
Andrew
-
I agree with the standby idea. when we first got radarbox we used to put the computer on standby and got this problem however once we got more of an interest in keeping track on what had been when we weren't watching we made sure it never went to standby and never experienced it again.
So, can DaveReid and BlinkNFG confirm whether or not they put their PC into standby (or hibernate) when running Radarbox?
Also see:
http://www.airnavsystems.com/forum/index.php?topic=3750.msg36901#msg36901
http://www.airnavsystems.com/forum/index.php?topic=3963.msg42367#msg42367
EDIT: Just checked back through beta-testing emails, and this was the final conclusion:
Q: MyLog start date/time anomalies when PC has been in hibernation
A: This one is very strange and difficult to correct. It could be caused by data saved in the buffer when computer is hibernating. Let’s leave this one for a future version if that is Ok to you.
-
So, can DaveReid and BlinkNFG confirm whether or not they put their PC into standby (or hibernate) when running Radarbox?
Nope, neither.
-
Hi,
No I don't put the PC into standby either
Jon