Jump to content
The simFlight Network Forums

birdstrike

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by birdstrike

  1. Hello Pete I'm bringing back up this topic, as I would like a little clarification on a (easier) way to write the NAV freq. in fsuipc. I succesfully managed to interface the NAV radio last year, but i had to write a line in fsuipc for each an every radio frequency, which took me some time to do as you might imagine. Ex: I had to write a line of key-combinations for freq. 108.00, one for 108.05, one for 109.00 etc. It works perfectly good, no need to change it or write a new script. BUT I am now going to interface a second NAV radio + two COM radios. I can't stand to think about the amount of time I'll have to spend writing fsuipc lines for all of these radios to work! Therefore I was thinking, that there might be an easier way to do this? I have a series of buttons. Lets say button1 is pressed, Can that set the ten'th in the freq. ie. 108.00 Button2 pressed = 109.00 Button3 pressed = 110.00 ... and so on... And button10 to set the decimal: 108.10 Button11 = 108.20 ... and so on... That would make the job a lot more simpel! :) Thanks.
  2. Thanks a lot for your help Pete. Really appreciate it! :) Regards Lasse
  3. This particular Collins adf operate from 190.00 to 400.00 in one band and 400.00 to 840.00 in another. I might be mistaken but are ndb's used for aviation not allways within 200 to around 535 khz? If so the pot would "only" need 400 positions in one band and 270 in the other. When i go to axis calibrating in fsuipc, i'm able to choose an axis value and assign it to set a specific adf freq. Have i understood correctly that the decimals (ie. if i want to tune 390.00) i have to convert 390.00 to binary-coded decimal? / Lasse
  4. Thanks for the reply Pete. I'm aware of the hardware interface using the Bodnar cards, i was thinking more of the programming part of it. I have had some time thinking about how to approach this, and this particular adf unit is not straight forward! What i mean about this is that 'normally' one would work with an adf panel showing digits ie. 390.00 khz. But here, as you might imagine, i have no way of knowing wether the adf is tuned to 390.00 or 392.00. So i was thinking that one way of approaching this problem would be to make the adf tune several frequencies at the same time. For instance lats say that i 'physically' tune 390.00 on the adf hardware. The frequency band would indicate .39. But the potentiometer might read 392.00 or maybe 388.05 khz. But if the adf is programmed to tune +/- 2 khz (for 390.00 it would be 388.00, 388.05, 389.00, 389.05 etc.) it would tune - and recieve if within range of the station - the ndb that i want. Would that be possible with some .ini editing? Thanks a lot for any help here! Lasse
  5. Hello, I was wondering how i can assign a rotary potentiometer to tune an adf station? I'm in the progress of interfacing this real Collins adf, and as the tuner does'nt have detends like rotary switches found on COM and NAV radios, i guess the only way is to use a potentiometer. Thanks, Lasse
  6. I know that you under 'normal circumstances' would adjust the radio frequencies, but I've interfaced a real com/nav control panel with the analog tape numbers as you can see in the picture below. The thing is that it works like two rotary switches. One controls the 100's and the other one controls the .00's. For instance; If I tune 108.10, the number one rotary switch (which is interfaced through a BUO836X card) presses button #1, #2 & #3. The second rotary switch is pressing button #11 & #12. If I rotate the #1 rotary switch one detent to the right, the tape display will show 109.10. Now the rotary switch is pressing down button #1, #2 & #4 and the second rotary switch will remain the same as before. For this reason I'm not able to program the settings through the FSUIPC options window in FS9 as I'm using a combination of keys. Is there any straight-forward logic in FSUIPC changing the parameter x10880 to 67712? -------------------------------------------------------------- Something else I just discovered I have a problem with: The button numbers in the windows game control does not match the button numbers within FSUIPC. However; it works perfectly when assigning buttons in FS9. It's the same for all my joystick cards. Thanks!
  7. Hi, I really need to be pointed in the right direction here! :) I'm not a great programmer (yet) but has a basic understanding about fsuipc, the language etc. and have successfully used fsuipc, sioc etc. for my cockpit project. But now it gets a little bit more advanced.. Basically I need the NAV1 freq to be - lets say 108.80 when i press button 2, 3 & 4 on joy1. How would this look in fsuipc.ini? Thanks for any help in advance! I really appreciate it. :)
  8. Ok, I understand the principle but having some troubles figuring out how to write this in sioc. Here's what I've got now: --------------------------------------------------------------------------------------------- Var 0001, name gs_alive, Link FSUIPC_INOUT, Offset $0C4C, Length 1 { IF &gs_alive = 1 { &gs_alive_ind = 1 } IF &gs_alive = 0 { &gs_alive_ind = 0 } } Var 0002, name gs_alive_ind, Link IOCARD_OUT, Device 1, Output 39 Var 0003, name loc_tuned, Link FSUIPC_INOUT, Offset $0C4A, Length 1 { IF &loc_tuned = 1 { &loc_tuned_ind = 1 } IF &loc_tuned = 0 { &loc_tuned_ind = 0 } } Var 0004, name loc_tuned_ind, Link IOCARD_OUT, Device 1, Output 41 ---------------------------------------------------------------------------------------------- Obviously the Loc tuned in feature works, but how can I add the needle position? And the same for the Glideslope? I did a test here for the GS, to see if anything happened when it came alive. Unfortunately nothing happened. - Lasse
  9. Hi Nico, When in the offset-list it says under 0C4C "NAV1 GS flag: TRUE if GS alive" what excactly does that mean? I did a quick test on my pc, but the GS doesn't work. Thanks for your time, Lasse
  10. Good evening fellow simmers & cockpitbuilders. :) I'd basically like to make an LED illuminate, as my aircraft capture the localiser, and another one when I capture the glideslope. But I'm not really sure to which offsets I should pay attention. My guess would be to use the offset 0C48 for the localiser needle, and the 0C49 for the glideslope needle. Lets say I'm using the 0C48 to register when i capture the localiser. When the parameters gets between -127 & +127 the localiser needle will be active. Is this correct? Thanks! Lasse
  11. The thing is that I'm flying the Boeing 727. This aircraft has an older autopilot (Honeywell Sperry SP-150). Basicly it only has two main functions. The HDG SEL, which turns the aeroplane to the requested heading (set on the HSI), and ALT HOLD which makes the airplane maintain the altitude it was at when the ALT HOLD was selected. This old autopilot does'nt have a altitude display, therefore the autopilot cannot climb or descent to a preset altitude. By "desired" i meant the altitude fsuipc (or fs?) was telling the aircraft to maintain. Regards, Lasse
  12. Where do I find the desired altitude? I've created a log file to see what happens, but it only shows me the ALT_HOLD_ON. Regards, Lasse
  13. Thanks for the quick reply Pete. I've done as you've suggested, but it does'nt seem to apply any difference. The ac still exceeds the altitude at which the ALT HOLD is selected, then it levels of to maintain a slightly higher altitude. Regards, Lasse
  14. Hello I'm working on a old Honeywell Sperry SP-150 autopilot, and has so far managed to interface all the functions by modifying the .INI file. The only trouble I'm experiencing is the ALT HOLD function. The aircraft should maintain the altitude it was at, when the switch was engaged. (It usually means that the aircraft levells of, and then descents/climbs to adjust the altitude) As far as I'm concerned the FSUIPC command is AP_ALT_VAR_SET_ENGLISH. The "control nr." is 66124 - and here's the problem - the parameter changes depending on the altitude. (i.e. the parameter would be 35000 if the ALT HOLD was engaged at fl350) The line under the "buttons section" in the .INI file would in this case look like this: #=P1,xx,C66124,35000 But how can I make the parameter change depending on the ac's actual altitude? P.s. I'm using fs9 and the DreamFleet 727. Thanks, Lasse
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.