Skip to content

Conversation

@linser233
Copy link
Contributor

Fix uMesh RF POWER configuration error
(see https://github.com/linser233/uMesh/blob/main/RF_Power.md)

@CLAassistant
Copy link

CLAassistant commented Jan 15, 2026

CLA assistant check
All committers have signed the CLA.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@fifieldt
Copy link
Member

Thanks. Since this uses a power amp, we should also set a TX_GAIN_LORA array in configuration.h , based on the charts at https://github.com/linser233/uMesh/blob/main/RF_Power.png

@linser233
Copy link
Contributor Author

Thanks. Since this uses a power amp, we should also set a TX_GAIN_LORA array in configuration.h , based on the charts at https://github.com/linser233/uMesh/blob/main/RF_Power.png

I have checked the relevant TX_GAIN_LORA config and it does not seem to fit the formula.

For the 30 dBm SKU:
Pout ≈ 11.75 + 0.85 * Pset
For the 33 dBm SKU:
Pout ≈ 21 + 0.55 * Pset

The output power cannot simply be treated as a linear offset. In this case, is there a better way to handle it rather than just using TX_GAIN_LORA 10?

@fifieldt
Copy link
Member

fifieldt commented Jan 15, 2026

@linser233 , see eg :

#define TX_GAIN_LORA 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 10, 10, 9, 9, 8, 7

for how to make an array of gains

(first value is gain added when 1dBm does into the SX1262, second value is gain added when 2dBm into the SX1262, ... 22nd value is gain added when 22dBm into the SX1262)

@linser233
Copy link
Contributor Author

@linser233 , see eg :

#define TX_GAIN_LORA 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 10, 10, 9, 9, 8, 7

for how to make an array of gains

(first value is gain added when 1dBm does into the SX1262, second value is gain added when 2dBm into the SX1262, ... 22nd value is gain added when 22dBm into the SX1262)

In that case, I would need four configuration files — 1262 and 1268, each with 30S and 33S. Would it be better to place them in a separate directory?

@fifieldt
Copy link
Member

fifieldt commented Jan 16, 2026

@linser233 , see eg :

#define TX_GAIN_LORA 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 10, 10, 9, 9, 8, 7

for how to make an array of gains
(first value is gain added when 1dBm does into the SX1262, second value is gain added when 2dBm into the SX1262, ... 22nd value is gain added when 22dBm into the SX1262)

In that case, I would need four configuration files — 1262 and 1268, each with 30S and 33S. Would it be better to place them in a separate directory?

Since the values are relatively close (at least for the different frequencies with the same device), maybe just take an average or a maximum to keep it simple ...

@linser233
Copy link
Contributor Author

linser233 commented Jan 16, 2026

@linser233 , see eg :

#define TX_GAIN_LORA 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 11, 10, 10, 9, 9, 8, 7

for how to make an array of gains
(first value is gain added when 1dBm does into the SX1262, second value is gain added when 2dBm into the SX1262, ... 22nd value is gain added when 22dBm into the SX1262)

In that case, I would need four configuration files — 1262 and 1268, each with 30S and 33S. Would it be better to place them in a separate directory?

Since the values are relatively close (at least for the different frequencies with the same device), maybe just take an average or a maximum to keep it simple ...

What I mean is that my module is available in four SKUs: the SX1268-based versions rated at 30 dBm and 33 dBm, and the SX1262-based version.😂

@linser233
Copy link
Contributor Author

@fifieldt I’ve considered that the 33 dBm SKU is unlikely to be produced in significant numbers, so it may be more practical to simply rename the current YAML files to reflect the 30 dBm SKU.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants