Seeker Factory Reset
Is there any instruction for the factory reset on Seeker?
Yes, depends on what you're trying to reset though. There are several options but before that can you explain your situation that you're having? Might be possible to resolve without a reset.
Thank you for your reply, @Adrian-Hidalgo .
This is the problem.
Did camera-server work before? Trying to grasp why it's not working; what's the history/what were you trying to attempt?
What config of Seeker do you have? Hi-Res, TOF, & Tracking?
@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 + Trackingwith
Just before, I chose
3: Hires + Stereo + Trackingand
voxl-inspect-qviooutputted correct x,y, and z data (in QGC).
Do you think this is the issue only for my Seeker?
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?
As I mentioned, selecting
C3configuration in my Seeker make
voxl-inspect-qviodisplayed correct pose data.
By the way, I am wondering if I can increase the storage size of
/dev/rooton the VOXL. Do you have any idea?
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/rootfor libraries... so I need to increase the size of this.
@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?
I am moving files to
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
sudo ln -s /data/usr/lib /usr/liband '
sudo ln -s /data/usr/lib64 /usr/lib64.
But I see the error
-bash: /bin/resize: No such file or directorywhen I used some ubuntu commands.
Could you please advise me to move these folders into
@VOXL-Flight I'm sorry, but this isn't something that we have ever attempted.
FYI, I just moved
This allowed to have enough space for my work.