Topics created by dclaar

@dclaar I have no problem with the Stamp-PICO running on the 3.3V power from the programmer. And the StampS3 running on USB 5V actually outputs out 3.3V at the RGB output... So, YES!

Hello @dclaar I don't think this has been documented yet - but I could be wrong. But consider this. I have multiple M5Stack (Gray, Basic, Fire) and even with the same brightness setting the actual brightness differs visibly. Thanks Felix

I was successful in recording something like a wave form with the following code: from machine import I2S, Pin import array mic = I2S(I2S.NUM0, ws=Pin(0), sdin=Pin(34), mode=I2S.MASTER_PDM, dataformat=I2S.B16, channelformat=I2S.ONLY_RIGHT, samplerate=16000, dmacount=16, dmalen=256) b2 = array.array("h", 4096 * [0]) mic.readinto(b2) However, there seems to be a systematic offset around ~+1000. Not sure what is going on here. Could it be related to PDM encoding and the I2S clock? Also, I experience values that are larger than the 12bit precision documented somewere def eval(): mic.readinto(b2) print(min(b2), max(b2), sum(b2)/len(b2)) for i in range(1000): eval() ... 48 1963 1017.062 811 1237 1027.727 927 1122 1021.952 849 1286 1023.281 763 1719 1029.73 102 1966 1015.185 -903 2878 1012.832 -788 2683 984.9133 -1524 2761 982.3828 -815 3075 986.0596 -864 3044 980.6567 -713 2904 993.0678 -669 2615 1014.595 -138 2182 1022.794 -73 1954 1018.482 ...

Hmm, OK, get_wifi() works on 1.5.4, so maybe I just guessed wrong back then.

Thanks, once I got the other computer to see the device (can't flash a device that doesn't show up in device manager), I was able to reflash it. Then I took it back to my laptop, and it still wasn't seeing it. So I switched USB cables, and it did. Then I switched back to the original USB cable, and it worked with that cable again. (Note that I had hooked up a M5StickC via the original USB cable, and it is working fine with that cable now, so the cable isn't bad). Gotta love Microsoft Windows sometimes.

@keesjan With micropython, port 22 works fine, and as expected: CDS_PIN = 33 TX = 19 RX = 22 As an aside, the idea that the labeling of the pins is "oriental logic" shows an unawareness of the history of rs232 and is a bit insulting. The question of what to label the pins depends on whether the manufacturer thinks of the device as DTE or DCE: StackExchange has a good explanation of the history. In particular: 'some manufacturers try to "help" by effectively labelling their DTE equipment as if it was a piece of DCE. They mark their data input pin as Tx so that user just connects "Tx" from the external device (which, if it's DTE, will be the data output from there) to the pin marked "Tx" on their equipment (which they know is an input). Thereby allowing them to say "just connect Tx on your device to Tx on our equipment". They think they are trying to help, but such labelling often just adds to the confusion.'

Great project

In the REPL of any program you need to hit ctrl + c to kill any running processes in order to get to a command prompt

Beta version (v2.0.0 for Mac) looks nice. Thanks @m5stack.

Rshell works pretty well, although the newer M5 releases are a lot harder to get into the correct mode, particularly on the atom. Uiflow is micropython: I have often written something in uiflow and then switched to the micropython side to see what the python is for a given uiflow thing. And then I can cut and paste into repl. For long-term debugging (fails once a day or week), I leave the device connected to putty. I have considered adding code that would catch Exception () in the main loop, do a stack trace, and save it into a file so that I don't need it to always be connected, but have never implemented it.

Rather, I chose to switch to polling, which worked much better, so it seems.

@ajb2k3 Adding to this: I'm using the pymakr extension to VS Code. It handles selective code upload (only changed ones). Note that pymakr does not handle binary file transfer eg. jpg.

@dclaar isPressed() reflects current state of the button (is it pressed?), and returns a Boolean. wasPressed() is an event trigger you use to execute code when the button is pressed. Sample code below (generated from uiflow) to illustrate. from m5stack import * from m5ui import * from uiflow import * lcd.setRotation(1) setScreenColor(0x111111) isExit = None def buttonB_wasPressed(): global isExit isExit = True pass btnB.wasPressed(buttonB_wasPressed) setScreenColor(0x000000) axp.setLcdBrightness(40) isExit = False while isExit == False: lcd.print((btnA.isPressed()), 3, 0, 0xffffff)

The serial console access is known as REPL. If you didn't know about REPL then it is no wonder that you are surprised.

Given that I can now see the console, I determined that it throws OSError if the http GET fails. Which is a weird error to throw, but OK. So I put that in my except: clause, and it's humming away!

I will finally note that lcd.print works fine with lcd.orient(lcd.LANDSCAPE) and lcd.orient(lcd.LANDSCAPE_FLIP)