[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4938: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3936)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4940: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3936)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4941: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3936)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4942: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3936)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions_reimg.php on line 136: preg_match_all(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions_reimg.php on line 136: preg_match_all(): The /e modifier is no longer supported, use preg_replace_callback instead
BLISSTOOLFORUM.COM • View topic - BLISSTOOL LTC64X is extreme deep all-terrain detector. For objective reasons, not just talk.

BLISSTOOL LTC64X is extreme deep all-terrain detector. For objective reasons, not just talk.

Base Information and Documentation for all BLISSTOOL LTC64X metal detectors.
User avatar
Posts: 205
Joined: Tue Apr 01, 2014 6:44 pm

BLISSTOOL LTC64X is extreme deep all-terrain detector. For objective reasons, not just talk.

Postby BLISSTOOL » Mon Sep 02, 2013 8:14 am

BLISSTOOL LTC64X is extreme deep all-terrain detector. For objective reasons, not just talk.

Hello,

Below is relevant information available for metal detector BLISSTOOL LTC64X in response to the various comments from users on forums. The goal is knowledge and understanding from more users of the concept of BLISSTOOL LTC64X detectors.

BLISSTOOL LTC64X is extreme deep all-terrain detector. For objective reasons, not just talk.

Firstly, about BLISSTOOL LTC64X v3, please note that:

As a concept, BLISSTOOL LTC64X is designed:
- to have excellent depth of detection in all conditions!;
- to be used on any type of terrains;
- to can change its behavior: whether to be "noisy" or completely "silent";
- to have expanded opportunities for setting of the discrimination and ground balance;
- to successfully detect coin placed into ceramics, stones and rocks;
- to successfully detect coins in highly mineralized terrains;
- to have good depth of detection, not only to copper but also to silver and gold objects;
- to have high detection speed and high recovery speed and at the same time to have good
stability.

As BLISSTOOL LTC64X versions:
- v2 is a version specially adapted for heavy field conditions.
- v2i is an improved version of v2.
- v3 is the top version with extreme performance.

Base Technologies in BLISSTOOL LTC64X v3:
- Induction Balance ( IB )
- SuperB Depth = Super BLISSTOOL Depth ( SBD )

All the comments that BLISSTOOL LTC64X is not stable, are completely wrong and false. The purpose of setting of BLISSTOOL LTC64X is precisely obtaining satisfactory stability according to the criteria of the individual user. I repeat: obtaining satisfactory stability according to the criteria of the individual user. If the detector is not stable - it means a user has not done his job, ie did not set up it properly for the conditions. Explain. BLISSTOOL LTC64X has all the necessary adjustments to ensure stability on any type of terrain, including in extreme conditions where other detectors can not function. Some of them are: GAIN, SILENCER, THRESHOLD, FREQUENCY, TONE. Leading to BLISSTOOL LTC64X is the depth of detection in all conditions, but its behavior can be drastically changed as desired.

BLISSTOOL LTC64X, without knowing it, is not "turn on and go" detector. It is such only for users with experience with it and know their terrain. To achieve extreme parameters, it has several settings that need to be properly adjusted by the user. After getting used to the detector, it is easy and routine operation.

The main mistake made ​​both beginners and experienced but unfamiliar with BLISSTOOL LTC64X detector users is that overestimate their experience and knowledge. In the first meeting with the BLISSTOOL LTC64X, they set it to maximum performance when it exceeds the performance of almost all other similar detectors on the market. Yes, this is possible, but not suitable for welcome. It is desirable the detector to be understand step-by-step, starting from the minimum or recommended settings, and then gradually to be increased until the detector is still sufficiently stable.

Even with low levels of the settings, BLISSTOOL LTC64X as depth of detection, without difficulty, usually outperforms all other detectors with which the user is working. This applies to all areas: low mineralized, medium mineralized, highly mineralized. This has created some confusion in the user. For this it is useful initially BLISSTOOL LTC64X to be known as a concept rather than being treated as a standard detector. BLISSTOOL LTC64X is not a standard detector. It is detector with extreme depth opportunities. Explain. If you drive your standard car usually with 60 - 120 km/h, is not safe for you on your first drive with a powerful sports car you immediately to accelerate it up to 200 - 320 km/h. Yes, this is possible, but not suitable for welcome, ie can be fatal for you, because you still do not know the car well. Usually is not legal and not safe. Of course, in BLISSTOOL LTC64X, the things are not so dramatic. Even the user to avoid this error, follow the simple two scenarios: some users self-realize their mistake and optimize the settings of the detector, others simply write on forums that the detector is not stable. Please keep this in mind.

With proper user setup, BLISSTOOL LTC64X has high stability and depth of detection usually better than any other similar detectors. It is not true that if be stabilize its depth of detection is similar with other detectors. Even unnecessary stabilized, its depth of detection is much better. For example, even with GAIN = MIN, its depth of detection is better than many other detectors. Usually not well-wishers or our competitors when making parallel depth tests deliberately set BLISSTOOL LTC64X with GAIN = MIN or close to it (GAIN = 1 - 3), to provide a chance for their detectors to be a little closer to the depth of detection of BLISSTOOL LTC64X, although on most terrains BLISSTOOL LTC64X allows working with GAIN = 6 - MAX with extreme depth of detection. For example, its recommended setting is GAIN = about 5, and if necessary can be stabilized with THRESHOLD = 4 - 6, and SILENCER = OFF - 2.

Typically, the most common reasons for work with GAIN = MIN - 3 is "because only in this way the detector is stable". This is not true. It's like you to have a car with a 5 gears and to drive it only on the 1st and 2nd gear. You're not really doing this right? You use all of 1 to 5 by adjusting the speed of the car by the accelerator and brake. On most terrains, even with GAIN = 5 - MAX, BLISSTOOL LTC64X has good enough stability. The specific level of stability can be easily adjusted by THRESHOLD and SILENCER, etc. Yes, GAIN = MIN - 3, is suitable for beginners and advanced users with no or with little experience with BLISSTOOL LTC64X, but with their acquisition if want to achieve the maximum extreme depth of detection should work with higher levels, if the terrain allows. GAIN = MIN - 3 can be permanent setting, only for very highly mineralized or very highly contaminated terrains.

Achieving extreme parameters is not easy and is not cheap. Everything in BLISSTOOL LTC64X, including the search coils, is optimized and tuned for achieve a extreme depth of detection. Each BLISSTOOL LTC64X detector is individually fine-tuned (factory has about 40 - 60 fine settings), to ensure equal 100% performance for all our BLISSTOOL LTC64X detectors. For comparison, the tolerance of the most other manufacturers, ranges from about 80% to about 100% performance depending on the piece.

And something very important. Only after the user know the detector and can adjust it optimally, it can be used on any type of terrain, including but not limited to: low, medium, high mineralized, contaminated, on the beach, etc, ie BLISSTOOL LTC64X is universal all-terrain detector. It is not specialized detector, as some users with no or with minimal wrong experience with it, try to argue and likened it.

I hope this information is helpful.

With best wishes,

Ahmed Merchev
(President, sole owner and chief developer of BLISSTOOL)

BLISSTOOL

info@blisstool.com
+359883450667

Return to BLISSTOOL LTC64X Base Information and Documentation

Who is online

Users browsing this forum: No registered users and 5 guests