Home › Forums › The libraries hosted on the site › EByte LoRa e220 UART devices LLCC68 › E220 remote Switch project crash
Tagged: ADDL Addressing, E220, WOR
- This topic has 5 replies, 3 voices, and was last updated 10 months, 4 weeks ago by
William.
-
AuthorPosts
-
-
10 June 2024 at 12:46 #30775
E220 Remote Switch Sender Crash Video
Countdown timer triggered!
Battery Switch is ON
ESP32 waking from Deep SleepHi, I’m going to send message!
TimeStamp: Sat 06/08/24 08:43:19E (119451) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (119451) task_wdt: – async_tcp (CPU 0/1)
E (119451) task_wdt: Tasks currently running:
E (119451) task_wdt: CPU 0: IDLE0
E (119451) task_wdt: CPU 1: async_tcp
E (119451) task_wdt: Aborting.
abort() was called at PC 0x400e66b5 on core 0
Backtrace: 0x400838a9:0x3ffbec4c |<-CORRUPTEDELF file SHA256: de2a1108edda429d
Rebooting…
�]��W �,��
�$�$uC�
MAC: B0:A7:32:82:0A:B4
Connecting to R2D2
Web server running. Waiting for the ESP32 IP…
Server IP: 10.0.0.27
Port: 80
MAC: B0:A7:32:82:0A:B4
Wi-Fi Channel: 10
Connection result: 3Gist code of E220 Remote Switch Sender and Receiver
Hardware:
2 — ESP32 Devkit V1
2 — Ebyte E220-900T30D Transceivers; used the xReef E220 Library.
1 — KY002S MOSFET, Bi-Stable Switch
1 — INA226 Battery MonitorRequesting help debugging; code is complex, have traced out all of the wiring with DMM continuity tests.
RX, TX, and AUX have 4.7K ohm; external, pull-up resistors.Restated computer
Deleted Arduino builds from c:\Users\William\Appdata\Temp
Updated AsyncTCP
RecompiledOn Serial Monitor; ESP32 reset receiver, then reset sender. Sender sends WOR message; receiver shows callback message (Interrupt arrives), sender shows timeout. Opening web browser request (tried Brave and Chrome browsers) to produce on demand web URL request; sender crashes. Repeated process; no change.
Gist of code for Sender and receiver
Web page with videofeed link to turn-on camera
Camera is currently off line. Project is an effort to conserve battery power to allow camera viewing as needed.
William
-
This topic was modified 11 months ago by
Renzo Mischianti.
-
This topic was modified 11 months ago by
Renzo Mischianti. Reason: Add files
Attachments:
You must be logged in to view attached files. -
This topic was modified 11 months ago by
-
17 June 2024 at 08:43 #30820
Hi William,
I think you must check the power supply and the memory usage, you must debug all the variables used and the size.
Bye Renzo -
18 June 2024 at 03:07 #30824
Made multiple changes; crash issue has been resolved.
Have question; is the Receiver destination address the same as the configuration address, or is it the destination addresses of the sender module of the configuration address?
Issue persists where Receiver does not wake up. Have set AUX_PIN as interrupt and enabled ext 0 wakeup and level to 0.
Powering both Sender and Receiver by 5V, 5 Amp switching power supply.
When using WOR does TX of E220 to to TXD2 of the ESP32?
Kind Regards,
William-
This reply was modified 11 months ago by
William.
Attachments:
You must be logged in to view attached files.-
20 June 2024 at 22:42 #30842
Hi,
In fixed transmission you must use as destination address the address set in the config of the device that just receive the message.
In wor the tx and rx is setted as usual respectly to the rx tx of the counter part.
Bye Renzo
-
This reply was modified 11 months ago by
-
18 June 2024 at 23:38 #30830
So I am not all that great at this stuff, but I feel like the server.on( call or maybe processor may be the issues there. is String linkAddress = “xxx.xxx.xxx.xxx:80”; supposed to be a bunch of x’s instead of an IP address? If not then that certainly would confuse the crap out of a system trying to start a service on that port 🙂
Personally, I am not all that good at debugging using the tools. So what I would do is rip out the part that is causing the watchdog trigger (async_tcp) makes me think its the webserver stuff. So go replicate a Webserver by itself make all that work without the triggers and such. Because I think you will end up finding what is causing. Anyway its that part of the code that’s the problem, so you need to debug it and sort out why its taking so long to move on. OR TURN OFF THE WATCHDOG HEHEHE… (This is not a good idea I don’t think)
-
24 June 2024 at 01:33 #30865
String linkAddress = “xxx.xxx.xxx.xxx:80” is left over and for future addition; once I have WOR working. LinkAddress was for port forwarding and a placeholder on an HTML page. When coding I work just on the local area network; no need for port forwarding.
I have resolved the crashing that I linked to earlier. Issue is being unable to wake ESP32 from deep Sleep.
@Renzo Mischianti
“In fixed transmission you must use as destination address the address set in the config of the device that just receive the message.”
Ebyte RF config software, e220-900T30D Factory default frequency, 868 — user manual
Receiver: ADDL = 3 Sender: ADDL = 2
Channel = 66 Channel = 66
Mode = Fixed Mode = Fixed
WOR Period = 2000ms WOR Period = 2000ms
Power = 30 dbm Power = 30 dbm
Rec. #define Destination_ADDL 2 Sender #define DESTINATION_ADDL 3William
-
This reply was modified 10 months, 3 weeks ago by
William.
-
This reply was modified 10 months, 3 weeks ago by
-
-
AuthorPosts
- You must be logged in to reply to this topic.