Fix for default preset EU/UK (Narrow)#2216
Fix for default preset EU/UK (Narrow)#2216formtapez wants to merge 1 commit intomeshcore-dev:mainfrom
Conversation
|
+1 for this Right now, a lot of tooling classifies nodes on stock defaults as a custom preset ( For a mesh we can rely on, every node on that channel should use the same LoRa modem settings (frequency, bandwidth, spreading factor, and coding rate - not only the first three). We are already seeing fragmented/degraded meshes in Western Europe because of this split, and it was hard to debug because a CR mismatch is easy to miss next to the correct frequency, BW, and SF. I am surprised this was not raised sooner. Unless there is evidence that CR5 is deliberately better for that EU narrow air setting, we should ship this fix in the next release, otherwise the honest alternative is to change the official EU/UK (Narrow) preset (and API copy) to CR5 so documentation, apps, and firmware all match + sending out a message to the whole MeshCore community. |
In #1820 the default preset was changed to
EU/UK (Narrow), but without settingLORA_CRto 8.The coding rate actually defaults to 5, so that it doesn't match the preset.
These settings are compatible to each other, but the lower coding rate is not very reliable.