Page 1 of 3 123 LastLast
Results 1 to 10 of 21
  1. #1
    75+ Posting Member
    Join Date
    Jan 2005
    Posts
    75
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Cant assign "BELOW GLIDESCOPE/PULL UP" annunciator and such

    Hi everyone,
    Can some one tell me if its possible to assign this annunciator for my 737 cockpit that Im biulding.
    I see that there are some items that I cant seem to find to assign to activate for my 64LED board. They dont require a digital input.
    Also:
    "LE FLAPS TRANS" indicating they are moving.
    I find that only certain assigned items can be calibrated also.Is this normal?


    . The items I am selecting should be activated by MS2004 default aircraft.
    Mabe the listing in the software is described a bit different then what Im looking for mabe? :confused:

    Kind regards
    James

  2. #2
    alandyer
    Guest
    James,

    Is there an FSUIPC offset for the functionality you are looking for ?

    If answer is yes, you can get it to work.
    If no, then there is no way with any software I know of.

    There are offsets for flap position.
    Assign and enable them and you will see FSvalue change as flaps extend or retract.
    FSUIPC has tools to examine Offsets while FS or pmSystems is running.
    FSUIPC SDK has copious documentation on their Offsets.

    Why would you assign annunciators to digital input ?
    Digital output, surely!

    and have I checked each and every offset for Microsoft Flight Simulator and pmSystems in the supplied INI file ?
    and have I checked each of those against every Phidget componenet type ?
    and have I checked all the above permutations against each aircraft type ?
    Short answer: No.

    Too busy building B737-700 sim!!!

    Regards,
    Alan

  3. #3
    75+ Posting Member
    Join Date
    Jan 2005
    Posts
    75
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Hi Alan,
    I have spent the week trying to figure out my "BELOW GLIDESLOPE" annunciator
    dilemma having it attached to my LED64 board.May I ask your assistance on this
    issue?
    If you find that their is no way possible..I will let it rest at that.
    I'm totally stumped and out of ideas. :confused:

    Kind regards
    James

  4. #4
    imported_sweker
    Guest
    Evening James,
    I have been an avid Flight Simmer for 15 years, but have only joined the cockpit builders community within the last year. I have been researching 'Phidgets' as my interface hardware, but have not yet purchased it. Regardless, in reading this forum, I think your answer might be found in some of the other questions.

    Again, I may be way off, but take a look at the following offset and see if you can assign a certain value for your annunciator to activate. If you note while flying within FS2004, the 'Below Glideslope' comes on at a point when the needle hits a certain 'threshold' (bottom 1/4 of the glidescope indicator).....Give it a try...can't hurt....

    0C49 1 NAV1 Glideslope Needle: –127 up to +127 down

    Let me know if it works.

    Steve

  5. #5
    75+ Posting Member
    Join Date
    Jan 2005
    Posts
    75
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Thanks Steve,
    I will try anything at this point.
    Have you seen this listed in the drop down choices exactly like that? because this is a LED 64 board that Im using and
    I would have to assume to make a copy of what is closest to that and rename it slightly different and then work from there in the pidgetfsuipc.ini file.

    Ill give it a try and report back
    Thanks for your ideas!
    James

  6. #6
    alandyer
    Guest
    Steve,
    Thanks, Capt.
    You're right on the money!

    James,

    Step 1: Identify Offset.
    Courtesy of Steve we're past Step 1.

    Step 2: Verify that Offset is in your FS2PhUIPC.ini file

    If Not, add these entries (can get em from FSUIPC documentation).

    [NAV1_GS_NEEDLE]
    Offset=0C49
    Length=1
    FSType=Proportional
    LoValue=-127
    HiValue=127

    Instead of [NAV1_GS_NEEDLE] you could have [MY_OFFSET_DESCRIPTION]

    Now on to Step 3: Examine Offset values coming from FS.

    Here's easy way to do this (Does not require Phidget card).
    Create a Dummy Tab (button is on tool bar of main screen).
    Assign NAV1_GS_NEEDLE to any line on Dummy Tab.
    Don't forget to ENABLE component.
    Save those settings!!!!!!!

    Fire up FS.
    Fire up WideClient (if FS2Phidget is on different PC from FS).
    Fire up FS2Phidgets.
    That saved setting will be restored every time Dummy tab is opened again.

    Play around with Flight Sim:
    (a) Shoot an approach.
    or
    (b) Taxi to somewhere along extended runway center line of ILS approach path.
    Preferably out to the Middle Marker.
    Also, you want to make sure you're centered on the localizer.
    Use slew mode and pretend you're flying a Harrier for a while.
    This will allow you to drop above, below and smack onto G/S while observing G/S needle.
    Hint: write observations down (Not FAA requirement, just good tip
    You should get good feel for Values.

    Step 4:
    Hook up hardware and calibrate "On" range for LED as well as brightness
    (Yes - that can be set now!) based on your observations.

    Regards,
    Alan.

  7. #7
    75+ Posting Member
    Join Date
    Jan 2005
    Posts
    75
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Hi Alan,
    Well I entered the following :
    [NAV1_GS_NEEDLE_BELOWGLIDESLOPE]
    Offset=OC49
    Length=1
    FSType=Proportional
    LoValue=127
    HiValue=127

    and then I got an ERROR 6 and it shut down

    When I changed it back to
    [NAV1_GS_NEEDLE]
    Offset=OC49
    Length=1
    FSType=Proportional
    LoValue=127
    HiValue=127

    and proceeded to go into the calibration screen it said"invalid property error"
    I even downloaded the newer version also.

    So what do you think?
    James :confused:

  8. #8
    imported_sweker
    Guest
    Hey Guys,
    Glad I could help....actually amazed I was on the right track! I've also decided that Phidgets is for me, and I'll be ordering my first one soon. It took awhile to understand how everything interacts, but using all the available doc's (i.e. FSUIPC guide) and forums really help.

    James, maybe there is a character length restriction on the name, or perhaps it didn't save properly before you exited.

    Once I get my first unit, I'll be able to help out a bit more.

    Cheers, Steve

  9. #9
    imported_sweker
    Guest
    Thanks Al,
    I appreciate the vote of confidence. I've been reading for a long time about interface units to ensure I understand how they work and determine which one is relatively easy to work with. Needless to say, Phidgets has me sold! I'll be purchasing my first unit tonight.

    James,
    Not sure if I can help with this one, but when I get my first unit, I'd be glad to work together to get both set-ups working....

    Cheers, Steve

  10. #10
    75+ Posting Member
    Join Date
    Jan 2005
    Posts
    75
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    I got it to work... Finally!!

Page 1 of 3 123 LastLast

Similar Threads

  1. Replies: 0
    Last Post: 03-23-2010, 01:31 PM
  2. Real Flight Simulators versus PC "Games" - the eternal debate...
    By ryanf in forum Pilots Lounge - Let your Hair down
    Replies: 3
    Last Post: 01-01-2010, 06:32 PM
  3. Replies: 17
    Last Post: 03-05-2008, 12:39 PM
  4. Gwyn Perrett's Article "Creating a glass cockpit display"
    By Matt Olieman in forum General Builder Questions All Aircraft Types
    Replies: 0
    Last Post: 08-31-2007, 07:20 PM