Does this mean that there was no pixilation? No. Running through all the same tests, the ZenPad surpassed the N7 LTE in all the “wobble” tests. Right from the beginning, things were better. Next came flight/battery #2, using the Asus ZenPad S 8.0. Feeling the tablet, while it wasn't hot enough to cook an egg, it was somewhat hot. Overall, I can say that the new Go (2.0.0) app does run better than the previous 1.2.0 version, and the video image, as viewed from the N7, did appear more “fluid”. During this flight, while the app, itself, didn’t crash, Google Play Services did crash. Several times there were what I can only describe as multi-colored “bars” running across the screen, from left to right. Multiple times the images appearing on the N7 got distorted…sometimes with the entire screen becoming pixelated, albeit minor pixilation. At this point, I repeated the “speed/distance test” portion of my first flight, although, this time around, I wasn’t moving the P3P as fast, nor was I interested in actual distance achieved…I was keeping an eye on the video quality, as viewed from the tablet. ![]() Again, there was pixilation in the prop areas, but more severe than the previous tests. I performed the “wobble” test one final time, this time at a distance of 2,000 feet. Increasing the height to 350 feet, as well as moving the P3P to a distance of 500 feet, I performed the same “wobble” test. There was, almost immediately, moderate pixilation in the areas where the props appeared. While the image (meaning the horizon, etc) being received remained as stable as possible, I can’t say the same for the image quality. Now for the part everyone has been waiting for…Rocky vs Bullwinkle…oops, Rocky vs Apollo Creed…oops, Nexus 7 LTE vs Asus ZenPad S 8.0 (Z580C).įor flight/battery #1, using the Nexus 7 LTE, I started by ascending to 200 feet, followed by purposely “wobbling” the right stick as much as possible. If it can make it to 5,600 feet in a radio-infested area like San Jose, I can only wonder how far it can go in a radio-free (or, at least, seriously radio-diminished) area. As for distance, I was just about to break 5,600 feet (1.06 miles) when I lost signal. With a reasonable wind blowing (the problem with Bay Area wind is that it’s constantly changing direction), it topped out at just under 30mph…not bad, in my estimate, and for which I’m guessing it would go faster if there was no wind. ![]() I then aimed it in the direction I felt would give it the longest line-of-sight path, and blasted it forward at full speed. I started the first flight (using the ZenPad S 8.0) by ascending to 121 meters (just under the 400 foot ceiling, at 396.982 feet) at a fairly brisk pace. I figured, if it can fly a considerable distance with this much radio interference, once I get it to a signal-free area, it will, in all likelihood, travel much further. Being that I live in the south SF Bay Area, I decided to test in South San Jose…partially because the “no-fly” zone extends too far north, due to the San Jose airport, and partially because I know there’s a lot of air-signal interference. Having finally received a third battery, I decided to use the first battery to “warm” the drone up, as well as to satisfy my curiosity in a couple areas (speed, and distance). ![]() I finally had the chance to run back-to-back flights, comparing the Nexus 7 LTE against the recently-released Asus ZenPad S 8.0 (note: this is the Z580C, not the soon-to-be-released Z580CA), and the results were interesting. BACK-TO-BACK FLIGHT RESULTS: Nexus 7 LTE vs Asus ZenPad S 8.0 (Z580C)
0 Comments
Leave a Reply. |