Hi @Tejas-Shah . Yes you can. We are using AT10 right now for ouru work.

@scottesicdrone
The problem is because fastboot command needs root to run properly or else it wont detect device in bootloader.

refer this for more info about running it without root.
https://docs.modalai.com/setup-adb/

or simply run install.sh script as root.

Thank you so much for this. This was of great help @Chad-Sweet

This is solved. I'm made to source my_ros_env.sh file everytime before launching the mpa file. But this never used to happen before. Anyway for now its working by sourcing the my_ros_env.sh everytime. Thanks all!

@Dong-Liu yes that's correct. Everytime a master ip or ros ip changes, I make sure to give the corrects IPs in the bachrc file and source it. This is not the issue, but thanks for the suggestion though!

@modaltb @Ed-Sutter @tom @Alex-Gardner anyone?

Can someone help me with this? Thanks!

For some reason, when I do -
roslaunch voxl_mpa_to_ros voxl_mpa_to_ros.launch

it doesn't seem to work fully. Here's the output -

voxl:~$ roslaunch voxl_mpa_to_ros voxl_mpa_to_ros.launch 
... logging to /home/root/.ros/log/7da4c736-3eb2-11ed-b715-18473db1be57/roslaunch-apq8096-3745.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://localhost:57891/

SUMMARY
========

PARAMETERS
 * /rosdistro: indigo
 * /rosversion: 1.11.21

NODES
  /
    voxl_mpa_to_ros_node (voxl_mpa_to_ros/voxl_mpa_to_ros_node)

auto-starting new master
process[master]: started with pid [3764]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 7da4c736-3eb2-11ed-b715-18473db1be57
process[rosout-1]: started with pid [3777]
started core service [/rosout]
process[voxl_mpa_to_ros_node-2]: started with pid [3780]


MPA to ROS app is now running

Found new interface: qvio_overlay
Found new interface: stereo
Found new interface: tracking
Found new interface: imu1
Found new interface: qvio

And it stops after this. When I do rostopic list on the other terminal, it says unable to communicate with the Master. My bashrc file is correct with correct ROS_MASTER_IP and ROS_IP. Even rqt says the same thing. I plan to see the output of the camera in the rqt viewer.

Hi @Vinny @modalab could you confirm this RMA process would be without any cost? Please confirm so that I can begin this immediately.

Thanks @Vinny for your response. But do we have to pay the 100$ amount for diagnostic? Since this is under a 3 month product, I believe I just need to fill up the RMA document and just send the board back, right?

@modalab Okay, but I'm a bit confused here. The Voxl flight deck plus the extension cable plus the hires sensor (M0026) is all new(less than 3 months old). So in the RMA process, do I just need to complete the form and email it and just send the product right? without adding the diagnostic fee in the cart.

Hi @modalab Thanks for your message. I have received one new cable from my previous communication with ModalAI (Since I had ordered 2 cables at the first place). At this point, I'm kinda convinced its not a cable issue. I have replaced cable thrice now, but it's still the same issue. What's even more weird is that, I have a “VOXL only” board with me that I sometimes use if for debugging purposes, and it's working great with this board. I’m able to get the data and also see image stream on rqt. So, this confirms that the cable is not faulty. I also compared the system images of the Voxl flight deck and just the voxl board and they are the same as well i.e 3.3.0. We also have an offshore team working in India who are using same setup (VOXL flight deck + extension cable + M0026 sensor ).

I feel this requires deeper investigation on the voxl side of my board as mentioned by @Vinny . As a matter of fact, even the voxl flight deck that I have is a new one. I'd like to have screen share session and look at this issue together and hopefully we might find a solution there. I already sent an email yesterday regarding the same.

Hi @Vinny , the problem still exists even after trying with a new cable.