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

Details the mapping between peripherals on Solo #249

Closed
wants to merge 2 commits into from

Conversation

njoubert
Copy link
Contributor

This is crucial information for developers attempting to use the accessory port, such as myself. Details the mapping between serial ports on the accessory port, and the various parameter settings, serial ports, and internal naming schemes of the HAL in Arducopter.

This is crucial information for developers attempting to use the accessory port, such as myself. Details the mapping between serial ports on the accessory port, and the various parameter settings, serial ports, and internal naming schemes of the HAL in Arducopter.
@njoubert
Copy link
Contributor Author

@mrpollo

@mrpollo
Copy link
Contributor

mrpollo commented Dec 29, 2015

hey @liamstask @johnfinley would you guys mind double-checking this is accurate info?

@hamishwillee
Copy link
Contributor

@njoubert Anything else you'd like to see on this page to make the accessory bay easier to use?

@njoubert
Copy link
Contributor Author

@hamishwillee Perfect timing: I'm just writing a post on https://discuss.dronekit.io/c/solo-development

It'd be helpful to include:

  • how the USB ports map to the iMX6 and Pixhawk2
  • over what peripheral does the iMX6 and Pixhawk2 communicate (so that I don't accidentally prevent those from communicating)
  • whether iMX6 comes with FTDI and similar drivers (aka can I plug in an arduino directly? with what cable)
  • current limits on the power pins
  • voltage levels of the serial pins

@njoubert
Copy link
Contributor Author

BTW, here's the documentation I'm putting together for integrating Piksi into Solo: https://github.com/njoubert/spooky#integrating-piksi-with-3dr-solo

@hamishwillee
Copy link
Contributor

Hi @njoubert Thanks! I'd still include all those questions on your solo development post :-) Feel free to cross link here and I'll ask internally if we can get some answers.

@njoubert
Copy link
Contributor Author

Thanks guys!

Also, it's totally great to be able to communicate so easily with you guys, and to be able to send pull requests straight to the dev page!!

@mrpollo
Copy link
Contributor

mrpollo commented Dec 30, 2015

@peterbarker can you review plz?

@hamishwillee
Copy link
Contributor

@njoubert
Copy link
Contributor Author

That's a good answer there, how about we incorporate some of that into the
dev page?

BUT!

  • How do we connect sensors directly to the Pixhawk2? The serial ports are not supported on most solos?

-Niels

On Wed, Dec 30, 2015 at 2:03 PM, Hamish Willee [email protected]
wrote:

FYI Most of the @njoubert https://github.com/njoubert question (#249
(comment)
#249 (comment))
is now answered here:
https://discuss.dronekit.io/t/peripherals-mapping-between-accessory-port-pixhawk2-and-arducopter-parameters-to-connect-secondary-rtk-gps/198/2


Reply to this email directly or view it on GitHub
#249 (comment)
.

@proficnc
Copy link

Serial 2, (telem2) is on the accessory bay of all Solos, it connects directly to the Pixhawk 2

@hamishwillee
Copy link
Contributor

Hi @njoubert

We'll be doing a lot more work on the dev guide in January ... this should all get incorporated then. Those are good questions too - keep posting them on the forums.

@hamishwillee
Copy link
Contributor

@njoubert Should the "Peripheral Mapping" section be underneath the "Accessory Breakout Board" heading? ie isn't it just related to that board?

@njoubert
Copy link
Contributor Author

njoubert commented Jan 5, 2016

There's more to it that just the breakout board - the developer also needs
to understand how the peripherals inside solo talk to each other. If she
doesn't, the developer can easily change the ArduCopter parameters to
disable, say, the Gimbal, without realizing it.

It's also worth it for the large dev community that currently understands
Pixhawk to have an understanding of how Pixhawk is integrated into the rest
of the peripherals on Solo. You really want to capture the strong dev
community around Pixhawk and ArduCopter and make it easy for them to
transition to Solo.

@mrpollo
Copy link
Contributor

mrpollo commented Jan 26, 2016

hey @njoubert can you help us by rebasing your work with the latest changes in master?, we had some problems with our tests before

@falense
Copy link

falense commented Mar 26, 2016

Issue #292 may be related.

@mrpollo
Copy link
Contributor

mrpollo commented Apr 26, 2016

closed in favor of #308

@mrpollo mrpollo closed this Apr 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants