HERE-3 GPS on CAN failed by upgrade to V4.5.4

Here GPS
1

Help please :slight_smile:

My HERE3 GPS has worked fine on CAN with ArduPlane V4.3.5 for months
Today upgraded to V4.5.4, now GPS not recognised in Mission Planner

  • LED lights on unit flash green (locked, disarmed)
  • All CAN settings rechecked.
  • Moved it to CAN2, no joy.
  • Updated bootloader and firmware on HERE3 (v2.1)
    I only have one instance of node id 125 in

All I get is this message… Selected GPS Node 125 is not set as instance

any suggestions gratefully received :slight_smile:

image
image835×325 73.9 KB

image
image1065×308 84.2 KB

2

@Michael_Oborne
@philip

Please guys, any suggestions as to what this could be?
Thank You

3

@steviegeek please share your parameters, make sure you have cleared GPS1_CAN_OVRIDE (set to 0)

4

Hi,
I did set both GPS1/GPS2_CAN_OVRIDE to 0 but no joy, (also 125)
param file is …
240626 No GPS working.param.zip (5.3 KB)

5

Hello,
Have you resolved this issue?

6

@steviegeek seems like I missed to revert back to you on this, did you get the issue resolved? Parameters all look ok.

7

Managed to look at this again tonight.

CUBE still had v4.3.5 and when poered on bench with just PWR1, USB and HERE-3 on CAN 1 I get an almost instant fix and long/lat are correct

Did straight update to v4.5.4 no GPS found

Did straight update to v4.5.5 still no GPS found

Reverted back to v4.3.5 and GPS back working :slight_smile:

No other changes made,

I’ve included copies of MP message panel
MP Messages.zip (813 Bytes)

any ideas guys?
Thank You
Steve

8

@steviegeek I just noticed something unusual in your parameters. GPS_CAN_NODEID1 is set to 0 (should be set automatically to 125, once Here GPS comes up). GPS1_CAN_OVRIDE is set to 125 which is manually entered by user, to remove bad parameter state, I think it might be worth erasing parameters and redo the setup. Is this something you have tried? Use Reset to default option in Mission Planner to do so. And set GPS_TYPE1 to 9 and CAN_P1_DRIVER to 1 after reboot.

9

@sidbh
Thank you for your response, I do appreciate it.

I have done a clean install of v4.5.5.
I reset values to default
I also interim flashed a ‘rover’ build to clear out any remaining ‘plane’ data

I have set :-

  • CAN_P1_DRIVER to 1
  • GPS_TYPE1 to 9
  • NTF_LED_Types to include ‘dronecan’

Still will not see the GPS
GPS_CAN_NODEID1 and GPS_CAN_NODEID2 are reporting 0 and I cannot change it in MP
Reverting back to v4.3.5 works everytime, I’m getting ready to pul out what little hair I still have left :slightly_smiling_face:

I notice that in previous posts I said I was using HERE3, this is a mistake, I have a HERE2
Would my error here affect your advice?

Param files for both versions are attached
two param files.zip (9.9 KB)

Best regards
Steve

PS, comparing both param files shows:-

image
image692×206 4.64 KB

How can I force GPS_CAN_NODEID1 to ‘125’ in v4.5.5 ?

Thank you

10

@sidbh
@Michael_Oborne
@philip

I have turned to a Matek H743 WING V3 to try to resolve this issue
Using MP 1.3.82
Using ArduPLANE V4.6.0-dev

Exactly the same issue with the HERE 2 GPS, i.e EKF3 waiting for GPS config data with no GPS detected
GPS_CAN_NODEID1 still defaults to 0 and I am unable to change the value to 125 as previously suggested.

Advice gratefully received, Thank You
Steve

11

Have you try to put the drone and gps outside to get the gps reception?

12

Thanks, but it’s not a reception issue.
In the working configuration on FW 4.3.5 it pulls in 16/18 sats with no problem

13

The Solution :smiley:

Flash COPTER v4.5.5
Set

  • CAN_P1_DRIVER to 1
  • GPS_TYPE1 to 9
  • NTF_LED_Types to include ‘dronecan’

Check GPS is recognised and lock can be obtained

Flash PLANE v4.5.5
Set

  • CAN_P1_DRIVER to 1
  • GPS_TYPE1 to 9
  • NTF_LED_Types to include ‘dronecan’

All should be good now, PLANE on latest firmware with HERE2 GPS working.
This worked on CUBE BLACK, CUBE ORANGE and Matek H743WING V3

Thanks to all who contributed to this thread :slight_smile: