9 replies to this topic

[Nicolas Dorier]

I have tried to program sockets with the netduino in v4.1.0 (update 5) and v4.1.1 ALPHA 7.
From what I have seen, I had some problems.
Sometimes, call to bind like this

server.Bind(new IPEndPoint(IPAddress.Parse("192.168.5.100"), 5656));

completely blocks the netduino (even MFDeploy can't ping it after that)

Sometimes it does not block but throw an exception which means that no interface have this IP
And sometimes, after several reboot, without doing anything, it works.

Most of the time, when I use sockets, I can't deploy without replugging the USB cable.
And MFDeploy can't ping when the server is on.

Am I doing something wrong ?

Here two project, "Portal.Debug.Client" is a WPF test client which connect and "ping" the netduino.
"Portal.Debug" just listen for a client, and send back the data it recieves.

Sometimes it does not work, sometimes it work, it's very unreliable.

Attached Files

•  Portal.Debug.Client.zip   826.92KB   12 downloads

[Chris Walker]

Hi Nicolas, That's very odd. What happens if you pass in an IP address parameter of IPAddress.Any? Also, what are your IP settings? MAC address? [Also, if you upgraded your firmware...did you reset your MAC address back to the one on the sticker attached to your Netduino Plus?] For firmware, I'd recommend using 4.1.0.6 RC2 or 4.1.1 a7. We've been fixing quite a few bugs in the lwIP networking implementation over the last few months (which are incorporated in the newest releases). Let's see what we can do to create a reasonably consistent repro case...and then we can dig into it and trace through things here. Chris

[Nicolas Dorier]

I had not reset the MAC address, I just did but same problem here how I do :

-Run in debug the two projects
-Click on "Ping" from the WPF application
(Here I test several pings and it works fine...)
-Click "Renew"...
(Here the "socket.Connect of the wpf application works, whereas the netduino is not blocked on socket.Accept)
-Click" Ping"
(Does not work)
-Stop debug,
-Unplug the netduino
-Replug
-Run in debug the two projects
-Now the netduino is blocked on server.Bind

Every time I unplug/replug the netduino it blocks on server.Bind... and by chance it works again once

I use 4.1.1 a7, thanks for your help !!

Update

Same problem when I use UDP.
sometimes it blocks on server.Bind, sometimes it blocks when I create the socket

Socket udpSocket = new Socket(AddressFamily.InterNetwork, SocketType.Dgram, ProtocolType.Udp);

[Nicolas Dorier]

When I instanciate the Socket object, the netduino crashs (Even tinybooter does not respond) I have found a workaround : I need to put a breakpoint between the new Socket, and the Bind and plug the ethernet cable at this time.

[Chris Walker]

Hi Nicolas, Hmm, that shouldn't be happening. We will pull your code up on a development machine within the next few days and will see if we can reproduce the issue. Chris

[Nicolas Dorier]

The workaround was to use the NetworkChange.NetworkAvailabilityChanged event. I unplug the ethernet cable when the netduino start, when it's started, I plug the ethernet cable and then I start a new thread in the event handler and opens the socket.

[gaibwm]

I have tried to program sockets with the netduino in v4.1.0 (update 5) and v4.1.1 ALPHA 7.
From what I have seen, I had some problems.
Sometimes, call to bind like this

server.Bind(new IPEndPoint(IPAddress.Parse("192.168.5.100"), 5656));

completely blocks the netduino (even MFDeploy can't ping it after that)

Sometimes it does not block but throw an exception which means that no interface have this IP
And sometimes, after several reboot, without doing anything, it works.

Most of the time, when I use sockets, I can't deploy without replugging the USB cable.
And MFDeploy can't ping when the server is on.

Am I doing something wrong ?

Here two project, "Portal.Debug.Client" is a WPF test client which connect and "ping" the netduino.
"Portal.Debug" just listen for a client, and send back the data it recieves.

Sometimes it does not work, sometimes it work, it's very unreliable.

I run it a few weeks ago and it is still running. I will post my codes, if issue is not solved.

[Nicolas Dorier]

The issue is not solved, can you send me your code please ? I think I did it right... maybe my netduino is buggy

[Stephen_P]

I'm not sure if this is going to be useful but I had very similar problems with my netduino plus but they all went away after I bypassed my 10BASE-T hub. The hub which appears to have been causing the problem is not in my office here so I haven't been able to re-connect it to verify that it was definitely the problem but I would suggest if you are having issues try avoid the hub. Hope that helps a bit. Cheers Stephen

[gaibwm]

Instanciated, "call" function will create a thread to connect and receive in "Receive" function until connection is terminated

Attached Files

•  netduinoPlus_socketClient.txt   27.95KB   78 downloads