ID NORM

[Crusty]

One of the new features in V3 is ID NORM.
"The Target ID value for a specific target will be consistent across the 4 operating frequencies when the ID Norm option is activated."

Seems to me this is a good option and makes sense......how do otheres here feel about ID NORM ?

Dave

 

[Andy Sabisch]

Two ways of looking at that option . . .

1) It makes it easier to remember what specific targets register as across all frequencies

2) Having TID values shift as you change frequencies is one way to check for targets such as bottle caps so locking the TID with this function negates that ability

Two camps - and for me, my use depends and where I am hunting.

Personally, the range of good TIDs is not that hard to remember across multiple frequencies but it was added to address a stated need and it does address that request quite well

Andy

 

[Crusty]

Two ways of looking at that option . . .

1) It makes it easier to remember what specific targets register as across all frequencies

2) Having TID values shift as you change frequencies is one way to check for targets such as bottle caps so locking the TID with this function negates that ability

Two camps - and for me, my use depends and where I am hunting.

Personally, the range of good TIDs is not that hard to remember across multiple frequencies but it was added to address a stated need and it does address that request quite well

Andy

Thanks Andy, I knew there had to be two ways, at least two, to how this feature may or may not add to my detecting experience.
Also just wanted to say I'm surprised how easy the menu is to navigate on the Deus......a pleasent surprise these days.

Dave

 

[Ism]

When people were making v3 requests, one of them was ID normalization. I thought it was a great idea and wanted it also.
Now that I have it, I don't use it. For all the reasons Andy Mentioned.

 

[WestTn]

They should have used 12Khz for ID Norm simply because it is closer to the TID numbers of the majority of other detectors on the market. Whenever I use 12Khz, the TID numbers just seem to make sense to me and seem more familiar than the 18khz numbers that XP chose to go with. Of course, since many European users prefer 18Khz for their sites it makes sense that they chose 18Khz for the detectors that are closer to them, but a simple option to choose which khz to normalize to would be easy to implement in 3.2