@Kevin We've recently released VOXL SDK support for RB5-Flight, I'd highly recommend upgrading your drone to this newer system image and VOXL SDK as you will have much more software support. Checkout the video we have here: https://docs.modalai.com/Qualcomm-Flight-RB5-system-image/#voxl-sdk-for-rb5-flight

I'm not sure if you still have this problem, but if you know ROS, you can stream the cameras on your computer by configuring the drone to have the ROS master on your computer. First follow the steps at this link to setup ROS on RB5. https://docs.modalai.com/setup-ros-on-voxl-2/

Then you can set the ROS master to be on your computer by opening ~/.bashrc on the RB5 drone, and entering these lines in the file:

export ROS_MASTER_URI=http://{PC_IP_ADDRESS}:11311/ export ROS_HOSTNAME={RB5_DRONE_IP}

PC_IP_ADDRESS can be obtained from ipconfig on your computer. RB5_DRONE_IP is the one you use to ssh into it.
Then on the drone:

source ~/.bashrc

On your computer execute:

roscore Rviz

On the drone execute:

roslaunch voxl_mpa_to_ros voxl_mpa_to_ros.launch

You will then be able to view the camera display topics from voxl_mpa_to_ros on your computer. You can stream them on Rviz, and you can create ROS nodes to subscribe to these topics for whatever computer vision application you develop. Hope this helps.

I encountered this problem a while ago and its just a matter of a usb device on your virtual machine

7e018bc6-8636-428f-b624-327316eb00a7-image.png

You can also download adb for windows to verify that the drone is detected by the computer. If it's not detected by your computer at all (on host OS), then it won't be detected by your VM.

Thanks, that's exactly what I'm looking for

Hi Adrian Hidalgo ,
The status is like the video below. Do you have any suggestions? thanks

https://www.youtube.com/watch?v=urtfFJ4y4kw&feature=youtu.be

@Gregory-A-Welch, sounds like there was a significant crash. We can send you replacements but I would be worried about the damage that might have been sustained to the Flight-Deck. Would you mind sending a pic of the state of the drone?

We can build you a replacement drone, basically an RMA. I would recommend going this route, since there are a lot of little nuances to the build and would be the quickest to get the drone back in the air. We can also repair the Flight-Deck

Hi @umlr ,

Here's some info for VOXL 2 which shares most of the design.

https://docs.modalai.com/voxl2-linux-user-guide/#gpios

For the RB5, qualcomm had some sample code here:
https://github.com/quic/sample-apps-for-Qualcomm-Robotics-RB5-platform/tree/master/GPIO-samples

For example, we are using it here:
https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-bind/-/blob/master/src/voxl-bind.c#L58

GPIO 46 going to J10 pin 6.

GPIOs 82, 83 and 84 control the onboard LED which you can use and get visual feedback.

@Sam-Kiley All of the VOXL suite is open source, voxl-modem lives here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/tree/dev

The quectel related source is from https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/tree/dev/src/quectel-CM

But yes I believe that’s where I get the updated version from. I’ve also reached out to Quectel to make sure I get the very latest.

@stevedan It is better to use this wrapper project to build px4: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-px4. Use the instructions in the readme for that project instead of the documentation you were looking at. Sorry for the confusion!

You can register the drone here: https://faadronezone-access.faa.gov/#/

Yes, things are working fine now. Thanks for the support.@RichieRich

Actually, I realized that the Hold mode can be switched back to Position mode once I move sticks more than 30%. However, the switching from Position to Hold mode was too fast (i.e., within 1 second), so whatever changes during that time was discarded and after moving 30% of sticks in order to switch from Hold to Position, the Altitude is either too high or too low for the next move.

Do you know which parameters postpone the process of switching from Position to Hold mode? Thank you.

I setup wifi connectivity on the RB5 drone by executing

voxl-wifi station ssid password

It automatically connects to any network with that matching ssid and password, whether it is a hotspot setup by my cellphone or setup by my personal laptop, regardless of their IP address. This is the functionality that I want. If the IP address of the drone changes because it is connected on a different network, that is fine. The issue is the drone IP address changing even though it is re-connecting on the same network after being turned off and turned back on.

@tom said in Drone IP Address keeps changing:

@alfa-budiman The ROUTE_IP and LOCAL_IP depend on the format of the IP addresses on the WiFi network you are attempting to connect to.

I would connect to your WiFi network and check the IP address given to your drone by the network.

If it gives you an IP address in the format 192.168.X.Y you'll want to set the ROUTER_IP to 192.168.X.1

then set LOCAL_IP to whatever IP you want to request from the router, it will need to be in the format 192.168.X.Z where Z is the number you want to request.

My concern with entering these IP addresses is that it would then cause the cause drone to search for a specific IP address or else it will not connect.

I documented the steps I took to setup my drone here:
https://github.com/albud187/uav_nav_ops/blob/manual/RB5_Drone_Setup.docx

@Alejandro-M
I documented the steps I took to get my RB5 drone from out of the box to flying programmatically with MAVROS. It includes intermediate steps such as wifi and QGround control setup.

https://github.com/albud187/uav_nav_ops/blob/manual/RB5_Drone_Setup.docx

Hi @Alejandro-M
It's highly likely the ESC or Power Module board was irreversibly damaged from this configuration (normal lab wall power supplies cannot power a drone without near certainty of failure).
If there is a short on the +5V_DCIN to GND, you can easily observe that, but the other failure mode could be an open circuit which will not show up on a DMM easily.
Your best course of action may be an RMA with us so we can explore the drone and find the failure(s) and offer you replacement options to get this platform back up and running.
https://www.modalai.com/pages/rma

Discussion moved to https://forum.modalai.com/topic/1647/voxl-streamer-does-not-handle-teardown-request-signal-correctly/4

Everything looks good, gave it a glance and a quick test, it's been merged to our dev and staging branches in v0.4.2 and will be in the next release, thanks!