[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 can be used to search on the beach? On dry sand? On wet sand? On black sand? In salt water?

BLISSTOOL LTC64X can be used to search on the beach? On dry sand? On wet sand? On black sand? In salt water?

Answers to the most frequently asked questions about BLISSTOOL LTC64X metal detectors.
User avatar
Posts: 205
Joined: Tue Apr 01, 2014 6:44 pm

BLISSTOOL LTC64X can be used to search on the beach? On dry sand? On wet sand? On black sand? In salt water?

Postby BLISSTOOL » Sun Feb 26, 2012 10:15 am

BLISSTOOL LTC64X can be used to search on the beach? On dry sand? On wet sand? On black sand? In salt water? By immersion in water? On saline soils?

- Yes, all BLISSTOOL LTC64X versions can be optimized directly by the user for these conditions. Generally, BLISSTOOL LTC64X work well on dry sand and wet sand on the beach, and on saline soils. For such conditions, sometimes is necessary, the THRESHOLD potentiometer to be set at lower level (5, 4, 3 or 2) and, if absolute necessity the GAIN potentiometer also to be set at lower level. Also recommended is the search coil to move horizontally, some few centimeters above the surface, ie not very close to the surface. Of course this applies to the worst conditions, as black sand, where sometimes is necessary to work also with low level of DISCR DEPTH. It all depends on the specific conditions, as the composition of the beaches, the beach conditions and the soils anywhere in the world are quite varied. Leading in this case, is that BLISSTOOL LTC64X is extreme depth and universal all-terrain metal detector. It works quite well in all possible conditions.

These tips also apply to work in salt water, with complete immersion of the search coil in salt water. Everything except the electronic block of BLISSTOOL LTC64X, located under the armrest, can be immersion in the salt water. The electronic block of BLISSTOOL LTC64X is not fully protected from water, and BLISSTOOL LTC64X not applicable to underwater search, with full immersion. BLISSTOOL LTC64X allows safe dipping and search only to about 70-90 cm depth of the water, in river, sea, ocean, etc, provided that the electronic block is held entirely over the water. To protect the electronics block from the water is recommended BLISSTOOL LTC64X to be immersed in the water, maximum to the level of the handle. To further protect of the electronic block, in this case can be used the [url=index.php?option=com_content&task=view&id=249&Itemid=104&lang=en]Protective cover of dust, moisture and rain BLISSTOOL PTC4R[/url], but note that it does not provide 100% protection from water. It is desirable to use it and when you leave the metal detector on the beach, ie to protect the electronics block from the sand. Please make sure in advance that you put the stopper of the connector PHONES, if you do not use headphones, because the hole of connector PHONES is an area in which can directly enter a water, sand or dust in the electronics block. Please note that the penetration of water into the electronic block can cause serious damage of your metal detector, or to reduce its performance, so be careful, keep the electronic block totally dry.

For a particular beach, the ground balance for wet sand is the same or close to the ground balance for dry sand. Therefore, before working in wet sand, to achieve stability on the wet sand it is necessary initially to manual ground balance the metal detector on the dry sand to allow for a true reading of the ground without the interference of the wet sand. Once the manual ground balance is achieved on the dry sand use this ground balance setting when working on the wet sand. In addition, on wet sand, may be necessary to drop off the audio threshold into silent through reducing of THRESHOLD of lower level (4, 3 or 2), to eradicate the interference of the ground saturation.

Of course, the wet sand and the salt water creates more interference. This may seem like a lack of a ground balance on the wet sand in the standard "pumping", ie vertical movement of the search coil to find ground balance. In such large interference, which usually leads to false signals, if the initially manual ground balance on the dry sand does not lead to satisfactory results, proceed otherwise: looking for that position and those settings in which, under standard HORIZONTAL movements with the search coil the metal detector does not issue false signals. This is the correct setting for the beach, and especially for: dry sand, wet sand, salt water, saline soils. This is usually achieved in: GROUND MODE = MAN, GROUND RUDELY = "-", GROUND FINELY = "-", ie end leftist positions or near to this, and THRESHOLD set at lower level (4, 3 or 2). Reducing of THRESHOLD of lower level, it is usually necessary, especially on wet sand with large interference. In most cases, GAIN can be set at a high level, at the expense of reducing of THRESHOLD, ie operation without audio threshold.

Return to BLISSTOOL LTC64X Frequently Asked Questions (FAQ's)

Who is online

Users browsing this forum: No registered users and 1 guest