interesting, a some of those guys are saying the exact opposite from what the stock timing maps indicate.. high split in vacuum, low to no split in boost??

it was my impression that with no split, it causes the two flame fronts to collide more violently, causing a more powerful reaction, but more uncontrolled. and a bigger split makes for a more controlled, rolling combustion, which is what you want in a higher risk area of the map for detonation (high load areas, i.e. high boost, low rpm). im no expert, thats just what i picked up from reading on the forums. i would really like to understand the physics behind negative split though

 

I don't know, but there is a wide range of different degrees of split that people use. I'm definetly going to run split in boost, but I'm debating how much I want to run under vac.

 

I know adjusting timing splits in vac/no boost affects fuel consumption

 

Holy crap I just lost my whole split map as I was making changes and it reverted back to stock. Its going to take me a while to change it back.


This is with a Palm Zire 71

 

wow that sucks....hope it doesn't do that while driving

 

Well when I was trying to reload all of the split map it crashed again and I lost almost everything. I tried to reload a saved map but it wouldn't do it. All of my settings got screwed big time. It wouldn't even let me view the fuel corrections tables without freezing up.


So I deleted RTEK of the palm and reloaded it again. Reconnected to the ECU and looked at the lead timing map and I was suprised to see my settings where still there. I had to set it to map based again.

Tried to start it, but no start. Looked at the starting fuel and it was zeroed out. So I gave it 33ms across the board for now and it started right up.

Set my parameters, VR analog PLX for logging. But now my VR analog is not reading a signal!!? WTF


So I have to figure out why my VR analog is not reading my PLX now. It was before. Remap the split timing and check my lead timing to make sure it didn't get messed up.

I'll check the output signal from the PLX box to make sure it putting out a signal.

VR analog reads a constant 16.59 and doesn't move. It might blip when I connect and disconnect the palm to the ecu.

 

The split map didn't really go to stock setting. It left some of mine there but somehow most of the map went 40-56 advanced

 

did you try reinitializing the ecu? then reloading your saved map? but yah that sucks. it took me like 30-45 minutes to change my timing map to the way i want it.

was your v/r working before? I have my eugo wb hooked up to it with no problems

 

Yep I tried that also.


This is what I did this morning.


I checked the voltage output on the PLX box and I'm getting readings from 3-4 volts so I know my PLX wideband is sending a signal out. On the palm is just reads 1.50 now and I have the external sensor clicked as PLX.


When I try to reload the a map it goes into connection change error and only loads a small part of the timing map.

I reset the ECU and it goes back to stock fine, but it won't load my maps for some reason.

When I try to view the fuel correction maps it freezes the palm.


When I had the 2.0 I didn't have any problems. Any suggestions?


Yes the palm was showing me a wideband signal before it started to give me problems

 

Please email me your maps.pdb file.

 

i still have the random disconnection while logging?

i think the pda cable connector is getting loose though

 

I sent it to support@pocketlogger.com. Hopefully thats the right one.


For some reason it disconnects when I'm trying to load the maps. And its still a no go for VR analog

 

So you are using the map setting for timing? How has this worked for you?

Its always a good idea to save when working on computers.

'I think' the timing numbers look pretty good, but 'I think' I'm going to run less or no split in vac and 0psi. I've read N/A cars can run less split for more power.

As to fuel correction, can you post those maps? I was supposed to get my ecu in the mail yesterday, but I wasn't there to sign...

I plan to start w/ stock turbo, Inj's, and IC. Then move up to Hybrid TO4b w/ FMIC and 680 and 800cc inj. If anyone has any tips/tricks or valuable information that I should know, hook it up! Even if it is not related to tuning.

Thanks!

 

Yeah I'm using the map based timing.


I was able to fix my split map and some of my lead timing map that got messed up somehow. So I took a drive to the Trenton area to check out some fish stores and I thought the car felt good, but I think your right and from reading other threads. The split map should have less to no split in vac.


This is how I had it set up on my test cruise.


16-------- 15
14-------- 12
13-------- 11
11-------- 10
10-------- 10
8-------- 10
7-------- 9
5-------- 8
4-------- 7
2-------- 5
1-------- 3
1-------- 0
-4-------- 3
-7-------- 5
-10-------- 6
-13-------- 7
-16-------- 8
-19-------- 8

So right now I'm going to change a few things. Look at my connection to the ECU for my VR analog in. Then get some logs in.

 

I dunno if this is crazy, but has anyone tried a palm emulator running on a laptop?

 

no, but im sure you would still run into the same problem of the emulator screen being to small to view the whole map

 

this is your split map right

 

Yes thats my split map that I'm currently using. I'm going to be trying something closer to negative split or even -5 in the high vac area's.


I don't remeber If I posted this one yet.
https://www.rx7club.com/showthread.p...e+split+vacuum

 

anybody else having problems viewing certain logs in plviewer? I keep getting an unsupported parameter ID 253 error with the three logs i made yesterday. i attached one

 

Yeah I tried to view a log on PLviewer also with my newer logs and I get the same error. It still works with my older logs though.

 

ok, i made a help ticket at digital tuning

 

I had the same problem as well using

 

What parameters are logged in the logs that give this error? And do you have the newest viewer from the website?

 

never mind

 

Thats usually from trying to view version 1 logs with version 2 pocketlogger.