Posts made by tom

@tom I just ran the following successfully:

cd voxl-tflite-server
git checkout master
git pull
voxl-docker -i  voxl-cross:V2.7
./install_build_deps.sh qrb5165 sdk-1.4
./build.sh qrb5165
./make_package.sh

here's a snippet

[ 60%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/model_helper/generic_object_detection_model_helper.cpp.o
[ 66%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/model_helper/yolov5_model_helper.cpp.o
[ 73%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/model_helper/posenet_model_helper.cpp.o
[ 80%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/model_helper/yolov8_model_helper.cpp.o
[ 86%] Building C object src/CMakeFiles/voxl-tflite-server.dir/resize.c.o
[ 93%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/utils.cpp.o
[100%] Linking CXX executable voxl-tflite-server
/usr/lib64//libtensorflow-lite.a(nnapi_delegate.cc.o): In function `tflite::delegate::nnapi::NNMemory::NNMemory(NnApi const*, char const*, unsigned long)':
nnapi_delegate.cc:(.text+0xd58): warning: the use of `tmpnam' is dangerous, better use `mkstemp'
[100%] Built target voxl-tflite-server
voxl-cross(2.7):~(master)(0.4.1)$ ls
CHANGELOG         build              include                scripts
CMakeLists.txt    build.sh           install_build_deps.sh  services
LICENSE           clean.sh           make_package.sh        src
README.md         debug_source.sh    misc_files
bash_completions  deploy_to_voxl.sh  pkg
voxl-cross(2.7):~(master)(0.4.1)$ ./make_package.sh 
Package Name:  voxl-tflite-server
version Number:  0.4.1
Consolidate compiler generated dependencies of target voxl-tflite-server
[100%] Built target voxl-tflite-server
Install the project...
-- Install configuration: "DEBUG"
-- Installing: ../pkg/data/usr/bin/voxl-tflite-server
/home/root
starting building Debian Package
dpkg-deb: building package 'voxl-tflite-server' in 'voxl-tflite-server_0.4.1_arm64.deb'.
DONE

@Wondosen You're building voxl-tflite-server which is part of SDK 1.4.4, while calling install_build_deps.sh qrb5165 dev will pull the dependencies for a much newer version of voxl-tflite-server than you're using.

Try running ./install_build_deps.sh qrb5165 sdk-1.4

@Wondosen How are you running ./install_build_deps.sh?

@Muqing-Cao Yes that would work as well

@mkriesel I recommend connecting the drone to QGroundControl and using the spin tool through there to determine correct orientation. voxl-esc spin doesn't take into account anything px4 is doing to determine motor direction so won't be entirely accurate in term of what direction the motor will spin via the flight controller.

@Thomas-Müller you can read up on our "VOA" implementations here: https://docs.modalai.com/voa/

@Muqing-Cao If you don't want a bulky USB hub on there you can use a different add-on board like this one: https://www.modalai.com/products/m0130-3?variant=48186331693360

it has 1 USB 3.0 and 2 USB 2.0 ports

@Thomas-Müller See here for info on connecting an external flight controller to VOXL 2: https://docs.modalai.com/voxl2-external-flight-controller/

@Muqing-Cao On Starling 2 there is likely a wifi dongle in that port

@wilt From the production team, these should work for you: https://www.mcmaster.com/99461A923/

@Muqing-Cao No you'd likely want to use an add-on board, this would be the cheapest option to give you a USB-A connector that you could attach a USB to ethernet adapter: https://www.modalai.com/products/m0141?variant=46829445513520

@Muqing-Cao We haven't used this sensor before but if you use an ethernet to USB adapter, you should be able to get a network connection to the sensor from VOXL 2

@Taylor814 I would recommend starting the RMA process: https://www.modalai.com/pages/rma

@tonygurney See here for adb install instructions and debugging tips:
https://docs.modalai.com/setting-up-adb/#setting-up-adb

The udev rules at the bottom may solve your issue

@greg_s Just pinged our support team, they're taking a look at it now

@Kiazoa-Joao At this point it's probably worth sending it in for an RMA: https://www.modalai.com/pages/rma

@tom Or if you don't want to reset all of them, you can just run voxl-configure-vision-hub factory_enable

@QSL I would run voxl-configure-mpa and it'll reset all config files to default

@greg_s Apologies, correct email is contact@modalai.com or fill out the form here: https://www.modalai.com/pages/contact-us

@Kiazoa-Joao Can you try the following on a native linux system:

sudo dmesg -wH

Power on and plug in m500 via USB

Monitor output from dmesg and post any relevant messages here