Create 2024-02-14-modem-presets.md #6
Conversation
|
Will update with our regular template (below current) now that I've found it. |
|
why do you say names "do not represent either theoretical or real world implications/effects on LoRa radio peformance."? They are based on the preset |
@andrekir Because we have no evidence (or it's undocumented) that ShortFast's Link Budget of 143dB and Data Rate of 10.94 kbps equates to a short distance, especially because we haven't even defined what "Short Range" is. For LoRa, in a theoretically perfect scenario, does that mean 2 miles? Does it mean 20 miles? Does it mean 0.5 miles? It's like saying I took a really short jog, but I'm a jogger who normally runs ultramarathons. What distance did I jog? Who knows. We don't want users to make assumptions because then they use the settings improperly, similarly to what we've seen with Hops. |
|
Another example is that MediumFast vs. MediumSlow is not Medium but Slow...it's more like 6 vs 7 on a 1-10 scale. It's "slower" but not "slow". |
|
|
Modem Preset naming convention renaming
I have submitted this PR/RFC using @tekstrand's template.
PR Branch Link
The words "Long", "Medium", "Short", "Fast", and "Slow" used in the modem presets do not represent either theoretical or real world implications/effects on LoRa radio peformance. The terms used for the Mesthastic modem presets, such as "LongFast", are misleading. The terminology such as "Fast", "Slow", "Long", and "Short" cause users to assume that each preset has tradeoffs. For example users may assume "MediumFast" is only for moderate (which is not defined or tested) ranges, while also assuming the Slow option will result in slow message sending or some other vague effects.