Replies: 3 comments 5 replies
-
|
The first thing to start with is what the arming blockers says. Arming blockers are shown at the top of Configurator as colored icons, along the right side, in the status bar, in the output of "status", and on the OSD. My favorite places to see them are in the OSD and in the status bar, at the very bottom right of Configurator. But if it's a navigation blocker, the OSD or the output of "status" will show more detail. |
Beta Was this translation helpful? Give feedback.
-
|
Oh dear, nearly two months have elapsed! I had other issues (video) with this quad, not a prime need for use, and so parked it. Have now largely resolved that video issue. On this quad the issue of refusing to arm and constant beeping is still present. Remember friend could sometimes (with NO changes) get his to arm and it then flew OK? I have not cured the issue, and it appeared "hard on". However to precis events.................. Connect battery to quad........... Beeping, will not arm, nothing in goggles to suggest why. Connect to USB and Configurator, still beeping, then notice the small battery indicator top of screen is red. BUT battery is fully charged! Battery power is there since items not powered via USB now show they are live. Check voltage, OK Disconnect Battery and reconnect. Repeat. After several times the battery indication in Configurator suddenly goes green and it all works with no beeping, Disconnect USB and quad flies LOS and FPV. Following day its back to beeping and won't arm. (not near USB to check) Yet battery voltage IS reaching FC (Foxeer Reaper AIO) and VTX and GPS. Tried several times to no avail, so moved onto a quad that does work! |
Beta Was this translation helpful? Give feedback.
-
|
Make sure you have System Messages on the OSD. |
Beta Was this translation helpful? Give feedback.
-
|
Cheers, I have, but no undue system messages result! Have just refreshed Goggles 3 and O4 firmware in the hope that the unspecified iNav to DJI OSD bug that SHOULD have been eliminated when I first updated to that fix by DJI will affect this specific issue and work next visit. I'm getting loads of OSD fields working, some that clearly should be graphics being letters. What appears on screen is way different to the Configurator screen, lots of fields appearing that are not set in Configurator, and some of the ones that are, are in different places. (Tried various HD settings) Today here in SE UK it was not just quite windy but REALLY erratically gusty. On arrival at field I set it up and the Sat's OK warble came quite quickly, less than 30 seconds. I armed and took off. NO constant beeping. It flew. Most of the OSD fields were updating, but not all. I was unsurprisingly having to put in a lot of minor corrections due the wind spiralling from the upwind trees. There was a Buzzard up and it was struggling!!! Bit the bullet, and tried Position Hold, then Alt Hold, then both. And shock of shocks, they worked, it doing a passably good job of a decent on the spot hover. Went in and out several time from manual, all good. End of battery, so landed. Later on after flying other non iNav non GPS quads I went back to it. Again it booted, now locking enough Sats in a couple of seconds, as my others always do on Matek GPS after the first of the day's longer delay. Took off flew around fine, engaged Position Hold and it immediately pulled back and left. Tried off and on, several times, Pos, Alt, and both. Manual flight fine, but Pos Hold pulling back and left every time. Alt seemingly not working now. Yes, it was on the right model, No I had not changed anything on it other than battery, which was "balanced" as before. Yes it was showing sufficient Sats locked. Levelling fine in Angle or Horizon when manual. So frustrating. Tomorrow might be less "testing" conditions, but...................... Gave up................ AGAIN. |
Beta Was this translation helpful? Give feedback.
-
|
And yesterday it was again pulling back and left as soon as Pos Hold engaged. OK in manual self levelling (Angle), no issue evident. I had a great deal of trouble getting calibration to run through when setting it up, but there is a small left/back slant shown on the Status quad image. I thought that on the calibration page the lower numbers could be edited to manually fine tune, but I can't? I'm wondering if this level offset is causing the beeping and refusal to arm, but I cannot see a message so. How can fine trim the quad manually please? I REALLY do not want to go through the turn and press calibrate process again |
Beta Was this translation helpful? Give feedback.
-
|
The first thing I would do is slightly loosen or tighten the screws holding the FC to level it out with the frame. Tighten the high side and/or loosen the low side. Having it level is always better than trying to compensate for the fact that it isn't. If there are no gummies, be careful it's not too loose where it will vibrate. Other than that, you can adjust the FC alignment settings to declare that it's not quite level in the frame. The cli offers more precision - down to 0.1° as I recall.
Pretending that gravity has a different strength than it really does is unlikely to be useful. That's what those numbers are - the reading from your particular sensor when subjected to 1 G at your particular location. (Different parts of the Earth have different gravity.)
Did you calibrate the FC after mounting it in the frame rather than before? That can make it difficult. Even more so if it's mounted not-quite-level in the frame. |
Beta Was this translation helpful? Give feedback.
-
|
OK, thanks, have spent some time to ensure the FC board is perfectly level with frame. That is not very easy as its a double layer small Cine Whoop with a thick moulded polycarbonate "ducts and frame" plus a beefy carbon frame, but its now done. Its on gummies and tiny O rings. Its made the already OK hover in manual even better. RE: those "lower numbers", I'm a Pilot, I need to be told things like "You fly down the Yeyyo line, den the bluu one, den the wed one". Show me a senseless and seemingly useless set of arbitrary numbers like that and I'll seize and start screaming Mayday! :-D It was already assembled and using Betaflight (very well, but of course not autonomously), so motors and ancillaries connected, etc, etc, so I installed iNav and calibrated it in the frame. It flies sans GPS perfectly well, so how can it be doing as it is? I have swapped GPS (Matek 10Q-5883) with one on a VTOL. Its not the GPS unit. The Foxeer Reaper AIO FC is an ArduPilot suggestion of a good FC candidate, so I thought iNav install would be simple. Ha! Today's test flight went differently again, In manual Angle/Horizon/Acro it behaved impeccably. Sats were never lower than 15 while armed live and in air. Booted rapidly, 20 seconds average to Sats warble, Disarmed, briefly disconnected at take off location and reconnected. Most time around 20 showing. Today............near zero breeze. Switching to Alt Hold alone changed the throttle down or up quad under manual power if moving up or down, but did not "hold" altitude well enough for use though def some effect. Switching to Position Hold had no effect at all. Switching in Return to Home had no effect at all. Remember these HAVE all worked sometimes when it feels like it, with no changes other than battery swap. No sign of the refusal to arm beeping. Ardupilot equipped VTOL(s) worked well today. Thanks very much for your efforts but something is clearly very wrong and its reached my tolerence limit. Its going back onto Betaflight sometime. For now its parked. |
Beta Was this translation helpful? Give feedback.
-
|
Do you have FPV with OSD? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Firstly, better state that this is affecting myself and a flying buddy in the same way. Neither of us are newbies, we both have built loads of quads on Betaflight, inc in my case ones with GPS RTH, but I wanted to try iNav autonomous waypoint operation. I already have two active VTOL on Ardupilot with the same GPS but didn't want the complexity. I have three quads on Betaflight with the same GPS, they just installed and worked then and always.
EQUIPMENT AFFECTED
Buddies is a 5" "Bitsa" with Matek F405 FC, mine a Foxeeer CineWhoop 2.5" Foxeer Reaper v3 AIO. Both on iNav v8.0.1. both have Matek M10Q-5883 GPS. Mine is a working conversion from Betaflight, it has HDZero. His has Analogue and is a parts bin special.
TEST PROCESS
Open top of hill but flat grass field, no obstructions for 500 metres plus. Quad on ground, Tx tried five metres down to one metre away
Do a normal Tx on, model battery connect to quad and then wait for GPS to go from power up steady green LED to start flashing green, then throw arm switch, and beeper starts continuous beeps, does not arm. (Does not seem to matter how long the wait for Sats is allowed to take, have tried waiting FAR longer than any other install I have)
On his quad, repeating this arm attempt several times from brief battery disconnect and reconnect sometimes, and only sometimes, allows arm and use. On two days last week he was unable to get it to arm at all. Yesterday first flight was the fifth attempt after the beeps and flashing LED of supposed Sat lock.
He has had the situation several days where at the field he is unable to arm, but get home five miles away and in his garden it arms instantly.
I have mine refusing to arm at home or at field, even with brief disconnect/connect. It has not connected at all for several days, no Sats being found, though it has done last week, and used to work relaibly on the same wiring with Betaflight. Once last week it managed to bring up the map with accurate home positioning. When NOT working (remember, not arming at all), if USB connected then in Config GPS page there's seemingly no Sats being found, though the Lat and Long figures displayed on the GPS page do show and seem correct.
To be clear, my other quads on Betaflight or planes on Ardupilot with the same GPS type find Sats and Arm at both locations quickly and easily, its only affecting his and my iNav equipped quads.
Beta Was this translation helpful? Give feedback.
All reactions