Fixed-Channel, No-Duty-Cycle Operation – How to Achieve This with MM8108?

General
1

Hello everyone,

we are currently evaluating the MM8108 for a deployment scenario where EU duty‑cycle restrictions (ETSI EN 300 220 / ERC 70‑03) do not apply, because the system operates in an RF‑isolated environment under a separate frequency authorization that explicitly allows continuous transmission and fixed‑channel operation in the 863–868 MHz band.

We understand that Morse‑Micro firmware enforces regulatory limits on two levels:

  1. Host‑side regulatory database (which we can modify)

  2. BCF‑embedded regulatory domain (FIELD_TYPE_BCF_REGDOM)
    – which we cannot modify and which enforces duty cycle and channel rules at firmware level

On the host side we can configure the required S1G channels with 100% duty cycle.
However, based on the SDK documentation, the BCF-level regulatory domain acts as a hard lower bound, meaning the firmware may still enforce EU duty-cycle limits even if the host configuration allows 100%.

Our questions to the community / Morse‑Micro team:

  1. If our deployment is outside standard EU regulatory constraints,
    is it possible to operate the MM8108 without firmware-level duty‑cycle enforcement?

  2. Do we need a custom BCF with relaxed regulatory fields, or is there an official mechanism (debug BCF, test profile, custom regdom, etc.) to allow fixed‑channel, no‑duty‑cycle operation?

  3. If a custom BCF is required, what is the correct process to request one?

We only need clarification on whether our understanding is correct and how we should proceed within the Morse‑Micro ecosystem.

Thanks for any guidance!

2

We’re a bit hesitant to publish information on how to bypass regulatory restrictions, so I’ll reply to this by email.

Thanks,
-Zandr

3

Thanks for the update. Good to hear that you’ll follow up by email.

For context: we’ve already tried multiple times to contact support directly, but were repeatedly redirected back to the community. After we explained in detail why we believe we do not fall under the mentioned restrictions, our follow‑up emails were no longer answered. Our request regarding the BCF Editor also remains unanswered.

That’s why it’s important for us that this issue is now being addressed. We’ll wait for your email.