<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mammut/Barryvox Pulse v3.2- Avalanche Beacon Review</title>
	<atom:link href="http://www.wildsnow.com/6064/mammutbarryvox-pulse-32-review/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wildsnow.com/6064/mammutbarryvox-pulse-32-review/</link>
	<description>Backcountry Skiing Weblog Blog, FAQs, more, links and info about randonnee, telemark and backcountry ski mountaineering.</description>
	<lastBuildDate>Wed, 19 Jun 2013 14:22:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Robert Campbell</title>
		<link>http://www.wildsnow.com/6064/mammutbarryvox-pulse-32-review/#comment-51536</link>
		<dc:creator>Robert Campbell</dc:creator>
		<pubDate>Mon, 25 Feb 2013 21:15:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildsnow.com/?p=6064#comment-51536</guid>
		<description>Just a brief follow-up to my earlier query regarding Pulse Barryvox beacons and problems searching for Tracker 2s. An e-mail to Mammut got a very speedy phone reply and a detailed discussion of the issue. The problem, as one might have suspected, is signal overlap, certainly not new, but one exacerbated by the Tracker 2&#039;s signal. All devices experience the overlap, but the Pulse gives a visual acknowledgement of the overlay--the &quot;Stand Still&quot; command. This still doesn&#039;t explain adequately the blank screen problem. Perhaps this will be remedied with the Tracker 3 or future Pulse software updates. And, again the issue for me has been limited to practice searches with multiple beacons sending signals. For users familiar with the advanced settings, switching to analog can help. Even given these issues, I prefer the Pulse to other devices, particularly in multiple burial scenarios and I appreciated Mammut&#039;s prompt customer service.</description>
		<content:encoded><![CDATA[<p>Just a brief follow-up to my earlier query regarding Pulse Barryvox beacons and problems searching for Tracker 2s. An e-mail to Mammut got a very speedy phone reply and a detailed discussion of the issue. The problem, as one might have suspected, is signal overlap, certainly not new, but one exacerbated by the Tracker 2&#8242;s signal. All devices experience the overlap, but the Pulse gives a visual acknowledgement of the overlay&#8211;the &#8220;Stand Still&#8221; command. This still doesn&#8217;t explain adequately the blank screen problem. Perhaps this will be remedied with the Tracker 3 or future Pulse software updates. And, again the issue for me has been limited to practice searches with multiple beacons sending signals. For users familiar with the advanced settings, switching to analog can help. Even given these issues, I prefer the Pulse to other devices, particularly in multiple burial scenarios and I appreciated Mammut&#8217;s prompt customer service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Campbell</title>
		<link>http://www.wildsnow.com/6064/mammutbarryvox-pulse-32-review/#comment-51456</link>
		<dc:creator>Robert Campbell</dc:creator>
		<pubDate>Fri, 22 Feb 2013 18:12:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildsnow.com/?p=6064#comment-51456</guid>
		<description>I&#039;ve experienced multiple practice search failures using the Pulse Barryvox to find BCA Tracker 2s. The failures display differently, but most often result in a blank screen and silence while searching within 3 metres of the buried device. The apparent &quot;shut-down&quot; lasts to up to half a minute, though it&#039;s typically shorter in duration, but no less disconcerting. Having spoken with a number of Canadian guides, my experience is consistent with theirs--as clients with Pulses have routine problems while practice searching for Tracker 2s. And, I might add this is different than the standard &quot;Hold Still&quot; Pulse system warning that displays if a searcher moves too rapidly in fine search mode. Switching to analog mode (as an advanced system setting) appears to alleviate the search problem with Tracker 2s. I know from other web posts that there were earlier issues with respect to the Pulse and Tracker 2, but this seems to remain a problem.  Have others experienced problems with the Pulse and Tracker 2?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve experienced multiple practice search failures using the Pulse Barryvox to find BCA Tracker 2s. The failures display differently, but most often result in a blank screen and silence while searching within 3 metres of the buried device. The apparent &#8220;shut-down&#8221; lasts to up to half a minute, though it&#8217;s typically shorter in duration, but no less disconcerting. Having spoken with a number of Canadian guides, my experience is consistent with theirs&#8211;as clients with Pulses have routine problems while practice searching for Tracker 2s. And, I might add this is different than the standard &#8220;Hold Still&#8221; Pulse system warning that displays if a searcher moves too rapidly in fine search mode. Switching to analog mode (as an advanced system setting) appears to alleviate the search problem with Tracker 2s. I know from other web posts that there were earlier issues with respect to the Pulse and Tracker 2, but this seems to remain a problem.  Have others experienced problems with the Pulse and Tracker 2?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenkins</title>
		<link>http://www.wildsnow.com/6064/mammutbarryvox-pulse-32-review/#comment-49368</link>
		<dc:creator>Jenkins</dc:creator>
		<pubDate>Mon, 24 Dec 2012 13:46:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildsnow.com/?p=6064#comment-49368</guid>
		<description>I own a Pulse from 2 years with 3.2 version now and from the begining I have the same problem : after some 30&#039; using the device my way uphill if I grab it from his holster to for exemple switch to search mode the display is completly blurred by huge deep bleue smear hiding all the informations displayed and this for about 5 or 6 minute the time for the thing to adapt to the cold I suppose ?... Barryvox send me a new item and the problem is still there ! I wear the device directly on my first layer, under some sweater or jacket. Do you have any clue ?
Thanks for your job. Claude</description>
		<content:encoded><![CDATA[<p>I own a Pulse from 2 years with 3.2 version now and from the begining I have the same problem : after some 30&#8242; using the device my way uphill if I grab it from his holster to for exemple switch to search mode the display is completly blurred by huge deep bleue smear hiding all the informations displayed and this for about 5 or 6 minute the time for the thing to adapt to the cold I suppose ?&#8230; Barryvox send me a new item and the problem is still there ! I wear the device directly on my first layer, under some sweater or jacket. Do you have any clue ?<br />
Thanks for your job. Claude</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kean</title>
		<link>http://www.wildsnow.com/6064/mammutbarryvox-pulse-32-review/#comment-47777</link>
		<dc:creator>Kean</dc:creator>
		<pubDate>Sun, 04 Nov 2012 07:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.wildsnow.com/?p=6064#comment-47777</guid>
		<description>I&#039;ve just bought a Pulse with 3.2 firmware. I&#039;m an experienced user, but went for the advice of using the &quot;Basic&quot; profile to familiarize myself &amp; set about practising at home.
Now, having spent years being used to the idea of manually reducing signal strength on my Ortovox M2 as I get close to the victim, my kneejerk reaction was to hit a button as I homed in on the victim. But this just &quot;marks&quot; the victim, essentially turning off the signal. The problem is that in &quot;Basic&quot; mode, you can&#039;t unmark. So I essentially found myself several metres away from the burial site with my search signal suddenly turned off and no way to rectify the situation except turning the device off and back on again. Nothing in the instruction manual about this. I only found it by doing a web search and finding this article.

Um...if I was buried, I really wouldn&#039;t want to be wondering about whether or not my partner has sufficient knowledge of the device to work out why my signal has just disappeared off his Pulse cos they&#039;ve just inadvertently pressed a button in their panicked state...

It seems to me the risk of not being able to unmark in a life-or-death scenario is significant...</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just bought a Pulse with 3.2 firmware. I&#8217;m an experienced user, but went for the advice of using the &#8220;Basic&#8221; profile to familiarize myself &amp; set about practising at home.<br />
Now, having spent years being used to the idea of manually reducing signal strength on my Ortovox M2 as I get close to the victim, my kneejerk reaction was to hit a button as I homed in on the victim. But this just &#8220;marks&#8221; the victim, essentially turning off the signal. The problem is that in &#8220;Basic&#8221; mode, you can&#8217;t unmark. So I essentially found myself several metres away from the burial site with my search signal suddenly turned off and no way to rectify the situation except turning the device off and back on again. Nothing in the instruction manual about this. I only found it by doing a web search and finding this article.</p>
<p>Um&#8230;if I was buried, I really wouldn&#8217;t want to be wondering about whether or not my partner has sufficient knowledge of the device to work out why my signal has just disappeared off his Pulse cos they&#8217;ve just inadvertently pressed a button in their panicked state&#8230;</p>
<p>It seems to me the risk of not being able to unmark in a life-or-death scenario is significant&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
