7 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHBest track day data logger?
Leading reported evidence
Use development purpose
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
I have the AIM MXS 1.3 which is way overkill as it has 8 additional channels and I only use 4 of them to monitor 2 oil pressure locations and 2 oil temp locations.....but it is used for development purpose..
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I have the AIM MXS 1.3 which is way overkill as it has 8 additional channels and I only use 4 of them to monitor 2 oil pressure locations and 2 oil temp locations.....but it is used for development purpose..
Leading evidence: 'Use development purpose' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Use 4 of them' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I have the AIM MXS 1.3 which is way overkill as it has 8 additional channels and I only use 4 of them to monitor 2 oil pressure locations and 2 oil temp locations.....but it is used for development purpose..
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Additionally, you�ll find a lot of folks here using aim equipment which is helpful for comparative and soliciting advice from friends.
Use different graphical formats and hardware metrics you get
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
If you don�t want to use the different graphical formats and hardware metrics you get from a traditional logger for driver improvement and want more to be shown where you can improve in a very clear way - it seems like the ticket.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
You can start with a solo and then move up to the more sophisticated units and they all use the same software, so you only have to learn it once.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Use 4 of them
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I have the AIM MXS 1.3 which is way overkill as it has 8 additional channels and I only use 4 of them to monitor 2 oil pressure locations and 2 oil temp locations.....but it is used for development purpose..
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
I have the AIM MXS 1.3 which is way overkill as it has 8 additional channels and I only use 4 of them to monitor 2 oil pressure locations and 2 oil temp locations.....but it is used for development purpose..
Use different graphical formats and hardware metrics you get
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
If you don�t want to use the different graphical formats and hardware metrics you get from a traditional logger for driver improvement and want more to be shown where you can improve in a very clear way - it seems like the ticket.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
7 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T172408Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I would not call the garmin a logger, I�d say it�s more of a coaching tool. If you don�t want to use the different graphical formats and hardware metrics you get from a traditional logger for driver improvement and want more to be shown where you can improve in a very clear way - it seems like the ticket.
A logger to me will provide the raw data you want to assess opportunity for driver improvement but also keep measure on hardware as well.
For me, Aim is the clear choice. You can start with a solo and then move up to the more sophisticated units and they all use the same software, so you only have to learn it once. Additionally, you�ll find a lot of folks here using aim equipment which is helpful for comparative and soliciting advice from friends.
Great support from
@Matt Romanowski
who can walk you through options based on what you�re looking to accomplish.
Check out this thread.
https://rennlist.com/forums/data-acq...k-day-kit.html
Although i have an Aim dash and its very powerful, i find it to be very cumbersome to set up and cost can get out of control.
Check out the vbox stuff and bob
@NaroEscape
is also a good vendor for data gear.
I'm always happy to help. AiM systems have a great ecosystem with car connection, sensors, cameras, and analysis. The tools are all available for the user to get as much as they want from it and there is a very large user base. Feel free to email me
[email removed]
or shoot me a PM and I'll help out any way I can.
I don't know if the Garman Catalyst has provisions to monitor oil pressure and oil temp, but that should be a MUST HAVE for any performance data acquisition so you can just concentrate on driving and not be looking at gauges..
I would suggest the AIM Solo DL as I know it has the capability to add oil pressure and oil temp to the data...
I have the AIM MXS 1.3 which is way overkill as it has 8 additional channels and I only use 4 of them to monitor 2 oil pressure locations and 2 oil temp locations.....but it is used for development purpose..
Also be aware that if you have a 99 C2 with DME 5.2.2 that you cannot get OBDII data to the AIM , I don't know if the Garman Catalyst will do OBDII on a 99 C2 or not..... IF you have a newer Porsche then AIM can get OBDII data no problem...
For a simple, standalone solution, Aim Solo DL all the way. I have an AEM CD-7L in my track car but this is too much pain IMO if you're trying to just enjoy a day at the racetrack.
IMO - if you are going to invest in a logger - I would suggest starting with these sensors at a minimum. You can get by with less, but with these you get granularity to really help fine tune opportunities for improvement.
Hardware:
Oil P
Oil T
Water T (on the can network .2)
RPM (on the can network .2)
Driver:
Brake Pressure
TPS (on the can network .2)
G meter
Speed (on the can network .2)
Nice to have sensors would include steering angle, TPMS, tire temps
This is a source reference. Confirm exact model applicability in the original material.
