Genzod
Banned
- Joined
- Apr 25, 2017
- Messages
- 392
I'm considering getting the ZL-H32w as a headlamp for extended trail running (through the night) that employs mail drops along the way. It's important to me to conserve battery consumption to keep pack lightweight, so running with the lamp on maximum like urban runners might do on a 45 minute jog is not an option.
What I would like to do is fill the profile up with certain useful outputs and click through them without having to twist my brain every time I need more light or need to reduce it to conserve battery.
In most instances, I would be using the 50 lm level for uphill, level and downhill running. At times that the trail becomes increasingly technical or slippery, I would want the option of of 100 and 245 lm, for level and downhill situations respectively.
I would need 446 lm for searching trail blaze markers in the distance when I think I might have wandered off the trail. I think 8.5 lm would do well for water collection and other zero progress activities not involving running, and I think I would use the 2.5 lm setting when I stop to check a trail guide or a map. The only other useful level of light I see is 22 lm.
I'm not too savvy on how the UI works just yet. I think what I have available to me at anyone time is a set of H1, M1 and L1, and a set of H2, M2 and L2, no more than 6 settings at a time.
The 100 and 245 lm settings are in the same H2 sublevel set of options. The 22 lm and 8.5 lumen options are in the same M2 sublevel set of options.
Can I create a profile of 6 settings with the settings I specified? If you were clicking back and forth between 50 and 100 and 2.5 a lot, and rarely using 22, 245 and 446, how might you set that profile up to make the switching less of a mindful task?
If I can't get the profile I'd like, particularly with both 100 and 245 lm simultaneously, it seems I can have the choice of three high level options with the newer expanded programability of the H53 generation. Is that correct?
For convenient reference:
Light Output (runtimes)
What I would like to do is fill the profile up with certain useful outputs and click through them without having to twist my brain every time I need more light or need to reduce it to conserve battery.
In most instances, I would be using the 50 lm level for uphill, level and downhill running. At times that the trail becomes increasingly technical or slippery, I would want the option of of 100 and 245 lm, for level and downhill situations respectively.
I would need 446 lm for searching trail blaze markers in the distance when I think I might have wandered off the trail. I think 8.5 lm would do well for water collection and other zero progress activities not involving running, and I think I would use the 2.5 lm setting when I stop to check a trail guide or a map. The only other useful level of light I see is 22 lm.
I'm not too savvy on how the UI works just yet. I think what I have available to me at anyone time is a set of H1, M1 and L1, and a set of H2, M2 and L2, no more than 6 settings at a time.
The 100 and 245 lm settings are in the same H2 sublevel set of options. The 22 lm and 8.5 lumen options are in the same M2 sublevel set of options.
Can I create a profile of 6 settings with the settings I specified? If you were clicking back and forth between 50 and 100 and 2.5 a lot, and rarely using 22, 245 and 446, how might you set that profile up to make the switching less of a mindful task?
If I can't get the profile I'd like, particularly with both 100 and 245 lm simultaneously, it seems I can have the choice of three high level options with the newer expanded programability of the H53 generation. Is that correct?
For convenient reference:
Light Output (runtimes)
- High: H1 446 Lm (PID, approx 1.4 hr) or H2 245 Lm (1.6 hrs) / 100 Lm (4.1 hrs)
- Medium: M1 50 Lm (11 hrs) or M2 22 Lm (26 hrs) / 8.5 Lm (70 hrs)
- Low: L1 2.5 Lm (8 days) or L2 0.37 Lm (38 days) / 0.05 Lm (2.5 months) / 0.01 Lm (3 months)
Last edited: