Subcategories

• ---

• VOXL 2 Mini

  VOXL 2 Support Forum

  72 382
  72 Topics

  382 Posts

  A

  Yes, I believe the system image v1.8.08 has all the above changes built applied. Easy way to confirm voxl-camera-server -l and check the printed min gain. it should be 100 not 54. if you see 100, then you have the latest com.quite.tuned.default.bin exposure control improvements should also be in there as of v1.8.05 (com.qti.sensor.ar0144.so). this is harder to test, but sdk 1.6.5 should have the latest. To test, cover up the camera to drive the exposure and gain to the max and then uncover and you should observe smooth transition, no jumps in image brightness. it looks like we are not shipping com.qti.sensormodule.ar0144_fsin_3.bin in the system image right now, but like i mentioned earlier we are moving towards putting the camera drivers into the voxl-camera-server repository.. but for now you will need to manually copy that one. Alex
• VOXL 2

  VOXL 2 Support Forum

  596 3k
  596 Topics

  3k Posts

  Z

  Hello there, @RoyAzriel said: 2d Lidar 50gram above the gps bridge 2 x light ilumination (front, down - we are flying and dark tunnels next to tracking cameras) props guards the are seen by the tracking camera we have added tof camera, moving from C28 to C29 ( currently its not working or wired in sw), we have changed the extrinsix.conf file in /etc/modalai accordingly. all of those changes did not effect our filght and we had good flight with good vio during the flight If the platform we are discussing has this added elements, it is a custom frame. @RoyAzriel said: we are exploting a tunnel for the first time.we use the poshold durung junction turns to hold in place during turbolance. my answer would be we can live with resets assuming we can accumulate the positions for mapping between the resets. Yes, so that is a mapping/loop closure software responsibility, not VIO. @RoyAzriel said: how do we make sure what you are saying is right and we are passing estimates to px4 ? Check your voxl-vision-hub.conf, if en_vio is set to true, it passes to PX4 as external vision estimates. Also rectified by: @RoyAzriel said: HGT_REF=3 //VIO EKF2_EV_QMIN=16 EKF2_EV_CTRL=15 For now, our PX4 flavour doesn't handle VIO resets gracefully always. We currently have overcome this issue by using VFC. Hence, the reason I suggested that you should try to repeat the same maneuver under VFC position. If you have any questions on how to enable VFC, please feel free to ask. @RoyAzriel said: what should I expect ? Likely more robust performance under resets at the potential cost of manually hover thrust, PID/PD tuning. PS: I wanted to try reproducing your setup here with non-modded Starling2 Max, but I am unable to match your setup without logs
• VOXL Flight

  77 300
  77 Topics

  300 Posts

  L

  @LucasW to answer my own question, VOXL supports 5 GHz. This can be verified by running iw list and looking at the supported channels. The /data/misc/wifi/wpa_supplicant.conf file does not seem to take effect when trying to specify frequencies, for instance (for 5 GHz channels 36, 40, 44, and 48: country=ch ctrl_interface=/var/run/wpa_supplicant network={ ssid="my-ssid" bssid=00:00:00:00:00:00 freq_list=5180 5200 5220 5240 scan_freq=5180 5200 5220 5240 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP psk="my-pwd" } The only way I found to connect to 5 GHz is to disable the 2.4 GHz radio entirely on the router. Otherwise, the connection defaults to 2.4 GHz. On the router, it is also better to set a fixed channel (e.g., 36) rather than letting it be automatic. In auto mode, the robots could not connect systematically to the network. Note also that my question was wrong in the sense that the hostapd.conf files are used to generate the access point, not to connect in station mode. These are maybe considerations that could be added to the technical doc @Chad-Sweet ?
• VOXL

  119 560
  119 Topics

  560 Posts

  A

  @qqa , we have document how to achieve folder-level encryption on VOXL2 here : https://docs.modalai.com/enabling-file-encryption/ . Please let us know if you have any other questions.
• Flight Core v2

  42 234
  42 Topics

  234 Posts

  F

  I fix this issue. switch the Pin1 & Pin4 of MCBL-00010 cable is OK
• Flight Core

  36 135
  36 Topics

  135 Posts

  T

  Unbricked! Here's some context/advice for anyone trying to do the same. If you purchased a cheapo STLINK V2 from Amazon as I did. Picture below... [image: 61TfQhFysAL._AC_SX679_.jpg] $0 Fix: What may very well happen to ya, is the RESET pin doesn't work. In this case you will need a friend. With said friend, you must dilligently connect to the board using Under Reset Mode and Hardware Reset. The second your homie clicks the connect button, you, the bricker of the board must move your jumper cable from the RESET pin which is 3.3V to an open Ground, leave it for exactly 1 second, then move it back to RESET. This should work like a charm, but may require one or two tries to get the right timing. See instructions below. [image: raiders.jpg] $10 Fix: Program a Pico/Arduino to do your 1 second ground for you. $78 Fix: Buy the real STLINK V2.
• VOXL 2 IO

  VOXL 2 I/O (M0065) Support

  25 176
  25 Topics

  176 Posts

  L

  @Moderator The description to MCBL-00128 (https://docs.modalai.com/cable-datasheets/#mcbl-00128), the TOF for the Voxl 2 Mini says it's supported with M0188 (https://docs.modalai.com/M0189/) without specifying any sub P/N (-1 or -2), even in the documentation of the M0188 doesn't say anything about P/N -1 or -2 (https://docs.modalai.com/M0188/).
• Flight Core - ArduPilot

  3 12
  3 Topics

  12 Posts

  P

  ok I found the problem... the Cube Serial inteface are driven by TXS0108E Level Shifter powered both side with 3.3 volt making it marginal for the Voxl Primary Serial interface. Switching to secondary interface on the Voxl made it work correctly. I sent a request for a change in the WIKI to reflect that configuration [image: 1682588997181-40f28124-b098-4482-a038-25c450b9df6c-image.png]