Spurious ARPA Targets DRS25A-NXT

[Quitsa]

R&D at our parent company reviewed this thread and passed on that the full auto-tracking feature in XL can be helpful as it is set not to acquire targets further than the land echoes. The ACQ by doppler examples seen are normal so one needs to adjust Gain/Sea/Rain as needed for the operational area (as everyone has seemed to already discovered). They confirm that there were no changes from the previous version of software for this but downgrading is a good way to confirm that it isn't software.

I am using the radar with the TZT 3 units at my main helm. I don't see how limiting the ARPA acquisition to the range of land echoes would be especially helpful. I could do that manually I assume by using a shorter range. Generally speaking, at least in my home waters there are more potential real and spurious targets between my boat and land anyway so it wouldn't help. It sounds to me as though your R&D group confirmed what Bayhouse tested, which is that setting the sea state manually to a higher level can reduce the spurious targets.

It sounds to me as though there is an issue with the software settings controlling the ARPA target selection on the NXT radars. I lived happily with prior generations of Furuno magnetron radars with ARPA that performed perfectly and never showed spurious targets. It wasn't until I got the DRS25A-NXT that I saw the issue so I am guessing it has to do with how the "auto acquire by Doppler" was implemented.

My boat will not be in the water again until May so I cannot test manually adjusting sea state myself for a while. I also want to try turning off the setting for auto acquire by Doppler, which I don't think I tried. Did anyone else try that?

 

[Johnny Electron]

I personally have very little thoughts on bayhouse case due to the starlink install, even if moved amps with damage can have issues. Thanks for following up. Stepping back on software is aways an option if you guys feel strongly it was something with the recent change(s). Our support team can send whatever older version you would like to try. I will ensure they are aware in case they can make some additional software tweaks for next version.

 

[Quitsa]

I personally have very little thoughts on bayhouse case due to the starlink install, even if moved amps with damage can have issues. Thanks for following up. Stepping back on software is aways an option if you guys feel strongly it was something with the recent change(s). Our support team can send whatever older version you would like to try. I will ensure they are aware in case they can make some additional software tweaks for next version.

I had the issue for quite a while before starting this thread nearly a year ago. The software history for the DRS25A-NXT shows the last update being v. 1.11 in April 2024. However, that version appears to have been aimed primarily at the XL: "Improved: TT Auto-acquisition (Full Auto-tracking) function is added for use with the avoidance route function on TZTXL."

Probably we would have to go back to v. 1.10 or even v. 1.07 to test whether there was something in the software update that produced the problem.

What's puzzling is that more people do not seem tobe reporting an issue. It's is not exactly subtle -- the radar display gets covered with numerous ARPA targets.

 

[Bayhouse]

I am actively using the boat and am happy to downgrade to v1.10 or 1.07 if someone at Furuno can send me those versions.

 

[Bayhouse]

I personally have very little thoughts on bayhouse case due to the starlink install, even if moved amps with damage can have issues. Thanks for following up. Stepping back on software is aways an option if you guys feel strongly it was something with the recent change(s). Our support team can send whatever older version you would like to try. I will ensure they are aware in case they can make some additional software tweaks for next version.

So, let me see if I understand your response.

Even though my results are identical to Quitsa and SaltyBrad, MY problem is related to the Starlink install location/masthead light move.

Quitsa and SaltyBrad do not have a Starlink installed but experience identical outcome. Saltybrad even has a different array size.

I still experienced the issue with 1) with the starlink shut down entirely, 2) with sector blanking of that entire area (including the masthead light) blanked BUT my radar has been damaged by the Starlink??