Replies: 9 comments 21 replies
-
|
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 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. |
Beta Was this translation helpful? Give feedback.
-
|
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: 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 😄 |
Beta Was this translation helpful? Give feedback.
-
|
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>
|
Beta Was this translation helpful? Give feedback.
-
|
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! |
Beta Was this translation helpful? Give feedback.
-
|
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
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 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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
|
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: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
very interested in your progress, I have two StationG2s on meshtastic right now and would love to see them work on reticulum |
Beta Was this translation helpful? Give feedback.
-
|
It's been deferred in lieu of other paying projects and work for the time being. I can probably revisit it again in the near future. |
Beta Was this translation helpful? Give feedback.
-
|
Just for reference, and anyone else willing to take a look, this is what I've been able to find as far as pins for a board def that I've been trying to squeeze into the CE firmware: https://github.com/meshtastic/firmware/pull/3282/files My current travel equipment isn't set up for compiling the firmware right now. But, it's a place to start from. |
Beta Was this translation helpful? Give feedback.
-
|
fyi, this is as far as I have gotten (I may have been able to set up a little dev environment remotely 😁 ): |
Beta Was this translation helpful? Give feedback.
-
|
Oh, and I still haven't gotten the screen to work either. I'll need to see how the TBeam Supreme works with RNode firmware. |
Beta Was this translation helpful? Give feedback.
-
|
Um... disregard that last comment. ohshitwut
|
Beta Was this translation helpful? Give feedback.
-
|
NICE! |
Beta Was this translation helpful? Give feedback.
-
|
I had missed this before responding originally but it looks like you certainly have gotten further than me here. Seems to be related to setting the radio settings. Those were the same errors I was getting when I was working on the G1 last week. The G2 I keep getting err 9 serial issues.
|
Beta Was this translation helpful? Give feedback.
-
|
Ok, so this is what I'm working with, trying to get the right magic incantation for getting the radio to work: #elif BOARD_MODEL == BOARD_STATION_G2
#define IS_ESP32S3 true
#define MODEM SX1262
#define DIO2_AS_RF_SWITCH true
#define HAS_BUSY true
#define HAS_TCXO true
#define OCP_TUNED 0x38
#define HAS_DISPLAY true
#define HAS_CONSOLE true
#define HAS_BLUETOOTH false
#define HAS_BLE true
#define HAS_PMU false
#define HAS_NP false
#define HAS_SD false
#define HAS_EEPROM true
#define HAS_INPUT true
#define HAS_SLEEP false
#define PMU_IRQ 40
#define I2C_SCL 6
#define I2C_SDA 5
const int pin_btn_usr1 = 38;
const int pin_cs = 11;
const int pin_reset = 21;
const int pin_sclk = 12;
const int pin_mosi = 13;
const int pin_miso = 14;
const int pin_tcxo_enable = -1;
const int pin_dio = 48;
const int pin_busy = 47;
const int SD_MISO = 37;
const int SD_MOSI = 35;
const int SD_CLK = 36;
const int SD_CS = 47;
const int IMU_CS = 34;
#if HAS_NP == false
#if defined(EXTERNAL_LEDS)
const int pin_led_rx = 9;
const int pin_led_tx = 8;
#else
const int pin_led_rx = 9;
const int pin_led_tx = 8;
#endif
#endif
There are a few changes also made to Display.h and Utilities.h. Made some changes locally in my venv for rnodeconf to display things pretty like, so don't expect just the board def to be all that's needed. |
Beta Was this translation helpful? Give feedback.
-
|
Hi. Came across this thread and exited to see your efforts. Is this working with rnsd as an rnode? Do you have a fork up somewhere? |
Beta Was this translation helpful? Give feedback.
-
|
I am so glad to see some folks working on getting compatibility for Neil's Station G2 devices. I am just stumbling on this thread after trying on my own to get some of my older Station G1 devices working as Rnodes. I am new from meshtastic and am glad to have found what I would consider a much more exciting project with significantly more potential. As far as the Station G1, that is more closely related to the standard T-beams. For both the G2 and G1, I tried my best to replicate the pin definitions as provided in meshtastic but the furthest I have gotten is a successful install and EEPROM provision through rnodeconf. Any attempt by rnsd to interact over serial results in errors with the serial connection. All of this has been with the CE firmware version which allegedly has improvements over mark's reference implementation but his version also seems to still be under active development and many commits ahead so I wanted to make sure I had the right ideas for how this project is structured. I also tried @kc1awv 's G2 branch from November as well as the snippit above with similar errors. I wasn't ever able to get the display either. I will keep prodding at this best I can and look forward to hearing more from folks in this community! |
Beta Was this translation helpful? Give feedback.
-
|
The branch of my fork is very very out of date. 1.73 CE vs 1.81 mainline. If someone has the time, maybe reaching out to B&Q/Neil is an option, make sure there's no other gotchas we're missing. From what I gather, there's nothing sitting between the ESP and the SX1262, things are pinned up the way it should be. The PA is only enabled when a 15VDC power supply is attached. LNA is in line and there's an RF switch on DIO2. TCXO is fed from DIO3. Screen is as mentioned by Mark to be the same/similar to the T-Beam Supreme. As a matter of fact, the whole Station G2 is very similar to the T-Beam Supreme. No external LEDs, but for the time being, pins 8 and 9 can be used, which are exposed on the GPIO socket. Simple enough to add an external board for that. GPS can be added through the Grove socket. If someone finds a I2C SD card reader, I wonder if that could be added on the other connector (I think the FW only has support for SPI SD?). I've had a look through sx126x.cpp and the only change that I can see that needed to be made was for the TCXO. Everything else should be the same. Once the right settings are discovered or we receive some info from B&Q/Neil, it should be a trivial matter to get a PR started. We'd need to get Mark's input on what product/board/model codes would be adequate without stepping on any future developments he may have. As far as errno 9, that might be something local? Is that a Mac? Double-check the port name. |
Beta Was this translation helpful? Give feedback.
-
|
The discussion about that topic is split. If someone is searching for the latest information about the Station G2 support, then you should follow liberatedsystems/RNode_Firmware_CE#79 |
Beta Was this translation helpful? Give feedback.
-
I attempted to test this today but I am a little stuck. How can I build the firmware? Normally I follow the documentation and have built other firmware for DIY devices such as the e22 but I am not able to build this using I am sure its me being very dumb as I do not find the code easy to follow at all (coming from platformio background). I would appreciate any help on this to get a successful build. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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?
Beta Was this translation helpful? Give feedback.
All reactions