Current sensing (safely) for Heavy Octo?

Hi everyone,

I'm building a heavy Octo for aerial photo & video based on the APM2 board + Carbon Core Octocopter1000 with 360 Pano Mount and Mega Radius camera mount.

The power is provided by two Turnigy nano-tech 6000Mah 6C batteries connected to 8 Himodel 40Amp ESCs powering 8 Tiger motor MT3515-15 400Kv motors with Master Airscrew 14x7 3-blade propellers fitted.

The theorical maximum amp draw for each motor is 29Amps making a theorical max Amp draw of 232Amps. I want to measure battery Voltage and current draw but the biggest AttoPilot Current & voltage sensor is rated for 180Amps Max.

I know I'ts impossible or near impossible to go to max Amps with all motors at same time doing AP but given that burning the Attopilot sensor will stop the power feed to the multicopter, and this will result in a more than sure crash, I want to be very conservative and not overload it.

Is there an option to connect two 180Amp sensors to the APM2 board (one on each battery) and get readings?

Two sensors should be capable of handling 360Amps and this would solve my problem.

Other sugestions?

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • jbabio, I  have a heavy Y6 built a few years ago and still in the air.  In my case I have three parallel 5s, 5000mah batteries.  It works for me and my Y6, but I would not recommend three parallel batteries as this creates battery issues you can not anticipate.  Anyway, I use one AttoPilot 180A  sensor attached only to one battery.  In this setup the sensor will report the correct voltage, but reflect an incorrect current.  In mission planner you can set a parameter to adjust Amps per Volt, or amps reported per volt from the sensor.  Using an external battery monitor during flight the external battery monitor will report the max current during the flight, then find the AttoPilot max current recorded in the  telemetry log and calculate a new setting for the Amps/Volt parameter.  Repeat the process until the reported current equals the battery monitor results.  Like I stated, it works in my case, but is not generally recommended as failure of one of the two non-monitored batteries will not be reported to the flight controller, and the voltage of the remaining operative batteries will drop like a rock, faster than the FC can anticipate.

    Also, I have been educated by those knowledgeable that the available current from multiple parallel batteries IS NOT additive, in other words if each battery can supply 100 amps then two batteries DO NOT provide 200 Amps.  My understanding is that this is due to the battery's internal resistance.  In my case I switched form 20C Batteries to 50C Batteries and Im fine.  In my case I have six 50 amp motors for a  theoretical 300Amps, (5S)  I hover at 80 amps and have never seen 200Amps reported.

    On another note:  Check the wicki, I believe I have seen reference to a second battery monitor, However I have not chased down that issue and I don't know how the FC uses the second sensor data.

  • MR60

    I designed with Nick Arsov and sell a hall effect current sensor (up to 200A), up to 8S

    http://www.airbotservices.com/airbotpower.html

    AirbotPower | Drones
  • I also already use mission planner software with my dragon link
  • I was thinking of getting a pixhawks cube but I'm wondering if I can make this dull current sensor thing work with my eagle tree vector too?????
  • How would I then wire that to my osd ? I have a vector eagle tree osd
  • You can just use this:

    http://www.mauch-electronic.com/apps/webstore/products/show/7594449

    with 2 of these:

    http://www.mauch-electronic.com/apps/webstore/products/show/7588549

    and you are good all the way to 400A.

  • my X8 can pull up to 531 amps so can I even use a current sensor?

  • In my case with parallel batterys, I used the Attopilot on only one battery feed.  The voltage is correct, and I adjust the pixhawk parameter to adjust "amps per volt," to compensate for the additional current.  With a little fiddling it seems to work.

    On a similar, related subject, your max current is 200+ amps, so you expect to draw 1/2 that current from each battery?  My situation is similar.  However once in flight I am finding serious voltage lag triggering battery fail safe way to soon.  This indicates I am pulling more current than the battery is capable of delivering.

    I sent a message to the guys at AtomikRC and they responded that the parallel battery arrangement will deliver the current on ONE battery pack, and that with lipo battery you do not get to multiply the current C rating by the number of battery packs.

    I'm doubtful of this response but I suppose that internal balancing of the cells between packs may be using current capacity.  I'm considering a balance cable between the lipo packs.

    Any thoughts?

    • What is the correct way to connect the AttoPilot 180A ground wire without causing a ground loop when using two separately fed 6Ss into a PDB while only sensing one of the packs (I only want to monitor 1 pack)? Pixhawk is powered via the top power port using the original Pixhawk PM via a separate 3S (I’m not running the Pixhawk from the PDB).

       

      I have hit a massive dead end after trawling the forums for hours, help greatly appreciated.

       

      Thanks

  • Warning, using attopilot with draw more than 180 can be dangerous because the power consumation grow wtih square of current :

    P = I² * R

    actual attopilot for 180A :

    180*180*0.00025 = 8.1 watts

    if you draw 272A

    272*272*0.00025 = 18.4 watts

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @TinkerGen_: "The Tinkergen MARK ($199) is my new favorite starter robocar. It’s got everything — computer vision, deep learning, sensor…
yesterday
DIY Robocars via Twitter
yesterday
DIY Robocars via Twitter
RT @roboton_io: Join our FREE Sumo Competition 🤖🏆 👉 https://roboton.io/ranking/vsc2020 #sumo #robot #edtech #competition #games4ed https://t.co/WOx…
Nov 16
DIY Drones via Twitter
First impressions of Tinkergen MARK robocar https://ift.tt/36IeZHc
Nov 16
DIY Robocars via Twitter
Our review of the @TinkerGen_ MARK robocar, which is the best on the market right now https://diyrobocars.com/2020/11/15/first-impressions-of-tinkergen-mark-robocar/ https://t.co/ENIlU5SfZ2
Nov 15
DIY Robocars via Twitter
RT @Ingmar_Stapel: I have now explained the OpenBot project in great detail on my blog with 12 articles step by step. I hope you enjoy read…
Nov 15
DIY Robocars via Twitter
RT @DAVGtech: This is a must attend. Click the link, follow link to read the story, sign up. #chaos2020 #digitalconnection #digitalworld ht…
Nov 15
DIY Robocars via Twitter
RT @a1k0n: Got a new chassis for outdoor races (hobbyking Quantum Vandal) but I totally didn't expect that it might cause problems for my g…
Nov 11
DIY Drones via Twitter
First impressions of the Intel OpenBot https://ift.tt/36qkVV4
Nov 10
DIY Robocars via Twitter
Nov 9
DIY Robocars via Twitter
Excellent use of cardboard instead of 3D printing! https://twitter.com/Ingmar_Stapel/status/1324960595318333441
Nov 7
DIY Robocars via Twitter
RT @chr1sa: We've got a record 50 teams competing in this month's @DIYRobocars @donkey_car virtual AI car race. Starting today at 10:00am…
Nov 7
DIY Robocars via Twitter
Nov 6
DIY Robocars via Twitter
RT @a1k0n: Car's view, using a fisheye camera. The ceiling light tracking algorithm gave me some ideas to improve ConeSLAM, and having grou…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: To get ground truth I measured the rug, found the pixel coordinates of its corners, calibrated my phone camera with my standard…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: @DIYRobocars is back in December, but outside. Time to reinvestigate ConeSLAM! I rigged up a quick and dirty ground-truth captur…
Nov 5
More…