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

@McMason That is how we usually calibrate our sensors, you should have no issue doing so. I will send your camera calibration files to the email you have registered with the forum.

@Chad-Sweet Thanks; any comment on what temperatures you or the team have seen trying to stream higher than vga resolution through voxl-streamer? Interested if you are seeing the same using 1080p or the full resolution of the sensor, for example.

Thank you @Chad-Sweet. Have you seen any issues with connecting a graupner receiver output to pin11(uart rx) on J19? Just looking for RC input without taking up more space with the IO board, and due to specifics we cant use certain radios. I cant find too much data on if the receiver has an inverted signal like the FrSky does.

@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

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

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.

Wanted to update this by saying I experienced same issue, but I resolved this by disconnecting tracking camera that had been installed upside down. So, if anyone is reading this in the future....try disconnecting your cameras attached to the board

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

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

@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!

@mkwan Can you make a new thread with this issue and include the output of voxl-inspect-services -v

@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.

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.

@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

@powerralley -- I don't work for ModalAI but my off the cuff answer is "yes" and it is something I am trying to build something similar. Modal does provide some mapping/SLAM capabilities that use the Time-of-flight depth sensor to build a 3D map of an indoor space. It does work, but not without some tweaks and work on your part.

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

@Vinny Thanks, this helps a lot!