liversedge wrote:
mcmetal wrote:
liversedge wrote:
Kscycler wrote:
As far as I know, SpinScan is proprietary to CompuTrainer. Last time I chatted with them about it, they were telling me the tremendous amount of data and sampling that it took to generate the graphic (or bar chart, depending on modality). That's why it only works using the wired cadence sensor, as ANT+ just can't move that much data fast enough.LOL. You've been had.
The Computrainer serial connection is 2400 BAUD even over USB.
Telemetry updates are sent in blocks of about 42 bytes.
Mark
Wrong. ANT+ only updates 4 times a second. It's not the quantity of data it's the frequency of the updates. To determine exactly where the crank is during a pedal stroke which takes less than a second it just can't be done with 4/sec updates. It's not that ANT+ couldn't do more frequent updates, they just chose not to in the current standards to save on battery life.
I think you're boxing shadows my friend. I was talking about the Computrainer.
You are also conflating data collection with data transmission, they aren't the same. And certainly aren't the same on the CT.
FWIW, ANT+ can do transmission rates above 4hz and indeed the Kickr does -- the command channel used to send commands are sent at 16hz.
Mark
You're confusing update frequency with transmission rate. The ANT+ transmission rate is irrelevant if it only sends it's data 4 times per second. As I said, it's done this way to conserve battery life. They COULD send updates 400 or more times per second but choose not to.
The CT being 2400 baud or 1200 baud is irrelevant. It can send more than enough data (transmission rate) over 400 times per second (update frequency) even if it was 1200 baud. The relevant point is it's sending cadence data over 400 times per second so the CT can keep track of exactly where the cranks are.
Note: I'm not saying spinscan is useful, I don't use it. BUT, in order for it to work it requires significantly more updates per second than ANT+ (current standard) provides (despite it's capability). The CT folks have stated they can't ANT+ support for spinscan until ANT+ sends more frequent updates.
http://www.racermate.net/...ilit=spinscan#p22342
Just to back up the bus a bit and elaborate. Your original response was "you've been had". That is incorrect. Your explanation for why was also incorrect, as you responded about block size. ANT+ while capable of updating frequently enough and enough data, the current standard only allows for it to send 4 updates a second. The CT, using a serial connection, has no such limitations on frequency of updates. Again, feel free to consult the link I posted and contact the CT folks if you believe current ANT+ cadence sensors are sending more than 4 updates every second.