# V1.3.0 beta testing **URL:** \ **Category:** Flight Testing & Log Analysis\ **Created:** [March 30, 2016, 7:17pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283 "2016-03-30T19:17:47Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![bujiebuhuo](https://discuss.px4.io/letter_avatar_proxy/v4/letter/b/ee59a6/32.png) [@bujiebuhuo](https://discuss.px4.io/u/bujiebuhuo)\ **Post date:** [April 9, 2016, 5:45pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/21 "2016-04-09T17:45:02Z")
Can flow module through jtag interface debug it? ---
**Author:** ![LorenzMeier](https://discuss.px4.io/user_avatar/discuss.px4.io/lorenzmeier/32/17_2.png) [@LorenzMeier](https://discuss.px4.io/u/LorenzMeier)\ **Post date:** [April 10, 2016, 7:14pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/22 "2016-04-10T19:14:22Z")
@gervais I’ve fixed the telemetry issue - I disabled receive for OSD which is the default on TELEM2 - stupid mistake. I updated the beta and master branches with the fix. We also discovered that there might be a better tuning for small quads / racers: Could you help us testing that here? > [@Pixraxer as a RACER](http://discuss.px4.io/t/pixraxer-as-a-racer/183/44): > > That’s really odd - we believe its a Wifi issue with the ESP8266 since we see packet loss there, but not via USB. Could you try setting your gains with USB and a computer? In general we noticed that dropping the ROLL\_P gain and increasing the ROLLRATE\_P gain is better for racing - could you help us testing that? One experiment to try is to drop ROLL\_P to 3 and increase ROLLRATE\_P to 0.25 (same for pitch). You still need to tune, that’s just a starting point. I would be interested to know if yo… ---
**Author:** ![gervais](https://discuss.px4.io/user_avatar/discuss.px4.io/gervais/32/42_2.png) [@gervais](https://discuss.px4.io/u/gervais)\ **Post date:** [April 15, 2016, 8:49pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/23 "2016-04-15T20:49:34Z")
Todays Master surprised me with the following warning: ![](https://discuss.px4.io/uploads/default/original/1X/f8b04cc0027950bd46cd49ee4e8e88def9d07448.jpg) Note: Rx was not connected. ---
**Author:** ![LorenzMeier](https://discuss.px4.io/user_avatar/discuss.px4.io/lorenzmeier/32/17_2.png) [@LorenzMeier](https://discuss.px4.io/u/LorenzMeier)\ **Post date:** [April 18, 2016, 6:27pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/24 "2016-04-18T18:27:21Z")
This could be a potential hardware corner case where a pulldown is missing. I have filed [https://github.com/PX4/Firmware/issues/4293](https://github.com/PX4/Firmware/issues/4293) to track this. In other news: I just updated the beta branch with a couple of fixes, in particular for single switch flight mode selection. Basic re-testing would be appreciated. Just manual flying and preferably a small mission. On the failsafe question: I will respond to that separately. I think it mostly needs fixes on the QGC GUI side. ---
**Author:** ![gervais](https://discuss.px4.io/user_avatar/discuss.px4.io/gervais/32/42_2.png) [@gervais](https://discuss.px4.io/u/gervais)\ **Post date:** [April 19, 2016, 7:43pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/25 "2016-04-19T19:43:59Z")
Thx, tried latest Master of yesterday noon with Quanum Nova and F450 defaults. No recognizable issues, although I still need some more “deadband” for Althold. Quite a bit too nervous, although the baro is covered very well and inside the “Nova box”. Is there sth. like an EKF\_ALT\_NOISE Parameter ? I checked vibs via APM vibe 3.3 log , definitely superb, [http://fs5.directupload.net/images/160416/4voyr6zb.jpg](http://fs5.directupload.net/images/160416/4voyr6zb.jpg) , so this is not an issue. Flight mode assignment (Stab,AltHold,Pos Ctl.,Land by Mixer) was easy. Compass Cali with daily QGC was a little confusing, since some of the axis (not always the same) turned yellow but did not turn green. Nevertheless,the Sensor health showed green after a few trys, so I cared less, since YAW was correct. Despite these littles, I´d personally consider this version safe to fly. ---
**Author:** ![gervais](https://discuss.px4.io/user_avatar/discuss.px4.io/gervais/32/42_2.png) [@gervais](https://discuss.px4.io/u/gervais)\ **Post date:** [April 20, 2016, 4:41pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/26 "2016-04-20T16:41:35Z")
**Update:** I really enjoyed several batteries flight with todays master (@ F450 PR r12) , and the QGC Android app, (Higly appreciated, the new scrollable tuning pages @5.5", all in all **great usability** ) Compass cali behavior was the same I mentioned yesterday, although all remaining yellow fields turned green @ finish… Formerly supposed Althold “issuses” were gone after I turned the tuning slider to the mid. Still have to re-adjust my PosCtl.settings which appear to swing back (lock) too hard.The associated tuning slider did not help , not sure what it does at PosCtl.) **All in all I´m very delighted.** Small cosmetic flaws: 1.Experienced incredible high (9 digits) accumulated battery consumption. Don´t need that anyhow, could be as well hardware on my side. 2.Always after moving the tuning slider, **Manual Control lost** appears (nothing lost though). Besides that Failsafe Options OFF and LAND are still not available , I´d consider this dev version as **fool proof** (at least for my simple quad builds) Thx a lot,guys ! ---
**Author:** ![Andreas\_Hoffmann](https://discuss.px4.io/user_avatar/discuss.px4.io/andreas_hoffmann/32/3467_2.png) [@Andreas\_Hoffmann](https://discuss.px4.io/u/Andreas_Hoffmann)\ **Post date:** [April 20, 2016, 8:26pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/27 "2016-04-20T20:26:31Z")
Installed latest Master on Pixracer and AUAV-X2 using QGC Build 418. Having nonsense Values for Accumulated Consumption of the Battery before, there is now higher Values jumping between 0 and fantastic values. It does not matter if there is a Current Probe attached (i.e. Controller only attached to USB or if there is a real Current/Voltage Probe). Could someone explain the meaning and source of this value? Apparently it is not just an addition of actual current consumption since it can jump to any value. Anyone has good Values for ACSP 4 and ASCP 5? For ACSP 4 I needed quiet a lot of try and error to adjust voltage while ACSP 5 with factory defaults was on spot. Still my Current Readings are quiet wrong. There is no explanation why there are several multiplicators FMU/IO etc… One example of the Values displayed shortly before going back to 0: ![](https://discuss.px4.io/uploads/default/original/1X/b793266c2df37615c248081580d7dbcfbd42b02d.png) ---
**Author:** ![gervais](https://discuss.px4.io/user_avatar/discuss.px4.io/gervais/32/42_2.png) [@gervais](https://discuss.px4.io/u/gervais)\ **Post date:** [April 20, 2016, 11:34pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/28 "2016-04-20T23:34:16Z")
Since both of us reported the same, it´s obviously a bug and has nothing to do with your settings.You don´t need accumulated values anyways. 😉 ---
**Author:** ![LorenzMeier](https://discuss.px4.io/user_avatar/discuss.px4.io/lorenzmeier/32/17_2.png) [@LorenzMeier](https://discuss.px4.io/u/LorenzMeier)\ **Post date:** [April 21, 2016, 6:22am UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/29 "2016-04-21T06:22:27Z")
Thanks for reporting! I will check what’s going on with Pixracer on current. ---
**Author:** ![Andreas\_Hoffmann](https://discuss.px4.io/user_avatar/discuss.px4.io/andreas_hoffmann/32/3467_2.png) [@Andreas\_Hoffmann](https://discuss.px4.io/u/Andreas_Hoffmann)\ **Post date:** [April 21, 2016, 7:18am UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/30 "2016-04-21T07:18:14Z")
IMHO the the reading was juming around already in 1.2 but not at such high values. ---
**Author:** ![Justin\_Cooper](https://discuss.px4.io/letter_avatar_proxy/v4/letter/j/e274bd/32.png) [@Justin\_Cooper](https://discuss.px4.io/u/Justin_Cooper)\ **Post date:** [April 23, 2016, 2:57am UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/31 "2016-04-23T02:57:25Z")
I think I found a bug in the 1.3 beta or it may be in QGC. I had the telemetry failsafe on under safety but in the summary section is says disabled. ---
**Author:** ![Justin\_Cooper](https://discuss.px4.io/letter_avatar_proxy/v4/letter/j/e274bd/32.png) [@Justin\_Cooper](https://discuss.px4.io/u/Justin_Cooper)\ **Post date:** [April 23, 2016, 5:24am UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/32 "2016-04-23T05:24:56Z")
The other issue i just noticed is that I am having telemetry drop out when the battery gets below 20%. I am using an RFD900 in low latency mode. ---
**Author:** ![gervais](https://discuss.px4.io/user_avatar/discuss.px4.io/gervais/32/42_2.png) [@gervais](https://discuss.px4.io/u/gervais)\ **Post date:** [April 23, 2016, 8:16am UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/33 "2016-04-23T08:16:47Z")
So you´re lucky, that FS has been disabled. When GCS/Telemetry FS came up on default @ APM,which I sadly didn´t notice, I experienced one of my most expensive crashes, so I turn it off, if I´m able to. Call it a trap : Can´t image RTL if _connection lost_ appears (which is not unsual _for me_) **We need** a Failsafe config page for PX4 where we´re able to do so and **have the choice to fix** either **RTL** or **LAND** or **Do Nothing action**. Until this is the case, I can´t do safe testflights within urban environments. ---
**Author:** ![LorenzMeier](https://discuss.px4.io/user_avatar/discuss.px4.io/lorenzmeier/32/17_2.png) [@LorenzMeier](https://discuss.px4.io/u/LorenzMeier)\ **Post date:** [April 23, 2016, 10:22am UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/34 "2016-04-23T10:22:19Z")
That config page is there. If you don’t check any of the options t will do nothing by default. ---
**Author:** ![gervais](https://discuss.px4.io/user_avatar/discuss.px4.io/gervais/32/42_2.png) [@gervais](https://discuss.px4.io/u/gervais)\ **Post date:** [April 23, 2016, 10:42am UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/35 "2016-04-23T10:42:00Z")
Sorry, I didn´t find it. I´ve got only this page: ![](https://discuss.px4.io/uploads/default/original/1X/adc82594b8bfb99531fa068f5269dea0e40ea461.jpg) where I´m only able to uncheck Telemetry Signal timeout (Is this a loss, and how long ?), but I can´t disable RTL or change it to LAND. Under _Radio Signal Loss_, I only find a Loiter time parameter. ![](https://discuss.px4.io/uploads/default/original/1X/cff345dffe218709300fe171573d17de6bc2b803.jpg) Thats where simple users like me would expect some further action adjustments. I understand that this might not be of any importance for plane users. ---
**Author:** ![gervais](https://discuss.px4.io/user_avatar/discuss.px4.io/gervais/32/42_2.png) [@gervais](https://discuss.px4.io/u/gervais)\ **Post date:** [April 23, 2016, 11:12am UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/36 "2016-04-23T11:12:30Z")
Regarding _Radio Signal Loss_. I almost forgot: RSSI status shows a 100% even if the Tx is turned off. Q: Is this related to Rx only ? ![](https://discuss.px4.io/uploads/default/original/1X/c58e9b106571517e480e04d58dec6afc238aa4d7.jpg) ---
**Author:** ![Justin\_Cooper](https://discuss.px4.io/letter_avatar_proxy/v4/letter/j/e274bd/32.png) [@Justin\_Cooper](https://discuss.px4.io/u/Justin_Cooper)\ **Post date:** [April 23, 2016, 12:12pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/37 "2016-04-23T12:12:33Z")
This is of importance to plane user having the options you are discussing. Having the plane return home and land on RC signal loss is a much better option than loiter and terminate flight. More options for telemetry failsafe would be much better as well. ---
**Author:** ![LorenzMeier](https://discuss.px4.io/user_avatar/discuss.px4.io/lorenzmeier/32/17_2.png) [@LorenzMeier](https://discuss.px4.io/u/LorenzMeier)\ **Post date:** [April 23, 2016, 2:56pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/38 "2016-04-23T14:56:35Z")
I fixed the Pixracer current (I think), please try master. I also added land and “do nothing” for RC and data link loss. Its not yet on master but on this PR: [https://github.com/PX4/Firmware/pull/4344](https://github.com/PX4/Firmware/pull/4344) ---
**Author:** ![Justin\_Cooper](https://discuss.px4.io/letter_avatar_proxy/v4/letter/j/e274bd/32.png) [@Justin\_Cooper](https://discuss.px4.io/u/Justin_Cooper)\ **Post date:** [April 23, 2016, 4:47pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/39 "2016-04-23T16:47:50Z")
Awesome. I will make sure to test all of this including the throttle disarm when it makes it to beta. Hopefully these features can make the cut for the 1.3 release. ---
**Author:** ![Andreas\_Hoffmann](https://discuss.px4.io/user_avatar/discuss.px4.io/andreas_hoffmann/32/3467_2.png) [@Andreas\_Hoffmann](https://discuss.px4.io/u/Andreas_Hoffmann)\ **Post date:** [April 23, 2016, 7:44pm UTC](https://discuss.px4.io/t/v1-3-0-beta-testing/283/40 "2016-04-23T19:44:44Z")
Hi Lorenz, sorry but Power Consumption is still erratic on Pixracer and AUAV-X2. Now the Values jump between 0, 255 and some really large number (see Screenshot). ![](https://discuss.px4.io/uploads/default/original/1X/27b6680a9ee00a74367ed149233e108042c963d4.jpg) Value shows also up in Mavlink Inspector. 1.2 and earlier often shows -1 and some strange number. Never had anything useful there. [Previous page](https://discuss.px4.io/t/v1-3-0-beta-testing/283.md?page=1) [Next page](https://discuss.px4.io/t/v1-3-0-beta-testing/283.md?page=3)