All

Which is what ohlins has been doing since their entrance into the MTB market. From the assembly video it looks like the HSC adjustment is somewhat unique. From what I can tell the piston has 3 main ports with a number of smaller ports, on the same BCD, that can be blocked from the flow path decreasing the amount of port surface area of the face shim, very different than the ellipse camp plate on the ohlins HSC circuit which adjusts the clamp diameter and the resulting force curve slope. No idea if it rides the same but I would...

Now sold 👍

I have a hosted demo (read-only) version of by analysis software live at demo.bodaqs.net . No installation needed, just follow the link. If you want, there are some short familiarization videos on YouTube, here . As usual, I welcome and encourage all feedback. I'm aiming for a quality product here, and I'm grateful for the insight others have brought to it this far. I'll be publishing the most recent logger design this week too - stay tuned :-) Build website: bodaqs.net Instagram.com/bodaqs Github.com/benconnor1972/bodaqs https://discord.gg/rpqqWbtwXJ

I'd be curious to try this. Would your bike be moving like a trophy truck -Suspension moving fairly quick through the travel but the rebound is fast enough to return to the ground so the chassis is in the same spot for the most part and wheels are just doing their thing.

The point about filtering (especially) still stands, but there's no reason except convention to be stuck on histograms. Here's the old favourites rendered as cumulative frequency distributions. The little overlaid bars show median, interquartile range, P95 and max values. Personally I think that tells the story quite well.

I think Jordi's point is mostly about data collection and analysis being most important in the bike design, validation and product testing phases, and not so much on the day to day of riding the bike during a race event. If I were at the pointy end of the field as a mechanic or engineer involved in the world cup circuit, I would likely just take data all of the time and share none of that with the rider until the season was over. The most important thing a rider could do with regards to data acquisition and analysis is...

Maybe flip the colors? Compression is usually blue on the adjusters (and rebound red), maybe it would make sense to align with that?

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

Interesting take here from Jordy https://youtu.be/mnl9xQJF9ok?is=Aa7TLQLWLpn97NtU Seems like the Suspension Engineers don't like the teams using DAQ that much. I also noticed this... In the videos from last years worldcup you saw maybe 30% of the teams using DAQ system and this year you see pretty much 100% of them running the BYB DAQ. I feel like DAQ is almost more useable for "normal" riders that haven't the experience of a racer that know what "suspension feel" they're chasing. For example I don't know what my bike feels like at its best possible setup. For the longest time I thought...

Quite so: there's a fundamental difference between those methods. Characterising each stroke (which my system does, by the way) carries another set of gotchas: what counts as a stroke? Real suspension data doesn't look like a neat sine wave. You need to allow for some hysteresis near the stroke end points: if you use a strict 'velocity crosses zero' test for stroke end you end up with loads of tiny strokes with no useful information. Practically, this means you have to set a threshold for what counts as 'no movement'. I use 30mm/s (but configurable). On data.syn.bike it's explicitly called...

"Honey, I shrunk the DAQ!" First testride with the new Trazer V2.2 and the new Sensors. About 50 % smaller Trippled Battery capacity Standalone USB-C charging port Beeper for UX support Two Buttons with LED Front Sensor is now a "standard" linear potentiometer with a carbon tube "casing" Re-designed rear sensor that now has a bearing instead of plastic on plastic with small air gaps. Works great! Edit: Another overlay video for those interested. Also with a pretty stiff fork setup regarding dynamic sag (21%) ;-) https://youtu.be/1LCTslCTWLQ?is=856_7CwAul5PZ51R

Credit goes to sghctoma who originally did the rotational sensors. I have ordered some linear sensors, but I don't think I can fit anything in the SC tunnel... I got tired of the cave look, so now with light mode! Also - lots of quality of live improvements for the sessions. The telemetry plots can be reordered, minimized and embedded in one another. They are also scrollable and resizable with dividers Holding down Option/Alt while zooming in/out of the plots makes it much slower and precise. Holding Shift while scrolling in the plot area will skip zooming the plot under...

These are old photos but hopefully you can figure out whats going on inside them! They are all constructed in a similar way

Another DIY datalogger update. I have three main things to report, and an invitation. - The project has a build website: www.bodaqs.net has sourcing and build guides for the hardware, a user guide for the logger, and a software guide, as well as an overview of the project. - syn.bike compatibility. The logger can output files for direct upload to data.syn.bike, which is a simple, clean option that will satisfy most users. I'm still working on my own software, but that is going to take time and I don't want to reinvent the wheel (more than I have already). -...

I opened up my BYB fork sensor to clean it up - was a little easier than the AIM ones were - its a snug fit but not as tight since the screws hold it in place, so can be carefully pryed apart with a metal spudger or blade. The wipers looked pretty good, a tiny bit of dirt in there so I'll clean it out, replace the o-rings and add a tiny amount of thin super lube grease to the contact points to reduce friction and give smoother contact for the wipers. It had quite a lot of play...