Azure Percept: Video Analyzer live pipeline not working

Question

Azure Percept: Video Analyzer live pipeline not working

Tina Jain 36

I am trying to setup Azure Video Analyzer (CVR) on Percept device. I have successfully deployed the ava module (running status) on the edge device based on the docker image mcr.microsoft.com/media/video-analyzer:1.

I am now trying to setup Live pipeline in Video Analyzer. I created the topology and pipeline, activated the pipeline too but the video throws the following error:

Attached is the live topology json - 176409-ava-topology.txt.

I also tried setting up the pipeline through API calls mentioned here. The actual topology and pipeline never shows in the Azure Portal (Can seem them in Visual Studio Code extension). The video does show up with at times (Not live mode, but with time interval bar in the player), but then stops streaming after some time.

António Sérgio Azevedo 7,671 Reputation points Microsoft Employee Moderator

2022-02-22T16:50:11.19+00:00

Hello @Tina Jain ,
It is my understanding that you have opened an Azure Support Request with this issue, can you please confirm? In the meantime can I kindly request you to follow the steps in Troubleshoot the Azure Percept DK device and share with us what you found out?

Thanks!
Tina Jain 36 Reputation points

2022-02-23T15:02:58.137+00:00

I looked at the module logs (Via ssh) on the device but it shows up the same error that comes in IOT Hub. The RTSP url rtsp://azureeyemodule:8554/h264raw with the default credentials did work for me once before, so not sure why it is throwing an error now. I also refreshed the AVA provisioning token of the module.

Here is the output from the ava module:

"data": {
"code": "404",
"target": "rtsp://azureeyemodule:8554/h264raw",
"protocol": "rtsp"
},

"data": {
"error": {
"code": "RtspIngestionDisconnected",
"target": "The RTSP ingestion was disconnected"
}
Quinn Tran 191 Reputation points

2022-02-23T22:24:17.347+00:00

Hello @Tina Jain ,

Thank you for sharing the output above. Let me check in with our product team. Also just want to confirm if you currently follow any Azure Percept instruction to enable Video Analyzer, which result in the original error message (Error related to streaming). If so, can you share the instructions and the specific steps where this issue happened? It would be very helpful to pinpoint the issue if we know the source. Thanks!
Tina Jain 36 Reputation points

2022-02-24T15:24:25.303+00:00
I have been following Percept Reference article here. The steps mentioned in the article worked the first time for me, but after that subsequent deployments have started creating the 404 issues.

Things tried so far:

I tried deleting the ava module explicitly from IOT Hub, and redeploying the module with a fresh provisioning token.

Deleted the video analyzer resource, re-created a new one and thus a new AVA token as well, followed by another deployment of ava module

Deleting the video in Video Analyzer explicitly, so that a new one can be created when the live pipeline is activated

None of the above steps have worked so far for me.
Quinn Tran 191 Reputation points

2022-02-24T18:48:57.95+00:00

Thanks @Tina Jain !

Can you share both the eye module log and the ava module log after activating the pipeline?
Here is the step;

1) ssh to your device
2) make the command - docker logs azureeyemodule -f and docker logs avaedge -f
3) copy and paste here the content of the log

Thanks!
Quinn Tran 191 Reputation points

2022-03-01T18:40:20.81+00:00
@Tina Jain ,
Did you get a chance to get the azureeyemodule and the aveaedge logs?

Also, the problem might be with the rtsp source. Can you also try the following:

Install the VLC player https://www.videolan.org/vlc/index.html

Copy and paste this url (rtsp://azureeyemodule:8554/h264raw) in the browser

VLC player will pop up to view and check the rtsp h264 stream? (and yes, you need to Install VLC player first)
https://www.videolan.org/vlc/index.html

Let me know if that works for you.
Tina Jain 36 Reputation points

2022-03-02T15:33:37.417+00:00

@Quinn Tran ,

We are currently facing problem with the Percept device itself, due to which we are not able to connect to it at all. As soon as it starts working again we will post the logs here.

Thanks for you support on this!
Quinn Tran 191 Reputation points

2022-03-02T19:23:00.33+00:00

@Tina Jain - Thank you very much for the update! I'll be looking out for your log.

Also feel free to open a separate Q&A thread if you are still facing issues with connecting your devkit. Meanwhile, you can check out this troubleshooting guide: https://learn.microsoft.com/en-us/azure/azure-percept/how-to-troubleshoot-setup
Quinn Tran 191 Reputation points

2022-03-07T18:59:14.537+00:00

Hello @Tina Jain ,
How is your devkit connection issue coming along? Please feel free to post the issue here. I would love to help you to move pass that.

Thank!
Tina Jain 36 Reputation points

2022-03-08T14:23:30.103+00:00

We are still facing issue with the device. It is powered on, but it shows up as Disconnected in the Azure Percept Studio. The device is not available via SSH too.
Quinn Tran 191 Reputation points

2022-03-08T19:08:48.277+00:00
Hello @Tina Jain ,
To further troubleshoot this, could you:

Power cycle the devkit and go through the OOBE again setup Experience. Please create a new device, don't use the old one:
https://learn.microsoft.com/en-us/azure/azure-percept/quickstart-percept-dk-set-up#launch-the-azure-percept-dk-setup-experience

Once done, SSH to the device to get the following log:
sudo iotedge logs edgeAgent
sudo iotedge logs edgeHub

Share the logs here.

Thanks!
Gautam Kasturi 1 Reputation point

2022-03-09T04:43:09.067+00:00

Hi,

I work with tinajain. I tried to get into the OOBE again but when I connect to the devices wifi (apd-xxxx) it connects but does not bring up the OOBE. Even manually connecting to 10.1.1.1 or your.new.device or the original local IP does not work. So I can't get past step1 above to get to step2.
'
Appreciate your help in advance.
Quinn Tran 191 Reputation points

2022-03-09T19:26:15.68+00:00

Hello @Gautam Kasturi ,

When said "manually connecting to 10.1.1.1", did you click to the provided http://10.1.1.1 link in the document? If so, could you try open a browser and type in the "http://10.1.1.1" instead? (In this order: 1) power cycle the devkit 2) Connect your host computer to the dev kit’s Wi-Fi access point (apd-xxxx) and 3) open a browser and type in the "http://10.1.1.1")

If that still doesn't work, I want to re-confirm with you: Have you upgrade your devkit to the latest SW Feb release?

1) If not, please a) upgrade your devkit through DIP switch method (provide that you can't SSH in your device at the moment) and b) go through OOBE again

DIP switch method: https://learn.microsoft.com/en-us/azure/azure-percept/how-to-update-via-usb#using-the-dip-switch-method

2) If you already did update the latest SW Feb release, then try to a) downgrade to the January release using DIP switch method and b) go through OOBE again to get connect and c) Upgrade to the latest SW Feb release.

You can get the Jan/Feb SW release here: https://learn.microsoft.com/en-us/azure/azure-percept/software-releases-usb-cable-updates
DIP switch method: https://learn.microsoft.com/en-us/azure/azure-percept/how-to-update-via-usb#using-the-dip-switch-method

My goal is to help you relauch OOBE and get the device connected again. Hence, suggesting the above steps.

Hope this helps!
Gautam Kasturi 1 Reputation point

2022-03-09T20:01:34.28+00:00

Thanks for your response and perseverance QuinnTran.
I did exactly those steps to get to http://10.1.1.1.
I did not update to the Feb release but I had previously updated to the Jan 2022 release using the DIP switch method and it had worked.
Presently the SSH is not working either (even over USB).
Quinn Tran 191 Reputation points

2022-03-09T20:38:59.047+00:00

Hi @Gautam Kasturi ,
Thanks for confirming! Since you are on Jan 2022 release, please use the DIP switch method to update to Feb release so that you can launch the OOBE experience again and create a new device. By using DIP switch, you don't need to SSH into our device to update it.
Quinn Tran 191 Reputation points

2022-03-15T17:18:13.847+00:00

Hello @Gautam Kasturi ,
Just want to check in if you are able to get your devkit connected from the previous suggestion?

Thanks!
Tina Jain 36 Reputation points

2022-03-17T10:19:26.137+00:00

@Quinn Tran ,
We were able to get the device working by applying the Feb update. Things seem to be working fine on this device, hence I will go ahead and close the ticket now.

Thanks for all your help on this!

Accepted answer

0 additional answers

Your answer

António Sérgio Azevedo 7,671 Reputation points Microsoft Employee Moderator

2022-02-22T16:50:11.19+00:00

Hello @Tina Jain ,
It is my understanding that you have opened an Azure Support Request with this issue, can you please confirm? In the meantime can I kindly request you to follow the steps in Troubleshoot the Azure Percept DK device and share with us what you found out?

Thanks!
Tina Jain 36 Reputation points

2022-02-23T15:02:58.137+00:00

I looked at the module logs (Via ssh) on the device but it shows up the same error that comes in IOT Hub. The RTSP url rtsp://azureeyemodule:8554/h264raw with the default credentials did work for me once before, so not sure why it is throwing an error now. I also refreshed the AVA provisioning token of the module.

Here is the output from the ava module:

"data": {
"code": "404",
"target": "rtsp://azureeyemodule:8554/h264raw",
"protocol": "rtsp"
},

"data": {
"error": {
"code": "RtspIngestionDisconnected",
"target": "The RTSP ingestion was disconnected"
}
Quinn Tran 191 Reputation points

2022-02-23T22:24:17.347+00:00

Hello @Tina Jain ,

Thank you for sharing the output above. Let me check in with our product team. Also just want to confirm if you currently follow any Azure Percept instruction to enable Video Analyzer, which result in the original error message (Error related to streaming). If so, can you share the instructions and the specific steps where this issue happened? It would be very helpful to pinpoint the issue if we know the source. Thanks!
Tina Jain 36 Reputation points

2022-02-24T15:24:25.303+00:00

I have been following Percept Reference article here. The steps mentioned in the article worked the first time for me, but after that subsequent deployments have started creating the 404 issues.

Things tried so far:

I tried deleting the ava module explicitly from IOT Hub, and redeploying the module with a fresh provisioning token.

Deleted the video analyzer resource, re-created a new one and thus a new AVA token as well, followed by another deployment of ava module

Deleting the video in Video Analyzer explicitly, so that a new one can be created when the live pipeline is activated

None of the above steps have worked so far for me.
Quinn Tran 191 Reputation points

2022-02-24T18:48:57.95+00:00

Thanks @Tina Jain !

Can you share both the eye module log and the ava module log after activating the pipeline?
Here is the step;

1) ssh to your device
2) make the command - docker logs azureeyemodule -f and docker logs avaedge -f
3) copy and paste here the content of the log

Thanks!
Quinn Tran 191 Reputation points

2022-03-01T18:40:20.81+00:00

@Tina Jain ,
Did you get a chance to get the azureeyemodule and the aveaedge logs?

Also, the problem might be with the rtsp source. Can you also try the following:

Install the VLC player https://www.videolan.org/vlc/index.html

Copy and paste this url (rtsp://azureeyemodule:8554/h264raw) in the browser

VLC player will pop up to view and check the rtsp h264 stream? (and yes, you need to Install VLC player first)
https://www.videolan.org/vlc/index.html

Let me know if that works for you.
Tina Jain 36 Reputation points

2022-03-02T15:33:37.417+00:00

@Quinn Tran ,

We are currently facing problem with the Percept device itself, due to which we are not able to connect to it at all. As soon as it starts working again we will post the logs here.

Thanks for you support on this!
Quinn Tran 191 Reputation points

2022-03-02T19:23:00.33+00:00

@Tina Jain - Thank you very much for the update! I'll be looking out for your log.

Also feel free to open a separate Q&A thread if you are still facing issues with connecting your devkit. Meanwhile, you can check out this troubleshooting guide: https://learn.microsoft.com/en-us/azure/azure-percept/how-to-troubleshoot-setup
Quinn Tran 191 Reputation points

2022-03-07T18:59:14.537+00:00

Hello @Tina Jain ,
How is your devkit connection issue coming along? Please feel free to post the issue here. I would love to help you to move pass that.

Thank!
Tina Jain 36 Reputation points

2022-03-08T14:23:30.103+00:00

We are still facing issue with the device. It is powered on, but it shows up as Disconnected in the Azure Percept Studio. The device is not available via SSH too.
Quinn Tran 191 Reputation points

2022-03-08T19:08:48.277+00:00

Hello @Tina Jain ,
To further troubleshoot this, could you:

Power cycle the devkit and go through the OOBE again setup Experience. Please create a new device, don't use the old one:
https://learn.microsoft.com/en-us/azure/azure-percept/quickstart-percept-dk-set-up#launch-the-azure-percept-dk-setup-experience

Once done, SSH to the device to get the following log:
sudo iotedge logs edgeAgent
sudo iotedge logs edgeHub

Share the logs here.

Thanks!
Gautam Kasturi 1 Reputation point

2022-03-09T04:43:09.067+00:00

Hi,

I work with tinajain. I tried to get into the OOBE again but when I connect to the devices wifi (apd-xxxx) it connects but does not bring up the OOBE. Even manually connecting to 10.1.1.1 or your.new.device or the original local IP does not work. So I can't get past step1 above to get to step2.
'
Appreciate your help in advance.
Quinn Tran 191 Reputation points

2022-03-09T19:26:15.68+00:00

Hello @Gautam Kasturi ,

When said "manually connecting to 10.1.1.1", did you click to the provided http://10.1.1.1 link in the document? If so, could you try open a browser and type in the "http://10.1.1.1" instead? (In this order: 1) power cycle the devkit 2) Connect your host computer to the dev kit’s Wi-Fi access point (apd-xxxx) and 3) open a browser and type in the "http://10.1.1.1")

If that still doesn't work, I want to re-confirm with you: Have you upgrade your devkit to the latest SW Feb release?

1) If not, please a) upgrade your devkit through DIP switch method (provide that you can't SSH in your device at the moment) and b) go through OOBE again

DIP switch method: https://learn.microsoft.com/en-us/azure/azure-percept/how-to-update-via-usb#using-the-dip-switch-method

2) If you already did update the latest SW Feb release, then try to a) downgrade to the January release using DIP switch method and b) go through OOBE again to get connect and c) Upgrade to the latest SW Feb release.

You can get the Jan/Feb SW release here: https://learn.microsoft.com/en-us/azure/azure-percept/software-releases-usb-cable-updates
DIP switch method: https://learn.microsoft.com/en-us/azure/azure-percept/how-to-update-via-usb#using-the-dip-switch-method

My goal is to help you relauch OOBE and get the device connected again. Hence, suggesting the above steps.

Hope this helps!
Gautam Kasturi 1 Reputation point

2022-03-09T20:01:34.28+00:00

Thanks for your response and perseverance QuinnTran.
I did exactly those steps to get to http://10.1.1.1.
I did not update to the Feb release but I had previously updated to the Jan 2022 release using the DIP switch method and it had worked.
Presently the SSH is not working either (even over USB).
Quinn Tran 191 Reputation points

2022-03-09T20:38:59.047+00:00

Hi @Gautam Kasturi ,
Thanks for confirming! Since you are on Jan 2022 release, please use the DIP switch method to update to Feb release so that you can launch the OOBE experience again and create a new device. By using DIP switch, you don't need to SSH into our device to update it.
Quinn Tran 191 Reputation points

2022-03-15T17:18:13.847+00:00

Hello @Gautam Kasturi ,
Just want to check in if you are able to get your devkit connected from the previous suggestion?

Thanks!
Tina Jain 36 Reputation points

2022-03-17T10:19:26.137+00:00

@Quinn Tran ,
We were able to get the device working by applying the Feb update. Things seem to be working fine on this device, hence I will go ahead and close the ticket now.

Thanks for all your help on this!

Answer 1

Hello @Tina Jain ,
Sounds good. I'm glad that updating to Feb release fixes 1) the device's disconnect issue and 2) the original issue of Video Analyzer live pipeline not working. Please click on "Accept Answer" or upvote which might help other community members reading this thread.

Re-post the solution here for other folks in the community who might run into the same issue:
"Since you are on Jan 2022 release, please use the DIP switch method to update to Feb release so that you can launch the OOBE experience again and create a new device. By using DIP switch, you don't need to SSH into our device to update it."

Thanks!

Share via

Azure Percept: Video Analyzer live pipeline not working

0 additional answers

Your answer