You are not logged in.

  • Register to access all forum features  

#26

Mr T
Member
From: Newcastle, NSW
Joined: 19 March 2014
Posts: 140
Member
02 October 2019 08:48 am

correct as per the tutorial

only works in MULTI FEQ setting

#27

goldtrapper
Member
Joined: 26 September 2018
Posts: 373
Member
02 October 2019 09:46 am

When I ran the dectector in multi frequency the EMI was terrible.

#28

Smoky bandit
Member
Joined: 05 April 2016
Posts: 4,323
Member
02 October 2019 10:15 am

goldtrapper wrote:

When I ran the dectector in multi frequency the EMI was terrible.

First thing I noticed as well.


No pain No gain..

#29

PhaseTech
Phase Technical
From: Adelaide, SA
Joined: 29 May 2014
Posts: 1,912
Phase Technical
02 October 2019 11:29 am

goldtrapper wrote:

Frustratingly it took 8 separate goes of opening the Minelab download window before it recognised my detector this time. Back to V 1.175

Have you managed to get it to upgrade?

Here is what I do.

- Open the Update Utility
- Plug the USB in
- Make sure coil is connected to c/box
- Switch on detector
- Click Install on computer

I have upgraded several units now, and it works no problem


Agent for Minelab, Nugget Finder, Nokta & Makro, Quest, Detech, SteelPhase - Phase Technical Website

2 users like this post: Smoky bandit, robmoto

#30

caparobertsan
Member
Joined: 27 January 2017
Posts: 702
Member
02 October 2019 04:37 pm

So I should not update it yet? skull thumbsup thumbsdown ?


Minelab Gao Find 60 owner , Victoria Miner`s right permit holder. Ebay purchase-> C.Scope CS4ZX! C.SCope CS330! Nexus Bonanza, Minelab Sovereign XS-2! Minelab 2100(have not used it yet)
Makro Pointer, XP MI-6!

#31

Kai
Member
Joined: 17 April 2016
Posts: 73
Member
02 October 2019 06:40 pm

I'm pleased with the update, my 600 was very jumpy on most targets, first thing I noticed when I bought it months ago, my xterra705 seemed very stable in comparison.
Now its alot more stable on good targets, I tried it in fe2 mode and found it would false out on trashy iron signals quite well.
Still more testing to go, but personally I'm pleased with the update.


Minelab Xterra 705 10x5 DD 18.75khz Eliptical coil, 6" 3khz DD digger coil

1 user likes this post: robmoto

#32

goldtrapper
Member
Joined: 26 September 2018
Posts: 373
Member
02 October 2019 10:13 pm

PhaseTech wrote:
goldtrapper wrote:

Frustratingly it took 8 separate goes of opening the Minelab download window before it recognised my detector this time. Back to V 1.175

Have you managed to get it to upgrade?

Here is what I do.

- Open the Update Utility
- Plug the USB in
- Make sure coil is connected to c/box
- Switch on detector
- Click Install on computer

I have upgraded several units now, and it works no problem

As per the reply, I had upgraded it and now have it back to version 1.1.75. thumbsup

#33

rockdev
Member
Joined: 05 December 2017
Posts: 149
Member
03 October 2019 10:14 am

Am very pleased with my update, I have a user profile setup with iron bios FE2@9 in park 1, its works a treat on very rusty caps and bolts, producing a warbly jumpy signal.


Equinox 800, X-Terra 705.

2 users like this post: PhaseTech, Trash

#34

Pieces-Of-Eight
Member
From: East Lake Macquarie, NSW
Joined: 27 July 2019
Posts: 61
Member
03 October 2019 07:46 pm

rockdev wrote:

Am very pleased with my update, I have a user profile setup with iron bios FE2@9 in park 1, its works a treat on very rusty caps and bolts, producing a warbly jumpy signal.

I'm confused with the @9 setting, unless you are in all metal mode doesn't is discriminate out 9 and below anyway ?

#35

Guessologist
Member
Joined: 06 February 2018
Posts: 209
Member
03 October 2019 10:43 pm

Pieces-Of-Eight wrote:

I'm confused with the @9 setting, unless you are in all metal mode doesn't is discriminate out 9 and below anyway ?

If I'm reading you right, I think where you're getting confused is mixing up iron bias and the accept/reject settings. You're right that the default program rejects IDs of 9 and below, the FE/FE2 iron bias setting changes the likelihood of a given signal to be reported as a negative ferrous ID (more bias, more likely a sketchy signal will be classed as iron). It's not really a setting that filters by the ID numbers, it comes in before the accept/reject is applied. Someone correct me if I've got that wrong....

Last edited by Guessologist (03 October 2019 10:48 pm)


Equinox 600 / White's GMT / Go Find 40 . Combined age of predecimals found so far: ~16,666 years (151)

3 users like this post: Smoky bandit, PhaseTech, Pieces-Of-Eight

#36

rockdev
Member
Joined: 05 December 2017
Posts: 149
Member
04 October 2019 09:29 am

Pieces-Of-Eight wrote:
rockdev wrote:

Am very pleased with my update, I have a user profile setup with iron bios FE2@9 in park 1, its works a treat on very rusty caps and bolts, producing a warbly jumpy signal.

I'm confused with the @9 setting, unless you are in all metal mode doesn't is discriminate out 9 and below anyway ?

What Guessolgist said is spot on, Fe and Fe2 settings are filters only, and have no bearing on discriminated numbers. It does however make the VDI jump all over the shop under an iron target when using FE2 6-9 giving them a tell-tale warbly unclean signal, but once the horse shoe is engaged they then become so easy to distinguish as they now become an iron target with a grunt. I was out testing again yesterday afternoon in my yard and having the FE2 on 9 certainly makes bottle caps and rusty nails sound like iron. big_smile

1570141672_caps1.jpg
1570141690_caps2.jpg

Last edited by rockdev (04 October 2019 09:30 am)


Equinox 800, X-Terra 705.

2 users like this post: Heatho, Pieces-Of-Eight

#37

PhaseTech
Phase Technical
From: Adelaide, SA
Joined: 29 May 2014
Posts: 1,912
Phase Technical
04 October 2019 12:50 pm

Yep, I like to think of the Iron Bias setting as the "How annoying is this iron" scale. As you get more annoyed, turn it up. You knowingly might be missing the odd good target, but I think this is offset by the extra ground coverage.

I've done some playing on some partially rusted bottle caps, and on normal Iron Bias you still get a confused signal. On the new Iron Bias, some would start to chop up at a setting of 6 or 7, and 9 really sorts them out! I think on a beach where targets are generally spread apart, I would have no problems running the Fe2 very high. But come across a narrow tidal gutter where many targets have accumulated, I'd probably back it off a little.


Agent for Minelab, Nugget Finder, Nokta & Makro, Quest, Detech, SteelPhase - Phase Technical Website

5 users like this post: Heatho, AngerManagement, rockdev, Trash, Pieces-Of-Eight

#38

Sunny Coast Gold
Newbie
Joined: 24 July 2019
Posts: 7
Newbie
06 October 2019 04:24 pm

Hi All
I updated my 800 to the new version but found it to be very jumpy and the tones different from what I'm used to. Anyone else find this? I've put my machine back to previous version as it seems more stable.

#39

goldtrapper
Member
Joined: 26 September 2018
Posts: 373
Member
06 October 2019 10:20 pm

Sunny Coast Gold wrote:

Hi All
I updated my 800 to the new version but found it to be very jumpy and the tones different from what I'm used to. Anyone else find this? I've put my machine back to previous version as it seems more stable.

Same here.

#40

Rustynails
Member
Joined: 20 May 2019
Posts: 52
Member
07 October 2019 05:20 pm

I updated my 600 and hit the beach last week, and had a shocker. To be fair, there was a fair bit of black sand about and this may have caused the F2 to cancel some good signals. I was running on beach 1 presets with a gain of 20. After an hour I had not one bottle cap on a beach that normally has plenty. Unfortunately I had no good targets either, (not a single coin) just one matchbox car and a few shallow pull tabs.
I buried a $2 coin at 6 inches and was struggling to hit it, with a very scratchy signal. This surprised me as I normally hit goldies easily on this beach. Again it may have been the black sand. I reduced the f2 and also tried reverting to FE for a slight improvement but still not convincing.
Reverted back to 1.7.5 today but haven’t been back to the beach to try it out yet. Not very scientific I know, but there’s nothing worse than detecting without confidence in your machine. I didn’t need the backlight mod and as a beach detectorist I don’t really find bottle caps a problem. A good beach scoop makes short work of them. Also, when anybody asks me how I’m going, I enjoy pulling a handful of crown seals out of the finds bag, it’s good PR for the detecting community.
School holidays are over and there have been plenty of depositors on the beach so I’ll try again during the week. If I bury a $2 and get the same response on beach1 presets then I’ll know it wasn’t the update causing the poor result.

1 user likes this post: Pieces-Of-Eight

#41

Pieces-Of-Eight
Member
From: East Lake Macquarie, NSW
Joined: 27 July 2019
Posts: 61
Member
09 October 2019 11:34 pm

Guessologist wrote:
Pieces-Of-Eight wrote:

I'm confused with the @9 setting, unless you are in all metal mode doesn't is discriminate out 9 and below anyway ?

If I'm reading you right, I think where you're getting confused is mixing up iron bias and the accept/reject settings. You're right that the default program rejects IDs of 9 and below, the FE/FE2 iron bias setting changes the likelihood of a given signal to be reported as a negative ferrous ID (more bias, more likely a sketchy signal will be classed as iron). It's not really a setting that filters by the ID numbers, it comes in before the accept/reject is applied. Someone correct me if I've got that wrong....

Thanks #Guessologist I appreciate the clarification. I think its time to hit the beach with some test targets again.
Apologies for the late reply, I was away.


Contact Us - Privacy Policy - Terms Of Service

View Desktop Site

Top