Windows 10 and TARGET

[heloguy]

So, I just upgraded to Windows 10, and started my run through of testing everything out. The only problem I've found, and it's an annoying one, is that if I run a TARGET profile for my Warthog, throttle, and F-16 MFDs, the profile will start, but the F-16 MFDs will blink, and the profile will stop with an error that the USB connectors have been disconnected.

 

Everything works fine on its own, and I've tried to use different USB ports, but I just can't get them to work in TARGET anymore. I've confirmed that if I take the same profile, and just remove the MFDs from it, then the profile will run just fine.

 

It almost seems like the MFDs are losing power for a moment, then coming back on. I remember this happened in Windows 7 every once in awhile (not everytime), but it didn't seem to affect how the profile ran.

 

I've attached a screen shot of TARGET after the script fails to run.

 

Anyone have any ideas?

[majapahit]

perhaps unrelated, perhaps a solution

 

I had severe problems with USB connections on Win 8.1, and - much - later found that I could not use (specifically certain type of cables) USB extension cables from either a powered USB hub, or the mainboard.

 

You can check this voltage drop from your USB cable with a USB Volt meter (those chinese cheapoo ones will display ~5V with 0.10V error which is good enough).

 

Specifically 'good' USB cables with those 'noise suppressor iron rings' make the voltage drop. A 3 Ft one of these drops voltage to 4.75V and I got USB intermittent disconnects (that will drive you crazy)

 

2 cts

[heloguy]

This sounds plausible, but I only have one USB extension cable, and it isn't attached to either one of my MFDs.

 

The problem does seem to be that they intermittently lose power. Like I said, I tried two different sets on the main board. I also tried an externally powered USB hub, with the same results.

[Iku_CC]

Look this post...you get help from it..:)

http://forums.eagle.ru/showpost.php?p=2422898&postcount=58

[heloguy]

Thanks for that, but it still didn't work. Even with advanced power management turned off, they still blink off when starting a profile and kill the script.

 

Edit: Actually, it did work! After I posted the above, I thought 'Hmm, maybe I should try a restart.' So far so good. I guess after you change those registry entries, you need to restart for them to take hold. Thanks again!

Edited August 11, 2015 by heloguy