I’ve received my AE3 now and successfully run most of the example files - including the Yolo8 person object example. Congrats on your successful Kickstarter campaign. I want to run a series of progressive experiments: 1) with the complete 80 objects yolo model and then 2)filter to a short list of 4 or 5 objects (ie person, car, bus, truck, motorcycle) and then 3) custom trained object.
Can the AE3 run the 3 experiments? For the complete 80 object model does it have enough memory?
if it can run can you describe how to acquire the yolo model and load it into the AE3 as I’m not a software engineer!
Also - how do we activate the free licenses that come with the Kickstarter purchase (Edge & Roboflow)?
Hi Richard,
I can send out the Roboflow license today. Just have to create an email. I already have the codes.
…
-
Yes, you can do this. Note that YOLOV8 operates on a transposed object list output. When you do 80 classes… the algorithm will be very slow on the post-processing part. We can speed this up, though, and will have this optimized before Q3 of the year.
-
Yes, that’s easy in Python using the language. Remember that the heap onboard is 4MB. This is quite large compared to any MCU you’ve ever used.
-
Yes, via Roboflow.
Let me send out emails with the Roboflow license and a link to the video where I showed off this ability.
Awesome - appreciate the info and look forward to the licenses…
I’ve trained now 3 models using Roboflow but have not been able to deploy any to OpenMV. - see image error message.
Hmm, something might have changed on the platform. I’ve forwarded this to their engineers.
I’m also stuck when I attempt to Edit RomFS - OpenMV IDE when selecting either core - the message is “Waiting for the device” and the Busy visual at the top of the Edit ROMFS screen show busy…
You need to unplug and reply the device when that happens. However, what IDE version are you using? We’ve fixed the issues related to that happening with the latest IDE and bootloader that units were programmed with.
I’ve tried unplugging - both physically and using the IDE disconnect to no avail - also with the camera running dumping frames and also when stopped. the camera blue light blinks when i try the Read ROMFS and the Busy visual bars shows a rolling image…
I’m running IDE4.8.7
Hi, uh… it seems like you are trying to run scripts while the IDE is trying to update the firmware. I’m somewhat confused. There should be a period of time when the system is running the bootloader which is when the green light is running. It will blink for about 2 seconds. During this time the IDE needs to connect to it. When using the latest IDE, when DFU-Util is active the IDE will be able to connect to the camera and update the firmware.
The waiting for device dialog you see means that DFU Util is waiting for the bootloader to appear with that 2 second window.
Does Tools→Install latest development firmware work? Or the same issue? The only thing I can think of is that on windows any USB device in the warning state will cause the handoff to fail. The IDE has code to warn you about that when you click connect. Otherwise, you could potentially have too many devices on your USB bus leading to a slow enumeration.
I get the same issue when I try to install latest dev firmware - it goes to busy visual with message, waiting for device.
I do see the camera green light flash for about 1 sec, then blinks blue after I select core when attempting to Edit ROMFS on OpenMV Cam
Hi Richard, Roboflow fixed the download issue. Please try again. As for updating ROMFS.
There’s only two things that can be wrong, either the driver is now working… which I think is not the case as we’ve had folks using this for a while now, or that enumeration is taking too long due to USB bus issues.
Can you remove all extra usb devices from your pc and plug the camera directly in bypassing any hub? Also, please send me a screen shot of your windows device manager.
If you happen to have Python installed, do pip install mpremote and try mpremote bootloader.This jumps to bootloader in forced mode, and stays in there, Vs reset to bootloader which exits after a timeout. When you do, see if the camera enumerates. I suspect it’s not enumerating in bootloader mode at all, for some reason. Maybe something is blocking dfu-device access.
I’m building a version of the IDE now with a new option under tools, which will allow you to enter the bootloader with no timeout. You can then invoke the edit romfs option at your leisure, same for updating the firmware. If this updated IDE doesn’t work for you then there’s a driver issue.
It will be ready by tomorrow.
I’ll look forward to the new version of the IDE. i did connect it directly into one USB slot with no USB hub… same problem. see attached win device mgr screenshot.
Can you fully expand the com and serial ports section and usb device section and show eveything there. IDE should be done now. Posting in a bit.
quick question regarding the AE3 camera. Does the lens simply pull off or twist for focus and cleaning - assuming it does but perhaps this is only feature of the other cameras like the N6 - I don’t want to break camera by pulling too hard and I don’t see any set screws…
The lens just screws off. It has a certain amount of clamping force that keeps it in place.
Regarding the IDE, Mac build failed because Apple’s servers were down. Re-running that. This part takes about 3-4 hours.
I’ve successfully created and downloaded a Roboflow model - so the download issues seems resolved! Thanks! Still yet to test loading into my AE3 … tbd.
Still working on getting the IDE out. Apologies for the delay. I am traveling, and it is hard to keep track of everything. I fixed another issue with the IDE building on Mac. It’s going again… Will have a dev release soon.
