TPS - incorrect signal reading

gun_hawk · Post by **gun_hawk** » Mon Mar 03, 2008 6:29 pm

I am using microsquirt version 2.88 . When I try to calibrte my TPS I get values of 2 for closed and 11 for Wide open trottle. This cause the TPS to only move from 0 percent to 1 percent.

Help please..

gun_hawk · Post by **gun_hawk** » Tue Mar 04, 2008 5:13 am

I checked the wiring as per manual . I am using the 20 valve silver top TPS . It has 4 wires.

Any help please.

Post by **grippo** » Tue Mar 04, 2008 2:10 pm

The tps that microsquirt is expecting has 3 wires - I am not sure it will work with your unit. You can either wait until someone replies who is familiar with your tps or show us an electrical diagram of it. Or you can measure the different terminals with a multimeter and see what voltages you get when you move the lever from full closed to full open. Ideally you should see 0 to 5 V, but even 0 to 1 V will work, but with poor resolution. If you see greater than 5 V, then you may have blown out the port.

gun_hawk · Post by **gun_hawk** » Tue Mar 04, 2008 8:34 pm

I re-flashed the ecu with code 2.88 and the TPS started to operate correctly . Then I reloaded my msq file and the controller lost connection with the laptop. I tried reflashing the ecu and it was successful but I still can't connect to microsquirt with megatune.

So I can connect to the controller with bootloader but cannot with megatune.

Help pleaase..

gun_hawk · Post by **gun_hawk** » Wed Mar 05, 2008 3:08 pm

I tried using port checker to find microsquirt and it did not find the microsquirt. However I notice that I am able to flash the microsquirt with or without the jumper connected . (strange)

I tried flashing it with and without the bootloader jumpered and it reported that 4 files skipped and 1429 records written.

It seems it is in a continous bootloader mode . This might be the reason why I can't connect to the controller.

Help again please

Post by **Bruce Bowling** » Wed Mar 05, 2008 3:48 pm

gun_hawk wrote:I re-flashed the ecu with code 2.88 and the TPS started to operate correctly . Then I reloaded my msq file and the controller lost connection with the laptop. I tried reflashing the ecu and it was successful but I still can't connect to microsquirt with megatune.

So I can connect to the controller with bootloader but cannot with megatune.

Help pleaase..

Please keep this in one thread so I can keep this straight.

So, you were able to download your MSQ after a bootload or not?

Are you re-cycling power to the MicroSquirt after reflashing and before you run MegaTune?

Are you setting the ECU type in MegaTune right after reflashing?

- Bruce

gun_hawk · Post by **gun_hawk** » Wed Mar 05, 2008 4:09 pm

So, you were able to download your MSQ after a bootload or not?

Yes I am recycling the power .
I tried and I even disconnected the battery at times.

When i try to set the ecu to 2 in the general menu i am unable to write the changes to the controller.

It seems in in a bootloader loop. ????

Post by **Bruce Bowling** » Wed Mar 05, 2008 4:30 pm

gun_hawk wrote:So, you were able to download your MSQ after a bootload or not?

Yes I am recycling the power .
I tried and I even disconnected the battery at times.

When i try to set the ecu to 2 in the general menu i am unable to write the changes to the controller.

It seems in in a bootloader loop. ????

Is the fuel pump cycling, and when you bring up MegaTune is the RPM jumping from 0 to 8000 back and forth? This is after you bootload, recycle power, bring up megatune.

If you observe this behavior then it is running the ECU firmware and not stuck in bootloader mode.

- Bruce

gun_hawk · Post by **gun_hawk** » Wed Mar 05, 2008 4:35 pm

I tried to reflash and I am now getting this message

MegaSquirt Download 1.04

Reading C:\Program Files\MegaSquirt\Firmware\MS-II\Monitor_v2.883j.abs.s19:
C:\Program Files\Metrowerks\CodeWarrior CW12_V3.1\MSIIC_Proj\bin\Monitor.abs
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3db380
File read successfully.

Opened comm port 1 at 115200.
Erasing main FLASH:
Erased.
Writing:
Setting page register 0x3c:
Page set.
Erasing page 0x3c:
Erased.
Setting page register 0x3d:
Page set.
Erasing page 0x3d:
Erased.
Write complete, 1429 records, 45677 bytes.
Verifying:
Setting page register 0x00:
Page set.
ERROR: Could not read monitor prompt, 0x00 0x3E 0x00
Elapsed time: 8.64 seconds

Post by **Bruce Bowling** » Wed Mar 05, 2008 4:50 pm

Email me off-list at bbowling@earthlink.net. I have never seen the situation where you can burn flash but it fails a verify, this is with thousands of MSII's and lots of MicroSquirts. You have a unique situation and I want to investigate...

- Bruce