PowerStroke and VeloComp Aero

[TdeCampo]

I am missing the elephant in the room!.
I have VC Aero 0.4 and I have the sampling rate for PowerStroke, however I can not find where the PowerStroke is.
Yes if I load Issac is there and works very well but the fact that even the image of PowerStroke is in VC Aero / About indicates that it should be there.
BTW VC Aero is working very well other wise.

[Velocomp]

I am missing the elephant in the room!.
I have VC Aero 0.4 and I have the sampling rate for PowerStroke, however I can not find where the PowerStroke is.
Yes if I load Issac is there and works very well but the fact that even the image of PowerStroke is in VC Aero / About indicates that it should be there.
BTW VC Aero is working very well other wise.

We haven't yet implemented PS in VA. It's coming but timetable is unclear...

[TdeCampo]

John,

Thank you! It works great under Isaac, so it is not a big deal.

[TMWLUK]

Wish to re-activate the question again for PowerStroke and VeloComp Aero. I have a PowerPod V5 with PowerStroke.

I have been analyzing my PowerStroke data on my desktop computer (Windows 10) with Isaac 5.0. I now have a laptop (Windows 11) with which I like to analyze my PP and PS data when I am away from home. I am running Velocomp Aero v1.0.41 software. However, when I "click" the PowerStroke icon to review my HiDef ibr files, I get this message.

No PowerStroke Data to display

But I have no problems viewing the PowerStroke data with the same HiDef ibr files with Isaac. Am I doing something wrong?

[Velocomp]

Wish to re-activate the question again for PowerStroke and VeloComp Aero. I have a PowerPod V5 with PowerStroke.

I have been analyzing my PowerStroke data on my desktop computer (Windows 10) with Isaac 5.0. I now have a laptop (Windows 11) with which I like to analyze my PP and PS data when I am away from home. I am running Velocomp Aero v1.0.41 software. However, when I "click" the PowerStroke icon to review my HiDef ibr files, I get this message.

No PowerStroke Data to display

But I have no problems viewing the PowerStroke data with the same HiDef ibr files with Isaac. Am I doing something wrong?

PowerStroke works just fine with Velocomp Aero. If you have this message then there is no PS data in the particular ride file. If you wish you can confirm this by opening the same file in Isaac.

Make sure your cadence sensor is paired to your PowerPod. Also, in the VA "Device/Configure Device/Set Sample Rate" window, make sure PowerStroke is checked.

[TMWLUK]

Wish to re-activate the question again for PowerStroke and VeloComp Aero. I have a PowerPod V5 with PowerStroke.

I have been analyzing my PowerStroke data on my desktop computer (Windows 10) with Isaac 5.0. I now have a laptop (Windows 11) with which I like to analyze my PP and PS data when I am away from home. I am running Velocomp Aero v1.0.41 software. However, when I "click" the PowerStroke icon to review my HiDef ibr files, I get this message.

No PowerStroke Data to display

But I have no problems viewing the PowerStroke data with the same HiDef ibr files with Isaac. Am I doing something wrong?

PowerStroke works just fine with Velocomp Aero. If you have this message then there is no PS data in the particular ride file. If you wish you can confirm this by opening the same file in Isaac.

Make sure your cadence sensor is paired to your PowerPod. Also, in the VA "Device/Configure Device/Set Sample Rate" window, make sure PowerStroke is checked.

Glad to hear PowerStroke works with Velocomp Aero. It must be something I missed.
The two attached ibr files' PowerStroke data worked well with Isaac 5.1.0 but when I open them in VA and tried to review the PS data, I get the No PowerStroke Data to display message. The 2025 file was downloaded from PP with Isaac and the 2026 file was downloaded with VA.

[Velocomp]

OOPS! Something has gone awry...

We will investigate ASAP.

[Velocomp]

We just released VA 1.0.42, which fixes the PS problem.

If you're using a Mac, this release also gets rid of the need to install USB drivers

[TMWLUK]

Thanks it works now.