Skip to main content

hammock suspension systems

I am far from being an expert hammock or hammock suspension person, however, I slept at a Holiday Inn last night... Actually I'm not qualified and I'm not trying to substitute my wisdom for yours I'm just calling it like I see it.

I have a number of hammock suspension systems to evaluate and I'm not expecting to break new ground as this sort of thing has been researched and written about to death. My hypothesis is that any simple gathered end hammock can be suspended by a plain webbing or cordage (properly rated of course). And with enough practice the number of fine adjustments should be minimal.

I have a number of suspension systems:

  • ENO Atlas Straps
  • ENO Helios
  • Whoopie Sling with Soft Shackle
  • plain webbing
  • plain para-max
  • plain 550 paracord
I'm not going to test the paracord because the para-max is just a stronger version of the same.

The weigh in:
  • Atlas - 180g
  • Whoopie Sling - 20g
  • webbing - 80g
  • paramax - 100g
The weight of the Atlas strap was expected. It's a thicker strap and in the loop section the material is essentially  doubled.


Capacity:
  • Atlas - 300lbs
  • Helios - 300lbs
  • Whoopie Sling - 3000lbs
  • webbing - 3500lbs
  • paramax - 1000lbs
The complete System:
  • Atlas - needs a carabiner
  • Whoopie - needs a tree huger
  • webbing - as is
  • paramax - as is
You can always get complicated with the webbing or paramax by adding buckles and so on but that complicates the system and creates additional failure opportunities.

Installation and Adjustment:
  • Atlas - wrap the strap around the tree at the right height and using the carabiner select the hang.
  • Whoopie - decide if you're going to replace the gathered end of the hammock and if not then you have one knot on the hammock side; then a strap around the tree and then a marlin-spike. Adjustments are made by pulling on one end or the other.
  • webbing - a figure 8 knot on one end and around the tree. and a slippery-becket-hitch to the gathered end once or twice for the perfect hang. Adjustments are made by resetting the becket-hitch.
  • paramax - just like the webbing
Observations

Looking closely at the different suspension systems I made some observations. Even though there is something to be said for a proper commercial entity behind a product like the Atlas straps there is a very good chance that it's just a branded accessory. It's just a matter to scan Amazon for the number of similar suspension systems.

The whoopie sling seems un-commercial. Regardless of the qualify of materials the presentation in the packaging was not all that fantastic and unless I had made the product myself I could not be sure that it was amsteel. Some amsteel products are sold as winch or towline replacements. This just does not feel right.

The webbing packs up smaller than the paramax but is limited to this one use. 

The paramax might have multiple uses. One possible configuration could be an all-in-one ridgeline and suspension although this is a little complicated to hang and adjust.

Cost
  • Atlas - $30
  • Helios - $35
  • Whoopie - $20 (but incomplete)
  • webbing - $7 for 30ft
  • paramax - $19 for 50ft
Tests:

I tested the Atlas with an ENO DoubleNest last week and did not experience anything special. The positioning of the loops meant that fine tuning had to be accomplished by raising or lowering the tree straps.

Today I tested a Yukon Featherlite with the webbing and paramax suspension systems. Tuning the suspension was as simple as re-positioning the becket-hitch (or sheet bend).


webbing wrapped around the tree with a figure 8 loop

paramax attached to the tree with a figure 8 loop
One thing I noticed when I disassembled the hammock was that the loop and the working end on the tree wrap seemed to be fused. Once I realized what happened they pealed away.

slippery double sheet bend
I thought this was a proper double but it's not. This knot worked but was not slippery. It took some finesse to undo.

slippery sheet bend
The sheet bend knot got turned inside out with both ends being webbing. This also happened on the paramax side and so I did a double there. I was not at all discouraged with the time or effort it took to get the hammock and suspension adjusted. It was clearly as fast as the Atlas or Whoopie but took no more or less adjustments. (this was the first hang for the Yukon hammock so I had to contend with sag and stretching.

Conclusion:

I appreciate that people, me included, need to collect things. In a previous post I indicated how many bushcraft knives I purchased... and so I effectively have 4 hammock suspension systems. Some people collect 3rd party libraries (programmer humor) and others lightweight suspension systems. It probably has more to do with being braggadocios than practical.

As for which suspension is preferred let's start with least preferred.

The Atlas is least preferred because it's heavy, while it has capacity for the hammock it might fail if used for something else, and the pack volume.

The Whoopie sling is a least favorite too. I cannot confirm that it's actually amsteel and even with the some confidence there are many moving parts. Regardless of it's weight advantage  I would question it's durability or even field repair. I suppose any side or both could be replaced with any of the other systems if necessary. Having not used this system I lack the necessary confidence which I will have to work on.

I think I would prefer a single material solution whether it's paramax or webbing. That the webbing seemed to turn inside out is troubling. As I was taking the system apart I almost opted to cut the strap but finally worked it free. With all due respect to the tree people I think the winner is going to be a double wrap paramax although I'm also going to test the Whoopie. So stay tuned This could change.

More testing:

attached to the tree
 I think that because I doubled the cordage the paramax did not fuse like the previous test.
with the soft buckle

the whoopie sing was wrapped in the gathered end of the hammock
I do not particularly like the diameter of the sling and the hammock material. I think the force is distributed but as the cordage and webbing fused in the previous test I'm certain there is a point at which the sling will cut the gathered end. And as I was removing the sling from the gathered end I discovered just how taut the sling was.

I decided to test the Whoopie sling anyway. First I tried the marlin-spike and that was a FAIL. [a] because it's subject to the wind. There was a slight breeze and the whoopie landed on the ground. Had I been hammocking in the Everglades the hammock and I would be soaked. [b] In my case as soon as I put my weight on the hammock the spike broke and I landed on my ass. I'm confident I was in the correct position. [c] I still had to use a good amount of cordage to wrap around the tree. [d] I used the soft buckle but I found it to be unreliable looking... but they worked.

And the winner is...

paramax cordage with a double sheet bend and the existing webbing on the yukon featherlight.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…