Cube Orange with 4.2 firmware.
Updated bootloader.
Here3 updated to version 1.8.
*eliminated induced voltage noise as a possible cause
*confirmed no wires are damaged
*firmware updated to latest (v1.8)
*900mhz radio (RFD900) antennas moved and reduced, no change
*compass confirmed to be accurate
*Set BRD_BOOT_DELAY to 5000, no change
*disconnected all peripheral components, connected direct to cube orange, no change
*force arming results in Unhealthy GPS Signal warning
*moved Here3 connector to CAN2 port, did not change parameters, no change
*connected main battery and did a full system bootup to the drone airframe, no change
*connecting a Here2 module with no parameter changes and the autopilot sees up to 16 out of 26 possible satellites with Hdop around .76 to .91. Again, I should be locking at least 18 under these conditions.
*Updated the U blox m8p chipset with the “rover” version of the firmware from U Blox company to version Flash firmware version FW 3.05 HPG 1.43 for NEO-M8P, rover
Initial install went fine, but could only track a max of 11 satellites. I’m used to getting 18-21. As of now though, I can’t get a single satellite. I’ve tried outdoors, I’ve moved radio frequency generators (antennas, radios etc.) and still no joy. I’ve followed the Here3 manual to the letter. I installed version 1.8 on it from version 1.0.
The compass works and is calibrated. Here3 is connected to CAN1 port, no damage to wires that I can tell. The attached param file is NOT the completed configuration as this is a work in progress.
Does the MissionPlanner hardware ID screen indicate a connected GPS?
Try BRD_BOOT_DELAY,5000 to allow the GPS time to boot before the flight controller.
New result, I disconnected the Here3 and instead hooked up an old Here2 to the GPS1 port. I get satellites but again, not what I typically should get. I am seeing 11 to 16 with hdop around .7-.9 when I should be able to have up to 26 (27 satellites are visible at this moment).
So, same thing that happened with the Here3, poor satellite detection for awhile and I’ll bet the Here2 will eventually not detect any.
The Here2 is factory set/defaulted/not modified/not updated.
So how can my Here3 be getting all of this information yet Mission Planner fails to report a GPS fix?? On top of this, I am only getting GPS and GLONASS constellations and not Beidou!
At these startup messages I was hoping to see the message “GPS specified as …”, so it shows that the device is being found by ardupilot during startup, but right now I am in doubt if this message is Copter vehicle specific, never used Arduplane so I could be wrong about it, it is strange that the UAVCAN screen on MP shows the device.
