5 replies to this topic

[Omar (OZ)]

FIXED


Visual Studio said unable to communicate with device... really? I am about to kill my computer, some save its life amd tell me its fixable.

EDIT:
Power light is on.

The application it has on right now runs fine, and the device smells fine i.e., it doesn't smell like burn circuits.

I didn't change anything physically, I was just uploading some edits to my application that I showed in the Video a couple posts ago.

[Thomas Mason]

Visual Studio said unable to communicate with device... really? I am about to kill my computer, some save its life amd tell me its fixable.

EDIT:
Power light is on.

The application it has on right now runs fine, and the device smells fine i.e., it doesn't smell like burn circuits.

I didn't change anything physically, I was just uploading some edits to my application that I showed in the Video a couple posts ago.

Mine does that sometimes i just unplug the USB and then plug in agian and all is well.

[Omar (OZ)]

Mine does that sometimes i just unplug the USB and then plug in agian and all is well.

Didn't work for me... I restarted my pc, it gave me a lovely blue screen [real nice shade of blue be the way ] on shutdown. I turn it on again, all is well... Netduino works fine now... soooo its ok? I hope.

[RedHermit]

I've had the same problem. Unplug and reinserting the USB usually works, if not, a full reboot works. Applying the firmware patch to the netduino has made it occur less often as well;

http://forums.netduino.com/index.php?/topic/39-netduino-firmware-v410-patch-1/

[Chris Walker]

If you can reproduce when/why Visual Studio doesn't want to deploy (until you hit the reset button or unplug/replug your Netduino), we'd love to know. We've made it easy to fix things when they go awry...and we'd also like to make it so you never need to do so.

[Omar (OZ)]

If you can reproduce when/why Visual Studio doesn't want to deploy (until you hit the reset button or unplug/replug your Netduino), we'd love to know. We've made it easy to fix things when they go awry...and we'd also like to make it so you never need to do so.

It was something that happed out of the blue, maybe my code froze the netduino. If it happens again I'll let you know