Excellent work on this diagram. I’ve got a few comments:
The “safety sw” is currently disabled in our recommended parameters. The buzzer is optional.
I would recommend supplying power to the Raspberry Pi via one of the auxiliary outputs (shown on page 3 of your slides)
If you are planning to use a pressure sensor for depth, you will need to use the I2C expander that comes with the PixHawk to connect both the pressure sensor and GPS/compass. (Slide 5)
Please let us know if you have any other questions.
I put together the diagram to help address questions we had while trying to interconnect our BlueROV that we are trying to build in a stock Mechanical/Electrical/Software configuration. Your question is funny/ironic as we just noticed this morning that the C2 link between the Raspberry PI and the Pixhawk was missing. As we are still Newbies trying to get our BlueROV up and running.
Perhaps someone from BlueROV can answer your/our question:
We have not been able to determine what the proper connection between the Raspberry Pi2 and Pixhawk is.
Do we connect a USB between a USV connector on the Pi and the micro USB on the Pixhawk? or
Do we use a SPI Connection? or
Something Else?
Please let us know or point us to a link in the BlueRobotics Documentation.
Once Answered, I will update the Block Diagram. Thanks in advance. Paul
I’ve had success with the following approach to linking the RPi2 to the Pixhawk. The only change I made was to drop the +5v line and just run with the Rx, Tx and GND
I updated block diagram using micro usb cable as described by Jacob above. Let me know if you see any other missing connections or errors. Thanks to all Paul
Glad this diagram is helpful. Feel free to edit/add to the the powerpoint file as you work on your BlueROV project. We will do the same and hope others help to contribute as well. We are getting to the software load part of the task now and plan to contribute to that documentation as well as we have questions and move forward.
We worked the past two weeks to consolidate the information on all the new electronics packages, and your powerpoint was incredibly helpful. I edited it for our build and included some extra documentation to help anyone else trying to build the BlueROV with the new software recommendations.
Thanks for all of the updates - you did a great job adding detail, correcting errors, and just cleaning up the crude documentation - we will have to delve into this as it appears you have found some details on the wiring and interconnections that we were not aware of - many thanks.
I added another update (FWIW) with a few slides towards the end documenting a few other items and options:
slide 12 - Lumen Light connections.
slide 13 - OPTION - Use of an Ethernet Breakout / terminal strip to allow removal / replacement of penetrator from endcap without cutting wires. Many versions available on Amazon or Ebay for under $5.
slide 14 - OPTION - Adaptor for USB Connection Between Pixhawk and Pi - looks like this is not needed if connect GPIO rail to Telem port 2 as shown on your slide 2 works well. We found that Coms thru the USB port on side of Pixhawk was unreliable because the connector (even with a right-angle micro-USB)kept impacting the inside of the housing and getting bent. We changed the standoffs on the chassis for the pixhawk (from 25mm(~1-inch) to 7/8-inch) and this reduced the problem and made assy and disassy of the housing easier - less binding.
BTW, Has anyone seen documentation of the HW/SW/interconnection for the new BlueROV2?
This looks fantastic! We are planning to draw a lot from this document to make official diagrams for the ArduSub page. Keep the good work! It’s incredibly helpful.