ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. blue
    3. Posts
    • Profile
    • Following 1
    • Followers 0
    • Topics 10
    • Posts 24
    • Best 0
    • Controversial 0
    • Groups 0

    Posts made by blue

    • RE: VOXL-MAVCAM-MANAGER: how to configure multiple video streams in QGC without entering RTSP URL

      After connecting the VOXL2 Mini to an external flight controller as described here via J10 on VOXL2 Mini, MAVlink data was viewable from a VOXL Flight Core v2.

      We are still having some troubles with viewing the streams, however now the stream/camera names are appearing in QGC with the video feed selector now that the above MAVlink connection has been established.

      It seems like in order to route MAVlink data out of J3 on VOXL2 Mini via USB, we will need to look into MAVrouter or a similar solution. For now we will continue integration via J10.

      Our goal with routing MAVlink data via USB on VOXL2 is to reduce the telem connections required on a flight controller for our product. We would like the ability to run multiple RTSP streams and MAVlink communication via a single USB connection (from J3 on VOXL2 Mini) to an external flight controller.

      Is UART communication via J10 the preferred or only method of communicating with VOXL2 Mini over MAVlink?

      Is there a way to do MAVlink routing with the VOXL SDK as I mentioned, or will this need to be custom implementation?

      If the VOXL2 Mini is receiving MAVlink data via a UART connection from another device, will the VOXL2 Mini forward and receive MAVlink data to/from the MAVlink device through to a Flight Core via the external flight controller connection J10 on VOXL2 Mini?

      Thank you for very much for your time and feedback on this topic.

      posted in VOXL SDK
      blueB
      blue
    • RE: Mount Holes on M0153

      @Vinny Thank you for the file sir.

      The kit ordered is pictured below:

      MDK-M0153.png

      It would be nice to have 1.6mm or larger mount holes on the next rev of the backboard PCBA to interface with the Boson+ directly, without the need for a mounting bracket, if possible. Not a big deal, but it would be convenient.

      posted in Feature Requests
      blueB
      blue
    • RE: VOXL-MAVCAM-MANAGER: how to configure multiple video streams in QGC without entering RTSP URL

      As a follow up here, I was wondering if we have the proper hardware connections to support VOXL-Mavcam-Manager?

      Our hardware setup is as follows: we have a VOXL2 Mini streaming video from the USB port (J3) on VOXL2 Mini to a USB to Ethernet converter connected to QGC.

      We are hoping to utilize VOXL-Mavcam-Manager with just a single connection to the VOXL2 Mini via J3 as described above.

      Would you be able to confirm that we can utilize VOXL-Mavcam-Manager with the above configuration please?

      We are currently getting "nullMsg array" and "ERROR validating mavlink_message_t data received through pipe:...." as shown above in the previous post.

      posted in VOXL SDK
      blueB
      blue
    • RE: Mount Holes on M0153

      @Vinny thank you for the update sir.

      As for the kit it was an MDK-M0153.

      We do have a printer, would you mind sending that over in a .step format when you have the time please?

      posted in Feature Requests
      blueB
      blue
    • RE: VOXL-MAVCAM-MANAGER: how to configure multiple video streams in QGC without entering RTSP URL

      Hello,

      After running voxl-inspect-mavlink hires412_large_encoded with the services running mentioned above we are seeing the following output:

      ERROR validating mavlink_message_t data received through pipe: 56 of 56 packets failed
      last magic number received was 38, expected MAVLINK_STX=253
      ERROR validating mavlink_message_t data received through pipe: read partial packet
      read 1312 bytes, but it should be a multiple of 44
      ERROR validating mavlink_message_t data received through pipe: read partial packet
      read 1272 bytes, but it should be a multiple of 44
      ERROR validating mavlink_message_t data received through pipe: read partial packet
      read 1384 bytes, but it should be a multiple of 44
      ERROR validating mavlink_message_t data received through pipe: read partial packet
      read 1624 bytes, but it should be a multiple of 44
      ERROR validating mavlink_message_t data received through pipe: read partial packet
      read 1704 bytes, but it should be a multiple of 44
      ERROR validating mavlink_message_t data received through pipe: read partial packet
      read 1624 bytes, but it should be a multiple of 44
      

      Any idea of what may be the problem here?

      posted in VOXL SDK
      blueB
      blue
    • RE: Mount Holes on M0153

      @Vinny thank you very much for your prompt reply!

      That drawing you are referencing is the minimum diameter of a 1.6mm thread. 1.2mm is the measurement on the most concave point of the thread.

      The outer dimension for that thread at the most convex point is 1.6mm as shown in the below drawing from FLIR's CAD. For a m1.6 screw to pass through the PCBA and mount to the aluminum Boson housing, the through hole will need to be >1.6mm. I have a Boson unit on my desk and can confirm M0153 cannot mount to the Boson with the current mounting holes of 1.2mm.

      20-Boson Drawing v1.jpg

      Not a big deal, we made a nice lil hat 🎩 for the backboard to hold it in place.

      My feature request would be: Increase the thru holes to 2mm to accommodate for the m1.6 mount hardware.

      Hopefully this is helpful feedback, thank you for your time and great products.

      posted in Feature Requests
      blueB
      blue
    • VOXL-MAVCAM-MANAGER: how to configure multiple video streams in QGC without entering RTSP URL

      Hello,

      Hardware:

      VOXL2 Mini streaming via wired ethernet connection to QGC

      SDK:

      1.3

      Summary:

      We are working on getting multiple RTSP streams to appear on QGC's fly view without the need to enter in different RTSP endpoints manually with the use of VOXL-MAVCAM-MANAGER.

      Currently, the two different streams can be viewed when the RTSP endpoint is manually changed in QGC, however when the RTSP endpoint is blank, the video feed is cut off.

      Services Running:

      voxl-wait-for-fs
      voxl-streamer (RTSP stream 1 on port 8900)
      voxl-streamer-2 (RTSP stream 2 on port 8901)
      voxl-mavlink-server (auto IP set to "true")
      voxl-mavcam-manager (config file has two streams defined with "default_uri" set to IP addresses that are confirmed streaming to those IP addresses)

      Questions:

      Is there an easy way to debug this similar to what this user is doing: https://forum.modalai.com/topic/3666/voxl-mavcam-manager-crashes-on-mav_cmd_video_start_capture-mavlink-command-when-trying-to-record-video?_=1722617227523?

      Do you have any recommendations based on the summary?

      posted in VOXL SDK
      blueB
      blue
    • Mount Holes on M0153

      Hello,

      We are working with your M0153 and it appears that the thru holes on the M0153 are ~1.25mm. For M0153 to mount to a Boson sensor, the corresponding mounting holes are 1.6mm.

      On the next rev, would you be able to increase the mounting holes to 2mm in diameter?

      posted in Feature Requests
      blueB
      blue
    • M0173 Compatibility and Availability

      Hello,

      I just recently reviewed the release notes for VOXL SDK v1.3 and noticed the M0173 PCBA is now supported.

      • Is the M0173 compatible with VOXL 2 Mini at this time or are there plans to support M0173 on VOXL 2 Mini?

      • What is the expected availability of M0173, as well as associated cables and sensors?

      posted in VOXL 2 Mini
      blueB
      blue
    • M0153 and M0162 CAD Files

      Hello @Moderator,

      We are looking for the M0153 and M0162 CAD files and cannot find them in the ModalAI PCB Catalogue.

      Would you be able to add those to the catalogue web page above?

      posted in 3D Models
      blueB
      blue
    • RE: Voxl 2 Mini Static IP

      After having some issues with a static IP on the VOXL2 Mini above it ended up being an issue with being on the wrong subnet for the host computer to communicate.

      We ended up fixing the issue by changing the subnet for the host computer once we changed the IP on the VOXL2 Mini.

      e.g VOXL2 Mini IP of 192.168.144.15 will require a host computer on the same subnet e.g. 192.168.144.98.

      posted in Ask your questions right here!
      blueB
      blue
    • RE: Voxl 2 Mini Static IP

      @tom @wilkinsaf @Moderator I am hoping you can help shed some light on an issue with setting up the VOXL2 Mini with a static IP. I have seen mention of utilizing a customized version of voxl-modem for a static IP so perhaps I am missing something but I have tried every approach to setting a static IP and more than I have ever used with no avail. It seems there is a service that is enabled by default to clear the IP address of the VOXL2 Mini and messes with the routing of the eth0 interface because anything I implement does not function properly. I must be missing something here if you would please enlighten me πŸ™‚

      Goal:
      Set a persistent static IP on VOXL2 Mini that is maintained after reboots and during operation, then access the VOXL2 Mini with an ssh connection via a Ethernet to USB adapter.

      Overview of Approaches:
      -Approach #1: Does NOT Work- Use commands to flush and wipe the eth0 interface and set a new IP as shown below. This works temporarily but is overwritten typically within 30 seconds while running. After a reboot, the IP address defaults back to 169.254.4.1 and VOXL2 Mini cannot be accessed via ssh on eth0.

      -Approach #2: Does NOT Work- Use system.d file to set eth0 interface with a new IP as shown below. This works temporarily but is overwritten typically within 30 seconds while running. After a reboot, the IP address defaults back to 169.254.4.1 and VOXL2 Mini cannot be accessed via ssh on eth0.

      -Approach #3: Does NOT Work- Use bash script to constantly check and set the IP. This works to set the IP but the VOXL2 Mini cannot be accessed via ssh on eth0.


      Approach #1
      Steps to Reproduce:

      1. adb into VOXL2 Mini
      2. Run:
      ip addr flush dev eth0
      ip link set dev eth0 up
      ip addr add 192.168.1.100/255.255.255.0 dev eth0 
      ifconfig
      
      1. Wait 2 minutes and run:
      ifconfig
      

      Actual Result:
      -IP address changes back to 169.254.4.1.
      -Device no longer available via ssh on eth0 at 169.254.4.1.

      Expected Result:
      -IP should not change after being set.


      Approach #2
      Steps to Reproduce:

      1. adb into VOXL2 Mini
      2. Run: sudo mkdir -p /etc/systemd/network
      3. Run: sudo vi /etc/systemd/network/10-eth0-static.network
      4. Add the following to the file created above:
      [Match]
      Name=eth0
      
      [Network]
      Address=192.169.144.15/24
      Gateway=192.169.144.1
      DNS=8.8.8.8
      
      1. Run:
      sudo systemctl restart systemd-networkd
      sudo systemctl enable systemd-networkd
      ip addr show eth0
      sudo systemctl status systemd-networkd
      
      1. Wait 2 minutes and run:
      ifconfig
      

      Actual Result:
      -IP address changes back to 169.254.4.1.
      -Device no longer available via ssh on eth0 at 169.254.4.1.

      Expected Result:
      -IP should not change from 192.169.144.15 after being set.


      Approach #3
      Steps to Reproduce:

      1. adb into VOXL2 Mini
      2. Run:
        vi /usr/local/bin/set-eth-dongle-ip.sh
      3. Add the following to the file created above:
      #!/bin/bash
      
      eth_dongle_interface="eth0" # Replace with your dongle interface name
      ETHERNET_IP="192.168.144.15" # Replace with your desired IP address
      BROADCAST_IP="192.168.144.255" # Replace with the correct broadcast address
      
      while true; do
          if [[ -e "/sys/class/net/$eth_dongle_interface" ]]; then
              eth_dongle_ip=$(ip -4 addr show $eth_dongle_interface | grep -oP '(?<=inet\s)\d+(\.\d+){3}' | head -1)
          else
              eth_dongle_ip=""
          fi
      
          if [[ "$eth_dongle_ip" != "$ETHERNET_IP" && -e "/sys/class/net/$eth_dongle_interface" ]]; then
              echo "Setting IP address to: $ETHERNET_IP"
              ip addr flush dev $eth_dongle_interface
              sleep 1
              ip link set dev $eth_dongle_interface up
              sleep 1
              ip addr add $ETHERNET_IP/24 broadcast $BROADCAST_IP dev $eth_dongle_interface
          fi
          sleep 1
      done
      
      1. make service file executeable, run:
        sudo chmod +x /usr/local/bin/set-eth-dongle-ip.sh
      2. create systemd service file, run:
        vi etc/systemd/system/set-eth-dongle-ip.service
      3. Add the following to the file created above:
      [Unit]
      Description=Set Ethernet Dongle IP Address
      After=network.target
      
      [Service]
      ExecStart=/usr/local/bin/set-eth-dongle-ip.sh
      Restart=always
      User=root
      
      [Install]
      WantedBy=multi-user.target
      
      1. Run:
      #reload the systemd daemon to recognize the new service 
      sudo systemctl daemon-reload
      
      # enable the service so that it runs on boot
      sudo systemctl enable set-eth-dongle-ip.service
      
      # start service immediately
      sudo systemctl start set-eth-dongle-ip.service
      
      # verify service has started properly
      sudo systemctl status set-eth-dongle-ip.service
      
      1. Wait 2 minutes and run:
      ifconfig
      

      Actual Result:
      -IP address changes back to 169.254.4.1.
      -Device no longer available via ssh on eth0 at 169.254.4.1.

      Expected Result:
      IP should not change from 192.169.144.15 after being set.

      posted in Ask your questions right here!
      blueB
      blue
    • RE: M0138: VOXL FPV ESC - No Current Readings When Calibrating

      @Alex-Kushleyev all good to go! Great work on this plotting feature, it is excellent πŸ’―

      VOXL_ESC_M0138_Spin_Test_Results.png

      posted in ESCs
      blueB
      blue
    • RE: M0138: VOXL FPV ESC - No Current Readings When Calibrating

      Hey @Alex-Kushleyev please disregard this. I just read through a post here that mentions the current measurement on the calibration script is not currently working. It also states that M0138 only has current monitoring on id 2

      I will run spin test command below for now to capture current via id 2:

      ./voxl-esc-spin.py --id 2 --power 40 --ramp-time 2.0 --timeout 2.5 --enable-plot 1 --cmd-rate 250
      
      posted in ESCs
      blueB
      blue
    • M0138: VOXL FPV ESC - No Current Readings When Calibrating

      Hello @Alex-Kushleyev I was hoping you could help me figure out why I am not seeing current readings when calibrating the ESC.

      SW Setup:
      FW Build - m0138_1_v0_39_RC11

      HW Setup: Connected directly to J1 on the M0138 ESC with a UART adapter to a PC running Ubuntu 22.04. ESC externally powered by batteries.

      Issue Summary:
      No calibration data is being displayed when running voxl-esc-calibrate.py

      Steps to Reproduce:

      1. Connect M0138 to motors, battery and via J1 to a PC with a UART to USB adapter
      2. Run:
      ./voxl-esc-calibrate.py --id 0 --pwm-min 10 --pwm-max 95
      

      Actual Results:
      No_Current_ESCCalibration.jpg

      Expected Results:

      • My expectation for voxl-esc-calibrate.py would be to output the current data after the calibration test.

      Questions / Comments:

      • I saw some discussion within the forum that for some of the ESCs current sensing is setup for all 4 channels and the output of the current is a total current measurement for all 4 channels. Does the M0138 measure current individually on each channel or as a combined measurement of all 4 channels?
      • As a follow up to the last question, I tried to run calibration on each channel individually and did not see any current readings. Is there a way to run the calibration for all motors at once such as the spin test with running id 255? I attempted to pass this argument and it failed: ./voxl-esc-calibrate.py --id 255 --pwm-min 10 --pwm-max 95
      • Do I need to configure anything in FW to read current?

      Any help would be greatly appreciated!

      posted in ESCs
      blueB
      blue
    • RE: What connector do you use for integrating a peripheral into MAVLink Instance 1 on TELEM 2?

      @Alex-Kushleyev thank you for your response, this answers my question!

      posted in VOXL Flight
      blueB
      blue
    • What connector do you use for integrating a peripheral into MAVLink Instance 1 on TELEM 2?

      Hello,

      Looking through your documentation here I found mention of the following:

      "MAVLink Instance 1
      hard coded to TELEM2 as it’s routed in the PCB, defaulted at 921600 baud in Normal mode
      this is the primary serial interface to communicate with VOXL
      the baud rate and mode are configurable by the user, but recommended to use the defaults"

      **I cannot find mention of TELEM2 in any of the documentation for connectors and see that it is routed on the PCB and is the primary serial interface. What is the correct connector on the VOXL Flight for interfacing with TELEM2? Can any UART work, and if so, how would that connector be defined as the interface to route MAVLink messages? **

      Thank you very much for your time and any help on this matter.

      posted in VOXL Flight
      blueB
      blue
    • RE: Does VOXL Flight Support Express LRS?

      Express LRS does work via the above wiring on VOXL flight after testing πŸ‘ in Q Ground Control

      posted in VOXL Flight
      blueB
      blue
    • RE: 12V Output Option for Power Module v3

      @Vinny thank you so much for the thorough and punctual response!

      I will give this rework a shot per your instruction and report back if I have any issues.

      posted in Power Modules
      blueB
      blue