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

    kiprock

    @kiprock

    2
    Reputation
    14
    Profile views
    38
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    kiprock Unfollow Follow

    Best posts made by kiprock

    • RE: Docker daemon fails to start on voxl
      rm /data/network/files/local-kv.db
      

      did the trick. Thanks for providing that missing piece of data!

      posted in Software Development
      K
      kiprock

    Latest posts made by kiprock

    • RE: Docker daemon fails to start on voxl

      @Eric-Katzfey if you cannot start docker images, you can try the command above to clear them. Good luck.

      posted in Software Development
      K
      kiprock
    • VOXL mainboard appears to be dead

      Hello,

      Yesterday the voxl main board stopped responding. I removed all cameras and devices except for power and cannot get adb shell to respond.

      If I do adb devices, I get a device in the list, but when i try adb shell, I get error, closed.

      I attached the fastboot interface and tried following the unbricking procedure described at https://docs.modalai.com/unbrick-voxl/ but no response.

      posted in Ask your questions right here!
      K
      kiprock
    • RE: Avoidance Question

      Hi @Chad-Sweet it appears that I am on voxl-suite 0.2.0 as indicated above. However, if QGC reports that avoidance system is unavailable and the vehicle will not arm. If I run

      voxl-vision -s
      

      I can see the obstacle debug info on the terminal, also I set

      "en_voa":    true,
      

      Any suggestions as to what I am doing wrong?

      posted in Ask your questions right here!
      K
      kiprock
    • RE: How can I see the apriltag offset in ROS

      That is what I thought. I have not updated the system yet. Please let me know when this update is available!

      posted in Ask your questions right here!
      K
      kiprock
    • RE: How can I see the apriltag offset in ROS

      Thanks, so my question is, if I am running a planner in ROS, and sending out move simple goals to a local coordinate, will the vehicle auto correct it's odometry while flying around? My tests seem to suggest that this would not be the case.

      posted in Ask your questions right here!
      K
      kiprock
    • RE: How can I see the apriltag offset in ROS

      No response. I'll ask a related question... what is the most stable odom topic that is transmitted in MAVROS? /mavros/local_position/odom seems to have a lot of drift.

      posted in Ask your questions right here!
      K
      kiprock
    • RE: Docker daemon fails to start on voxl
      rm /data/network/files/local-kv.db
      

      did the trick. Thanks for providing that missing piece of data!

      posted in Software Development
      K
      kiprock
    • RE: Docker daemon fails to start on voxl

      just looking at the logs, the docker deamon fails here:

      level=fatal msg="Error starting daemon: Error initializing network controller: could not delete the default bridge network: network bridge has active endpoints"
      

      Most forums suggest removing the docker network folder: rm -r /var/lib/docker/network

      I did this but still having issues. Just curious if the modalAI setup stores docker files somewhere else?

      posted in Software Development
      K
      kiprock
    • RE: Docker daemon fails to start on voxl

      I had a battery go pretty low and the system crashed while running mavros in docker last night, after reboot, docker deamon is not responding and I cannot see any images.

      posted in Software Development
      K
      kiprock
    • RE: Docker daemon fails to start on voxl

      Just looking at your script, I realized that modal has it's own docker services.. so perhaps this provides a little more info: I have created a few images from the kinetic image

      yocto:~# systemctl disable docker.service
      yocto:~# systemctl enable docker-start.service
      yocto:~# systemctl enable docker-prepare.service
      yocto:~# systemctl status docker-prepare.service
      ● docker-prepare.service
         Loaded: loaded (/etc/systemd/system/docker-prepare.service; enabled; vendor preset: enabled)
         Active: failed (Result: exit-code) since Thu 1970-01-01 00:00:24 UTC; 51 years 4 months ago
       Main PID: 2352 (code=exited, status=1/FAILURE)
      
      Jan 01 00:00:20 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
      Jan 01 00:00:21 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
      Jan 01 00:00:22 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
      Jan 01 00:00:23 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
      Jan 01 00:00:24 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
      Jan 01 00:00:24 apq8096 docker-prepare.sh[2352]: failed to see cpuset appear after 15 seconds
      Jan 01 00:00:24 apq8096 systemd[1]: docker-prepare.service: Main process exited, code=exited, status=1/FAILURE
      Jan 01 00:00:24 apq8096 systemd[1]: Failed to start docker-prepare.service.
      Jan 01 00:00:24 apq8096 systemd[1]: docker-prepare.service: Unit entered failed state.
      Jan 01 00:00:24 apq8096 systemd[1]: docker-prepare.service: Failed with result 'exit-code'.
      Hint: Some lines were ellipsized, use -l to show in full.
      yocto:~#
      yocto:~#
      yocto:~# systemctl status docker-start.service
      ● docker-start.service
         Loaded: loaded (/etc/systemd/system/docker-start.service; enabled; vendor preset: enabled)
         Active: failed (Result: exit-code) since Thu 2021-05-13 15:57:11 UTC; 3min 11s ago
       Main PID: 3873 (code=exited, status=1/FAILURE)
      
      May 13 15:57:11 apq8096 systemd[1]: Started docker-start.service.
      May 13 15:57:11 apq8096 docker[3873]: time="2021-05-13T15:57:11.453820000Z" level=info msg="API listen on /var/....sock"
      May 13 15:57:11 apq8096 docker[3873]: time="2021-05-13T15:57:11.477567000Z" level=info msg="[graphdriver] using...lay\""
      May 13 15:57:11 apq8096 docker[3873]: time="2021-05-13T15:57:11.527540000Z" level=info msg="Firewalld running: false"
      May 13 15:57:11 apq8096 docker[3873]: time="2021-05-13T15:57:11.595538000Z" level=fatal msg="Error starting dae...oints"
      May 13 15:57:11 apq8096 systemd[1]: docker-start.service: Main process exited, code=exited, status=1/FAILURE
      May 13 15:57:11 apq8096 systemd[1]: docker-start.service: Unit entered failed state.
      May 13 15:57:11 apq8096 systemd[1]: docker-start.service: Failed with result 'exit-code'.
      Hint: Some lines were ellipsized, use -l to show in full.
      yocto:~#
      yocto:~# df
      Filesystem     1K-blocks    Used Available Use% Mounted on
      /dev/root        2837860 1890496    930980  68% /
      devtmpfs         1861956       0   1861956   0% /dev
      tmpfs            1930660       0   1930660   0% /dev/shm
      tmpfs            1930660   17136   1913524   1% /run
      tmpfs            1930660       0   1930660   0% /sys/fs/cgroup
      tmpfs            1930660       4   1930656   1% /var/volatile
      /dev/sda2           2168      80      1964   4% /persist
      /dev/sde12         12016    4184      7508  36% /dsp
      /dev/sda3          58888      40     57568   1% /cache
      /dev/sde11         97232   33616     63616  35% /firmware
      /dev/sda9       15248568 7060916   8171268  47% /data
      tmpfs             386132       0    386132   0% /run/user/0
      
      posted in Software Development
      K
      kiprock