Connection String ID for Altek AI Camera IoT Device
Closed this issue · 68 comments
Just curious what the syntax for the connection string ID to add the IoT device to a IoT hub in Azure during the setup process. The camera keeps trying to connect, but it hangs on this screen and eventually fails...
This is what the general syntax of the connection string looks like:
@agryguc According to our testing if the camera keeps trying to connect, but it hangs on this screen and eventually fails means there is a problem with connectivity. If the network connection is slow it takes time to connect and then it fails.
If you have IoT edge connection string then give it otherwise you can go n click the next button.
Here is the link for reference- https://azure.github.io/Vision-AI-DevKit-Pages/docs/quick_start/#configure-your-camera-to-connect-to-azure-as-an-iot-edge-device.
@v-prsasa - thanks for your response. I dont believe there is an issue with connectivity.... I was referencing the quick-start guide throughout the process of getting it configured. What I am asking is the about the syntax for the connection string to connect the camera to Microsoft Azure? T I don't believe I am using the correct device ID or, host name or shared access key, what are those? It still hangs on the screen and eventually fails irrelevant of what device ID/hostname/access key I put, so I am not sure I am using the correct syntax. Please advise.
@agryguc Yeah I understand your problem . Are you trying to configure it for first time or you have done before? If it's first time then you don't need any device ID/hostname /access key. You should click on next button and continue with further process.
Because according to our testing it's working fine.
@v-prsasa thanks, but intuitively that is what I initially tried (no connection string just clicking next), but it does need one to proceed as it states "invalid connection string" when you leave it blank...
Also, yes, I am trying to configure it for the first time.
@agryguc I am attaching my screenshots step by step for your reference. Kindly go through it.
Thanks, but I followed the setup walkthrough already, your device uses a device code to connect, this one does not.... it requries a connection ID string... I need to simply know what the synatax I should be using for this string? There are no other options like the one you suggest below:
The only option is with an IoT Edge connection string like below:
Please advise, all I am asking is simply what do I fill in for the "XXXX's" in the string below:
HostName=XXXXXXXXXXXXXXXXX;DeviceId=XXXXXXXXXXXXXX;SharedAccessKey=XXXXXXXXXXXXXXXX
@agryguc I got your point, So according to my observation and testing the syntax i.e for hostname,shared accesskey and device id , It's an example of my testing.
HostName=Priyanka-Hub.azure-devices.net; SharedAccessKeyName=device; SharedAccessKey=xBdz+R5jDk7sbir4wx3FZL8H2fUOu8+AzcYTOuGCfJg=
@v-prsasa thanks, where did the access key info come from? And the host name? And the shared access key name? Can you give me an idea if any of those are the SSID/password or S/N of the actual device or are they the SSH remote login credentials????
Or does it relate to the IoT hub information that I setup in Azure?
@agryguc Yeah sure, It's related to the IoT hub information that you setup in Azure. There is Settings in that portal. In settings you have to go to Shared access policies and then you can go to device. If you click on device you can see the shared access keys. I am attaching a screenshot for your reference too.
@v-prsasa thanks that makes alot more sense. I am trying to reset the camera because the SSID network isnt showing up on my computer anymore (my guess is it partially got through the configuration process and isnt allowing me to connect to it to restart the setup process again at http://setupaicamera.ms/)
I held the small reset button on the back of the device for over 30 seconds until an audible "click noise" was heard, then I plugged everything back in and the camera's network still doesnt show up on any of my computers.... any advice here? Because of that when I try and access the camera now for setup it wont allow me to connect...
Thanks,
Andrew
@agryguc Actually it should work after all this reset. Can you try to do full factory reset.
Here is the link for your reference- https://azure.github.io/Vision-AI-DevKit-Pages/docs/reset/
Still 3 flashing red lights (setup mode) and no wifi network showing up. The first step of the reset process you sent via the link is to press the "power button" for 5 seconds... this device has no power button, only a small pinhole reset button. Please advise.....
@agryguc Yeah you are correct that there is a small pinhole reset button, just press the "power button" for 5 seconds and restart it. Try to reset and configure everything from starting.
@v-prsasa - so there is no power button on this device at all, as in it doesnt exist.... There only is the small pinhole reset button which I have tried multiple times and reset/rebooted the device, but still the SSID device wifi-network does not show up on my wifi tray and the device then continues to flash three red lights.
@agryguc Yeah I understood your problem of SSID device wifi-network does not show up on your wifi tray. I need you to do full reset means reboot your device from scratch means- Go to this folder->PEABODY_QCS603_LE_r37-v0.5370_Perf->v0.5370_Perf and run FastbootUpgrade_v6_5 this one.and then it will work most probably. Just try it out till then I will try in my device.
@v-prsasa, with the camera plugged in via USB running that batch-file fails...
Please let me know if there is anything else I can try.
@agryguc If the batch-file fails means the device is not plugged in via USB properly. Please just try to check whether it is connected properly via adb tool.
@agryguc Yeah sure, When you connect your device via USB cable then open command prompt and type the following command-
adb
adb devices
I am attaching screenshot for your reference-
@agryguc yes it won't work, because you have to install platform tools for this.
Kindly refer to this Link- https://azure.github.io/Vision-AI-DevKit-Pages/docs/platform_tools/
Still no luck......
@agryguc Okay let me explain you with full process-
1)Download Platform-tools_r30.0.4
2)Add the platform tools path in your environment variables path i.e Go to System properties -> Advanced -> Environment variables -> Go to Path -> Add the platform tools path there -> and then click on OK
I think after this it will work.
@v-prsasa - still no luck.... adding the platform tools bath to the user and system variables still doesnt make a difference when I run adb devices
Command prompt pops up briefly when I run adb.exe, but nothing else noticeable happens....
Still no luck running adb devices...
There has got to be an easier way to do this... can we not troubleshoot connectivity in device manager? The camera was working before, once I tried the actual syntax of the connection string it froze and I was unable to get it to reboot/reset so that I could try re-configuring it from scratch....
@v-prsasa I have never updated the firmware from what it shipped with. I dont even know how to check to be honest...
@agryguc Can you download the latest firmware from the below link-
https://azure.github.io/Vision-AI-DevKit-Pages/docs/Firmware/
Step 2 of the link you just sent literally contains the issue we are having with adb tools, so I haven't been able to update the firmware...... (I tried this over a week ago with no luck)... Please advise how I should proceed
Is says device is not attached when I try to run FastbootUpgrade_v6_5.bat
@agryguc Once you update the firmware to latest version it will start working. Let me check from my end once until then can you try again.
Understood, I have been trying to update the firmware for the past week, but I will try again. Please let me know if you figure out a workaround.
@v-prsasa - any word on how to fix this problem, still no luck updating the firmware.
@v-prsasa - any suggestions on how I can get update the firmware without ADB tools or use some other workaround?
@agryguc This is the only way to update firmware with adb tools which is given in the links- https://azure.github.io/Vision-AI-DevKit-Pages/docs/Firmware/#download-and-extract-the-latest-firmware
@v-prsasa - so what do you recommend I do then? Since ADB devices is continually not recognized and "device is not attached"? Giving me the same information that I have had for the past two weeks and was literally the first thing I tried following the issue isn't a terribly useful workaround.
@agryguc Can you please share screenshots of the steps you are following ? It will be helpful for me
@agryguc I would like to suggest you when you download the platform tools, extract the zip files and set the path of the extracted zip file (platform tools) in command prompt. I have attached the screenshot, kindly look into it.
Okay, that worked, now do I try updating the firmware?
@v-prsasa - after copying the windows specific batch files to the firmware directory and doubleclicking the "FastbootUpgrade_v6_5.bat" file... it still says device is not attached, despite it being recognized in the list of devices using adb devices in a separate command prompt
@agryguc Which firmware version you are using? The latest one is v0.5370 and if you are using latest version then no need to perform this step. You can skip this and reboot this by using this command - adb shell cat /etc/version.
I dont know what firmware is on the device, how do I check that? The firmware I had downloaded was v0.5370. I will try rebooting, but using that command did not yield anything.... I am assuming I need to replace "version" with the version number?
@agryguc No need to replace version with version number. By using this command -adb shell cat /etc/version youcan check the firmware version. First try to reboot the device by using adb reboot command.
Device audibly clicked using the adb reboot command (and the flashing red lights went solid red for about 10 seconds), then returned to flashing red (setup mode). The devices has v.0.2680 version of the firmware.
Running the batch file to update the firmware afterwards still fails though....
@agryguc It's the older version firmware. Please update it to latest version. You can refer to the link-https://azure.github.io/Vision-AI-DevKit-Pages/docs/Firmware/#update-the-firmware
@v-prsasa - yes, I did that (and have been trying to update the firmware for the past two weeks). When I run the batch file nothing happens.... after copying the windows specific batch files to the firmware directory and doubleclicking the "FastbootUpgrade_v6_5.bat" file... it still says device is not attached
@agryguc Let me clear things here when you are connecting your device and running the ADB command that time ADB is showing list of the devices, once it shows the list of devices then you run the "FastbootUpgrade_v6_5.bat" file. This is the process.
Okay, do run it from the same cmd window? or do I double click on the batch file in the firmware directory? How do I run it from the cmd window? None of that information is stated in the firmware update link....
https://azure.github.io/Vision-AI-DevKit-Pages/docs/Firmware/#update-the-firmware
@agryguc No dont't run it from same cmd window. Double click on the batch file in the firmware directory.
Okay, that hasnt worked the last 20-30 times I have tried it over the past 2 weeks.... so I doubt it will work now.... and to confirm trying that again. Still says device is not attached.
Yes, tried rebooting twice again and same thing when clicking the batchfile to update the firmware. Also, the device SSID is still not showing up in the wifi tray.
@agryguc According to my testing it's working, Can you check device battery level ? by using this command- adb shell cat /sys/class/power_supply/battery/capacity , Because when the battery is less than 50% this batch file won't run.
Battery level is 100%
@v-prsasa - well it does not.... this was literally the issue since day one... please advise how I should proceed. For some reason the firmware isnt flashing....... all of this other diagnostic information just confirms the issue I originally had as I followed the instructions verbatim. Please advise. Running the batch file to flash the firmware as an administrator still does the following.
@v-prsasa - any ideas on why the batch file to upgrade the firmware isnt running properly?
@agryguc mostly it doesn't work when the battery power is less than 50% , but in your case battery is 100% so it should work.
@v-prsasa - yes, I have ensure the battery level is 100% multiple times while trying to flash the firmware, yet it still doesn't work. Please advise as to next steps and/or workarounds....
@agryguc I have provided you all the steps and workaround still you are facing the problem. Let me check with my team internally.
@agryguc Yes, Everyone is able to connect it to adb and fastboot upgrade works for them. Still wondering why the issue occurs with you. Have you tried again?
@v-prsasa - same result, I confirmed the battery level was 100%, confirmed that the device is connected via usb and is being recognized by adb devices... confirmed that I placed the batch files in the firmware directory folder and executed the batch from within that folder. The same error message keeps happening...
