I would like to use some servos based on the object detection coordinates coming from jetson nano through USB.
Somehow coordinates are being updated later and later as the time passes.
I have added the simple test code.( image url)
Hi Felix.
Thaks for your repply, and sorry for my late resonse.
I had some issues logging in again after I created my account.
Your links got the example code to at least build.
But once uploaded to the board I never get past "Connect Error" in the setup.
I have two hats, and two M5StickCPlus, and same issue on both.
So guess I still have some troubleshuting to do.
Re: Faces stock firmware tft repl source?
I only just purchased an M5Stack Faces kit this year, with the sole desire to build a firmware based on this feature (As it is shown or mentioned in all videos relating to the faces kit)). Is the engineer that wrote this no longer contactable?
It seems you have just moved onto other products and abandoned something that had promise. It feels like you have swept the whole faces kit under the rug.
Also why is the speaker and amp so bad? all firmware produces horrible noise
@staberas
This code was very helpful. Thanks!
I tried adding temperature as well:
tmp = i2c.readfrom_mem(MPU6886_ADDRESS, MPU6886_TEMP_OUT_H, 2)
temp = (tmp[0]<<8|tmp[1])
temp = (float(temp) / 326.8) + 25.0;
I'm getting temps of 40.5C (105F). Am I doing something wrong or is this temperature the CPU temp?
Thanks,
/Chris
@chriszang and another update.
So I am happily working on my CAN receiver sketch and just noticed that I forgot to press the button that grounds INT-output of the mc2515 but the upload still worked. Gave it another try (w/o pressing the button) and it's still working - weird.
Then I swapped this COMMU module for my 2nd COMMU Module and here the upload doesn't work.
My explanation is that the grounding of the mcp2515 INT-output basically created a short circuit in the transistor that controls this pin and eventually burned it out. Not a big problem for me as
a) I am not using interrupts in my sketch
b) I have a 2nd COMMU unit
I just wanted to warn you guys that grounding the INT output has unintended consequences.
After a lot of testing I came to the following conclusion:
The problem was that I waited too long before enabling GPIO pin 12 in my code. This pin is used to keep the device powered by the battery.
I'm just speculating here, but it seems like there is a time frame in which you need to enable this pin, otherwise the device will not successfully boot.
Thanks!
Nick
I didn't get anywhere setting GPIO1 however I downloaded UIFlow v3.0 from https://docs.m5stack.com/en/download and uploaded the latest version v1.10.1 to my Core Ink and now I have working Restart and Power On / Off :-)
Hello @schedule-display
Have you tried the RTC example (w/o modifications)?
In your code, why did you add the two gpio_xxx lines? I think they are the reason M5Paper cannot shutdown.
Also this thread might be helpful.
Thanks
Felix
@macsbug Thanks for the tip I will give it a shot. The short demo video looks promising as I see a gauge that looks great. I have similar results with the Sprite library but fall short on compositing sprites past pushRotated.
Thanks
Hello @dominik
the nice thing about ESP32 and its variants (like the C3) is that different functions (like SPI) can use almost any GPIOs.
With the Arduino environment you can define the GPIOs to be used for SPI like this:
#define SCK GPIO_NUM_6
#define MISO GPIO_NUM_4
#define MOSI GPIO_NUM_7
#define CS GPIO_NUM_5
SPI.begin(SCK, MISO, MOSI, -1);
Thanks
Felix
@twostick
FYI; light sleep current pulled out of the battery depend on the battery voltage:
<2.7V device wont wake up anymore
2.7V 4.4mA
3.0V 3.9mA
3.7V 3.1mA
4.2V 2.7mA
This dependacy is caused by the DC-DC conversion that converts the Lipo voltage first to 5Vdc. (SY7088 chip).
The 5Vdc gets also down converted to 3v3 (SY8089 chip) .
According to the datasheet, the ESP itself should only use 0.8mA in light sleep. So 2mA gets waisted.
What a pitty.
dd.07-04-22:
The above is not completely true. I'm using the M5GFX lib and when I execute the function display.sleep(); before going to deep sleep (esp_deep_sleep_start();) the sleep current drops to a 1.25mA. Still considerable...
Hi,
It's actually significantly simpler to type an e after the umlauted letters, and utilize a twofold s (ss) for ß. That is how Germans treat they need to.
My device is now running for about 6 days with one battery charge.
But I'm using deep sleep mode now.
If I use disableEPDPower() before getting into light sleep mode, I need to re-init the display after wake up. So the advantage of light sleep is lost and display need to be fully updated.
I choose this device with e-paper display to build a low power application, but at the end it was not the best decision to use M5paper.
