Skip to content
  • 0 Votes
    10 Posts
    4k Views
    Eric KatzfeyE
    @Mustafa_Cayci You can get the Starling 2 Max with a ToF sensor for depth mapping indoors (The sensors don't really work outdoors). https://www.modalai.com/products/starling-2-max?variant=49129974923568
  • UAVCAN error in FC v2 px4 firmware

    Ask your questions right here!
    5
    0 Votes
    5 Posts
    607 Views
    Jetson NanoJ
    @Eric-Katzfey UAVCAN is working in the latest versions, when enabled. And yes I meant heading error, thats my mistake. The collision prevention is the major issue I am having. The heading error is in the latest version, and I also came across it in the issues section and it was shown solved, but I did not test it out still with VIO, I was testing with only Optical flow and it was not working.
  • GPIO on DSP?

    VOXL 2
    8
    0 Votes
    8 Posts
    2k Views
    J
    @tom got it, I think you indirectly answered my question by giving me the last valid configuration. Am I looking in the right place?: voxl sdk 1.5.0 -> system image 1.8.04 -> recipes-kernel/linux-msm/files/dts/common/m0xxx-modalai-gpio.dtsi : &soc { voxl_gpio { ... modalai,gpio-init-output-high = <0 1 53 56 57 85 86 87 88 89 124 152 157 159>; modalai,**gpio-init-output-low** = <36 37 **46** 54 55 67 82 83 84 131 153 154 155>; modalai,gpio-init-input = <48 49 50 51 52 110 111 112 113 114>; status = "ok"; }; ... }; So settings for gpio pin 46 on sentinel w/ spektrum receiver should be direction:out, value:0 assuming they aren't overwritten somewhere else.
  • evaluating navigation technologies for UAV

    Feature Requests
    1
    0 Votes
    1 Posts
    852 Views
    No one has replied
  • 0 Votes
    1 Posts
    711 Views
    No one has replied
  • Microhard pDDL Carrier stopped working

    Ask your questions right here!
    10
    0 Votes
    10 Posts
    1k Views
    VinnyV
    @gerard I also just remembered we had a stint of bad MCBL-00010's a few months ago... We have since cleared that up, but there is no telling how long ago you may have ordered that cable... Please see this thread for guidance and if you do think your MCBL-00010 is at fault, we will replace your M0048, just reference both threads in your RMA (this one and this one -->) https://forum.modalai.com/topic/4632/flight-core-2-firmware-update-through-qgc?_=1781284416780
  • VOXL2 and QGC via USB Connection Issues

    Ask your questions right here!
    4
    0 Votes
    4 Posts
    323 Views
    nickanickN
    @Eric-Katzfey We reinstalled the QGC in a new laptop and it is working fine now.
  • Connecting to QGC Via Transmitter

    VOXL 2
    6
    0 Votes
    6 Posts
    1k Views
    Eric KatzfeyE
    @PatkirkMartin No, as I said a UART mapped to the applications processor would also work. PX4 has a split architecture on VOXL2 with all flight critical operations happening on the DSP and support functions such as Mavlink, logging, and data manager are on the applications processor. But there is flexibility to move functions between them as needed. So, to match the ELRS receiver with the Mavlink module you could run it on the applications processor instead of the DSP. However, you would need an expansion board that exposes such a connector.
  • Voxl ESC not responding and not detected

    ESCs
    10
    0 Votes
    10 Posts
    4k Views
    Alex KushleyevA
    Hi @Jetson-Nano, Can you please clarify the following - in your original post, you mentioned that the third party ESC also had issues, however in the post above you said no issues. I am quoting your notes from above: " Scenario 3 – Third-Party ESC Evaluation To further isolate the issue, we replaced the VOXL FPV ESC with a NeutronRC X-CLASS 4IN1 ESC V2 (3–8S, 70A) configured using the DShot protocol. During testing, we observed the following: ESC temperature increased rapidly, reaching approximately 80°C to 90°C within two minutes of flight. One motor would subsequently stop during flight. The aircraft would lose stability and crash. " I just wanted to clarify what actually happened and then we can investigate further. Than, you for providing the diagram, i think it looks OK. I have never seen this behavior where the ESC reports incorrect voltage and these short spikes in temperature. This may point to a hardware issue on the ESC board, but i do not actually know where it might be or what would cause it. Have you visually inspected the FPV ESC that has this issue to see if any components appear damaged or anything looks unusual? Alex
  • VOXL2 USB Host Port J18 Not initializing

    Ask your questions right here!
    9
    0 Votes
    9 Posts
    625 Views
    nickanickN
    @Eric-Katzfey We are experiencing connection issues between VOXL2 and QGC. QGroundControl is showing disconnected after inputting the comms link with 192.168.7.2:14550 in UDP. mavlink_to_gcs and mavlink_from_gcs are both reporting data. voxl-px4 and voxl-mavlink-server are running. voxl-my-ip 192.168.7.2 (usb0)
  • 0 Votes
    2 Posts
    2k Views
    Alex KushleyevA
    @nl_vdi , if you log into developer.modalai.com, you will see the CAD models. the latest model we have is: D0012-4-V3-C28-M36-T7-K0-Starling2-Max-V3-20260317.step [image: 1781036132877-376bf0dd-494a-4bf1-8d92-1b2d91afb83d-image.png]
  • 0 Votes
    34 Posts
    13k Views
    Alex KushleyevA
    @cguzikowski , Sorry for the delay. Regarding the new HW not working, since you have two identical setups, i would recommend swapping components to identify what exactly is not working. This is the most efficient way to diagnose it. From the logs you provided, the ov64b camera is detected and initialized, it seems, but no frames come in, which could be a cabling or interposer issue. I will get back to you with an update on the lens shading tomorrow. Alex
  • Spektrum RC Bind Issues after SDK Update

    Sentinel
    3
    0 Votes
    3 Posts
    2k Views
    J
    So I'm guessing this has to do with the following I noticed in the changelog: 1.7.4 (voxl2_SDK_1.1.3) BSP: add voxl-fysnc-mod kernel module add voxl-gpio-mod kernel module --- GPIO now exporting to /sys/class/gpio convert SE13 from 4W to 2W UART, freeing GPIO36/37 add voxl-platform-mod kernel module --- see /sys/module/voxl_platform_mod/parameters add new target 'M0054-2' support (same rootfs as M0054-1) new kernel new devcfg.mbn In system image 1.7.1 (SDK v1.1.2) on the drone that has no rc issues, recipes-kernel/linux-msm/files/dts/common/m0xxx-modalai-gpio.dtsi has: &soc { b2b_conn_gpio_init { compatible = "modalai,voxl-b2b"; pinctrl-names = "default"; pinctrl-0 = <&tck22912G_ctrl_pin &b2b_pin7 &b2b_pin9 &b2b_pin17 &b2b_pin19 &b2b_pin38 &b2b_pin40 &hs_b2b_pin41 &hs_b2b_pin42 &hs_b2b_pin43 &hs_b2b_pin44 &hs_b2b_pin46 &hs_b2b_pin47 &hs_b2b_pin50 &hs_b2b_pin51 &hs_b2b_pin78 &hs_b2b_pin79 &hs_b2b_pin80 &hs_b2b_pin81 &hs_b2b_pin82 &j10_lvl_shf_ctrl_pin>; status = "ok"; }; rc_in_enable_init { compatible = "modalai,voxl-rc-in"; pinctrl-names = "default"; pinctrl-0 = <&rc_in_3v3_en_pin>; status = "ok"; }; }; In image 1.7.4 (SDK 1.1.3), recipes-kernel/linux-msm/files/dts/common/m0xxx-modalai-gpio.dtsi: &soc { voxl_gpio { compatible = "modalai,voxl-gpio"; pinctrl-names = "default"; pinctrl-0 = <&tck22912G_ctrl_pin &b2b_pin7 &b2b_pin9 &b2b_pin17 &b2b_pin19 &b2b_pin38 &b2b_pin40 &hs_b2b_pin41 &hs_b2b_pin42 &hs_b2b_pin43 &hs_b2b_pin44 &hs_b2b_pin46 &hs_b2b_pin47 &hs_b2b_pin50 &hs_b2b_pin51 &hs_b2b_pin78 &hs_b2b_pin79 &hs_b2b_pin80 &hs_b2b_pin81 &hs_b2b_pin82 &hs_b2b_pin95 &hs_b2b_pin96 &j10_lvl_shf_ctrl_pin &rc_in_3v3_en_pin &ds2_led_red &ds2_led_green &ds2_led_blue &id_som_1 &id_som_2 &id_mai_3 &id_mai_4>; modalai,gpio-init-output-high = <0 1 53 56 57 85 86 87 88 89 124 152 157 159>; modalai,gpio-init-output-low = <36 37 46 54 55 67 82 83 84 131 153 154 155>; modalai,gpio-init-input = <48 49 50 51 52>; status = "ok"; }; voxl_fsync { compatible = "modalai,voxl-fsync"; pinctrl-names = "default"; pinctrl-0 = <&camera_sync_110 &camera_sync_111 &camera_sync_112 &camera_sync_113 &camera_sync_114>; status = "ok"; }; }; And then in image 1.8.06 (SDK v1.6.3) that is on the drone with the bind issues, recipes-kernel/linux-msm/files/dts/common/m0xxx-modalai-gpio.dtsi: &soc { voxl_gpio { compatible = "modalai,voxl-gpio"; pinctrl-names = "default"; pinctrl-0 = <&tck22912G_ctrl_pin &b2b_pin7 &b2b_pin9 &b2b_pin17 &b2b_pin19 &b2b_pin38 &b2b_pin40 &hs_b2b_pin41 &hs_b2b_pin42 &hs_b2b_pin43 &hs_b2b_pin44 &hs_b2b_pin46 &hs_b2b_pin47 &hs_b2b_pin50 &hs_b2b_pin51 &hs_b2b_pin78 &hs_b2b_pin79 &hs_b2b_pin80 &hs_b2b_pin81 &hs_b2b_pin82 &hs_b2b_pin95 &hs_b2b_pin96 &j10_lvl_shf_ctrl_pin &rc_in_3v3_en_pin &ds2_led_red &ds2_led_green &ds2_led_blue &id_som_1 &id_som_2 &id_mai_3 &id_mai_4 &camera_sync_110 &camera_sync_111 &camera_sync_112 &camera_sync_113 &camera_sync_114>; modalai,gpio-init-output-high = <0 1 53 56 57 67 85 86 87 88 89 124 152 157 159>; modalai,gpio-init-output-low = <36 37 54 55 82 83 84 131 153 154 155>; modalai,gpio-init-input = <48 49 50 51 52 110 111 112 113 114>; status = "ok"; }; voxl_fsync { compatible = "modalai,voxl-fsync"; pinctrl-names = "default"; status = "ok"; }; }; So the gpio initialization process changed and rc_in_enable_init was removed between SDK v1.1.2 and v1.1.3, and between SDK v1.1.3 and v1.6.3, GPIO pin 67 got moved from modalai,gpio-init-output-low to modalai,gpio-init-output-high and GPIO pin 46 got removed from modalai,gpio-init-output-low. https://gitlab.com/voxl-public/system-image-build/meta-voxl2-bsp/-/commit/538c324713548174c8c1694680e9cba7f2d47bcb https://gitlab.com/voxl-public/system-image-build/meta-voxl2-bsp/-/commit/ccd3893e062b03d05885da5a279be2f8d2f6c97c Idk which change is responsible for the binding issues. I'd like to avoid flashing v1.1.3 to narrow it down. Can someone explain how the pins are meant to function for my set-up (M0094 + M0054, rc already bound)?
  • GNSS EMI Mitigation Guidelines

    Starling & Starling 2
    7
    1 Votes
    7 Posts
    2k Views
    Alex KushleyevA
    Hi @bschulzhf You need to copy the new sensormodule file with the correct slot id (number at the end) to /usr/lib/camera and (re)move the existing one, so that it does not get picked up by the camera pipeline. Good idea to back up your existing configuration before making changes. Also more general details here : https://docs.modalai.com/configure-cameras/#connect-a-new-camera Alex
  • 0 Votes
    6 Posts
    710 Views
    tomT
    @vmbasvi That appears to be a Microhard modem, not a WiFi dongle.
  • 0 Votes
    3 Posts
    249 Views
    M
    @Alex-Kushleyev At a bare minimum I just need the additional pwn channels to be controlled by joysticks via QGC. They don't need to be connected to PX4/Autopilot at this point. Does this allow for an easier solution? Thanks! Matt
  • Latest SDK versions - How to access?

    VOXL SDK
    3
    0 Votes
    3 Posts
    2k Views
    N
    @tom said in Latest SDK versions - How to access?: https://storage.googleapis.com/platform-beta-releases/voxl2/voxl2_SDK_1.6.4-beta8.tar.gz Thanks @tom !!!
  • 0 Votes
    2 Posts
    102 Views
    Alex KushleyevA
    @j-angel , We had a small batch of color AR0144, but those have run out and due to low demand, we do not have any stock. I would like to clarify something. Motion blur is present when using any camera (global shutter or rolling shutter). Global shutter cameras also have exposure control and long exposure times will cause motion blur. I think what you may be referring to, which is different in rolling shutter cameras (compared to global shutter), is the rolling shutter skew. Rolling shutter cameras use a technique where the start of exposure of each image row is offset slightly, so each row is essentially exposed over a different time frame. The offset is usually very small (4-30 microseconds per line, depends on the camera, mode), but from top to bottom, the rolling shutter effect can add up and be visible when there are moving features in the scene. The fastest rolling shutter camera we have right now is IMX412 and in the 2x2 binning mode, the 1920x1080 resolution, the total frame readout time is 4ms. (https://docs.modalai.com/camera-video/low-latency-video-streaming/#camera-pipeline-latency-in-different-operating-modes). This means that the difference of the center of exposure between the first and last image row is 4ms. Considering the information above, 4ms can seem a lot, but keep in mind that is the time delay across the whole image. depending on the size of features, the rolling shutter effect across a smaller image area will be smaller. Using the height of 1080, we can compute the time offset for each line, 4ms / 1080 ~ 4us. Depending on the size of features that are being tracked, the rolling shutter may not create a lot of local skew. Additionally, the camera timing is deterministic, so it is possible to calculate the time offset of the center of exposure of each line (with respect to the first line). If you want to provide some more details on type of perception, I could provide more guidance. Unfortunately, right now, we do not have a color global shutter camera option. Alex
  • 0 Votes
    6 Posts
    856 Views
    Hector GutierrezH
    @ApoorvThapliyal : the problem (Error message: "set_position_target_local_ned: coordinate frame 0 unsupported") appeared in QGC after updating VOXL SDK from 1.5.0 to 1.6.3. The error blocked me from being able to use QGC to calibrate or arm the drone. Stopping and restarting voxl-vision-hub solved the problem. For now I'm using voxl-vision-hub as it comes on SDK 1.6.3 (no changes yet) and have not made changes to the .conf file (yet).
  • VOXL 2 and WIFI Dongle

    Ask your questions right here!
    2
    0 Votes
    2 Posts
    280 Views
    Alex KushleyevA
    @nickanick , can you please clarify which exact WIFI Dongle you would like to use?