Forum Replies Created
@bassmaniac thanks lot. I still have no clues about your arming problem except the ones I already mentioned. Keep us informed and happy flying
@bassmaniac thanks for your Note that you would like to share the diff with me. I allready build a minitri based on the rcf3 flashed with triflight .5. As I wrote I would like to change to triflight .7 beta 3. A diff would be perfect even if you use the v4. As long it is the same board the diff would be a good start point.
Back to your not arming point. Did you do the on bench tail tune procedure and save the results? Another point could be that arming is blocked when the Tri is not leveled and arming is blocked when USB is connected.
- This reply was modified 3 years, 3 months ago by norwenkel.
Dear All, after nearly one year loosing a bit of interesst in Tri´s I just want to start again with Davids Mini Tri based on the RCF3 board. I´m still on triflight 0.5. Therefore i need to use the old cleanflight 1.23 configurator. I would like to test the new triflight 0.7 beta 3 Version and wondering which configurator I need to use.
With my quads I´m on the cleanflight 2.2.0, Betaflight 10.4.0 configurator and inav 2.0.0 rc3. I do not want to mess up my excisting triflight setup therefore i would be happy if someone could give me an advice which one to use. Another question is want to do with the cli dump. Could the dump be copied for starting because diff all is not a valid command in CL 1.23. what’s about resources. Do I need to change it? What about the feedback measurement? Is it necessary to do any adaptation when using the beta software? Maybe a 0.7 Beta 3 clip dump for an rcf3 board would be helpful
Thanks a lot
Thanks for your advices
Greetings out of Germany
sorry to say, but I have started a new non-iNav project and will test the resistor mod later this month.
Take care and happy flying
- This reply was modified 3 years, 2 months ago by RCExplorer - David.
I will try it later this week with a 400 ohm resistors soldered between the scl pin heater and the 3v pin header. Same with sda and 3v. Fingers cross!
may be I didn´t get it but where did you physicaly solder the 400 ohm resistor(s) between. (SDA—+3V and/or SCLK—+3V) My knowledge of electronics is a bit low.
so adding a resistor (400 ohm) at R23 or R22 on the F3FC in parallel could help?
@Marlon take a look at https://rcexplorer.se/forums/topic/sonnar-on-the-f3fc/. For me it looks like that Sonar is not possible with triflight and F3FC.
@villalji i’ve tested 4 different GPS/integrated compass solution with .5 and .6 and getting I2C error after a while. I was only successful when using the GPS and a separated compass board connected to the I2C bus. Reading some threats there seems to be problem with pull-up resistors. Maybe you will get some additional information.
Norbert13 November, 2016 at 10:06 in reply to: Throttle/motor behavior on RC Explorer, Naze32R6 & Triflight #34791
Just a short advice. You should not have the +-5v of the ESC’s connected to the NAZE32 if the Board allready have a +-5V connection. If not, just use one and not all 3 5V connections.
Hmmm… could be a couple of reasons. I would start like this:
– TX/RX binds correctly?
– check failsafe in the RX/TX
– assuming you have used the correct BHeli version (Multi) calibrate ESC´s again, (you are using a Naze32 rev.6, there are some issues with rev.6 depending which revision you have)
– calibrate ACC with ACC set to 180° in the CL config tab
– set ARM and FL Modes in CF to a switch using the AUX channels
– trim your channels carefully to min=1000, mid=1500, max=2000
– recheck your model in the Taranis
– connect the MiniTri without probs via LiPo and USB to CF. Check channel movement, motors and servo
re-watch Davids setup video and conpare with your setup
If you still have the same issue post your CF CLI Dump
hope that helps a bit
As far as I know Softserial is not available on the F3FC neither with INAV or Triflight! To use OSD, telemetry and GPS I flashed my x4rsb RX with the sbus-Cppm firmware from Frsky and switched to PPM. Sure you have some ms latency more, but That doesn’t bother me on a non-racer.
looks great. Thanks for sharing.
One question: inflight_acc_cal seems to be not implemented. Can you confirm that? How have you calibrate the servo movements?
@billyd apart from a broken ppm stream or a bricked Tx RX combination it could be a broken or wrong mixer definition in your TX. Setup a new model in your tx could help to investigate further.