iGPSPORT BSC500

[shaxberd]

Am i the only one minding the ghost watts? I'd have thought it'd almost be a deal breaker for anyone using a power meter? I sure AF wouldn't have bought mine had i known that would be a problem, let alone one that would never get fixed because igpsport clearly gives 0 F about it.

I assume you mean power not dropping to zero when coasting or something along the lines? Seems like you deleted your post on this, so I'm guessing a bit 😅 I'll keep an eye on that during the next ride!

What's the comparison on the apps side?
Before my current BCS300 I had a fairly simple Magene C406, so I can't really make a apples-to-apples comparison, but when switching over I liked the iGPSport app much better than OneLapFit.

While not perfect either, the app itself seems more coherent on Magene's side in my opinion, iGPSport's one feels a bit chaotic without a uniform design/UX philosophy (for example, the device and profile pages use completely different menu styles).

[biph]

I assume you mean power not dropping to zero when coasting or something along the lines? Seems like you deleted your post on this, so I'm guessing a bit 😅 I'll keep an eye on that during the next ride!

Yeah, I guess he refers to that.
 
From the BiNavi thread (also GPLama made a video about it):

First impressions (based on one week of riding):

Bad
- sticky watts - apparently due to be fixed by end of September - but the fact that it launched with this issue is very bad and creates trust issues (what else is it not recording correctly?).

Update: support got back to me and said to pair over Bluetooth instead. Magene only supports a bluetooth connection when connecting to its app, and only supports ANT+ when connecting to a cycling computer. These functions previously worked on a Garmin 530. Pressed this a bit further and just got - in short - too bad, can't support all third-party products. I get that, but it's disappointing to take a step backwards compared to the Garmin 530 - the signal is clearly being broadcast properly over the ANT+ protocol as that is how the Garmin is working with it. Liveable, but frustrating.

So if your Power Meter supports Bluetooth connection, maybe you could test if that helps.

[shaxberd]

Sorry, took me a while to test a few scenarios due to some mechanical work on one of the bikes.

Yeah, there's definitely sticky/ghosts watts, along with some general lag regarding power data - going by my fit files, there's about a 1s general delay, e.g. when rolling up to a hill and then putting the power down.
Presumably on top of that, there's sticky/ghosts watts when dropping to zero/coasting, resulting in about a total of ~3s it takes to actually drop to 0W (again, in the fit files).
Both behaviours look worse on the device as well as the displayed numbers ironically both update more regularly than the 1s fit file interval, but also seem to suffer from the device's (presumed) low processing power, so it's easily 5s on there while riding.

Those numbers are all based on a SRAM Rival PM - I've also tested with a Leoseek spider PM but that already comes with its own small lag so the numbers are slightly higher still.

There's also the issue that the "power gauge" widget (which is well-designed in theory) seemingly updates the gauge and the number bit separately from another, sometimes resulting in some weird changes (think power zone dropping to a lower colour while power value increases).

So yeah, maybe not the best device if you want to dive into power metrics - I think the overall averages, NP, etc. will still be okay, but it's still annoying especially mid-ride.

EDIT: Oh yeah, I also tried to connect the Leoseek PM via Bluetooth, but that just wouldn't work at all, so the suggested workaround might not be available depending on your PM hardware.