Jump to content
The simFlight Network Forums

thruster600

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by thruster600

  1. Pete, your deductions are spot on! I followed your instructions and now have a fully functioning altitude adjustment rotary! Thanks so much for resolving this for me.
  2. I haven't had a chance to post on the S-A forum yet, but I'll let you know what I find. I agree that someone else must have tackled this in the past, although several users on the S-A forum refer to commercial (engravity, opencockpits, etc.) MCP and CDU hardware. It may require a Lua plug-in to cope with my set-up so that'll be something else for me to learn!
  3. It appears that S-A is based on the altitude number, as I can't see an offset relating to the inc/dec buttons. Most other functions (eg. battery switch) are defined as buttons, set via offsets, with in some cases corresponding output offsets to allow reading of the switch state. In terms of widefs, S-A utilises a server application on the FSX machine, and my (proposed) set up runs all other S-A applications on a seperate low-spec PC. My hardware is connected to the FSX machine and configured in FSUIPC, and I presume the server application handles the communication to the low-spec machine displaying the MCP, Avionics, etc. From the S-A documentation, it would appear that WideFS could be used as part of the setup, but as my current configuration is only 2 PCs, and hardware is fairly limited at this stage, I do not need that level of complexity.
  4. No, S-A assignments are made exclusively through the use of offsets. I did a check and it doesn't react to the FS AP offset in 07D4. In theory, there is a button combo that can be used, but the MCP application runs on a seperate PC to the hardware, and I'm not running WideFS. The tools I mention simply allow you to monitor and write to offsets that you specify, running as part of the S-A server application. In my OP I noted that S-A state the altitude is a 4-byte value, and their "FSUIPC Help" document says that this can be known as "a DWORD or INTEGER or FLOAT32 or SINGLE depending on the usage" - therefore, as there appeared to be no DWORD INC choice in the drop down, I assumed Offset Float32 Inc/1000 would be the same format. If there's no DWORD inc option, then I agree I may be scuppered! Thanks for your prompt reply, Pete. I'll go to the S-A forums of course, and also check out MyCockpit. Once I've resolved this issue, I'll post back here.
  5. Hello Pete, I would appreciate if you could help me unravel a problem I'm having with FSUIPC (4.57) and Mark Hastings' Sim-Avionics (1.07) I have pored over the documentation for both FSUIPC and S-A and I'm still none the wiser. I have a Leo Bodnar card with connected rotary switches that FSUIPC sees as button presses. I am trying to get the MCP Altitude increment function to work from one of the button presses (clockwise rotation) and decrement from anti-clockwise rotation (seperate button), but I am completely stuck on what selection to make from the 'Control sent when button pressed' drop-down list, and what parameter to enter. Offset is x53A4, as shown below. From the S-A documentation: [FSUIPC_MCP_INPUTS] MCP_ALTITUDE=53A4 Note: MCP_ALTITUDE 4 bytes (Dword) {From S-A FSUIPC Help doc: 4 bytes (known as a DWORD or INTEGER or FLOAT32 or SINGLE depending on the usage) can store a whole number between 0-4294967296 or decimal values} // ALT = value ft /3.28084*65536 MCP_ALT_FS_FORMAT=1 MCP_ALTITUDE is expected FS formatting - like offsets 07D4. ie: 31700ft = 317(00) = 317 * 1997537 = 633219229 write 633219229 to the MCP_ALTITUDE offset Using the tools in S-A I am able to write the above specific value to the specific offset and I see the expected changes in S-A's MCP panel. I have tried several of the drop-down options, but without success. It would appear that I need the Offset Float32 Inc/1000 selection, but using this with a parameter of only 1 immediately pushes the value in x53A4 above the maximum limit of the MCP Altitude, and the S-A display goes straight to 41000ft, whereas I obviously need 100ft increments/decrements. Any guidance you can give me on this would be much appreciated! Cheers, Rob Bowers
×
×
  • 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.