Hi @JANG The only time a power module is damaged is when a power supply is used to power the system and the motors are spun up, creating a voltage spike on the input rail that exceeds 28V, not a battery. So, this overall is very surprising to me. You are welcome to use any 5V source for FCv2. It does not need much power (maybe 1-2Amps total) so our power module is overkill for a FCv2, but it helps by providing current and voltage readings to to PX4 or you FC SW of choice.

@buem799 Yes, I think that one should work fine. But there's probably a bunch of configuration options for the receiver so you have to make sure that it has been setup properly to do CRSF.

@buem799 Hi, no worries, I am also very new to this space. ffplay is separate thing, part of the ffmpeg program, not something inside VLC. This is the reddit link that I posted in the thread I listed above https://www.reddit.com/r/reolink/comments/yzhlxp/found_a_solution_for_rtsp_blackno_video_in_vlc/#:~:text=In VLC%2C under the Tools,video stream in VLC player If you read through it, the fix was for a windows machine, which I was using at the time. It states further down in the reddit post that live555 support was removed in newer versions of ubuntu (linux operating system). From your screenshots, it looks like you are using ubuntu, so it could make sense that VLC may not work. I believe it is more a ubuntu issue rather than VLC. Don't try to dig into that, especially if you are new to linux. I would install ffmpeg on your system and try to access the RTSP stream using that. I just asked ChatGPT for the commands to do that and will paste below: sudo apt install ffmpeg Id recommend asking Chat how to access an RTSP stream using ffplay, or read the documentation The other thing you could do, if you had a windows laptop, you could connect the windows laptop to the drone wifi and try to access the RTSP stream via VLC on windows and do the fix included in the reddit link

@yardy Folks recover using that tool all of the time. When it doesn't work, it's due to hardware damage. Often from ESD, or simply crashing the drone. See https://modalai.com/handling

@Aaron-Porter , the voxl-logger does not control what format the images are coming from voxl-camera-server. Currently, voxl-camera-server can output images in RAW8, YUV format and JPEG only in the case of a snapshot (not continuous). So, to answer your first question, the camera server does not support outputting PNG or JPEG in continuous streams. voxl-logger already supports saving images in png or jpeg format, depending on the type of image that is being logged (RAW8 mono or YUV color, etc). You could tweak the behavior to your needs or add a flag to voxl-logger to force a logging format : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-logger/-/blob/master/tools/voxl-logger.cpp?ref_type=heads#L1455 . Alex

@GlennTee Good news! The program now runs, turns out I needed to add the .py extension to the file name when calling the run command, so it should be "ros2 run px4_ros_com offboard_control.py" However, we experienced a lot of errors while running. The drone did arm (But only would do every even numbered attempt for some reason), however it did not fly. I'm working now to debug these errors. [image: 1742487372952-image-1-resized.png]

@Alex-Kushleyev Can you provide me an EMAIL where I can share the video?

@wen-max On the datasheet it says take-off weight of 566g https://docs.modalai.com/starling-2-max-datasheet/ Take off weight includes the battery

@wen-max Yes, the 500g payload capacity is in addition to the battery. If you double the weight, flight time will be cut in half

Thank you for your detailed response! It has already addressed much of the urgent information we needed. We look forward to receiving more details on the props and speed.

@dongsup-seo I would recommend flashing the latest SDK (1.4.1) as that will have much better handling for M0054-1/2, I think a lot of that logic was missing on 1.1.3 as that is very old.

@Eric-Katzfey Thank you for your work! It successfully resolved the issue. The unexpected characters no longer appear on the OSD. I appreciate your support and quick response.

Hello @Alex-Kushleyev, Thank you for the confirmation. It has helped us decide upon the architecture for the current and an upcoming project. The suggested M0141 add-on is really helpful suggestion as well. Regards, Ashwin

@tkddnjs825 Hello, can you post the output from the command voxl-version. We urge all starling users to migrate to SDK 1.4.1.