When I am looking at an engine log there is a Vertical red line at consistent intervals. What does this represent? Thanks!
Engine Log Help
Moderator: LT401Vette
-
- Super MS/Extra'er
- Posts: 1986
- Joined: Sat Jul 22, 2006 8:02 pm
- Location: Eureka, NV USA
- Contact:
Re: Engine Log Help
To the best of my recollection, those are time gaps........
It might help if you were to post the actual log!
Ken
It might help if you were to post the actual log!
Ken
1979 Corvette - 383 CID SBC w/ Holley Pro-Jection 900 CFM TBI, 4-85 lb lo-z injectors & Walbro 255 pump
MS2 v3 w/extra 3.4.2 Release
36-1, Delphi LS2/7 coils in wasted spark, driven by v2.0 logic board from JBPerformance
Spartan Lambda Sensor from 14point7
TinyIOX from JBPerformance
MS2 v3 w/extra 3.4.2 Release
36-1, Delphi LS2/7 coils in wasted spark, driven by v2.0 logic board from JBPerformance
Spartan Lambda Sensor from 14point7
TinyIOX from JBPerformance
-
- Master MS/Extra'er
- Posts: 409
- Joined: Sun Jan 30, 2005 11:13 pm
- Location: Monroe, Wa.
- Contact:
Re: Engine Log Help
It shows up as a Mark in the log file But I don't know how or why it is triggered, I can't find anything in the manual that references it either.
-
- Running MSx/Extra
- Posts: 558
- Joined: Sat Jul 21, 2007 6:49 am
- Location: Manchester
Re: Engine Log Help
Hitting the space bar during logging gives the red line...
John
John
-
- Master MS/Extra'er
- Posts: 409
- Joined: Sun Jan 30, 2005 11:13 pm
- Location: Monroe, Wa.
- Contact:
Re: Engine Log Help
Yes, this is the same type of Mark you would get hitting the space bar. but it is at very specific intervals. So my though is that this is when the ECU is starting the Sequential cycle over and the line is a representation.
Phil, can you confirm that for me?
Phil, can you confirm that for me?
-
- Super MS/Extra'er
- Posts: 12731
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Engine Log Help
Yes, the red lines are MARKs.
In a normal log there is a MARK if you hit the space bar or an event like going offline occurs.
With the high speed logs like the engine log, the data is not read in a steady streaming fashion like a normal data log. In this case The Firmware writes the raw data to a page of RAM, then when the page is full notifies TS that the page is ready to read. TS reads that page, then the firmware starts logging again.
So you will end up with chunks of data with pauses between them. To make it easier to see where these data gaps are, there is a MARK. So you can know that you shouldn't expect the data have proper continuity across the red line.
In a normal log there is a MARK if you hit the space bar or an event like going offline occurs.
With the high speed logs like the engine log, the data is not read in a steady streaming fashion like a normal data log. In this case The Firmware writes the raw data to a page of RAM, then when the page is full notifies TS that the page is ready to read. TS reads that page, then the firmware starts logging again.
So you will end up with chunks of data with pauses between them. To make it easier to see where these data gaps are, there is a MARK. So you can know that you shouldn't expect the data have proper continuity across the red line.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
-
- Master MS/Extra'er
- Posts: 409
- Joined: Sun Jan 30, 2005 11:13 pm
- Location: Monroe, Wa.
- Contact:
Re: Engine Log Help
Thank you for the clarification Phil, that is just what I was looking for!