@Mark-Ogata , Starling 2 Max already has 4 or 5 cameras (depending on configuration - 5th could be a TOF sensor if selected). There are two high resolution IMX412 cameras (up to 4056x3040 resolution rolling shutter RGB cameras) and there are two AR0144 monochrome global shutter cameras that are used for feature tracking / VIO (1280x800 resolution). If you really wanted to, you could add two more high resolution cameras to VOXL camera port J8 (camera ports J6 and J7 are fully used up). Adding the first IMX412 camera would just require you to buy a camera with the correct adapter, such as M0161 camera (with ucoax cable) and M0155 adapter which would plug in to VOXL2's J8. In order to get two IMX412 cameras added to starling 2 Max, it will be a bit more complicated, including a small Kernel change. It looks like you are potentially looking to re-configure cameras on Starling 2 Max, so my suggestion is first to understand the capabilities of the cameras you have (resolution, field of view, etc) . The lenses on the IMX412 cameras have about 120 degress of horizontal FOV (and you can check it) : https://www.modalai.com/products/msu-m0161 . So for full 360 degree coverage, you would technically only need three of these cameras. However, you have a total of 4 cameras already and the lower resolution AR0144 cameras also have a wide FOV (almost 140 degrees horizontal : https://docs.modalai.com/M0166/) and can be used to supplement the two high resolutions cameras. It seems to me that you could take the cameras that you already have and build a hardware mount for them. Also, as Eric said you might want to consider using VOXL2 for whatever you are trying to do on the Raspberry pi, since VOXL2 runs Ubuntu linux (but no display). In terms of USB adapters, your startling 2 max already has a wifi module that uses a USB2 adapter, so you can plug in an ethernet adapter instead of that wifi dongle. BTW M0151 adapter board (which is part of Starling 2 Max, this is were the wifi dongle is plugged in) supports USB 3.0 : https://www.modalai.com/products/m0151 Alex

Hi @Tamilselvan, Yes, our FPV ESC should be a good match for this motor in terms of power, however you will need to perform tuning and testing (non-flying) to prevent de-syncs, as described here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/doc/low_kv_motor_tuning.md You would first need to follow our standard tuning guide as described here, but first increase timing advance and sense advance to the numbers from the above link, so that you don't have a de-sync during calibration : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md Please note that the FPV ESC only has the total current sensing, so you would want to run the tests with the ESC ID2, which measures the total current, so it will be reported to the python test scripts. Just for full disclosure, we do not do a lot of testing using low kV motors, but the parameters are there to adjust and test performance. You would need to do sufficient bench testing to convince yourself that the ESC tuning is good and you are ready to test flying. If you need more guidance for testing the ESC performance, I can help you. You should first start with the link I mentioned above and then modify the script to run continuous tests and perhaps detect anomalies. We may extend our test script to support testing like this with automatic error detection in the future. If you do not have experience with ESC tuning or do not wish to go through this procedure, then our ESC may not be the best choice for this motor. Alex

@groupo Thanks for this! I am pretty familiar with the AT Commands I just haven't tried disabling bands yet. Will add it to me to-do list

@rdjarvis Okay, great! Instead of starting voxl-px4 with systemctl start voxl-px4 can you start it as a foreground process using voxl-px4 -d and then capture the output and paste as a response? I'd like to see if there are any error messages printed that could help determine why it isn't seeing your GPS unit.

@buem799 Yes, you would be able to use Seek. We do not currently support this, it's just some internal stuff we are using for Seek evaluation and development. Here is the contents of our Dockerfile, hopefully this is helpful to you. FROM arm64v8/ubuntu:focal WORKDIR /home RUN apt-get update RUN DEBIAN_FRONTEND=noninteractive apt-get install -y cmake libopencv-dev libusb-1.0-0-dev RUN DEBIAN_FRONTEND=noninteractive apt-get install -y git RUN DEBIAN_FRONTEND=noninteractive apt-get install -y g++ vim # This will update if there have been any updates to the voxl-dev branch and force a new git clone # ADD https://api.github.com/repos/modalai/libseek-thermal/git/refs/heads/dev version.json RUN git clone https://github.com/modalai/libseek-thermal.git RUN mkdir libseek-thermal/build WORKDIR /home/libseek-thermal/build RUN cmake .. RUN make RUN make install RUN ldconfig WORKDIR /home COPY Seek_Thermal_SDK_4.4.2.20.zip . RUN DEBIAN_FRONTEND=noninteractive apt-get install -y zip RUN unzip Seek_Thermal_SDK_4.4.2.20.zip RUN rm Seek_Thermal_SDK_4.4.2.20.zip RUN DEBIAN_FRONTEND=noninteractive apt-get install -y libsdl2-dev WORKDIR /home/Seek_Thermal_SDK_4.4.2.20/aarch64-linux-gnu RUN DEBIAN_FRONTEND=noninteractive apt-get install -y usbutils RUN DEBIAN_FRONTEND=noninteractive apt-get install -y udev RUN cp lib/libseekcamera.so /usr/local/lib RUN cp -r include/* /usr/local/include RUN mkdir -p /etc/udev RUN cp driver/udev/10-seekthermal.rules /etc/udev/rules.d # RUN udevadm control --reload RUN chmod a+x bin/* WORKDIR /home/Seek_Thermal_SDK_4.4.2.20/aarch64-linux-gnu/examples/build RUN cmake .. RUN make WORKDIR /home COPY libmodal-json*.deb . RUN dpkg -i libmodal-json*.deb RUN rm libmodal-json_*.deb COPY libmodal-pipe*.deb . RUN dpkg -i libmodal-pipe*.deb RUN rm libmodal-pipe*.deb ENV LD_LIBRARY_PATH=/usr/lib64 WORKDIR /usr/local/workspace

@Tamilselvan Correct, for example take a look at our UVC camera server: https://docs.modalai.com/voxl-uvc-server/

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.