@Mihir-Bala Technically it should work, we have not done any pre-integration as you've mentioned

@awoods ,

Here is a sample log from one of our recent tests using a Starling platform.

You can review the PX4 log here : https://review.px4.io/plot_app?log=3a4c53fd-db88-4d54-8f2e-5f22e159bfc6

The accelerometer noise looks comparable to yours, perhaps a bit less. The main thing is that motor outputs are pretty clean, very minor oscillations. You can collect a similar log and compare using px4 flight review. Also look at gyro noise which more directly affects motor commands.

starling_imu_noise_sample.png

Thanks @Alex-Kushleyev, will do, much appreciated

@thomas Thank you the update procedure worked and the results I posted in this thread

https://forum.modalai.com/post/14049

@Darshit-Desai , yes i believe you are showing the TOF and Hires camera local frames correctly.

As for the vehicle, the convention we normally use is FRD, but since you mentioned that you are assuming FLU in your case, that also looks correct.

Hi @riteshsharma
We usually recommend a small screwdriver (flat edge) or tweezers to actuate those small switches.
For the FASTBOOT switch, you need to use something less likely to break the top plastic, so the back end of a qtip or a pencil is good for that one.

@Jetson-Nano Looks like MPC_POS_MODE is needed as well per the documentation https://docs.px4.io/main/en/computer_vision/collision_prevention.html

@Eric-Katzfey We loaded the default parameters with QGC and everything is back to normal.

Thank you for your help!

@Moderator As far as I can see, there is no interference in the area, I am working along for like 100's of meters. I don't have any such equipment in my premises which can interfere.

Physically, I checked the "915MHz ELRS Receiver" (BetaFPV Nano RX) and it's not lose. What else I can check?

Please help us fix all the issues, we are in agony since we started using this (Starling) kit.

I have other open issues too.

Starling gone rogue (uncontrollable) in Position flight mode

What does /etc/modalai/voxl-vision-hub.conf contain?

Did you follow the setup instructions and configure offboard_mode to trajectory?

Thanks, this worked!

@tom
I have a new issue

Since yesterday, when I turned on the Starling drone, it just sits there. It's not getting armed. When I checked for ADB shell, it's not getting connected, and an error comes up saying no devices found. When I checked the forum, it said it might be bricked due to some file loss. We followed the unbrick tutorial, and after successful flashing of the latest QDL M0054.14.1a-flat-v3, the device is showing up as Qualcomm bulk something. However, ADB still isn't getting connected.
Please note that I am unable to enter adb shell and fast boot mode .

For unbrick I followed this
https://docs.modalai.com/voxl2-unbricking

Thanks for the wonderful support from team modal AI. Here is the solution which they have shared with me, which is tested and working 100%.

Please download the attached file

file:
Download this

Move into the ufs sub directory of that release ^:
cd 2024-02-09-1.7.4-M0054-2/ufs

Slide the SW2 switch to ON to be in QDL mode
Plug in power and USB

Run:

sudo qdl --debug --storage ufs --include . prog_firehose_ddr.elf rawprogram_unsparse0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml

@kgn-mdlai Is HITL interesting for your purposes? https://docs.modalai.com/voxl2-PX4-hitl/

@Moderator Hello, thanks for your help. However I am still confused about what to do with this information. Is there a special version of the SDK I need to install for our version (M0054-2)? It says it requires SDK version 1.1.3+ and we are trying to install 1.2.0 which should be ok, correct?

When we start voxl-tag-detector service with "en_tag_fixed_frame": true any change to offboard mode makes the drone loose the position, heavily drifting sideways. Isn't the px4 control referenced only to local frame? If so tag relocalization shouldn't affect the hold position. Is there any other configuration we are missing?

@labkit it is part of the SDK but not installed on the kernel - on you voxl2 please run the following:

sudo apt-get install voxl-ros2-foxy sudo apt-get install voxl-microdds-agent sudo apt-get install voxl-mpa-to-ros2 voxl-configure-mpa-to-ros2

Once this is done you should be ready to use ros2 by running source /opt/ros/foxy/setup.bash as well as export ROS_HOME=/opt/ros/foxy

Hope this helps. Also ensure that for the voxl-configure-mpa-to-ros2 line you have an active internet connection on the voxl2 as this requires some pip installs.

Thanks!
Zach

@Eric-Katzfey Issue is mostly resolved. There were two main errors to fix. The first was that the cable that I was using needed to have its RX and TX wires swapped as Vinny pointed out. The second was that Docker Desktop needed to be uninstalled and replaced with only the core Docker CE Engine. After doing this, the HITL seems to be up and running on the alternate Linux computer I tested with. On the original computer, the "Serial port closed error" is no longer present although there does seem to be a graphics issue when attempting to run the Gazebo image with graphics.

8d0e6ab0-9969-4fb4-853c-4879b46992bf-image.png

Once this is fixed I think it should be all ready to perform simulations.