Recent content by VCD

you can replace the cells, og get a BMSOne and fly with any normal 4S battery

Do you mean the iactual mages, (no - unless you do some programming) - or the FPV video from HDMI (yes) ?

you may be right, I do not remember the result, but there was a good amount of unused energy left when the cells reached the lowest voltage I aimed at, and reducing the current per cell might enable the use of that. - it's just a thought unless somebody has some data on that.

I can consistently get 22m (with gimbal and gopro) using 4S3P Li-ION made of Samsung INR30Q Sanyo 18650GA I suspect adding 4 more cells would help by reducing the load per cell. 20min of so with Tattu 5200mAh Did anyone try 7-9Ah packs?

@5r49 the BMS inside Solo batteries seems to update it's capacity when reaching a certain low voltage - it should not bounce the SoC back up. Can you post the dataflash-log from the Solo? - or even the .tlog ?

yes, the closest to a replacement is BMSOne and a Tattu battery (or any suitable Li-Ion or Li-Po battery.) - but then you can fly with "any" type of battery. (no longer limited to a battery made for Solo)

@5r49cfu So your battery is a bit degraded already, you may expect the Act.C to drop further over time. As it does, you will usually observe that the 25..0 State-of-charge percents drops off faster than expected (the curve is logarithmic) @SKuhn68 Yes, and no, the internal resistance is a...

With the said madhacker tool: if you started out with a fully charged battery - then flew it down to 10-20% SoC - the battery's BMS would update it's actual capacity. Then you connect the madhacker tool - and read out Act.Cap (Actual Capacity) - The battery's design capacity is 5.2Ah , if you...

If I connect mavproxy to the UDP stream from the controller, with --mav10 (to force MAVLink 1.0) - all works fine. If I let QGC or APMPlanner2 connect from the same computer, recieve telemetry (and occasionally updated params) - but they can't send commands to arducopter (set mode etc) or...

The Controllers haptic feedback confirms the input, but monitoring RC_CHANNELS.chan7 shows no change. AP4.0.3 params.zip What could be a possible reason for this ? Please note that I am NOT asking for servo connection. The intention is to toggle precision landing by RC7_OPTION=39

That is possible if the Controller/IMX6 on board does not recognize the firmware or maybe even MAVlink version 2 Me sure to install OpenSolo 4 on both

Also verified: This gimbal behaves well in a Solo, Another 3DR gimbal acts the same way. (so it is NOT the gimbal) Tested with AC4.0.3 and AC4.0.5 - I have attached parameters. MNT_TYPE is 2 (Solo Gimbal) - if set to 0 , then the Gimbal will not misbehave (nor be fully usable)...

I attached 3DR Gimbal + IMX6 only a bigger copter with CubebBack , running AC4.0.5 The gimbal link is on Telem2 using MAVLink1 at 230k : It configured rates itself If I disconnect the serial to the gimbal connection, then the gimbal is nice and still ... when connected, it will do "random"...

That software is VERY outdated, and you can have better, more feature-rich software with additional/better safety. Start here: OpenSolo/OpenSolo

Too little info. Are you using the 3DR app? You should upgrade the software on Solo & Controller to OpenSolo 4.0 and use Solex (or some alternative that works on apple) - even QGroundControl may be a good alternative.