Heltec ESP32 Single Channel Packet Forwarder

Gateways [obsolete] SCPF
1

Hi All,

I built a single channel gateway a while ago using a Heltec ESP32 LoRa board and the “ESP-sc-gway.h” library. Everything worked just fine.

At some point, I used the Heltec ESP32 for another purpose. When I wanted to reuse it as SC gateway, I wasn’t able to get it to work again, despite uploading the exact same code that used to work previously. It wouldn’t even connect to the WiFi. After erasing the flash memory (esptool.py erase_flash), at least a connection to WiFi could be established but the gateway kept crashing (“Starting” blinking on OLED display). In the serial monitor, the following lines keep repeating:

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:9720
ho 0 tail 12 room 4
load:0x40080400,len:6364
entry 0x400806b8
SPIFFS loaded success
Assert=Do Asserts
debug=1
readConfig:: Starting
SSID=lsm-59086
CH=0
SF  =9
FCNT=0
DEBUG=0
CAD=0
HOP=0
NODE=0
BOOTS=61
RESETS=0
WIFIS=61
VIEWS=0
REFR=0
REENTS=0
NTPETIM=5803
NTPERR=17
NTPS=78
MAC: 80:e6:3f:8e:ba:1d, len=17
0:1. WiFi connect to: lsm-59086
WLAN reconnected
Host esp32-8e351d WiFi Connected to lsm-59086
Gateway ID: B4E62DFFFF8E351D, Listening at SF9 on 868.10 Mhz.
setupTime:: Time not set (yet)
Time: Thursday 22:29:14
Gateway configuration saved
WWW Server started on port 80

abort() was called at PC 0x400d6dfd on core 1

Backtrace: 0x4008cc2c:0x3ffb1eb0 0x4008ce5d:0x3ffb1ed0 0x400d6dfd:0x3ffb1ef0 0x400d6e57:0x3ffb1f10 0x400d8405:0x3ffb1f30 0x400e249b:0x3ffb1fb0 0x40089341:0x3ffb1fd0

Rebooting...
ets Jun  8 2016 00:22:57

The sketch I’m using is too long to be posted here but it’s the standard “ESP-sc-gway” sketch that comes with the ESP-sc-gway.h library.

Any help with this issue is greatly appreciated!

2

Best recommendation would be to return that board to node usage and get an actual gateway.

Even when operating as intended single-channel devices cause many problems in the gateway role, so their usage is strongly discouraged here.

And there’s not really anything in your trace that could be used to debug - by appearances the software is hitting a “should not happen” situation and giving up. If you really want to pursue this, perhaps raise it with the author of the software.

1 Like
3

I have adjusted the topic title to reflect that your setup is most definitely not a gateway. As mentioned by @cslorabox these devices are disruptive for the network. Please get yourself a TTIG or something alike that is a genuine gateway.

1 Like