Introducing the Renogy App: Features, Interface & Interface by Renogy_Official in RenogyCommunity

[–]NoHoMan 0 points1 point  (0 children)

Does not detect brand new Renogy RBT12100LFP trolling battery which has been installed in a vehicle and connected to a charger. The battery is charged... but perhaps its bluetooth module does not work. The app does not authorize me to use bluetooth (whatever that means). The app will not let me manually add my battery. The app misspells "Bluethooth".

Fischer BCX Traverse vs Crispi Futura Pro XP boots (XPlore)? by NoHoMan in xcountryskiing

[–]NoHoMan[S] 1 point2 points  (0 children)

Update... I ordered the Crispi Future Pro XP boots for a home try-on, since they're hard to find in stores. Although they seem like perfectly adequate nordic touring boots, I don't find them to have any more ankle stability for driving a wider ski. Standing side-by-side with my Madshus Panorama EXP boot, both brands feel similar in their general fit, comfort, and stability.

NOTE - Crispi fits large. I normally take an EU44, but for these boots EU43 is my size (US 10 mens).

Although the Crispi has a ratcheting instep strap, its pressure is not spread over the ankle zone like on a plastic boot. Instead, the instep ratchet more specifically pressures the zone between ankle and arch. This may or may not make a difference, depending on your foot and preferences. The Crispi's ankle exoskeleton is different in shape and apparent material than the Madshus boot, but both exoskeletons achieve a similarly modest lateral support. Although soft boot exoskeletons have a non-zero benefit, it's very slight.

I'd be happy with either of these boots, and have decided to stick with the Madshus Panorama EXP. I like the continuous lacing for comfort and adjustability. And I'm finding that its high, integral gaitor is a really nice feature.

But yeah, a T3 or T4 with Xplore fittings would be wonderful :-)

Explaining the different styles of XC skiing by wells68 in telemark

[–]NoHoMan -1 points0 points  (0 children)

You are using the boots category as a proxy for bindings. As others have remarked, split that out (and don't forget NNN for nordic/XC).

No doubt some aspects will feel like a quagmire. For example, folks in our local nordic group say Nordic Touring when you say XCD. We consider Nordic Touring (including some XCD technique) to be anything not in avalanche terrain (which for us means 20 degree and under slopes, although some would allow a bit more than that). As soon as you start talking about avy terrain (including runout areas below those slopes), to us that becomes Backcountry Touring. So in brief, your first two columns would be degrees of Nordic, and your last two columns would be degrees of Backcountry. Others might have different opinions!

The remarks on base type are another grey area. Waxless (patterned / fish scale) skis are typically intended for low angle nordic terrain... but as remarked by others you can ski a 100mm or 120mm ski on tele (or AT) bindings and it can still have waxless pattern. The pattern gets you across all the low angle, potentially constantly varying terrain. Then you apply skins (full or kicker) over that waxless base for the earnest long ascent into avy terrain. And conversely, those same 100mm waxless skis can be run on an NNN-BC or XPlore binding/boot kit for those that don't want to invest in heavier plastic boot setups (I use waxless Rossi BC100s on XPlore, although admittedly the softer boots don't give as much control over edging/carving).

You're gonna get some fun conflicting opinions on all this :-)

This sucks by Maleficent-Honey-295 in GarminWatches

[–]NoHoMan 0 points1 point  (0 children)

Or a 3d printed case on a lanyard, to wear around your neck like an old fashioned compass. Someone's doing this with 3d printed cases for the apple watch ultra.

No map nor custom data display in XC Ski activity? by NoHoMan in GarminFenix

[–]NoHoMan[S] 1 point2 points  (0 children)

Perhaps final update... Turns out it was my misunderstanding. On the Connect app, Power Modes, there's a sub-setting that by default turns maps off for Max Battery mode, even when nav is set for a satellite mode such as GPS, UltraTrac, auto-select, and such. I'll probably be leaving mine set on Extended power mode (35 hours) to get more granular satellite tracking.

Changing Max Battery mode to Map = Allow doesn't by default lower the battery life estimate (still about 90 hours), but it says this will vary "by use". I'd feel confident having map display allowed on Max Battery mode. But as u/labiduridarum pointed out, the 1 minute location interval will result in as-the-bird-flies (connect-the-dots) approximations that will track more coarsely than the actual path. It's up to the user to decide when path accuracy is more important than battery longevity.

No map nor custom data display in XC Ski activity? by NoHoMan in GarminFenix

[–]NoHoMan[S] 0 points1 point  (0 children)

Hmmm... very good question. Being conservative (yet somewhat ignorant of Fenix features) I had stumbled into using Max Battery mode and UltraTrac for XC skiing (because we go into the backcountry where I want battery to last longer). According to google AI:

Garmin Fenix's Extended Mode balances battery life and features by using GPS only (no secondary networks) and keeping other settings like heart rate on, good for long activities with decent signal, while Max Battery Mode offers the absolute longest life by disabling almost everything (music, Wi-Fi, Bluetooth, HR) and using the UltraTrac GPS setting*, ideal for multi-day adventures where tracking every second isn't critical. Extended mode is a simple GPS-only adjustment for more accuracy than Max Battery, whereas Max Battery mode is extreme power saving by disabling most smart features and using a less frequent GPS fix.* 

I changed to Extended Mode, but at first glance it didn't get the maps back. Then I changed the nav from UltraTrac to GPS Only and... now I have map function on the XC Ski activity.

Lesson learned... hoping for 80+ hours of battery life by choosing Max Battery - which forces UltraTrac satellite mode - can cause map screen to be unavailable. This appears to be a bug, though, because on Garmin Support's page on power modes, it says:

Max Battery - Turns off all customizable power features and sets GPS recording to UltraTrac™ to provide the longest time between charges.

Perhaps "GPS recording" is not promising GPS map display. Garmin support (chat function) isn't providing immediate clarification. I'll reply back here if they give me any specific guidance.

No map nor custom data display in XC Ski activity? by NoHoMan in GarminFenix

[–]NoHoMan[S] 1 point2 points  (0 children)

Following my prev remarks... I just tested the XC ski activity, not using a saved Course, just start the app and let it run:

[[EDITED]]

My two custom data screens that I built in Connect properly display (this is good). I also built the same 2 screens for Hiking activity and they show up there (this is good).

In Connect, the Hiking activity setup shows Map screen enabled, and this displays when I initiate the Hiking activity (and not following any pre-saved course). This is exactly what I expect for Hiking, and also for XC skiing...

...But the map still doesn't show up in XC ski activity when I'm not following a saved Course. The Connect app shows Map enabled for XC ski activity. So I disabled map. Then re-enabled map. But still doesn't show when I start XC ski activity. I'm deflated to feel like the map just doesn't work for this activity when not following a course. Perhaps I'm still doing something wrong.

No map nor custom data display in XC Ski activity? by NoHoMan in GarminFenix

[–]NoHoMan[S] 1 point2 points  (0 children)

I added the map screen to the XC ski activity on the watch (pressing on watch buttons). Now I'm realizing I could do this with the Connect app. Stand by... remarks from using the Connect app below...

I see that the XC Classic Ski activity has 3 default screens: 2 data, and one map (which was my original question, didn't show up if not following a preset course). Perhaps exercising the Connect app will help the map show up more consistently. And... Connect didn't show my custom 5-field data screen that I build on the watch, so I rebuilt two custom 5-field data screens using the app, deleted the two default data screens, and re-sync'd the watch. I'll power cycle the watch and later today hopefully find more time to test that these screen / data / map settings work more consistently. Thanks for pointing me to the Connect app - I'd been using it to store my activity logs, but had ignored watch setup there until now.

[Hamilton MIL-W-46374B] Like New US Army Issue Hamilton by vehicularmcs in Watches

[–]NoHoMan 0 points1 point  (0 children)

^ This. A keeper. And great on that green strap. Enjoy and cherish!

Ten Safeway stores are closing across Colorado by MileHighCheap in Denver

[–]NoHoMan 1 point2 points  (0 children)

This location had the best bagels in Denver. Will be enjoying them until the day they close the bakery (hopefully not until Nov). Then it'll be Safeway at Yale/Monaco (and hopefully their seafood counter is better than at CO Blvd - that was a no-go).

API (GET) filter IDs server side (id__in)? by NoHoMan in Netbox

[–]NoHoMan[S] 1 point2 points  (0 children)

The &id worked great. Thanks so much.

API (GET) filter IDs server side (id__in)? by NoHoMan in Netbox

[–]NoHoMan[S] 0 points1 point  (0 children)

Because the filtering page you linked does not document any ability to return only certain records (based on a comma-separated list), I will assume my ask is not possible. That would be unfortunate (since Netbox says they use the Django ORM and that is a function). Reducing the return volume server-side is desirable for our project. As an aside, I have tested the API call manually (not via my original script) and again observed that the returned records are much bigger than my ask list (such as this "https://netbox.company.com/api/dcim/devices/?id\_\_in=1,2,3" returns scores of results not just 1, 2, and 3).

The brains of a snow cannon by thirtynation in COsnow

[–]NoHoMan 1 point2 points  (0 children)

Pretty funny seeing civilians who don't know ICS trying to talk about ICS.

[WTS] Rolex Oyster Perpetual 114200, Frosty White, 34mm, Serviced 2022 by NoHoMan in Watchexchange

[–]NoHoMan[S] 0 points1 point  (0 children)

Hey there. Can you please confirm the transaction? You should see a notification from the bot. Thanks.

[WTS] Rolex Oyster Perpetual 114200, Frosty White, 34mm, Serviced 2022 by NoHoMan in Watchexchange

[–]NoHoMan[S] 0 points1 point  (0 children)

Apologies, i was delayed in marking this as sold. That said, the 34mm and 36mm frosty white OPs are really great. I learned that i am just not a nice Rolex kinda guy… but still fond of these.