It's here...... Ortovox S1 Transceiver

[Hacksaw]

..It's here...... Ortovox S1 Transceiver

--------------------------------------------------------------------------------

A little over three weeks ago, I got my hands on one of the new production Ortovox S1 transceivers. I have been using it for the last three and half weeks. I used it daily on a two week trip in Canada. I have done about 35 transceiver practice search's with it. Most of these search's have been multiple transceiver search's.

I'll just say it up front, I am very impressed with the performance of the S1 transceiver. But, I have found a few little quirks with the S1, but they are usually caused by user error or lack of proper transceiver technique.

When I first got ahold of the S1, I sat down a read the manual ( I often have folks show up at avy courses who have never sat down and actually read their transceiver manual. And then they wonder what their transceiver is telling them.....). When I went out to do my first practice search, I started out with two transmitting transceivers about 3-4 meters apart. I really wanted to see strait away how well the "flagging feature" worked. The "flagging feature," is where after pinpointing the first found transceiver, you can "flag it as found," and then eliminate that transceivers signal, and start searching for the next transmitting transceiver.

The flagging feature worked like a charm with both digital and analog transmitting transceivers. I have tried all sort of mixes of digital and analog transmitting transceivers in my search's. I can't exactly say that the S1 prioritizes to another digital transceiver first instead of a analog transceiver. But, this afternoon in 10 practice search's the S1 did pulled me to a transmitting Tracker twice, while the transmitting transceivers where laid out in line facing me, about 5 meters apart. So, I can't really say that I think the S1 prioritizes to other digital transceivers first.

I really like the flagging feature. Once you've flagged on the pinpointed transceiver, the S1 will then lock on to the next closest transmitting transceiver. The S1 can search for 4 buried transceivers at one time. If there are more then 4 buried victims, there is a secondary search feature, that you can switch to that cuts the reception range of the S1 down for doing a 5 meter micro-strip search method.

While doing a two transceiver Nerfball method search, the balls (with the transmitting transceivers inside) ended up coming to rest within 2 meters of each other. I was really happy how the S1 locked on to one transmitting transceiver. I flagged that transceiver and the S1 went strait into pinpoint mode for finding the second transceiver that was so close by.

To search with the S1, all you have to do is line up the larger buried victim icon on the centerline of your search. Then you start going towards that icon. The S1 will bring you around on the flux-line of the transmitting transceiver. So, your not going in a strait line to the victim as you might think from the display. At the bottom of the display screen, there is a distance number (and number of buried victims signals). Obviously, you want to move so that the numbers are getting smaller. If there are several buried victims, you'll see a couple of other victim icons. These will be off in their respective locations, as you work on finding the first victim (more on this later).

Pinpointing with the S1, you use the grid method when you get within 3 meters. I personally like this method. There are a series of displayed circles on the display screen. Within these circles is a distance readout. Along with the circles there are arrows around the edge of the circle, that either point inward or outward. If your still getting closer to the buried transmitter the arrows keep pointing inward. If you have gone passed the buried transmitter the arrows start p[pointing outward. So... You have to really pay attention while your pinpointing and doing your grid method properly. Doing some deep burials, I have found that the S1 has pinpointed bang-on above the buried transceiver.

One of the quirks I have with the S1 and ALL DIGITAL transceivers for that matter, is that you can "out-run," your transceivers ability to keep up with fast running or hurky-jerky movements. But, search ablities of the S1 make up for this. When you have out-run the S1's ability to sort things out, or when it is faced with a "flux line salad" (i.e. several close overlapping signals) a little STOP hand icon appears on the display screen. So, its really important to move in a smooth and deliberate manner with the S1. If your hurky-jurky with the S1, other icons will come up to tell you to go right or left. If your tipping the S1 up and down too much an alarm will sound. So, always keep in mind SMOOTH, DELIBERATE AND FLAT.

When I have "out-run," the S1, the little stop hand icon has come up. It feels like it takes forever for the S1 to figure out what it wants to do. But, in reality when this has happened I have counted and found that the maximum length of stop time has been 12-15 seconds. Only when the S1 was totally maxed out with too many transceiver signals (like 20-30 signals = think LOTS of heli skiers milling around a parking lot) did it really "lock-up," for a longer amount of time.

One of my Canadian friends made an interesting comment about the S1. In a large scale accident a guide/leader could use the S1 as sort of a "command and control transceiver" while doing a search. Since the S1 has excellent range (approx 50-55 meters) the guide/leader with an S1 could come into an accident site and start directing other folks to consent rate their search's in selected areas (i.e., "Hay, there are two victims over to my right, there's one to my left. I'll take the one strait ahead. Split up and get to work, fast..."). Rescue/ski patrols/heli-rapid response teams will like that idea.

There are a couple of extra features that I don't think I'll use much (compass, inclinometer, thermometer).

There is a "revert to transmit" feature (in case of a secondary avalanche burining the searcher) that can be programmed to either 30, 90 or 120 seconds. This feature only activates if you haven't moved the S1 in the slightest way in the programmed given time. This is a lot better way of having the revert to transmit, then other older transceivers have had. But, you can also change the S1 back to transmit quickly, just by flipping the case closed.

Ortovox has programmed in a function that if you've allow your batteries to get below 20% capacity, the transceiver will switch over to an emergency acoustic reception/search method. Basically, the S1 becomes an analog search style transceiver. At first this made me wonder if the S1 used up batteries quickly. What I found in 20 days of use (approx 7.5 hours a day) the batteries capacity was only down 25%.

I do wish the harness system was a "right-side" harness system. But, that is a personal preference (because I've had my 2-way patrol radio on my left side for years). I can see the design thinking behind the harness that the transceiver ends up coming out of the harness in you right hand, since most folks are right handed it makes sense.

Overall, I think the Ortovox S1 is an excellent transceiver. In fact I really think its the best transceiver currently on the market (and I have tried almost every transceiver out there). Yes, Its been a long wait for the S1, but its been well worth the wait it in my opinion.

Cheers,
Halsted
__________________

[dirtybryan]

Cool review.

I have a Mammut Pulse and I remember getting the command role in a group rescue scenario because I could immediately tell how many beacons were buried as soon as the group switched to receive.

The Pulse also will sometimes tell you to stop briefly for it to sort things out.

[The Dad]

So if you, say, had an Ortovox X1 sitting new in box, which you could still return, would you?

[nesta]

Great review Halsted. I was really wanting one of these when they were
"supposed to be" coming out last year. When that was delayed I was slightly disappointed, but you have reconfirmed what I had first thought, that these have the potential to make all other transceivers obsolete. I might still wait a year in case there are any "bugs" to iron out, as this seems to be the case with most new transceiver technologies. But I can definitely see myself with one soon, finally joining the digital crowd. I currently use an Ortovox analog, which I am very comfortable with, but the features on the S1 from all I've read about or heard make it almost irresistable. Too bad about the price tag!

[lemon boy]

Awesome review hacksaw, thanks for taking the time to do it up.

[Hacksaw]

So if you, say, had an Ortovox X1 sitting new in box, which you could still return, would you?

Well, you'll have to pay the difference in price from what you paid for the X1 Vs. the S1.

If you don't want to pay the difference, you still have an excellent transceiver with the X1.

Cheers,
Halsted

[MakersTeleMark]

Thanks Halsted, I've really been waiting for this review.

[summit]

good review halsted!

[MakersTeleMark]

Wow, $500.

[H-man]

Thanks Halstead. One question though. When you use the term "out run" you mean this literally right, as in you are moving so fast down the slide path that the beacon can't keep up? Is it that literal or is there some hidden meaning that I don't get?

[Hacksaw]

Thanks Halstead. One question though. When you use the term "out run" you mean this literally right, as in you are moving so fast down the slide path that the beacon can't keep up? Is it that literal or is there some hidden meaning that I don't get?

No hidden meaning. Literal.

Halsted

[Yossarian]

Thanks Halsted! I am about due for a new beacon, this might be my next one.

As for out-running...yeah, literal. I know from experience that it's actually pretty easy to do in pinpoint search with a Tracker. If you're close in, and moving your searching beacon quickly back and forth above buried beacon, it's not hard to move "too fast" across the "flux line salad" (nice term there Halsted). The processor gets confused for a second, and takes a couple breaths to get itself figured out again as it reacquires.

[Hacksaw]

..."flux line salad" (nice term there Halsted).

I can't take credit for that term. I first heard it from Steve Christie of BCA.

[backcountry1pr]

Nice review

[summit]

I *knew* that the graphical representations had to be flux line bearings not true space representations!!!

[PNWbrit]

Thanks Halsted! I am about due for a new beacon, this might be my next one.

As for out-running...yeah, literal. I know from experience that it's actually pretty easy to do in pinpoint search with a Tracker. If you're close in, and moving your searching beacon quickly back and forth above buried beacon, it's not hard to move "too fast" across the "flux line salad" (nice term there Halsted). The processor gets confused for a second, and takes a couple breaths to get itself figured out again as it reacquires.

Anyone using a digital beacon who hasn't noticed this needs to practice more and read the manual.

[Yossarian]

I *knew* that the graphical representations had to be flux line bearings not true space representations!!!

But it works either way, right? I am not sure if I am visualizing this right, but in my head, it's like a little uhhh whatsitcalled uhhh target crosshair scope Top Gun fighter pilot "get tone" thingy? You move and simply try to keep the body icon lined up in your cross hairs, but your movements aren't straight line, they happen to be flux line? Halsted, is that right?

So, it shows body icons graphically, but they're not really spread out like that in physical space, they're spread out like that in "flux space."

[Hacksaw]

I am not sure if I am visualizing this right, but in my head, it's like a little uhhh whatsitcalled uhhh target crosshair scope Top Gun fighter pilot "get tone" thingy? You move and simply try to keep the body icon lined up in your cross hairs, but your movements aren't straight line, they happen to be flux line? Halsted, is that right?

So, it shows body icons graphically, but they're not really spread out like that in physical space, they're spread out like that in "flux space."

Basiclly, you have the right idea. You line up on the strongest buried victim and go until you get them into the crosshairs. At 3 meters the display automaticlly switchs over to the pinpoint circles. But, as your headed to this victim you'll notice that you have been following a curved fluxline. As for the other displayed victims they are displayed in relative location on the display.

Halsted

[summit]

Yoss: true... i was just hoping that maybe it had come up with some very very advanced DSP...

Now I am not as sure what differientiates the Pulse and the S1 (other than the Mammuts radio link and vital sensor)

Halsted you have handled both. Can you compare and contrast?

[Yossarian]

Yoss: true... i was just hoping that maybe it had come up with some very very advanced DSP...

Yeah, now that I think about it, why isn't that possible yet?

With dual antennas, known signal strength, known flux line/EM wave characteristics, and so on, don't we have all the info to calculate a direct line path to the position?

Just a "bit" of juicy math, no?

[summit]

Yeah, now that I think about it, why isn't that possible yet?

With dual antennas, known signal strength, known flux line/EM wave characteristics, and so on, don't we have all the info to calculate a direct line path to the position?

Just a "bit" of juicy math, no?

Don't consider my comments on this subtopic to be very authoritative because this is on the fringes of my understanding.
I believe that a device that would give real space coordinates for a ULF radio beacon (an 457 transmitter) would need either:

1. Dual or triple antenna + electronic compass + accelerometers (for a crude INS) and advanced DSP that would attempt to "triangulate" absolute real space coordinates based on measured signal strengths at measured bearings for different user positions (system collects and analyzes data as the user moves)

OR the simpler, easier, bulkier way

2. Two triple-antenna arrays with singificant seperation and simpler DSP to compare the two computed bearings/signal strengths for "triangulation" of relative real space coordinates (I don't think this would be a fit in your pocket device)

Maybe an experienced bug hunter or an antenna engineer will chime in

ETA: you might be able to remove the need for INS from option 1 if you simply had it programed so the user hits the "reading" button and the computer goes "step forward 1 step and hit the button again" then it gives the reading but that would make the beacon less foolproof and harder to use, though cheaper and easier to design)

[Hacksaw]

Now I am not as sure what differientiates the Pulse and the S1 (other than the Mammuts radio link and vital sensor)

Halsted you have handled both. Can you compare and contrast?

I have only gotten to use a Pieps Pulse in a couple of searchs. It is the one transceiver that I haven't gotten to use much. So, before I would write any compare/contrast comment, I'd want to do 20-30 searchs with the Pulse.

Halsted

[Yossarian]

Summit, I think I follow.

So, here's a wild idea for the next gen after this.
We all carry two items as part of a "beacon system", not one.

Our future beacon is like the S1, only it has a detachable or separate transmitter/receiver that you have with you in the field.

You start your search as normal, then when you get a strong consistent signal and go to phase two of the search, you detach the extra receiver-transmitter from the main (at which point it goes live), and THROW IT way down field diagonally towards and to the side of where you're heading. The main body has the processor, and now gets buried transceiver info from both itself and the satellite receiver-transmitter. Software should even be smart enough to recognize the satellite signal and allow anyone else with the same system to use the extra signal as well.

Switch to search, run, run, acquire, detach and toss satellite, wait 10 seconds, bam! Straight line to body, pinpoint circles, flag as found, on to the next.

?

Hell, if it can be made to work with one satellite, why not more? Data processing is relatively speaking cheaper and cheaper these days.
Detach two satellites, throw one left, one right, wait 5 seconds, go right to body.

Edit: and/or have an option to use multiple searchers as part of the satellite network

[summit]

extra receiver-transmitter from the main (at which point it goes live), and THROW IT way downfield diagonally towards and to the side of where you're heading. The main body has the processor, and now gets buried transceiver info from both itself and the satellite receiver-transmitter. Software should even be smart enough to recognize the satellite signal and allow anyone else with the same system to use the extra signal as well.

Switch to search, run, run, acquire, detach and toss satellite, wait 10 seconds, bam! Straight line to body, pinpoint circles, flag as found, on to the next.

?

Hell, if it can be made to work with one satellite, why not more? Data processing is relatively speaking cheaper and cheaper these days.
Detach two satellites, throw one left, one right, wait 5 seconds, go right to body.

Interesting thought and goes along the lines of my sensor fusion post from last year:

http://www.tetongravity.com/forums/s...81&postcount=6

I think the sensor fusion is brilliant. Encode the identity of the received beacon signals, broadcast that to the other beacons with one tagged as as that particular beacon's search target.

It kind of reminds me of how the military can have newer fighters see what their wingman's radar sees.To take that idea further: if you integrated GPS into the beacons, the searching beacons could communicate their coordinates and the relative locations of the buried signals for more precision, triangulation, and extended search range. Maybe that is in the next model. You could even make a pro search only model with larger antennas and amplifies for long range. It could be used by ski patrol/SAR/helicopters. It could radio link as stated above, working like a AWACS, showing all the little normal beacons the big picture, and relaying lockon information as well. (Barryvox, if you use these ideas from reading them here, I expect you to send me a free beacon!)

The satellite beacon idea you propose has potential but many complications because users must:
purchase and not lose these extra sensor/relay units,
must pull out, activate, then throw theh units and wait for them to activate and link up
the units must know where they are and how they are oriented (they will have to have GPS and a compass)
the units hopefully will not end up in useless positions

Linking each users beacon for sensor fusion as I described is probably a simpler and cheaper method that giving each user additional sensor/relay satellite units to throw around. On the other hand, my idea would require multiple searchers with compatible beacons to be effective where as your method only requires one beacon and one searcher /w at least one properly placed satellite.

[Yossarian]

in fact, you don't even have to throw the satellites.

You can just place them/it on the ground as you go, leaving them/it behind for triangulation with your on-body main processor.

if you're already moving in a straight line to the body, great, but otherwise you'll start to curve on the flux, and the more you curve, the better the triangulation with the satellite system left behind would be, which, via your on-board CPU would then direct you in a faster/straighter line to the right final destination.


EDIT: was writing my post as you were writing yours... Nice, I like your idea, and agree with your points... Very interesting...

EDIT EDIT: okay, maybe a slightly smarter placement of my satellites is needed. You detach from the main, it goes live, you already know the flux line direction because the main is following it, you ALIGN the satellite as you place via some alignment readout/process between satellite and main? Anyway...