I have had the first one happen to me before but not the second one your best bet from my experience is to go to your esp32s ip address and then go to config parameters and set the board to the correct type if it isn’t already then just restart it or if restarting it doesn’t work unplug it and wait a few seconds and then plug it back in but that’s all i know
1 Like
Thank you for the advice! However, in my case, I’m using a direct USB serial connection (connected to my Debian server via /dev/ttyUSB0) rather than accessing it over Wi-Fi.
Because I can’t get any serial output from screen or cat even after clearing all port conflicts, I’m stuck on the “LoRa Gateway” screen with no logs at all. Do you know if this behavior typically points to a flashing/firmware issue, or a potential baud rate mismatch on the Heltec V3?
unfortunately no im not experienced with that
1 Like
Please share the output of ls -l /dev/ttyUSB0 and id
Jan | PE0SAT
1 Like
Here are the outputs:
Plaintext
yukio@nec:~$ ls -l /dev/ttyUSB0
crw-rw----+ 1 root dialout 188, 0 Sep 7 07:42 /dev/ttyUSB0
yukio@nec:~$ id
uid=1000(yukio) gid=1000(yukio) groups=1000(yukio),4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),101(netdev),102(scanner),110(bluetooth),113(lpadmin)
Thanks, so you are able to read write because you are a member of the dialout group.
You can try by installing ckermit and if you are able to connect by changing serial speed settings in ${HOME}/.kermrc
Example:
cat .kermrc
SET LINE /dev/ttyUSB0
SET SPEED 9600
SET CARRIER-WATCH OFF
SET FLOW-CONTROL NONE
I am also not sure if there is a getty active on the Heltec
Jan | PE0SAT
2 Likes
Thank you for the guidance! I updated ~/.kermrc to 115200 baud and connected via ckermit. Here is the boot log after pressing the RST button:
Plaintext
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x29 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce2820,len:0x10cc
load:0x403c8700,len:0xc2c
load:0x403cb700,len:0x30b0
entry 0x403c88b8
[ESP32] 起動完了
The board seems to boot, but it is currently stuck on the “LoRa Gateway” screen. What would be the next step to troubleshoot this?
@jp7dvx Just a short note about your project in general. I see, you put a lot of effort into your LoRa solution. When participating in 2 LoRa satellite missions, I have learnd a lot about the restrictions and pitfalls associated with these boards, which can really hurt. I have run the backup groundstations for the PY4 and the HYPE satellites with redundant links to several systems, based on TTGO boards and raspberries with LoRa heads.I am not sure if you are aware of these limitations - just want to avoid, you are disappointed after putting in a lot of effort.
1 Like
Thank you for the kind advice and sharing your experience! Actually, dealing with barriers like closed Telegram channels or recommendation requirements is part of why I decided to set up my own independent station to observe things directly. I really appreciate you highlighting these pitfalls.
To be more detailled, there are speed limitations when pushing data immediately via usb or wifi.this is not a problem, when just receiving telemetry in 30s intervals. For higher datarates usually used for bulk-data transfers, up to approx. 8 packets a second it is essential to store data in a Fifo memory locally and transfer via usb/wifi, when the satellite pauses the transmission. During emptying buffer, a second board should be ready to receive, in case satellite starts transmission again. In unbuffeted mode, the board misses most of the transmissions. For fsk the siituation is even more restricted, because we have to deal with bit-oriented transmission, in a byte buffered environment. The sx1262 isnt really designed for fsk - but I think fsk is not the focus of your project. For pushing data directly to satnogs from the esp32 i use a function similar to push-telmetry.py via http without Linux inbetween.
2 Likes
Thank you for the detailed technical explanation! That makes a lot of course, especially regarding the buffer handling and packet rates.
For now, I’ll focus on getting the basic telemetry reception stable and keeping these practical limits in mind for my setup.
1 Like
maybe its good time to try this stale project
2 Likes
Haha, looks like an interesting time capsule!
Regarding the satnogs-tiny link, my little V3 here seems to be saying, “I appreciate the throwback, but I’m still stuck on the ‘LoRa Gateway’ screen! I wanna grow up and start working too!”
For now, I’ll stick to getting the basics running, but maybe someday I can run something like that too.
why not just reset or reflash with another firmware and start again?
1 Like
That sounds like a solid plan. If I do reflash it, what firmware would you recommend trying out next besides the default setup?
I have tried it. It will most likely not work because it needs a mqtt server from satnogs but when i tried to run it on an esp32 it didn’t find the mqtt server meaning its very unlikely it will work.
2 Likes
just send mail to admin
and flash the board
1 Like
I had no idea about that email address! Every official page just points to Telegram or an invitation requirement. Did you actually get in through that email method yourself? Thanks for the great tip!
actually i never try this. but nothing to loose. why not try.
1 Like
Haha, classic! “Nothing to lose” is a great motto. I might just give it a shot for science, or keep building my own independent path. Cheers for the laugh and the tip!