Hi,
I want to write a code to connect an AtomS3 Lite to a Wi-Fi access point. The following code works fine until I add the WLAN STA connect block.
However, once I added the block, I got an error as follows.
Traceback (most recent call last):
File "<stdin>", line 40, in <module>
File "<stdin>", line 18, in setup
OSError: Wifi Internal Error
It would be much appreciated if you could show me a way to specify a pair of SSID and PASSWORD.
Thanks,
Shigeru
Hi,
I found that the following code works as I expected. I want to share for your reference until official examples are provided.
Thanks,
Shigeru
Hi,
I found that the print block in the Text category works fine without configuring pins.
I overthought about this issue.
Thanks,
Shigeru
I confirmed that this issue is still reproducible with the latest version (i.e., v.1.12.6). Am I the only person who can reproduce this issue?
Hi,
I want to use the USB CDC port on AtomS3 (Lite) for serial debugging. It seems that there are no dedicated blocks for USB CDC in Alpha-26. Is it possible to use USB CDC with the UART blocks (e.g., Init UART 0 with or UART 0 setup) with a particular configuration?
Thank you very much in advance,
Shigeru
Hi,
I'm trying to implement an HTTP client on AtomS3 Lite with UIFlow 2.0. I have implemented on ATOM LITE with UIFlow 1.0 as follows:
My questions are as follows:
HTTP close, right after an HTTP request block or after handling a response?Get Data in UIFlow 1.0, get content or get text?It would be much appreciated if you give me advice regarding this topic.
Thank you very much in advance,
Shigeru
Update: I found the shadowed URL by removing a variable connected to the http_request block. At first, I directly specified the API key as a part of the URL, then replaced it with the variable.
Update: I confirmed that I can reproduce this issue with the latest version (i.e., v1.12.3). I also tried specifying the SSID and PASSWORD using a Network block but got no luck. Can anybody else reproduce this issue?
Hi,
I want to publish examples for UIFlow using HTTP requests. I did as follows.
API_KEYI found that the variable for URL is replaced as I expected. However, the original URL containing the API key seems to be available in the http_request block.
How can I remove the key in UIFlow? Alternative ideas are removing it with a text editor or creating a utility tool, but I want to know if there is a way in UIFlow.
Thanks,
Shigeru
Hi,
The following code works fine with the UIFlow_Lite firmware versions between v1.7.5 and v1.9.6.
https://gist.github.com/kotobuki/aab0a8b0e65e501c8a354198bdc4d969
However, the HTTP request fails with versions after v1.9.7, including v.12.2. If I change the URL to http://api.m5stack.com/v1, it also works fine with those versions. It seems that firmware versions after v1.9.7 only accept the URL for GET HTTP requests.
I'm sorry if this is a false alarm.
Best,
Shigeru
Hi,
I want to deploy my custom firmware. I have submitted firmware in the past, but it seems that the format has been changed (it was .zip but now .bin only).
https://github.com/kotobuki/M5Stack-HID-Input-Framework-for-xR-firmware
As a trial, I exported a .bin file by Sketch > Export compiled binary then specified the .bin file but got no luck.
Where is the document explaining how to prepare the firmware for use in the User Custom tab of M5Burner v3.0?
@m5stack said in The range of values from an ANGLE between directly connected to PORT B and connected to PORT A via PbHUB is different:
ESP32 and mega328 has different ADC resolution
Thank you very much for your reply.
Yes, the ADC module on mega328 has a 10-bit resolution, whereas ESP32 has a 12-bit resolution. If this issue is just a resolution issue, the result should be 0 - 1023 instead of 15 - 745 or 0 - 715. If nobody can reproduce this issue, the PbHUB may be broken...
Hi,
I'm testing my PbHUB with my M5GO and ANGLE, and I have a question.
When I connect the ANGLE to port B of the M5GO, the range of values from the ANGLE is between 0 and 4095.
However, when I connect the ANGLE to port A via the PbHUB of the M5GO, the range of values from the ANGLE is between 15 and 745 (when connected to between ch0 and ch3) or 0 and 715 (when connected to between ch4 and ch5).
I confirmed with both Arduino and UIFlow. Is this normal, or my PbHUB seems to be broken?
from m5stack import *
from m5ui import *
from uiflow import *
import time
import unit
setScreenColor(0x222222)
pbhub0 = unit.get(unit.PBHUB, unit.PORTA)
label0 = M5TextBox(10, 10, "Text", lcd.FONT_DejaVu18, 0xFFFFFF, rotate=0)
while True:
label0.setText(str((str('ANGLE: ') + str((pbhub0.analogRead(0))))))
wait_ms(100)
wait_ms(2)
Best,
Shigeru
Hi,
I just downloaded M5Burner v2 from https://m5stack.com/pages/download, unzipped, and tried to launch. However, I got an error message like 'The application "electron-m5burner-v2-eletron" can't be opened'. I also tried unzipping with The Unarchiver and could open the app, then got error messages as follows (an excerpt).
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @rpath/Electron Framework.framework/Electron Framework
Referenced from: /Applications/electron-m5burner-v2-eletron.app/Contents/MacOS/electron-m5burner-v2-eletron
Reason: no suitable image found. Did find:
/Applications/electron-m5burner-v2-eletron.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework: file too short
/Applications/electron-m5burner-v2-eletron.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework: stat() failed with errno=1
M5Burner v1.0.1 has been working fine in the same environment. Could you please let me know if you know anything about this issue.
BTW, I found an article that seems to be related to this issue. https://medium.com/cacher-app/getting-your-electron-app-working-on-macos-catalina-10-15-63e53f397da2
Thanks,
Shigeru
Hi,
I want to utilize the HAT pin in UIFlow to add a digital sensor. Are there any plans to support the HAT pin in UIFlow? Though I can code in the Arduino environment, I want to go with UIFlow if possible. Because UIFlow is easy to deploy and let non-experts tinker.
Thanks.