VOXL portal not working
-
@restore You can't use
10.223.0.1as the IP address when configuring the doodle modem, it is reserved. You'll have to choose a different IP on the 10.223 subnet -
@tom I tried the default 10.223.0.100 and 10.223.0.200 and it is has the same result. I get to the same page shown in the image above.
-
@restore Are you able to ssh or ping to the voxl via. the doodle network from your host machine?
Does your host machine have it's own doodle connected?
-
@tom I am able to ssh into VOXL via this IP. I am using the doodle dev board with ethernet to my host machine. I can see the rtsp camera stream, but portal is not working.
We had this working previously before we upgraded to SDK 1.3 (previously on 1.2)
-
@restore What do you see with
journalctl -u voxl-portal?Can you also post the output of
voxl-version? -
voxl2:/$ journalctl -u voxl-portal -- Logs begin at Thu 2023-03-02 12:58:02 UTC, end at Thu 2023-03-02 13:35:18 UT Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 12:58:58 m0054 voxl-portal[1415]: received SIGTERM Mar 02 12:58:58 m0054 voxl-portal[1415]: voxl-portal started up Mar 02 12:58:58 m0054 voxl-portal[1415]: e481 1 mongoose.c:3626:mg_iotest Mar 02 12:58:58 m0054 systemd[1]: Stopping voxl-portal... Mar 02 12:58:58 m0054 systemd[1]: Stopped voxl-portal. Mar 02 12:59:07 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 13:03:04 m0054 voxl-portal[1429]: received SIGTERM Mar 02 13:03:04 m0054 voxl-portal[1429]: voxl-portal started up Mar 02 13:03:04 m0054 voxl-portal[1429]: 4a586 1 mongoose.c:3626:mg_iotest Mar 02 13:03:04 m0054 systemd[1]: Stopping voxl-portal... Mar 02 13:03:04 m0054 systemd[1]: Stopped voxl-portal. Mar 02 13:03:04 m0054 systemd[1]: Started voxl-portal. -- Reboot -- Mar 02 13:03:18 m0054 voxl-portal[1415]: received SIGTERM Mar 02 13:03:18 m0054 voxl-portal[1415]: voxl-portal started up Mar 02 13:03:18 m0054 voxl-portal[1415]: 4dbba 1 mongoose.c:3626:mg_iotest Mar 02 13:03:18 m0054 systemd[1]: Stopping voxl-portal... Mar 02 13:03:18 m0054 systemd[1]: Stopped voxl-portal. Mar 02 13:03:18 m0054 systemd[1]: Started voxl-portal. lines 10-47/47 (END)voxl-version
voxl2:/$ voxl-version -------------------------------------------------------------------------------- system-image: 1.7.8-M0054-14.1a-perf kernel: #1 SMP PREEMPT Fri May 17 23:29:23 UTC 2024 4.19.125 -------------------------------------------------------------------------------- hw platform: M0054 mach.var: 1.0.0 -------------------------------------------------------------------------------- voxl-suite: 1.3.0 -------------------------------------------------------------------------------- Packages: Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-1.3/binary-arm64/ Last Updated: 2023-03-02 12:58:43 WARNING: repo file has changed since last update, packages may have originated from a different repo List: kernel-module-voxl-fsync-mod-4.19.125 1.0-r0 kernel-module-voxl-gpio-mod-4.19.125 1.0-r0 kernel-module-voxl-platform-mod-4.19.125 1.0-r0 libfc-sensor 1.0.7 libmodal-cv 0.5.6 libmodal-exposure 0.1.0 libmodal-journal 0.2.2 libmodal-json 0.4.3 libmodal-pipe 2.10.0 libqrb5165-io 0.4.5 libvoxl-cci-direct 0.2.3 libvoxl-cutils 0.1.1 modalai-slpi 1.1.14 mv-voxl 0.1-r0 qrb5165-bind 0.1-r0 qrb5165-dfs-server 0.2.0 qrb5165-imu-server 1.0.1 qrb5165-rangefinder-server 0.1.3 qrb5165-slpi-test-sig 01-r0 qrb5165-system-tweaks 0.2.6 qrb5165-tflite 2.8.0-2 voxl-bind-spektrum 0.1.1 voxl-camera-calibration 0.5.5 voxl-camera-server 1.9.4 voxl-ceres-solver 2:1.14.0-10 voxl-configurator 0.6.6 voxl-cpu-monitor 0.4.8 voxl-docker-support 1.3.1 voxl-elrs 0.2.0 voxl-esc 1.4.3 voxl-feature-tracker 0.3.10 voxl-flow-server 0.3.6 voxl-fsync-mod 1.0-r0 voxl-gphoto2-server 0.0.10 voxl-gpio-mod 1.0-r0 voxl-jpeg-turbo 2.1.3-5 voxl-lepton-server 1.2.1 voxl-lepton-tracker 0.0.1 voxl-libgphoto2 0.0.4 voxl-libuvc 1.0.7 voxl-logger 0.4.1 voxl-mavcam-manager 0.5.6 voxl-mavlink 0.1.1 voxl-mavlink-server 1.4.1 voxl-modem 1.1.2 voxl-mongoose 7.7.0-1 voxl-mpa-to-ros 0.3.8 voxl-mpa-tools 1.1.6 voxl-neopixel-manager 0.0.3 voxl-open-vins 0.4.11 voxl-open-vins-server 0.2.53 voxl-opencv 4.5.5-2 voxl-platform-mod 1.0-r0 voxl-portal 0.6.6 voxl-px4 1.14.0-2.0.73 voxl-px4-imu-server 0.1.2 voxl-px4-params 0.4.2 voxl-qvio-server 1.0.4 voxl-remote-id 0.0.9 voxl-streamer 0.7.4 voxl-suite 1.3.0 voxl-tag-detector 0.0.4 voxl-tflite-server 0.3.4 voxl-utils 1.4.1 voxl-uvc-server 0.1.7 voxl-vision-hub 1.8.0 voxl-vtx 1.0.2 voxl2-io 0.0.3 voxl2-system-image 1.7.8-r0 voxl2-wlan 1.0-r0 -
@restore Is this a custom drone you've developed or one of you development drones?
-
@tom it is a custom drone
Voxl2 and the 4in1 FPV ESC
-
@restore As a test to try to get you back to a solid starting point, can you try the following:
-
Run
voxl-configure-sku -w -
Select
voxl2-board-only -
Select your camera config, if no cameras select
0 -
Press enter to continue.
-
Run
voxl-configure-mpa -
When the above is finished, reboot drone
This should get you into a known good state, you should be able to access voxl-portal and px4 should be running, you can also try connecting to QGC.
-
-
@tom we tried that and still have the same behavior. Everything seems to run successfully.
-
@restore Hmm that shouldn't be the case, I wonder if there is some sort of corrupted file screwing things up.
Can you run through the SDK installation again but this time use the
./install.sh -woption? This will wipe the entire file system including the/datapartition which is usually untouched.If you have any calibration files in
/datayou'll want to pull them off before flashing -
@tom the full wipe SDK install sorted it out. Thanks
