OK - I completely acknowledge that it clearly states the CC3000 works on 802.11b/g only in both:
- The TI datasheet - http://www.ti.com/lit/ds/symlink/cc3000.pdf
- The tech specs section of https://www.spark.io/
But I’d missed this. It was only when playing with my CC3000 device that I noticed that I could configure it fine from my old Linux laptop but not from my newer Macbook Air - the difference being one was connected to my AP using 802.11g and the other with 802.11n.
If I switch my AP to support only 802.11g then both the Linux and Mac laptops play well with the CC3000 (it was easy to switch off 802.11n in my AP, I didn’t find an obvious way to just force my Mac to 802.11g).
So even though this was clearly stated is it not a serious limitation?
802.11n has been around since at least 2009 (many manufacturers we’re producing APs before the standard was finalized in Oct 2009) and it’s been supported in iPhones since the iPhone 4 was released in Jun 2010.
So there are a lot of devices (smartphones, laptops, etc.) that are connected using 802.11n to their APs.
Is this not a serious issue for any device that targets non-tech savy end users? It seems a serious proportion will be unable to configure their devices - or am I missing something?
I think most consumers just about know what wifi is - but even if you stuck a massive sticker on your device saying “802.11b/g only” I don’t think it would mean much to many people.
I don’t know if Android or iOS provide an easy mechanism to force the current wifi connection to a particular variant of 802.11 but I certainly don’t see any obvious way to do this in a standard way on desktop OSes (e.g. Mac OS X, Windows or Linux).
At the moment the limitation that it does not support 802.11n would seem to me to limit the CC3000 to a more tech savvy market segment, i.e. one that will be a bit stoical when they notice that they really should have read the data sheet for once when they work out why the device isn’t getting it’s configuration data.
Note: my current CC3000 device isn’t a Spark Core rather it’s an Adafruit CC3000 breakout board, but I value the quality of the discussion here