Hello unearth,
I detect similar venues much as you do only further north. The local mineralization conditions where I hunt run from mostly mild (3 blocks) to moderate (7 blocks) on the vertical mineralization bar graph on the far right side of the screen. I do run into localized patches of ground within these areas that are much higher. I’m a little confused about the “mineralization bar hits your numbers” (what/which numbers ?), when it was mentioned to be normally “between 3 and 5”. I’m assuming you may be encountering the same type of hot ground patches I do periodically and are concerned that your G.B. mode is set appropriately?
The XP link stated that “ tracking is best suited for ground with gradual changes in mineralization and is not recommended for ground with lots of iron mineralization and fast ground changes”. That seems to suggest manual G.B. would be the preferred mode to run in areas of human habitation and use where the likely concentrations of iron will be found.
The XP link also stated that the G.S. was fixed at 10 in earlier program versions, it is now preset to 6. Additionally the default G.B. in 4.1 is 88 which you might consider taking for a spin with the lower preset G.S.
I don’t think you are missing a step and also suggest you just run it as is with the factory presets until you an issue comes up.
On an aside, I read your post and a couple others regarding the continued troubles with the MI 6 Pinpointer after updating is still not resolving the connectivity issues that were to resolved with the new update. I’ve also read a number of comments in various posts suggesting that the LF coil and headphones should be charged up rather than connected to the charging leads during the entire process when updating to ver. 4.1 as per XP’s instructions and have since been speculating whether there was a connection (no pun intended) between them.
I’m not suggesting you or others didn’t update correctly, but am curious if the coil and headphones were on the charging leads during the update ? and if not..... it may explain the pinpointer issue...... again, I’m only speculating and could very well be wrong.
Hope this helps,
Bob