- Wed Apr 19, 2023 4:26 pm
#62540
I’ve a dropbear in a jeep Cherokee, I’ve been using it for a few months now and I had no problems until now.
I was pulling a truck that was stuck the other day, after the second pull the car stopped and I was unable to start it again. In tunerstudio everything seems to be ok except I get no rpm when cranking. When trying to do a tooth log or composite log I get this error “Error: Unable to read Logger data. Controller Instruction failed! Error: Response packet failed validation: Controller reporting BUSY, 3 attempts made.”
I’ve a VR sensor with a 36-1 wheel and I’ve been testing the original jeep sensor 66-2-2-2 with Mike501’s decoder with some success, now in both cases I have no RPM, I even tried a spare sensor in the 36-1 wheel.
I tested the crank wiring for continuity and everything seem to be all right. I even have another teensy board installed but the problem still persists.
I’ve made a wiring for bench testing (only crank and power) but I can’t see RPM and the tooth logger error persist.
Any suggestions on what could be the problem or what can I do to identify the issue?
Imagen
I was pulling a truck that was stuck the other day, after the second pull the car stopped and I was unable to start it again. In tunerstudio everything seems to be ok except I get no rpm when cranking. When trying to do a tooth log or composite log I get this error “Error: Unable to read Logger data. Controller Instruction failed! Error: Response packet failed validation: Controller reporting BUSY, 3 attempts made.”
I’ve a VR sensor with a 36-1 wheel and I’ve been testing the original jeep sensor 66-2-2-2 with Mike501’s decoder with some success, now in both cases I have no RPM, I even tried a spare sensor in the 36-1 wheel.
I tested the crank wiring for continuity and everything seem to be all right. I even have another teensy board installed but the problem still persists.
I’ve made a wiring for bench testing (only crank and power) but I can’t see RPM and the tooth logger error persist.
Any suggestions on what could be the problem or what can I do to identify the issue?
Imagen
Attachments
Log
log.png (142.79 KiB) Viewed 9096 times
log.png (142.79 KiB) Viewed 9096 times