search

cfr34k / t-echo-lora-aprs

LoRa-APRS firmware for the Lilygo T-Echo
Other
21 stars 4 forks source link

Missing "wide1-1" for digipeating #21

Closed IZ1HMT closed 3 months ago

IZ1HMT commented 3 months ago

Please can you implement the "wide1-1" string in the firmware?

cfr34k commented 3 months ago

WIDE1-1 was included some time ago, but was removed in favor of destination call digipeating. See https://github.com/cfr34k/t-echo-lora-aprs/commit/b39ec4d9f6469aacebe47e4f6c6bcb2ec857ff16

As digipeating is usually not done for LoRa-APRS and airtime is a precious resource, this is a reasonable compromise. If you really need WIDE1-1, you can just revert the above commit.

IZ1HMT commented 3 months ago

Thanks for your kind reply. I raised the problem because some digipeater firmwares do not accept and therefore do not repeat packets sent in this way. I will do my best to ensure that the developers of these firmware introduce support.

IZ1HMT commented 3 months ago

I now notice that neither the firmware of IW1CGW https://github.com/iw1cgw/LoRa_APRS_Meteo_dds-cgw nor that of Ricardo CA2RXU https://github.com/richonguzman/LoRa_APRS_iGate support this mode of DIGI. I think in the next firmware it would be better if I go back to the old wide1-1 to maintain better compatibility. With your setting which DIGI firmware do you use to make the beacon repeat correctly?

cfr34k commented 3 months ago

I have never actually seen a digi/iGate that does digipeating on LoRa APRS, even when WIDE1-1 was still included, so I assumed it was not really relevant. That’s also what I hear from other users with different devices. At least here in Germany digipeating does not seem to be very popular. Maybe that’s different in other countries?

However, I still don't really like switching back to WIDE1-1 by default, as it increases the airtime by about 10% for every packet (which is a lot considering the channel is accessed randomly by many users). However, I can add an option that allows to select the addressing mode from:

Not sure yet if no digipeating or destination call digipeating will be the new default.

I will do my best to ensure that the developers of these firmware introduce support.

That would be really nice!

IZ1HMT commented 3 months ago

Yes, in Italy "pure" Dgipeaters are popular, especially in the mountains and where there is no internet connection. So that the beacons will be picked up by the first available iGate. It would be great to have a menu option like you described. At the moment I am forced to use the old 0.8.1 due to my difficulties in compiling a modified firmware.

cfr34k commented 3 months ago

Hi, I have now added a configuration option as described in my last post. You can find it in the APRS Advanced configuration menu.

I could not test it yet on the device, as I don't have it nearby, but I'm quite confident that it works (the changes were not too large). Here is a build, feel free to test:

t-echo-lora-aprs-with-sd-v1.0-2-gcc438bf.uf2.gz

IZ1HMT commented 3 months ago

Thanks so much! Now I'm on holiday with my t-echo but I don't have a computer available. When I return in a few days, I will try the new firmware and update you.

DayleDrinkwater commented 3 months ago

Hi,

I've been following this in the background. I've just tried the new version and it seems to be working. My digipeater is digipeating the packets correctly and they are appearing on the T-Echo.

Thanks, Dayle M0OUE

IZ1HMT commented 3 months ago

I found a computer and installed the file. It works perfectly.

cfr34k commented 2 months ago

Sorry for the late reply. Thanks a lot for testing. I have released this change in Version 1.1.