Re:TurboEdit 1.29
 

think i found the problem went to make sure the MAP was plugged in good and it looks like one of the pins is bent! ------ GM POS ::) going to hit up the junkyard and snag a couple tomarrow....

Re:TurboEdit 1.29
 

Sorry your having problems Dustin. I will be spending more time on your car after Christmas. I made up a new spead sheet that more acurately converts your Zdyne maps to the 3bar modified TE maps. Should smooth things out.

Re:TurboEdit 1.29
 

well it may correct its self with the plug fixed, went for a ride to the store and it seemed to be a lot better...thinkin its not the tunes fault its that gay ------ connector looks like it has been bent, then bent back a couple times. but it does need some WB tuning for sure, put the Zdyne back in to seal the deal for the sale (wanted proof?) and it was rippin hard. thinkin it could use some more timing?

think this needs a little more paciants from me...thanks again Dave for helping out.

Re:TurboEdit 1.29
 

Sorry I haven't been replying.. the combination of me being sick and no Internet access at the new homestead has left me sort of out of the loop.

TE2.0? ..Well, I might have a "prerelease" out because Blundar is having a cow about no one being able to edit the new boost bin... sooooo.. I'll probably release a little taste of TE2.0 on Friday.

As for the boost transition, I don't use the GeorgeHack ROM myself, so I don't know, but I did try using the TE boost retard feature on a stock NA ignition table and is smoothed out the transition quite a bit.

Right now I'm using the new boost bin, and there are 0 glitches, hiccups, or whatever you want to call them. Transition is perfect. Now, scaling for a 3bar, if you want to get me the voltage scale, I'll see if I can sneak a possible routine in for scaling automatically.

Re:TurboEdit 1.29
 

I hope you're all better now Jason..I got the flu during the weekend to.
I can edit the new boost bin though ;D.
the PGMFI forum is awesome.

Re:TurboEdit 1.29
 

Seems Blundar has stumbled upon OBD0 scalars, he and I will be working together to implement them this afternoon. This might make the "preprelease". Also, I think I might have figure out what is wrong with my car causing me to fry MAX233As... any I'll test tht theory tomorrow.

Re:TurboEdit 1.29
 

Try19 is tight, yo!

Opening the BIN took some coaching but after you the right help (thanks PGMFI)...its pretty cake.

Blundar's good at coding...but his guessing on the maps leaves much to be deisred :P which is why try19 runs severly lean...make sure you richen it up before running.

Scalers within TE i think would make things much, much, much less dangerous than using his excel file...hehe

EVIL I tell yah!

Re:TurboEdit 1.29
 

Ok turds, in order to give you 2bar/2.25bar/2.5bar/3bar/7bar (heh) MAP sensor support, I need a couple things:

-I need to know the stock honda MAP sensor voltage at idle (preferably on the same car that a 2bar/3bar/etc is used on)

Then for each sensor you would like good support for, I need the following:
-MAP voltage key on, motor off.
-MAP voltage at idle
-MAXIMUM MAP VOLTAGE that the sensor goes to.
-BOOST PRESSURE at MAXIUMUM VOLTAGE.

MAP voltage at idle / key on-motor off is fairly self explanatory.

To figure out the maximums:
1. disconnect your MAP sensor vacuum line from the intake manifold.
2. Connect it using a T-fitting or something similar to an old valve stem from a tire.
3. "Fill" the MAP sensor using a tire inflation attachment with enough pressure so that you are at least 10% above what the sensor "should" read. (35 psi for 3bar, 18psi for 2bar, etc.)
4. Measure the pressure to verify that it is significantly above the theoretical maximum pressure the sensor can read.
5. Connect a multimeter between signal and ground on the MAP and record the MAXIMUM VOLTAGE. (3 or more significant figures please)
6. Add more pressure. The voltage should remain constant and NOT increase further. Expect: 4.5v - 5v
7. Slowly bleed pressure out of the valve stem. As soon as you see the MAP voltage drop at all, take a pressure reading. This is the MAXIMUM PRESSURE.

With these values, I can plot out the voltage/pressure curve well enough to add support for whatever MAP sensors you want to measure.

If you wanna get *really* spiffy and make me want to send you free donuts, datalog RAM 0A8h. ECUcontrol will not do this anymore due to changes to be realtime-programmable friendly... I don't have high hopes here.

Oh yeah, if you want realtime programmability sooner rather than later (like your zdyne) send a donation to pgmfi@pgmfi.org ... The last round of prototype boards cost $57, the USB UARTs are going to be about the same for 10 of em, the NVSRAMs are expensive as ----... A lot of the development at PGMFI (like this code) doesn't cost me / others anything other than our time. The hardware development on the other hand gets really $$$ real quick. $5 here and $10 there would really help...

And FYI: admin@pgmfi.org = me. pgmfi@pgmfi.org = the Site's paypal account. Seperate. The site also has its own bank account, in PGMFI's name. Copies of the PGMFI@PGMFI.org paypal account and bank account history are available on request to anyone who would like to see how money has been spent.

Sorry to beg, but I'm getting a little scared at how much personal funds are going to be involved in finishing off the realtime boards in the coming months. Guess: $500-800 for the first 20. If you contribute now while development is still ongoing, I solemnly swear you will have the opportunity to get a kit at *cost* or an assembled unit significanly cheaper than otherwise.

peace
-Dave

Re:TurboEdit 1.29
 

Just awesome....I'll have to get back at you for the stock map. I want to run a 2bar GM map, but I don't have it right now

Re:TurboEdit 1.29
 

Ill have stock and 3bar info up tonight Blundar. I plotted voltage vs map readings from my Hondata logs and came up with some good data. Also came up with a quick formula to convert from Honda/3bar Votages and Hg readings.

Re:TurboEdit 1.29
 

Parker,

Blundar tells me I flattened out the tune of his beta ROM maps...

Is there something buggy in TE that when you edit the entire map grid by increases in percentages, it does funny things? Check it out, because I did notice that say I increased the entire map by 100%, then I decreased by 50%...the map wasnt the same as when it started.

Seems odd...

Re:TurboEdit 1.29
 

Sent you some ish Blundar.

Re:TurboEdit 1.29
 

some ish is a ------- understatement and a half leed.
Thankyou *very* much.

Re:TurboEdit 1.29
 

hahahaah lol better said...leed mail bombed you some ish ;)

Re:TurboEdit 1.29
 

Uhm, well, if you increase by 100%, then decrease by 50%, you're effectively increasing by 50%. So it wouldn't be expected to be the same?

But I tested it your concept, and it works fine. The minor differences (.01) are attributed to the conversion formulas and rounding. .01 differences will not effect the overall value due to the integer numeric used in the bin itself.

Re:TurboEdit 1.29
 

Isn't increasing by 100% like multiplying by 2 and decreasing by 50% deviding by 2 ??

Re:TurboEdit 1.29
 

HA! Ya.. I confused myself.. :) I was thinking with the initial value.

..but the differences he sees is the rouding..

Re:TurboEdit 1.29
 

I thought so ;D

Re:TurboEdit 1.29
 

I've just started using turboedit and i used the ghettodyne 450 with boost bin just to take the car out for the first time, i think its based on the georgehack rom, this doesnt work too good on my ZC, can you guys advise me on a map to use with it ???

Re:TurboEdit 1.29
 

New boost code...check out www.pgmfi.org ..forum

Re:TurboEdit 1.29
 

Yo Semnos you're running a ZC aren't you? What kind of setup is it and what boost bin are you using? I'm assuming you are boosted.

Re:TurboEdit 1.29
 

No more ZC .... I was running a hack.

Re:TurboEdit 1.29
 

Im not sure what was happening in my version...weird things.

Seems to be working better in 2.0...tomorrow ill be out testing and trying to actaully get a decent tune for try21...

By decent i mean not blowing up my ---- and getting somewhat steady 11.0 - 11.8 afrs.

Ill post on PGMFI sometime tomorrow night.

Re:TurboEdit 1.29
 

I'm working on the Te2.0 datalogger... So far, it's HOT! I've been running it in my car the last few days making sure it doesn't crash, and making it faster and such, it's coming along great.

I believe the next step with it is to start talking.. you guessed it, Real Time Programming. :D

Re:TurboEdit 1.29
 

All right. This is what I've been waiting for. ;D ;D ;D

Keep us up to date on that shizz too.

*edit- will this completely remove the need for a batronix (or the like) unit?

Re:TurboEdit 1.29
 

I emailed Leed a 3bar-friendly version of the code.
If anyone else has a 3bar and wants to test it, EMAIL me.

Re:TurboEdit 1.29
 

Still waiting for the beta testing :-)

blindfashion@msn.com


Josh Ross

Re:TurboEdit 1.29
 

Re:NEW!!!!! TurboEDIT 2.0 BETA GET IT WHILE IT'S HOT!!!!!!!!!!!
 

TurboEDIT 2.0 Beta is now available for use...

Anyone who wants it can download and test out a lot of the new features, give feedback, do whatever..

For information on downloading, and latest bug tracking, and feature addition..

http://www.TurboEDIT.org click SUPPORT

Re:NEW!!!!! TurboEDIT 2.0 BETA GET IT WHILE IT'S HOT!!!!!!!!!!!
 

great work, any plans for a Pocket PC version of TurboEdit?

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

I'm running TE 2.0 with the PM6 stock rom (try19) opened up for boost as I am getting everything together to burn a chip for my ecu. The problem is that the boost cut option will not save at the value I specify and the MAP sensor I select will not stay. I am trying to put the boost cut at 12 but it always returns to 77. I figure the MAP sensor one will not matter as I am trying to select stock but it always returns as unmarked. The tune information will not be retained, either.
Also, maybe it's just me, but I don't notice the maps changing when selecting a different map sensor or by changing the adv/retard on timing.
Stable bin from blundar will adjust timing, but map does not change anything on maps.
TurboEF9- Is the timing on this PM6 map already retarded for boost or is the boost timing map showing a stock timing at 0 vacuum?

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

Remember, the TE2.0 you're running is still a beta..

Not all of the ROM's features have been activated, so to keep people from corrupting the ROM, I have certain things disabled. If you notice osmething isn't saving, it's been disabled. The only reason you can get to it is because I wanted to make sure that the value works in TE so when the ROM is ready, it will be nothing but just turning it on.

Tuning Comments are not a big deal, I'll make those active when I realease Try7..

-- I do believe the map is retarded a bit.. I don't know, I didn't create the tune. Dave did.. You might pop and e-mal to him.. If it's not retarded, then you can use the TE Boost Retard function to retard it.

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

I thought that might have been the case, but I wanted to ask to make sure I wasn't doing it incorrectly. Keep up the great work. I look forward to boosting my A6 (once I get all my parts together). Thanks.

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

I've been perusing the forums and pgmfi, but the answer to my question remains unanswered...

I have a pr4, that will run a b18a. do I use the pm6 with boost maps? or is there a pr4 map with boost that I should be using? I just cannot get my mind straight on that.

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

you should run pr4 maps if at all possible because your motor will require more fuel than the d16 the pm6 came with. if you cannot find a pr4 map (someone should have one) then you could richen the fuel tables up a bit and try, but be sure you have a way to check this with A/F or EGT or wideband O2

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

bike is correct.

You can use PR4 basedmaps in the PM6 code on a PM6 ECU. I'm not sure of the status of running the PM6 code on the PR4 ECU as there has been unconfirmed knowledge if this works. Some say it does, some say it doesn't.

When I figure out my brakes situation, I'll chip my PR4 and throw it in and see what's up for myself, and let everyone know.

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

Parker, I loaded up George's PM7 try21 ROM in my PA-less PR4 and it ran...and boosted well. It was very rich in boost tho and that was all I tested...just so everyone knows.

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

Awesome.. Looks like things are back on track.


Leed tested TurboEDIT Try7 (which hasn't been released so don't go looking for it, anyone :P ) with his ROMulator and it loaded up and ran the car perfectly. :D

When I get my ROMulator back, I'll finish the byte changes and ROMulator RTP will be done. :D

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

any new info on support for obd1??? :) *cross's fingers*

-P

Re:TurboEDIT Support (OBD0) - Current Verison: 2.0 Beta
 

I am hoping for some PR3/PW0 boost support. Getting a supercharger for my EF8 SiR and need something to use for engine management. run out of money.

btw, love your work, love the program =] hint hint