Find's Treasure Forums

Welcome to Find's Treasure Forums, Guests!

You are viewing this forums as a guest which limits you to read only status.

Only registered members may post stories, questions, classifieds, reply to other posts, contact other members using built in messaging and use many other features found on these forums.

Why not register and join us today? It's free! (We don't share your email addresses with anyone.) We keep email addresses of our users to protect them and others from bad people posting things they shouldn't.

Click here to register!



Need Support Help?

Cannot log in?, click here to have new password emailed to you

Changed email? Forgot to update your account with new email address? Need assistance with something else?, click here to go to Find's Support Form and fill out the form.

On the Rail with the V3i....

Wow!
Just came in from detecting and I see lots of reply's to this.:shocked:
First and foremost, Let me say that I am not and will never give up on the V3 or V3i machines. They are the best on the market by a long shot!
I am only having a small problem and I am trying to get it resolved. Its just that I have been having so much fun with my V3 that I haven't given it alot of thought lately.

Here is the issue in full detail. I was detecting with the V3i and came upon a dime hit at about 4 inches. When I went to pinpoint, I could see the bars but had no sound. Sometimes it would give sound at first but then it just faded to nothing. I could always see the three frequency bars at all times...no problem with that. Just no audio. I grabbed my V3 from my truck and took it to the spot and pinpointed dead on it without even ground balancing. I dug it and it was a clad dime. Also, there was a nail about an inch deeper in the hole. I know its not anything I am doing wrong and I know its not something I should have to change or balance differently because it doesn't do it on my V3 and all of my settings are the same. I dont use the salt mode.

In my opinion, I think it is loosing its ground balance somehow. I use loctrac because I didn't have much luck with auto trac. I have noticed that I can ground balance and the machine will balance like it should by going quiet and all I have to do is just wait about 15 to 30 seconds and go to ground balance in the same spot again and it makes the woosh sound because its out of balance again. I have quit using a +1 offset, I keep it at zero now. I know whites is busy right now and I am content with keeping it for a while and sending it in later. If I had to use the V3i right now, I would still know that I have the best machine out there, I would just have to get around the pinpointing issue some how. It only does this about once out of about 25 targets.

Please dont anyone give up on the V3i. Its a great machine! I just had the thought that it was going to be so much better than the V3 and in some ways it is but not that much above the V3.
Maybe its better for the users that was having issues with the V3 and they got the V3i which is right and it seemed so much better? Dont know. I would love to go to Sweet home and do some testing and stuff. I have all the time in the world if Whites ever need the help. I would do it just for my love of detecting and the to be of service to great Whites products.
 
I can't say I have the PP problem. If it's a really deep target it is hard to PP and I don't get much in tone or frequency bar, but I would expect that. I have noticed that if I get a good VDI hit and no PP it is two targets close together and I am between them so the PP moves off to the side in the two directions, but nothing where I was getting the high VDI hit. I figure this is edge effect so it doesn't bother me as I find that to be fairly common. With any detector I have used, if it misfires on PP let up on the trigger and move off to the side PP again and move over the supposed target. That always works for me if there is something there to PP. There was one field in Kentucky where I did have problems PP targets, but other things were acting up too like the threshold would not stay steady. I was continually ground balancing. I moved to the next field and no problem whatsoever. The problem was not the detector.
 
OK, I went back and re-read the post. Sorry Rob. I did mis-quote you. I guess I am in agreement with Burlbark. Apologies to you as well Burlbark. Magic, please keep us posted on your progress with the pinpoint issues. This is not the first time I have heard of this happening. I may just have to pick up a new V3i. :rolleyes:
 
CyberSage said:
OK, I went back and re-read the post. Sorry Rob. I did mis-quote you. I guess I am in agreement with Burlbark. Apologies to you as well Burlbark. Magic, please keep us posted on your progress with the pinpoint issues. This is not the first time I have heard of this happening. I may just have to pick up a new V3i. :rolleyes:

When I used the v3 and not the v3i I did notice that the vdi was a tad but jumpier. There may be more stability to the v3i as my buddy was running his 15 yards away and could not get his to settle down in this pygmy soil. He kept complaining about it but he may have been getting interference from my detector. So in theory the v3 may be a bit more sensitive but to the extreme of stability suffering.

If you dont have an issue with your detector than dont fix it. Mine works like a champ even with a little null when pinpointing and dealing with trashy areas. Its as simple as pulling the trigger again.
 
I am not yet a V3i owner(will be here thursady though)yet, but would like to comment on this issue. After using Magic's V3i(not his V3) for roughly 9-10 hours and countless pinpointed targets, not one time did it fail to pinpoint w/audio. That does not mean that the problem does not exist. I highly regard Magic's comparison an his skill level. He is a top notch detectorist for sure.

I do wonder if the right ground minerals plus good vs. trash targets in close proximity are the over arching culprits here as others who posted might have been indicating.
It might be prudent to suggest to Whites to conduct extensive tests between the V3 and the V3i while pinpointing targets in the field or in laid out test beds.
Maybe Magic or some of you who have had similar situations may already have spoken to Whites engineering about this.

One thing I can say being a V3i novice is that the V3i is one sensitive machine and does go deep. Not having any experience with the V3, I cannot say whether better or worse.
I will leave that up to Mr. Magic!

Two more days till I get mine, maybe I will know more with time under my belt!:detecting:
 
Here is a post made by Sun Ray.

(2) However, the stock White's 10" DD coil may or may not overload with the DX-1 in-line depending on the tolerances from coil to coil. This has nothing to do with the probe or coil involved, rather with the switch (for switching from coil to probe and visa versa)

(3) It was found that by either reducing the RX gain a number or two ,or, disengaging TX Boost resolved the problem.


I know that magic and I both run the V's hot and use the D2. I lose the threshold on my DX1 and have to hit the trigger to get it back when pinpointing. Could the problem be related? Could the DX1 be contributing to the problem. I can't check because I'm not losing audio.

I wrote Sun Ray and got NO answer.
 
Just read the comment on the DX1 rcasio44. Might be relevant indeed. I did have another thought. Since the video manual indicates that DC sensitivity for pinpointing when cranked high can affect shallow target pinpointing and knowing that Magic has his cranked high plus that dime he mentioned was at 4, maybe the V3i works differantly than the V3 using the same program?

Maybe the V3i needs to have DC sensitivity lowered?
 
corvair said:
Maybe the V3i needs to have DC sensitivity lowered?

That would never work for Magic and Me.:devil: :devil: I have the DC higher to get depth with the DX1. Again I lose the threshold on the Dx1 not when pin pointing with the D2. Magic is losing it with the D2 but they could be related. Someone having the problem and using the DX1 will have by pass the DX1 when the problem accurs and see if it solves the problem.

OK, you electronic gurus out there, how could the switch be causing the problem. I need to know in electrical terms.:stars:
 
I closed this post and started new separate ones because we are talking about 3 issues in one post. It got too complicated.
 
Top