Syvecs Forums

Here you go: http://www.syvecs.co.uk/forum/viewtopic ... 3ee9#p4579

Here you go: http://www.syvecs.co.uk/forum/viewtopic ... 3ee9#p4579

I quickly edited the screenshot Stevie posted with the correct values, based on what you reported from SCal. It should give you an idea of how to get the values you want from SCal into the vbox software. Scale is a multiplier, so if SCal reports x/81.92, the vbox software wants x * 0.01220703125, wh...

So...turns out you can really confuse yourself if you change the speed unit in SCal to mph, instead of km/h, and forget to change it back

It certainly is strange. I never noticed it when originally configured, simply drove around in the parking lot to check all wheels read the same, not comparing with GPS/Speedo. Only discovered much later the ECU reading was off. With the new circ, speed in ECU is correct, but now logdistance is wron...

Just to add to this old thread.

On my vehicle with 235/40R18 tyres, and 45 tooth trigger wheels with 15 teeth per reading, I need to set circumference to 3.190m, instead of the expected 2.026m that I measured on the ground.

Can anyone tell me what the function of the "Playback" menu item is in SCal, in the Device menu?

Are you experiencing any driveability issues? From looking at the log, it just seems like the overrun fuel cut is kicking in at the point in time you mention.

I would ignore this until your wideband issue is resolved. Once the fuel cut is registered, it does seem the wideband is "lazy" in going leaner, which could be due to running incorrect temperature.

The Nissan speedo needs a sine wave yes, but it doesn't need to be a perfect sine wave. A poor quality sine wave will work, as long as it crosses 0V. The speedo triggers on 0V, and needs 10000 pulses per km, or 16000 pulses per mile. My pulses per meter is set to 10 under Output Functions->Trip Mete...