Radio parameter mismatch on lora32_v21 #39
Comments
|
Thanks for the bug report. Have you tried powering off the device completely and then connect it back to power and then try to bring it up? Is there anything showing on the display (if present)? I believe @jeremybox had a similar issue before. If that doesn't work, I will investigate further :) |
I exclusively power my devices via usb, since I have no batteries to connect them to. The physical power switch on them doesn't seem to do anything (on all firmwares, on all versions). I assumed this is not a bug. I power them off simply by physically connecting the usb cable (I hope this isn't bad). Is this powering it off completely? I'm not sure.
The display functions as normal prior to starting Please tell me if I misunderstood any of your questions :) |
|
Trying to configure the transmit power manually beforehand with
|
|
What is the output from a terminal when you just try to connect to the device with minicom/screen/tio or whatever terminal you like? |
|
@jeremybox |
|
one of the things I noticed with the techo stuff was it would repeat (not once every 5 second but several times a second) nonsense characters when it was unhappy and trying to initialize the radio. adding |
Yes :) That's quite strange, it seems that the RNode is initialising but whatever bandwidth and TX power values it is returning are incorrect. This won't have anything to do with disabling firmware validation, since that definitely works fine on the ESP32. @FountainOfInk Can you please try running |
|
@jacobeva Here you go: (The first run reports a transmit power of 143dBm, and a frequency of 915mhz, and the second two report 0dBm and 0mhz.) And again: A third time: |
|
Can you please try this again now? Sorry for taking so long :) |
|
Aha, no worries. I tried it again, and the same issue arises, in the same way. Additionally, the display graphics seem to be corrupted now (particularly the version number and the top of the screen immediately after powering on the device.) I will probably record a video of this and create a new issue for it later. |
|
That's interesting. I think I've seen the version number bug you're on about, I'll investigate that. Does the TX power set correctly, or does this not get set correctly when powering up also? |
|
The TX power follows the same pattern as it did before. Everything seems to be the same as before the commit. |
|
Okay, that's interesting. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary:
After successfully building and flashing the firmware on my lora32_v21 boards, rnsd reports that the TX power and bandwidth reported by the board does not match, and thus the RNode setup fails. This issue does not occur when using
rnodeconf --autoinstall, nor when manually building and flashing markqvist's firmware. (I have noticed that sometimes it is only the TX power that is mismatched, but usually it's both the TX power and the bandwidth.)Versions:
rnspackage version (from pip):0.7.7rnsdversion:0.7.7rnodeconfversion:2.1.3Repository commit hash:
2cdf2951e6f68074a7cf6b381ca22562d6101e5fConfig:
RNode config block:
Steps to reproduce:
Clone this repository:
git clone https://github.com/liberatedsystems/RNode_Firmware_CE && cd RNode_Firmware_CE/Build and flash the firmware:
make firmware-lora32_v21 && make upload-lora32_v21Run
rnsd:rnsd -vExpected outcome:
rnsdreports no errors, and successfully brings up the RNode interface.Example output:
Actual outcome:
rnsdreports that the radio parameters are mismatched, and is unable to bring up the RNode interface.Actual output:
The text was updated successfully, but these errors were encountered: