Changes by last author:
Added:
** be sure to upload the mdd0c terminal log (preferrably binary, not hex) taken during this condition. Your latest published log is from Feb 3 that didn't show the wheel error! |
It's a good idea for you to start to ask for help in a sufficient way: * document problem with related published logs (mdd0c and MegaTune logs. This way you'd have completed the project weeks ago). Phonecall without these is useless, a waste of time Other hints to try: * your internal crankhome-VR pullup (to 5V) is 43k (Ohm), that is weaker than the other successfull installs (because it's easy to make it stronger with external pullup, but not to make it weaker!) ** try an external 20..47k pullup * try to change to the 1.0.30 non-ALS firmware (http://www.vems.hu/files/Firmware/ ) ** the ALS firmware you are using requires extra attention during configuration (eg. can cut spark according to configured conditions you might not be aware of yet). You can switch back to an ALS enabled firmware later. * document your ground connections ** and flyback ** and fuses * upload uptodate mdd0c logs. This is very important. Especially when you have wheel errors. (I've told you this several times. Noone will be able to help without this) * also take logs (and upload) with MegaTune (this cannot be made at the same time as mdd0c so it needs to be a different starting attempt). This xls file (zip for upload) is very useful to verify that no unintentional fuelcut is configured. Eg. if you press the TPS > 65% (or so) during cranking, flood-clear mode will be activated (fuel pulsewidth=0). This would show up in the log. |