7 replies to this topic

[The3dman]

Hi all, I'm having some problems in using the ethernet connection with my netduino plus. I'm running a simple http client that send some informations to a web server. If a power up my netduino with the ethernet cable connected, then everything works. I can also unplug the cable and plug again it after a while withouot problems. If a power up my netduino without the cable and then I connect it after a while, nothing works. I think that it could be a problem with dhcp or with the firmware. I'm using 4.2.0 firmware Andrea.

[Chris Walker]

Hi Andrea, This is a known bug in the lwIP stack implementation of .NET MF 4.1/4.2. There's a bugfix in the newer lwIP releases and the NETMF 4.3 roadmap indicates that it should be incorporating the newer release. We should be seeing the first NETMF 4.3 beta very very soon. Chris

[The3dman]

Hi Andrea,

This is a known bug in the lwIP stack implementation of .NET MF 4.1/4.2. There's a bugfix in the newer lwIP releases and the NETMF 4.3 roadmap indicates that it should be incorporating the newer release.

We should be seeing the first NETMF 4.3 beta very very soon.

Chris

It sounds good, I'm looking forward for the new update.

Andrea

[David_G]

I’ve been tinkering on and off over several months with using a Netduino Plus to read One-wire sensors (DS18S20), and send the data to COSM at regular intervals (https://cosm.com/feeds/56826). I’m also writing an event log to the on-board micro SD card.

I seem to have a similar issue, but I am not sure it is the same, so would appreciate suggestions/comments.

The problem occurs when my ADSL router is reset (ND+ is connected directly to the router). What seems to happen is that the router sometimes allocates a different IP address. The Netduino doesn’t detect the new IP address, and logging NetworkInterface.IPAddress continues to return the old address. I have tried forcing of DHCP Release and Renew before each attempt to connect to COSM. However, then the IP then gets changed from whatever it was, and remains as 0.0.0.0 even though in the router’s DHCP table it is listed as 192.168.1.1 (for example).

I have previously tried a static IP for the ND+ but unsuccessfully – perhaps because I was not able to get MFDeploy to work? I run MFDeploy to check the network configuration, and it shows DHCP is enabled. However, when I try to update settings, I get the message:
Unable to erase configuration sector memory
Am I using the wrong version of MFDeploy (2.0.3036.1)? Am I using it incorrectly?

In order to use the inbuilt one-wire support, I previously upgraded the firmware to Netduino_v4.1.1_beta1_CW.NETMF.OneWire-1.0.5.0 (http://forums.netdui...-onewire-alpha/)

Is there an issue with DHCP in this firmware? Would it help to upgrade firmware to 4.2? If so, what about one-wire support? Would it be better to go back to 4.1.0.6 and use a different one-wire library? Any other ideas? How soon will 4.3 be available? Will that include one-wire support?

Short of ditching the project, I’d be interested in any ideas on the best way forward.

cheers

[caEstrada]

David_G, I run a lot of Ethernet exchange under 4.2 without problems. However, I had problems with firmware and IP & MAC Addressing. I was oriented here in the Forum to include some statements in the code instead the firmware: byte[] MAC = { 0x5C, 0x86, 0x4A, 0x00, 0x4E, 0x5A }; Microsoft.SPOT.Net.NetworkInformation.NetworkInterface.GetAllNetworkInterfaces()[0].PhysicalAddress = MAC; Microsoft.SPOT.Net.NetworkInformation.NetworkInterface.GetAllNetworkInterfaces()[0].EnableDhcp(); Please try and let me know if I can help. Regards,

[The3dman]

I successfully ran my web client on the netduino+ for two days and an half. It was sending correctly data to the server every 3 seconds during these days. Then this morning, I noticed that the data flow interrupted roughly during the night for 8 hours. The netduino got stuck during these 8 hours doing nothing. I think that it got stuck on the HTTP call "(HttpWebRequest)WebRequest.Create(requestUri)" not even returning an exception!!! I think this should be possible because a DHCP polling. Andrea

[The3dman]

I successfully ran my web client on the netduino+ for two days and an half.
It was sending correctly data to the server every 3 seconds during these days.
Then this morning, I noticed that the data flow interrupted roughly during the night for 8 hours.

The netduino got stuck during these 8 hours doing nothing.
I think that it got stuck on the HTTP call "(HttpWebRequest)WebRequest.Create(requestUri)" not even returning an exception!!!
I think this should be possible because a DHCP polling.

Andrea

I forgot to say that to fix it, it was enough to unplug and plug again the ethernet cable. Without restarting the netduino+.

[caEstrada]

I forgot to say that to fix it, it was enough to unplug and plug again the ethernet cable. Without restarting the netduino+.

The3dman,

Why don't you post your code to look at it? I have learn to send a Ping before any TCP or even UDP transaction to see if I have minimal connectivity. Obviously, the firmware cannot include all the possible tools already included in the .Net Framework because size constraints.

Regards,