John Dowson

Yes, that is correct. However, it is far easier, and recommended, to access hvars using either presets or calculator code directly rather than using *.hvar files to make the hvars known to FSUIPC7. You should use the available presets. Even though most are aircraft-specific, the ones for the GN530, G1000 etc, are specific to the model and valid in all aircraft that use them. They are also valid for both the default/Asob versions as well as the Working Title mods. If developing using C#, you should check-out Paul Henty's client dll for .Net. This provides a higher level interface to both FSUIPC offsets as well as the WASM API / WAPI. See https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ John

Your log is showing that the ASN dll for v5 is being loaded, not v6: Do you not have the v6 dll (which you said was called 'as_connect.dll') in your FSUIPC6 installation folder?

Can you try the attached version please. In this version, the InitialStallTime ini parameter is now being obeyed - previously thus was ignored and was defaulting to a value of 25 (seconds). Can you initially try setting this to -10. This will then log a message every 10 seconds until the SimConnect_Open call has been successfully processed. Wait and see if it eventually connects and if so how many messages are logged before connection. If it does eventually connect, then you can update the value of InitialStallTime to be (number-of-messages-logged * 10) + 5 If you find that it is still not connecting, try with a larger positive value, e,g, 50. This should then try and reconnect every 50 seconds. Let me know how it goes, John FSUIPC7.exe

Your log shows that the Simcommect_Open call failed with an error: I am not sure what can cause this. I will make a few changes and post another version for you to test. John

Please try the attached and post your new FSUIPC7.log file. Leave FSUIOC7 running for a minute or so after loading an aircraft and then exit, Thanks, John FSUIPC7.exe

Very strange...I will provide you with another version that has additional logging so that I can see what is happening, but this will be tomorrow sometime now.

In the mean-time, could you try the attached dll and show me/attach your FSUIPC6.log file after using it. This will at least tell me if the ASN dll is loaded and if the ASN active function link is set. Thanks, John FSUIPC6.dll

I also see that AS for P3Dv6 is still in beta. Anyway, I have requested a license and will take a look at some point. John

Even after you have selected an aircraft in MSFS and are loaded and ready-to-fly?

As I said, I don't have ASN for P3Dv6 so it is difficult for me to check this. I will take a further look when time permits and let you know, Note however that I am in holiday in a couple of days, back towards the end of next week, so I won't be looking into this for a couple of weeks. John

It does keep retrying, which is why I don't understand your issue. If you just leave it, does it not reconnect?

All I have to say on FSUIPC7 auto-start is documented in the following FAQ entry: I can only suggest that you try removing all of your entries in the EXE.xml file and add them back one-by-one, and when you have found the one that prevents the others from restarting then contact the developer of that add-on. You can also try re-ordering the entries to see if that makes a difference. John

Yes, it should... Strange, as your log still indicates that it is trying to reconnect, whereas it should just log a message and continue waiting... It seems to be taking longer and longer for MSFS to respond to an initial connection requests with each release...the start-up process id very CPU intensive and it can take quite a while for an initial response. I will look into seeing if I can delay the initial connection attempt a bit longer, but I also have to consider the case where MSFS is already started/running, so I don't want to delay too long,,, John

You shouldn't need to disconnect and reconnect manually - does FSUIPC not automatically reconnect if you just leave it? Can you check your settings of the following ini parameters (in [General] section): InitialStallTime & NormalStallTime Also try with the following settings: InitialStallTime=-100 NormalStallTime=-5 Using negative numbers for these settings will instruct FSUIPC to just log a message when SimConnect data is stalled rather than re-questing.

At the side of the throttle, I only see a pitch-trim control and a TOGA button. Not sure what this means.... I have tried assigning a switch to the Spoilers Inc and Spoilers Dec controls and using these I can see the spoilers extending and retracting. I also tried assigning an axis to Spoilers Set but get extremely weird behavior - the spoilers initially seem to extended but then all of a sudden the aircraft, which was on the runway, is now in free-fall but falling up at an incredible rate....very strange! You just need to create a new (empty) profile in MSFS. I recommend you do this anyway if assigning in FSUIPC7, although it is fine to have some settings in MSFS and others in FSUIPC7. I have not noticed this, although I have only taken this into the air once. I will check the next time I take a look. John

License sent via PM. John

Any other assignment shouldn't affect this, unless the assignment is being triggered. Maybe check your assistance settings as these can affect things like flaps. I will take another look at some point to see if I can see any spoiler controls, or/and if the spoiler events have any effect.

Please see the section Gauge local variable access (L:vars), by macro on page 39 of the Advanced User guide. If using MobiFlight, you can also assign to just write the value to a spare/free FSUIPC offset, and gave a lua script that monitors the offset (using event.offset), and then when the offset changes you can update the lvar using ipc.writeLvar. You can also have an offset for reading the value of the lvar, by having another lua script that monitors the lvar value (event.lvar) and writes the value to an offset when it is changed. Better to have the read/write offsets as distinct offsets, although you could use the same one if you prefer.

Also, you should change this: to just so that the profile is loaded if you use a different variant.

I have this aircraft now and the throttle worked with my default throttle assignments - assigned with Send Direct to FSUIPC calibration using Throttle1 and Throttle2 controls. But this means that your throttle assignments should also work, so something else must be going on... The flaps lever has 3 discrete positions, and my default flaps switch assigned to Flaps Incr and Flaps Decr also works ok. Assigning an axis to Flaps Set also works, but exhibits strange behavior - using Axis Flaps Set works better. I don't see any spoiler controls....does this aircraft have spoilers?

So, the assignments are not working, nothing to do with profiles. For the throttle, try the Axis Throttlen Set controls, or the Throttlen Axis Set Ex1 controls to see if they work, Also, you can try setting logging for Axes Controls and see what is logged when you move the throttle in the VC, and then use that. I am more surprised about the flaps and spoilers. Does the aircraft actually have axis controls for these, or are they in discreet positions, so that you can only set them to a specific value and inc/dec them? If it does have axis controls, again try logging axis controls and see what is logged when you move the axis in the VC. Also, more and more aircraft are starting to use lvars for axis controls - for some strange reason...! Try listing the lvars to see if any look applicable. Your key assignments are also very strange: Each assignment is the same, and just runs a lua script. The lua it runs is waiting for an event: Each time you press one of those assigned keys, the lua script will be killed and re-started. If the script is handling the 12 key assignments, you don't need those keys assigned in FSUIPC7, and you want the lua script auto-started when the aircraft is loaded. I suspect this may be because your other lua script is maybe preventing the key press from being processed. Try activating logging for Buttons & Keys, make sure the Lua 12-Keys+AP script isn't running (you can temporarily assign a key or button to kill the script), and then try activating it. However, you don't need that script to log lvars in FSUIPC7. The easiest way yo do this is just use the Add-ons->WASM->List Lvars menu item. If you want to list them on a key/button assignment, use the List Local Panel Vars control. I don't have the Cockspur C510 so it is difficult to help with this further. If you continue to have difficulties, I can maybe request a press-copy license and take a look. John

That is logging from Buttons & Keys (which I didn't ask you to set). Did you actually set logging for Events? If so, and none were reported, just try the standard events I mentioned to see if they have any affect. No. I don't have a license for this aircraft - it is payware. John

You cannot assign an axis (left-hand side of the axis assignment window) to a non-axis control, such as Rotor Brake, as this doesn't make any sense, as you would be sending the axis value to the Rotor Brake control. If you want to assign an axis to a non-axis control, you would usually do this on the right-hand side of the axis assignment window, and assign to send one control when it enters a specific range, and another when it exists a specific range. So you can assign to send your Rotor Brake control (or preset) for lever up when the axis moves up into the range and then assign to lever down when it moves down into the range. If your axis range is the standard -16384 - +16384, and as I presume you will be using these axes like a lever, then you can use any range really, but I would suggest something like -12500 - +12500 for both your up/down ranges. John

By default, it matches in the aircraft title, which is defined in the aircrafts aircraft.cfg file, and logged by FSUIPC7 (in the FSUIPC7.log file) with entries such as the following: These are the names that are added to the profile when you create a profile or add an aircraft to an existing profile. Because you don't really need to, a FSUIPC will add the names (aircraft or folder name) for you - you can just edit these to get better matches on different variants of the same aircraft. The actual location will be either under your MSFS Official or Community folder, depending on whether the aircraft is a default/included one or an add-on, and will be under: <aircraft-folder-name>\SimObjects\Airplanes\<aircraft-name> All profiles are matched using the [Profile.xxx] sections in the main FSUIPC7.ini file. What do you mean by 'Doesn't seem to work'? Do you mean that the profile is not loaded? Any issues with profiles, please attach your FSUIPC7.log and FSUIPC7.ini files, together with the relevant aircraft-specific profile file if using profiles-in-separate-files. John

You may also need to send an event, with or without the lvar update. Set logging for Events in FSUIPC7 (Log->Events), open the console window (Log->Open Console) and see if any events are logged when you use the Avionics Master Switch in the VC with the mouse. If so you can use that. First try it on its own, as that may also trigger the lvar change (and animation). If not, you may need to send the control(s)/Event(s) as well as setting the lvar. You can do this by either overloading your assignment or creating your own preset. But first you need to determine which, if any, of the standard MS controls/events it is using. It would normally be one of the AVIONICS_MASTER_* events, but for some aircraft this can be a combination of various electrical events. I don't have the JF KingAir so cannot look into this for you, but if you try the above and report back any events you see, I can maybe help you set up a preset to use those events. Alternatively, you could ask about this on the MobiFlight Discord channel (under the HubHop support channel). Cheers, John