ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Dawid Mościcki
    3. Posts
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 30
    • Best 0
    • Controversial 0
    • Groups 0

    Posts made by Dawid Mościcki

    • RE: QGC keeps crashing when sentinel drone is reconnected

      @Zachary-Lowell-0 This could be probably caused by missing sdlog_mode parameter. Maybe it was introduced in one of the commits that modified logger.cpp in src/modules/logger ?

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Sentinel drone AWUS wifi problem

      I reflashed firmware and reconfigured drone manually (not using automatic scripts which platform detection) and problem vanished. Probably there is something wrong with detecting actual drone version in those automated scripts.

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Sentinel drone radio stopped working

      If any1 will have similar problems in future don't follow guide : https://docs.modalai.com/sentinel-user-guide-pre-flight-setup/

      See those docs : https://docs.modalai.com/voxl-elrs/
      All You need to do is voxl-elrs -b, then on aperture go to ExpressLRS and choose bind 🙂

      Can be closed.

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Strange Turbulent Flight Behavior when transitioning into Offboard Mode (Please Help!!)

      In my case similar behavior was fixed by :
      "The thing that is most likely the issue I believe is voxl-vision-hub. There is a program in vision-hub that will automatically do a figure 8 in offboard when it gets kicked off programatically and this is most likely conflicting with your takeoff. The parameters you needs to disable in /etc/modalai/voxl-vision-hub.conf are:

      offboard_mode: off"

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • Sentinel drone radio stopped working

      Hi, I'm using Sentinel drone. For some reason RC apparatus stopped working and i can't bind it again.
      When i'm trying to set up bind mode nothing happens. I was following this guide :
      https://docs.modalai.com/sentinel-user-guide-pre-flight-setup/

      Led is blinking always slowly on blue....

      What can i do about it ?
      I'm using out-of-the-box commando8 (included with Sentinel drone).

      Why this could happen ?

      Thanks for help

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • Sentinel drone voxl qvio server high cpu usage

      For some reason CPU load on qvio-server is very high.

      Output from voxl-inspect-services
      Service Name | Enabled | Running | CPU Usage

      docker-autorun | Disabled | Not Running |
      modallink-relink | Disabled | Not Running |
      voxl-camera-server | Enabled | Running | 71.0%
      voxl-cpu-monitor | Enabled | Running | 0.6%
      voxl-dfs-server | Disabled | Not Running |
      voxl-feature-tracker | Disabled | Not Running |
      voxl-flow-server | Disabled | Not Running |
      voxl-imu-server | Enabled | Running | 5.4%
      voxl-lepton-server | Disabled | Not Running |
      voxl-mavcam-manager | Enabled | Running | 0.0%
      voxl-mavlink-server | Enabled | Running | 3.5%
      voxl-modem | Disabled | Not Running |
      voxl-neopixel-manager | Disabled | Not Running |
      voxl-open-vins-server | Disabled | Not Running |
      voxl-portal | Enabled | Running | 0.2%
      voxl-px4-imu-server | Disabled | Not Running |for some reason CPU load on qvio-server is very high. We also have problem with Alfa wifi modem - every few minutes it's turning off and restarting ... Led isnt blinking for few seconds then network start working again . While this is happening Qgroundcontrol is crashing (as every time when drone is reconnected)

      Output from voxl-inspect-services
      Service Name | Enabled | Running | CPU Usage

      docker-autorun | Disabled | Not Running |
      modallink-relink | Disabled | Not Running |
      voxl-camera-server | Enabled | Running | 71.0%
      voxl-cpu-monitor | Enabled | Running | 0.6%
      voxl-dfs-server | Disabled | Not Running |
      voxl-feature-tracker | Disabled | Not Running |
      voxl-flow-server | Disabled | Not Running |
      voxl-imu-server | Enabled | Running | 5.4%
      voxl-lepton-server | Disabled | Not Running |
      voxl-mavcam-manager | Enabled | Running | 0.0%
      voxl-mavlink-server | Enabled | Running | 3.5%
      voxl-modem | Disabled | Not Running |
      voxl-neopixel-manager | Disabled | Not Running |
      voxl-open-vins-server | Disabled | Not Running |
      voxl-portal | Enabled | Running | 0.2%
      voxl-px4-imu-server | Disabled | Not Running |
      voxl-px4 | Enabled | Running | 57.1%
      voxl-qvio-server | Enabled | Not Running |
      voxl-rangefinder-server | Disabled | Not Running |
      voxl-remote-id | Disabled | Not Running |
      voxl-softap | Enabled | Completed |
      voxl-static-ip | Disabled | Not Running |
      voxl-streamer | Enabled | Running | 0.0%
      voxl-tag-detector | Disabled | Not Running |
      voxl-tflite-server | Disabled | Not Running |
      voxl-time-sync | Disabled | Not Running |
      voxl-uvc-server | Disabled | Not Running |
      voxl-vision-hub | Enabled | Running | 1.9%
      voxl-wait-for-fs | Enabled | Completed |
      voxl-px4 | Enabled | Running | 57.1%
      voxl-qvio-server | Enabled | Not Running |
      voxl-rangefinder-server | Disabled | Not Running |
      voxl-remote-id | Disabled | Not Running |
      voxl-softap | Enabled | Completed |
      voxl-static-ip | Disabled | Not Running |
      voxl-streamer | Enabled | Running | 0.0%
      voxl-tag-detector | Disabled | Not Running |
      voxl-tflite-server | Disabled | Not Running |
      voxl-time-sync | Disabled | Not Running |
      voxl-uvc-server | Disabled | Not Running |
      voxl-vision-hub | Enabled | Running | 1.9%
      voxl-wait-for-fs | Enabled | Completed |

      What can I do in order to debug this issue further ? This wasn't an issue until last week (normally it ran at much lower cpu % usage).

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • Sentinel drone AWUS wifi problem

      Hi, I' using Sentinel drone. Wifi was working very well untill last week. For some reason now it keeps disconnecting every 1-2 minutes.

      Output from journalctl -xe |grep wlan

      Mar 02 13:11:37 m0054 dhcpcd[1694]: wlan0: carrier acquired
      Mar 02 13:11:37 m0054 dhcpcd[1694]: wlan0: IAID ca:b5:ab:b9
      Mar 02 13:11:37 m0054 dhcpcd[1694]: wlan0: adding address fe80::76d9:b52b:91ff:9629
      Mar 02 13:11:37 m0054 dhcpcd[1694]: wlan0: rebinding lease of 192.168.88.243
      Mar 02 13:11:38 m0054 dhcpcd[1694]: wlan0: soliciting an IPv6 router
      Mar 02 13:11:41 m0054 dhcpcd[1694]: wlan0: probing address 192.168.88.243/24
      Mar 02 13:11:46 m0054 dhcpcd[1694]: wlan0: leased 192.168.88.243 for 600 seconds
      Mar 02 13:11:46 m0054 dhcpcd[1694]: wlan0: adding route to 192.168.88.0/24
      Mar 02 13:11:46 m0054 dhcpcd[1694]: wlan0: adding default route via 192.168.88.1
      Mar 02 13:11:51 m0054 dhcpcd[1694]: wlan0: no IPv6 Routers available
      Mar 02 13:12:28 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:fd:74:f3:01:e1 reason=0 locally_generated=1
      Mar 02 13:12:28 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
      Mar 02 13:12:28 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
      Mar 02 13:12:28 m0054 dhcpcd[1694]: wlan0: carrier lost
      Mar 02 13:12:29 m0054 dhcpcd[1694]: wlan0: deleting address fe80::76d9:b52b:91ff:9629
      Mar 02 13:12:29 m0054 dhcpcd[1694]: wlan0: deleting default route via 192.168.88.1
      Mar 02 13:12:29 m0054 dhcpcd[1694]: wlan0: deleting route to 192.168.88.0/24
      Mar 02 13:12:32 m0054 wpa_supplicant[2278]: wlan0: Trying to associate with 18:fd:74:f3:01:e1 (SSID='autonomy_lab' freq=2452 MHz)
      Mar 02 13:12:32 m0054 wpa_supplicant[2278]: wlan0: Associated with 18:fd:74:f3:01:e1
      Mar 02 13:12:32 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
      Mar 02 13:12:33 m0054 wpa_supplicant[2278]: wlan0: WPA: Key negotiation completed with 18:fd:74:f3:01:e1 [PTK=CCMP GTK=CCMP]
      Mar 02 13:12:33 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:fd:74:f3:01:e1 completed [id=0 id_str=]
      Mar 02 13:12:33 m0054 dhcpcd[1694]: wlan0: carrier acquired
      Mar 02 13:12:33 m0054 dhcpcd[1694]: wlan0: IAID ca:b5:ab:b9
      Mar 02 13:12:33 m0054 dhcpcd[1694]: wlan0: adding address fe80::76d9:b52b:91ff:9629
      Mar 02 13:12:33 m0054 dhcpcd[1694]: wlan0: soliciting an IPv6 router
      Mar 02 13:12:34 m0054 dhcpcd[1694]: wlan0: rebinding lease of 192.168.88.243
      Mar 02 13:12:39 m0054 dhcpcd[1694]: wlan0: probing address 192.168.88.243/24
      Mar 02 13:12:44 m0054 dhcpcd[1694]: wlan0: leased 192.168.88.243 for 600 seconds
      Mar 02 13:12:44 m0054 dhcpcd[1694]: wlan0: adding route to 192.168.88.0/24
      Mar 02 13:12:44 m0054 dhcpcd[1694]: wlan0: adding default route via 192.168.88.1
      Mar 02 13:12:46 m0054 dhcpcd[1694]: wlan0: no IPv6 Routers available
      Mar 02 13:13:34 m0054 dhcpcd[1694]: wlan0: carrier lost
      Mar 02 13:13:34 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:fd:74:f3:01:e1 reason=0 locally_generated=1
      Mar 02 13:13:34 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
      Mar 02 13:13:34 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
      Mar 02 13:13:34 m0054 dhcpcd[1694]: wlan0: deleting address fe80::76d9:b52b:91ff:9629
      Mar 02 13:13:34 m0054 dhcpcd[1694]: wlan0: deleting default route via 192.168.88.1
      Mar 02 13:13:34 m0054 dhcpcd[1694]: wlan0: deleting route to 192.168.88.0/24
      Mar 02 13:13:38 m0054 wpa_supplicant[2278]: wlan0: Trying to associate with 18:fd:74:f3:01:e1 (SSID='autonomy_lab' freq=2452 MHz)
      Mar 02 13:13:38 m0054 wpa_supplicant[2278]: wlan0: Associated with 18:fd:74:f3:01:e1
      Mar 02 13:13:38 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
      Mar 02 13:13:39 m0054 wpa_supplicant[2278]: wlan0: WPA: Key negotiation completed with 18:fd:74:f3:01:e1 [PTK=CCMP GTK=CCMP]
      Mar 02 13:13:39 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:fd:74:f3:01:e1 completed [id=0 id_str=]
      Mar 02 13:13:39 m0054 dhcpcd[1694]: wlan0: carrier acquired
      Mar 02 13:13:39 m0054 dhcpcd[1694]: wlan0: IAID ca:b5:ab:b9
      Mar 02 13:13:39 m0054 dhcpcd[1694]: wlan0: adding address fe80::76d9:b52b:91ff:9629
      Mar 02 13:13:39 m0054 dhcpcd[1694]: wlan0: soliciting an IPv6 router
      Mar 02 13:13:40 m0054 dhcpcd[1694]: wlan0: rebinding lease of 192.168.88.243
      Mar 02 13:13:43 m0054 dhcpcd[1694]: wlan0: probing address 192.168.88.243/24
      Mar 02 13:13:48 m0054 dhcpcd[1694]: wlan0: leased 192.168.88.243 for 600 seconds
      Mar 02 13:13:48 m0054 dhcpcd[1694]: wlan0: adding route to 192.168.88.0/24
      Mar 02 13:13:48 m0054 dhcpcd[1694]: wlan0: adding default route via 192.168.88.1
      Mar 02 13:13:53 m0054 dhcpcd[1694]: wlan0: no IPv6 Routers available

      Could You please provide help ? I have no idea how to fix this issue. This issue keeps happening even when drone is stationary on ground.

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      I will close this ticket and make a new ones. This conversations is too long, sorry for that 😕 Thanks for help so far !

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • QGC keeps crashing when sentinel drone is reconnected

      Hi, Im using sentinel drone.
      When drone is connected for the first time to QGC everything works. After lost of signal and reconnection or just powering off drone then powering up QGC is crashing.

      Output :
      Settings location "/home/autonomylab/.config/QGroundControl.org/QGroundControl.ini" Is writable?: true
      Filter rules "*Log.debug=false\nGStreamerAPILog.debug=true\nqt.qml.connections=false"
      System reported locale: QLocale(English, Latin, United States) ; Name "en_US" ; Preffered (used in maps): "en-US"
      MAVLinkLogManagerLog: MAVLink logs directory: "/home/autonomylab/Documents/QGroundControl/Logs"
      Map Cache in: "/home/autonomylab/.cache/QGCMapCache300" / "qgcMapCache.db"
      qml: QGCCorePlugin(0x5559f952fc80) []
      setCurrentPlanViewSeqNum
      setCurrentPlanViewSeqNum
      _recalcFlightPathSegments homePositionValid false
      _recalcFlightPathSegments homePositionValid false
      "v4.3.0"
      Adding target QHostAddress("192.168.88.243") 14550
      _recalcFlightPathSegments homePositionValid false
      setCurrentPlanViewSeqNum
      setCurrentPlanViewSeqNum
      _recalcFlightPathSegments homePositionValid false
      _recalcFlightPathSegments homePositionValid false
      ParameterManagerLog: Attemping load from cache
      ParameterManagerLog: Parameters cache match failed /home/autonomylab/.config/QGroundControl.org/ParamCache/1_1.v2
      QCoreApplication::postEvent: Unexpected null receiver
      setCurrentPlanViewSeqNum
      setCurrentPlanViewSeqNum
      _recalcFlightPathSegments homePositionValid false
      _recalcFlightPathSegments homePositionValid false
      _recalcFlightPathSegments homePositionValid false
      VideoReceiverLog: Stop called on empty URI
      corrupted size vs. prev_size while consolidating
      Aborted (core dumped)

      In my other project this type is behavior was caused by my custom px4 module with new set of parameters. Maybe it's possible in Your software as well?

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      this is output from journalctl :

      Mar 02 13:11:37 m0054 dhcpcd[1694]: wlan0: carrier acquired
      Mar 02 13:11:37 m0054 dhcpcd[1694]: wlan0: IAID ca:b5:ab:b9
      Mar 02 13:11:37 m0054 dhcpcd[1694]: wlan0: adding address fe80::76d9:b52b:91ff:9629
      Mar 02 13:11:37 m0054 dhcpcd[1694]: wlan0: rebinding lease of 192.168.88.243
      Mar 02 13:11:38 m0054 dhcpcd[1694]: wlan0: soliciting an IPv6 router
      Mar 02 13:11:41 m0054 dhcpcd[1694]: wlan0: probing address 192.168.88.243/24
      Mar 02 13:11:46 m0054 dhcpcd[1694]: wlan0: leased 192.168.88.243 for 600 seconds
      Mar 02 13:11:46 m0054 dhcpcd[1694]: wlan0: adding route to 192.168.88.0/24
      Mar 02 13:11:46 m0054 dhcpcd[1694]: wlan0: adding default route via 192.168.88.1
      Mar 02 13:11:51 m0054 dhcpcd[1694]: wlan0: no IPv6 Routers available
      Mar 02 13:12:28 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:fd:74:f3:01:e1 reason=0 locally_generated=1
      Mar 02 13:12:28 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
      Mar 02 13:12:28 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
      Mar 02 13:12:28 m0054 dhcpcd[1694]: wlan0: carrier lost
      Mar 02 13:12:29 m0054 dhcpcd[1694]: wlan0: deleting address fe80::76d9:b52b:91ff:9629
      Mar 02 13:12:29 m0054 dhcpcd[1694]: wlan0: deleting default route via 192.168.88.1
      Mar 02 13:12:29 m0054 dhcpcd[1694]: wlan0: deleting route to 192.168.88.0/24
      Mar 02 13:12:32 m0054 wpa_supplicant[2278]: wlan0: Trying to associate with 18:fd:74:f3:01:e1 (SSID='autonomy_lab' freq=2452 MHz)
      Mar 02 13:12:32 m0054 wpa_supplicant[2278]: wlan0: Associated with 18:fd:74:f3:01:e1
      Mar 02 13:12:32 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
      Mar 02 13:12:33 m0054 wpa_supplicant[2278]: wlan0: WPA: Key negotiation completed with 18:fd:74:f3:01:e1 [PTK=CCMP GTK=CCMP]
      Mar 02 13:12:33 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:fd:74:f3:01:e1 completed [id=0 id_str=]
      Mar 02 13:12:33 m0054 dhcpcd[1694]: wlan0: carrier acquired
      Mar 02 13:12:33 m0054 dhcpcd[1694]: wlan0: IAID ca:b5:ab:b9
      Mar 02 13:12:33 m0054 dhcpcd[1694]: wlan0: adding address fe80::76d9:b52b:91ff:9629
      Mar 02 13:12:33 m0054 dhcpcd[1694]: wlan0: soliciting an IPv6 router
      Mar 02 13:12:34 m0054 dhcpcd[1694]: wlan0: rebinding lease of 192.168.88.243
      Mar 02 13:12:39 m0054 dhcpcd[1694]: wlan0: probing address 192.168.88.243/24
      Mar 02 13:12:44 m0054 dhcpcd[1694]: wlan0: leased 192.168.88.243 for 600 seconds
      Mar 02 13:12:44 m0054 dhcpcd[1694]: wlan0: adding route to 192.168.88.0/24
      Mar 02 13:12:44 m0054 dhcpcd[1694]: wlan0: adding default route via 192.168.88.1
      Mar 02 13:12:46 m0054 dhcpcd[1694]: wlan0: no IPv6 Routers available
      Mar 02 13:13:34 m0054 dhcpcd[1694]: wlan0: carrier lost
      Mar 02 13:13:34 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:fd:74:f3:01:e1 reason=0 locally_generated=1
      Mar 02 13:13:34 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
      Mar 02 13:13:34 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
      Mar 02 13:13:34 m0054 dhcpcd[1694]: wlan0: deleting address fe80::76d9:b52b:91ff:9629
      Mar 02 13:13:34 m0054 dhcpcd[1694]: wlan0: deleting default route via 192.168.88.1
      Mar 02 13:13:34 m0054 dhcpcd[1694]: wlan0: deleting route to 192.168.88.0/24
      Mar 02 13:13:38 m0054 wpa_supplicant[2278]: wlan0: Trying to associate with 18:fd:74:f3:01:e1 (SSID='autonomy_lab' freq=2452 MHz)
      Mar 02 13:13:38 m0054 wpa_supplicant[2278]: wlan0: Associated with 18:fd:74:f3:01:e1
      Mar 02 13:13:38 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
      Mar 02 13:13:39 m0054 wpa_supplicant[2278]: wlan0: WPA: Key negotiation completed with 18:fd:74:f3:01:e1 [PTK=CCMP GTK=CCMP]
      Mar 02 13:13:39 m0054 wpa_supplicant[2278]: wlan0: CTRL-EVENT-CONNECTED - Connection to 18:fd:74:f3:01:e1 completed [id=0 id_str=]
      Mar 02 13:13:39 m0054 dhcpcd[1694]: wlan0: carrier acquired
      Mar 02 13:13:39 m0054 dhcpcd[1694]: wlan0: IAID ca:b5:ab:b9
      Mar 02 13:13:39 m0054 dhcpcd[1694]: wlan0: adding address fe80::76d9:b52b:91ff:9629
      Mar 02 13:13:39 m0054 dhcpcd[1694]: wlan0: soliciting an IPv6 router
      Mar 02 13:13:40 m0054 dhcpcd[1694]: wlan0: rebinding lease of 192.168.88.243
      Mar 02 13:13:43 m0054 dhcpcd[1694]: wlan0: probing address 192.168.88.243/24
      Mar 02 13:13:48 m0054 dhcpcd[1694]: wlan0: leased 192.168.88.243 for 600 seconds
      Mar 02 13:13:48 m0054 dhcpcd[1694]: wlan0: adding route to 192.168.88.0/24
      Mar 02 13:13:48 m0054 dhcpcd[1694]: wlan0: adding default route via 192.168.88.1
      Mar 02 13:13:53 m0054 dhcpcd[1694]: wlan0: no IPv6 Routers available

      Idk wifi keeps disconnecting. Could You please help me ? And every time when wifi is disconnecting and connecting again, QGC is crashing 😕 This behavior could be caused by px4 modules shipped with Your forked version of px4 ...

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @Alex-Kushleyev for some reason CPU load on qvio-server is very high. We also have problem with Alfa wifi modem - every few minutes it's turning off and restarting ... Led isnt blinking for few seconds then network start working again . While this is happening Qgroundcontrol is crashing (as every time when drone is reconnected)

      Output from voxl-inspect-services

      Service Name | Enabled | Running | CPU Usage

      docker-autorun | Disabled | Not Running |
      modallink-relink | Disabled | Not Running |
      voxl-camera-server | Enabled | Running | 71.0%
      voxl-cpu-monitor | Enabled | Running | 0.6%
      voxl-dfs-server | Disabled | Not Running |
      voxl-feature-tracker | Disabled | Not Running |
      voxl-flow-server | Disabled | Not Running |
      voxl-imu-server | Enabled | Running | 5.4%
      voxl-lepton-server | Disabled | Not Running |
      voxl-mavcam-manager | Enabled | Running | 0.0%
      voxl-mavlink-server | Enabled | Running | 3.5%
      voxl-modem | Disabled | Not Running |
      voxl-neopixel-manager | Disabled | Not Running |
      voxl-open-vins-server | Disabled | Not Running |
      voxl-portal | Enabled | Running | 0.2%
      voxl-px4-imu-server | Disabled | Not Running |
      voxl-px4 | Enabled | Running | 57.1%
      voxl-qvio-server | Enabled | Not Running |
      voxl-rangefinder-server | Disabled | Not Running |
      voxl-remote-id | Disabled | Not Running |
      voxl-softap | Enabled | Completed |
      voxl-static-ip | Disabled | Not Running |
      voxl-streamer | Enabled | Running | 0.0%
      voxl-tag-detector | Disabled | Not Running |
      voxl-tflite-server | Disabled | Not Running |
      voxl-time-sync | Disabled | Not Running |
      voxl-uvc-server | Disabled | Not Running |
      voxl-vision-hub | Enabled | Running | 1.9%
      voxl-wait-for-fs | Enabled | Completed |

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @Alex-Kushleyev Thanks for help, after changing propellers everything seems to work normal, but somehow RC apparatus stopped working. When i'm trying to set up bind mode nothing happens. I was following this guide :
      https://docs.modalai.com/sentinel-user-guide-pre-flight-setup/

      Led is blinking always slowly on blue....

      What can i do about it ?

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @tom this is my dump from /data folder : https://drive.google.com/drive/folders/1ZJXCvCcAg81zJolngtlS-Y_re2BjY2pz?usp=sharing

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @tom this is my second try https://review.px4.io/plot_app?log=cba05321-9bb5-42f2-a766-ecfa6ee01f80

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @Dawid-Mościcki after importing parameters for vio-indoor without gps from https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/master/params/v1.14/EKF2_helpers/indoor_vio_missing_gps.params

      i only armed vehicle to see vibrations : https://review.px4.io/plot_app?log=c70ab712-72c1-4abf-b954-edda6316bf05

      What could I do next ?

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @tom i created backup from /data folder on my pc, but i don't know if this could be helpful

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @tom after flashing, i've got problem with calibrating IMU, btw should 2 imu be present ? because i can see only one :
      voxl-calibrate-imu-temp
      voxl-imu-server currently has no calibration file
      Server has IMU0 enabled and available for temperature calibration
      WARNING, voxl-fan utility missing, can't turn on fan

      ============================================================================
      We're now starting the COLD stage of the calibration.
      Please stop all unnecessary services in another terminal, and try your best
      to cool the PCB with a fan. Alternatively, start this process on a cold PCB.

      We will be measuring the static gyro and accel offset as the board heats up.
      VOXL must remain completely still through this entire process!
      The IMU temperatures will be printed here continuously.

      Press ENTER to start the heating process when you are happy that the IMUs
      are cold enough for the lower bound. 25-35C is a reasonable goal for this.

      CPU: 36.3C IMU0: 30.4C ^M
      WARNING, voxl-fan utility missing, can't turn off fan

      ============================================================================
      We're now starting the HOT stage of the calibration. We just turned off
      the fan, and started stressing the CPU to heat up the PCB.
      This will run automatically for a while collecting data points until enough
      data has been collected, something gets too hot, or the timeout is reached.

      CPU: 57.1C IMU0: 34.9C all imus reached steady state, finishing test
      taking sample #2
      not enough samples, need at least 3

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @Zachary-Lowell-0 what do You mean by SDK ? Is this guide that i should follow, but without full wipe ? https://docs.modalai.com/sentinel-factory-reset/

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @Dawid-Mościcki i don't even know how's that possible https://review.px4.io/plot_app?log=973783b8-6262-46e3-8214-602dce495131
      look at actuator FFT

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki
    • RE: Position mode works, but offboard mode don't

      @Dawid-Mościcki Any 3D files for this drone are available for download ? For example landing skid ?

      posted in Ask your questions right here!
      Dawid MościckiD
      Dawid Mościcki