uPyEasy BETA-1 is available!

Moderators: Voyager, BertB, grovkillen, Stuntteam, LisaM

Post Reply
Message
Author
alpat59
New user
Posts: 3
Joined: 22 Dec 2016, 21:11

Re: uPyEasy BETA-1 is available!

#11 Post by alpat59 » 29 Jan 2018, 21:01

tested plugin test ... same output. I neededd to reset ESP32.

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: uPyEasy BETA-1 is available!

#12 Post by LisaM » 29 Jan 2018, 23:29

BertB wrote: 29 Jan 2018, 19:48
LisaM wrote: 29 Jan 2018, 00:40
And the test plugin? It's a test plugin designed to always return 17 as value for testing purposes.
17 shows up in the devices list and it all seems to be ok, but then:

Code: Select all

stack: 2000 out of 15360
GC: total: 96000, used: 72224, free: 23776
 No. of 1-blocks: 1200, 2-blocks: 153, max blk sz: 901, max free sz: 617
570570373.535 <HTTPRequest object at 3ffbb2d0> <StreamWriter <socket>> "GET /devices"
2018-01-29 19:46:40 [debug] uPyEasy-uPyEasy: Pages: Authorize User!?
2018-01-29 19:46:40 [debug] uPyEasy-uPyEasy: Pages: Entering Devices Page
2018-01-29 19:46:40 [debug] uPyEasy-uPyEasy: Utils: uPyEasy Name
2018-01-29 19:46:41 [debug] uPyEasy-uPyEasy: Plugins: Read device test
2018-01-29 19:46:41 [debug] uPyEasy-uPyEasy: Plugin: test read
stack: 2000 out of 15360
GC: total: 96000, used: 82224, free: 13776
 No. of 1-blocks: 1293, 2-blocks: 167, max blk sz: 901, max free sz: 371
570570421.218 <HTTPRequest object at 3ffbfe40> <StreamWriter <socket>> "GET /static/upyeasy.css"
stack: 2000 out of 15360
GC: total: 96000, used: 83840, free: 12160
 No. of 1-blocks: 1339, 2-blocks: 174, max blk sz: 901, max free sz: 371
570570421.218 <HTTPRequest object at 3ffc5370> <StreamWriter <socket>> "GET /static/upyeasy.js"
static/upyeasy.css
static/upyeasy.js
2018-01-29 19:47:03 [debug] uPyEasy-uPyEasy: Plugin: test process
Traceback (most recent call last):
  File "main.py", line 2, in <module>
  File "upyeasy/__init__.py", line 56, in main
  File "picoweb/__init__.py", line 275, in run
  File "uasyncio/core.py", line 138, in run_forever
  File "uasyncio/core.py", line 97, in run_forever
  File "upyeasy/plugins/test.py", line 107, in asyncprocess
  File "upyeasy/utils.py", line 277, in plugin_senddata
NameError: name 'stype' is not defined
MicroPython v1.9.3-255-g979c688-dirty on 2018-01-27; ESP32 module with ESP32
Type "help()" for more information.
>>>
Both bugs fixed and new firmware uploaded. Please log these bugs in github, in this thread i might lose track of them...
The stack trace is helping me a lot to find these bugs!

psy0rz
Normal user
Posts: 232
Joined: 02 Feb 2017, 12:12

Re: uPyEasy BETA-1 is available!

#13 Post by psy0rz » 29 Jan 2018, 23:36

Great work lisa!
Please support ESPEasy development via Patreon or buy us a coffee.

pppp33
Normal user
Posts: 71
Joined: 25 Oct 2015, 17:53

Re: uPyEasy BETA-1 is available!

#14 Post by pppp33 » 30 Jan 2018, 01:36

Hi Lisa,
Thank you for the great work.....
I am trying to set up upyeasy on the TTGO board (ESP32+display+battery):

I get this message at startup:
rst:0x10 (RTCWDT_RTC_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:4364
load:0x40078000,len:0
load:0x40078000,len:10992
entry 0x4007a6c4
I (440) cpu_start: Pro cpu up.
I (440) cpu_start: Single core mode
I (441) heap_init: Initializing. RAM available for dynamic allocation:
I (444) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (450) heap_init: At 3FFDCDD0 len 00003230 (12 KiB): DRAM
I (456) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (463) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (469) heap_init: At 4009005C len 0000FFA4 (63 KiB): IRAM
I (475) cpu_start: Pro cpu start user code
I (46) cpu_start: Starting scheduler on PRO CPU.
OSError: [Errno 2] ENOENT
MicroPython v1.9.3-255-g979c688-dirty on 2018-01-28; ESP32 module with ESP32
Type "help()" for more information.



And I get this error messages when I try to setup wifi:
>>> import network
>>> sta_if = network.WLAN(network.STA_IF); sta_if.active(True)
I (42943) wifi: wifi firmware version: 111e74d
I (42943) wifi: config NVS flash: enabled
I (42943) wifi: config nano formating: disabled
I (42943) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (42953) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (42973) wifi: Init dynamic tx buffer num: 32
I (42973) wifi: Init data frame dynamic rx buffer num: 64
I (42973) wifi: Init management frame dynamic rx buffer num: 64
I (42983) wifi: wifi driver task: 3ffe15dc, prio:23, stack:4096
I (42983) wifi: Init static rx buffer num: 10
I (42993) wifi: Init dynamic rx buffer num: 0
I (42993) wifi: Init rx ampdu len mblock:7
I (43003) wifi: Init lldesc rx ampdu entry mblock:4
I (43003) wifi: wifi power manager task: 0x3ffe850c prio: 21 stack: 2560
W (43013) phy_init: failed to load RF calibration data (0x1102), falling back to full calibration

Brownout detector was triggered

Guru Meditation Error of type IllegalInstruction occurred on core 0. Exception was unhandled.
Guru Meditation Error of type IllegalInstruction occurred on core 0. Exception was unhandled.
Guru Meditation Error of type IllegalInstruction occurred on core 0. Exception was unhandled.

Any Idea ?
It looks like it can't set MAC Address.....

Regards
Paolo
Attachments
download.jpg
download.jpg (5.87 KiB) Viewed 33093 times

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: uPyEasy BETA-1 is available!

#15 Post by LisaM » 30 Jan 2018, 10:13

pppp33 wrote: 30 Jan 2018, 01:36 (43003) wifi: wifi power manager task: 0x3ffe850c prio: 21 stack: 2560
W (43013) phy_init: failed to load RF calibration data (0x1102), falling back to full calibration

Brownout detector was triggered
There's your cause: you have a power problem. It may be caused by poor quality usb cable, bad solder joints or low power from USB connector. If you can monitor 5v and 3.3v voltage on esp32 during startup then you may have some clue. Use a better usb power source?

(If you see no power dip during startup of the esp32, you might try this:solder a 100nF ceramic or 220uF/16V capacitor on the 3,3V output on the esp32 to suppress the power peak.)

pppp33
Normal user
Posts: 71
Joined: 25 Oct 2015, 17:53

Re: uPyEasy BETA-1 is available!

#16 Post by pppp33 » 30 Jan 2018, 13:10

thx a lot, Lisa.
I'll check asap.
Regards
Paolo

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: uPyEasy BETA-1 is available!

#17 Post by BertB » 30 Jan 2018, 20:15

LisaM wrote: 29 Jan 2018, 23:29
Both bugs fixed and new firmware uploaded. Please log these bugs in github, in this thread i might lose track of them...
The stack trace is helping me a lot to find these bugs!
Houston, we have a go :D
Deeply impressed too, I am.

Works fine now, but it is very very very slooooooow. Lots of debug data on the serial output.
I guess this comes with the territory of being a beta tester?

BertB
Normal user
Posts: 1049
Joined: 25 Apr 2015, 14:39

Re: uPyEasy BETA-1 is available!

#18 Post by BertB » 30 Jan 2018, 22:29

Knipsel.PNG
Knipsel.PNG (26.48 KiB) Viewed 33004 times

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: uPyEasy BETA-1 is available!

#19 Post by TD-er » 31 Jan 2018, 00:03

Ohh you guys already have a delete option on the devices...
I wanted that on the V2.0/Mega for so long... ;)

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: uPyEasy BETA-1 is available!

#20 Post by LisaM » 31 Jan 2018, 11:38

BertB wrote: 30 Jan 2018, 22:29Knipsel.PNG
Looking good! Please let me know if it runs stable and not out of memory (which might indicate a memory leak).
uPyEasy is not optimized yet, functionality (to test) and stability (to run) first.

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: uPyEasy BETA-1 is available!

#21 Post by LisaM » 31 Jan 2018, 12:38

TD-er wrote: 31 Jan 2018, 00:03 Ohh you guys already have a delete option on the devices...
I wanted that on the V2.0/Mega for so long... ;)
In uPyEasy, all data is just a record in a table in the database. All processes are reading from the database, so deleting device data from the database means the device's plugin no longer read by this device... Unloading the plugin the moment no device is using it anymore, is not implemented yet.

jbishop129
New user
Posts: 5
Joined: 04 Jan 2018, 17:05

Re: uPyEasy BETA-1 is available!

#22 Post by jbishop129 » 31 Jan 2018, 16:17

Hi @LisaM
Thanks for your hard work on this, I'm excited to give it a try today!
I notice the Wiki links seem to be dead, referenced from your gitHub page:
"Introduction and wiki: https://www.letscontrolit.com/wiki/inde ... troduction"
Have these pages moved?

LisaM
Normal user
Posts: 513
Joined: 11 Apr 2017, 18:29

Re: uPyEasy BETA-1 is available!

#23 Post by LisaM » 31 Jan 2018, 18:44

jbishop129 wrote: 31 Jan 2018, 16:17 Hi @LisaM
Thanks for your hard work on this, I'm excited to give it a try today!
I notice the Wiki links seem to be dead, referenced from your gitHub page:
"Introduction and wiki: https://www.letscontrolit.com/wiki/inde ... troduction"
Have these pages moved?
Nope, not ready yet...

Post Reply

Who is online

Users browsing this forum: No registered users and 14 guests