alaxus

Update No2 Enrico got back to me. It seems offset 5418 is a bit outdated and there are other offsets to use. Enrico mentioned 540C for V/s instead of 5418 bit 14/15. Bit 15 seems to be a tricky thing to handle. Seems also offsets 5406, 5408, 540A, and 540E are used as well. Time to bark up another tree I guess :) Thanks Jeff

Hi Pete, just a quick update. I went through the logs and pick out the offsets that are being written, then monitored each one. Off all the offsets I look at, the following were the ones affected by offset 5418. 0330 is set to 16208 when offset 5418 bit 15 is written to. 04F4 cycles between value 3 and 102 when offset 5418 bit 15 is written to. <--- this seems to cause my ND issues. 5524 cycles between value 1 and 2 when offset 5418 bit 15 is written to. Other than 0330 the other 2 offsets are PM ones, which explains my ND issues. On a side note I set offset 5418 bit 14/15 to joystick button to see if there was a difference. When using the button I have none of the current issues. Jeff

Thanks again Pete, Looks like I have some more work to do. I will post back with more info if need be. Jeff

Thanks for the quick reply Pete. I am afraid I cant see into Alan's programming of fs2phidgets. I was just looking for something specific to help him chase down a problem for me. I could understand if it was going to 29.92, but 29.91 is just wierd, and that it also affects the PMRJ ND screen as well, and the HSI, seems to me it might be something internal with PMRJ. I was thinking that it may be a fs2phidget problem of writing to the wrong offsets, but if it only writes to offset 5418 bit 15, then it must be the way PMRJ handles it internally. Thanks Jeff Ps I will do some more logging and see what I can dig up.

Hi Pete, I have a issue where offset 5418 bit pair 14/15 affects my baro setting. In this case Offset 5418 bit pair 14/15 is the V/S setting for PM MCP. When offset 5418 bit 15 is accessed my baro setting goes to 29.91 regardless of where it was previously set. At the moment I am using fs2phidgets and a phidget encoder to do the v/s settings. All other bit pairs on this offset work fine just bit 15 is a problem. I have looked at the fsuipc logs and broken it down to just reads and writes and I cant find anywhere where the baro offset is written. Could you tell me what offset would specifically write 29.91 to the baro setting so I know what to look for in the logs. Here's a excerpt of an email I sent Enrico, Thanks Jeff

Ok, I have found a work around. Now I just press the button mapped to N and then the button mapped to N2 not real elegant, but works for now. Thanks again for you help Jeff

Yeah I will probably go down that road it seems to be the better solution. thanks again for all your help. Jeff

I think it is in the way the keypresses are delivered. press N and you can change whole numbers on Nav1. press NN and you change fractional numbers on Nav1 This is why nav 1 is easy, have a joystick button mapped to N and works fine. For nav2: press N2 to change whole numbers (which I can get by mapping N to a press and 2 to a release in fsuipc) press NN2 to change fractionals <-- this is the problem I cant get the button to imitate this. I think my problem is very unique, maybe its not able to be done this way with just one button. It would be so much easier if FS had a keyboard (or joy) command to go straight to the NAV 2 fractional selection and whole numbers for that matter rather than pressing N's and #'s. That being said 1 rotary per frequency as in the 737 would solve the problem. Unfortunatley the Lear dosent have that feature. On a side note I tried using NAV 2 Set in the buttons and key presses section of fsuipc but to no avail, i have no idea what this does. Thanks again, I think I will have to try and nut it out, there has got to be a solution somewhere. Jeff

yep, sorry. yep they can. The rotary encoder is sending the keypresses + / - to increase and decrease selection depending on which radio was being tuned. To put it simply. I cant select the fractional numbers on nav 2. I can get the whole numbers if i use fsuipc's keysend function using N on press and 2 on release. On nav 1 I also use the keypress feature and just send a N to fs, once for whole numbers and twice for fractionals. (twice in quick sucession) In fs that would be key presses N 2 for whole then N2 N2 for fractionals. This dosent seem to work very well even using the keyboard. Its very hit and miss. Was afraid of that. Ok, great I will look into to that as well. Thanks again for all your help, I have only used fsuipc for a few weeks and have been finding it very helpful. Jeff

PM are just mimicing the standard lear radiostack. All commands are going through FS direct. Except for the rotary encoder. This is a phidget running through wideFS sending keystrokes - / +. Oops didnt see that in the doc. I do have FSX just waiting on the key for fsuipc for fsx. I just checked again, it is N1 N2. And I was using the + /- keypresses through the rotary encoder. yep thats it, I can select the the first three digits of the frequency, just not the last 2. Yep I have tried them as well. I was just thinking if I had a rotary for each radio I wouldnt have a problem. Ok I will do some more reading into that. (Baileys on the rocks, with the fsuipc manual to read, sounds good) Anyway thanks for you help in this, I was hoping that FSX would have cleared that problem up, but it works the same as fs9. Jeff

I am using the pmrj suite and the setup I have for the radio uses one rotary encoder to change the values on the com and nav radios including the transponder and adf. Now they all work except for Nav 2. I just cant seem to be able to select the .xx digits. I was trying to use offset 0374 but cant work out how to get it to work in fsuipc. Basically its just a joystick button mapped through fsuipc, but am unsure of which selection to use. Previously I was using the keysend feature ( N2) to select the nav 2 radio. Any ideas welcome. Jeff