Problem with homemade RNode on 169MHz #37

tomdelta · 2022-04-04T15:18:15Z

tomdelta
Apr 4, 2022

Hello Mark,

I made my own RNode based on your design with the AVR ATmega1284P and the RFM98PW 169MHz module. With the Firmware 1.21 it worked and transmitted with Nomadnet. Now after update to 1.27 itś not working.
This is the log from Nomad:
nomadnet
[2022-04-04 16:43:01] [Debug] Started shared instance interface: Shared Instance[37428]
[2022-04-04 16:43:01] [Debug] Bringing up system interfaces...
[2022-04-04 16:43:01] [Debug] Skipping disabled interface "Default Interface"
[2022-04-04 16:43:01] [Debug] Skipping disabled interface "TCP soundmodem KISS Interface"
[2022-04-04 16:43:01] [Notice] Opening serial port /dev/ttyUSB0...
[2022-04-04 16:43:03] [Notice] Serial port /dev/ttyUSB0 is now open
[2022-04-04 16:43:03] [Verbose] Configuring RNode interface...
[2022-04-04 16:43:03] [Verbose] Wating for radio configuration validation for RNodeInterface[RNode LoRa Interface]...
[2022-04-04 16:43:03] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting frequency is 169.2 MHz
[2022-04-04 16:43:03] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting bandwidth is 125.0 KHz
[2022-04-04 16:43:03] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting TX power is 5 dBm
[2022-04-04 16:43:03] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting spreading factor is 8
[2022-04-04 16:43:03] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting coding rate is 5
[2022-04-04 16:43:03] [Verbose] RNodeInterface[RNode LoRa Interface] On-air bitrate is now 3.12 kbps
[2022-04-04 16:43:03] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting state is offline
[2022-04-04 16:43:03] [Error] Radio state mismatch
[2022-04-04 16:43:03] [Error] After configuring RNodeInterface[RNode LoRa Interface], the reported radio parameters did not match your configuration.
[2022-04-04 16:43:03] [Error] Make sure that your hardware actually supports the parameters specified in the configuration
[2022-04-04 16:43:03] [Error] Aborting RNode startup
[2022-04-04 16:43:03] [Error] The interface "RNode LoRa Interface" could not be created. Check your configuration file for errors!
[2022-04-04 16:43:03] [Error] The contained exception was: RNode interface did not pass configuration validation

Answered by tomdelta

Apr 5, 2022

Looks like it works!?? I#ll try to check trnasmission

$ nomadnet
[2022-04-05 17:24:03] [Debug] Started shared instance interface: Shared Instance[37428]
[2022-04-05 17:24:03] [Debug] Bringing up system interfaces...
[2022-04-05 17:24:03] [Debug] Skipping disabled interface "Default Interface"
[2022-04-05 17:24:04] [Debug] Skipping disabled interface "TCP soundmodem KISS Interface"
[2022-04-05 17:24:04] [Notice] Opening serial port /dev/ttyUSB0...
[2022-04-05 17:24:06] [Notice] Serial port /dev/ttyUSB0 is now open
[2022-04-05 17:24:06] [Verbose] Configuring RNode interface...
[2022-04-05 17:24:06] [Verbose] Wating for radio configuration validation for RNodeInterface[RNode LoRa Interface]...
…

View full answer

4c3e · 2022-04-04T22:08:05Z

4c3e
Apr 4, 2022

Hello, are you still having trouble with this?

3 replies

tomdelta Apr 4, 2022
Author

yes

4c3e Apr 4, 2022

Did you try re-flashing with the latest version of rnodeconfigutil?

tomdelta Apr 5, 2022
Author

I installed the newest version and reflashed the node

markqvist · 2022-04-05T12:06:43Z

markqvist
Apr 5, 2022
Maintainer

I don't know if you have hooked up RX and TX LEDs in your version, but if you did, can you please tell me if any pattern is being flashed from them when trying to initialise the radio (if any), and could you also check that no errors are being printed to the serial console when the device starts?

2 replies

tomdelta Apr 5, 2022
Author

The rnode 169 is based on your RNode scematic. Only LORA modul changed and aditional programming port. This is a video if I start nomad.

VID_20220405_164757.mp4

markqvist Apr 5, 2022
Maintainer

Thanks for that Tom. Can you try wiping the EEPROM and flashing it again with the autoinstaller? I just uploaded a new build about an hour ago. Or did you already do it? (it still says version 1.27, since I basically only changed one line)

markqvist · 2022-04-05T12:21:14Z

markqvist
Apr 5, 2022
Maintainer

Actually, first try just wiping the EEPROM with --epromwipe, and reinstalling with --autoinstall. This is a bit of a long shot, since I don't have your hardware to test with, but just tried something ;) There might have been a bug in the radio validation for homebrew RNodes on 1284p. Try now and see if it works, and let me know!

2 replies

tomdelta Apr 5, 2022
Author

I made update rnodeconf and eepromwipe then reinstall rnode:

rnodeconf -a

Hello!

This guide will help you install the RNode firmware on supported
and homebrew devices. Please connect the device you wish to set
up now. Hit enter when it is connected.

Detected serial ports:
[1] /dev/ttyUSB1 (USB-Serial Controller, None)
[2] /dev/ttyUSB0 (FT230X Basic UART, DN0248BV)

What serial port is your device connected to? 2

Ok, using device on /dev/ttyUSB0 (FT230X Basic UART, DN0248BV)

Probing device...
[2022-04-05 17:21:29] Device connected
[2022-04-05 17:21:29] Current firmware version: 1.27
[2022-04-05 17:21:29] Trying to read EEPROM...

The device seems to have an RNode firmware installed, but it was not
provisioned correctly, or it is corrupt. We are going to reinstall the
correct firmware and provision it.
What kind of device is this?

[1] Original RNode
[2] Homebrew RNode
[3] LilyGO T-Beam
[4] LilyGO LoRa32 v2.0
[5] LilyGO LoRa32 v2.1

? 2

Important! Using RNode firmware on homebrew devices should currently be
considered experimental. It is not intended for production or critical use.
The currently supplied firmware is provided AS-IS as a courtesey to those
who would like to experiment with it. If you want any degree of reliability,
please use an actual RNode from unsigned.io. Hit enter to continue.

What kind of microcontroller is your board based on?

[1] AVR ATmega1284P
[2] AVR ATmega2560
[3] Espressif Systems ESP32

? 1

Ok, that should be all the information we need. Please confirm the following
summary before proceeding. In the next step, the device will be flashed and
provisioned, so make that you are satisfied with your choices.

Serial port : /dev/ttyUSB0
Device type : Hombrew RNode (Band capabilities unknown)
Platform : AVR
Device MCU : ATmega1284P
Firmware file : rnode_firmware_latest.hex

Is the above correct? [y/N] y
[2022-04-05 17:21:41] Downloading latest frimware from GitHub...
[2022-04-05 17:21:42] Firmware download completed
[2022-04-05 17:21:42] Generating a new signing key...
[2022-04-05 17:21:42] Flashing RNode firmware to device on /dev/ttyUSB0

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e9705 (probably m1284p)
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "update/rnode_firmware_latest.hex"
avrdude: writing flash (24858 bytes):

Writing | ################################################## | 100% 4.73s

avrdude: 24858 bytes of flash written
avrdude: verifying flash memory against update/rnode_firmware_latest.hex:
avrdude: load data flash data from input file update/rnode_firmware_latest.hex:
avrdude: input file update/rnode_firmware_latest.hex contains 24858 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 5.20s

avrdude: verifying ...
avrdude: 24858 bytes of flash verified

avrdude: safemode: Fuses OK (E:00, H:00, L:00)

avrdude done. Thank you.

[2022-04-05 17:21:54] Done flashing
[2022-04-05 17:21:54] Opening serial port /dev/ttyUSB0...
[2022-04-05 17:21:56] Device connected
[2022-04-05 17:21:56] Current firmware version: 1.27
[2022-04-05 17:21:56] Reading EEPROM...
[2022-04-05 17:21:56] Clearing old EEPROM, this will take about 15 seconds...
[2022-04-05 17:22:12] Loading signing key...
[2022-04-05 17:22:12] Bootstrapping device EEPROM...
[2022-04-05 17:22:15] EEPROM written! Validating...
[2022-04-05 17:22:16] EEPROM checksum correct
[2022-04-05 17:22:16] Device signature validated
[2022-04-05 17:22:16] EEPROM Bootstrapping successful!

RNode Firmware autoinstallation complete!

markqvist Apr 5, 2022
Maintainer

Ok, can you post the debug output when starting nomadnet now? Is it the same?

tomdelta · 2022-04-05T15:27:06Z

tomdelta
Apr 5, 2022
Author

Looks like it works!?? I#ll try to check trnasmission

$ nomadnet
[2022-04-05 17:24:03] [Debug] Started shared instance interface: Shared Instance[37428]
[2022-04-05 17:24:03] [Debug] Bringing up system interfaces...
[2022-04-05 17:24:03] [Debug] Skipping disabled interface "Default Interface"
[2022-04-05 17:24:04] [Debug] Skipping disabled interface "TCP soundmodem KISS Interface"
[2022-04-05 17:24:04] [Notice] Opening serial port /dev/ttyUSB0...
[2022-04-05 17:24:06] [Notice] Serial port /dev/ttyUSB0 is now open
[2022-04-05 17:24:06] [Verbose] Configuring RNode interface...
[2022-04-05 17:24:06] [Verbose] Wating for radio configuration validation for RNodeInterface[RNode LoRa Interface]...
[2022-04-05 17:24:06] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting frequency is 169.2 MHz
[2022-04-05 17:24:06] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting bandwidth is 125.0 KHz
[2022-04-05 17:24:06] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting TX power is 5 dBm
[2022-04-05 17:24:06] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting spreading factor is 8
[2022-04-05 17:24:06] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting coding rate is 5
[2022-04-05 17:24:06] [Verbose] RNodeInterface[RNode LoRa Interface] On-air bitrate is now 3.12 kbps
[2022-04-05 17:24:06] [Notice] RNodeInterface[RNode LoRa Interface] is configured and powered up
[2022-04-05 17:24:07] [Debug] System interfaces are ready

3 replies

tomdelta Apr 5, 2022
Author

Ok ist transmitts and I can hear it on the RX. Iĺl flash more and try to communicate. What was the problem? The EEPROM must be wiped???

markqvist Apr 5, 2022
Maintainer

You probably don't need to wipe the EEPROM first, just wanted to rule that out for the first one. You can try just rnodeconf --update, and it should work. Let me know if it does! If so, it was just a bug in the radio init check.

tomdelta Apr 5, 2022
Author

ok will try later I´,m in viko. Thanks!!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problem with homemade RNode on 169MHz #37

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 10 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Problem with homemade RNode on 169MHz #37

tomdelta Apr 4, 2022

Replies: 4 comments · 10 replies

4c3e Apr 4, 2022

tomdelta Apr 4, 2022 Author

4c3e Apr 4, 2022

tomdelta Apr 5, 2022 Author

markqvist Apr 5, 2022 Maintainer

tomdelta Apr 5, 2022 Author

markqvist Apr 5, 2022 Maintainer

markqvist Apr 5, 2022 Maintainer

tomdelta Apr 5, 2022 Author

markqvist Apr 5, 2022 Maintainer

tomdelta Apr 5, 2022 Author

tomdelta Apr 5, 2022 Author

markqvist Apr 5, 2022 Maintainer

tomdelta Apr 5, 2022 Author

tomdelta
Apr 4, 2022

Replies: 4 comments 10 replies

4c3e
Apr 4, 2022

tomdelta Apr 4, 2022
Author

tomdelta Apr 5, 2022
Author

markqvist
Apr 5, 2022
Maintainer

tomdelta Apr 5, 2022
Author

markqvist Apr 5, 2022
Maintainer

markqvist
Apr 5, 2022
Maintainer

tomdelta Apr 5, 2022
Author

markqvist Apr 5, 2022
Maintainer

tomdelta
Apr 5, 2022
Author

tomdelta Apr 5, 2022
Author

markqvist Apr 5, 2022
Maintainer

tomdelta Apr 5, 2022
Author