Note to moderator: Please pin this post if possible. Some time ago, while corresponding with a pololu rep, they suggested I post this topic to see how many were interested.
Please answer this post with a short reply indicating whether you think Pololu should seek FCC approval for the WIXEL, and whether you would support and encourage them to do so. Pololo reps have told me they are considering such certification, but it is a very low priority. Further, they suggested I post this on the forum to see how much interest there is. So Pololu wants to hear from us .
Let's limit any contrary discussions here unless they are from Pololu reps, and let this be more a survey then anything else. Having had significant conversations with both Pololu representatives and TI engineers about this, the limitations that would come with such certification are well understood, but would be of great value just he same.
As we all know, the wixel is likely to be the most ideally packaged support structure for the powerful TI cc2511f32 chip we will ever see. This feature packed System on Chip offers plenty of code space and resources for developing very powerful and commercially viable applications. Thanks to Pololu, the wixel's compact size and small components offer a significant head start to product development. Having developed what I believe is a very marketable product myself based on the wixel, I know this to be true. The only issue is the FCC certification. And while other pre-certified RF modules are available from other suppliers, few offer the versatility and feature set of the wixel.
The challenges, and proposed solutions...
1. The wixel documentation states that it is based on a certified TI reference design, and therefore should pass muster with the FCC. Unfortunately according to a TI rep I consulted with, the TI reference design is slightly different. Apparently some components, such as the impedance matching balun are different in the wixel as compared to TI's design. In addition, the TI reference design in question did not even get its final certification from the FCC until November 2013, after the wixel documentation was published. However, due to the somewhat loose regulations regarding the portion of the 2.4Ghz band in use by the wixel, coupled with the low RF power involved, there is little reason to think any wixel based design would not pass. The problem is, without a reference design to leverage, the testing and application costs associated with certification is a major discouragement to any developer hopeful of marketing a product prototype.
2. It would be somewhat foolish for a Pololu customer to get the wixel certified on their own, with their own application, even if costs were not a concern. Pololu could make a change or improvement to the basic board (for example, there has been some talk about extending the wixel range) at any time. Any such change would then invalidate any independently acquired certification once stock of the old version was gone. This is another reason why it is best for any certification efforts to be spearheaded by Pololu.
3. It has been argued that according to FCC rules, such certification would have limited value, because any code added or changed would invalidate the certification. After having some informal discussions with both TI engineers and some legal advisers, I do not believe this is strictly the case. First of all, the FCC is not out to drop the hammer on everyone trying to turn out a product economically. They are there to ensure harmonious interoperability between the tens of millions of devices available commercially, have always done a good job at this, and are constantly tweaking their rules to help small developers. These rule changes evolve slowly, as they should. But all my research indicates that if Pololu developed a somewhat comprehensive application that fully utilized the radio (such as its bi-directional wireless serial port emulation), and had their module certified with this application active, we as independent developers could then leverage both the hardware module design and our own applications. Granted, it is technically true that our own applications would mean re-certification is necessary, but there are some ways to mitigate this. You could, for example, start with Pololu's pre-certified code and state that you simply added a data layer to the existing application interface (API) provided by Pololu. This is very similar to using another company's RF module and incorporating it into your design. Technically, in both cases, it should still be re-certified. But the cost difference would be a solid 1/10 reduction. And in truth, many start-up companies don't bother re-certifying initially when they are able to start with something that has already passed the process.
Even if it is of limited value for pololu to seek such certification, it would still allow developers to leverage their certification to reduce their own costs. Besides opening the door to much more wixel based product development, doing so should result in enough revenue from increased wixel sales to more than pay for their investment. Lets all let them know we'd appreciate their efforts in this area.