Better client test 12/01/11
Send an e in serial monitor to test
connection failed
disconnecting.
Which is as expected as Ethernet.begin is failing to initiate the shield. This is why Ethernet.localIP is returning 0.0.0.0 in my code. Now the question is, is this because the Ethernet Shield is somehow incompatible with BoArduino or is this shield defective...
I've now tested this thing on multiple networks and even tried crossover cables direct to my laptop. Even sniffed the traffic and absolutely nothing comes out of the Ethernet Shield when attempting DHCP so I'm thinking its a bum unit. Guess I'll swap it out at RS.
Even sniffed the traffic and absolutely nothing comes out of the Ethernet Shield when attempting DHCP so I'm thinking its a bum unit.
Is your UNO recognized when it is plugged into a router? When I run the code my netgear router provides the IP and I can see the wiznet in the connected devices.
I'm not using an UNO, but no the Ethernet Shield is never seen by the network and does not appear in the ARP table. Using code which would initiate a DHCP request hangs at Ethernet.begin(mac) indefinitely. Statically assigned IP via Ethernet.begin(mac, ip, gateway, subnet) does complete but Ethernet.localIP() always returns 0.0.0.0 and the Shield still never appears in ARP.
I use BoArduino for my Arduino work because I prefer breadboards. I do however have a WickedProto Shield adapter for the odd occasion I want to play with "standard" Arduino shields, and it has always worked great in the past.
After rereading the above, I suspect that is where your problem is and not the ethernet shield from RS.
As Arduino is Open Source Hardware, that would be unfortunate, if true.
If it is true, and I would tend to agree that it possibly is, all that it means is that the problem is with your "Arduino", not with the Rat Shack shield.
You would then need to look more closely at your hardware.
While I'm new to this forum, and it's easy to assume the newbie doesn't know much, I can assure you this isn't my first time around the workbench. Even won some design awards many moons ago in Nuts and Volts...
I was hoping someone had some advice on validating proper Ethernet Shield operation at the SPI level as the Arduino Ethernet library, even in 1.0, does a very poor job of providing feedback on what's happening inside the w5100. This may be beyond the scope of the regulars here though, I'm guessing. I'll pop over to adafruit's board and see if anyone there has messed with the 'duino Ethernet Shield.
...and the Mega owners should take note also. Since pins 11-13 are not wired, they are available for general use without interfering with the ethernet shield. The Mega does not use those pins for SPI.
I've now tested this thing on multiple networks and even tried crossover cables direct to my laptop. Even sniffed the traffic and absolutely nothing comes out of the Ethernet Shield when attempting DHCP so I'm thinking its a bum unit. Guess I'll swap it out at RS.
So is the ethernet shield going back to radio shack? The below may explain the 0.0.0.0 issue using the 1.0 IDE.
Did I miss something? The Radio Shack ethernet shield works just like the Arduino ethernet shield. Both use the ICSP connector. Any shield that wants to use the SPI and maintain compatibility with the Mega series must use that.
Just zoomkat's failed attempt at humor. Thanks again for the help SurferTim.
My pleasure!
Like I said in another post, this shield pin setup is relative to the advent of the Mega. Pre-Mega, pins 10-13 were used. Some older ethernet shields do not have the ICSP connector. That is important if you own a Mega and considering an ethernet shield. For ease of use, get one with the w5100 ethernet IC and the 6 pin ICSP connector (2x3) in the center rear of the shield. That is normally the giveaway on Mega compatibility.
Just zoomkat's failed attempt at humor. Thanks again for the help SurferTim.
I think it is funny that it was radio shacks fault for you apparently trying to use misatched parts. RS sells a mega and ethernet shield that apparently work together.