Skip to content

T-echo reports TX power 0 dBm #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fustygerbil opened this issue Dec 18, 2024 · 7 comments
Open

T-echo reports TX power 0 dBm #53

fustygerbil opened this issue Dec 18, 2024 · 7 comments

Comments

@fustygerbil
Copy link

fustygerbil commented Dec 18, 2024

When trying to start nomadnet, T-echo (CE firmware 1.73) reports TX power of 0 dBm

[2024-12-18 12:45:38] [Debug] Started shared instance interface: Shared Instance[37428]
[2024-12-18 12:45:38] [Debug] Cleaning ratchets...
[2024-12-18 12:45:38] [Verbose] Bringing up system interfaces...
[2024-12-18 12:45:38] [Notice] Opening serial port /dev/ttyACM0...
[2024-12-18 12:45:41] [Notice] Serial port /dev/ttyACM0 is now open
[2024-12-18 12:45:41] [Verbose] Configuring RNode interface...
[2024-12-18 12:45:41] [Verbose] Waiting for radio configuration validation for RNodeInterface[RNode LoRa Interface]...
[2024-12-18 12:45:41] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting frequency is 867.2 MHz
[2024-12-18 12:45:41] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting bandwidth is 125.0 KHz
[2024-12-18 12:45:41] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting symbol time is 2.05ms (at 488 baud)
[2024-12-18 12:45:41] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting preamble is 22 symbols (45ms)
[2024-12-18 12:45:41] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting CSMA slot time is 50ms
[2024-12-18 12:45:41] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting TX power is 0 dBm
[2024-12-18 12:45:41] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting spreading factor is 8
[2024-12-18 12:45:41] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting coding rate is 5
[2024-12-18 12:45:41] [Verbose] RNodeInterface[RNode LoRa Interface] On-air bitrate is now 3.12 kbps
[2024-12-18 12:45:41] [Notice] RNodeInterface[RNode LoRa Interface] is configured and powered up
[2024-12-18 12:45:41] [Verbose] System interfaces are ready
[2024-12-18 12:45:41] [Verbose] Utilising cryptography backend "openssl, PyCA 44.0.0"
[2024-12-18 12:45:41] [Verbose] Configuration loaded from /home/forest/.reticulum/config
[2024-12-18 12:45:41] [Verbose] Loaded 1 known destination from storage
[2024-12-18 12:45:41] [Verbose] Loaded Transport Identity from storage
@jacobeva
Copy link

Can you paste your interface config file here please? It looks like this configuration of 0dBm is actually set in your config file. If it wasn't, I would expect RNS to complain that the TX power does not match the configured value.

@fustygerbil
Copy link
Author

Sorry, I should have said that I saw the TX power mismatch error with any (config file) txpower value > 0. This situation applies regardless of the configured (non-negative integer) value (even though I did have it set to 0, here, to see what would happen).

Incidentally, running rnodeconf --info returns a maximum TX power level of 22 dBm.

@jacobeva
Copy link

@jeremybox any ideas mate?

@jacobeva
Copy link

jacobeva commented Feb 3, 2025

@fustygerbil Can you confirm if you still have this issue on the current dev branch?

@jeremybox
Copy link

jeremybox commented Feb 5, 2025

I have always used 0db in my device, so I'm not sure what it "should" be.

https://github.com/markqvist/Reticulum/blob/fd6d8ffff82d75f52fe3f3f9c5726a24f55ee4f0/RNS/Utilities/rnodeconf.py#L279

The above is the code that rnodeconf --info returns. It's just a hardcoded array of numbers. When I added the T-Echo code I just copied that 22 from the other lines because I didn't know what that value meant, but the 22dBm isn't polling the actual device itself. Will have to check out the chip's actual max power from spec when I get some time, but I have the same result in a quick test where anything besides 0dBm doesn't function.

Edit: the SX1262 is advertised as being able to go to 22dBm, so I'll have to check into it more.

@jacobeva
Copy link

That's odd.

@fustygerbil
Copy link
Author

fustygerbil commented Feb 25, 2025

@fustygerbil Can you confirm if you still have this issue on the current dev branch?

Sorry, I'm failing to get working firmware on the device now. After DFU upload, rnodeconf /dev/ttyACM0 --firmware-hash $(./partition_hashes from_device /dev/ttyACM0) fails because partition_hashes from_device /dev/ttyACM0 returns Could not get partition hash from device: list index out of range

Running the rnodeconf subprocess in partition_hashes manually as rnodeconf /dev/ttyACM0 -L fails:
[20:19:06 Opening serial port /dev/ttyACM0... [20:19:10 Serial port opened, but RNode did not respond. Is a valid firmware installed? Got invalid response while detecting device

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

No branches or pull requests

3 participants