Assigning events to an axis to allow calibration

[Brian McCrary]

I'm using FSUIPC 7.5.1 and it has been working great for years, but the elevator trim has always been unusable as it's way too jumpy.  I finally decided to see if I could fix this.  With other axes, I can fix issues like this with by using the joystick calibration tab.

The main issue here is that I'm using a control by Elite which runs over a RS232 serial port and has it's own totally unsupported piece of software that is basically an "event sender" to FSUIPC.  There is no usual Windows joystick interface and the controls are not seen by the OS or FSUIPC at all, just the events, so I can't use the rescan function in the GUI.  With that said, as an example, the events like this work fine and can be seen on the joystick calibration tab, as well as many others:

    50265  6248 ***  AXIS: Cntrl= 65762 (0x000100e2), Param= -1544 (0xfffff9f8) AXIS_ELEVATOR_SET
  2698890  6248 ***  AXIS: Cntrl= 65763 (0x000100e3), Param= -7630 (0xffffe232) AXIS_AILERONS_SET
   139359  6248 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 564 (0x00000234) THROTTLE1_SET

However, the elevator trim does not show up anywhere.  I would think it would show up on page 6 of the calibration tab where the elevator trim is listed, but I am guessing FSUIPC is expecting to see something else there.  The event I get for the trim from my controls is:

   173156  6248 ***  AXIS: Cntrl= 65706 (0x000100aa), Param= -156 (0xffffff64) ELEVATOR_TRIM_SET

FWIW, it does actually work and set the trim, it's just it really could use some calibration to be at all useful.  I just see all zeros in the elevator trim part of the calibration.

Is there a way to assign it through a config file perhaps since I can't use the GUI rescan feature?  I apologize if I've missed this in the manuals.  I may just be searching for the wrong thing.

 

[John Dowson]

44 minutes ago, Brian McCrary said:

The main issue here is that I'm using a control by Elite which runs over a RS232 serial port and has it's own totally unsupported piece of software that is basically an "event sender" to FSUIPC.  There is no usual Windows joystick interface and the controls are not seen by the OS or FSUIPC at all, just the events, so I can't use the rescan function in the GUI.

I am not sure I understand this - how is your controller assigned, in FSUIPC or elsewhere? The software cannot send such events to FSUIPC and all events are received from the FS.
So I suspect that it is the Elite software that is sending the events to the FS, and then FSUIPC is receiving them for logging purposes and possibly for calibration.

It should be possible to calibrate such events when not assigned in FSUIPC or when assigned but not with 'Send direct to FSUIPC Calibration', as long as the ini parameter AllowSendToFSCalibration is not set to No. If you cannot see any movement in the elevator trim calibration tab, could you please activate logging for Axes Controls, load your aircraft, move the assigned elevator trim axis through its full range and back again, exit FSUIPC7 and show me / attach your FSUIPC7.log and FSUIPC7.ini files.

John

[Brian McCrary]

On 1/16/2025 at 11:20 AM, John Dowson said:

I am not sure I understand this - how is your controller assigned, in FSUIPC or elsewhere? The software cannot send such events to FSUIPC and all events are received from the FS.
So I suspect that it is the Elite software that is sending the events to the FS, and then FSUIPC is receiving them for logging purposes and possibly for calibration.

It should be possible to calibrate such events when not assigned in FSUIPC or when assigned but not with 'Send direct to FSUIPC Calibration', as long as the ini parameter AllowSendToFSCalibration is not set to No. If you cannot see any movement in the elevator trim calibration tab, could you please activate logging for Axes Controls, load your aircraft, move the assigned elevator trim axis through its full range and back again, exit FSUIPC7 and show me / attach your FSUIPC7.log and FSUIPC7.ini files.

John

Thanks for your reply.  I am really not sure how it connects, although I did see this in the log file which might help:
    10031  5684 AppKey="SVPEU7YI8USJ", Module="EliteFSX.DLL

The EliteFSX.DLL is a DLL that comes with Elite's program and the Elite log, which says very little, does have this in it:

       0.015: SimConnect opened.
       0.015: Running in "KittyHawk", v11.0.282174.999 (SimConnect v11.0.62651.3).
       0.219: Reading FSUIPC version...
       0.250: FSUIPC version 0x7501 found.
       0.250: Connection to FSUIPC successfully established

So it appears it's able to connect somehow to FSUIPC but unfortunately after going through all of the little documentation I have on the driver, I can't find out much else.  It only says to consult FSUIPC's SDK for additional information, but that's the only place it's mentioned in their entire "User Guide".  I attached a ZIP with the log files from FSUIPC.  Thanks again, I really appreciate it!

 

FSUIPC_logs.zip