Future Profiles For OLV

For people running FreeEMS to discuss it and ask any questions about using and adjusting it.
Locked
User avatar
Fred
Moderator
Posts: 15431
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Future Profiles For OLV

Post by Fred »

This thread will contain guidelines on how to diagnose various situations. Many edits to come! :-)

Index:
  • Cranking To Verify Your RPM/Position Signal Integrity
If you have any suggested sets, additions, corrections or other comments, put them in the comments thread, here!

Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
User avatar
Fred
Moderator
Posts: 15431
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Cranking To Verify Your RPM/Position Signal Integrity

Post by Fred »

Cranking To Verify Your RPM/Position Signal Integrity

When setting up an engine for the first time, you will need to verify your RPM/Position signal is clean and stable! To do that you need to take a binary log using cutecom or similar and view it with OLV. When you do, follow this post as a guide to knowing what it all means :-)

Basic logs should be streaming from the device if it is a standard build, so simply plugging it in and beginning recording is sufficient. It is recommended that you power off and/or reset the device before commencing the log to ensure previous messing around hasn't polluted the data inside thus making it less clear what is happening.

If you need more information on the basics, read this thread first: viewtopic.php?f=54&t=1363

Main things that you need to see:
  • RPM - Should be stable and relatively noise free, without any spikes or dips.
  • currentEvent - Should increment up and fall down in a saw tooth pattern from zero to input event count minus one.
  • syncResetCalls - Should be at zero and stay at zero. If this is non-zero, or worse, increasing rapidly or saw-toothing, then you should see below for diagnostics on.
  • primaryTeethSeen - Should increment up and fall down in a saw tooth patten from zero to 255 fairly smoothly.
  • secondaryTeethSeen - Only if you're using a two input setup, otherwise this will just be zero, same as above.
  • inputEventTimeTolerance - Should be close to 1000 with minimal fluctuation up or down, and no spikes. When accelerating it will be a bit smaller and when decelerating it will be a bit larger. It will probably be biggest during starting and/or cranking.
If thing's don't look absolutely perfect above, then you'll need these too:
  • syncLostWithThisID - Tells you the reason why sync was lost, look up in a new file to be linked here from the docs site soon.
  • syncLostOnThisEvent - If this is random, then you've almost surely got the wrong decoder or bad noise issues.
  • syncCaughtOnThisEvent - Ditto, though all patterns are more likely to regain sync in certain places than others.
And also these, which should move from all zero to all one in the sequence listed:
  • DF-LAST_TIMESTAMP_VALID - Time of first input to the decoder
  • DF-LAST_PERIOD_VALID - Time of second input to the decoder
  • DF-LAST_MATCH_VALID - Only for missing tooth style setups, time of third input to the decoder.
  • DF-CrankSync and/or DF_CamSync and/or DF_CombustionSync - Depends on decoder, in future, several will support more than one.
  • DF-LAST_TPD_VALID - Currently not used in all decoders, indicates that loss of sync via time checking can be done and will start getting recorded on the next exection.
Other interesting fields:
  • MAP - It's interesting to see which input teeth have the highest and lowest MAP sensor readings, you can choose a better place for them to be taken using this field.
  • BRV - It's also interesting to see what happens to the battery Voltage during cranking as it can fall pretty low and it's worth knowing where it's going to for later setup of injector dead time and coil dwell curves with respect to Voltage.
  • Other analogue inputs: IAT, CHT, TPS, AAP - All of these should be smooth and stable at all times. If not, you need to look at your wiring. See this guide for more information.
Other log types to take
  • For lower resolution wheels the LA log type can be useful, however don't be deceived by it as it can miss information due to its low 1kHz resolution.
  • Future logging types will be useful here, however not yet.
See this for a guide on how to obtain and use each type: viewtopic.php?f=54&t=1363

Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Locked