John Dowson

@Andreas Stangenes Ok, glad thats solved. Strange that it actually requires the FSUIPC lvar module enabled. Anyway, I've just got a license for the CRJ so I'll check that. Thanks for reporting back.

You could try an ext.state call, using either EXT_NRML or EXT_MAX, but I'm not sure those will undock the window. Otherwise maybe ext.postmessage, if you can determine what the windows message is to undock....Alternatively, if there is a keypress or key combination that does this, you could try sending those key commands using ext.sendkeys or ext.postkeys. Just some ideas to try, but I wouldn't expect too much....!

Ah, ok. I'll see if I can get hold of a copy and check it out....

Ok. Maybe best to try without this running, if you haven't already.

As I said, your log shows only the one aircraft being used, and you have NO assignments at all for that aircraft in FSUIPC. Please update your profile section as suggested. The log also shows that dat was stalled at around 154 seconds and FSUIPC closed and re-connected. To prevent this, please change the following lines in your FSUIPC7.ini in your [General] section: to i.e. make the TrafficStallTime and NormalStallTime negative. This will instruct FSUIPC to just log a message when data is stalled rather than re-connect. Presume this is via the cockpit UI, no? As you have no assignments at all for the aircraft you had loaded, FSUIPC wasn't actually doing anything. I did notice this from the CRJ forum link you posted? That's interesting. I'm not sure how that works, and may cause priority issues if also assigning in FSUIPC as direct to fsuipc calibration. Does the CRJ come with its own configurer then for these axes? How do I check that? Go to the MSFS controllers page and take a look at what is assigned to your device. You can create a new (empty) profile using the Preset Manager. If you create a new preset, it will be empty by default. Sorry, but its difficult to determine what the problem is without actually having the CRJ. I see that someone is going to check the latest version with FSUIPC so lets wait until we see if they find anything. Otherwise, I'll see if I can get a (temporary) license to investigate. John

What actually happened in that session? The log file shows that MSFS ran for around 5mins then closed down, FSUIPC detected MSFS closed down and so exited. Also, the aircraft you used in that session was this one: 103828 26260 Aircraft="CRJ700ER Scandinavian Airlines New - EI-FPS" This aircraft is NOT covered by your CRJ profile: You need to add that variant to your profile section, or, maybe better, change that profile section to the following: That profile will then be used for all aircraft that contain the substring 'CRJ' in the title. Also, it looks like the CRJ is continually emitting certain events - this is normal but creates a lot of 'noise' in the log. You can ignore such events by using the DontLogThese ini parameter, e.g. Also check that you have an empty profile for your X52 in MSFS id assigning in FSUIPC7.

Yes, you need to calibrate them - if they are moving in the opposite direction, then check the Rev checkbox. As I said, you should just disable all controllers in P3D if assigning in FSUIPC. This will prevent dual assignments. And also don't use/run the honeycomb configurator as this will also assign your axes/buttons. To start again assigning in FSUIPC, just delete your FSUIPC7.ini and a new (empty) one will be created and you can start again. To assign and calibrate in FSUIPC, please see the section The Easy Step-by-Step Way to Calibrate Your Controls on P37 if the User Guide. Sorry, I don't know what this means. This is not the way FSUIPC works. FSUIPC will do nothing until you tell it to, i.e. you have to assign each of your buttons/axes to the functions required. There are a few things in your ini that need adjusting. Without FSUIPC7 running, you shhould delete the entire contents of your [General] section and let that get rebuilt. Also change this (in your [JoyNames] section: AutoAssignLetters=No to AutoAssignLetters=Yes This will prevent issues if/when your joystick ids change, such as when changing USB ports. So, in summary: - disable controllers in P3D - unintall any honeycomb software (ir at lest make sure that it is not running) - make those changes to your FSUIPC7.ini as suggested - start MSFS/FSUIPC7, and then try and assign and calibrate your axes as described in the User guide. For any further issues, please attach both your FSUIPC7.ini and FSUIPC7.log files. John

I have no idea what could be causing this.. its very strange. Your log file is empty - it show the sim was detected then closed down 11 seconds later. Did FSUIPC shut down on its own? Are there any related events in the Windows Event viewer? You could try deleting the contents of the [General] section of your ini and let that get rebuilt, as the defaults you have there are rather old and need updating. I don't think this will help with your issue though, but worth a try. Also activate logging for Extras and Events, then try again and show me your new log file, with a description of what happened - and if FSUIPC closed/shutdown/crashed, also check the windows Event viewer and show me any info there related to FSUIPC. Thanks, John

Which version and from where are you trying to download? I've just tried both sites and they are all working ok. If having issues, try right-clicking the downloadable file and select 'Save as...'. Also, please don't posy in the announcements forum. I will move your post.

Could you please show me your FSUIPC7.log and FSUIPC7.ini files from when FSUIPC crashes please, together with any event viewer information available.

If by 'exteranl' you mean un-docked, then I don't think there is currently a way to do this via simconnect.

Thanks for reporting back. I was going to try this today - not sure why the previous dev version crashed FSUIPC7.... John

Can you please attach your FSUIPC7.ini and an FSUIPC7.log file generated with logging for Buttons & Switches and Events activated, and press the buttons you have assigned to the elevator trim and I'll take a look. John

if assigning in FSUIPC, better to disable controllers completely in P3D. Your log shows that you still have controllers activated:

As Pete says, please always attach your FSUIPC7.log file, as well as the event viewer information, if you think FSUIPC7 has crashed. Also, if it works fine in the stable version, I would suspect that the problem is in the FBW dev version. However, II've just switched to the FBW dev version so I'll check this over the weekend to see what is happening. John

You could try this user contribution for the Bravo leds: John

@FHamoudi No problem. I'll create a sticky topic for this so its always at the top of the forum and easier to find/see. The attached license is valid until 12th June: FSUIPC7.key

Which aircraft and lvar are you talking about? If you let me know I could possibly check it here - as long as its not an add-on aircraft. Note that not all lvars are writeable - some are read only, but its not possible to tell which without trying them (as far as I'm aware).

Just checked the MobiFlight spreadsheet to determine the state if the FBW events, and the FCU VS/ALT pull/push events are all documented as: dev version, soon on experimental (see https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454) So these aren't working yet on the stable - and also not in the experimental. So, it sounds like you need the dev version for these to work at the moment, or maybe wait until it has been moved to the stable.

Also, just checked again, and it looks like those controls for the VS pull/push don't work, but the altitude ones seem ok, but please test. I'll keep looking for the VS pull/push....

What aircraft are you using? Your A320NX profile is only set-up to be used with the following aircraft: Airbus A320 Neo Alitalia 8K (A32NX Converted) Is this the old FBW A320 that replaced/augmented the stock one? If so, its vety old now. The latest FBW A320 is installed as a distinct A320 to the stock one, and is called: Airbus A320 Neo FlyByWire So, first can you check that you are up-to-date with the latest FBW release. Also, in your FSUIPC7.ini, you should change this: to this: to pick-up all variants (including the stock A320). If you don't want to include the stock A320 in your profile, you can adjust so that the name you enter is a substring match to only the FBW A320 (e.g. 1=FlyByWire). How have you assigned this? I see nothing in the ini you attached that does this... Once you have checked you are using the latest FBW A320, please try again. You can also open the console window (Log -> Open Console) to see which events are being sent when you pull/push the knobs in the UI, then try your assignment to these functions to see if they emit the same controls. You can attach your .log file (and updated .ini) with this logging if still not working.

Please don't create new topics for ones that already exist. You should have posted your request here: I will add a new trial license to that topic shortly, but it will be for 7 days or so. This topic is now locked.

If it appears (and has disappeared) from a PMDG menu, you will ask to ask PMDG support I'm afraid. I don't have any PMDG aircraft and didn't even know FSUIPC appeared in a menu option there (or what that option does!). If it appears in the add-on menu for P3D, then it is installed and running ok. No idea what the issue could be. Was your TQ6 assigned through FSUIPC6? What has changed? If it was previously working, something must have changed. Please show me your FSUIPC6.log and FSUIPC6.ini files. John

I can't read those images. Please show me your FSUIPC7.ini file.

Ok, thats good. What did you assign to for these? Did you try what I suggested: ? That won't animate the knob, but should hopefully activate what you have set. Not much point at the moment - an explanation and your ini and log files is usually more informative than a video. How are you assigning to push/pull the knobs?