Jump to content
The simFlight Network Forums

Erups

Members
  • Posts

    46
  • Joined

  • Last visited

Posts posted by Erups

  1. Philippe, Peter advice to use FSI is good, but be warned: FSI may be vicious.

    Assuming that any offset occupies AT LEAST 2 bytes (which is true for the majority of values, but there are exceptions) every row of FSI is a 2 bytes offset.

    Then the columns do support I64 values and other big things.

    This all contrast as you may end up looking at a value in a raw, and see something change in the row above and getting confused.

    It's because there is no clear division in FSI, everything is read and not categorized.

    There are no 2 bytes offsets, or 8 bytes offsets.

    The longest offsets (like file pointers, or coordinate values) do not exist: they are simply splitted in a number of words.

    So it's up to you to keep this in mind and not be fooled by some of the FSI shows.

    My 2 cents :)

  2. You need FSUIPC registered, then under the "buttons" tab you have to do the following:

    -press the joystick button you want to program, it should get recognized by FSUIPC and appear in the upper line

    -on the right mark "select for FS control"

    -the drop down list that was grayed out is now usable

    -select "offset byte control"

    and in the fields enter the informations provided by Peter.

    That's it.

  3. About the rotaries:

    it is possible to think of a system in which the phased outputs of the encoders are common.

    In such a system you have only one direction/pulse decoder, but you have to check the grounds of all the encoders...

    You are simply shifting the problem from the output to the input.

    I mean: usually encoders have ground in common, and the phased outputs are read for each encoder.

    It is possible (in theory) to make a device in which the outputs are in common, and you check the grounds, but it requires a very complicated circuitry. Better to use the standard system...

    About the axis control: sadly FS itself only disables the throttle, all the other axis remain active while in autoflight.

  4. I try to explain what is the problem here:

    when you assign a keyboard function to an hardware button, many things may happen.

    All of which you can simulate with your keyboard and a finger.

    If you assign the actions "ON" and "OFF" to a hardware momentary button, when you press it it's like pressing the "L" key two times.

    You get the lights on and off rapidly.

    Then, if you also turn on in fsuipc the "AUTOREPEAT" function, holding down the button, will result in a repeated continous press and release of the L key, resuling in the strobing effect.

    So you have to check what Peter told you about toggle and momentary.

    Toggle switches are those which hold their position (like lever switches), momentary are those which hold the position only as long as you keep them pressed (like for example the keyes on your keyboard).

    So if you assign a momentary action to a toggle switch, you will get repeated actions.

    So please try to check you are using the correct type of action for your hardware.

    If you have a two state knob or switch, use LANDING LIGHTS ON and LANDING LIGHTS OFF types for the two states of the knob/switch.

    Hope this helps.

  5. For example, take the string "Pete". Inside the computer, in ASCII, this is 4 bytes (one per character) plus a zero terminator. Ignoring the latter for the moment, the 4 bytes in hexadecimal would contain:

    50 65 74 65

    Pete, sorry to bring this thread up again, but here i need to know:

    which one is wrong between your statement above and this ascii table? http://www.asciitable.com/

    Please, forgive me, i do not intend to just point out your errors, i really need to know which one is right for an article i'm writing.

    Thank you

    Claudio

  6. can do it by program. Either use the FSUIPC facility but switch it off (offset 32F6) whilst the APU is not running (and no Ground Power is available -- don't forget the ground power option! :) ).

    He he :)

    First i must have the electrical system running correctly (which is a very tough work), after that i can see to retrofit my plane with the 115vac plug :D

    About the 32F6, this is a control bit, so i have to enter a number in the fsuipc setup in order for it to work.

    I can't do this:

    when apu running stop dischargeing battery

    when apu not running, discharge battery

    This would need control on the "extend battery life" value which is not possible :(

    Or you can investigate manipulating the battery directly -- offset 2834 should be useful.

    So the battery charge is based on the voltage output readable from this offset?

    I have to do some testing about this...

    Thank you for the info, usefull as usual :)

    Claudio

  7. FSUIPC provides control over excessive battery discharge.

    But is this "discharge" percentage available to users?

    I haven't found anything about it.

    I would like to simulate an apu and have the battery discharge stop when the apu gens are connected (like some commercial products do) but i can't find the controls.

    Thanks

    Claudio

×
×
  • 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.