Valkyrie-MT

What was that shiny new Netduino hardware seen in the keynote?It's not officially announced quite yet

Piwi, I am interested too.  My wifi requirements are tough though.  It has to have WPS, and some other way of joining without an interface.  It has to support SSL and have at least 6 sockets.  And, it has to come in an FCC certified unit. 

Yes, I am still working on the cc3000 driver, almost everyday.  The reality is that the cc3000 firmware has had too many bugs to work.  Unfortunately, TI did not try to fix the issues until the Sparkcore guys started complaining.  Even still there is a bug that combines UDP packets for which there is no workaround.  I've been in contact with TI, and I've even had a call on the phone to discuss issues.  I've had a variety of unreleased firmware builds in the last few months.  Most of the changes where made to fix the ARP issue which impacted the sockets as well. 

Having said all that.  The last version DID fix a lot and I know another build is coming.  So, the cc3000 is looking better.  However, I am still working around issues.  In the last week I rewrote the code to stop using the cc3000 Profiles because for some reason they can just stop working.  And, I am testing a DNS lookup using UDP sockets because the built-in functionality seems to work unreliably. 

But, when I get the cc3100 tomorrow, I'll probably focus more on that. 

I just ordered the cc3100 from TI.  It has some great improvements like SSL, built-in web server, WPS for easier pairing, and price (around $7 per chip for large volume).  However, it looks a bit less DIY friendly.  The example board is 4-layer, the chip appears to require an SPI-Flash companion chip and you'll need a crystal and some inductors in addition to the antenna components.  And the pin pitch of the package looks VERY small. 

I'll take a hard look at it. 

One of my goals for mIP was to simplify the end-user experience for the typical Connection-less UDP request/response and simple HTTP web requests and HTTP web servers. 

To some extent, I was concealing TCP socket access to avoid intimidating users with complex APIs and concepts.  Rest assured that you can still do TCP socket communication, it is just under the covers.  The HTTP implementation uses all TCP communication and is in fact a working example implementation, although not one I'd recommend as a simple example. 

In the TCP.cs file, you will find a Connection class.  This is essentially the TCP Socket class.  You can create a new Connection and the Send methods on that class are all TCP Send calls. 

The code would look something like this:

<code>

class TcpProgram

{

public static void Main()

{

Networking.Adapter.Start(new byte[] { 0x5c, 0x86, 0x4a, 0x00, 0x00, 0xdd, "mip", InterfaceProfile.NetduinoGo_Socket3_ENC28);

var tcpSocket = new Networking.Connection() { RemoteIP = new byte[] { 192, 168, 0, 1 }, RemotePort = 80 };

tcpSocket.OnConnectionPacketReceived += TcpSocket_OnConnectionPacketReceived;

tcpSocket.SendAsync(new byte[] { 1, 2, 3, 4 });  // Send some bytes

while (true) Thread.Sleep(100);

// When you are done, you can close the socket

tcpSocket.Close();

}

static void TcpSocket_OnConnectionPacketReceived(Packet thePacket)

{

// A TCP Packet was received.  If the message is long, you will have to piece the packet contents back together to  get the full message. 

Debug.Print("New Packet of length: " + thePacket.Content.Length + ", contains: " + thePacket.Content.ToHexString());  // Here is the packet data

// Note: there are other useful properties on the Packet Class

}

}

</code>