Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support indoor VIO/flow setups #780

Open
julianoes opened this issue Jul 1, 2019 · 5 comments
Open

Support indoor VIO/flow setups #780

julianoes opened this issue Jul 1, 2019 · 5 comments

Comments

@julianoes
Copy link
Collaborator

It would be nice if MAVSDK was compatible with setups without GPS (so no global position) for indoor use based on Flow or VIO localization.

@hamishwillee
Copy link
Collaborator

That would be awesome. I assume we can simulate this already in Gazebo and test where it fails?

@julianoes
Copy link
Collaborator Author

I assume we can simulate this already in Gazebo and test where it fails?

In theory yes. I've never actually been able to use Flow in Gazebo.

@shrit
Copy link
Contributor

shrit commented Jul 2, 2019

@julianoes Yes, I totally agree, since it is not possible to fly it with the actual flying mode.
You have once pointed to me that we need to comments some of these lines to fly without GPS in Gazebo.
It would be also nice if the user can be able to recover the video from the optical flow in real time. In case if we are using a pico quad copter that can not support another camera

Action::Result ActionImpl::arm() const
{
Action::Result ret = arming_allowed();
if (ret != Action::Result::SUCCESS) {
return ret;
}
// Go to LOITER mode first. // For No GPS mode with vision system comment the next 5 lines.
ret = action_result_from_command_result(_parent->set_flight_mode(SystemImpl::FlightMode::HOLD));
if (ret != Action::Result::SUCCESS) {
return ret;
}
MAVLinkCommands::CommandLong command{};
command.command = MAV_CMD_COMPONENT_ARM_DISARM;
command.params.param1 = 1.0f; // arm
command.target_component_id = _parent->get_autopilot_id();
return action_result_from_command_result(_parent->send_command(command));

@hamishwillee
Copy link
Collaborator

It would be also nice if the user can be able to recover the video from the optical flow in real time. In case if we are using a pico quad copter that can not support another camera

I would address that completely separately. But in any case this is only a "MAVLink/MAVSDK" question if the optical flow camera supports the MAVLink Camera API and exposes the video feed via an RTSP stream. Otherwise there is no way for the SDK to know about the output of optical flow.

@hamishwillee
Copy link
Collaborator

I assume we can simulate this already in Gazebo and test where it fails?

In theory yes. I've never actually been able to use Flow in Gazebo.

Fair enough. I'd say getting this working and in CI would be a precondition for doing anything else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants