Question/Issue:
Since App-Lab and Uno-Q update, Object Detection apps are now using standard object-detection model when they were using imported Edge-Impulse .eim files
Project ID:
904591
Context/Use case:
Model trained, exported and run on Uno-Q to detect drones.
Summary:
Custom model was running successfully before App-Lab and Uno-Q updates.
Steps to Reproduce:
- Run Drone Detection App. This is the Detect Objects on Camera demo, pointing to a custom model .eim
Expected Results:
Prior to tools and dev-kit update, the app would run and it would “detect” drones with label and bounding box.
Actual Results:
After Tools and dev-kit update all Object-Detection apps that were previously using custom models are now using the same generic object detection model. Custom objects are not detected, but cup, keyboard, monitor etc… are all detected as per default object-detection model.
The variable set in the app.yaml file to direct the App to use a custom model (.eim file) does not seem to work anymore.
name: DJE-Drone-Detection
description: This example showcases object detection within a live feed from a USB camera.
ports: []
bricks:
- arduino:video_object_detection: {
- variables: {*
-
EI_OBJ_DETECTION_MODEL: /home/arduino/.arduino-bricks/ei-models/uno-q-drone-linux-aarch64-v1.eim* -
}*
*} *
- arduino:web_ui: {}
icon: 
Reproducibility:
- [ ] Always. All object detection apps are now falling back on a common model where previously they were using individual models generated in Edge-Impulse…
Environment:
-
Platform: Uno-Q
O/S Win11, accessing Uno-Q with VS-Code and App-Lab v0.5.0
