Range of Over-water Radio Stations???

[Guest klucznik]

Hi JD, I did say that I have no idea whether you programmed any hooks or not but I will take your word in that you programmed none. Thanks for the alert. Nevertheless, there could be some interaction between an unintentially hit key and the FSUIPC data that is being fed over the Ethernet, via WideFS, to RCv3 on the networked computer. I honestly do not know but now that I can actually look at the FSUIPC data being fed across this link, on the fly, I will delve into it a bit as I manipulate some unsuspecting key/s. Certainly one should stay away from the keyboard unless one intends on using it, my general practice, but I am not sure that possibly one, or more, keys could not have been hit unwittingly during that 7-1/2 hour flight. In any case there must have been a longitudinal data difference between what FS2002 and FSNav were seeing, which was correct, and what RCv3 was seeing otherwise why the discrepancy in Center Controller location? Until I find out what caused this problem how can I ever be sure it won't happen again. I do not fly with FS20002 often but only to, sort of, mimic my children's and grandchildren's RW flights. Thus when I do take off I want it right. Thanks for your note John.Regards

[bobbyjoh 11]

Blias,I have flown the altantiic routes from the US to both the UK and Germany countless times during the testing of RCV3. I can assure you that the ATC centers have worked and do now perfectly. If you want to test the flight I did this past week coming back from London here is the route:BLOCK TIMES FLIGHT TIMES FUELIN . . . . . ON . . . . TAKEOFF . . . .OUT . . . . . OFF . . . . LANDING . . . .TOTAL . . . . . TOTAL . . . . BURNOFF . . . .FLT REL IFR AAL327 EGLL/KORD MACH 80 A/C B767-300 W/ 767PIC ADDON FUEL TIME CORR TOGWT LDGWT AVG W/CTAXI 000000 0000 . . . . 336326 257371 P000DEST KORD 078956 0852 . . . .RESV 005814 0045 . . . .ALTN 002034 0015 . . . . ALTN KMKE DIST 58HOLD 001938 0015 . . . .EXTRA 002584 0020 . . . . ZFW 245000 PAYLOAD 047000TTL AT TO 091326 1027 . . . . DIST 4035REQD 091326 1027 . . . .CLB BIAS -6.0 % CRZ BIAS -10.3 % DSC BIAS 0.0 %EGLL CPT3G CPT UG1 SHA BABAN UN544 MASIT 5620N 5630N 5540N 5350N YAY J553 ML J555 YQB J546 UFX YXI TVC TVC.PMM4 JONSN BITTR TVC.PMM4 CLAUD PIVOT TVC.PMM4 ORD KORD/0852 M/H FL WIND ATCTO NM AWY M/C TAS G/S ZT ACTME ETA ATA ACBO ABO REM AREM N5127.4/W0038.8 264 CLB 030069 LOND259G 006 CPT3G 263 390 390 00/00 00/00 .../... 0004/... 0909/... N5127.1/W0052.7 272 CLB 000000 LONWOD 0352.0 008 CPT3G 272 390 390 00/01 00/02 .../... 0009/... 0903/... N5129.5/W0113.1 280 CLB 000000 LONCPT 114.35 013 CPT3G 280 390 390 00/02 00/04 .../... 0018/... 0895/... N5131.2/W0127.3 285 CLB 230051 LONKENET 008 UG1 286 390 390 00/01 00/05 .../... 0023/... 0889/... N5133.8/W0142.5 284 CLB 230051 LONBASET 009 UG1 285 390 390 00/01 00/06 .../... 0029/... 0883/... N5140.3/W0228.3 287 CLB 230051 LONNOSDA 029 UG1 287 390 390 00/04 00/11 .../... 0049/... 0863/... N5146.3/W0305.7 284 CLB 230051 LONTOC 024 UG1 284 390 390 00/03 00/14 .../... 0065/... 0847/... N5146.6/W0315.5 286 390 270057 LONDIKAS 005 UG1 285 457 457 00/00 00/15 .../... 0066/... 0846/... N5159.6/W0502.4 286 390 270057 LONSTU 113.10 067 UG1 285 457 457 00/08 00/24 .../... 0079/... 0833/... N5209.5/W0550.5 293 390 270057 EISNSLANY 031 UG1 294 457 457 00/04 00/28 .../... 0085/... 0827/... N5214.3/W0615.0 292 390 280061 EISNDIMUS 016 UG1 293 457 457 00/02 00/30 .../... 0088/... 0824/... N5230.1/W0738.8 292 390 280061 EISNABAGU 053 UG1 293 457 457 00/06 00/37 .../... 0099/... 0814/... N5243.2/W0853.1 292 390 280061 EISNSHA 113.30 047 UG1 292 457 457 00/06 00/43 .../... 0108/... 0805/... N5400.0/W1200.0 311 390 310105 EISNBABAN 135 DCT 311 457 457 00/17 01/01 .../... 0134/... 0778/... N5422.0/W1200.0 008 390 000000 EGGXMASIT 021 DCT 008 457 457 00/02 01/04 .../... 0138/... 0774/... N5600.0/W2000.0 301 390 340064 EGGX5620N 290 DCT 300 457 457 00/38 01/42 .../... 0195/... 0718/... N5600.0/W3000.0 286 390 330026 CZQX5630N 335 DCT 287 457 457 00/43 02/26 .../... 0260/... 0652/... N5500.0/W4000.0 282 390 220026 CZQX5540N 344 DCT 282 457 457 00/45 03/11 .../... 0324/... 0588/... N5300.0/W5000.0 275 390 240021 CZQX5350N 372 DCT 276 457 457 00/48 04/00 .../... 0393/... 0519/... N5123.6/W5605.0 271 390 290035 CZQXYAY 113.70 243 DCT 271 457 457 00/31 04/32 .../... 0439/... 0474/... N5011.0/W6146.8 276 390 000000 CZULYNA 113.60 227 J553 276 457 457 00/29 05/01 .../... 0481/... 0432/... N4950.2/W6423.1 281 390 250084 CZULPN 0360.0 103 J553 281 457 457 00/13 05/15 .../... 0500/... 0413/... N4836.7/W6812.5 267 390 6418198 CZULYYY 115.90 166 J553 267 457 457 00/21 05/37 .../... 0530/... 0382/... N4737.3/W7019.4 256 390 270107 CZULML 0392.0 103 J553 255 457 457 00/13 05/50 .../... 0549/... 0363/... N4642.3/W7137.5 242 390 000000 CZULYQB 112.80 076 J555 242 457 457 00/09 06/00 .../... 0563/... 0349/... N4611.5/W7325.1 265 390 000000 CZULUFX 0260.0 080 J546 265 457 457 00/10 06/11 .../... 0578/... 0335/... N4539.7/W7736.1 276 390 310079 CZYZYXI 115.60 177 DCT 277 457 457 00/23 06/34 .../... 0609/... 0303/... N4440.0/W8532.9 275 390 240083 MSPTVC 114.60 340 DCT 274 457 457 00/44 07/19 .../... 0669/... 0243/... N4336.8/W8549.2 195 390 000000 MSPJONSN 065 DCT 195 457 457 00/08 07/27 .../... 0680/... 0232/... N4307.2/W8556.6 193 390 240073 CHIBITTR 029 DCT 193 457 457 00/03 07/31 .../... 0685/... 0227/... N4440.0/W8532.9 014 390 000000 MSPTVC 114.60 094 DCT 014 457 457 00/12 07/43 .../... 0701/... 0211/... N4226.2/W8619.6 199 390 000000 CHICLAUD 138 DCT 199 457 457 00/18 08/01 .../... 0724/... 0188/... N4220.2/W8706.9 264 390 000000 CHIPIVOT 035 DCT 264 457 457 00/04 08/06 .../... 0730/... 0182/... N4440.0/W8532.9 028 390 000000 MSPTVC 114.60 155 DCT 028 457 457 00/20 08/26 .../... 0757/... 0156/... N4356.8/W8621.1 218 390 000000 MSPTOD 055 DCT 218 457 457 00/07 08/34 .../... 0766/... 0146/... N4159.2/W8754.2 215 DSC 000000 CHIORD 113.90 136 DCT 215 455 455 00/17 08/52 .../... 0773/... 0139/... N4158.7/W8754.2 181 000000 CHIKORD 000 DCT 181 210 210 00/00 08/52 .../... 0789/... 0123/...Print a copy of my flight plan and input into FSNav. Notice on this plan on the far right are each ATC center that the waypoint in located in. RC did this perfectBob Johnson

[Guest klucznik]

Hello Robert, After flying this same exact route twice myself after my first flight I do concur that the Controllers were right on the money the second and third times. I used the RW Flight Maps just as a check and they win hands down. What I am trying to find out is how Radar Contact could have been misled to think that the Centers for Gander Domestic, Gander Oceanic, Shanwick Oceanic and Shannon were all considered to be answerable by Moncton Center on my first flight. I am convinced that the problem was caused here at my location but I have yet not found a plausible answer for the discrepancy. I now can interrogate FS2002 from the same networked computer that runs RCv3, using the program GF-Interrogate, and it is now up to me to see if this problem might have been caused by an inadvertent striking of a keyboard key during this long initial flight. If, and it is only an if, there is a buffer involved, something like a FIFO, that could have had several repetitive lat/lon coordinates pushed onto its stack then read out enough number of times, the actual coordinates of the current location of the aircraft would eventually be correct. In fact the Centers did give the aircrafts correct location when I hit the London FIR. (This is an if.) Just like holding down a keyboard key and have it repeat a number of times. I am mainly concerned in this because if I can find what may have caused the problem I will insure, one way or the other, that the incident will not repeated. Thank You for your response Bob. I hope I wasn't too long winded.Regards

[Guest klucznik]

Hi, That GF-Interrogate should be FS-Interrogate.Cheers

[bobbyjoh 11]

Good luck Blias,I hate to say this, go enjoy flying, much better than debugging. We have done enough of that on this project for you. what you may have experienced was a system "hickup" that you may NEVER find again.Bob

[Guest klucznik]

Hi Bob, You are correct in that I may never find what caused the problem. I have no guarantee whatsoever. Yet I am aware that our microproccessors are stack-oriented devices and our high level languages are designed for these stack-oriented devices. Thus when module A talks to module B they do so by pushing data onto and popping data off of the stack. A DLL receives its data via the stack as does the Ethernet buffer so that is one common factor. Another clue is that neither FS2002 nor FSNav, both running on the main machine, were impacted at all. It was only Radar Contact running on the networked machine, the only program using FSUIPC DLL, that seemed to be impacted. As I mentioned in my previous note, I can monitor the data being sent to Radar Contact right at the second machine, via the DLL and Ethernet, and try to see how I can fool Radar Contact into thinking the aircraft is where it was at a previous time and not where it is located now. The position NOW is determined by FS2002 and FSNav's current visual indication. You are correct in that I may never find out what happened. I do not believe it was a machine hickup but inclined to think that too much LAT/LON data was pushed onto the stack at one point during the flight and that this was while the aircraft was in the Moncton Center's area. Thank you for your advice Bob. I just hate to give up on a problem. Once I can repeat it then the problem is essentially resolved.Regards

[jagabom 22]

Thanks for all your insite Pete. We are truly indepted to people like yourself who give unselfishley so much of your own time. We are truly gratefull to you. You guys do a job that the rest of us would like to be involved in but cannot. Thanks again.JimCYWG