Volume only works in "playMusic" function.

@martinsky No problem - glad to hear it is now working..... the other two menus on my github page are also very good.... little more involved to setup, but worth the effort. The SD-Updater menu supports M5Stack library versions 0.1.6 and 0.1.7 (see notes under installation). The MultiApp Firmware Menu uses the ESP Flash Downloader to upload the code in place of the Arduino "IDE".

@jp No problem JP !!

@m5mpy microcode is very low level, I like how these MCU bring back old memories and old hacks like I used to do on Amiga. And how in general they force into better programming habits. So what I'm trying to do is general purpose signal camera. At the moment, a sound camera will do. From what I was told on eevblog, I need one FFT per microphone to calculate inter-mic delay. So far Arduino FFT switched to uint32 (faster on esp32 than uin8 I'm told) I'm getting 512 bins at 12 ms, which is't very zippy as I'll need 4 cameras at least. Not that big a deal because I don't need 60fps refresh but ... well, that would be nice :D As for the frequency, at the moment I'm interested in detecting the origin of low frequency sound as they're notoriously difficult to locate by ear. Eventually I'd like to expand into an EMF camera.

Concise code for sure. I need all the speed I can get so it'll be Arduino for now. I'm surprised you wouldn't see any flicker on the display since you print every frame, also surprised that there is no clearScreen preceding the print. I'm thinking the python print has a background.

answer: use the TFT_eSPI library, you can pass transparency color in the sprite draw functions

@petero Hi PeterO, Sorry I didn't get a chance to look into that further - was busy with github stuff etc. Glad you found the problem. These things can be very particular !! Also glad the link was useful....... the SAM menu is fantastic.... with the included I2C scanner and other features. There are also two other excellent menu systems... You can easily add your own apps to the "M5Stack-SD-Updater" menu (more are being added over time) and the other "M5Stack_MultiApp _Firmware" has a number of useful tools included.... including I2C scanner, voltmeter, etc..... https://github.com/PartsandCircuits Enjoy !

@drwino I've not seen any designs available in STEP format. DXF and DWG formats are available via the link below, along with some 3D design examples. Note Zazardev's Proto design - he managed to alter the original Proto STL at least a little as he filled in the holes in the frame. https://github.com/PartsandCircuits/M5Stack-3DPrintFiles

I am been able to read the ADC on pin 35. This corresponds to ADC1_CH7 BUT I cannot get ADC on pin 36 to work. I think this is ADC1-CH0. Anybody has any sample code ? Thanks.

@jimit Many thanks for the reply, it is sad as it was the example I wished to include in my M5Stack YouTube review. Glad you liked it anyway! For those who are interested the video is here: M5Stack Review

Hello, I found some pictures on the web, the pads are not populated and yes it is a short!! I removed the short with some fluxed solderwick and hope nothing is damaged by the short. Hopefully the M5Stack-team respondes on how that could happen in production and releases the schematics and placement of parts. Something else that is really odd, on the Keypad there is no bypass capacitor for the Atmel Microcontroller! Best Regards, Seppel

You can use hardwareSerial to assign (ex)Serial1 and Serial2 to different pin's then use Serial1 and Serial2 to communicate with the GSM and GPS HardwareSerial Serial1; Serial1.begin(unsigned long baud, uint32_t config=SERIAL_8N1, int8_t rxPin=x, int8_t txPin=y, bool invert=false); Just an ideea...

@calin the bottom stack should be the watch 😂

Here is the solution. https://github.com/Bodmer/TFT_eSPI/tree/master/examples/Sprite/Sprite_scroll Thanks to @Calin

@calin freeze with no serial message. What is the IDLE task and how do I control all this?

Bodmer wrote a nice article on this https://github.com/Bodmer/TFT_eSPI/issues/121#issuecomment-380245040 When un-commenting Display.h/#define SPI_FREQUENCY 40000000, fillscreen nearly doubles. 80M doesn't work on some M5.