How to interface FSUIPC based software
How to interface FSUIPC based software
I am very happy with the Air Manager software.
I do not use it for gauge building but for interfacing with my hardware by Arduino.
I am planning to use AM to interface my entire Learjet 45 home cockpit, but my avionics software (Jet45), like other suites use FSUIPC to interface.
Is there a way i can communicate with AM to my Jet45 suite?
I am afraid i have to fall back to MobiFlight instead.
I do not use it for gauge building but for interfacing with my hardware by Arduino.
I am planning to use AM to interface my entire Learjet 45 home cockpit, but my avionics software (Jet45), like other suites use FSUIPC to interface.
Is there a way i can communicate with AM to my Jet45 suite?
I am afraid i have to fall back to MobiFlight instead.
Re: How to interface FSUIPC based software
Found with the search function
https://siminnovations.com/forums/viewt ... ipc#p25717
https://siminnovations.com/forums/viewt ... ipc#p25717
Re: How to interface FSUIPC based software
What simulator are you on?
I did data exchange with Air Manager and FSUIPC in FSX.
I did data exchange with Air Manager and FSUIPC in FSX.
Re: How to interface FSUIPC based software
Why would you need FSUIPC?
Re: How to interface FSUIPC based software
First off I'm an Air Manager fan since day 1 and no fan at all of FSUIPC.
I can't speak for@Shimokuta but for me in FSX it was useful. Some add-on developers created controls that can only be operated by mouse clicks. No key to assign to, no LVar to read/set, no XML gauge to edit but FSUIPC has this thing called mouse macro where it records your action and then sends it even without the panel being visible.
As outdated as it may be, FSUIPC did solve a problem for me there.
I can't speak for@Shimokuta but for me in FSX it was useful. Some add-on developers created controls that can only be operated by mouse clicks. No key to assign to, no LVar to read/set, no XML gauge to edit but FSUIPC has this thing called mouse macro where it records your action and then sends it even without the panel being visible.
As outdated as it may be, FSUIPC did solve a problem for me there.
Re: How to interface FSUIPC based software
I used data transfer from FSUIPC to Air Manager on P3D.
FSUIPC had access to some text data (ATC, messages, etc.) not available in Air Manager.
I had a LUA script in FSUIPC that read these text messages and write them in a text file.
It then write a code in an unused SimConnect variables.
I created an instrument in AM. I used fsx_variable_subscribe() in my instrument to be warned when a new text was available.
I can then read the text with static_data_load(), process the file based on the parameter code and display the text in the instrument.
It used the same technique with another variable to send messages from AM to FSUIPC.
Seems complicated but it worked.
FSUIPC had access to some text data (ATC, messages, etc.) not available in Air Manager.
I had a LUA script in FSUIPC that read these text messages and write them in a text file.
It then write a code in an unused SimConnect variables.
I created an instrument in AM. I used fsx_variable_subscribe() in my instrument to be warned when a new text was available.
I can then read the text with static_data_load(), process the file based on the parameter code and display the text in the instrument.
It used the same technique with another variable to send messages from AM to FSUIPC.
Seems complicated but it worked.
Re: How to interface FSUIPC based software
What I did instead of unused SimConnect variables was create a simple XML gauge where I'd introduce new LVars.
FSUIPC can write to them, Air Manager will find them as "available LVars".
You can see this in my instrument "Vertical speed indicator / VSI with traffic display for ATR-500" in the store.
This sample XML code will create 3 user defined variables in an FSX aircraft. There is no declaration, they exist just by being used.
FSUIPC can write to them, Air Manager will find them as "available LVars".
You can see this in my instrument "Vertical speed indicator / VSI with traffic display for ATR-500" in the store.
This sample XML code will create 3 user defined variables in an FSX aircraft. There is no declaration, they exist just by being used.
Code: Select all
<Gauge Name="TrafficInfo" Version="1.0">
<Size X="400" Y="300" />
<Update Frequency="5" Hidden="No">
<!-- Clear old values -->
0 (>L:TCAS_bearing,degrees)
(>L:TCAS_distance,nmiles)
(>L:TCAS_altitude, feet)
[...]
</Update>
</Gauge>
Re: How to interface FSUIPC based software
Well ADD-ON software developers use FSUIPC interface with the for developers available FSUIPC Offsets.
They wrote coding round those offsets which i can not use.
I know things are changing with new versions and all, but so far i am missing functionality and still have the need for FSUIPC
Re: How to interface FSUIPC based software
Ah ok....that is interesting!!flyatr wrote: ↑Sat Feb 20, 2021 1:52 pm What I did instead of unused SimConnect variables was create a simple XML gauge where I'd introduce new LVars.
FSUIPC can write to them, Air Manager will find them as "available LVars".
You can see this in my instrument "Vertical speed indicator / VSI with traffic display for ATR-500" in the store.
This sample XML code will create 3 user defined variables in an FSX aircraft. There is no declaration, they exist just by being used.Code: Select all
<Gauge Name="TrafficInfo" Version="1.0"> <Size X="400" Y="300" /> <Update Frequency="5" Hidden="No"> <!-- Clear old values --> 0 (>L:TCAS_bearing,degrees) (>L:TCAS_distance,nmiles) (>L:TCAS_altitude, feet) [...] </Update> </Gauge>
thx