This is a late reply I know but...

The webrequest timeout appears to be broken in the Netduino. If the webrequest target device is not available the request will simply wait forever and hang.

I got around the problem by wrapping the webrequest in a ping request. If the ping succeeds the webrequest is executed. If the ping fails the request is bypassed.

I used this version of Ping and it appears to work well:

https://github.com/gittela/pingbox

Hi There,

I have been running a Netduino Plus 2 (with a small app) for about a year. On occasion I have encountered a situation where the device boots up very slowly - as in maybe 15 minutes to boot. It actually goes though the entire boot process and loads and runs the application without any errors. Its just about 1000X slower. Usually powering it down and up again solved the problem. Not any more.

At this point nothing appears to help. The Netduino appears to be running properly (as indicated by a display I have connected to it)... its just takes it several minutes to do anything.

Any help would be appreciated.

Thanks

Mike 

Is there any way to use the netmf_toolbox_http_client with a timeout (like httpWebRequest)? If the site does not respond the client appears to wait indefinitely.  

Thanks

Mike

I managed to solve this issue. I was getting the following warning message which suggested where the problem lay:

Hi Chris,

Thanks for your reply. Unfortunately, I cannot do what you suggested. When I deploy this one line application referencing PWM... during the deploy Windows pops up a message saying:  

"The last device you connected to this computer malfunctioned, and Windows does not recognize it"

After that, MFDeploy will not see the board again until I reload the board with 4.3.1. All of my Netduinos (5) behave the same way. I guess it could be my PC. When this first happened I uninstalled everything (VS2012, MF framework SDK, Secret SDK) and re-installed it all. But the problem continued.

Could I use the MS PWM library instead? Can you think of any other troubleshooting approaches?

Thanks for your help.

Mike

Hi There,

I am running Windows 8, VS 2012 Premium, Netduino 4.3.1.

If I simply create an application that attempts to use the Secret PWM library (see below)... during deploy I get a message that the PC no longer recognizes the USB device. From that point the only recourse I have is to take the Netduino back to 'bare metal' and reload everything. Other than PWM all the other applications I load on the device seem to work without problem.

Thanks for any assistance.

Regards

Mike

Hi Chris,

Thank you so much. It is now working.

One problem I had may be related to Win8.1. When I run the NetduinoUpdate.exe app it appears to do nothing i.e. I double click on it and nothing at all happens. I have to right click on the app and select 'Run with Graphics Processor' and then select the PC's graphics card... then it works. Go figure.

Thanks for your help. Much appreciated.

Regards

Mike

Hi There,

Something happened to my Netduino Plus2 today - it became completely unresponsive during a debug session. I had been using it with Win8.1, FW V 4.3.1 and VS2013 successfully  - until today.

I tried following the instructions to reload the 4.3.1 software but didn't get very far. The application NetduinoUpdate.exe appears to do nothing when I double click it. So I started MFDeploy and it too sees nothing - no board at all.

I then started the STM DFuSe application and it also reports nothing - again, no board at all. Under ->computer devices-> USB I can still see the Netduino driver. At this point I am at a loss as to what to do.

Any help would be appreciated. This is the second Netduino plus2 where I have encountered this problem. To resolve the previous problem I bought a new Netduino. But I don't want to keep doing that.

Any assistance would be much appreciated. Thank you.

Mike 

Hi Wendo,

Thanks so much... it did the trick.

Regards

Mike

Hi There, I am using a Netduino Plus 2 with VS2012 and NETMF 4.3. When I add any of the toolbox DLLs to a project and then attempt to deploy to the device I get the same error as above: