Closed amotivv closed 3 months ago
I dont know excalty about mdb Support for this device but when the .so is not there then normally its not supported by the device
Thank you. Built the same application for a M3065-V (aarch64) with 10.12.240 firmware and got the same:
2024-07-08T15:32:49.395-04:00 axis-b8a44f078bac [ INFO ] consume_analytics_metadata[3208]: /usr/local/packages/consume_analytics_metadata/consume_analytics_metadata: error while loading shared libraries: libmdb.so.0: cannot open shared object file: No such file or directory
Is this an issue with the acap-native-sdk, or have I just picked the wrong devices to test with?
Did you read about the API Firmware Version where Mdb is added to Axis OS? 10.12.240 is to low. https://axiscommunications.github.io/acap-documentation/docs/api/native-sdk-api.html#metadata-broker-api
Did you read about the API Firmware Version where Mdb is added to Axis OS? 10.12.240 is to low. https://axiscommunications.github.io/acap-documentation/docs/api/native-sdk-api.html#metadata-broker-api
Yes, for the camera. Was just trying to reproduce the issue. I bet the mdb is not available in the radar. Thanks for the help.
Works fine on my camera, you could just Login into radar device via ssh and confirm by search for the .so via "find" command. If you dont find it its not supported.
Good tip. Looks it's not there in the radar:
root@axis-b8a44f809e92:/# find . -type f | grep libmdb
root@axis-b8a44f809e92:/#
Hi @amotivv , thanks for your detailed report.
The SoC is ARTPEC-7 which is marked as supported for the Metadata Broker API. I think this Beta API has so far been focusing on information on detected objects on a video stream from an image sensor and not a radar and could be a reason that it's not included on the product.
But it's a good question and I will look in to it.
If I remember correctly the broker is so far present only on products where one of the standard topics are produced. These currently coincide with the presence of the metadata producer labeled Analytics Scene Description; see /camera/index.html#/system/metadataConfig
on your device. Unfortunately, I don't have a D2110-VE at hand to verify, so if it seems I may be wrong then I probably am.
Hi again @amotivv , the pure radar product D2110 doesn't have support for Metadata Broker API today because the current available topics
com.axis.analytics_scene_description.v0.beta
com.axis.consolidated_track.v1.beta
are only related to detections from a video stream.
The Scene Metadata page on axis.com has a list of products that are supported for the current topics. There are two Radar-Video Fusion Cameras on the list.
Describe the bug
Running example metadata-broker/consume-analytics-scene-description application on AXIS D2110-VE Security Radar produces the following error in the app logs on the device:
To reproduce
Build Docker image using example Dockerfile in current repo:
docker build --tag consume_analytics_metadata:1.0 --build-arg ARCH=armv7hf .
Copy application:
docker cp $(docker create consume_analytics_metadata:1.0):/opt/app ./build
Install
consume_analytics_metadata_1_0_0_armv7hf.eap
application to D2110-VE. Start application. View App logs:Screenshots
Environment
Additional context
Building and installing the
hello-world
sample app works without issue when installed on the D2110-VE.