Moderator: djandruczyk
with MSnS 29v V3 on a Rover v8 with 36-1 and VR.
I would expect it to show the missing tooth in a far more pronounced way. It's possible that megatunix is screwing it up, or that the ECU isn't recording the data correctly. This is an expermental feature, and I DO NOT have a wheel signal simulator here on the bench in order to test it either... If anyone have a wheel signal generator (in hardware, I have no windows PC to use) thatthey are willing to donate, or long term loan it would help me to test this feature more thoroughly.istruggle2gate11 wrote:Hi all,
Im finally up and running
But when doing a log with meatunix, I dont seem to see a missing tooth.
So does megatunix display the missing tooth like a scope would?
Im assuming the vr is good as it starts quickly and runs nice.
This is a typical screen dump....
It's right at the TOP of the screen, trigger times in usec (microseconds)Jon k wrote:I have the same question - also, what the heck is the scale on the left?
By the way, it scrolled real slow, often pausing for like 5 secs before refreshing. Is this normal?djandruczyk wrote:It's right at the TOP of the screen, trigger times in usec (microseconds)Jon k wrote:I have the same question - also, what the heck is the scale on the left?
The MSnS-Extra site didn't have much documentation describing that feature, but I built the viewer as per their description, so if their description is incorrect, then the viewer may not be working as intended. It appeared to work for me on the stim, but my stim can't send a missing tooth signal,, but changes in RPM show changing in pip height which is expected, and it scrolls the correct way, so I figured it worked and those with missing tooth wheels could test it.
Yes It grabs a LARGE block of data (historical tooth/trigger times), as often as possible, and if you have the realtime vars running (comms/Runtime tabs) they will contend for I/O, so it's best to stop the RT vars to give the tooth/trigger logger all the I/O.Jon k wrote:By the way, it scrolled real slow, often pausing for like 5 secs before refreshing. Is this normal?djandruczyk wrote:It's right at the TOP of the screen, trigger times in usec (microseconds)Jon k wrote:I have the same question - also, what the heck is the scale on the left?
The MSnS-Extra site didn't have much documentation describing that feature, but I built the viewer as per their description, so if their description is incorrect, then the viewer may not be working as intended. It appeared to work for me on the stim, but my stim can't send a missing tooth signal,, but changes in RPM show changing in pip height which is expected, and it scrolls the correct way, so I figured it worked and those with missing tooth wheels could test it.
Ok cool - that may make it possible to see the missing tooth. Would it be better to enable tooth or trigger monitor. Probably tooth. Ask jsmcortina for more info, as he designed that feature in the firmware, I only made the frontend as per his docs.djandruczyk wrote:Yes It grabs a LARGE block of data (historical tooth/trigger times), as often as possible, and if you have the realtime vars running (comms/Runtime tabs) they will contend for I/O, so it's best to stop the RT vars to give the tooth/trigger logger all the I/O.Jon k wrote:By the way, it scrolled real slow, often pausing for like 5 secs before refreshing. Is this normal?djandruczyk wrote: It's right at the TOP of the screen, trigger times in usec (microseconds)
The MSnS-Extra site didn't have much documentation describing that feature, but I built the viewer as per their description, so if their description is incorrect, then the viewer may not be working as intended. It appeared to work for me on the stim, but my stim can't send a missing tooth signal,, but changes in RPM show changing in pip height which is expected, and it scrolls the correct way, so I figured it worked and those with missing tooth wheels could test it.
If you want to see the tooth you have to enable the tooth logger, that's why it is called tooth logger.....Jon k wrote:[Ok cool - that may make it possible to see the missing tooth. Would it be better to enable tooth or trigger monitor. Probably tooth.
When testing either, I didn't see a discernible difference between the two and how they logged - will look closer.jsmcortina wrote:If you want to see the tooth you have to enable the tooth logger, that's why it is called tooth logger.....Jon k wrote:[Ok cool - that may make it possible to see the missing tooth. Would it be better to enable tooth or trigger monitor. Probably tooth.
James
No niether do I, am I missing a basic setting James, on tooth log, I do have a dip in the middle - is that it?Jon k wrote:When testing either, I didn't see a discernible difference between the two and how they logged - will look closer.jsmcortina wrote:If you want to see the tooth you have to enable the tooth logger, that's why it is called tooth logger.....Jon k wrote:[Ok cool - that may make it possible to see the missing tooth. Would it be better to enable tooth or trigger monitor. Probably tooth.
James
OK, MegaTunix-0.9.10 has a WORKING tooth/trigger logger, which should show the missing teeth correctly. jsmcortina has validated it for me.istruggle2gate11 wrote:No niether do I, am I missing a basic setting James, on tooth log, I do have a dip in the middle - is that it?Jon k wrote:When testing either, I didn't see a discernible difference between the two and how they logged - will look closer.jsmcortina wrote: If you want to see the tooth you have to enable the tooth logger, that's why it is called tooth logger.....
James