Unable to on-board and use Azure Percept Devkit

Regular Visitor

I'm trying to set up and use the Azure Percept DK by following the instructions of the following documentation, but I'm stuck at this step:- "https://docs.microsoft.com/en-us/azure/azure-percept/quickstart-percept-dk-set-up#launch-the-azure-p....

 

After connecting with the wifi, the setup URL doesn't open up in the browser. Tried all the troubleshooting steps as per the documentation, but still no result.

 

Please let me know if any solution. Thanks!

7 Replies
Hi @MJ410 - just to confirm, have you tried opening a web browser and pasting this url, "https://10.1.1.1"? That should open the setup experience if you are properly connect to the device. If that does not take you to the setup experience then it could indicate that your computer is not connected to the device.
Hi, I am stuck at the same point as well. I can PING the device (in my case 10.1.1.108), 10.1.1.108, 10.1.1.1 or your.new.device/ in a browser refuses to connect. I've rebooted the device a few times.
@Santa_Cruz - it's possible you are still running an earlier version of the software on the dev kit. Can you try 10.1.1.1:4242?

@MikeMcCoy-AED thanks, very much for the tip and I am in!  Time to update the firmware.

Running into a different issue when attempting to create an SSH account to update the firmware:

Command failed: useradd -m -p "$(openssl passwd -1 $'[password]')" [username]
You are required to change your password immediately (password expired)
useradd: PAM: Authentication token is no longer valid; new one required

I tried a different username and password and received the same error.

@Santa_Cruz are you getting this error as you try to connect to SSH or while going through the setup experience? 

 

Have you been able to update the dev kit yet (my guess is you're blocked by this SSH issue, but need to check)?

 

@MikeMcCoy-AED it occurred when I was going through the setup experience. However, after further reading I was able to update the firmware (Azure-Percept-DK-1.0.20210511.1825) via USB-C and no longer getting this error when setting up the SSH account through the setup experience. The last step is connecting to azure...