Station G2

[kc1awv]

I've become exhausted with Meshtastic, and have been migrating my network of devices here to Reticulum lately. I do have one device "specifically" designed for use with Meshtastic, but I was wondering about the feasibility of using it with RNode. I think it would be a killer device to take portable with me, or use as a standalone "router/repeater" for an area that may need some additional coverage.

The Station G2 device is an ESP32S3 and uses an SX1262 LoRa chip. Using the board definition from the Meshtastic firmware we can get the pins.

What would be the best possible way to test this? Is it as simple as forking RNode, and adding in a new board definition?

[markqvist]

Interesting device. Looking at the specs page, it should be more or less directly compatible with the RNode firmware, but will of course need the pins remapped to whatever values it's using. The BOARD_RNODE_NG_22 target already uses the ESP32-S3 and SX1262 in a similar configuration to the Station G2, so that would probably be a good place to start, just to get the hardware mapping verified and working correctly:

https://github.com/markqvist/RNode_Firmware/blob/master/Boards.h#L341

I'd suggest just forking the firmware, and starting by modifying that existing target until it's working. When it is, create a new board definition. It's probably best to base this off of the Community Edition fork of the firmware, maintained by @jacobeva, since it already has several improvements and updates: https://github.com/liberatedsystems/RNode_Firmware_CE

Only gotcha will be the use of Bluetooth Low Energy to connect host devices, since work on that is still ongoing and not fully supported everywhere. It will work fine over USB/serial as is, though.

[kc1awv]

Thanks Mark! I'm alright using USB for communications until BLE is ready. I typically use my devices that way anyway.

I am running into some compilation errors with the CE firmware (across all targets) so I believe my DE isn't set up the right way, or may be using some old libraries. Probably a question that @jacobeva could help with. There's a lot of undefined reference to errors.

Lots of lines (well over the scrollback limit) similar to this:

~/.arduino15/packages/esp32/tools/esp-xs3/2302/bin/../lib/gcc/xtensa-esp32s3-elf/12.2.0/../../../../xtensa-esp32s3-elf/bin/ld: ~/git/RNode_Firmware_CE/Radio.cpp:262: undefined reference to `digitalWrite'

Used library         Version Path                                                                         
SPI                  3.0.4   ~/.arduino15/packages/esp32/hardware/esp32/3.0.4/libraries/SPI   
EEPROM               3.0.4   ~/.arduino15/packages/esp32/hardware/esp32/3.0.4/libraries/EEPROM
Adafruit GFX Library 1.11.10 ~/Arduino/libraries/Adafruit_GFX_Library                         
Adafruit BusIO       1.16.1  ~/Arduino/libraries/Adafruit_BusIO                               
Wire                 3.0.4   ~/.arduino15/packages/esp32/hardware/esp32/3.0.4/libraries/Wire  
Adafruit SSD1306     2.5.11  ~/Arduino/libraries/Adafruit_SSD1306                             
Crypto               0.4.0   ~/Arduino/libraries/Crypto                                       

Used platform Version Path                                                        
esp32:esp32   3.0.4   ~/.arduino15/packages/esp32/hardware/esp32/3.0.4

Also, not sure if this is a concern yet, but the screen on the Station G2 is an SSH1107. I think the Adafruit SSD1306 driver might support it, but I haven't gotten that far yet 😄

[faragher]

I suggest running `make prep-esp32` in order to target esp32 2.0.15. That solved a lot of my problems. Be aware, it will blow away any arduino-cli versions besides that. So if you're running multiple projects, it may be an issue.

…

On Sun, Sep 22, 2024, 4:42 PM Steve Miller ***@***.***> wrote: Thanks Mark! I'm alright using USB for communications until BLE is ready. I typically use my devices that way anyway. I am running into some compilation errors with the CE firmware (across all targets) so I believe my DE isn't set up the right way, or may be using some old libraries. Probably a question that @jacobeva <https://github.com/jacobeva> could help with. There's a lot of undefined reference to errors. Lots of lines (well over the scrollback limit) similar to this: ~/.arduino15/packages/esp32/tools/esp-xs3/2302/bin/../lib/gcc/xtensa-esp32s3-elf/12.2.0/../../../../xtensa-esp32s3-elf/bin/ld: ~/git/RNode_Firmware_CE/Radio.cpp:262: undefined reference to `digitalWrite' Used library Version Path SPI 3.0.4 ~/.arduino15/packages/esp32/hardware/esp32/3.0.4/libraries/SPI EEPROM 3.0.4 ~/.arduino15/packages/esp32/hardware/esp32/3.0.4/libraries/EEPROM Adafruit GFX Library 1.11.10 ~/Arduino/libraries/Adafruit_GFX_Library Adafruit BusIO 1.16.1 ~/Arduino/libraries/Adafruit_BusIO Wire 3.0.4 ~/.arduino15/packages/esp32/hardware/esp32/3.0.4/libraries/Wire Adafruit SSD1306 2.5.11 ~/Arduino/libraries/Adafruit_SSD1306 Crypto 0.4.0 ~/Arduino/libraries/Crypto Used platform Version Path esp32:esp32 3.0.4 ~/.arduino15/packages/esp32/hardware/esp32/3.0.4 Also, not sure if this is a concern yet, but the screen on the Station G2 is an SSH1107. I *think* the Adafruit SSD1306 driver might support it, but I haven't gotten that far yet 😄 — Reply to this email directly, view it on GitHub <#558 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALIZNIY4S7D7ZH333U6ZTGLZX42S3AVCNFSM6AAAAABOUVMPFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZSGA2DCMI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[kc1awv]

I downgraded the esp32 board manager package thing to 2.0.17 which seems to work. Not that concerned with breaking anything else, I don't usually use arduino for much 😄

Got it compiled, flashed (at least rnodeconf can talk to it) so now I just need to write the EEPROM and figure out how to get the screen to work!

[faragher]

Check out the memory map in the wiki and you can work out writing it pretty easily. The key is to use the RNode itself.

…

On Sun, Sep 22, 2024, 5:29 PM Steve Miller ***@***.***> wrote: I downgraded the esp32 board manager package thing to 2.0.17 which seems to work. Not that concerned with breaking anything else, I don't usually use arduino for much 😄 Got it compiled, flashed (at least rnodeconf can talk to it) so now I just need to write the EEPROM and figure out how to get the screen to work! — Reply to this email directly, view it on GitHub <#558 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALIZNI2QLUMSH7EWBVJLCMLZX5AENAVCNFSM6AAAAABOUVMPFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZSGA2TMMI> . You are receiving this because you commented.Message ID: ***@***.***>

[kc1awv]

Going to put this on hiatus for now. I am able to compile and write EEPROM data (homebrew model FF) but cannot seem to get the display to work at all. EEPROM has (I assume) correct information for the display address and such. rnodeconf proceeds with configuring TNC mode, but retrieving info shows no change (still in normal mode). rnsd craps out with radio state mismatch and bad file descriptor errors

[2024-09-23 13:42:56] [Notice] Opening serial port /dev/ttyACM0...
[2024-09-23 13:42:58] [Notice] Serial port /dev/ttyACM0 is now open
[2024-09-23 13:42:58] [Verbose] Configuring RNode interface...
[2024-09-23 13:42:58] [Verbose] Waiting for radio configuration validation for RNodeInterface[RNode LoRa Interface]...
[2024-09-23 13:42:58] [Verbose] RNodeInterface[RNode LoRa Interface] On-air bitrate is now 1.07 kbps
[2024-09-23 13:42:58] [Error] Radio state mismatch
[2024-09-23 13:42:58] [Error] After configuring RNodeInterface[RNode LoRa Interface], the reported radio parameters did not match your configuration.
[2024-09-23 13:42:58] [Error] Make sure that your hardware actually supports the parameters specified in the configuration
[2024-09-23 13:42:58] [Error] Aborting RNode startup
[2024-09-23 13:42:58] [Error] A serial port error occurred, the contained exception was: [Errno 9] Bad file descriptor
[2024-09-23 13:42:58] [Error] The interface RNodeInterface[RNode LoRa Interface] experienced an unrecoverable error and is now offline.
[2024-09-23 13:42:58] [Error] Reticulum will attempt to reconnect the interface periodically.

Since I am probably the only one with this device and desire 😄 I'll work on it as I have time available. If anyone else wants to take a peek at what I've been doing then check the station_g2 branch in my fork. I'll hold off on a PR until it's working.

I have an email out to the hardware developer, see if there's any schematic or pin definitions that could help me out.

[jacobeva]

Yeah, your pins are potentially wrong. Set rns to the max debug level in the config and post the log when you try and bring it up, that would help.

[kc1awv]

[2024-09-23 15:13:51] [Verbose] Waiting for radio configuration validation for RNodeInterface[RNode LoRa Interface]...
[2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting state is offline
...
[2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting frequency is 908.625 MHz
[2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting state is offline
[2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting bandwidth is 250.0 KHz
[2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting TX power is 14 dBm
[2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting state is offline
[2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting spreading factor is 11
[2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting coding rate is 5
[2024-09-23 15:13:51] [Verbose] RNodeInterface[RNode LoRa Interface] On-air bitrate is now 1.07 kbps
[2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting state is offline
[2024-09-23 15:13:51] [Error] Radio state mismatch
[2024-09-23 15:13:51] [Error] After configuring RNodeInterface[RNode LoRa Interface], the reported radio parameters did not match your configuration.
[2024-09-23 15:13:51] [Error] Make sure that your hardware actually supports the parameters specified in the configuration
[2024-09-23 15:13:51] [Error] Aborting RNode startup

The pins for the SX1262 are set correctly as far as I can tell, using the Meshtastic variant file as a reference. I may have to break this down with some basic SX1262 examples, see if the radio will respond outside of RNode firmware.

[jacobeva]

Looks liek you're right, pins seem correct. Was the firmware hash set correctly when you flashed the device?

…

On 24/09/23 12:31pm, Steve Miller wrote: ``` [2024-09-23 15:13:51] [Verbose] Waiting for radio configuration validation for RNodeInterface[RNode LoRa Interface]... [2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting state is offline ... [2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting frequency is 908.625 MHz [2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting state is offline [2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting bandwidth is 250.0 KHz [2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting TX power is 14 dBm [2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting state is offline [2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting spreading factor is 11 [2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting coding rate is 5 [2024-09-23 15:13:51] [Verbose] RNodeInterface[RNode LoRa Interface] On-air bitrate is now 1.07 kbps [2024-09-23 15:13:51] [Debug] RNodeInterface[RNode LoRa Interface] Radio reporting state is offline [2024-09-23 15:13:51] [Error] Radio state mismatch [2024-09-23 15:13:51] [Error] After configuring RNodeInterface[RNode LoRa Interface], the reported radio parameters did not match your configuration. [2024-09-23 15:13:51] [Error] Make sure that your hardware actually supports the parameters specified in the configuration [2024-09-23 15:13:51] [Error] Aborting RNode startup ``` The pins for the SX1262 are set correctly as far as I can tell, using the Meshtastic variant file as a reference. I may have to break this down with some basic SX1262 examples, see if the radio will respond outside of RNode firmware. -- Reply to this email directly or view it on GitHub: #558 (reply in thread) You are receiving this because you were mentioned. Message ID: ***@***.***>

[kc1awv]

It's a start. Gonna fight with the screen a bit. Is there a serial debug in RNode that could help?

[faragher]

The RNode tends to respond to each command with a status update, but I don't believe anything released handles it for anything other than confirming radio settings.

In any case, the display routines don't return any status, so it wouldn't really help anyway.

My understanding is you're uncertain if the display library supports the display and you're unsure if the pin definition is correct (I mean how sure are any of us until it works?) so can I suggest trying a minimum program using the library and pin you're using now? If it doesn't work, it'll be easier to troubleshoot, and if ti does work, then we know it's an integration issue.

[kc1awv]

I figured as much, so I'm working on figuring out how the display works from just poking at it until something happens. The manufacturer (Neil) confirms that the display is a CH1115, and doesn't use the reset pin. The I2C pins are easily determined by the existing variant file in Meshtastic. What's interesting though is that it looks like Meshtastic is driving the display using a SH110X library. My initial work has been around this, but to no avail. Yet. At least the modem communication seems to work so far, though I forgot my SDR at home (again) so I'll work on the display instead today.

[NHOQA]

So just to confirm the CE firmware leaves you with a functioning G2 RNode? other than the screen? Just diving in from meshtastic and have had good luck with the T beam Rnodes, and really want to get this G2 switched over

[markqvist]

It might be worth noting that the T-Beam Supreme device also uses a SH110X display, so it might be even easier to add full support now when that device is supported in the main firmware repo.