PX4 / PX4-Autopilot

PX4 Autopilot Software
https://px4.io
BSD 3-Clause "New" or "Revised" License
8.53k stars 13.52k forks source link

Hardware and Sensors #7648

Closed mrpollo closed 6 years ago

mrpollo commented 7 years ago
TSC21 commented 7 years ago

Hi guys. About this me @vilhjalmur89 are going to sync to push a lib to MAVROS that will serve as a bridge between PX4 msgs coming on fast-RTPS and translating them into ROS. This was something that probably pass through you as usually I am not able to attend to the dev meetings at thaf time. Is there someone else I should sync with to get this done? Marcus? Also about MAVROS port to ROS 2.0 - that's also something on the maintainers TODO list.

TSC21 commented 7 years ago

Also to inform that Jaime Losa, eProsima CEO, is aware of this integration effort.

LorenzMeier commented 7 years ago

I've mentioned this a couple times, just making sure it does not drop: I think we should put some effort behind making sure that mavlink-router (serving as bridge to FastRTPS) and mavros can share as much code as possible on the serialisation part. They are doing the same task for much of what they execute and they should base of the same base serialisation library.

TSC21 commented 7 years ago

I agree with you. But talking with the mavlink-router team the answer I got was short and something as close as "we are commited to mavlink-router at the moment". So unless we sync efforts to have a common library for fast-RTPS (that can support both MAVLink and CDR msg translation) to have a common base for both MAVROS and mavlik-router, we are going to end-up having different libraries doing the same. On a purpose-base perspective, it can also make sense as mavlink-router is a more general bridge than MAVROS, which focus on translation for the ROS framework, and based on that perspective @vilhjalmur89 agreed also that MAVROS could have a module implemented (as libmavconn) that could wrap CDR from and to fast-RTPS. Still, the serialization code would be really similar, while the translation would be different. So this is just to let know there's an effort on MAVROS side and mine so this can happen.

PX4BuildBot commented 6 years ago

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

evercltech commented 6 years ago

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its recipients. This is a temporary error. The following address(es) deferred:

ricardo@hotchipsandsalsa.com Domain evercl.com has exceeded the max emails per hour (201/200 (100%)) allowed. Message will be reattempted later

------- This is a copy of the message, including all the headers. ------ Received: from github-smtp2-ext1.iad.github.net ([192.30.252.192]:56691 helo=github-smtp2a-ext-cp1-prd.iad.github.net) by apollo.graphium.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from noreply@github.com) id 1eoU6e-0007id-PI for rr@evercl.com; Wed, 21 Feb 2018 08:06:44 -0500 Date: Wed, 21 Feb 2018 05:04:02 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1519218242; bh=Zx0Q7i+oH3vnxJJjnhNN23C8G2PrSV/oAzzDSPhGXfA=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fnveK5mE5YMBVJE8OXwx3NAFCbG8BToTdZtY8svT8BGB4RW1is/i3pwOv5p7Tm7dn s7wW1HwlbBtZxoeF7fuE++uxyuvYw1XXYkcIhUvrI78u9Vh/PSjDFucZzvGw2WeV8B Ut0ktIx3+KtdPD+JEodCF16ht4GOHuNjRKaVOaMQ= From: PX4 Build Bot notifications@github.com Reply-To: PX4/Firmware reply@reply.github.com To: PX4/Firmware Firmware@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Message-ID: PX4/Firmware/issue/7648/issue_event/1484605266@github.com In-Reply-To: PX4/Firmware/issues/7648@github.com References: PX4/Firmware/issues/7648@github.com Subject: Re: [PX4/Firmware] Hardware and Sensors (#7648) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a8d6e42dbcd6_1ea62af1bf85eec811542d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: PX4BuildBot X-GitHub-Recipient: evercltech X-GitHub-Reason: subscribed List-ID: PX4/Firmware List-Archive: https://github.com/PX4/Firmware List-Post: mailto:reply@reply.github.com List-Unsubscribe: mailto:unsub+00248898b4a9a9735b24dafe71f3a27861bb6ebd93039fae92cf0000000116a5304292a169ce0e8d7bfc@reply.github.com, https://github.com/notifications/unsubscribe/ACSImLDVG1HdDXBB4QlSOujYh-aGAsOdks5tXBRCgaJpZM4OdNY3 X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: rr@evercl.com

----==_mimepart_5a8d6e42dbcd6_1ea62af1bf85eec811542d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #7648.

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/PX4/Firmware/issues/7648#event-1484605266 ----==_mimepart_5a8d6e42dbcd6_1ea62af1bf85eec811542d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #7648.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a8d6e42dbcd6_1ea62af1bf85eec811542d--