News:

New Users: Send [email protected] an email with your account name. I've turned off auto-approve to reduce the 100 new spam accounts a day. Thanks, -Jason

Main Menu

VEMS Log Viewer Software

Started by hilly, January 09, 2009, 04:08:40 PM

Previous topic - Next topic

hilly

I have got an install which keeps reporting trigger errors, once the viewer detects an error it locks the message on screen so trying to work out how many and when is impossible.

I have looked through a datalog .xls to try and chase down exactly when they are happening, but can't figure out where the trigger error information is in the spreadsheet.

Anyone know how the trigger errors logged ???

Hilly

GintsK

Look at vemsv3.ini:

indicator = {status1 & 0b10000000}, "ALS Off", "ALS Sw On", white, black, blue, black
   indicator = {status1 & 0b01000000}, "Launch Off", "Launch Sw On", white, black, blue, black
   indicator = {status1 & 0b00100000}, "Shift-cut Off", "Shift-cut Sw On", white, black, blue, black
   indicator = {status1 & 0b00010000}, "---", "Soft Igncut Idle", white , black, red, black
;   indicator = {status1 & 0b00001000}, "IAC Off", "IAC On", white, black, green, black
   indicator = {status1 & 0b00001000}, "Slot 0", "Slot 1", white, black, green, black
   indicator = {status1 & 0b00000100}, "EGO off", "EGO On", white, black, green, black
   indicator = {status1 & 0b00000010}, "---", "Trigger Errors", white, black, red, black
   indicator = {status1 & 0b00000001}, "---", "ALS Active", white, black, red, black

and then in datalog definitions area:
    entry = status1,         "StatusBits", int, "%d"

So you must observe Bit7 is Yes in datalog.

But I suppose you cant count errors. It is like a flag. If error occurs flag switches on and stays until restart.

hilly

Quote from: GintsK on January 10, 2009, 01:19:15 AM
Look at vemsv3.ini:

indicator = {status1 & 0b10000000}, "ALS Off", "ALS Sw On", white, black, blue, black
   indicator = {status1 & 0b01000000}, "Launch Off", "Launch Sw On", white, black, blue, black
   indicator = {status1 & 0b00100000}, "Shift-cut Off", "Shift-cut Sw On", white, black, blue, black
   indicator = {status1 & 0b00010000}, "---", "Soft Igncut Idle", white , black, red, black
;   indicator = {status1 & 0b00001000}, "IAC Off", "IAC On", white, black, green, black
   indicator = {status1 & 0b00001000}, "Slot 0", "Slot 1", white, black, green, black
   indicator = {status1 & 0b00000100}, "EGO off", "EGO On", white, black, green, black
   indicator = {status1 & 0b00000010}, "---", "Trigger Errors", white, black, red, black
   indicator = {status1 & 0b00000001}, "---", "ALS Active", white, black, red, black

and then in datalog definitions area:
    entry = status1,         "StatusBits", int, "%d"

So you must observe Bit7 is Yes in datalog.

But I suppose you cant count errors. It is like a flag. If error occurs flag switches on and stays until restart.

Thanks for the reply

Hmmmmm, looks like I can't count the number of errors then.

More head scratching then

Hilly

GintsK


smurfinator

Isn't this a lovely endeavor?  I just want to do 4-wheel burnouts.  No more head scratching over tiny silicon bits  >:(
Audi ABZ 4.2 V8 in 1993 90 quattro
TTV 60-2 flywheel and cam sync
firmware: 1.2.20

Smurf blue (BMW Laguna Seca), hence the name!