8e11675afd
* smart gpio: fix tle8888 direct pin mapping for MRE * MRE: use TLE8888 pins instead of MCU gpios that drives TLE8888 * TLE8888: cleanup * TLE8888: do not reset driver private data on WD/undervoltage reset * TLE8888: diagnostic updates * TLE8888 driver: BIG driver rework * TLE8888: check SPI answers for abnormal states Reply with other than requested register can be a sign of: -Power-On-Reset, then OpStat0 will be replyed -WatchDog reset, then FWDStat1 will be replyed -Invalid communication frame, then Diag0 will be replyed Keep tracking last accessed register and check with the next reply. * TLE8888: debug clean-up * TLE8888: implement spi array write This reduce CS inactive state time between two consequent accesses from 8.8 uS to 1.4 uS * TLE8888: fix PP outputs in OD mode * TLE8888: cleanup register definitions * TLE8888: run separate driver thread for each chip instance Calculating poll interval for few chips become more complex, avoid this running thread for each device. * TLE8888: fix cypress and kinetic compilation Both platforms define its own MAX and cause redifination error if common.h is included in driver. * MRE: update mapping.yaml and fix direct pin mapping for TLE8888 * TLE8888: diagnnostic: disable switch off in case of overcurrent For all output, use current limiting instead * TLE8888: check for overvoltage on OUT8..OUT13 * TLE8888: add TODO note about how to recover from failure condition Currently TLE8888 automaticly recovers only from overcurrent and (may be) overtemperature conditions. Short to bat cause output disable (bit in OECONFIG is reset) and needs driver/host intervention. * TLE8888: save few bytes of RAM * TLE8888: Lada Kalina is test mule for IDLE stepper on TLE8888 Don't forget to enable PP mode for TLE8888 outputs 21..24: uncomment line 1087 in tle8888.c * TLE8888: reorder code, cleanup * TLE8888: mode all debug/statisctic to per-chip struct * TLE8888: rework poll interval calculation * MRE: use TLE8888 pins instead of MCU gpios that drives TLE8888 #2 |
||
|---|---|---|
| .. | ||
| GY6_139QMB.cpp | ||
| GY6_139QMB.h | ||
| bmw_e34.cpp | ||
| bmw_e34.h | ||
| bmw_m73.cpp | ||
| bmw_m73.h | ||
| bmw_m73_mre.cpp | ||
| chevrolet_c20_1973.cpp | ||
| chevrolet_c20_1973.h | ||
| chevrolet_camaro_4.cpp | ||
| chevrolet_camaro_4.h | ||
| citroenBerlingoTU3JP.cpp | ||
| citroenBerlingoTU3JP.h | ||
| custom_engine.cpp | ||
| custom_engine.h | ||
| dodge_neon.cpp | ||
| dodge_neon.h | ||
| dodge_ram.cpp | ||
| dodge_ram.h | ||
| engine_template.cpp | ||
| engine_template.h | ||
| engines.mk | ||
| ford_1995_inline_6.cpp | ||
| ford_1995_inline_6.h | ||
| ford_aspire.cpp | ||
| ford_aspire.h | ||
| ford_festiva.cpp | ||
| ford_festiva.h | ||
| ford_fiesta.cpp | ||
| ford_fiesta.h | ||
| honda_600.cpp | ||
| honda_600.h | ||
| honda_accord.cpp | ||
| honda_accord.h | ||
| lada_kalina.cpp | ||
| lada_kalina.h | ||
| mazda_626.cpp | ||
| mazda_626.h | ||
| mazda_miata.cpp | ||
| mazda_miata.h | ||
| mazda_miata_1_6.cpp | ||
| mazda_miata_1_6.h | ||
| mazda_miata_base_maps.cpp | ||
| mazda_miata_base_maps.h | ||
| mazda_miata_custom_hunchback.cpp | ||
| mazda_miata_na8.cpp | ||
| mazda_miata_na8.h | ||
| mazda_miata_nb.cpp | ||
| mazda_miata_nb.h | ||
| mazda_miata_vvt.cpp | ||
| mazda_miata_vvt.h | ||
| me7pnp.cpp | ||
| me7pnp.h | ||
| mitsubishi.cpp | ||
| mitsubishi.h | ||
| nissan_primera.cpp | ||
| nissan_primera.h | ||
| readme.md | ||
| rover_v8.cpp | ||
| rover_v8.h | ||
| sachs.cpp | ||
| sachs.h | ||
| subaru.cpp | ||
| subaru.h | ||
| test_engine.cpp | ||
| test_engine.h | ||
| toyota_jzs147.cpp | ||
| toyota_jzs147.h | ||
| vw.cpp | ||
| vw.h | ||
| vw_b6.cpp | ||
| vw_b6.h | ||
| zil130.cpp | ||
| zil130.h | ||
readme.md
This directory contains pre-defined configurations for popular engines.
These configurations are a convenience, not a limit. Most engine types can be manually configured.
In TunerStudio or rusEfi console use the "Popular Vehicles" dialog to apply one of these presets.
See http://rusefi.com/wiki/index.php?title=Manual:Engine_Type
This folder is also used by the continuous integration testing suite.
New configurations should follow the pattern of .cpp for consistency. A future change may rename these to .cpp