Evander Posted March 4, 2020 Report Share Posted March 4, 2020 Hello, I noticed that offset 085C has strange behavior The manual says: VOR1 Latitude in FS form. Convert to degrees by Ok-SimC N/A *90/10001750. If NAV1 is tuned to an ILS this gives the glideslope transmitter Latitude. But sometimes it reads the VOR1 latitude not the NAV1 latitude When there's an ILS Same problem with the longitude, offset 0864 I checked with the FSUIPC logging in a window, when a few times I swap the frequency, it gives the wrong result, it's very inpredictable. So in my program it reads about I guess 20% wrong. Have someone a solution? Evan Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 4, 2020 Report Share Posted March 4, 2020 You'll need to state which Flight Simulator you are talking about, and which version of FSUIPC. If you use the Monitor facility in FSUIPC Logging tab, right-hand side, then, assuming you are using FSX or later, not FS9 or before, then FSUIPC will log exactly the value it receives from SimConnect, along with the Sim Var name. If this is wrong it points to either a bug in that version of F, or possibly a bug in the nav data in the scenery. FSUIPC doesn't manipulate the data received except to put it into the same units as FS98, FS2000, FS2002 and FS2004 used to provide. It does this to provide ongoing compatibility. Pete Link to comment Share on other sites More sharing options...
Evander Posted March 4, 2020 Author Report Share Posted March 4, 2020 FSUIPC 4949c FSX SP2 It's very strange when i swap the freq. I see short the good value and it change immediately in the wrong one. I have cheked many different default Airports, all the same. Evan Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 4, 2020 Report Share Posted March 4, 2020 1 hour ago, Evander said: FSUIPC 4949c First off you need to update to the currently supported version 4.974. The one you are using is very old. Check on fsuipc.com Only after you'd done that, add the monitoring as I requested and show me the log file after a session in which you see the problem. Please note down what I should look for. Pete Link to comment Share on other sites More sharing options...
Evander Posted March 4, 2020 Author Report Share Posted March 4, 2020 Hello Pete, Thank you for helping me. I see nothing weird in the log Tested on EDDK RW 25 freq: 109.100 swap freq: 111.100 Output in FS windows gives: I started with no Ils and no VOR gives 0 (111.100) First swap was wrong gives number 5652010 the same as the VOR 2e gives 0 is ok 3e gives 5652883 is ok 4e gives 0 is ok 5e gives 5652010 and is wrong For FSX is this no problem the ILS is working fine Attached a screenshot Log File gives: ********* FSUIPC4, Version 4.974 (24th February 2018) by Pete Dowson ********* User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired 309412 System time = 04/03/2020 19:59:43, Simulator time = 12:12:39 (11:12Z) 309412 FLT path = "C:\Users\ET\Documents\Flight Simulator X Files\" [Continuation log requested by user] Running inside FSX on Windows 7 Module base=573D0000 334825 *** EVENT: Cntrl= 66448 (0x00010390), Param= 1 (0x00000001) NAV1_RADIO_SWAP 354247 *** EVENT: Cntrl= 66448 (0x00010390), Param= 1 (0x00000001) NAV1_RADIO_SWAP 356322 *** EVENT: Cntrl= 66448 (0x00010390), Param= 1 (0x00000001) NAV1_RADIO_SWAP 365853 *** EVENT: Cntrl= 66448 (0x00010390), Param= 1 (0x00000001) NAV1_RADIO_SWAP 367928 *** EVENT: Cntrl= 66448 (0x00010390), Param= 1 (0x00000001) NAV1_RADIO_SWAP Evan Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 5, 2020 Report Share Posted March 5, 2020 The log tells me nothing I'm afraid. In the Monitor facility please make sure you check the "normal log" option so the entries appear in the log. We need to show that it is SimConnect providing the wrong value. Monitor the offset you are concerned with (085C) as type U32, then show me the log pointing out where you think the Sim is getting it wrong. And please DO NOT use the "New Log" button to make FSUIPC start a new log. I also want to be able to see the initialisation entries! AND close the session and show the complete log please. Unfortunately, even if we gather solid proof that FSX is in error, it won't get fixed. But maybe Iit can be tested in P3D4 so that L-M can be asked to fix it. Oh, i'd also need to know that both the aircraft and scenery in use is default, and no NAVAID updates from Herve Sors or FSAeroData. Otherwise L-M won't want to know. Pete Link to comment Share on other sites More sharing options...
Evander Posted March 5, 2020 Author Report Share Posted March 5, 2020 Default scnenery Default Cessna 172 No NAVAID updates Airport EDDK Look at the end of the log, where it goes wrong. Reads the latitude and longitude ok and then: 1021713 Monitor IPC:085C (S32) = 5652010 the number now is: 5652010 must be 5652883 Evan Log file: ********* FSUIPC4, Version 4.974 (24th February 2018) by Pete Dowson ********* Windows 7 Ultimate 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1) fsx.exe version = 10.0.61472.0 Reading options from "F:\FSX installed\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=5B9D0000 User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired 31 System time = 05/03/2020 12:53:41 31 FLT path = "C:\Users\ET\Documents\Flight Simulator X Files\" 31 ------ Module Version Check ------ 31 acontain.dll: 10.0.61472.0 31 api.dll: 10.0.61472.0 31 controls.dll: 10.0.61472.0 31 fs-traffic.dll: 10.0.61472.0 31 G3D.dll: 10.0.61472.0 31 language.dll: 10.0.61472.0 31 sim1.dll: 10.0.61472.0 31 visualfx.dll: 10.0.61472.0 31 weather.dll: 10.0.61472.0 31 window.dll: 10.0.61472.0 31 ---------------------------------- 62 Trying to connect to SimConnect Acc/SP2 Oct07 ... 62 FS path = "F:\FSX installed\" 140 LogOptions=F0000000 0000001D 140 ------------------------------------------------------------------- 140 ------ Setting the hooks and direct calls into the simulator ------ 140 --- CONTROLS timer memory location obtained ok 140 --- SIM1 Frictions access gained 140 --- FS Controls Table located ok 140 --- Installed Mouse Macro hooks ok. 140 --- Wind smoothing fix is fully installed 140 --- G3D.DLL fix attempt installed ok 140 --- SimConnect intercept for texts and menus option is off 140 --- All links checked okay 140 ------------------------------------------------------------------- 140 SimConnect_Open succeeded: waiting to check version okay 140 Trying to use SimConnect Acc/SP2 Oct07 140 Opened separate AI Traffic client okay 1388 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 1388 Initialising SimConnect data requests now 1388 FSUIPC Menu entry added 1435 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 1435 F:\FSX installed\FLIGHTS\OTHER\FLTSIM.FLT 1435 F:\FSX installed\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 1435 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=N 1560 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 1731 Memory in use: 546Mb, Avail=3550Mb, MaxFreeBlock=2047Mb 7067 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 39390 F:\FSX installed\SimObjects\Airplanes\C172\Cessna172SP.AIR 71729 Memory in use: 650Mb, Avail=3446Mb, MaxFreeBlock=2047Mb 105020 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 124239 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 124254 Aircraft loaded: running normally now ... 124270 User Aircraft ID 1 supplied, now being used 124520 System time = 05/03/2020 12:55:46, Simulator time = 12:12:18 (11:12Z) 126532 Starting everything now ... 126548 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 126579 FollowMe service initialised and ready ... 130027 Advanced Weather Interface Enabled 131774 Memory in use: 1085Mb, Avail=3011Mb, MaxFreeBlock=2047Mb 139153 *** EVENT: Cntrl= 66445 (0x0001038d), Param= 0 (0x00000000) NAV1_RADIO_FRACT_DEC_CARRY 143068 *** EVENT: Cntrl= 65640 (0x00010068), Param= 0 (0x00000000) NAV1_RADIO_WHOLE_DEC 143489 *** EVENT: Cntrl= 65640 (0x00010068), Param= 0 (0x00000000) NAV1_RADIO_WHOLE_DEC 143926 *** EVENT: Cntrl= 65640 (0x00010068), Param= 0 (0x00000000) NAV1_RADIO_WHOLE_DEC 144379 *** EVENT: Cntrl= 65640 (0x00010068), Param= 0 (0x00000000) NAV1_RADIO_WHOLE_DEC 145112 *** EVENT: Cntrl= 65640 (0x00010068), Param= 0 (0x00000000) NAV1_RADIO_WHOLE_DEC 145689 *** EVENT: Cntrl= 65640 (0x00010068), Param= 0 (0x00000000) NAV1_RADIO_WHOLE_DEC 146219 *** EVENT: Cntrl= 65640 (0x00010068), Param= 0 (0x00000000) NAV1_RADIO_WHOLE_DEC 146843 *** EVENT: Cntrl= 65640 (0x00010068), Param= 0 (0x00000000) NAV1_RADIO_WHOLE_DEC 149293 *** EVENT: Cntrl= 65642 (0x0001006a), Param= 0 (0x00000000) NAV1_RADIO_FRACT_DEC 151180 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 159214 *** EVENT: Cntrl= 65645 (0x0001006d), Param= 0 (0x00000000) NAV2_RADIO_WHOLE_INC 159667 *** EVENT: Cntrl= 65645 (0x0001006d), Param= 0 (0x00000000) NAV2_RADIO_WHOLE_INC 160088 *** EVENT: Cntrl= 65645 (0x0001006d), Param= 0 (0x00000000) NAV2_RADIO_WHOLE_INC 167139 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 167670 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 167888 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 168153 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 168340 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 168512 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 168699 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 168855 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 169027 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 169198 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 169386 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 169557 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 169729 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 169932 *** EVENT: Cntrl= 65646 (0x0001006e), Param= 0 (0x00000000) NAV2_RADIO_FRACT_DEC 174580 *** EVENT: Cntrl= 66452 (0x00010394), Param= 0 (0x00000000) NAV2_RADIO_SWAP 184471 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 187201 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 189900 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 191834 Memory in use: 1089Mb, Avail=3007Mb, MaxFreeBlock=2047Mb 192084 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 194174 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 195734 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 198152 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 199899 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 202271 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 203862 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 206202 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 207419 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 229009 KEYDOWN: VK=80, Waiting=0, Repeat=N, Shifts=0 229009 .. Key not programmed -- passed on to FS 229040 *** EVENT: Cntrl= 65561 (0x00010019), Param= 0 (0x00000000) PAUSE_TOGGLE 229087 KEYUP: VK=80, Waiting=0 231224 KEYDOWN: VK=80, Waiting=0, Repeat=N, Shifts=0 231240 .. Key not programmed -- passed on to FS 231240 *** EVENT: Cntrl= 65561 (0x00010019), Param= 0 (0x00000000) PAUSE_TOGGLE 231427 KEYUP: VK=80, Waiting=0 243190 Deactivated for PID=3088, "explorer.exe" 243236 Lost focus to PID=3088, "explorer.exe" 251895 Memory in use: 1105Mb, Avail=2991Mb, MaxFreeBlock=2047Mb 311955 Memory in use: 1105Mb, Avail=2991Mb, MaxFreeBlock=2047Mb 372015 Memory in use: 1106Mb, Avail=2990Mb, MaxFreeBlock=2047Mb 432107 Memory in use: 1105Mb, Avail=2991Mb, MaxFreeBlock=2047Mb 444228 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 444228 Sim stopped: average frame rate for last 320 secs = 57.1 fps 444275 Max AI traffic was 81 aircraft (Deleted 0) 458237 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 463603 Deactivated: culprit unknown 463603 Lost focus to PID=5360, "UltraMonTaskbar.exe" 492214 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb 552321 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb 612444 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb 672551 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb 732658 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb 792812 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb 806338 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 806353 Sim stopped: average frame rate for last 348 secs = 59.8 fps 806400 Max AI traffic was 81 aircraft (Deleted 0) 829348 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 847662 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 848442 Monitor IPC:085C (S32) = 0 848442 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=0, Lon=0, Alt=0 850330 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 851453 Monitor IPC:085C (S32) = 5652883 851453 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=50.86704724, Lon=7.152247131, Alt=92.04901123 851750 Monitor IPC:085C (S32) = 5652010 852904 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb 881998 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 882435 Monitor IPC:085C (S32) = 0 882435 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=0, Lon=0, Alt=0 890141 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 891452 Monitor IPC:085C (S32) = 5652883 891452 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=50.86704724, Lon=7.152247131, Alt=92.04901123 912996 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb 973103 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb 1003804 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 1004443 Monitor IPC:085C (S32) = 0 1004443 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=0, Lon=0, Alt=0 1006971 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 1008453 Monitor IPC:085C (S32) = 5652883 1008453 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=50.86704724, Lon=7.152247131, Alt=92.04901123 1013991 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 1014443 Monitor IPC:085C (S32) = 0 1014443 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=0, Lon=0, Alt=0 1016128 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 1017469 Monitor IPC:085C (S32) = 5652883 1017469 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=50.86704724, Lon=7.152247131, Alt=92.04901123 1018530 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 1019451 Monitor IPC:085C (S32) = 0 1019451 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=0, Lon=0, Alt=0 1020309 *** EVENT: Cntrl= 66448 (0x00010390), Param= 0 (0x00000000) NAV1_RADIO_SWAP 1021447 Monitor IPC:085C (S32) = 5652883 1021447 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=50.86704724, Lon=7.152247131, Alt=92.04901123 1021713 Monitor IPC:085C (S32) = 5652010 1033194 Memory in use: 1111Mb, Avail=2985Mb, MaxFreeBlock=2047Mb Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 5, 2020 Report Share Posted March 5, 2020 54 minutes ago, Evander said: 1021447 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=50.86704724, Lon=7.152247131, Alt=92.04901123 1021713 Monitor IPC:085C (S32) = 5652010 Aha! Okay, so the SimConnect value is correct, but something is going wrong in FSUIPC after it is received. I'll check it out in FSUIPC5 as I am now set up to debug that rather than FSUIPC4. It might not be for a couple of days as I've got a lot of prior stuff to get through. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 5, 2020 Report Share Posted March 5, 2020 20 minutes ago, Pete Dowson said: Aha! Okay, so the SimConnect value is correct, but something is going wrong in FSUIPC after it is received. Actually, reading the documentation more carefully, it appears that 085C is supposed to be the VOR latitude, always. Offset 0874 is the same except when NAV1 is tuned to an ILS in which case it is the ILS latitude. So, if there is an error, isn't it that 085C isn't maintaining the VOR latitude when NAV1 is on an ILS? I'll look at the code, but I'm wondering if the problem is actually more to do with when the NAV1=ILS indication is provided by SimConnect. If there was a delay it would explain the change you are seeing, albeit very quickly. Whether it is an ILS is indicated by bit 7 in offset 0C4D. The SimConnect variable for that flag is "NAV HAS LOCALIZER". So, could you repeat the test but not only monitor 085C, as you have, but also 0874 (also a U32), and 0C4D (as U8). Then you could see if you get the results you want with offset 0874 . Pete Link to comment Share on other sites More sharing options...
Evander Posted March 5, 2020 Author Report Share Posted March 5, 2020 Ok, I will do that Evan Link to comment Share on other sites More sharing options...
Evander Posted March 5, 2020 Author Report Share Posted March 5, 2020 the offset 0874 gives always the VOR and the offset 0C4D gives bit 7 set 1082023 Monitor IPC:0C4D (U8) = 0 1082039 SimRead: 0C4D="NAV BACK COURSE FLAGS:1" [also 0C4A] INT32: 131 (0x00000083) 1082039 Monitor IPC:0C4D (U8) = 128 1082039 SimRead: 0C4D="NAV HAS LOCALIZER:1" [also 0C4A] INT32: 1 (0x00000001) 1082039 Monitor IPC:085C (S32) = 5652883 1082039 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=50.86704724, Lon=7.152247131, Alt=92.04901123 1082039 Monitor IPC:0874 (S32) = 5652010 1082039 SimRead: 0874="NAV VOR LATLONALT:1" [also 0878] [also 087C] FLT64 Lat=50.85919004, Lon=7.120706588, Alt=92.04901123 Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 5, 2020 Report Share Posted March 5, 2020 2 hours ago, Evander said: the offset 0874 gives always the VOR and the offset 0C4D gives bit 7 set Hmm, that is very strange. Are those bits of log immediately after you did a "swap"? I'll need to find time to check this on FSUIPC5 ... maybe over the weekend. Please remind me if I haven't got back by monday. I seem to have a lot on and, being old, tend to forget and mislay things (I've written a Note to myself and left it on my desk! 😉 Pete Link to comment Share on other sites More sharing options...
Evander Posted March 5, 2020 Author Report Share Posted March 5, 2020 Yes, it goes verry quickly Link to comment Share on other sites More sharing options...
Evander Posted March 7, 2020 Author Report Share Posted March 7, 2020 After further investigation I noticed that when you make a go around that after about 4 miles out it change also to the VOR without changing the radio frequency or something else. Evan Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 7, 2020 Report Share Posted March 7, 2020 1 hour ago, Evander said: After further investigation I noticed that when you make a go around that after about 4 miles out it change also to the VOR without changing the radio frequency or something else. Maybe the ILS reception has faded too much to be recognised -- did you check the flag which determines this? Pete Link to comment Share on other sites More sharing options...
Evander Posted March 8, 2020 Author Report Share Posted March 8, 2020 I think not because the ILS identifier also not changed. Wich flag do you mean? When you mean offset 0C4D then Yes: on approach bit 7 and 6 set (192) near touchdown bit 7 (128) halfway runway bit 3 and 5 (40) and then bit 7 set (128) at the same time change to the VOR. Evan Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 8, 2020 Report Share Posted March 8, 2020 6 hours ago, Evander said: I think not because the ILS identifier also not changed. Wich flag do you mean? When you mean offset 0C4D then Yes: on approach bit 7 and 6 set (192) near touchdown bit 7 (128) halfway runway bit 3 and 5 (40) and then bit 7 set (128) at the same time change to the VOR. Yes, 0C4D bit 7. I'm afraid I've got problems to sort out here befre I can investigate this (I think I need to reinstall windows), so it will be later in the week. In any case if it is a bug in FSUIPC I can get it fixed in an FSUIPC5 release, but I'm not sure about FSUIPC4 which was frozen a couple of years back (after 14 years of continuous development). Seems odd no one came u with the problem you report in all that time? I'll let you know what I can do. What do you use the Lat/Lon/Alt value for when on Approach, exactly? And just for clarification , are we talking about the VOR signal for the localiser, when you want the ILS glideslope transmitter location? Pete Link to comment Share on other sites More sharing options...
Evander Posted March 8, 2020 Author Report Share Posted March 8, 2020 I check the distance from the plane for an ILS aproach with a glideslope in a graphical chart, when the distance is wrong then the plane is of the glideslope, i have made a work around but this is not 100% proof. So I imust have the lat/lon/alt from the localizer not the VOR , the alt is always good see this video:https://www.youtube.com/watch?time_continue=39&v=lDk3JpNb5mw&feature=emb_logo Ofcourse in this video is all working well. Evan Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 8, 2020 Report Share Posted March 8, 2020 12 hours ago, Evander said: I check the distance from the plane for an ILS aproach with a glideslope in a graphical chart, when the distance is wrong then the plane is of the glideslope, i have made a work around but this is not 100% proof. So you don't use the glideslope deviation value in offset 0C49? Prefer to do it the hard way? You've also got 0C48 for the localiser deviation. Looking at the video you linked to, I'm not sure how this relates. There are changing moving Lat/Lons for a ship -- I didn't even know they had VORs/ILSs! Pete Link to comment Share on other sites More sharing options...
Evander Posted March 9, 2020 Author Report Share Posted March 9, 2020 Hey, it's not the hard way it's another way. It's very simple infact: I know thw planes height I know thw runway height I know the glideslope degrees And when I also know the correct distance is it very simple Example: at 1000 feet with a glideslope of 5.50 degrees the distance = 1.709 Nm. at 1000 feet with a glideslope of 3.00 degrees the distance = 3.140 Nm. So when the plane is on the glideslope at 500 feet and the Glislope is 3.00 degrees distance is then 1.570 Nm. When on the glideslope at touchdown the distance is 0 Nm. In the graphical is the end of the glidesope 0 Nm. I must know this point and that is the offset we talk about. My question was is the offset wrong or I'm wrong. Have you test it on your Machine? When I know for sure the offset is not wrong I must do more investigation. When the offset is wrong I must live with that. Evan Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 9, 2020 Report Share Posted March 9, 2020 2 hours ago, Evander said: My question was is the offset wrong or I'm wrong. Have you test it on your Machine? Sorry, I've been 100% tied up trying to get my setup back up in time for a visit I've got tomorrow (travelling from Australia) to do some updated visuals for my cockpit. I haven't forgotten, and should get around to testing this during this week. Meanwhile, because even if there is a problem in FSUIPC with timings regarding SimConnect callbacks (because that is what I am suspecting), I can get it fixed in FSUIPC5 which is still in development, but probably not FSUIPC4 which stopped development over two years ago. This is why I thought you might use the deviation indications instead. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 11, 2020 Report Share Posted March 11, 2020 Today I finally managed to start tedting this for you -- but on P3D4 using FSUIPC5, as I said. I used the same details as yourself, excepting as there's no Cessna I used the Baron 58. On the threshold of Runway 25 at EDDK with 111.10 and 109.10 on NAV1. Offsets 0C4D, 085C and 0874 each reported correctly, and were correct on every swap of the frequencies. I repeated this many times till came to the conclusion that it just wasn't going to go wrong. The data from SimConnect always arrived in exactly the same order, every time, the sequence for 109.10 being: 2614717 SimRead: 0C4D="NAV HAS NAV:1" [also 0C4A] INT32: -1 (0xFFFFFFFF) 2614717 Monitor IPC:0C4D (U8) = 0x0 2614717 SimRead: 0C4D="NAV BACK COURSE FLAGS:1" [also 0C4A] INT32: 131 (0x00000083) 2614717 Monitor IPC:0C4D (U8) = 0x40 2614717 SimRead: 0C4D="NAV HAS GLIDE SLOPE:1" INT32: -1 (0xFFFFFFFF) 2614717 Monitor IPC:0C4D (U8) = 0xC0 2614717 SimRead: 0C4D="NAV HAS LOCALIZER:1" [also 0C4A] INT32: 1 (0x00000001) 2614717 Monitor IPC:085C (U32) = 5652883 2614717 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=50.86704724, Lon=7.152247131, Alt=92.04901123 2614717 Monitor IPC:0874 (U32) = 5652010 2614717 SimRead: 0874="NAV VOR LATLONALT:1" [also 0878] [also 087C] FLT64 Lat=50.85919004, Lon=7.120706588, Alt=92.04901123 and then for 109.10: 2616714 SimRead: 0C4D="NAV HAS NAV:1" [also 0C4A] INT32: 0 (0x00000000) 2616714 Monitor IPC:0C4D (U8) = 0xE8 2616714 SimRead: 0C4D="NAV BACK COURSE FLAGS:1" [also 0C4A] INT32: 0 (0x00000000) 2616714 Monitor IPC:0C4D (U8) = 0xA8 2616714 SimRead: 0C4D="NAV HAS GLIDE SLOPE:1" INT32: 0 (0x00000000) 2616714 Monitor IPC:0C4D (U8) = 0x28 2616714 SimRead: 0C4D="NAV HAS LOCALIZER:1" [also 0C4A] INT32: 0 (0x00000000) 2616714 Monitor IPC:085C (U32) = 0 2616714 SimRead: 085C="NAV GS LATLONALT:1" [also 0864] [also 086C] FLT64 Lat=0, Lon=0, Alt=0 2616714 Monitor IPC:0874 (U32) = 0 2616714 SimRead: 0874="NAV VOR LATLONALT:1" [also 0878] [also 087C] FLT64 Lat=0, Lon=0, Alt=0 So, since the coding in FSUIPC5 in this area is identical to that in FSUIPC4, I can only conclude that it is a bug, or data timing error, in the SimConnect in FSX SP2. Have you never thought of updating at least to FSX-SE which had a number of corrections to bugs in FSX, and which was also recompiled with more modern versions of the compiler, leading to more efficient code. Alternatively, if you don't want to move to proper 64-bit, P3D3 would be a good choice. (Though I do not currently have dbugging facilities for either, I'm afraid). Pete Link to comment Share on other sites More sharing options...
Evander Posted March 11, 2020 Author Report Share Posted March 11, 2020 Ok, thanks for your effort. But how about offset 0874 he gives always the VOR?? Evan Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 11, 2020 Report Share Posted March 11, 2020 16 hours ago, Evander said: But how about offset 0874 he gives always the VOR?? For an ILS, the Glideslope location is 085C and the Localiser (which you are calling the VOR) is 0874. True VORs don't have LOC or GS. Pete Link to comment Share on other sites More sharing options...
Evander Posted March 12, 2020 Author Report Share Posted March 12, 2020 Ok, Everything is now clear. Thank you. Evan Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now