Here4 Blue RID Issue

Hi

Using the Here4 Blue RID with from time to time I get a PreArm failure saying: “OpenDronId: Invalid Location”. trying to trace the arducopter code it looks like it is originating in the RID module but at the time it happens the drone usually have RTK_Float or even RTK_Fix.
the only way I managed to get it to arm is after power cycle when it happens.
I tried looking up the error both on Ardupilot, Google and here but can’t find any answers.
Anyone else seen something like it?

Have you setup the GCS GPS? Ardupilot | opendroneid-panel

Hi

I did, and just to make sure it is clear the drone id works most of the time, but from time to time it will show the “OpenDronId: Invalid Location” and it will only be solved with power cycle.

I don’t even change anything on the GCS when it happens i just power cycle the drone since it is a udp connection it will reconnect and work properly, so i suspect it is a bug in the HERE4 RID code somewhere.

May I have the log while it’s running? and also the configuration you’re using

Good Day @guyzoler,
This message should simply indicate no valid GPS lock when trying to arm. For Drone ID, this applies to vehicle and GCS.

1 Like

@Thomas Most of the time this happens the drone is at RTK_Float and the base is using the GPS from the RTK base which is a Emlid RS2+ unit which is also at RTK Float or FIx

@Cybra I’ll looks through the logs to see if i have an example, since we are not flying without RID I need to see if we had the Log_Disarm on…

@Cybra see example here, the drone had 27 sats and GPS Status of 5 but still sent invalid location
2024-09-24 14-42-42.bin (2.2 MB)

Which GCS are you using? Please take a screenshot of the GCS GPS section, and also the Here4 firmware version you’re using now

@guyzoler do you have telemetry logs as well. That way we can see the location messages originating from Cube are good or not. Also set DID_MAVPORT to same as telemetry.

Also make sure you are runnig latest firmware on Here4 as well. Here 4 Manual | CubePilot

@sidbh I’ll check for the telemetry logs for this run if not i’ll reproduce the issue and upload, might take a few days to find time for it but I’ll get it.

as for the DID_MAVPORT it is on CAN and it does work most of the time but from time to time it will give that message and it will clear on power cycle and work well so i think it is not a param issue.

I updated the firmware, I’ll make sure i have latest and post the version with the next logs.

Thanks for the pointers. I’ll follow up.