Using EC3 connections on my quad was a good idea...except when it applied to the AttoPilot 90A sensor from SparkFun. The goal for adding this sensor to the system was to be able to remove it cleanly if needed. The sensor pcb design was changed (from earlier pics in the Wiki) to provide a clean installation of Dean's connectors. What to do? Adapt and Overcome! Behold my solution!
And from the back of the audience I hear "Yeah? So what?" Well the 'what' is the constant challenge we as hobbyists face to take parts and components from different maunfacturers and adapt them to our uses. Have you read the thread on adding this small part? To save you the trouble of looking for it, HERE. Imagine the confusion on the part of the hobbyist who asked if the sensor should be getting hot enough to melt the solder! Wow. The first task I performed after getting a successful adaptation to EC3 was checking for a direct short of the battery connection - none was found. (whew!!) The second task was to insulate the power connections to ensure a short was not added accidently while in use (or crashed).
The solution? Hot Glue! The low temp variety of hot glue guns is cheap and cheap to use. Both sides were sealed off and then tested for mechanical strength. Next was to integrate it into the quad and set it up via Mission Planner. The above linked instructions worked flawlessly to set up the sensor. There is some confusion if you should subtract the 0.3V from the actual measured output from the PDB to the APM. I subtracted it anyway - the MP prompts said I should even if it is contradicted in the Wiki instructions.
The actual function of the sensor can be seen after the APM is reset. It can also be tested with the CLI under the 'tests -> battery ' command string. NOTE: The CLI prompts you with a "Careful" mesage. THIS MEANS THE MOTORS WILL BEGIN RUNNING! ALL THE MOTORS! I did have my propellors removed prior to making the mod but if you, dear reader, decide to add this and perform the CLI tests.. REMOVE YOUR PROPS.
What you see above is the output of the CLI while the battery test is running. Note that 'Careful' actually blends into the 'Hit Enter to exit' string. When I hit Enter, the screen stopped updating but THE MOTORS CONTINUED TO RUN! I tried various commands from 'exit' to 'Cntr-C' to 'stop battery' all to no avail. The motors stopped spinning when I clicked on the 'Flight Data' icon at the top of the screen. I suspect the command string that is sent to the APM to shift from CLI to Flight Data mode flushed the command registers of the battery test states.
The last part of this tale will be a photo of the AttoPilot sensor as installed on the quad. It is installed prior to the PDB on my system but after the arming plug harness (covered in a previous blog post HERE). Thank you for reading this far and I wish you success should you choose to add this neat device to your system.
Comments
Stephen, Thank you for the pictures. It just goes to show others another way to get the job done.
I initially started to do an installation like yours but making the unit modular won out over making it slim. This quad is my 'starter quad' to gain experience. The next one, currently in construction, will be more refined. In fact with the next quad, 'Q2', I plan to mount the voltage/current sensor on or adjacent the PDB on that section of the frame deck (a larger frame deck that will allow 3DR stack up - pictures coming soon enough).
I like the 3DR PDB. I would like it more if it would allow integration of the AttoPilot module into the PDB. A simple jumper installation if someone did not have the AttoPilot, a simple solder in if they did. Same connector output, blend it into the wiring harness to the APM, fine'!
=-Doug
Instead of using the through holes, you could spit the wire so that half of the strands are one 1 side and half are on the other. Then use heatshrink to cover everything. The hot glue will probably come off eventually. Similar to what I did here, except I didn't use connectors.
Split wire:
Kim, Just above the photo there is a link to the blog post regarding the arming switch.
HERE it is for added convenience.
-=Doug
Crash - It is heavy... duty. ;)
For the benefit of those who may be numerically obsessed.. it weighs just under 11 grams.
The quad, RTF with empty camera mount, is 3.4 lbs, 1.5 kg. Flight/hover time has been at 9 min with a 3S 3200 mAh Eflite 30C battery. See THIS post regarding flight time and modeling information.
As I have stated before, I do not complain about her weight, she does not complain about my flying. :)
Hi, I really like your red on/off switch on the right hand side of the the picture.
Can you take some more photos off it? How did u make it?
Kim
Looks heavy
Dany, Are you are referring to the CLI motor test --> 'setup motors'. That is a great tool for confirming motor connection/dircection.
In my case I was using 'test battery' - something I had not used before. It was a big surprise for all the motors to start up simultaneously. Some form of battery information and not motor function was expected. It makes sense to load the system and monitor/display results.
-=Doug
BTW the motors in CLI motor test will stop when they finish their cycle (each motors will spin a bit in sequence)
When you hit ENTER it will complete the sequence, let it finish (going back to motor 1)
Great write up! thanks
Hello Alex. I initially attempted to have the EC3 connectors in the same plane as the pcb. This would have required longer leads from the EC3 to the pcb and would have worked well with large heatshrink tubing idea.
As with many things, there is usually more than one solution. Thank you for the comment and if you get a chance, add a picture so others could see another way to do it.
-=Doug
-
1
-
2
of 2 Next