Matt@pcmtec Posted September 1, 2021 Posted September 1, 2021 Changes to data logging: - Log and channels tabs are now in the top section - Bottom section displays RPM (when available), and can be zoomed in - Selected parameter highlighted in log - Playback / Live channels displayed, depending if a log file is opened or connected to the PCM - Details tickbox will display sidebars with displayed values and units CTRL will select start and end of Average / Trace selection TRACE button displays histograms and maptracing If over 5 minutes of logging is selected, then the trace lines will not be available, and Trace button becomes red Trace window selection: Histogram, select scales and histo trace values: (Or load them from a table) Press OK to display the histogram: Trace cursor updates and the trace line can be disabled if required. Decimal points can be adjusted Map Trace tables can be searched, and clicked on for one click trace display: Use CTRL UP/DOWN to adjust label positions Right click to access options such as adjusting priority (update rate) of parameters Or colours, range and chart positioning Layout load, save and appending is now located as a popup in the bottom panel of the log window 1 Quote
Bill Posted September 1, 2021 Posted September 1, 2021 (edited) Hi Matt, having a play with histograms this afternoon & didn't have a suitable log file created with 2.10 to use the trace function so I've opened a couple of 1.25 logs. I've found it appears to update the file & it increases in file size. After this happens, it's no longer able to be opened in 1.25. It also distorts some of the values eg temps. If a workshop were to need to review a previous log created in 1.25 to confirm/prove what was logged whilst tuning, their log would be lost or invalid due to values displayed. Some examples where the temps are skewed when a 1.25 file is opened in 2.10. Changing units only makes the extreme temps even more extreme. Edited September 1, 2021 by Bill Add images Quote
Puffwagon Posted September 1, 2021 Posted September 1, 2021 I opened a histogram and it showed the correct values for afr/dlp1 for a while then showed incorrect ones, lean. It was fine in the datalog, so just the numbers weren't lining up between them. Quote
yoda598 Posted September 1, 2021 Posted September 1, 2021 id like to figure out a way to use the histogram to dial in the speed density.. not sure how of course. not the greatest with histograms 😅 Quote
Matt@pcmtec Posted September 30, 2021 Author Posted September 30, 2021 On 9/1/2021 at 5:28 PM, Bill said: Hi Matt, having a play with histograms this afternoon & didn't have a suitable log file created with 2.10 to use the trace function so I've opened a couple of 1.25 logs. I've found it appears to update the file & it increases in file size. After this happens, it's no longer able to be opened in 1.25. It also distorts some of the values eg temps. If a workshop were to need to review a previous log created in 1.25 to confirm/prove what was logged whilst tuning, their log would be lost or invalid due to values displayed. Some examples where the temps are skewed when a 1.25 file is opened in 2.10. Changing units only makes the extreme temps even more extreme. Hi Bill. Thanks for the report. We have now fixed these issues with the latest beta version. With 1.25 files these are now upgraded to a backups folder and loaded from there (so you can still use the original file with 1.25 later on). Also we fixed up an issue with unit conversion which affected the temperatures when displaying in the 2.10 beta 1 Quote
Bill Posted September 30, 2021 Posted September 30, 2021 1 minute ago, Matt@pcmtec said: Hi Bill. Thanks for the report. We have now fixed these issues with the latest beta version. With 1.25 files these are now upgraded to a backups folder and loaded from there (so you can still use the original file with 1.25 later on). Also we fixed up an issue with unit conversion which affected the temperatures when displaying in the 2.10 beta Thanks Matt. I'd noticed that the temps were now displaying correctly & there was a new backups folder. Great work guys!! 1 Quote
RAWMotorsport Posted October 1, 2021 Posted October 1, 2021 Hi Matt anyone else had slow update from the new betas logger, i have been using it over the last 3 days and found it to be slow updating, freezing during a log, I am going to install the software on my second pc to rule it out as an issue but in the previous release it worked like a dream. Quote
Roland@pcmtec Posted October 2, 2021 Posted October 2, 2021 1 hour ago, RAWMotorsport said: Hi Matt anyone else had slow update from the new betas logger, i have been using it over the last 3 days and found it to be slow updating, freezing during a log, I am going to install the software on my second pc to rule it out as an issue but in the previous release it worked like a dream. Are you using the latest version here? Use help about and check your version. www.pcmtec.com/alpha-release Also if you can list your system specifications. Quote
RAWMotorsport Posted October 2, 2021 Posted October 2, 2021 20 minutes ago, Roland@pcmtec said: Are you using the latest version here? Use help about and check your version. www.pcmtec.com/alpha-release Also if you can list your system specifications. Yip. Will install it shortly and do some logging on another pc it is almost identical to this one but slightly newer, I have had an issue with this pc using 1.25 as well but it was sorted a few months back and I never had the issue on my older pc when trialing it with kirby so may be the pc, Ill report back with the results. Quote
Roland@pcmtec Posted October 2, 2021 Posted October 2, 2021 Have a look at the release notes. There have been some big updates to the datalogger performance. Check your version against the release notes listed. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.