All

That's quite some nonlinearity. It would move the dynamic sag quite a bit further into the travel if you assumed a linear zero to full travel behaviour.

I wouldn't try to match the dynamic sag values front to rear - the front can be anything from 15 to 25% and the rear might be 25 to 35. Or even wider ranges. Because the rear is always more progressive the sag can be quite a lot higher, but things will "catch up" further in to the travel so what feels "balanced" might have quite different dynamic sag values @thegromit the overall progression value only tells half the story - the way it gets there and also total travel has a large effect too. I didn't find the exact...

This is almost certainly entirely driven by kinematics and it relationship to damper performance. Higher leverage -> softer damper due to the inverse shaft speed relationship. The other factor is people often look at bottom-out resistance as a function of progression only; in truth bottom-out resistance is the total energy absorbed by the spring (area under the wheel for curve) AND a large function of damper, especially "high speed" compression adjustments on shocks. In your case (a more progressive and heavy bike) it sounds to me like the harshness is probably coming from being under-supported. When a bike sits too...

Time for a project update! A lot has been going on. First, the hardware has evolved. I've done a major redesign to make the logger more robust and easier to build. It now supports up to 8 analog channels, plus digital on I2C and a UART connector for external GPS. The firmware has moved a long way too. It now supports AS5600 and AS5048 rotary encoders and DAN-F10N GPS modules (these are available from Sparkfun on a breakout board and work really well). There is now an option to write log files in a compact binary format, which reduces file...

I'm certainly no suspension expert but I've tuned a few things, from engines to inkjet printers. I think the First Rule of Tuning is that whatever you aren't measuring is the thing that will screw you 🙂

I think you still find a world cup level guys who bolt it on at a race, think the numbers are way off and start changing things right away....thats the type of team Jordi is talking about, as they will likely be asking him for certain change based totally on the data instead of anything the rider is asking for - thats the big mistake. The tools are still really good and useful to have, as long as teams don't let it dominate the decisions. It's fine if people come up with the own interpretations but it puts people like...

My $0.02 on Jordi and DAQ... He's clearly not an idiot, but neither are the teams running DAQ at world cup level. Most likely, they're both right. Jordi sits in the Fox stand and deals with whatever walks through the door, under enormous time pressure. There's probably 3/5 of 5/8 he doesn't know about how Fox product behaves, both through his own honed intuition and through dyno data. Having people bring their own interpretations probably does get in the way of him doing his thing. Even if you loved DAQ, you might think it belonged in the off season and...

"Data doesn't lie, but it also doesn't tell the whole truth" - I can't remember who originally made that quote but it is very true I'm not as blunt as Jordi but I agree on a lot of the points and I think the other mechanics summed it up better - You need to focus on listening to the rider and understanding what they want instead of burying yourself behind a computer screen and expecting the lines to give you the answer. The data can supplement a technicians skills but it can't give the result all on its own. I...

Yeah I saw this also. And in this thread is definitely leaning on the side of DAQ, but there’s some people out there who don’t like it and that’s Ok. Jordi in all the Fox videos never seemed to care for Daq. It’s ok, personally I know the benefits, it helps me and my friends. I know you can get lost in it, but you can also get lost in rider feedback who doesn’t know how to explain what they are feeling. To me, data doesn’t lie.

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...