Closed stronnag closed 7 years ago
Build Tested : 2df6fae67458d4f2ce8c5bab7b1aff4fe985c169 Hardware:
Modes Tested:
Special Points:
diff all
Results:
Great results. I agree on a single place for test logs. This issue can serve that purpose.
Great results! @stronnag thanks for testing. I agree - one thread for test flights and logs is great (and new issues per specific bugs found)
Build Tested : 6883f08e794d8a04fc8a27cad54266770ae50807 Hardware: 600mm tricopter , SPEVO, M8N Modes:
Special Points:
diff all
Results:
Build Tested : 3b7620c80847c03e95ca197ca58292fda7101b6c Hardware: Z84 Fixed-wing, Spracing f3 mini. BN880 M8N, Frsky X4R and smartport telemetry. Modes:
Special Points:
Results:
Build Tested : 3b7620c Hardware: Sparky2, QAV 250, NAZA GPS, SBUS,
Not flown yet. MPU9250 MAG fails, it did this on 1.5.1 / 1.5 as well
CPU Clock=168MHz, GYRO=MPU6500, ACC=MPU6500, BARO=MS5611, MAG=AK8963 Sensor status: GYRO=OK, ACC=OK, MAG=FAILING, BARO=OK, SONAR=NONE, GPS=NONE Stack size: 2048, Stack address: 0x10010000 I2C Errors: 0, config size: 1798, max available config: 131072 System load: 1, cycle time: 2002, PID rate: 499, RX rate: 49, System rate: 39
I have a SPARKY2
board on the way to me. Soon we'll have this MAG issue fixed (hopefully in 1.6)
Build Tested (build / flash only) : INAV/SPRACINGF3 1.6.0 Jan 31 2017 / 19:42:23 (2c3a1d04)
Unexpected line appears in diff and dump:
VALUE rangefinder_hardware ERROR
This happens even after an explicit:
# set rangefinder_hardware = NONE
rangefinder_hardware set to NONE
# save
@stronnag fixed. See https://github.com/iNavFlight/inav/pull/1210
With the new model pre-sets feature, the default RC expo should go to something more useful for Aeroplanes ie 25% rather than the Quad 70%
Please make a ticket in Configurator project
czw., 2.02.2017, 19:08 użytkownik Redshifft notifications@github.com napisał:
With the new model pre-sets feature, the default RC expo should go to something more useful for Aeroplanes ie 25% rather than the Quad 70%
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/1172#issuecomment-277035393, or mute the thread https://github.com/notifications/unsubscribe-auth/AA7Amy40dB-MU36FVIqUEPGqBfUtjs2yks5rYhungaJpZM4Lv7FH .
-- Pozdrawiam, Paweł Spychalski
Build Tested : 50a53b76 Hardware: SPRF3 on 260mm dead cat, M8N, BMP280. SPEVO, 600mm tricopter, M8N
Modes Tested: Free flight (horizon, LOS) WP, PH, RTH, Auto land with disarm
Special Points: Configured via CLI diff all Default (racer) notch settings from latest configurator.
Results: Just Perfect!
Build Tested : dcc163f185486d46b00f6ef6b5b66814dd444158 (alpha-2) Hardware:
Modes Tested:
Special Points:
diff all
Results:
Build Tested : 73a5459 (Pre-alpha)
Hardware:
Modes Tested:
Special Points:
Results:
Build Tested : c305dba225bd6872ac1b48c55681379db0bcf764 merged with PR https://github.com/iNavFlight/inav/pull/1250 Hardware:
Modes Tested:
Special Points:
diff all
Results:
@stronnag thanks for testing! Mission Save/Restore is a very cool feature that was wanted for quite some time and after a year of development we got it working! :beers:
Build Tested : 1.6 Alpha 2
Hardware: Maple Mini (NAZE) on 480 custom built H wooden quadcopter with BMP280, MPU6050
Modes Tested:
Free flight (ANGLE); Nav ALT HOLD
Special Points:
Configured via CLI diff all PPM INPUT
No regressions or bad behaviours noted.
Build Tested : 160e5ac991d927acee29dbaf3a09e6f724d4e81a Hardware:
Modes Tested:
Special Points:
diff all
Results:
Build Tested : 490c164baf26e8221856f4da11ca3f2c72715eb6 Hardware:
Modes Tested:
Special Points:
diff all
Results:
Also tested arm safety modes with WP1 < 100m and > 100m from home. Working as expected.
Build Tested : dcc163f Hardware: •SPRF3 deluxe (w/ active baro and mag) on FPV49 (130cm flying wing), M8N.
Modes Tested: •Free flight (ACRO) •LAUNCH, ANGLE+MAG, ALTHOLD, ALTHOLD+POSHOLD, RTH
Special Points: •increased P(pitch: 40, roll 60) due to 30% servo rate •FF=0 •CRSF protocol for steering and telemetry
Results: •acceptable stability on a windy day (no tuning done) •CRSF telemetry issues •video and CLI dump •severe oscillations while recovering from a steep dive in acro mode with zero throttle (most likely due to the current PIFF amplification at zero throttle when TPA is set). Will try to upload a video...
Build tested: b710cedc27be2e305dd13e589951020169305067
Hardware:
Modes Tested:
Results:
Build Tested : # INAV/SPRACINGF3 1.6.0 Feb 15 2017 / 16:52:52 (1c373bf6) [RC1] Hardware:
Modes Tested:
Special Points:
diff all
Results:
loopIteration time (s)
0 35.907236
50 35.957814
64 35.972139
114 36.022701
128 36.036887
178 36.0875
192 36.101595
242 36.152211
256 36.166564
306 36.217181
320 36.231354
370 36.281968
384 36.296125
434 36.346723
448 36.361064
498 36.411939
512 36.426045
562 36.476647
576 36.49087
626 36.541429
640 36.555556
690 36.606165
704 36.620646
754 36.671079
768 36.685231
818 36.735792
832 36.749916
882 36.800517
896 36.814751
946 36.865358
960 36.879465
1010 36.930006
i.e. alternating loop iteration intervals of 50 and 14, not quite what I expected: or coincidence that 50+14 = 64, a multiple of 32?
Build Tested : bc6d74d9990eaf95266f20b3efe144206bda83d0 Hardware:
Modes Tested:
Special Points:
diff all
Results:
Build Tested : dcc163f Hardware:
CC3D on MINITALON, AFRONAZE on miniSkywalker.
Modes Tested:
Free flight (ANGLE). ALTHOLD, FAILSAFE (RTH)
Special points:
LTM telemetry working perfect in EZGUI at 9600 bps through openlrngs modules. First time it works so well. FPV flights with minmosd in the same port and LTM. All working perfect.
Results:
No problems with miniskywalwer, but minitalon doesnt launch so well (some times to the ground, ,missconfigured picth parameters?)
Build Tested : RC2 Hardware:
Modes Tested:
Special Points:
Results:
Build Tested : 178d105bbf865f3af62119301c81e1fd842b140b Hardware: * SPRF3 on 260mm deadcat, M8N, BMP280.
Modes Tested:
Special Points:
diff all
Results:
Build Tested : dcc163f Hardware:
CC3D on MINITALON.
Modes Tested:
Free flight (ANGLE). ALTHOLD, FAILSAFE (RTH), FAILSAFE by switch and by link lost.
Special points:
None.
Results:
Minitalon autolaunching nicely on 20 degrees climb. Not so well when activating failsafe by switching off the transmitter. The plane goes full throttle and weird trajectory. Blackbox doenst work in my cc3d setup.
It seems to me it would be useful to have a single place to record incremental test successes (and failures) on the road to next release. It may also help catch regressions. If you disagree, please close. This does not preclude obvious bugs being logged under separate issues for triage and rectification.