Station G2 Doesn't Transmit or Receive

Support
1

Just got my Station G2 and went to test the default channel (LongFast, all default settings), but it doesn’t appear to receive or transmit any data. When I use the android and web clients they both show that a sent message was not acknowledged. I also double tapped the side “info” button which shows the “sent ad-hoc nodeinfo” on the device screen.

I also have two Nano G2s that work perfectly with the same settings. I am using those two devices to confirm that they can communicate with each other to rule out some other issue. Nano G2s see eachother and work fine. Station G2 does not.

I’ve also tried TX/RX with just USB power, and also with >20W USB-C external power per the docs.

Anyone else run into this issue? I have tried multiple firmware revisions and I’m now running the latest 2.4.3 Alpha (hotfix) release. Still to no avail.

2

First of all, Neil at Unit Engineering (the creator of the Nano G2 and Station G2), was extremely prompt and helpful solving this problem. It turns out this was a firmware issue whereby the NG2s and SG2 were not seeing each other and populating in the nodedb, which apparently can cause comms issues downstream. Long story short, I needed to wipe the NANO G2s (much to my surprise) and boom, the SG2 and NG2s are all talking.

2 Likes
3

They are great. I will make a note to see if this happens when my nano arrives. Thanks for posting. Wipe means “re-flash” or more than that?

4

In the flasher web utility there is an option to wipe/erase before flashing the new firmware. There is a bit more to this story as well.

After a lot more testing and fiddling, I was able to break it again. The issue occurs when moving the default PRIMARY channel to a secondary slot as documented here: Configuration Tips | Meshtastic

I followed the step to set the LoRa channel number to 20 using the web client, and even though the device rebooted indicating it has received the new channel number, it didn’t actually successfully set it. When I used the Python CLI to set the channel number to 20, the setting stuck and all the devices were communicating again.

Long story short, if you’re setting a non-default PRIMARY channel for privacy, you can’t forget to set the LoRa channel number to the default for your region (in my case, 20 for the US). And recommend you do that via the CLI. The web client did not work for me.

3 Likes