Author Topic: Test Lab costs for RF testing without full Bluetooth compliance.  (Read 992 times)

0 Members and 1 Guest are viewing this topic.

Offline MrRT84Topic starter

  • Newbie
  • Posts: 1
  • Country: de
Hi all,

I’ve some questions about RF certifikation, compliance and pre-compliance tests in test labs. Basically, we got a quote from a test lab which seems very expensive and i can not estimate if all tests are neccesarey or not.

But first, I will give you with some basic information.
  • We use a EFR32BG1x SoC from SiLabs.
  • We use the Silabs BLE stack but do not want to use "Bluetooth" (as a name) nor the Bluetooth logo.
  • We just wanna compley with the IEEE 802.15.
  • We hope to skip all those expensive bluethooth RF testing.
  • The end product will be certified for the EU, US and JP.

We know, that we have to make extended EMC tests to comply with FCC / CE… like the EN 300328, EN 301489 and FCC Part 15.
But what are the bare minimum tests and COSTS for a 2.4 GHz device without all those bluetooth naming and licensing stuff (+Bluetooth SIG = 8.000 USD)?

If we do not want to make full bluetooth compliance does it make seens to use a pre-certified module like the BGM13S? We would have to make EN 300328, EN 301489 and FCC Part 15 tests anyways? So, if we do not want to name it „Bluethooth“ Device nor use the Bluetooth or BLE Logo, what are the benefits of using such modules, besides reducing riskes of failing EMC tests?
 
Does anyone have some numbers or information how much such tests cost?
 
Do we really need to make a bluetooth full conformance (BT Core spec. 5.1 or lower) test?

What about the Bluetooth BQC Service, TCB Service and RCB Service? Do we have to use such services, if we do not use bluetooth?

I’m thankful about any information and experience on that.

Thanks
 

Offline Smokey

  • Super Contributor
  • ***
  • Posts: 2572
  • Country: us
  • Not An Expert
Re: Test Lab costs for RF testing without full Bluetooth compliance.
« Reply #1 on: May 01, 2022, 09:00:28 pm »
Bump for an interesting question that never got an answer.  Especially the part about being BLE "compatible" without using the Bluetooth name.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf