Skip to content

VOXL Flight

77 Topics 300 Posts
  • Stereo Cameras Error sending request 11, ErrorCode: -19

    2
    0 Votes
    2 Posts
    830 Views
    wilkinsafW
    My fault. Found a small tear in the ribbon for the stereo cameras RESOLVED
  • 0 Votes
    7 Posts
    2k Views
    m4v3rM
    Hey, just wanted to give an update it looks like the problem was a hardware fault. The behavior stayed the same after detaching the LTE and the setup works on a different VOXL Flight, so yeah...^^ cheers
  • ekf2_aid_mask

    12
    0 Votes
    12 Posts
    3k Views
    ?
    Glad to hear it was a QGC issue - interesting to see that. For the flight core portion of VOXL-Flight: Re-flashing the firmware will bring you back to factory (https://docs.modalai.com/flight-core-firmware/#px4-v111) and after that load parameters from our repo (https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master/). That should do it
  • Solid Red LED

    2
    0 Votes
    2 Posts
    767 Views
    Chad SweetC
    Sorry for the late reply, were you able to fix this? Based on more recent posts maybe reloading the Flight Core Firmware fixed the issue?
  • Land Detector not working after several landings

    5
    0 Votes
    5 Posts
    1k Views
    m4v3rM
    Hey, I played around with them today a bit and found yes, your values did reduce the frequency with which the failure occurred so I'll continue tweaking there, thanks a lot. Actually your link was double-helpful since I was looking for those specific parameters that regard the takeoff for quite some time now as well (without success...) ;D I understand this is actually more closely related to PX4 but I very much appreciate the help anyway. I sincerely don't even remember anymore why yesterday I thought this must somehow boil down to the fact that it's running on the VOXL-Flight hehe.
  • VOXL LOW_FEATURES

    6
    1
    0 Votes
    6 Posts
    1k Views
    Chad SweetC
    Your video points to a bad camera configuration. The tracking camera cannot produce the resolution that VLC is receiving.
  • Can not calibrate, No Mags detected

    5
    1
    0 Votes
    5 Posts
    1k Views
    wilkinsafW
    Yes, I realized I forgot to load the correct .params file before starting calibration. After selecting the one that disables gps and mag I had success. Thank you
  • scipy,opencv python libraries on VOXL

    1
    0 Votes
    1 Posts
    635 Views
    No one has replied
  • GPS/Mag - Connection woes and Firmware versions

    13
    2
    0 Votes
    13 Posts
    3k Views
    m4v3rM
    Hey everyone, just wanted to let you know that my fix got merged into master so it should work for everyone now... I'd have loved to change the title of this to something a little more descriptive but it's too late now I guess. anyway, cheers everyone, happy flying.
  • How to use PCA9685 with voxl

    2
    0 Votes
    2 Posts
    807 Views
    modaltbM
    @SWARNA-MOHAN-CHANDRA-KANTH said in How to use PCA9685 with voxl: PCA9685 Seems like that is an I2C device, you could start looking here at how to control an I2C bus from VOXL: https://docs.modalai.com/voxl-i2c-io/ How are you looking to control this and for what use case? Above assumes you are running the I2C program on the VOXL's processor (not PX4). If using PX4, you'd want to do this in the PX4 firmware instead.
  • Soft-Reboot not working

    3
    0 Votes
    3 Posts
    1k Views
    m4v3rM
    @modaltb said in Soft-Reboot not working: Hi @m4v3r , If you have VOXL connected via ADB and issue a reboot command via QGC, do you lose the ADB connection? Hi, yes if it's rebooted in ADB it's the same behavior. This particular VOXL did live through several crashes and stuff though (I am a test-pilot mainly afterall ... ;D) so it might just be busted. A different one, setup exactly the same, behaves as expected. Thanks for the insight though.
  • IMU selection

    5
    0 Votes
    5 Posts
    1k Views
    m4v3rM
    Computer Vision, of course. =D Since working with the VOXL I already learned RTK, VIO, EKF and so on... but this one escaped me, so thanks haha.^^
  • Hey everyone^^

    4
    1 Votes
    4 Posts
    1k Views
    Adrian HidalgoA
    Welcome aboard Chris! Looking forward to helping out.
  • VOXL can't be forced into fastboot/unbricked

    4
    0 Votes
    4 Posts
    1k Views
    A
    Hey sorry for the late reply but I got it to work after some trial and error, not really sure why it wouldn't work in the first place but maybe I just got the timing way off. Thanks anyway
  • voxl-io & I2C

    5
    0 Votes
    5 Posts
    1k Views
    T
    @modaltb my current cmake without the addition you mentioned: cmake_minimum_required(VERSION 2.8.3) project(powermodule) ## Compile as C++11, supported in ROS Kinetic and newer add_compile_options(-std=c++11) ## Find catkin macros and libraries ## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz) ## is used, also find other catkin packages find_package(catkin REQUIRED COMPONENTS roscpp std_msgs ) ## System dependencies are found with CMake's conventions # find_package(Boost REQUIRED COMPONENTS system) ## Uncomment this if the package has a setup.py. This macro ensures ## modules and global scripts declared therein get installed ## See http://ros.org/doc/api/catkin/html/user_guide/setup_dot_py.html # catkin_python_setup() ################################################ ## Declare ROS messages, services and actions ## ################################################ ## To declare and build messages, services or actions from within this ## package, follow these steps: ## * Let MSG_DEP_SET be the set of packages whose message types you use in ## your messages/services/actions (e.g. std_msgs, actionlib_msgs, ...). ## * In the file package.xml: ## * add a build_depend tag for "message_generation" ## * add a build_depend and a exec_depend tag for each package in MSG_DEP_SET ## * If MSG_DEP_SET isn't empty the following dependency has been pulled in ## but can be declared for certainty nonetheless: ## * add a exec_depend tag for "message_runtime" ## * In this file (CMakeLists.txt): ## * add "message_generation" and every package in MSG_DEP_SET to ## find_package(catkin REQUIRED COMPONENTS ...) ## * add "message_runtime" and every package in MSG_DEP_SET to ## catkin_package(CATKIN_DEPENDS ...) ## * uncomment the add_*_files sections below as needed ## and list every .msg/.srv/.action file to be processed ## * uncomment the generate_messages entry below ## * add every package in MSG_DEP_SET to generate_messages(DEPENDENCIES ...) ## Generate messages in the 'msg' folder # add_message_files( # FILES # Message1.msg # Message2.msg # ) ## Generate services in the 'srv' folder # add_service_files( # FILES # Service1.srv # Service2.srv # ) ## Generate actions in the 'action' folder # add_action_files( # FILES # Action1.action # Action2.action # ) ## Generate added messages and services with any dependencies listed here # generate_messages( # DEPENDENCIES # std_msgs # ) ################################################ ## Declare ROS dynamic reconfigure parameters ## ################################################ ## To declare and build dynamic reconfigure parameters within this ## package, follow these steps: ## * In the file package.xml: ## * add a build_depend and a exec_depend tag for "dynamic_reconfigure" ## * In this file (CMakeLists.txt): ## * add "dynamic_reconfigure" to ## find_package(catkin REQUIRED COMPONENTS ...) ## * uncomment the "generate_dynamic_reconfigure_options" section below ## and list every .cfg file to be processed ## Generate dynamic reconfigure parameters in the 'cfg' folder # generate_dynamic_reconfigure_options( # cfg/DynReconf1.cfg # cfg/DynReconf2.cfg # ) ################################### ## catkin specific configuration ## ################################### ## The catkin_package macro generates cmake config files for your package ## Declare things to be passed to dependent projects ## INCLUDE_DIRS: uncomment this if your package contains header files ## LIBRARIES: libraries you create in this project that dependent projects also need ## CATKIN_DEPENDS: catkin_packages dependent projects also need ## DEPENDS: system dependencies of this project that dependent projects also need catkin_package( #INCLUDE_DIRS ../../include #LIBRARIES powermdole #CATKIN_DEPENDS roscpp std_msgs #DEPENDS system_lib ) ########### ## Build ## ########### # DOESN'T WORK: #FASTRPC_STUB_GEN(../../include/io_rpc.idl) ## Specify additional locations of header files ## Your package locations should be listed before other locations include_directories( # include ${catkin_INCLUDE_DIRS} include ./include /usr/local/include /usr/include ../../include/ ) link_directories( ../../include /include include /usr/local/lib /usr/lib ) ## Declare a C++ library add_library(${PROJECT_NAME} src/${PROJECT_NAME}.cpp ) ## Add cmake target dependencies of the library ## as an example, code may need to be generated before libraries ## either from message generation or dynamic reconfigure # add_dependencies(${PROJECT_NAME} ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS}) ## Declare a C++ executable ## With catkin_make all packages are built within a single CMake context ## The recommended prefix ensures that target names across packages don't collide #add_executable (voxl_i2c ../../include/voxl-i2c.c) #target_link_libraries (voxl_i2c /usr/lib/voxl_io) add_executable(${PROJECT_NAME}_node src/main.cpp src/powermodule.cpp ../../include/colorprinting.cpp ) ## Rename C++ executable without prefix ## The above recommended prefix causes long target names, the following renames the ## target back to the shorter version for ease of user use ## e.g. "rosrun someones_pkg node" instead of "rosrun someones_pkg someones_pkg_node" # set_target_properties(${PROJECT_NAME}_node PROPERTIES OUTPUT_NAME node PREFIX "") ## Add cmake target dependencies of the executable ## same as for the library above #add_dependencies(${PROJECT_NAME}_node ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS}) ## Specify libraries to link a library or executable target against target_link_libraries(${PROJECT_NAME}_node ${catkin_LIBRARIES} /usr/local/lib/ # /usr/lib/aarch64-linux-gnu/libi2c.so #/usr/lib/rfsa/adsp/libio_rpc.so #/usr/lib/rfsa/adsp/libio_rpc_skel.so #/usr/lib/libvoxl_io.so #/usr/lib/libvoxl_io ) ############# ## Install ## ############# # all install targets should use catkin DESTINATION variables # See http://ros.org/doc/api/catkin/html/adv_user_guide/variables.html ## Mark executable scripts (Python etc.) for installation ## in contrast to setup.py, you can choose the destination # install(PROGRAMS # scripts/my_python_script # DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION} # ) ## Mark executables for installation ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_executables.html # install(TARGETS ${PROJECT_NAME}_node # RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION} # ) ## Mark libraries for installation ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_libraries.html # install(TARGETS ${PROJECT_NAME} # ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION} # LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION} # RUNTIME DESTINATION ${CATKIN_GLOBAL_BIN_DESTINATION} # ) ## Mark cpp header files for installation # install(DIRECTORY include/${PROJECT_NAME}/ # DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION} # FILES_MATCHING PATTERN "*.h" # PATTERN ".svn" EXCLUDE # ) ## Mark other files for installation (e.g. launch and bag files, etc.) # install(FILES # # myfile1 # # myfile2 # DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION} # ) ############# ## Testing ## ############# ## Add gtest based cpp test target and link libraries # catkin_add_gtest(${PROJECT_NAME}-test test/test_shutdown.cpp) # if(TARGET ${PROJECT_NAME}-test) # target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME}) # endif() ## Add folders to be run by python nosetests # catkin_add_nosetests(test) I think I need to figure out how I can add the IO correctly inside it. I'll post a new makefile when I did that.
  • Voxl-Flight adb not working but fastboot works

    7
    0 Votes
    7 Posts
    2k Views
    Chad SweetC
    Thanks for reporting! We definitely recommend a 6A regulator like the APM ships with the boards. The board will typically use <2A but there are transient peaks when frequencies are changed and definitely on boot.
  • Alternative voltage/current reading

    4
    0 Votes
    4 Posts
    989 Views
    modaltbM
    I think it's going to be a coding effort on your end to get this going. It's not something that's used out of the box (e.g. route ESC voltage as a battery voltage). My only experience has been when we created our power module driver, here: https://github.com/PX4/PX4-Autopilot/tree/master/src/drivers/power_monitor/voxlpm On the top of my head, you could modify the driver above, instead of querying I2C to our power module, you could just subscribe to your ESC messages in there, and covert that to a power monitor message perhaps! More info: https://docs.px4.io/master/en/config/battery.html