PP Loses all profiles after not charging for 3 months
PP Loses all profiles after not charging for 3 months
I use different bike in summer with Garmin Rally Pedal DFPS. Came back to my other bike which has PP mounted and spun sensors pressed button flashed green then constant red then I turned it off since when this has happened before I get a ride listing power as zero throughout -- sort of a bummer! In Isaac there are no Profiles coming from the device. Does the device actually not keep the Profiles in NVRAM??
Re: PP Loses all profiles after not charging for 3 months
Yes, profiles are stored in NVRAM.
Do a hard reset of your unit (press-hold button for 12 seconds, until light goes out briefly and then resumes flashing, then let go of button).
Try searching for your profiles afterwards; they should be there.
Do a hard reset of your unit (press-hold button for 12 seconds, until light goes out briefly and then resumes flashing, then let go of button).
Try searching for your profiles afterwards; they should be there.
John Hamann
Re: PP Loses all profiles after not charging for 3 months
Thanks for the quick reply. I'll try that. And if I do that and set the previous working profile as active, will I be again forced to do a cal ride or will it "just work," in the words of Steve Jobs?
-
lorduintah
- Posts: 659
- Joined: Fri Jan 11, 2008 9:37 am
- Location: Plymouth, MN
Re: PP Loses all profiles after not charging for 3 months
Previous rides? Even from 3 months ago. there could be another source to recover PP profiles.
Old ride files might also have the profile, if nothing else changed on the bike/rider.
Or am I mistaken? The first choice would be the PP NVRAM, then a fall back would be old ride files.
NVRAM will not necessarily permanently retain the data. The technology of each variation of NVRAM and the details of the process used to construct the memory will influence the length of data retention. If could range from a few days to many years, if it was produced with essentially defect free methods, the data can be "non-volatile." Of course old ride files are probably stored in some form of nonvolatile media, too.
Tom
Old ride files might also have the profile, if nothing else changed on the bike/rider.
Or am I mistaken? The first choice would be the PP NVRAM, then a fall back would be old ride files.
NVRAM will not necessarily permanently retain the data. The technology of each variation of NVRAM and the details of the process used to construct the memory will influence the length of data retention. If could range from a few days to many years, if it was produced with essentially defect free methods, the data can be "non-volatile." Of course old ride files are probably stored in some form of nonvolatile media, too.
Tom
Re: PP Loses all profiles after not charging for 3 months
You're correct that old ride files store the profile data used to create them. Open an older ride file, select Edit/Edit Profiles", and click "Extract from Ride File".lorduintah wrote: ↑Mon Oct 21, 2024 10:31 pm Previous rides? Even from 3 months ago. there could be another source to recover PP profiles.
Old ride files might also have the profile, if nothing else changed on the bike/rider.
Or am I mistaken? The first choice would be the PP NVRAM, then a fall back would be old ride files.
NVRAM will not necessarily permanently retain the data. The technology of each variation of NVRAM and the details of the process used to construct the memory will influence the length of data retention. If could range from a few days to many years, if it was produced with essentially defect free methods, the data can be "non-volatile." Of course old ride files are probably stored in some form of nonvolatile media, too.
Tom
John Hamann
Re: PP Loses all profiles after not charging for 3 months
At this point I'm done. Been a PP user since the beginning but this just doesn't work have reset it now three times, no previous profiles found when looking via Isaac, and when I set a new profile for a better but not best accuracy hoping to be able to go out and ride, I press the button, spin everything up but just solid red. Can I just send the thing back to you for repair?
Re: PP Loses all profiles after not charging for 3 months
Sorry you're still having problems. Please email technicalsupport@velocomp.com for next steps.Speedyg wrote: ↑Thu Oct 31, 2024 5:15 pm At this point I'm done. Been a PP user since the beginning but this just doesn't work have reset it now three times, no previous profiles found when looking via Isaac, and when I set a new profile for a better but not best accuracy hoping to be able to go out and ride, I press the button, spin everything up but just solid red. Can I just send the thing back to you for repair?
John Hamann
Re: PP Loses all profiles after not charging for 3 months
The NVRAM should last a year without power, so I think that's unlikely to be the problem.
I think I know what's going on though. Versions of the firmware prior to 10.01 (released October 19th) had a bug relating to ANT pairing.
Basically, if the device was turned on, and the speed sensor wasn't awake, it would look for other sensors in case it could find one matching another profile. During this search it would look for power sensors, in case it could find a wheel based torque sensor which could provide speed information.
The bug was that if it found a power sensor, it would add it to the current profile, and force a new calibration ride. Usually, it would then find that that power sensor wasn't a wheel-based torque sensor, or didn't match any of the other profiles, and so ignore it and carry on searching. But at that point it was too late.
You said you were riding a different bike with its own power sensor over the summer. My guess is that at some point, the PP was awake, its speed sensor wasn't, and it saw your other power sensor.
Btw, I understand your frustration - I got a second PP for my wife, and every time we rode together, one or the other (or both) of our PPs went into calibration mode (because they found the other PP, triggering the bug). Fortunately I had saved profiles in Velocomp Aero, so it was easy to restore - but it would just happen again the next time we rode together.
Anyway, that bug is now fixed, so my suggestion (if you haven't already) would be to download and install Velocomp Aero, then run it, connect your PP, and follow the prompt to update the firmware.
After that, if you have a saved profile, install it. Otherwise, if you have a saved ride, you should be able to extract a profile from that, and install it. But if not here's what you can do.
Spin up your sensors on the bike, then do a 4 second press on the PP's button to trigger pairing, and let it pair. Ideally you would now do a cal ride, but if you don't want to, you can connect to VA again, go to the "Device -> Configure Device..." menu, then select "Setup Calibration" from the "config" popup at the top. It should tell you "Device Needs a Calibration Ride", with a popup underneath to select where the device is mounted. Choose the right option, hit "Configure Manually", and you should be ready to go.
Note that this uses a "default" wind scaling factor that may not be ideal for your setup. You can use an out-and-back, or round trip ride to calibrate it in V.Aero. Open the ride, select the laps corresponding to the out-and-back or round trip (or all the laps), then right click to popup a context menu, and choose "Calibrate Wind Scaling". It will tell you the wind scaling factor (and give you the option to update the ride based on that). You can then manually copy the wind scaling factor into the profile (via Edit->Edit Profiles-Advanced), and send it to the device.
I think I know what's going on though. Versions of the firmware prior to 10.01 (released October 19th) had a bug relating to ANT pairing.
Basically, if the device was turned on, and the speed sensor wasn't awake, it would look for other sensors in case it could find one matching another profile. During this search it would look for power sensors, in case it could find a wheel based torque sensor which could provide speed information.
The bug was that if it found a power sensor, it would add it to the current profile, and force a new calibration ride. Usually, it would then find that that power sensor wasn't a wheel-based torque sensor, or didn't match any of the other profiles, and so ignore it and carry on searching. But at that point it was too late.
You said you were riding a different bike with its own power sensor over the summer. My guess is that at some point, the PP was awake, its speed sensor wasn't, and it saw your other power sensor.
Btw, I understand your frustration - I got a second PP for my wife, and every time we rode together, one or the other (or both) of our PPs went into calibration mode (because they found the other PP, triggering the bug). Fortunately I had saved profiles in Velocomp Aero, so it was easy to restore - but it would just happen again the next time we rode together.
Anyway, that bug is now fixed, so my suggestion (if you haven't already) would be to download and install Velocomp Aero, then run it, connect your PP, and follow the prompt to update the firmware.
After that, if you have a saved profile, install it. Otherwise, if you have a saved ride, you should be able to extract a profile from that, and install it. But if not here's what you can do.
Spin up your sensors on the bike, then do a 4 second press on the PP's button to trigger pairing, and let it pair. Ideally you would now do a cal ride, but if you don't want to, you can connect to VA again, go to the "Device -> Configure Device..." menu, then select "Setup Calibration" from the "config" popup at the top. It should tell you "Device Needs a Calibration Ride", with a popup underneath to select where the device is mounted. Choose the right option, hit "Configure Manually", and you should be ready to go.
Note that this uses a "default" wind scaling factor that may not be ideal for your setup. You can use an out-and-back, or round trip ride to calibrate it in V.Aero. Open the ride, select the laps corresponding to the out-and-back or round trip (or all the laps), then right click to popup a context menu, and choose "Calibrate Wind Scaling". It will tell you the wind scaling factor (and give you the option to update the ride based on that). You can then manually copy the wind scaling factor into the profile (via Edit->Edit Profiles-Advanced), and send it to the device.