Yes I did before I decided to try i2c after many hours. Has leaved it at i2c since then.
I have never been able to see any compass from the Here2 unit. Now it is in auto. But I will mask it to the three known types soon. Or should I mask all others, how about redundancy? Is anything lost if masking the intenals while using external?
Can’t remember. I think you’re right! I guess that log is with HW ID 1 and 2 as internal and HW ID compass 3 not found. When masking all except UAVCan. No compass can be found.
I did put second GPS on top instead. Then the issues is gone. I use 3DR GPS/compass, instead. Square, semitransparent black thing with uBlox. That compass is always found and as first compass in HW ID.
Did some switch back and fourth, but nope, no Here2 compass found in i2c.
The flat cable in the Here is always bended quite bad, like the wires needs to be formed in an short S-shape to get the PCB back down. May that lenght could be adjusted in future builds. Or the cable holder maybe can be a bit redesigned a bit more out the get more fittng space. This is just constructive feedback. May some people have broken cables out there? May my compass leads in the i2c is broken?
It is hard to measure these connectors while bending the cable, but got many good zero ohm readings when I did checking the CAN cable.
Hmm, about the cable, no twisted can pairs could that be the issue? I saw someware it is possible to adjust the CAN speed. Can that help to easier get CAN contact for the users?
Sorry for brainstorming. May I need some sleep here.