Fidgrove: data analysis tool, w/ team-shareable real-time telemetry, community records,...

Hey guys,

Since I last wrote here, we've deployed a few small features and fixes. Case in point, Fidgrove DataLogger (v.2.3.0) now logs water/oil temps and aux inputs (e.g., ABS, TC, Rear Flap, fuel mix, power mode, etc) when driving in online servers as well. You can analyze these indicators with correlation charts for each of the sessions logged

Even though we haven't been sharing news lately, we continue to work hard and are making significant progress in our goal to create wonder-features for teams this year. We've been fortunate to be working with positive feedback from several teams and sim racers alike, and we couldn't be more excited for what lies ahead for this year

As always, feel free to get in touch here or in our discord to discuss our platform and/or our plans.

 

Hey mate I registered, downloaded everything, launched the application and lapped online (LFM practice server and then a race), but I see no data on the website. I got the message "Fidgrove logging" in the message box in the game, but I can't see anything on the website

 

Hi @Pasquale Genchi,

We did register an issue this weekend, which caused data computation to pause. I apologize for the issue. Data was not lost, so you should see your results within the next few hours, as the engine goes through the pipeline.

On a related note, this month we'll deploy an update to the computation engine, which will have significant impact on performance (e.g., latency 10x lower), and on scalability. This means you'll see the data right away (e.g., laps showing in the platform as they're done), and it'll also enable us to launch real-time features. Exciting times for us this quarter.

Thank you for using the platform and reporting the issue. I appreciate any further feedback you may have in the future. In the meantime, do check the opt-in communities to compare lap times with others.

Regards

 

Oh good to know thanks, I thought I was missing something or did something wrong

 

Hello all,

In the last few days we deployed a major overhaul we did to Fidgrove platform. The most visible part of it is the new Fidgrove Trackside Station, a feature enabling you to see your rFactor 2 data, real-time, while on track, with virtually no impact on local CPU/resources usage.

We’re initially deploying Trackside Station with 2 different views, accessible through the new streaming icon on Eng. Station’s top navigation bar. One view relates to cockpit data, and includes extended aux inputs and oil / water temps (on offline sessions). The other is a time tables view, with performance metrics for each stint/lap/sector (i.e., time, avg speeds, min/max speeds).

The Trackside Station is the most visible chunk of this very significant update, of which the core part is the deployment of new tech that enables us to have stable, low latency, real-time cloud-computed data, available anywhere. Here is a summary of many other updates across the platform:

• Computing Engine: re-did streaming and computing technology, resulting in significant lower latency and a leap in scalability, all post real-time computing
• Eng. Station: introduced new profile car page with specific info (e.g., available aux inputs)
• Eng. Station: re-organized garage section with 3 car-specific pages: profile, setups, track records
• Eng. Station: adjusted list of sessions to highlight live sessions
• Eng. Station: enabled access to session details page for ongoing sessions, with live updates
• Eng. Station: added user stats to Community page (e.g., # track records, # car-track combo records)
• Eng. Station: improved charts rendering
• Eng. Station: fixed other minor bugs across the platform (e.g., shortcuts)
• Trackside Station: introduced cockpit data view, with real-time post-computed data
• Trackside Station: introduced time tables view (e.g., lap tables with avg speeds for each sectors)
• Trackside Station: introduced strip with live car status (e.g., on track, stopped, pit lane, pitting)
• DataLogger (v3.0.0): adapted DataLogger to new streaming technology
• DataLogger (v3.0.0): added logging for TC threshold mode and TC cut mode
• DataLogger (v3.0.0): added aux inputs & water/oil temps support for rFactor 2 RC build
• DataLogger (v3.0.0): optimized handling of AI mode trigger
• DataLogger (v3.0.0): made visual adjustments to app & fixed several minor bugs

With this big initiative out of the way, we’ll now focus on the teams’ features we have already under development. We're quite excited with it, and we can’t wait to share more news on this soon.

Cheers,
Ricardo

P.S. BTW, the aux inputs shown in the cockpit data will change to show the existing aux inputs for each specific car. When on online servers, some aux inputs are not live, and will display (grayed out) the relevant setup information.

 

Hi everyone,

Here's a changelog on our updates this week:

• Computing Engine: fixed sector and lap times (now always matching exact values from sim)
• Computing Engine: fixed session not being logged when formation lap not skipped
• Trackside Station: fixed lap state when quitting with “ESC” (time tables page)
• Trackside Station: added green font to stint best race paces (time tables page)
• DataLogger: fixed content validation for some modded content based on paid cars
• DataLogger: improved car validation process for modded free cars
• Corporate webpage: revamped project page to better reflect current state (https://fidgrove.com/)

There has been some questions regarding the new RC build, and its new telemetry output data available. From what we can see, these changes are essentially cleanups in preparation for hybrid engines support. Nothing really new for now. We already store and analyze electric engine variables separately (e.g., fuel mix vs power mode). That said, we're monitoring the changes, and we'll continue to update the DataLogger to make sure all works well. We're also looking forward to new cars with hybrid engines, which will allow us to provide some interesting charts / automated analyses

Cheers

 

This week we’ve deployed our first features to support teams! You are now able to create a team in Fidgrove’s platform and share data & setups when preparing for an event.

The workflow and new analysis tools have been developed around events. An event is essentially defined with a date, track, and car class. If the date is in the past, the event is no longer active. Once this is defined, whenever you drive with that track-class combo, data is automatically shared with the event, as long as you’ve been included as a driver in the event settings. This creates a data pool that the team can analyze at any time. Your specific data is also still available in the same places as before. Whenever data is being logged to an event, all data sharing with communities is suspended, so that your team does not show their performance to anyone else.

As you prepare for an event, you can make use of the new specific data analysis framework, which includes sections for Lap Analysis, Stint Management, and Setups. A section for Multi-Stint Strategy will be added soon. Each of these sections has their own sub-sections with multiple possible analysis. We’ll continue to expand this further in the future. Here are a couple of screenshots as examples:



Data Slicing feature is a new innovative possibility to filter or highlight data in the event’s data pool, impacting all event data analysis. You can access data slicing options in the event page, on the top of the right sidebar. Filtering data means you won’t see data that is filtered out, in any event chart or table. On the other hand, Highlights enables you to tag data and create an easy way to see patterns for specific contexts. Options for Data Filters and Highlights include general variables (e.g., car, driver), weather conditions (e.g., track temp), setup options (e.g., setup name, tire pressures), and performance options (e.g., lap time, avg engine mix when applicable). When applicable, minimum/max values or a list of logged values are shown next to the variable option.

An example of use of Highlights might be useful to better explain its capabilities. Imagine you’re looking at a chart with lap time vs tire wear. You could use Highlights (H1) to tag datapoints where the track temp was below a certain value (min and max values are shown to help this decision) and where rear wing was X and the driver was Y. You could even create a new highlight (H2) to show same situation but for driver Z. H1 shows datapoints in blue, and H2 in red. Doesn’t this make the chart much more insightful in terms of understanding what works and when it does ?

 

Hey all,

Our team is happy to share that you can now see your teammate's data live on Fidgrove anywhere with a browser, with virtually no local computing and lag

Here's a list of the updates we deployed:

• Eng. Station: added event participants access to live teammates’ data (Trackside Station)
• Eng. Station: added team and event participants online status on Eng. Station
• Eng. Station: improved event’s “Setups” page - i.e., basic comparison tool, car selection menu
• Eng. Station: improved event creation/settings form - i.e., improved teammates selection and drag & drop process for car allocation, expanded access to settings by all participants, duration format, bug in date used
• Computing Engine: rebuilt AI mode detection (logging not dropped; AI laps shown as nulls)
• Computing Engine: fixed bug preventing team sessions to be recorded properly in event's data pool
• Computing Engine: fixed DB access bug leading to sessions not being properly shared with events
• DataLogger (3.2.0): Updated logging of driver’s aux inputs and engine temps with new rFactor 2 build released

Cheers

 

Hi Ricardo,

That's very interesting, we'll certainly have a look at it.
Out of my curiosity: how are you able to extract mix, abs and TC info? As far as I remember this is not exposed on rFactor plugin api

 

Hey all,

We've been doing updates to the platform on a weekly basis. Here are the main changes since my message:

• Trackside Station: added electric info (hybrid cars) when applicable (e.g., temps, energy)
• Eng. Station: added user statistics in settings page
• Computing Engine: added support for hybrid engine data logging & automated RT computation of key variables
  
• DataLogger (v3.3.0): added data logging support after driver swap
• DataLogger (v3.3.0): simplified in-chat content validation messages at beginning of stint
  
• DataLogger (v3.3.0): improved installation process (better automated rF2 folder discoverability)
  
• DataLogger (v3.3.1): updated driver’s aux inputs / engine temps logging with new rF2 build
  
• Fixed several miscellaneous bugs across the platform & other minor adjustments

For those interested in being up-to-date on what we're doing, feel free to join our Discord server.

Cheers,
Ricardo

P.S. @Cicci8ino, looking forward to your feedback. Just sent you a PM

 

Hey all,

A quick message to share minor updates done this week:

• Trackside Station: updated fuel component with laps left value now in red font if below 2
• Eng. Station: community pages now have a dynamic widget showing last 3 lap times recorded (a delta time vs the best community combo time will be shown if applicable)

When looking at a community track records list, the new widget is on the left of the two personal stats we already have there, namely the number of absolute track records, and the number of car-track combo records one has in the community. These numbers are for the context specified (1 lap vs 10 consecutive laps, dry vs wet), and change accordingly when you toggle these.



As a reminder, the "My Records" page within a community provides you another quick way to check your time gaps vs others. This comparison can be done by class (default), or by car. Here's a screenshot as an example:


Cheers

 

Just a quick note to share that with today's rFactor 2's new build, Formula E gen3 vehicles now have energy telemetry.

As such, you can now analyze energy usage on Fidgrove's Eng. Station with these vehicles

 

Hey guys,

We've deployed a new page with live data to our Trackside Station

You and your team can now follow an event without entering rF2 server as a spectator. In addition to the leaderboard, a left sidebar shows you a circle track map with car positions (grey cars are cars from other classes), and right sidebar has a live pace analysis chart. The latter shows the interval between worst and best lap times, as well as average lap time (red dot) and last lap (white dot).

Cheers

 

Hey guys,

For those of you not in our Discord, we've continued to improve our Trackside Station, where you can see your data in real-time (or your teammate). Here's a summary of the main changes since my last message above:

• Trackside Station: added new gap chart to analyze delta evolutions in leaderboard page
  
• Trackside Station: added column data cycle modes in leaderboard table (e.g., sector columns show sector times, best sector times, min/avg/max speeds of previous lap, "Gap" column cycles with "Int" data in race sessions)
  
• Trackside Station: corrected running lap time in cockpit data page, after finished lap and each sector
• Trackside Station: added conditional laps/time info & fixed session time info on bottom strip
• Computing engine: fixed bugs related to creation/closing of sessions
• DataLogger (v3.4.2): improved connection resilience, mitigating session drop issues
• DataLogger (v3.4.3): improved system logging to identify potential bugs
• DataLogger (v3.4.5): fixed bug of open sessions creation, properly handling rF2 “junk” data after session end

Currently, Trackside Station does not get historical event data. E.g., minimum speed is only since first loading the page, not since beginning of a race necessarily. To be improved

Here are a couple of screenshots showing the time gaps chart and column cycle mode visual cue:





Cheers

 

Quick update to share Fidgrove now supports logging data from any car & track on rFactor 2!

Many requested this, and so we hope you can now use the platform with your most beloved content

Cheers
Ricardo

P.S. I need to update the initial post

 

These are really good news.

 

You can now download a table with info on all laps you've logged into a Fidgrove event. That's one line per lap, with 80 variables as columns

Essentially, within any event you create on the platform for your team, you can now go to Lap Analysis Section, and see a button on the right sidebar to download CSV file. This is a table with all laps in the event data pool, including laps from teammates. There are a lot of columns related to different topics, e.g.:

• ID information (e.g., Date, Layout, Car, Driver, Stint ID, Lap number, etc)
• Lap performance indicators (e.g., lap time, sector times, min/avg/max speeds total and per sector, fuel load at end of lap, fuel used in lap, tire wear per lap, tire age, % full throttle, average understeer angle in lap, avg tire pressures, avg carcass tire temps, etc)
• Aux inputs info (e.g., avg engine mix in lap, DRS use, P2P use, etc)
  
• Operating window info (e.g., min/max brake temps, min/avg/max oil temps)
• Track/weather context (e.g., track temp, water temp, water on track)
• Setup info (e.g., setup name, tire compounds, tire pressures, ride heights, front/rear wing info)

Note: By tire age we mean tire age. If you pit on-track, tire age only resets if you change tires
Note2: average engine mix in laps, water temps, and oil temps are only available if lap done offline (not in online servers) and using latest supporting DataLogger version.

Hope this is useful to all who use Fidgrove.

We'll continue to build tools on top of this data organization to help analyze data, assess performance, and suggest improvements.

Cheers
Ricardo

 

We've made a few updates which I believe haven't shared here yet. So here it is:

• Trackside Station: deployed alpha version of real-time telemetry, accessible by teammates
• Eng. Station - Event workflow: deployed alpha version of multi-stint strategy planner, with suggestions based on event pool data
• Eng. Station: S397 content now listed with rF2 logo to more easily see what is official content
• Eng. Station: Fixed several minor bugs
• Corporate website: revamped website showing "Fidgrove Friends" public community track records (w/ hot lap/10-laps pace and dry/wet track options, so everyone can easily check paces)

Bear in mind that real-time telemetry and automated multi-stint strategy planner as still in their early stages, and will need more development to be helpful in the user-friendly way we aim for

Also, I've finally changed the first post on this thread, which I think makes it easier to see what Fidgrove is all about

 

Here are a few updates we recently deployed:

• Eng. Station: added setting for metric <> imperial units
• Eng. Station: added setting for track records to be shared w/ communities w/ active events car-track combo
• DataLogger: Support additional variables logging in new rFactor2 public build (e.g., water/oil temps, aux inputs, driver swap)
• DataLogger: optimized installation process
• DataLogger: improved login security procedure
• DataLogger: added core support for unannounced upcoming features

As always, the DataLogger will automatically update to version v4.0.1, so no need to do this manually