Coskun

Thank you, Ralim. I understand.

I guess I figured it out by myself. I just had to suspend the thread for 10ms after sending the change baud rate command and before closing the existing connection at 9600. I can go up to 115200 now. Can someone confirm if that is the maximum I can get with a Netduino Plus? BR.

Hi Coskun,

Thank you for the feedback. This is an issue with .NET MF, not with Netduino...but obviously it affects both. It also seems to effect every other NETMF-based board out there.

Microsoft spent a significant amount of time trying to reproduce the issue--but couldn't get consistent blue screens. Maybe it would crash every once in a while...but not often enough to be able to grab debug data.

Please do not get me wrong. It is neither blaming you or threatening you with buying one of your competitors. If Netduino was not a good product, I would have gone for another board anyway. I share my (negative) feedback in order to improve your product and nothing else. Otherwise, I appreciate your intelligence and efforts behind Netduino.

However, considering that the result is the most important thing rather than what is the reason behind the bug, it just simply affects the satisfaction of your customers.

I know, it can be very painful to work with MS guys sometimes. They won't really investigate a bug (well, they will up to a certain point) but what they usually hope is not to be able to reproduce it so they can close the issue. I have come across to that scenario so many times, I could not blame you.

What is more, I am spending 5 hours a week for Netduino and I face problems with the driver a thousand times. I just cannot and would not believe in that MS could not find enough debug data. Just does not make sense...

You are right about many things being fixed. I can deploy without any problems with the new driver. It is just BS if I really have to unplug while deploying.

Hopefully, some of the next releases will solve the BS issue.

BR.

My issues with being have to unplug and replug 1000 times is resolved with this driver.

However, I started getting BS if I have to unplug because the Netduino becomes unresponsive.

I highly recommend you to solve this issue because either unplug/replug or BS makes it not such a pleasant experience to play with Netduino (Plus). If the time spent for fixing the things takes longer than playing with your toy, it does not become a "hobby" anymore.

I see that tons of people are having similar issues. It should not be hard for you to reproduce these issues on your computer or a test environment.

If this issue is not solved (which is the case for a while), I will seriously consider looking for other brands of development boards.

Netduino is the best of the boards I have found so far but development issues with this driver are too much sometimes, it can make me post you this message at 3:24am.

I hope you understand.

BR.

My issues with being have to unplug and replug 1000 times is resolved with this driver.