Won’t stay connected

[irussphone]

I flew two times today.

The first time everything connected well and I flew straight up to 50 meters and promptly got “not connected” thank goodness it returned home after a couple of minutes waiting for a connection. I tried to reconnect. No joy. I rebooted the TX, the phone app, and the drone in every possible sequence. No joy. I then turned all off AND restarted my phone. Brought all back up and it connected! Same result, went up to about 30 meters and “not connected” and returned to home. Spent about 30 more minutes trying to problem solved and no good, disgusted! Packed up and went home. I have screen recordings of all of it. I’m going back to previous release “44”

I never had this problem with it.

Update: Wouldn't connect when I got it home from the flying field so I reinstalled the older 1.0.44 firmware version and then it connected immediately...see tomorrow how it flies. If it flies well I'm sticking with this version until some REAL improvements happened.

[irussphone]

Just flew with 1.0.44 version and two perfect flights. Never lost connection and video was great out to 300+ meters. It did disconnect once on the ground and I decided to try to turn off my phones (iPhone 7) WiFi and never disconnected after that.
I also tried this with 1.0.46 and still did not connect. I’m staying with 1.0.44 for now.

[Djose24]

I with the version 1.0.44 and the 1.0.46 I go to 900 meters and 120 meters high without any problem.

[Hubsan-Ailsa]

Hello irussphone,

May I know if you update the all Zino firware to the latest one(FC ,Gimbal,IT firmware)?Kindly remind that format the SD card to FAT 32 when updating the IT firmware.
This customer Bellerophon solve his disconnect issue.Hope will help you

[irussphone]

Hello irussphone,

May I know if you update the all Zino firware to the latest one(FC ,Gimbal,IT firmware)?Kindly remind that format the SD card to FAT 32 when updating the IT firmware.
This customer Bellerophon solve his disconnect issue.Hope will help you

Ailsa,

Here is my screen recording of the flight...it shows all of my setup in doing all of the connections, horizontal calibrations, compass calibrations, etc.
This happened twice on Saturday so I reinstalled FC 1.0.44 and flew several flights on Sunday with very little problems (just some small GPS hold issues)

I have done all previous firmware upgrades successfully...so I know the correct procedure to update and was careful to follow all instructions exactly.

Thanks for reviewing,
Russ


P.S. Here is also my flight log for the Zino so far...

[Hubsan-Ailsa]

Hello Russ,

Thanks for your feedback

We reviewed that you take long time to pass the GPS accuracy in the video.Kindly suggest you take the phone and moving within a range of less than 5 meters from the Zino to pass the GPS accuracy.Hope will get the good GPS accuracy quickly.

[irussphone]

Yes I saw that too but the controller was within .5 meters the whole time, plus I had over 12 satellites available so I don’t know why that was happening. It’s part of the hardware/software problem for Zino engineers to solve.
It does not happen with version 1.0.44. ???

[501Pete]

Yes I saw that too but the controller was within .5 meters the whole time, plus I had over 12 satellites available so I don’t know why that was happening. It’s part of the hardware/software problem for Zino engineers to solve.
It does not happen with version 1.0.44. ???

I'd say it was an issue your phone manufacturer needs to address.
Firstly, and this is only my opinion, I'd forget about doing the GPS test. It is a waste of time and I always skip it.
(I don't use automated modes anyway).
However, the issue is invariably always the HDOP of the phone GPS, not that of the quad.
It clearly shows in your video the HDOP on the controller as 8m minimum.
Until that reduces to something smaller, then the check will always fail unless you walk around.
Things that make HDOP worse are disabling mobile data on your phone (e.g. putting into flight mode) and not setting the location services on the phone as "high accuracy" (ie use Assisted GPS with GPS, Wifi and Mobile network enabled).
You're right the quad has 12+ satellites in view and it will fly perfectly.
If you try and RTH and select to current position, it will say that the phone location accuracy may not be accurate (or words to that effect).
In reality it probably will still come back to you within arms reach.
RTH to the arm point will be fine as it's not making any use of the GPS position reported by your phone.
You can walk around with your controller and it will pass the test, that is a bodge however and doesn't actually mean the accuracy has changed in anyway

[irussphone]

Thanks and interesting thoughts...except that the troubles that I have using version 1.0.46 don't happen with version 1.0.44 and I'm using the same iPhone 7+ on both. I get initial accuracy of at least less than 2 meters (even though I'm 6 inches away from Zino with the controller) with "44". I'll keep trying the new firmware updates but I'm keeping "44" as my baseline because it lets me fly and make good videos, which is why I bought it. BTW, here is my "44" flight last Sunday...Russ

[kenman]

I'm flying with a cheap Samsung J3 android, flown with the 46 firmware about 6 times, having no problems with connection or anything! this phone is a 1.3 quad, not to strong, but I've flown out to about 600m with no issues... I think there might be something with your phone... I know the Iphones kick ass most of the time from what I'm hearing... just my opinion.... good luck