Wernfried

Is there any chance to get help?

If not, then I cannot use the Netduino anymore and because I'm afraid the same behaviour with Netduino 3 I have to search for alternatives.

After a very long time today I've has enough time to play with Windows 10 and the Netduino.

I installed a new W10 on my dektop, installed Visual Studo 2015, the MicroFrameWork SDK and the Netduino SDK.

And now I can report, thet the behaviour on my Desktop computer is the same as on the Laptop. The USB driver for Netduino permanently connects and disconnects, I can hear it playing the sound. Since the desktop has totally different hardware and all other USB devises work well with both computers, I now assume it must be something wrong with the driver.

Does anyone else here use the Netduino with W10?

Windows 10 IoT is an operating system, where .Net-based applications may run on. This has nothing to do with NetMF, on which Netduino is based on. NetMF is a reduced .Net framework while on W10 IoT the full .Net framework is available,

Windows Remote Arduino gives only a possibility to control the Arduino I/O from a Windows application.

So you cannot use W10 IoT on Netduino. Install W10 IoT on a Raspberry and you have a more powerfull MC then Netduino, but both solutions are not comparable, also Netduino has some advantages. In W10 IoT the applications are embedded in the W10 OS, in Netduino the NetMF is the OS, Apps are started emmediatly.

I'm runing W10 on a Lenovo Yoga Pro, unfortunatly I have no time in the next weeks to test it on a desktop pc with W10.

I have tested with several MicroUSB cables, since I use several of them, at least 5. All of them work properly with other devices (smart phone, raspberry pi 2).

And yes, when I have enough time to deploy to zhe N2P, then the program runs properly, even if I cannot establish a connecion. I have a tested it with a program sennding messages to a REST server and the messages are received there.

I assume stil, that the driver does not work properly in W10, because when it doesn't work, it also isn't shown in the drivers list, but it is, when it works.