Forum Discussion
Sridhar_Kothalanka
Microsoft
MicrosoftVision AI dev kit not working when specifying "ModelZipUrl"
Initial Setup: I got a new vision ai dev kit, set it up, updated the firmware and everything works fine. I see it detects a person and puts a box around. I also get events in IoT Hub.
Probl...
Nikunja - I found one problem. There was no more space available on the Camera for some reason. I reflashed it using the fastboot procedure listed in toubleshooting. The default model OOBE deployment now works. However, still running into the same issue with model not running when specifying ModelZipUrl as mentioned in this thread
Sridhar_Kothalanka Hello, I am having the same problem. Have you found a solution yet ?
I tested with two different cameras and the problem is the same anybody found the solution?
- Any update on this ? I am also having the same issue with the zip model failing to identify
Model downloads but does not box
Confirmation of 204 received for {"RtspVideoUrl": "rtsp://10.60.1.176:8900/live"}.
Confirmation of 204 received for {"Bitrate": "1.5Mbps"}.
Confirmation of 204 received for {"RtspDataUrl": null}.
Confirmation of 204 received for {"FrameRate": 30}.
Confirmation of 204 received for {"VideoOverlayConfig": "inference"}.
Confirmation of 204 received for {"Codec": "AVC/H.264"}.
Confirmation of 204 received for {"VideoAnalyticsEnabled": false}.
Confirmation of 204 received for {"HdmiDisplayActive": true}.
Confirmation of 204 received for {"ShowVideoOverlay": true}.
Confirmation of 204 received for {"ShowVideoPreview": true}.
Confirmation of 204 received for {"SupportedBitrates": "512Kbps | 768Kbps | 1Mbps | 1.5Mbps | 2Mbps | 3Mbps | 4Mbps | 6Mbps | 8Mbps | 10Mbps | 20Mbps"}.
Confirmation of 204 received for {"SupportedConfigOverlayStyles": "text | inference"}.
Confirmation of 204 received for {"SupportedEncodingTypes": "HEVC/H.265 | AVC/H.264"}.
Confirmation of 204 received for {"SupportedFrameRates": "24 | 30"}.
Confirmation of 204 received for {"SupportedResolutions": "4K | 1080P | 720P | 480P"}.
Confirmation of 204 received for {"ModelZipUrl": "https://irisprodaetraining.blob.core.windows.net/m-a996f7441eb0467691a5aa1397249a77/0d6d1908258a48988ace3e9df8eed03f.VAIDK.zip?sv=2019-12-12&se=2021-10-06T05%3A08%3A30Z&sr=b&sp=r&sig=a5MkF%2FIKfVjk0%2B9FJ1ILr4puhR5S13mH4JH%2BAwLi3S8%3D"}.
Confirmation of 204 received for {"TimeBetweenMessagesInSeconds": 12}.
Confirmation of 204 received for {"ObjectsOfInterest": "[\"All\"]"}.
send: b'\x89\x80\n\xe8\xadi'
send: b'\x89\x80.\xba\xae\xb4'
send: b'\x89\x80,\xa6\x9b\xbf'
send: b'\x89\x80\x06\x0c\x93/'- Sridhar_Kothalanka - It doesn't feel like this is 'Solved' yet...it can be reproduced easily and is happening with more and more developers using the AI Vision IoT Camera SDK and hardware...it should not be marked as solved IMO...
The Custom Vision Portal Export function should not be able to convert to and export models for the intended use with the Camera using documented unsupported NN operators that are missing on the Qualcomm (QC) NN chip. It's possible newer QC chips processing the exact same NN models might work...but it should be known what that chipset is now and which cameras are supporting the newer/more complex Custom Vision Portal exported models...
One thing to try which I haven't had the time to do yet would be to export from the Custom Vision Portal as ONNX and then attempt to use the Snapdragon SDK to generate a model DLC file from the ONNX that will works on the camera using IoT Device SDK. Older versions of the ONNX Tools may produce results that are compatible depending on how complex your models have become...
Cheers,
eem- Is this issue cleared?
since the 2 years ago this thread has been opened and not yet cleared.
