Topics created by nickyblanch

Hi @nickyblanch
Anytime.
yeah, we had quite a bit of cables and mods to get to FCv2, but we think it's worth it, and now much more aligned with Dronecode and present/future hardware we make.
FCv1 was a bit of a anomaly from it's early design inputs and constraints, so we do view FCv2 as much easier now to work with (if you are starting from scratch).

We do have on our roadmap a much more "standard" drone mounting pattern w/o changing any other functions, but that effort keeps moving to the right... haha

@Moderator I see, thank you for the clarification - I think I was confused because I saw the HW info returned Flight Core V2.

I will try to run everything from /data/ , but I was initially worried about path errors because the other ROS packages and Python dependencies appeared to be installed in root. Will update here.

@nickyblanch thank you so much for the great write up!

We accept pull requests if you think there is a bug or worthwhile improvement.

@AP123 Hi, I have not seen this before, but I also haven't tried enabling obstacle avoidance. I can't pretend to know much about the obstacle avoidance code running inn the VOXL SDK, but I suppose this error could be caused by some obstacle avoidance service not running on the VOXL when it should be, hence QGroundcontrol being confused.

@tom Apologies for the delayed response, but I took your suggestion and had better luck on 0.9.5. Thanks!

@Nicolas-Ethan-Blanchard I also re-loaded PX4 parameters from the provided file in the GitLab, so that could have helped as well. Although, I do think that the IMU orientation parameter was set correctly initially, because it matched the parameter in the working drone.