AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: NickJackson on October 12, 2009, 05:30:44 PM
-
I have a conflict this afternoon between what the MyLog Grid & Report says versus the network at the same time.
A MyLog report shows RYR35LK as EI-DWK but the network shows it as EI-EFM. This has been cross-checked with 'another system' and that shows RYR35LK as EI-EFM also. The log does correctly shows EI-EFM as the inbound flight to EGHH (RYR99TR)!
Meanwhile, the network shows EI-DWK operating Girona-Treviso.
I'm sure the log is wrong and somehow EI-DWK has been matched with the wrong Flight No. for the return flight. The MyLog grid/report now shows EI-EFM as operating RYR902 which is a Cork-Stansted flight.
Is it possible the indexing on the MyLog file is corrupted?
Nick
-
I have a conflict this afternoon between what the MyLog Grid & Report says versus the network at the same time.
A MyLog report shows RYR35LK as EI-DWK but the network shows it as EI-EFM. This has been cross-checked with 'another system' and that shows RYR35LK as EI-EFM also. The log does correctly shows EI-EFM as the inbound flight to EGHH (RYR99TR)!
Meanwhile, the network shows EI-DWK operating Girona-Treviso.
I'm sure the log is wrong and somehow EI-DWK has been matched with the wrong Flight No. for the return flight. The MyLog grid/report now shows EI-EFM as operating RYR902 which is a Cork-Stansted flight.
Is it possible the indexing on the MyLog file is corrupted?
Nick
It's more likely that this is connected with similar "which plane?" questions that are being asked about My Flights where old information persists in being shown when a different aircraft is selected.
-
So is it best to clear the log files regularly (daily?) to avoid this problem?
-
So is it best to clear the log files regularly (daily?) to avoid this problem?
Clear the log? I don't understand what you're suggesting.
The log is populated from the contents of the navdata.db3 file, that is added to as new aircraft are seen. I can't see that there is anything to "clear".
-
I clear my log once a month, and just keep the latest month's worth of flights. It still keeps all the aircraft in the log, just clears down flights over a month old.
-
I clear my log once a month, and just keep the latest month's worth of flights. It still keeps all the aircraft in the log, just clears down flights over a month old.
So you export the data somewhere then?
-
So you export the data somewhere then?
No. I'm not interested in old flights.
Clearing down old flights make my SQL queries run a LOT quicker.
-
This is an extract of todays log:-
4CA25A RYR022H EI-DHE B738 Ryanair 12/10/2009 18:21:48
4CA703 RYR022H EI-EBF B738 Ryanair 12/10/2009 11:35:12
4CA75C RYR022H EI-EFA B738 Ryanair 12/10/2009 16:40:45
4CA75E RYR022H EI-EFC B738 Ryanair 12/10/2009 19:52:02
I've got 4 aircraft all supposedly operating RYR022H at different times today. This problem isn't confined to RYR flights and is widespread throughout the log. By reference to other external data the aircraft, date and time are correct but they have been matched to the incorrect flight numbers. The network information appears to be correct, so it's a problem with the way the MyLog data is processed.
Any ideas?
-
What version of RB are you using I wonder?
I've checked my log for today - only from about 1630 UTC - and I can't see any duplicate flight ID's for different aircraft.
I'm not sure this paste is going to work, but I'll try it anyway:
4CA25A EI-DHE B738 Ryanair 2009/10/12 17:04:23
4CA264 RYR907 EGSS-EICK EI-DHH B738 Ryanair 2009/10/12 19:09:24
4CA264 RYR908 EICK-EGSS EI-DHH B738 Ryanair 2009/10/12 21:18:35
4CA265 RYR4459 LEMG-EGNX EI-DHI B738 Ryanair 2009/10/12 20:41:59
4CA266 RYR297X EGSS-EIDW EI-DHJ B738 Ryanair 2009/10/12 21:36:02
4CA266 RYR2UP EIDW-EGSS EI-DHJ B738 Ryanair 2009/10/12 20:27:20
4CA27D RYR98Y EI-DHP B738 Ryanair 2009/10/12 18:30:58
4CA2A7 RYR108S EINN-EGSS EI-DHS B738 Ryanair 2009/10/12 20:51:02
4CA2AC RYR29EW EIDW-EGSS EI-DHY B738 Ryanair 2009/10/12 21:16:09
4CA2BF RYR9274 EHEH-EGSS EI-DLB B738 Ryanair 2009/10/12 18:36:00
4CA2C0 RYR9429 LIME-EIDW EI-DLC B738 Ryanair 2009/10/12 21:09:05
4CA2C3 RYR71VC LIEA-EIDW EI-DLF B738 Ryanair 2009/10/12 20:52:06
4CA2D4 RYR119G EGKK-EIDW EI-DLH B738 Ryanair 2009/10/12 20:49:49
4CA2FF RYR1286 LFML-EGPH EI-DLS B738 Ryanair 2009/10/12 21:42:01
4CA2FF RYR1287 EGPH-LFML EI-DLS B738 Ryanair 2009/10/12 17:37:11
4CA301 RYR99RK EIDW-LIRP EI-DLV B738 Ryanair 2009/10/12 18:31:13
4CA304 RYR2TY EIDW-EGSS EI-DLY B738 Ryanair 2009/10/12 17:15:04
4CA21C EI-DMG C441 Untitled 2009/10/12 20:07:09
4CA4E5 RYR26QX EGSS-LEZA EI-DPA B738 Ryanair 2009/10/12 18:44:13
4CA4E9 RYR701 EGSS-EIKY EI-DPE B738 Ryanair 2009/10/12 17:44:23
4CA4EE RYR4537 LIME-EGGP EI-DPJ B738 Ryanair 2009/10/12 21:49:27
4CA4EE RYR4538 EGGP-LIME EI-DPJ B738 Ryanair 2009/10/12 17:55:32
4CA4F1 RYR9428 EIDW-LIME EI-DPM B738 Ryanair 2009/10/12 17:25:59
4CA4F2 RYR2319 LZIB-EGSS EI-DPN B738 Ryanair 2009/10/12 17:44:35
4CA4F6 RYR293 EGSS-EIDW EI-DPS B738 Ryanair 2009/10/12 18:59:54
4CA4F6 RYR906Y EICK-EGSS EI-DPS B738 Ryanair 2009/10/12 17:45:03
4CA564 RYR6G3B EGSS-LFML EI-DPY B738 Ryanair 2009/10/12 18:38:01
4CA759 AZA209 EGLL-LIRF EI-DTA A320 Air One 2009/10/12 20:04:36
4CA759 AZA5P4 LIRF-EGLL EI-DTA A320 Air One 2009/10/12 18:49:29
4CA566 RYR8326 LEVC-EGSS EI-DWA B738 Ryanair 2009/10/12 21:21:42
4CA568 RYR08L EI-DWC B738 Ryanair 2009/10/12 20:55:55
4CA56E RYR1639 EDDB-EGNX EI-DWI B738 Ryanair 2009/10/12 21:13:40
4CA61E RYR8747 LFBH-EGSS EI-DWR B738 Ryanair 2009/10/12 17:09:15
4CA61F RYR8163 LEMG-EGSS EI-DWS B738 Ryanair 2009/10/12 21:29:51
4CA624 RYR338 EIDW-EGGW EI-DWX B738 Ryanair 2009/10/12 17:46:34
4CA624 RYR4154 EGGW-LIME EI-DWX B738 Ryanair 2009/10/12 18:51:46
4CA647 RYR419 EGSS-EGPK EI-DYE B738 Ryanair 2009/10/12 21:17:37
4CA647 RYR426 EGPK-EGSS EI-DYE B738 Ryanair 2009/10/12 20:07:05
4CA6A4 RYR5997 LEMD-EGSS EI-DYO B738 Ryanair 2009/10/12 18:43:36
4CA6A4 RYR5998 EGSS-LEMD EI-DYO B738 Ryanair 2009/10/12 19:58:57
4CA6A8 RYR8224 EGGD-EPRZ EI-DYT B738 Ryanair 2009/10/12 17:17:00
4CA6A8 RYR8225 EPRZ-EGGD EI-DYT B738 Ryanair 2009/10/12 21:57:39
4CA700 RYR341 EGGW-EIDW EI-EBC B738 Ryanair 2009/10/12 19:39:19
4CA700 RYR342 EIDW-EGGW EI-EBC B738 Ryanair 2009/10/12 21:40:29
4CA700 RYR345R EI-EBC B738 Ryanair 2009/10/12 19:39:06
4CA705 RYR2613 LEXJ-EGSS EI-EBH B738 Ryanair 2009/10/12 17:58:19
4CA705 RYR6128 EGAC-EGSS EI-EBH B738 Ryanair 2009/10/12 21:08:38
4CA705 RYR6129 EGSS-EGAC EI-EBH B738 Ryanair 2009/10/12 19:13:58
4CA736 RYR3465 LERS-EGGW EI-EBM B738 Ryanair 2009/10/12 17:04:23
4CA736 RYR3769 LEGE-EGGW EI-EBM B738 Ryanair 2009/10/12 21:58:44
4CA738 RYR1925 LELC-EGNX EI-EBO B738 Ryanair 2009/10/12 21:21:37
4CA73A RYR8379 LEST-EGSS EI-EBR B738 Ryanair 2009/10/12 18:35:40
4CA741 RYR1K LHBP-EGNX EI-EBZ B738 Ryanair 2009/10/12 20:49:29
4CA75C RYR1213 EPBY-EGBB EI-EFA B738 Ryanair 2009/10/12 21:14:51
4CA769 RYR9346 EGNT-LEGE EI-EFN B738 Ryanair 2009/10/12 17:48:22
4CA76A RYR6662 LFBL-EGPH EI-EFO B738 Ryanair 2009/10/12 17:04:23
4CA7A7 RYR1725 EPKK-EGNX EI-EFP B738 Ryanair 2009/10/12 21:07:41 [/size]
-
Agreed yours look good and mines rubbish. I'm struggling to work out why though.
I've deleted old data in the MyLog Tools -> Delete old data but that didn't make any difference to the next report generated.
The report's meaningless in its current form as I can't use it to tie anything up!
Nick
-
What version of RadarBox software Nick? - Look in Help > About
-
software is 2.01 with firmware 02.03.1
I've only had it 8 days and still figuring out the software. I thought it was maybe some routine I hadn't run properly but now I'm thinking that whatever matches the flights to the grid data to produce a generated report isn't working correctly.
-
Is anyone else having problems with the report generator? I've done a lot of work checking flights and I've found that the standard report has all sorts of problems matching flights(callsigns) to the correct aircraft picked up in the MyLog.
If I extract the information from the 'flights' table in the MyLog.db3 file, I see good information. When I print from the report generator the Flight nos/callsigns are largely wrong if the flights on question are regulars each day or many days of the week.
I've resorted to writing my own report for now based upon data extracted from MyLog.db3. Should I report this to AirNav using an e-mail to support?
-
The problem you are having was abug in V2.01. If I were you I would download the full V3.07 beta as it resolves these problems and better too.
Hope this helps
-
Thanks for the suggestion but,
in all professional IT packages I've encountered through work you would expect the current official release (I assume 2.01) to be properly fixed. I wouldn't expect users to take a beta version, which by definition isn't fully tested and released, to fix an official release version.
I'm not saying it wouldn't do the trick, but it's a strange way to run a support operation.
-
Cutting edge software is always evolving - V2.01 is ancient in the overall scheme of things and there has been a lot on learning along the way.
You can install the full version of Beta V3.07 and leave V2.01 completely unaffected, as the installation goes into a new directory. Then you can run whichever version you like, then go back to the old version - without uninstalling anything :-)
-
I may do that Allocator, but I was hoping to wait for the official release (i.e. post beta phase).
I know you say 2.01 is ancient but I bought it less than 2 weeks ago, paid quite a lot of money for it and it would be nice to have the major bugs fixed. We all know software can be a nuisance at times but to have the only standard report in such a poor state is not a good reflection on AirNav. Where's the professional standards?
I'm not getting at you but I'm disappointed with the fundamental robustness of the product, while accepting that much of the functionality is good.
Thanks for your assistance anyway.
Nick
-
Thanks for the suggestion but,
in all professional IT packages I've encountered through work you would expect the current official release (I assume 2.01) to be properly fixed. I wouldn't expect users to take a beta version, which by definition isn't fully tested and released, to fix an official release version.
I'm not saying it wouldn't do the trick, but it's a strange way to run a support operation.
Well the simple answer is that what is now 3.0x actually began life as 2.1x, so I would not worry too much about installing the beta version.
As Allocator says, you can install both versions and use whichever one you find works best for you. My own opinion is that while 3.07 is not bug free, it has fewer bugs than 2.01. There are a couple of annoying ones, although not everyone sees them, and I think that Airnav are pretty close to finding and fixing them.