1.320.1298 update the removal of the "Built-in GPS"
Answered
With the 1.320.1298 update the removal of the "Built-in GPS" on the sensor page creates a problem. I have a combination cadence/speed sensor on my Trek Domane. I have not been utilizing the speed aspect, just the cadence aspect. With the removal of the Built-in GPS I no longer get speed, distance or average speed. Prior to the update by moving the Built-in GPS to the top of the sensor listing, I was able to get all of the speed functions.
Now I need to find a magnet to attach to the wheel to get the speed function back.
Any work around other than adding a magnet to the wheel?
-
In this release:
Added Options for Combined Speed/Cadence SensorsWe’ve introduced the ability to select the data you want your combined speed/cadence sensor to provide (speed, cadence, or both). This is particularly useful if you only want your combined speed/cadence sensor to provide cadence on outdoor rides. Go to the sensor’s Details page on Karoo to configure this setting for each of your combined speed/cadence sensors.
-
Hi @Ali
the Fazua system was previously supported flawlessly. Power and cadence were displayed correctly. speed was used by build-in-gps.
everything fine until the update with the removal of build-in-gps.i even recommended the hammerhead karoo 2 several times in the fazua facebook group.
I would even do without the new features if I could install the old version. but even that is incapable of hammerhead. sorry if I have to mention this choice of words. you can see it here in the comments and solution implementations. you just don't know what you're doing there.
It would have been clever to be able to switch each individual part of a multi-sensor on and off. regardless of whether the sensor offers 2 or 4 sub-sensors. instead a dirty hack was implemented, which only works with a certain double sensor.
with best regards,
-
@Stephen
that would also be an option. if you have already made sensors selectable for profiles, you could also select (and prioritize) the "build-in-gps" sensor there.
there are enough ideas/options that are easy to implement - to use this system flexibly.
the solution chosen by hammerhead was the worst of all possibilities. with all the consequences that the error is still there and the karoo 2 has suddenly become unusable for some users.
-
to make it clear again:
there is a triple bluetooth sensor (speed, cadence, power).
if I deactivate it because I want/must have speed from gps, then I miss cadence and power.
if i deactivate the sensor, i can get speed from gps and need another sensor for cadence. power is still unavailable.Unfortunately, I can't leave the sensor active because the speed value isn't accepted cleanly. this makes all recordings unusable in terms of speed and length.
and that's exactly what makes the karoo 2 really useless now.
it's not enough to install a cadence sensor. a power meter is a much more expensive purchase.the functionality with the fazua system was one of the reasons why i chose this bike computer. garmin and sigma also offer nice computers, e.g. fully supports fazua even in the cheap Rox 4.0. but then I have no decent navigation.
A vicious circle.and all caused by an update, which you can't undo. I'm not really interested in the new features. somehow give me the old version and i'll be happy again and able to use the bike computer for what it's meant to do. so it is now a paperweight.
-
Has the speed/cadence conflict really been fixed? I am using a DuoTrap and am selecting the sensor on my Hammerhead. I'm not seeing any additional settings to choose there, other than to select what Profiles I want it to work with. Where is the ability to deselect Speed as a sensor? It is still showing Speed and Cadence "connected" in that menu.
-
@Steve. This is just the way of the senseless censored sensor app.
You are a another victim of The Grim Repair.
See the " Sensor Connection Stability and Troubleshooting" podcast. Fascinating discussion of the issues involve.
Oh that's right , they haven't done one.
Really , though , we need a discussion on this, sensor loss, drop and intermittent function and connectivity plague all devices and annoy bigly. 20% of my rides to some degree, though most small and easy to correct if not self correcting. Stable connection and recording are a core function and a big deal.
-
Am I missing something or the issue is still there for fazua 50 evation which is only BLE as the ability to choose if we want the speed or not is only possible with ANT+ connectivity ? I still have to disable totally my bike from the sensors list since this update. That’s a shame ! I really hope I missed something.
-
Hi Bruno,
unfortunately the problem still exists. My inquiries just say it has been reported to the product team and will be fixed with the future e-bike support feature.The problem is actually explained very quickly.
The Fazu Bluetooth Sensor provides 3 values:
cadence
power
speedSpeed causes the problems.
Before the unfortunate update, you could prioritize GPS speed and push it up so that speed from the Fazua sensor wasn't used. Cadence and power, on the other hand, do.
This is not possible after the update and Speed ensures that the distance and speed are not displayed correctly and the recordings of the rides are therefore unusable.A workaround is to buy a separate speed sensor and use that. Of course, it doesn't make sense, since you actually have a GPS computer that should be able to do it much better.
-
Also made terrible experience with FAZUA Integration.
Power and Cardance wird well, speed via Fazu seems to be not tested and works bad.
Karoo 2 frequently shows zero.
Hammerhead Software Teams needs to improve sensor fusion and needs to ignore sensors which are not reliable.
If worse sensor fusion leads to wrong speed values this should be treated as a security risk as we need to follow all legal regulations.to increase pressure Hammerhead should sponsor speed sensors to all users which make this bad experience 😁
Minimum expectation would be to allow to turn of bad working sensors manually which shouldn’t be a big issue.
-
You introduced a bug 8 months ago by disabling the sensors precedence, promised to solve it with the e-bikes integration to come. In fact this e-bikes features are just for BLE so do not solve for everyone…
Why not just reintroduce sensors precedence who nobody complained about?
I’m really disappointed
Please sign in to leave a comment.
Comments
45 comments