After about 3 months of not trying to use mpscan it finally connected to my fwdperformance cal. I have no idea what is different. I just plugged the cable in and left all the settings as they were and it connected and works, Kinda.
First under t-2 gauge layout how can i select 3 bar map?
and second all gauges i can test seem to be working but the tach,
it is all over the place. At idle it bounces random all over the board. From 1k to 5k to 7k to 1k to 0 to 8k.......
How can this be resolved?
also noticed the dist PW is all over the place as well. Can someone take a look at theres and see what it does inder idle conditions.?
Does the FWDP cal use the same memory locations that MPScan is designed for? If you've got it set to look at what it thinks should be RPM but is in fact something else I can see why it would give bogus data.
My displays are all pretty steady at idle, but I'm running one of the turbonator based cals from here.
1) make sure you are using the correct ecu type. the t1 only sends 1 byte at a time and the lm/t2 stream bytes. so if you have it set up for a t1 but its a t2 you'll have problems.
2) as iangoround stated, without a disassembly of the fwd cal you cannot be certain of any ram address locations.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Hey wowzer, quick question. For some reason the displayed RPM I get is roughly half of what it should be in MPScan. I know there was a thread about this before and the answer was to change the scale in the layout file, but I can't find it. Do you remember what the answer was?
I'm an idiot. It was you talking to me about it a few months ago.
It is setup for t-2 but I'm not sure about ram locations
ian - should be a gauge called RPMLM. that should work.Originally Posted by iangoround
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Didn't see that at first. I guess I had to update the layout files. Thanks!
Posting Permissions
Reply With Quote