|
|
|
need some advice using aiop v1.1 with the gps. loaded arducopter 2.7,
just done calibrate escs,there running in sync but when i lower throttle to min the motors are starting and stopping..just a few seconds at a time.. doing my nut in as to why or how to cure it, simple solution i expect.. |
|
|
|
|
||
|
Quote:
https://www.rcgroups.com/forums/show....php?t=1790506 |
|
|
||
|
|
|
dazza44...
I had the same problem. I noticed it went away when I disconnected the bluetooth. It wasn't the blue tooth causing the problem, but I had 11.1 volts going into the extended power. This is OK to do (but a little risky with over heating the board). I installed a BEC and only put 5 V into the extended power in and the problem went away... Ray |
|
|
|
||
|
Quote:
|
|
|
||
|
||
|
Quote:
what to wear multiwi firmware 2.1 atu ardupirate ...? |
|
|
||
|
|
|
I am almost there to a fully functioning Crius AIOP running MegaPirate v2.8. Here is what I have working so far:
Bluetooth Module 3DR MinimOSD FPV Setup with Go Pro 3 and 600 mw vTx I am looking to get voltages (V, A and RSSI) on the OSD. I bought a 50 Amp Flytron current sensor that I am looking to hook up (Or if there is a plug and play sensor I would get that instead incase this one is tough to install). For the Flytron Sensor: The manual says that it needs to be hooked up through A0 and A1. Not quite sure what to do past connecting deans connectors, and A0/A1. |
|
|
|
||
|
Quote:
1st off - good going on the getting 2.8 up and running - analog ports A1-A5 don't work in 2.7 (A0 does but not the others), and that's where I lost most of my time scanning through the code - trying this trying that. When the pre release came out - current sensing on A1 - suddenly started working. I have a build video I put together - I just have to post it to Youtube, but it's really simple. There are 3 tiny solder pads on the edge of you current sensor but they're not labeled. I can't tell from the photo on Flytron's site which pins are current, ground, voltage, so you'll need to determine that first. On the Attopilot - they're labeled I (current), V (voltage), G (ground - we don't connect ground in these connections to avoid the possibility of a ground loop - might be different for a Flytron though). It should have a datasheet but if it doesn't there's no harm in just soldering a wire connection into each pad and feeding 1 wire at a time into A0 to see what it reports. The analog ports are just to the left of the Serial Ports and labeled A0-A5. V goes into Analog Port A0, I goes into Analog port A1. You'll need to grab one of the micro molex connectors that came with your Crius and rig up 2 wires to a servo connector, or just solder the wires directly into your current sensor if you don't have pin headers. Once you do that - you have take a multimeter and record the exact voltage going from your BEC into your flight controller. You'll need this number to plug into Mission Planner later. Mine was like 4.98 and yes the extra decimals matter. Now here's the hard part. Go into Mission Planner and enable Battery Monitoring. It has list of Current Sensors it supports, but I don't think Flytron is one of them - and that's a problem. Each current sensor has a current offset it uses to calculate the current draw and voltages - the problem is I don't know what they are for yours, or if your current sensor is ratiometric (like an allegro sensor), or if it uses the same scaling method as an Attopilot. I'd say - hook up a wattmeter and get some base line voltages and current draws at say 25% throttle. Then choose the Attopilot 45A current sensor and see what Mission Planner reports at 25% for current and voltage. Once you have those numbers, you can sort of extrapolate what the offsets should be and choose "Other" as a sensor type and just plug in your values. This is the part where you're in undiscovered country - so I'll be eager to see what you come up with. Once you get Mission Planner reporting back the right numbers, everything will just automagically appear in your OSD So let us know how far you get! ps - I have the ATTOPilot connections documented in my wiring diagram...you can compare notes against your current sensor https://www.rcgroups.com/forums/atta...mentid=5386192 |
|
|
Last edited by Mochaboy; Jan 02, 2013 at 11:54 PM.
|
|
|
|
|
Thanks for the reply. I look forward to your setup video!
I was pointed to a thread that had data for the Flytron Sensor setup: https://www.rcgroups.com/forums/show....php?t=1777474 Check out post #6 Looks like some of the hard work might be done already!!! |
|
Last edited by TheDonski; Jan 03, 2013 at 12:12 AM.
|
|
||
|
Quote:
It looks like you'll be plugging these numbers into Mission Planner's Battery Monitoring config tab. VOLT_DIV_RATIO 3.15 CURR_AMP_PER_VOLT 10.0 INPUT_VOLTAGE -> (You need to measure your BEC's input voltage for this number) He chose the Attopilot 50A - but I think you'll have to choose "Other" and just plug in your values manually. |
|
|
||
|
|
|
Hi, I'm trying to get my extend board working and am having some trouble. From what I understand (please correct me if I'm wrong) I need to change the baud rate of the gps that comes with the extend board. To do that I'm using an FTDI usb breakout board to connect to the extend board using the 8 pin connector to wire that came with the AIOP. I have plugged (all from extend to breakout board) ground into ground, 5V into 5V, TX2 into RXI (or 1, can't tell what it says) and RX2 into TX0. My GPS is connected to the GPS antenna port and my breakout board is connected to my computer. The extend board is powered (red and green lights are on) and I have u-center 7.02 open. I have it connected to port 11, but nothing is happening. I have been through all the baud-rates starting with 9600 and even used the autobaud feature. If I missed this info somewhere else in the thread please tell me and sorry for bothering you.
Thanks |
|
|
|
||
|
Quote:
|
|
|
||
|
||
|
Quote:
|
|
|
Last edited by Friman; Jan 03, 2013 at 08:35 AM.
|
|
|
||
|
Quote:
My idea is to have the MinimOSD as the first OSD with the FPV camera attached and then take the output that would normally go to the transmitter from the MinimOSD go to the Super Simple OSD camera input and let it combine the signal with the battery voltages. This way I do not have to deal with current sensors as the OSD from HK just reads two battery voltages. |
|
|
||
Thread Tools | |
Similar Threads | |||||
Category | Thread | Thread Starter | Forum | Replies | Last Post |
Mini-HowTo | Arduino and HobbyKing Multi-Rotor Control Board V3.0 or KKmulticontroller v5.5 | pprioverde | Multirotor Drone Talk | 33 | May 28, 2017 11:40 AM |
Discussion | New updated Crius Multiwii SE flight controller | SGsoar | Multirotor Drone Electronics | 72 | May 15, 2013 08:36 PM |
Sold | One New, one used ArduPilot 2560 APM1.0 Flight Controlls/autopilots | wingspinner | FPV Equipment (FS/W) | 3 | May 28, 2012 12:55 AM |
Question | Quad Build Using HobbyKing Multi-Rotor Control Board V3.0 (Atmega328 PA) | SJackson | Multirotor Drone Talk | 27 | Apr 30, 2012 08:51 PM |