Seeker Factory Reset

  • Dev Team

    @VOXL-Flight What happens when you restart camera-server?

    systemctl restart voxl-camera-server

    Are all the camera cables in good condition? Intact wires?

    You may also want to re-configuring mpa:

    voxl-configure-mpa -p -f seeker -b blue -c 7 --fc yes

    If it comes down to it, you can flash the Voxl with a system image & Voxl-suite.
    Select wipe & you'll start with a clean slate. Instructions can be found here
    *After flashing you will need to calibrate the cameras, both stereo & tracking: here

  • @Adrian-Hidalgo Thanks for your suggestions that I have already tried.
    Cables and connections are fine.

    What I found just before is cameras were shown up when I did not choose 7: TOF + Stereo + Tracking with voxl-configure-cameras.

    Just before, I chose 3: Hires + Stereo + Tracking and 2) yes_rotate.
    Then voxl-inspect-qvio outputted correct x,y, and z data (in QGC).

    Do you think this is the issue only for my Seeker?

  • Dev Team

    Ah, then you must have the Seeker with the c3 config, Hi-Res, Stereo & Tracking. The Voxl-Cam on the Seeker can have many camera layouts, but generally there's two prominent configs:
    C 3: Hi-Res, Stereo & Tracking
    C 7: TOF, Stereo & Tracking
    Of course the Voxl-Cam can be any of the camera configs listed in the configure cameras.
    So from what I gather C7 config didn't work, but in configure cameras selecting C3 displayed all cameras & QGC had all the correct data. What happened after selecting C3 in configure cameras?

  • @Adrian-Hidalgo
    As I mentioned, selecting C3 configuration in my Seeker make voxl-camera-server work correctly.
    I confirmed voxl-inspect-qvio displayed correct pose data.

    Thanks, though.

    By the way, I am wondering if I can increase the storage size of /dev/root on the VOXL. Do you have any idea?

  • Dev Team

    I'd have to defer you to the software team can answer that specific question, but there is additional 16GB in /data partition

  • @Adrian-Hidalgo Thank you.
    But the target directory is /dev/root for libraries... so I need to increase the size of this.

  • Dev Team

    @VOXL-Flight Unfortunately, the partition sizes are determined by the system image build and that is not something that is public. What library do you need to load that is too large? Is there any way to "slim" it down, like remove debug information? Alternately, can you place it somewhere else in the file system and use an environment variable like LD_LIBRARY_PATH to be able to link with it?

  • @Eric-Katzfey
    I am moving files to /data folder.
    I have

    voxl:/usr$ ls
    aarch64-oe-linux             bin   etc    include  lib64    local  share  tests
    arm-oemllib32-linux-gnueabi  data  games  lib      libexec  sbin   src

    I would like to move lib64 and lib folders to /data/usr and do sudo ln -s /data/usr/lib /usr/lib and 'sudo ln -s /data/usr/lib64 /usr/lib64.
    But I see the error -bash: /bin/resize: No such file or directory when I used some ubuntu commands.

    Could you please advise me to move these folders into /data?

  • Dev Team

    @VOXL-Flight I'm sorry, but this isn't something that we have ever attempted.

  • @Eric-Katzfey
    FYI, I just moved /lib and /usr/lib to /data.
    This allowed to have enough space for my work.

    Thank you.

Log in to reply