daniekuys Posted September 16, 2003 Report Share Posted September 16, 2003 Hi Pete, Can you possibly shed some light on weird behaviour from these 2 pigeonholes. #Expanding the 16bit variable for the Radial from bytes 2-3 gives a variable that behaves as expected until the aircraft passes from radial 179 to 180. At that point the variable displayed jumps to 356 and carries on from there into the 400's and 500's, carrying a difference of about +176 over and above the actual expected value, until you cross from actual radial 359 (527) to radial 000. Then the variable value jumps back to 000 and carries on normally to 179. Looking at the Radial value with FS Interrogator, however, gives correct behaviour from radial 000 through 360 as expected Thanks a stack Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 16, 2003 Report Share Posted September 16, 2003 Can you possibly shed some light on weird behaviour from these 2 pigeonholes. I assume you are talking about EPICINFO? You don't actualy say. I'm sorry, but I don't use it any more so cannot really check what you are saying. But it has not been changed in years, and certainly the correct radial was always shown on my KR1 back when I used it. Can you use the logging facilities, please? That's what they are for. If you cannot understand the logging just send it to me and I'll check it for you. Regards, Pete Link to comment Share on other sites More sharing options...
daniekuys Posted September 17, 2003 Author Report Share Posted September 17, 2003 Hi Pete please look at the extract from my log file . Hoe do I construct a value from 0 to 360 . Up to 180 it seems quite easy, but what about 181 to 360? ********* EPICINFO Module, Version 4.21 (9SEP03) by Pete Dowson ********* Panel=AIRCRAFT\beech_king_air_350\panel.rmi\panel.cfg Epic Ref= Icarus-BE200 CFG: Reading C:\FS2002\EPICINFO.CFG ************************************************ CFG: Processing section [All] CFG: RESEND=0 ************************************************ CFG: Processing section [icarus-BE200] CFG: Log=2 CFG: LocInterceptZone=90,125 CFG: Sets=FUEL NAV CFG: WHISKEY_COMPASS_DEGREES=1 Frequency not set 27537 PH040 = 000 000, 00000 [Hex 00 00, 00 00], orig val=0 [0x0000000000000000] VOR1_SIGNAL_STRENGTH 27537 PH029 = 255 000, 00000 [Hex FF 00, 00 00], orig val=0 [0x0000000000000000] NAV1_VOR_RADIAL Frequency set on Radial 022 67332 PH040 = 007 027, 02707 [Hex 07 1B, 93 0A], orig val=2707.29 [0x40A5269700000000] VOR1_SIGNAL_STRENGTH 67332 PH029 = 022 000, 00022 [Hex 16 00, 16 00], orig val=4079 [0x40AFDDFFFFFFFFD5] NAV1_VOR_RADIAL Frequency set on Radial 068 154397 PH040 = 087 010, 01087 [Hex 57 0A, 3F 04], orig val=1087.16 [0x4090FCA880000000] VOR1_SIGNAL_STRENGTH 154397 PH029 = 068 001, 00168 [Hex 44 01, A8 00], orig val=30621 [0x40DDE73FFFFFFFD7] NAV1_VOR_RADIAL Frequency set on Radial 247 252753 PH040 = 054 010, 01054 [Hex 36 0A, 1E 04], orig val=1053.55 [0x4090762FE0000000] VOR1_SIGNAL_STRENGTH 252753 PH029 = 242 255, 65422 [Hex F2 FF, 8E FF], orig val=-20782 [0xC0D44B7FFFFFFFE5] NAV1_VOR_RADIAL Frequency set on Radial 289 283343 PH040 = 034 009, 00934 [Hex 22 09, A6 03], orig val=933.594 [0x408D2CC060000000] VOR1_SIGNAL_STRENGTH 283343 PH029 = 184 000, 65464 [Hex B8 00, B8 FF], orig val=-13076 [0xC0C989FFFFFFFFDE] NAV1_VOR_RADIAL Frequency set on Radial 333 322227 PH029 = 228 000, 65508 [Hex E4 00, E4 FF], orig val=-5020 [0xC0B39BFFFFFFFFE6] NAV1_VOR_RADIAL 322227 PH040 = 006 009, 00906 [Hex 06 09, 8A 03], orig val=906.495 [0x408C53F5E0000000] VOR1_SIGNAL_STRENGTH Frequency set on Radial 009 351482 PH029 = 009 000, 00009 [Hex 09 00, 09 00], orig val=1642 [0x4099A7FFFFFFFFDE] NAV1_VOR_RADIAL 351482 PH040 = 019 008, 00819 [Hex 13 08, 33 03], orig val=819.067 [0x4089988860000000] VOR1_SIGNAL_STRENGTH Frequency set on Radial 091 372483 PH040 = 006 007, 00706 [Hex 06 07, C2 02], orig val=705.73 [0x40860DD780000000] VOR1_SIGNAL_STRENGTH 372483 PH029 = 091 000, 00091 [Hex 5B 00, 5B 00], orig val=16562 [0x40D02C7FFFFFFFEA] NAV1_VOR_RADIAL Frequency not set 384822 PH040 = 000 000, 00000 [Hex 00 00, 00 00], orig val=0 [0x0000000000000000] VOR1_SIGNAL_STRENGTH 384822 PH029 = 255 000, 00000 [Hex FF 00, 00 00], orig val=0 [0x0000000000000000] NAV1_VOR_RADIAL 425873 QP101 = Kill Done CFG: Mouse positions cleared ********* EPICINFO Log file closed ********* Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 17, 2003 Report Share Posted September 17, 2003 Hoe do I construct a value from 0 to 360 . Up to 180 it seems quite easy, but what about 181 to 360? The values 181 to 359 are arriving as negative numbers, which is screwing things in bytes 0 and 1 up a bit. Is this with FS2004? I'll look to see if this has changed. If so I'll see if it can be fixed. The data is actually there though, if you want to use it as it stands. ============== Frequency set on Radial 068 154397 PH029 = 068 001, 00168 [Hex 44 01, A8 00], orig val=30621 This is 168, not 68. If you are only reading the first byte you will get the units and tens only. The 3rd-4th bytes give the correct binary, the 1st and 2nd are split inot units, tens in one, hundreds and thoiusands in the other. This is for the convenience of some display systems. It is all covered in the documentation. It is going wrong for the -ve values it is receiving -- I think this must have changed in FS2004, if that is what you are using: Frequency set on Radial 247 252753 PH029 = 242 255, 65422 [Hex F2 FF, 8E FF], orig val=-20782 [0xC0D44B7FFFFFFFE5] NAV1_VOR_RADIAL This -20782 value represents -114, as in bytes 3-4 of the PH (65422 is 16-bit -114). -114 is the same as +246 (not 247). Frequency set on Radial 289 283343 PH029 = 184 000, 65464 [Hex B8 00, B8 FF], orig val=-13076 [0xC0C989FFFFFFFFDE] NAV1_VOR_RADIAL 65464 is -72 which is the same as +288, not 289. Frequency set on Radial 333 322227 PH029 = 228 000, 65508 [Hex E4 00, E4 FF], orig val=-5020 [0xC0B39BFFFFFFFFE6] NAV1_VOR_RADIAL 65508 is -28, which is the same as +332 not 333. ================= So, you see, you can derive the correct positive number. But if you'd like to wait a couple of days, I'll look to see what has changed. Derivation: if top bit of 4th byte is set, then do this: value = 360 - (256 - 3rd byte). i.e. 104 + 3rd byte. Regards, Pete 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