Love the idea, hate the presentation. Also, wasn't able to find the simulator link, is the simulator not publicly accessible?
Also, one friendly tip - if you are EU-based and plan to sell the hardware, drop the ESP32/wireless. Yes, that would mean no wireless pads, but it will make regulatory compliance a lot easier. Maybe replace with a breakout socket (not sure if that is allowed).
> Or do you still need the product as a whole to be compliant?
I'm not 100% sure, but I've been thru a round on RED (on a full-custom device) and much of it involved security and authentication within application software. RED basically boils down to "we are fucking tired of your little plastic shit running botnets, the customer are clueless, so fix it if you want to sell it".
So actual code review and running tests in front of the auditors, basically everything short of a pentest, not just RF PHY stuff. So my gut feeling is that while you can skip the stuff related to RF PHY if you use an off-the-shelf module, the rest will is still be on you.
> the module is FCC compliant with its number written on it.
Just like I'm telling in the sibling comment - IANAL but that's probably not enough for EU. RED cares not just about RF PHY, but also for example if you can ran a FOTA update, and if you do, is the key secure enough. So module being compliant simplifies things, but your device might still require a cert as a whole. Again IANAL, this is based on my experience with certifying a full-custom device.
Love the idea, hate the presentation. Also, wasn't able to find the simulator link, is the simulator not publicly accessible?
Also, one friendly tip - if you are EU-based and plan to sell the hardware, drop the ESP32/wireless. Yes, that would mean no wireless pads, but it will make regulatory compliance a lot easier. Maybe replace with a breakout socket (not sure if that is allowed).
Isn't the appeal of those esp32 modules that they're already compliant, as a module? Or do you still need the product as a whole to be compliant?
> Or do you still need the product as a whole to be compliant?
I'm not 100% sure, but I've been thru a round on RED (on a full-custom device) and much of it involved security and authentication within application software. RED basically boils down to "we are fucking tired of your little plastic shit running botnets, the customer are clueless, so fix it if you want to sell it".
So actual code review and running tests in front of the auditors, basically everything short of a pentest, not just RF PHY stuff. So my gut feeling is that while you can skip the stuff related to RF PHY if you use an off-the-shelf module, the rest will is still be on you.
Based on quick googling the certifiers agree with me (but again, that's not same as as a court saying that's true): https://compliancetesting.com/ce-certification-for-espressif...
https://emcfastpass.com/fcc-rules-kits-subassemblies/
Yes there is a link on the homepage.
About the ESP, the module is FCC compliant with its number written on it.
> the module is FCC compliant with its number written on it.
Just like I'm telling in the sibling comment - IANAL but that's probably not enough for EU. RED cares not just about RF PHY, but also for example if you can ran a FOTA update, and if you do, is the key secure enough. So module being compliant simplifies things, but your device might still require a cert as a whole. Again IANAL, this is based on my experience with certifying a full-custom device.
So, why are there 3 of them? I can make several guesses but I don't see any concise answers on the page.
[flagged]
[flagged]