27 November, 2018 at 10:46 #60311
Is ADC2 pad R4 on the Kakute v2? And R5 would be Rx pads (for ESC telemetry)? The readings in the Triflight data object do seem to be quite out of range (ADCServoFdbk around 18k and ServoAngle -95k).
27 November, 2018 at 14:40 #60313
- This reply was modified 2 weeks, 5 days ago by Frederoo.
ADC2 is the RSSI pad, ADC3 is the R4 pad. Both work, as I’m using them on my BiCopter. You should be able to use either on the tricopter.
The data object readings will be nonsensical until the on ground tailtune completes. The on ground tail tune not only sets the servo speed (which by the way is not used for anything if you are not using the virtual servo model), it also sets the ADC end and mid points, which are critical for computing the tail angle correctly.
The way dRonin is architected, it’s likely that any available uart receive pin will be useable for ESC telemetry, once it get implemented. You will be able to pick which port you want to use, and then select ESC telemetry as the function, similar to how the receiver protocol and other functions are selected.27 November, 2018 at 15:37 #60314
Just switching to ADC3 fixed the issue – TailTune works perfect! My machine was very stable on default settings, can’t wait to test how this helps. AutoTune on the other hand broke Yaw so much that I reverted back to default. Thanks for the help @jihlein, and also great job on Triflight! 😉
Thanks again @david for the guide, it has some gaps but it does the job.27 November, 2018 at 15:42 #60315
One thing I failed to mention – the autotune function doesn’t “understand” servo controlled axes too well. If you apply the autotuned yaw gains, simply zeroing out the yaw D gain makes it flyable.
On the tricopter yaw axis, and the bicopter pitch and yaw axes, I’ve noticed this oscillation after autotuning. On both airframes, zeroing the appropriate D term solve the issue and resulted in nice behavior.
Glad it’s all working now, and now we know what gaps need to be filled. Thanks for your patience and persistence.28 November, 2018 at 02:22 #60316
I flashed the rc explorer f3fc with the f3fc.hex and I am having issues with my board being connected for about 3 seconds then it disconnects and reconnects constantly. Did I flash the wrong hex or is their something else going wrong here28 November, 2018 at 02:52 #60317
The correct hex is ef_f3fc.hex. Is this the integrated or racing version of the F3FC? For reasons I’ve not yet figured out, the integrated version had trouble booting. I don’t have one to troubleshoot with unfortunately. Racing version works fine.28 November, 2018 at 02:55 #60318
it is the integrated board / frame28 November, 2018 at 03:43 #60319
Unfortunately I’ve got no good answer for you right now. I’ll need to see if I can get a hold of an integrated F3Fc and figure out what’s different between the two that causes the boot issues.28 November, 2018 at 16:20 #60326
What firmware should I use on the Kakute F4 V2 when using this version of Triflight?29 November, 2018 at 02:20 #60353
If their is anything you want me to try out just let me know1 December, 2018 at 01:22 #60359
Nevermind I see this video is using that firmware and is included in the DMG file. All good ignore my post. Delete it, its taking up bits now…1 December, 2018 at 22:43 #60360
Tried to download the dronin from the link for pc and I keep getting a malware message from avg1 December, 2018 at 22:51 #60361
The warning is normal…2 December, 2018 at 04:22 #60362
Thanks got it to instal finally4 December, 2018 at 05:38 #60395
Where should I get the power for the servo on a kakute f4 v2 aio
You must be logged in to reply to this topic.