@ PiWi
I find the same behavior as your last 2 posts running the latest versions of Valkyrie’s code on a Netduino Plus 2 (WRL-CC3000V2 ). In my case, the last version that will serve a web page after specifying an access point is cc3000-29055.zip.
Absolutely I’m still working on this. For most of November I was testing reliability and that meant leaving it running for days/weeks and debug the failure. I have put in place quite a few workarounds for quirks, but it is running very well now. In the last two weeks, I’ve had a ton of check-ins and made all the samples work properly again. Local Name resolution is now automatic. If you pass the name in the constructor, without doing anything else, it will enable mDNS and NetBIOS naming. SmartConfig is working well. But my focus has been the web server, which is also working well.
If you haven’t tried it in a while, I encourage people to try it again. The library makes .NET MF the easiest platform for WiFi, IMHO. The web server sample is like 10 lines of code! I am waiting for the next firmware version from TI before declaring the project in the “Beta” stage.
Great! I’m also very happy to see that you are focusing on UDP. Can’t wait until I can get a hold of a CC3000 module and switch my project’s wifi over to it :whistle:
Looks like you guys have got this cracked! I have been using the CC3000 for a number of months now, and it’s a great sensor and well priced. I have 2 at the moment one from Adafruit and the other from LS Research, they both work well. I am currently using them with C and C++. For some reason I can’t get on with C#, my loss I guess, maybe one day I will put more brain cells on it :wall:. After reading the whole thread I noticed that there is a question about power requirements, the only document I could find giving this information was from LS Research. The Tx current can be ~350mA so care should be taken when connecting power.
The Adafruit board has some extra components that might make it difficult to use (a voltage regulator and a shifter thingy). Great for Arduino, bad for Cerbuino ???
If I were to do it right now, you could make a gadgeteer module with a WRL-3000 and a breakout https://www.ghielectronics.com/catalog/product/405 but, be prepared to add 80 ohm resistors in series with each of the SPI pins (MISO, MOSI, and CLK).
Why is that important? A or B are plenty fast for almost any need these micros can conjure up.
Are you saying you’re going to make an adapter to the Embedded Adventures board or you’re going to make a Gadgeteer equivalent? It seems a Gadgeteer equivalent would be very easy and much cheaper than trying to just adapt theirs. You taking pre-orders yet?
@ ian, It’s important because of range. a/b/g just can’t cover my house, and its the number #1 problem that I had to try and “fix” when it came to wifi.
The CC3000 docs give a fair amount of guidance on this. It shouldn’t be a big problem. Of course, it’s also showing it on a 4 layer board. So, maybe its not quite as simple & cheap as most breakouts.
No I was just going to do an adapter board for the WRL-3000 in the first instance. Why would I do a module when Gus has a design sitting around as well as the manufacturing capability and distribution capability?