Hi Jared,
I’ve been developing a nRF9160 Feather based real-time departure board for use on the AT&T network. Unfortunately, after speaking to a couple AT&T reps it seems I won’t be able to use the feather going forward because the device lacks PTCRB certification.
Do you have any plans on getting the nRF9160 Feather PTCRB certified in the future?
Hi @Voxorin
Sorry, I will not be because it depends on the final application of use. AT&T and Verizon are picky about their end device certifications. You usually have to test to a certain firmware version (the actual firmware being deployed). Since there’s no feasible way to do that on my end, it’s up to other folks to get things tested themselves.
You can get around it by not directly using AT&T. Ultimately this stuff changes all the time so YMMV.
jaredwolff That’s what I figured. Unfortunately the company I’m currently working with doesn’t want to contract with another carrier, so I’m stuck with AT&T.
Interestingly the Particle Boron claims to be PTCRB End Product certified. I wonder if they’re able to do that because the “OS” is considered separate from the user application.
I’m not not very familiar with Particle’s products, but I wonder if something similar could be done with a particular version of Zephyr to get a certification.
Interestingly the Particle Boron claims to be PTCRB End Product certified. I wonder if they’re able to do that because the “OS” is considered separate from the user application.
I think you’re correct. I could get the device certified but it would have to be with a generic AT firmware like how NimbeLink does it. It doesn’t really cater to people who want to run everything on the same core.
