SP1ML module: How to configure for full 779MHz–956MHz frequency range?

Welcome.

As part of an Internet of Things project, I am using SP1ML radio modules to communicate between sensors. The whole thing will be monitored by another chip, which will already be connected to the internet. There are 2 modules on the market at 868MHz and 915MHz, however the datasheet says the range is from 779MHz to 956. My question is, how do I get access to such a large bandwidth?

Greetings.

Hi,
The range of frequencies the module can operate on is one thing. The range of frequencies you are allowed to use is another. In Poland you are allowed to work in the ISM 868MHz band. On Wiki or anywhere you will find details, equally important, such as maximum power and transmit time/channel loading. The width of the channel is focussed.
If you want to work on other frequencies the range cannot exceed 10m (as far as I remember).
And the datasheet clearly says there are two versions, one 863 to 870 MHz operation (SP1ML-868) the other 902 to 928 MHz operation (SP1ML-915).

Yes I know I can work on 868 in Poland, I'm just looking for the difference between these two chips SP1ML - 868 and SP1ML - 915, the filter/balun is used the same, well how did they change this frequency?

I am convinced that the balun and antenna are different. Layout-wise, of course, it's the same set of coils and capacitor, only that the values are a few pF and nH different.

See datasheet SPIRIT1 -> Table 3. BOM for different bands.

vonar wrote:

See datasheet SPIRIT1 -> Table 3. BOM for different bands.

Thank you for your help, I don't know how I could have missed it ;D

I have another question about programming. Would it be a good way to program the processor already built into such a module? Is it best to control such a processor using another one? The manufacturers even put out SWD programming notes. In the note I found this information:
"These signals are the serial wire debug (SWD) interface to the STM32L microcontroller, supporting the development and loading of custom firmware."

Remember that two processors = problems with remote software exchange, bootloaders etc. One CPU has to program the other. Better to avoid such situations, use this STM if there are enough resources and peripherals for SPI.