"Scrambled" Module Assignments

markek · April 2013

Recently I had to take my computer to the shop (memory stick issue) and the unplugging and re-plugging of the Go-Flight modules into the USB hubs have scrambled the settings. All three of the P-8's are switched as well as both T-8's. (The WP-6's were reversed but re-booting the computer switched them back to the correct position.) To be more clear, each module switch or button still is assigned correctly, it's the whole module that has switched with another like module. The pattern is that any module that is one of a kind has no issues (TQ-6, MCP-Pro, RP-48,GF-MESM, GF-LGTII.) The GF-166 radios have "swapped" in the past but held their current position this time. I'd love to find a solution to the larger USB hub issue, but for this forum specifically, I guess my question is how, if possible, to change these to their correct module without going into the interface and doing these one by one? I've done them manually and it's very time consuming plus its not permanent.

I've had the usb swapping or going dead issue on both computers that I have owned using Go-Flight modules. Changing from PMDG to another plane always requires a re-boot-you cannot go into the GF config and use other settings without problems so I have resigned to using their hardware with the NGX only to avoid headaches. I was told by thie tech support that my issue was not universal but the issue is identical and my newer computer as well.

Any guidance would be appreciated and glad to provide any more information that might be helpful. I'm using Interface V1.1.0.0.

Thanks in advance.

Mark

admin_pps · April 2013

Hi Mark,

You can edit the user.config file manually and change the Device ID's. The location of this file is detailed towards the back of the manual. It will be MUCH be easier using a free xml editor rather than notepad (I recommend XMLPad)

For example, the GFRP48's line is:

Look for the Device ID lines e.g. Device ID="0" and change the numbers. e.g. Device ID="1". This will swap the configs around to match your changed device ID's.

Not sure what you mean by "Changing from PMDG to another plane always requires a re-boot-you cannot go into the GF config and use other settings without problems so I have resigned to using their hardware with the NGX only to avoid headaches." Can you expand on this please.

Best wishes

Steve

markek · April 2013

Thanks, will try your instructions.

What I was meaning in the changing from PMDG comment is not related specifically to the interface but more an issue between the usb hubs and the Go-Flight GF config. If I switch profiles to say, the default from the one I saved as PMDG, it loses connection and at times, also scrambles the devices. The same thing happens when I change add on aircraft and leave the PMDG profile in GF config. I can't run multiple profiles without issues and that requires shutting down the computer, removing usb power and usb from computer ports. When the system comes back up, it's a wild card as to what devices it will use or for that matter, switch on me-just like what it did when I took the computer to the shop. Spending time setting up profile through your interface and labeling the switches and buttons becomes the issue when every time I introduce a change or unplug a hub, it's not going to come back up with the right settings.

What's interesting is that I had several conversations with John at Go-Flight some time ago and he was unfamiliar with this problem. One of the reasons I bought a new computer was to solve this and it did not. I've bought expensive powered hubs thinking that with all of the modules (15-16), maybe that was the issue but no.

So the reason I bring up this rant to you is to find a shortcut to setting them up again from scratch and you've kindly done that but if you have any thoughts on the bigger issue, I'd certainly appreciate them.

Regards,

Mark

trevg · April 2013

Hi Mark,
Same problem from day 1 (years ago)
I labelled all leads so I make sure they get plugged back into the same USB ports.
As mentioned only effects where you have multiple same units.

Yes, have tried "all" suggested remedies to no avail over 3 dedicated flight machines over the years.

Cheers
Trevor

admin_pps · April 2013

Hi Mark,

I haven't seen this behaviour before. However since you have bought a new computer and the same behaviour is occurring it must either be the way you have windows configured, your hubs (if you reused them) or your Goflight hardware.

I would always ensure that you have all USB suspend settings turned off in Windows Power Management. I would also have only one power heavy device per hub (MCP PRO, MCP, GF166, GF46).

To solve device lock up problems, I also power up the hubs before any power goes to the PC.

I'll look into it further if none of the above helps.

Best wishes

Steve

markek · May 2013

Steve:

I have done nothing to the basic Windows configuration (nor to the old computer either, for that matter). I do have the power settings turned off from suspending and no difference there either. I'll look at and test the GF 166's to be all on separate usb hubs. Right now, I run two usb hubs, neither of which is maxxed out from using all of the ports. Not sure if the GF166's are all on one or split among the two but for sure they are not each on different hubs.

I'll test and report back but am business traveling for the next couple of days.

Here's an example: I did not change GS config from the PMDG737 profile and had no intention of using the GoFlight modules when I started FSX to use the new Majestic Q400 yet one GF 166 is dark, one has a couple of lights but no frequencies lit and one changes the frequencies but does not swap them from the right standby to active and visa versa, just switches to something odd. The only resolution is to unplug the ports from power source and from computer and then I end up with the modules scrambled, per my original inquiry. As long as I stay with the PMDG 737, it tends to be stable.

Sounds like Trevor has the identical issues and not sure what's different for us than other GoFlight owners.

Thanks.

Mark

admin_pps · May 2013

Hi Mark,

"I did not change GS config from the PMDG737 profile and had no intention of using the GoFlight modules when I started FSX to use the new Majestic Q400 yet one GF 166 is dark, one has a couple of lights but no frequencies lit and one changes the frequencies but does not swap them from the right standby to active and visa versa, just switches to something odd."

I used to see this behaviour a lot before I moved them so I had only 1 power hungry (GF166, EFIS, MCP, MCP PRO, GF46 etc.) device per hub and ensured the hubs were powered up before the PC. They are very finicky with modern hardware (my issues started when I moved to Sandy Bridge).

Best wishes

Steve

markek · May 2013

Steve:
I will try your recommendation. Think I've tried everything but several usb's. I would have given up long time ago out of frustration of the modules didn't add so much to the experience.
I will report my results.
Thanks
Mark

markek · May 2013

No luck. I plugged the 3 GF-166's directly into CPU as well as the MCPPO. The rest of the modules are on an "industrial" powered usb hub. They still scramble virtually everytime I power off and then back on the computer. Now my P-8's and EFIS's are both reversed or changed assignments. The WP=6's stayed correct (this time) I could plug one more module direct even though the pattern indicates that wouldn't help but after that, I have to rely on hubs.

Any thoughts would be appreciated. Thanks.

Mark

admin_pps · May 2013

Hi Mark,

You really need lots of hubs with each power hungry device plugged into a separate hub - its the only way it ever works OK - direct into the motherboard rarely cuts it!

The other thing to check would be updated USB drivers for your motherboard and your hubs (go to the manufactures web sites) and also try disabling USB3 and enabling any USB computability options in the BIOS.

Best wishes

Steve

markek · May 2013

Steve:

Are you saying to use as many hubs as there are usb slots in the cpu but not to plug devices in directly? And, to spread out the "hungrier" GF-166's and MCPro into some of these separate hubs?

Some of these usb's a 3.0 and very few 2.0's Guess I could try avoiding the 3.0's but that would mean fewer hub opportunities.

Thanks.

Mark

admin_pps · May 2013

Hi Mark,

Yes use as many separate powered hubs as you need and connect your goflight gear to those. Separate the more power hungry devices, 1/maybe 2 of those per hub. You can use the other ports for the less demanding goflight gear. It fixed a load of issues for me and for others.

I can't promise it will fix it for you, so I would check you have the latest USB device drivers and BIOS settings before splashing out any cash for more hubs.

Best wishes

Steve

cmantel · May 2015

So then, what you are saying is that the "GF supplied" D-link powered hubs, the TWO that are supplied when you BUY an airliner system, just are not enough?? Then why would you guys market it that way? Shouldn't you be supplying more powered hubs to those who shell out a wad a cash on your systems??

cmantel · May 2015

sorry, that rant was directed at GF, not anyone who has worked hard to bring this nice piece of kit to us all. It just seems that GF probably knows about this problem with their big systems, but they don't supply the needed hubs to cure the problem. It surely would have saved a lot of us some very big headaches if they had, or even if they would just tell us folk that it was going to happen. Good powered hubs are not "really" that cheap, and it "bites" into GF's bottom line to be sure.

admin_pps · May 2015

Hi

The issue is very PC/hub specific. I'm not sure Goflight can do anything about it. All the GF devices work to USB spec but sometimes the PC's don't and cannot cope with devices that operate towards the maximum power requirements.

Separating out the power hungry devices has worked for me in the past, but it doesn't always work for other people.

Best wishes

Steve

"Scrambled" Module Assignments

Answers