All

You can pick your threshold of where you want it to split for me. It’s between 250-350 MMS. it’s just the average speed below that number and above that number. it’s not perfect, but it gives you something to tune off and compare run to run. The low speed on most suspension will also change the high speed. But it’s just cool to see the numbers a little more obviously for a quick tuning.

I try to use sag at the wheel whenever possible, if you have the leverage data. Same for velocities and every other metric really since that is the more "true" value that the rider feels and can be compared to the front (not that they will be the same, but can be compared fairly) The amount of wheel sag to shock sag can also vary wildly - even for 2 bikes that are progressive overall, 30% sag at the wheel could mean anything from 20% to 35% at the shock! Hence why the Commencal V4 had crazy low recommended sag...

So I spoke with one of our better local tuners and he kept mentioning the BYB position velocity graph so here it is. I am yet to understand how to properly read into it, I have been looking mostly into the Damping pyramid so far. I agree with @TheSuspensionLabNZ that the BYB traces can be very hard to read, so I added the option to show it as a heatmap too I also added video support that syncs with the telemetry timeline. This was super important to me and I bought my first ever action cam for it! Especially on...

I strongly suggest that people are very careful when comparing the numbers between different telemetry systems, especially with the homegrown ones. Relatively minor filtering/grouping/binning changes lead to very different speeds and graphs and there isn't a "true" one. For example there can be a big difference what "average" speed is, depending on how is it calculated. My app supports both the MotionIQ way - stroke-peak averaged, which counts each stroke once by peak velocity and peak travel and what I believe is the BYB way - sample averaged, which counts every sample inside compression and rebound strokes. The stroke-peak averaged...

Definitely agree about comparing data. I’ve heard there is even variance between the same systems and using different potentiometers. I’ve been working on my own app for MotionIQ data. I made the trimming of the run faster and also a page for comparing 2 runs. Trying some new things with “feedback to rider” also.

Thanks! Yeah, I was just trying to make it more simple and quick to read. I typically use this data either when we are doing shuttle runs or at the bike park. So how can I read it and do adjustments quick for the next run, so everyone I’m with doesn’t have to wait. Hahaha. Here’s another screen grab. I’ll try out the program a bit and make sure it all works. Then I can post a link on here if anybody else still using Motion instruments wants to use it.

I love the DIWhy vibes from the last few pages 😍 I have been working a lot on the App and the Firmware for the mast month or so. I have made a lot of progress into packaging it into end to end usable, both on desktop and mobile. Major changes Live data! Now you can stream the sensor readings from a connected DAQ in more or less real time (20-30ms delay). You can set the time on the DAQ and you can edit and replace the configuration, without dealing with memory cards and text files! You can also change...

From what Enrico at byb told me is averages are mostly LSC and 95th/Max HSC but depending on what numbers you see it can pull your averages up. I could be wrong but this is how I interpreted what he said. Also agree with ben c on 95th being less of an outlier.

So I sacrificed a string pot on the altar of science. TL;DR: So far, the results are encouraging. I used a lathe to drive the pot via an offset crankpin, allowing me to calculate the theoretical string trajectory exactly, and the maximum velocities and accelerations at different lathe speeds. The downside of this arrangement is secondary vibration: because the string oscillates vertically, its inertia introduces an error that gets larger as the speed of rotation grows. The good news is that, because it isn’t something the pot will experience in real use and occurs at mid-stroke, I think it can...

Interesting post on IG from @Downamics . It’s a great visual diagram of how each part on the bike set up affects the other. It can also remind us how in the weeds we can get by making a change. “This diagram is an overview of the scope for using DAQ as a holistic and specific analysis tool. It is not a comprehensive guide to the vehicle system or DAQ methodology.“ You can view and use the diagram here: Downamics Framework

Yeah that looks like an off-the-shelf unit (with generic libraries available on github) and Trailmetry is mostly just the app. Weird how it needs to be on a moving part of the suspension, but its on the fork crown up front but the shock body on the rear? Definitely weird.... The Stendec systems used acelerometers for suspension measurement and Downamics has been trying it too. In theory they are a good way to measure damping and actual wheel movement (eg it is possible/common that your wheels are moving up from bump but due to things like friction there is no...

The only way I see to have any meaningfull data from accelerometers to get suspension movement is if you have two accelerometers at each end of the suspension unit (fork crown and lowers or both shock ends) and compare the two. The difference between the two will be what actually moves the moveable part of the shock, from that you could get speeds and then movements. But you're not doing that with 25 USD BT accelerometers. You'd need a serious DAQ with synced channels to do that kind of measurements. As said, that website is full of red flags and...

Sounds like what's needed is a roll-your-own string pot that can be built for about $10... coming soon to an open-source data acquisition project near you. Maybe. This guy runs on the bench and can either emulate an analog pot or be read over I2C. It's built around an as5600 encoder: that plus a couple of bearings, a spring from a key lanyard, a 3d printed spool and a short piece of chrome shaft pulled out of an old scanner make up the driveline. It's multi-turn which keeps it compact (and the inertia low), but at the cost of having...