![]() From my experience with rally cars I know that having "creep" in the distance travelled can be quite a big problem. I agree that for rally stages, the philosophy and approach is a bit different from what is used in circuit racing for all the reasons you list. I can see that these would be very helpful when used in this application. I took a look at some of your videos, I really like the multiple view setup of pedals, driver and driver's view you put together. ![]() We put a lot of effort into these, so I'm glad you're finding it useful! Hi Armaki, thank you for the feedback on the course. P.S: to whom it may concern, you can have a look on our endeavors here: To sum it up, i would love to exchange thoughts with anybody with more experience with A-to-B stage logging, like rallying, hillclimbs, or sprint events! To make things even more tricky, changing the logger over to different cars is also on the table, asking for simplicity and "universal" settings. The video is your best chance, for basic points, like lines and braking points.Īn additional interesting parameter is that banking or road elevations, changing grip levels, variable conditions, ect are on the daily menu, making conclusions very tricky, without the driver's input. You will rarely have the change of reviewing any data, besides basic reliability data, through the course of the day, so there will be no feedback to the driver possible, to improve on the second pass, and it not so common for 2 guys driving "same" cars, willing to share data. On top, it's sometimes not really practical at the club level, to complicate the car with additional advanced sensors, like suspension pots, or even steering angle sensors. Hardware/Usage: Telemetry is practically 100% banned and depending on the regulations, it can be that it's not allowed to install any additional sensors for logging purposes. In rallying, you are usually looking at differences measured in tenths of a second/km, but it's very common to have 2 cars timed within 0,1, or even 0,0s, over a stage of several KMs. The above leaves us with a somehow "averaged" reference, which occasionally is useless for the differences involved. A car will usually change over the years, the crew is on a different mission/strategy each time, the conditions may vary alot each time you visit the stage, ect.ģ) No laps, or start/finish line: Clearly the start line is different than the finish line and on top, those might move, even on the same event slightly, due to external conditions. References: The reliability and relevance of reference data is somehow questionable, due to reasons like the ones below.ġ) No 2 runs are the same: Stages, especially the gravel ones, tend to change over time, conditions, or even car passes through the same day.Ģ) No real reference lap is possible: Driving the stage in anger, especially with a rally car is not allowed, so you can only rely on historical data, if available. Logging mostly on rally stages, offer some unique challenges, compared to what you describe in the course, which i would like to discuss with whoever is interested. ![]() I have been working with Race Technology products, which back then were within budget and offered a nice integration of my GoPro cameras, but the strategies, techniques and approach is clearly applicable, regardless of the equipment. In my 15 years or rallying, i am using cameras since day 1 and a logger for the last 10 years, after a crash, when it became obvious that even the most open minded and honest drivers, are no reliable source of data under pressure. ![]() Looking forward to the more advanced stuff, like damper pots ect. Great content once again! High-end distilled info, structured properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |