Re: M5Stack UnitV2 apriltag: how fast can read? FPS?

Not sure about apriltags. But video recording to sdcard with ffmpeg runs at the following speeds:

framerates:

• 30fps @ 640x480
• 20fps @ 1280x720
• 9fps @ 1920x1080

video only:
ffmpeg -f v4l2 -i /dev/video0 -c:v mpeg4 -s 640x480 output4.mp4

with audio like:
ffmpeg -f v4l2 -i /dev/video0 -f alsa -i default -c:v mpeg4 -s 640x480 -c:a aac -ar 44100 -ac 2 -b:a 192k output-x.mp4

h264 and vp8 should be present, but don't work.

Note: the cameras of Unitv2 and UnitV2-M12 are quite different and the latter (M12) has MUCH higher quality! It's not only the lens, also the sensor.

See more at our repo

@juergschwarz MQTT "keepalive" ist auf 5 Minuten (300) eingestellt. Da Du kein MQTT Publish machst, sondern per Get Request sendest, schläft Dein MQTT vermutlich ein => Probieren, ob es mit längerem Keepalive länger dauert, bis nichts mehr kommt. Ggf alle 5 Minuten ein neues MQTT Start machen.
Die Subscribes haben keine Andockpunkte, weil das Events sind.

The built-in firmware in UnitV2 (M5UnitV2RootfsRecoveryPackage-09072021) has some useful libraries missing (e.g. dnn support for OpenCV). Without complete instructions on how to cross-compile for this target it is not possible to make modifications.
Request: open-source your linux build environment (buildroot, drivers, tools, sample configuration)

Re: M5Stack UnitV2 apriltag: how fast can read? FPS?

Not sure about apriltags. But video recording to sdcard with ffmpeg runs at the following speeds:

framerates:

• 30fps @ 640x480
• 20fps @ 1280x720
• 9fps @ 1920x1080

video only:
ffmpeg -f v4l2 -i /dev/video0 -c:v mpeg4 -s 640x480 output4.mp4

with audio like:
ffmpeg -f v4l2 -i /dev/video0 -f alsa -i default -c:v mpeg4 -s 640x480 -c:a aac -ar 44100 -ac 2 -b:a 192k output-x.mp4

h264 and vp8 should be present, but don't work.

Note: the cameras of Unitv2 and UnitV2-M12 are quite different and the latter (M12) has MUCH higher quality! It's not only the lens, also the sensor.

See more at our repo

Hello. The present documentation for UnitV2 is basically useless if you want to develop you own applications. Is anyone from M5Stack still supporting UnitV2 or is it a dead product?

@ghz2000 Hello. We are starting a new project using the Unitv2. While support from M5 people is effectively zero, we thing it is still an interesting product. I was able to compile a compatible buildroot version, opencv-4 with DNN and ncnn framework. Currently training some networks to be ported to the camera. You might want to check
https://github.com/CodeforKarlsruhe/kikaefer/blob/main/docs/unitv2.md
We'll post news as they come in.

@juergschwarz MQTT "keepalive" ist auf 5 Minuten (300) eingestellt. Da Du kein MQTT Publish machst, sondern per Get Request sendest, schläft Dein MQTT vermutlich ein => Probieren, ob es mit längerem Keepalive länger dauert, bis nichts mehr kommt. Ggf alle 5 Minuten ein neues MQTT Start machen.
Die Subscribes haben keine Andockpunkte, weil das Events sind.

The built-in firmware in UnitV2 (M5UnitV2RootfsRecoveryPackage-09072021) has some useful libraries missing (e.g. dnn support for OpenCV). Without complete instructions on how to cross-compile for this target it is not possible to make modifications.
Request: open-source your linux build environment (buildroot, drivers, tools, sample configuration)

@felmue Tried both. 3.3V has a bit higher current. Strange, if there's just an LDO (guessing - no schematics!).
Also removed IR and RGB LEDs. Tried with Arduino and Espressif IDF deep-sleep example. No success. NodeMCU with Wroom32 is kind of OK (1.6mA), by the way. But mechanically too large ...

I'm testing deep sleep current for an Atom project. Atom starts, current is about 50mA. In deep sleep current drops to less than 1mA, which is what I expect. Atom awakes after 30 seconds to do its regular job, then goes to deep sleep again. However, this time (and all subsequent times) deep sleep current is about 11mA. When I press the reset button immediately after power on, the first deep sleep is also 11mA. I can also see a difference in the active current in the order of 11mA. There are no units connected. Whatever I do, disable Serial, I2C, Display, isolate GPIOs or not, there is no effect.
Unfortunately M5Stack doesn't provide schematics for the Atom, just a block diagram which misses out a lot of details.
Any ideas? Should I remove the RGB Led or the IR transmitter. My best guess is it is the FTDI chip coming out of sleep mode due to some fluctuation on the TX/RX lines. But without schematics I cannot do much. What I found on FTDI is something like 8-15mA, depending on the chip type. The only one in SSOP20 package is FT231X. Any help welcome. Below 1mA is good, but 11mA deep sleep current is a nightmare. There are many questions on the deep sleep power issue and I'd be very glad if M5 could do something to improve this ...

Using M5Burn 1.7.2 (same for 1.7.1) on Linux Fedora 33 with atom-lite or atom-matrix.
Ich can erase and flash the bootloader. The WiFi dialog on flashing works. But I cannot set config options to USB mode which is needed to use the desktop IDE.

First, there is a strange message about "setting APN required"

then javascript error: "loadall is not defined".

After that, M5burner shows the message "writing data, do not close" but no activity any more.

How can I set the device to usb mode? Can I do this via esptool.py alone, without the m5burner GUI?