Netduino Plus not showing up in the Network
#1
Posted 29 September 2010 - 06:10 AM
#2
Posted 29 September 2010 - 06:12 AM
#3
Posted 29 September 2010 - 06:34 AM
This is the Socket call that works on the main router but not on the second router.Did you set the IP address on your Netduino Plus so that it would be part of this other router's network? Are you using DHCP or static IP?
Chris
newSocket = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp); newSocket.Bind(new IPEndPoint(IPAddress.Any, 80)); newSocket.Listen(10);Neither routers use static IP.
#4
Posted 29 September 2010 - 06:39 AM
#5
Posted 29 September 2010 - 06:51 AM
I can't ping because I do not know its dynamic ip. I changed the code to this, but I'm having with that deployment issue again, so I don't know if it works or not yet.Can you ping the Netduino Plus while it's plugged into the router? Have you tried static IP--to see if it works then?
Chris
newSocket = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp); newSocket.Bind(new IPEndPoint(new IPAddress( new byte[] {10,0,0,7}) , 80)); newSocket.Listen(10);Chris, I really appreciate the late night support, but I think we both should get some sleep. I'll try more tomorrow.
#6
Posted 29 September 2010 - 06:58 AM
#7
Posted 29 September 2010 - 07:19 AM
This is very odd... Using your suggestion, I was able to see the Netduino IP.You can get the IP address of the Netduino Plus using:
Microsoft.SPOT.Net.NetworkInformation.NetworkInterface.GetAllNetworkInterfaces()[0].IPAddress
Good night, hari.
When connected to either router, the NetduinoPlus reports the same IPAddress (192.168.7.9)
I assigned for the first router's LAN ip range to be (192.168.7.1 to 254).
I do not do anything special on second router so my MacBook on second router is at 10.0.0.3, the second router is at 10.0.0.1, but the NetduinoPlus is at 192.168.7.9. That explains why I don't see it in attached device on second router, but why does it not have a 10.0.0.x IP?
Oh incidentally, 192.168.7.9 is also the IP shown for second router in the attached devices list of first router.
Good night Chris.
#9
Posted 29 September 2010 - 01:28 PM
EnableDhcp() fixed it! The Netduino Plus now shows up in attached devices list of the second router!It looks like your Netduino Plus isn't getting a DHCP-allocated address on the second network.
What happens if you do the following?
Microsoft.SPOT.Net.NetworkInformation.NetworkInterface.GetAllNetworkInterfaces()[0].EnableDhcp();
Chris
Thanks Chris!!! You're the best!
PS: My app worked once, but now it appears to be unresponsive in Socket.Accept(). I'll dig into this tonight. Thx again.
#10
Posted 06 August 2011 - 03:18 AM
#11
Posted 06 August 2011 - 08:25 AM
Very odd. We ran a demo on a 10MB network recently without any issues. I'm almost always on a 100Mbit link myself, but the Netduino Plus should do both 10Mbit and 100Mbit without a hitch.Are there any known issues running the Netduino Plus on a 10MB Ethernet? On my 10MB test setup, running continuous ping, it misses one out of two or one out of three. Looks like it keeps dropping the link and bringing it up again? I see no problems at 100MB. I need to support both 10MB and 100MB networks.
You are running full-duplex 10Mbit, not half-duplex...correct?
Welcome to the Netduino community,
Chris
#12
Posted 06 August 2011 - 12:44 PM
#13
Posted 06 August 2011 - 09:43 PM
#14
Posted 07 August 2011 - 12:13 AM
Chris, It is impressive that the .NET MF 4.2 Release Candidate is available as of August 3rd... and you expect to have a firmware update only a few days from now.Also, we'll be posting the .NET MF 4.2 release candidate within a few days. If you have a chance to test it against that, I'd appreciate it! There are a lot of networking bug fixes in the new release.
Nevertheless, can you hurry?
Look at me - an obnoxious newb. Pushing the overlords to go faster. Ha! I love the internet! I am power! Faster, faster!
No. Seriously, I'm dying to see if my severe problems with networking-DHCP-static-IP-not-helping just magically go away with 4.2 RC. I haven't successfully connected since my Light me up! post.
The intro blurb at the above link confirms your optimism:
So, in summary, we love you guys! Keep us the good work! Just work faster.... several bug fixes and improvements, among which the most important (for NetduinoPlus) are:
- Broadcast and static DNS addresses support with DHCP for lwIP TCP/IP stack
- Improvements to the time service for lwIP and RTIP TCP/IP stacks
#15
Posted 07 August 2011 - 03:27 AM
Hi John,
Are you using DHCP or static IP? If DHCP, can you try static IP really quick and see if it makes any difference?
Also, we'll be posting the .NET MF 4.2 release candidate within a few days. If you have a chance to test it against that, I'd appreciate it! There are a lot of networking bug fixes in the new release.
Chris
I tried it both ways with the same results. The problem occurs before the IP address comes into the picture, even before the Ethernet link comes up.
I'll test with MF 4.2 once it's available and see what happens.
JD
#16
Posted 10 August 2011 - 01:52 PM
Hi John,
Are you using DHCP or static IP? If DHCP, can you try static IP really quick and see if it makes any difference?
Also, we'll be posting the .NET MF 4.2 release candidate within a few days. If you have a chance to test it against that, I'd appreciate it! There are a lot of networking bug fixes in the new release.
Chris
I tried it both ways with the same results. The problem occurs before the IP address comes into the picture, even before the Ethernet link comes up.
I'll test with MF 4.2 once it's available and see what happens.
JD
Hi Chris,
10MB auto-negotiation issue.
OK. I ran a test with MF 4.2. I didn't use the Netduino Plus board but instead used a different, but compatible, board for testing. The USB and Phy are configured the same on this board as on the Netduino. I initially used MF 4.1 to make sure I could get it running and it ran, exhibiting the same problem. As expected, it's not a hardware issue. Then I moved to 4.2 and I still have the 10MB connect problem. I looked at the EMAC source and didn't see anything obvious in the auto-negotiation code. Could it be something as simple as the timeout? I see that the timeout for Netduino is shorter than when the netduino #define is not set.
Netduino contiues to report this sequence:
DM9161_AutoNegotiate
Valid PHY Found: 31
PHY: Vendor Number Model = 0xA
PHY: Model Revision Number = 0x0
DM9161_DSCSR = 0xF3F6
DM9161_BMCR = 0x3100
DM9161_DSCR = 0x414
Error: AutoNegotiate TimeOut
DM9161_AutoNegotiate
Valid PHY Found: 31
PHY: Vendor Number Model = 0xA
PHY: Model Revision Number = 0x0
DM9161_DSCSR = 0xF3F6
DM9161_BMCR = 0x3100
DM9161_DSCR = 0x414
Error: AutoNegotiate TimeOut
...
This will run forever.
DSCSR reports 'parallel detects signal link ready' but the auto-negotiation completed bit is not set. Thus, the timeout.
This is the capabilities dump:
HalSystemInfo.halVersion: 4.2.0.0
HalSystemInfo.halVendorInfo: Netduino Plus (v4.2.0.0 RC1) by Secret Labs LLC
HalSystemInfo.oemCode: 34
HalSystemInfo.modelCode: 177
HalSystemInfo.skuCode: 4097
HalSystemInfo.moduleSerialNumber: 00000000000000000000000000000000
HalSystemInfo.systemSerialNumber: 0000000000000000
ClrInfo.clrVersion: 4.2.0.0
ClrInfo.clrVendorInfo: Netduino Plus (v4.2.0.0 RC1) by Secret Labs LLC
ClrInfo.targetFrameworkVersion: 4.2.0.0
SolutionReleaseInfo.solutionVersion: 4.2.0.0
SolutionReleaseInfo.solutionVendorInfo: Netduino Plus (v4.2.0.0 RC1) by Secret Labs LLC
SoftwareVersion.BuildDate: Aug 7 2011
SoftwareVersion.CompilerVersion: 400902
FloatingPoint: True
SourceLevelDebugging: True
ThreadCreateEx: True
LCD.Width: 0
LCD.Height: 0
LCD.BitsPerPixel: 0
AppDomains: False
ExceptionFilters: True
IncrementalDeployment: True
SoftReboot: True
Profiling: False
ProfilingAllocations: False
ProfilingCalls: False
IsUnknown: False
It comes up reliably on a 100MB Ethernet.
JD
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users