Xinyuan-LilyGO / LilyGo-LoRa-Series

LILYGO LoRa Series examples
675 stars 183 forks source link

How to use MESHTASTIC with more personalised configuration? #167

Closed dms-rj closed 4 months ago

dms-rj commented 5 months ago

I will try in soon the CLI option to disbord the android and desktop meshtastic app limitation, that presents only the VeryLong_Slow, and others. That, VeryLong_Slow, is the reason that I opened this Ask, because it is the only option available in the meshtastic android app, in the CLI seems to be more options and I will try it, but not presents the 10.4KHz that I will speak at this text down in follow, and in the link https://meshtastic.org/docs/configuration/radio/lora/#lora-config-client-availability it's available only the 31KHz, less than it is not possible to set I guess, that will be tested in soon too. 1- I want to obtain the best config to get the most long range and don't matter to me how data per second is sent, I want long distance to send an information, such as GPS location, little packets of data (telemetry) and short messages, such as "I arrived and I am fine!" or "The mission runned very well and we will return in 30 minutes!". I suposed that in the worst case, the most long that these messages would travel a long distance in up to 10s or a little more, maybe 60s; 2- I know the range depends a lot of factors but in the right conditions, with the right link prediction, how I can put in the T-Beam the right config, offset the app and CLI, and forces the T-Beam to work with my lab config, I mean, I have some parameters that I want to put in radio and prove it's capacity, it is my academical work based on this platform; 3- the data is in semtech SX1261/2 datasheet, that in some tables in its initial pages presents the following parameters that I want to test:

lewisxhe commented 5 months ago

You should ask questions on the forum

github-actions[bot] commented 4 months ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 4 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.