I’d like to revive this thread. Fix type 4 is GPS dead reckoning and I am curious as to why we would dump out this message when this I believe is a perfectly sensible state. I have an uBLox F9R and am getting a similar output (state 33 in this case). I can submit a PR to remove this line (the message output), but would like to get an idea of why it was written this way in the first place?
I would like to revive this thread one more time. I have several ublox m8u and 9fr gps with deadreckoning, wich I think is a useful thing for ardupilot in case of temporal loss of satellites. I believe those new gps are not well supported but I also belive the changes needed to support them should not be many. In my case, sometimes the GPS works fine and got 3D fix, 3D dgps, or even RTK fix (with ntrip corrections from mission planner). However, sometimes I got the following:
The vehicle is shown on the map of the very spot it really is, but mission planner show “unexpected state 35” messages, 0 satellites in view, “no fix” and, interestingly, variable speed around 100 meters/second.
I am wondering if the gps could be configured using the u-center software in a way that the dead reckoning features are not used, so the states 33 or 35 are never reached, and making it compatible with ardupilot.
Any help will be much appreciated.
Thankyou in advance and regards!
Thankyou @amilcarlucas for your reply.
I have to apologise because I have been investigating further this issue and found that the problem was cause by interferences from a 4G/LTE USB modem that was only 10cm apart from the GPS antenna, not lack of support for this GPS by arudpilot.
Now, I get a fix with the GPS, only one problem remains: the “unexpected state 33” or 35 or 99 is shown, which I believe was the original concern of Fi156 when opened this thread. I have had a look to the source code and I understand that the new fix_type 4 (3DFIX+Dead reckoning according to the manual) of these M8u and F9r ublox gps is equivalent to a state of GPS_OK_FIX_3D, so that is not a problem other than the bothering message.
In any case, I haven’t found how to configure the ublox module to not to reach fix_type=4, which should be a way to get rid of the message.
Answering to your question, I am using rover 4.1.5, the vehicle is a mapping boat that I am building.