Discussion
GreenV8S said:
eliot said:
GreenV8S said:
Basically you edit one of the INI files to make an extra memory table in the ECU visible to MegaTune, the table is one that records the time interval between adjacent teeth in real time. The missing tooth stands out because the gap is much longer than normal. If you get one big gap you know you're OK; two smaller gaps indicates a problem.
I'll have another look later on and see if I can dig out the details for this.
Yes I recall such an option. I seem to recall having to use megatunix, I did try to install it - my my "tuning" laptop is way too slow - so i gave up.I'll have another look later on and see if I can dig out the details for this.
(And yes i did try searching for it lol..)
Find the .INI file that defines the memory page configuration. In my installation this is defined in C:\Program Files\MegaSquirt\MegaTune2.25\mtCfg\msns-extra.ini and it contains something like this in the [Constants] section at the top of the file:
#unset MEMPAGES ; set to enable all 13 pages for full debugging
#unset LOGPAGES ; set to enable 11 pages for trigger/tooth logging
Change the LOGPAGES line from 'unset' to 'set' i.e.
- set LOGPAGES ; set to enable 11 pages for trigger/tooth logging
; Pages 10 & 11 are special read only pages that can be used to view realtime logged data
; of inter-tooth or inter-trigger times. Primarily for code devel or checking your trigger
; wheel is giving normal pulses.
;At present you can only access this data by using the Table Editor and viewing the data directly
;Page 10 contains the time between each tooth in the generic (missing and/or 2nd trig) and Neon
;Page 11 contains the time between "triggers" and will work for all ignition types
;93 big endian 16bit numbers are returned. The 188th byte is the address of the _next_ byte to
;be written. The code logs continuously once the page is selected so you need to start from the
;next byte and wrap around to the beginning to get the data in the right order
;The 189th byte indicates the time units. 0 = microseconds, 1= 0.1ms units
;After you've selected the page, pause a little then hit Fetch, you'll get 93 new samples.
;Then somehow get them into a spreadsheet and plot a graph.
;i.e. if the data is (decimal) 52, 45, ....
; convert those two numbers -> (52*256) + 45
;page 12 = RAM bytes $0000 to $00FF ($0000 to $003f return zeros)
;page 13 = RAM bytes $0100 to $01FF
The Table Editor referred to in the comments is under the 'Tools' menu. I seem to remember being confused about the table numbering initially, I forget whether it starts from 0 or 1 and I assumed the opposite, so check to make sure that the contents are consistent with the description above. When I went through this it was quite obvious with a screen full of similar values and one much bigger value in the middle so you could see almost at a glance whether there was a problem.
Edited by GreenV8S on Sunday 13th July 10:41
stevieturbo said:
Im so glad I dont use Megasquirt lol.
On the other hand, *everything* is accessible from the basic hardware design right up to the user interface. Completely unlikely the OMEX system I had before it, which while extremely powerful, came with zero documentation and with no information forthcoming from OMEX. You'd think I was trying to steal state secrets rather than get basic information about what the ECU thought it was doing and why.
Gassing Station | Engines & Drivetrain | Top of Page | What's New | My Stuff