Hi @Judoor-0
We have had one other report of something similar where the ToF connector flex comes loose from it's connector located on the M0173 board from high vibe or several hard landings.

If you can see whether or not the connector from the M0177 ToF flex looks like it is not planar on the mating M0173 board, try to use something rather benign electrically (like plastic tweezers) and see if you can reseat the connector into the M0173 board.
We have a good description of these connections shown here: https://docs.modalai.com/voxl2-coax-camera-bundles/

We are going to add in some additional mechanical support here to make sure this issue does not happen long term, despite high vibe/shock scenarios.

If this does not seem to be your problem, please let us know and I'll have to tag someone from the SW team to help you debug further.
Thanks!

@Eric-Katzfey
Thak you for your information.

Should I check following DOCS?right?
https://docs.modalai.com/voxl2-rc-configs/

@tom Got it to bind again. Thank you for your help.

@Sasha-Bagan , actually the noise not too bad, on average under 2m/s/s which is 0.2G, which is considered low.

Are you able to create a video of QVIO overlay which can be viewed through voxl-portal? As well as post a px4 log. It is better not to fly in VIO control mode until this is resolved (fly in manual thrust/roll/pitch/yaw mode and collect the log + video).

@tom said in Has anyone integrated Starling 2 with Sylvus radios?:

M0130

Wonderful! Thank you. That answers my question.

@Jeremy-Schofield No, FPV goggles are not supported.

@tom lol. Thanks!

@Moderator Yes, I did see that. However I expected this to work out of the box. I haven't changed anything.

@ayrric yes, you can find it here: https://www.modalai.com/products/m0155

@Moderator Hi thank you for the link, may I check if the original 4921 green propellers are not supported anymore? And instead the DJI 4726 are the recommended replacement propellers? Also, would an ESC recalibration be necessary after the switch? Thanks.

@Usama-Hamayun you can order the drone without battery.

The Starling 2 and Starling 2 Max both use the same battery packs. They can be either Sony VTC6 or Amprius 18650 cells

@Zachary-Lowell-0

Hello! I was able to reinstall 1.3.5 and that somehow fixed it! I am not going to question it lol.

Now I'm trying to find out how to install voxl-mapper and I can't find documentation for it. I am flying the drone inside a test lab. Today when I was flying it around the room, the drone was not mapping anything. The 2D/3D map was blank when I went to plan a point. I think it's blank because I am missing voxl-mapper especially since I have camera-server, vision hub, voxl-px4 and qvio enabled/running. All I have seen is that I have to change "offboard_mode": "trajectory", in order to plan a point on the map and have the drone fly to it.

Is there any documentation on getting voxl-mapper and planning a point?

@Animeshs said in Tracking Camera Sync:

Are the tracking cameras on Starling 2 with C26 (dual tracking) and C27 (triple tracking) configs synchronized?

@Animeshs I believe if the fsync parameter in the /etc/modalai/voxl-camera-server.conf is set to true then the cameras will be in sync.

Zach

@Judoor-0 , if you can reliably reproduce this, please look at output of top, which will show all the processes and amount of memory they are using, you can also sort them by memory usage, please check usage of the top tool. Hopefully this will allow you to pinpoint which process uses a lot of memory and more importantly increasing amount of memory.

You can check the memory usage per process and see if there is any process that uses more memory over time. Try to do that without flying first, but running the whole processing stack if possible.

Alex

@griffin , this is expected behavior (from our point of view 🙂 ). Here is what's happening:

the image from hires large stream (which is what I assume you are using) is either 3840x2160 or larger, around 4xxx by 3xxx depending on which camera you are using voxl portal is not very efficient at processing large images and when it receives the huge 4K image (YUV or RGB), it will use turbojpeg (software JPG encoder) to convert it to jpeg. This process takes a lot of cpu for large images and especially if fps is 30, it is too much for voxl-portal to handle if you want to view hires images through portal, you can enable (if not enabled) en_small_video stream in camera config file /etc/modalai/voxl-camera-server.conf and set resolution to something smaller, usually 1280x720 or similar is good (depending on the aspect ratio that you need) once you enable the small video stream, you can view the hires_small_color stream from the voxl-portal the cpu % (assuming you are looking at output of top) will show the cpu usage percentage at the current cpu frequency . So this number is often very misleading because if the cpu is not running at max frequency, it will have higher % usage compared to perf mode (which can be set using voxl-set-cpu-mode perf. You can use tool voxl-inspect-cpu to show the total usage of each core (which takes into account the frequency of each core) and you can also see the current core frequencies (but you cannot see individual processes).

Please let us know if you have any other questions.

Alex