John Dowson

One thing you could also do is to change the following parameters in your FSUIPC7.ini, in the general section. Change: to Changing those stall times to a negative number will just log a message when data is stalled rather than reconnecting. As the CRJ seems to take a long time to load, it may be re-connecting to many times and then running out of SimConnect connections. However, I don't think this is your issue (from your log) but still worth doing. I will be releasing FSUIPC7 v7.2.0 sometime tomorrow, just got some documentation updates to do to complete the release. Once thats done, I'll take a look at the CRJ to see if I can duplicate your issues and investigate. Please update to 7.2.0 once released though. Thanks, John

This sort of issue is usually due to the axis being flagged as a digital axis (on/off) in your windows registry. To resolve, please see the following FAQ entry - although that mentions Saitek devices, it also applies to others:

I'll take a look tomorrow, but please check your ini. The last one you posted has this: Delete that bit in bold, and change to:

I don't think that is easily achievable. FSUIPC provides a mechanism for syncing flap detents, but not for throttle, sorry. I think the best you can do is to try to calibrate so that the throttle detents line-up as closely as possible., I guess things also depend on if using managed or manual mode, although I am not too familiar with the A320 to advise on this. You could try experimenting with the controls sent when with a range (i.e. the right-hand side of the assignments panel), by sending the axis control with the correct parameter value for the detent when within a range of that detent, but then you would not get a smooth axis movement.

They will probably be PMDG custom controls - you need to check your PMDG 737NGX header files to see what those are. You need to subtract THIRD_PARTY_EVENT_ID_MIN (which is, I think, 0x00011000 which equals 69632 - but check your header file to make sure), so for 85635, look for an event defined as (THIRD_PARTY_EVENT_ID_MIN + 16004) in the header on your PMDG documentation. John

That happens when you open the axes window directly from the system tray icon context menu. I'm not sure there is anything I can do - as its a modal sub-window of the main window, I certainly can't make it visible in the task bar as that is for main windows only. What you can do in this situation is: - press ALT-F - this is the hot key that displays the FSUIPC main window - then click the FSUIPC7 task bar icon. This will then bring both the FSUIPC main window and the Axes window to the foreground. John

As I have said several times, please just disable controllers in P3D for the time being. You still haven't done this: Also, please update to the latest version, v6.1.2, which was released 5 days ago. Only the latest version is supported. And also update your FSUIPC6.ini as suggested, i.e. (you don't seem to be following ANY of my suggestions....) Also, your ini shows that you have assigned your throttles as 'Send Direct to FSUIPC Calibration', but you have not calibrated your throttles. You MUST calibrate any axis that you assign via this method. Please read the documentation - the section I previously mentioned. As you only have assignments to the 4 throttle axis, anything else you are seeing MUST be coming from an assignment else where, either from P3D or the Honeycomb configurator, which is why I am asking you to disable controllers and stop (or uninstall for now) the honeycomb software. Enabling logging for Axes Controls will also show you the axes controls being sent, but best to remove the known culprits for this sort of behaviour (i.e. assigned in multiple places) before we look at this any further.

Sorry, but this is just confusing. For example, when you say moving lever 1 backwards, is that lever 1 on your Bravo? And if so, does that move your bravo lever 4 forwards? Or are you talking about in the UI, and mean thrust lever for engine 4? Anyway, I cannot help you if you do not show me your FSUIPC6.log and FSUIPC6.ini files. Please ALWAYS include these, especially after updating/changing. And did you follow the instructions I gave in my last post? Have you disabled controllers in P3D? Did you try calibrating as suggested?

Ok. That certainly is strange and sounds like an issue with FSUIPC. I will investigate. Thanks.

Please see the provided README.txt, included in the zip file you downloaded:

@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