Hello,
I’m having an issue with my pixhawk 2.1 running 3.5 RC4 on traditional heli.
I am using the here GPS unit and what is happening is this, what I power on my receiver and then the pixhawk indoors for bench testing the GPS does not lock on quickly and the servos lock up and the arming switch starts flashing red. Even if the here GPS has a good lock, all I have to do to replicate the problem it’s covered the GPS so it loses signal at which point the arming light goes from solid red to flashing and the servos lock. Keep in mind this is in stabilized flight mode, not one of the GPS assisted modes. If I bring the heli outside and boot everything, it works as expected. I am also getting lots of EKF switching from zero to one when indoors and the GPS loses signal. I have removed the here GPS from the chain and just plugged in the stock safety switch and I have no issues whatsoever. Also when the EKF changes from zero to one and Back Again the servos twitch which obviously would not be good behavior in the air. I intend on uploading parameter files and a logging .bin when I get home later this evening.
Thanks.
Those are screen shots some of the error messages I get when trying to bench test indoors with less-than-perfect GPS signal.
Tim
[https://drive.google.com/file/d/0BxUn7rkPzp9sa3FXQ25nSmVKRXc/view?usp=sharing](https://drive.google.com/file/d/0BxUn7rkPzp9sa3FXQ25nSmVKRXc/view?usp=sharing)
Hello,
This was solved. It all came down to a pin not making good contact on the factory connecter for the Here GPS. Tightened up the pin and the constant disarming went away.
Tim
Hi @timbaconheli, I do have problems with the Pixhawk 2.1 and Here GPS. It seems that the GPS in not detected by arducopter. Are you using the GPS1 port on the Pixhawk?
Looks like there are some problems on the GPS port of a batch of Pixhawk 2.1, i have read quite a few problems.
On one of my Pixhawk 2.1 the GPS (here+) was detected as NMEA 9600 and loiter had poor perfermances, changed board with a replacement and all was good.
Corrado
I had the same issue on two of my PH2.1 Boards.