I'm lost trying to set things up!

KenMax

I installed Depthai to a raspberry pi 4 with an OAK-D lite camera. The demo appeared to work over VNC. I connected my robot to the robot hub, and it tells me my robot is online, but not connected properly. I have no idea what that means.

i have gone back to VNC, and that now tells me that the demo can't run because no DepthAI device can be found. Not sure if that means the robot hub has grabbed it so it is no longer available or what. I am basically completely lost and don't have a clue even where to begin to look.

Can someone point me in the right direction?

jakaskerl

Hi KenMax
It is very likely, as you have said, the robothub (the script you are using) has grabbed the device. Stopping the script or replugging the device should make it available again.

Thanks,
Jaka

KenMax

Yes. I restarted the raspberry and the demo now works again. Thank you for that suggestion.

I still have no idea why RoboHub is complaining of my robot not being correctly configured. All I have done is run the provided script, I have no idea what other configuration is required, and I can't see any documentation that might give me a clue as to what I am missing.

jakaskerl

Hi KenMax
Could you attach some code/images of the errors you are getting?

Thanks,
Jaka

KenMax

Is this what you mean? Basically, although it recognises my device and recognises whether or not my raspberry pi (with attached OAK-D lite) is powered up, I can't seem to do anything. I feel as though I am missing something basic, but I have no idea what.

erik

cc @StepanKroupa ^

StepanKroupa

Hello @KenMax

The "robot is not configured properly" is currently a common warning on RPI devices - it means that the Agent cannot control how your RobotHub Apps will use HW resources of the device. You don't have to worry about it and in future versions this issue will not be present (therefore warning will dissapear).

Regarding the DepthAI script - RobotHub Agent will indeed grab all available devices, so running DepthAI locally will not work anymore - you can stop the robothub agent at any time with "sudo robothub-ctl stop" or disable the "Builtin App" in the cloud UI (Robots -> pick your robot -> Settings) to prevent this.

Regarding usage of RobotHub - you should be able to use RobotHub without issue right now. You can create Apps in the "Apps" tab and then install them on your Robot in Development mode to edit them. If you want some example Apps to go off of, you can check out this repository.

Hope this helps, please let us know if you have any further issues!

KenMax

Brilliant. I shall tackle that next week.

Can I just add my thanks for the level of support provided by this forum? It has been exemplary, and very much appreciated.