- Joined
- Jul 4, 2016
- Messages
- 90
- Reaction score
- 43
- Age
- 55
Do you suggest I try to cut and rewire, or just tape over that area and hope it still gives a good enough connection?And there is your button problem.
View attachment 24844
Do you suggest I try to cut and rewire, or just tape over that area and hope it still gives a good enough connection?And there is your button problem.
View attachment 24844
Awesome! It is flattened a little from being squashed down, but it's still intact so should hopefully pass a current through it.If the wire is not broken it should be fine to tape separately.
So, I put it all back together, and it seems good so far.No need to put it all the way back together. Just put the back of the controller in place, plug in the battery, and check to see if it fixed the problem. Either hardware monitor or the final output display will show the result. Then complete the assembly if all looks good.
I compared your other wiring to mine, and yours looks fine.
Yeah I went there early on to get a repair done once. Their warehouse was massive and they were super friendly and helpful. Their location was part of what tipped me to go with a yuneec yuneec instead of DJI.That is good news. Do you know you are near the first home of Yuneec USA? There offices were in a building at the airport business area.
I DO have real sense I just bought it recently (about a week back from Ebay) and plugged it in.Good catch @h-elsner ! I do see evidence of RealSense in the Telemetry as some of the indoor power ups show a flight mode change to 32 which is IPS. Those are the ones with the funky date stamp.
@Seachange01 , when you see this connect with the aircraft, go to the System Settings, and click on About then post a photo of the versions screen.
I'm pretty sure from memory I didn't have OBS turned on. I had read somewhere not to have it turned on at take off, and then where I was flying I didn't think I would need it, it was over some vacant land in a suburban area, so I just went high enough to clear any power lines and didn't think I would hit anything at all so I left it off.I’ll take a look at the FlightLog in the morning.
When you flew today did you have the OBS enabled so that the RealSense was operating? Part of your preflight now should be to ensure that the RealSense cameras at the front do not have smudges or dirt on them. Flying facing the sun near the horizon with OBS enabled can confuse the RealSense.
I cant tell you just how good it is to have people like yourselves on this channel to learn from you. Thanks for your time in reading my logs and my posts.I have RealSense and have only used it to test it out, and couple of times for Follow Me. I leave OBS off most of the time.
I looked at the flight in the open area you describe and the fsk_rssi readings are still poor and there is a lot of use of the WiFi redundancy for control. There are still issues with the 2.4 GHz RC. Either in the ST16 or on the aircraft.
The aircraft did stop responding to your controls and the only reason it did not do an auto RTH is that it still had some WiFi connectivity. Flight 00085 telemetry dropped out when things stalled at about 400 meters out. It was at that point when you said you used RTH to start bringing the aircraft back.
The telemetry for 00086 picks up about 35 seconds later and shows the aircraft in the RTH homing mode, then RTH landing. I see no flights after this.
I would like to see a flight using the stock antennas to rule out issues with the 4Hawks. You should be having good RC at 1000 meters or more in that area.
View attachment 24857View attachment 24858
The missing part of the yellow line between the two pics is the 35 seconds of missing data meaning no telemetry connection.
We use essential cookies to make this site work, and optional cookies to enhance your experience.