| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 23 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 57:10:19 |
| Calls: | 584 |
| Calls today: | 1 |
| Files: | 1,139 |
| D/L today: |
179 files (27,921K bytes) |
| Messages: | 112,136 |
V1 WahooAs are having a hard few days, essentially waiting on a firmware >update! As they have fairly significant bug.
<https://www.dcrainmaker.com/2025/08/wahoo-bolt-roam-v1-gps-units-reset-20-years-back-become-unusuable.html>
Roger Merriman
On 19 Aug 2025 20:11:31 GMT, Roger Merriman <roger@sarlet.com> wrote:
V1 WahooAs are having a hard few days, essentially waiting on a firmware >>update! As they have fairly significant bug.
<https://www.dcrainmaker.com/2025/08/wahoo-bolt-roam-v1-gps-units-reset-20-years-back-become-unusuable.html>
Roger Merriman
Thanks. More updates: ><https://support.wahoofitness.com/hc/en-us/articles/28876447336210-ELEMNT-BOLT-1-and-ROAM-1-GPS-data-and-ride-recording-issues-August-17-and-later>
On Tue, 19 Aug 2025 18:58:54 -0700, Jeff Liebermann <jeffl@cruzio.com>
wrote:
On 19 Aug 2025 20:11:31 GMT, Roger Merriman <roger@sarlet.com> wrote:
V1 Wahoo-As are having a hard few days, essentially waiting on a firmware >>> update! As they have fairly significant bug.
<https://www.dcrainmaker.com/2025/08/wahoo-bolt-roam-v1-gps-units-reset-20-years-back-become-unusuable.html>
Roger Merriman
Thanks. More updates:
<https://support.wahoofitness.com/hc/en-us/articles/28876447336210-ELEMNT-BOLT-1-and-ROAM-1-GPS-data-and-ride-recording-issues-August-17-and-later>
Y2K strikes again. From the above update page:
"We now fully understand the root cause of the issue relating to older
first generation devices, which use a limited 10-bit system to track
GPS time."
It's nice to see a company that is transparent and keeps its customers informed when a problem is found.
Jeff Liebermann <jeffl@cruzio.com> wrote:
On Tue, 19 Aug 2025 18:58:54 -0700, Jeff Liebermann <jeffl@cruzio.com>Indeed IAm not sure what Garmin would do the xx30 line hasnAt had any
wrote:
On 19 Aug 2025 20:11:31 GMT, Roger Merriman <roger@sarlet.com> wrote:
V1 Wahoo?s are having a hard few days, essentially waiting on a firmware >>>> update! As they have fairly significant bug.
<https://www.dcrainmaker.com/2025/08/wahoo-bolt-roam-v1-gps-units-reset-20-years-back-become-unusuable.html>
Roger Merriman
Thanks. More updates:
<https://support.wahoofitness.com/hc/en-us/articles/28876447336210-ELEMNT-BOLT-1-and-ROAM-1-GPS-data-and-ride-recording-issues-August-17-and-later>
Y2K strikes again. From the above update page:
"We now fully understand the root cause of the issue relating to older
first generation devices, which use a limited 10-bit system to track
GPS time."
It's nice to see a company that is transparent and keeps its customers
informed when a problem is found.
system updates for quite some time now, I get the impression that Wahoo is
a smaller company.
Curiously of the folks I know with V1 WahooAs one mates unit is fine or at >least it was last night! All the others failed as you were.--
Roger Merriman
On 21 Aug 2025 08:53:13 GMT, Roger Merriman <roger@sarlet.com> wrote:
Jeff Liebermann <jeffl@cruzio.com> wrote:
On Tue, 19 Aug 2025 18:58:54 -0700, Jeff Liebermann <jeffl@cruzio.com>Indeed IrCOm not sure what Garmin would do the xx30 line hasnrCOt had any
wrote:
On 19 Aug 2025 20:11:31 GMT, Roger Merriman <roger@sarlet.com> wrote:
V1 Wahoo?s are having a hard few days, essentially waiting on a firmware >>>>> update! As they have fairly significant bug.
<https://www.dcrainmaker.com/2025/08/wahoo-bolt-roam-v1-gps-units-reset-20-years-back-become-unusuable.html>
Roger Merriman
Thanks. More updates:
<https://support.wahoofitness.com/hc/en-us/articles/28876447336210-ELEMNT-BOLT-1-and-ROAM-1-GPS-data-and-ride-recording-issues-August-17-and-later>
Y2K strikes again. From the above update page:
"We now fully understand the root cause of the issue relating to older
first generation devices, which use a limited 10-bit system to track
GPS time."
It's nice to see a company that is transparent and keeps its customers
informed when a problem is found.
system updates for quite some time now, I get the impression that Wahoo is >> a smaller company.
Wahoo has 200 to 300 employees according to: <https://en.wikipedia.org/wiki/Wahoo_Fitness>
Founded in 2009.
Garmin has 22,000 employees according to: <https://en.wikipedia.org/wiki/Garmin>
Founded in 1989.
Most large companies, including Garmin, will not fix problems in their products that they no longer sell. Small companies tend to extend
lifetime warranties much longer because most buyers will avoid buying products from a company that abandons their early adopters.
"All You Need to Know about the GPS / GNSS Week Number Rollover" <https://www.septentrio.com/en/learn-more/insights/all-you-need-know-about-gps-gnss-week-number-rollover>
"In the 1970s, when the GPS system was originally designed, 10 bits
were assigned to the week number in the navigation data. As a result,
the transmitted week number can have a value from 0 to 1023 (= 210 -
1). After the maximum value is reached, the week number "rolls over"
to 0 and starts counting again. So the transmitted week number jumps
back to zero every 1024 weeks (about 20 years)."
There was a "roll over" in April 2019, 6 years ago. Why didn't anyone
at Wahoo notice? Also, the "roll over" problem was allegedly solved
in 1993. I'm beginning to have some doubts about whether that problem
was really due to "a limited 10-bit system".
Similar issue with different underlying cause: Unix time 'Epochalypse'.
Unix time (epoch) started on 01.01.1970 as a 32 bit integer. The year
2038 (specifically 3:14:07 AM on Jan 19, 2038 UTC (GMT)) is being
referred to as the "Epochalypse". Any system that uses Unix time with
the 32 bit architecture will have an 'integer overflow' that flips the >number from positive to negative, resulting in a date that is 2^31
seconds _before_ the base unix time, or 8:45:52 PM, 13 december 1901.
(...)
On Thu, 21 Aug 2025 12:41:42 -0400, zen cycle
<funkmasterxx@hotmail.com> wrote:
Similar issue with different underlying cause: Unix time 'Epochalypse'.
Unix time (epoch) started on 01.01.1970 as a 32 bit integer. The year
2038 (specifically 3:14:07 AM on Jan 19, 2038 UTC (GMT)) is being
referred to as the "Epochalypse". Any system that uses Unix time with
the 32 bit architecture will have an 'integer overflow' that flips the
number from positive to negative, resulting in a date that is 2^31
seconds _before_ the base unix time, or 8:45:52 PM, 13 december 1901.
(...)
Thanks for the explanation. The 2038 problem is just one of many date related land mines buried along the road to computing nirvana. Here's
a list of past and future computational date and time storage issues:
"Time formatting and storage bugs" <https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs>
My Garmin GPS-76 may have succumbed to a GPS computation error in
2019: <https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Second_GPS_rollover>
"GPS week number rollover" <https://en.wikipedia.org/wiki/GPS_week_number_rollover>
Notice that the Unix 2038 time problem might appear in 2036 on some
devices: <https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2036>
Considering the history, I would expect such problems to continue
until the end of civilization.
On 8/21/2025 11:33 AM, Jeff Liebermann wrote:My company sold a Supply-Chain-Planning software with a max_date of
On 21 Aug 2025 08:53:13 GMT, Roger Merriman <roger@sarlet.com> wrote:
Jeff Liebermann <jeffl@cruzio.com> wrote:
On Tue, 19 Aug 2025 18:58:54 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>> wrote:Indeed IrCOm not sure what Garmin would do the xx30 line hasnrCOt had any >>> system updates for quite some time now, I get the impression that
On 19 Aug 2025 20:11:31 GMT, Roger Merriman <roger@sarlet.com> wrote: >>>>>
V1 Wahoo?s are having a hard few days, essentially waiting on a
firmware
update! As they have fairly significant bug.
<https://www.dcrainmaker.com/2025/08/wahoo-bolt-roam-v1-gps-units- >>>>>> reset-20-years-back-become-unusuable.html>
Roger Merriman
Thanks.-a More updates:
<https://support.wahoofitness.com/hc/en-us/articles/28876447336210- >>>>> ELEMNT-BOLT-1-and-ROAM-1-GPS-data-and-ride-recording-issues-
August-17-and-later>
Y2K strikes again.-a From the above update page:
"We now fully understand the root cause of the issue relating to older >>>> first generation devices, which use a limited 10-bit system to track
GPS time."
It's nice to see a company that is transparent and keeps its customers >>>> informed when a problem is found.
Wahoo is
a smaller company.
Wahoo has 200 to 300 employees according to:
<https://en.wikipedia.org/wiki/Wahoo_Fitness>
Founded in 2009.
Garmin has 22,000 employees according to:
<https://en.wikipedia.org/wiki/Garmin>
Founded in 1989.
Most large companies, including Garmin, will not fix problems in their
products that they no longer sell.-a Small companies tend to extend
lifetime warranties much longer because most buyers will avoid buying
products from a company that abandons their early adopters.
"All You Need to Know about the GPS / GNSS Week Number Rollover"
<https://www.septentrio.com/en/learn-more/insights/all-you-need-know-
about-gps-gnss-week-number-rollover>
"In the 1970s, when the GPS system was originally designed, 10 bits
were assigned to the week number in the navigation data. As a result,
the transmitted week number can have a value from 0 to 1023 (= 210 -
1). After the maximum value is reached, the week number "rolls over"
to 0 and starts counting again. So the transmitted week number jumps
back to zero every 1024 weeks (about 20 years)."
There was a "roll over" in April 2019, 6 years ago.-a Why didn't anyone
at Wahoo notice?-a Also, the "roll over" problem was allegedly solved
in 1993.-a I'm beginning to have some doubts about whether that problem
was really due to "a limited 10-bit system".
Similar issue with different underlying cause: Unix time 'Epochalypse'.
Unix time (epoch) started on 01.01.1970 as a 32 bit integer. The year
2038 (specifically 3:14:07 AM on Jan 19, 2038 UTC (GMT)) is being
referred to as the "Epochalypse".