sakpase

This is my setup:
LM-1
Turboedit 2.6.1 with ecucontrol plugin
ostrich 1.0
PM6 w/ datalogging cable attached

I can manipulate my afr but this is how i"m doing it. My idle was around 13.1....14.5:1
1. I change the map in the -24to-19Hig and 500to1100RPM range within Turboedit,
2. save that as a .BIN file.
3. open that .bin file with TunerProRT
4. upload that .bin file to the ostrich
Now my idle is pretty smooth with out the raw fuel smell at 15.5 17.0

Somebody's probably saying TE should be able to communicate with the ostrich, it doesn't and I can't even datalog with it even though I did when I first set my car up. I've search everywhere for help,(-------------, pgmfi.org, and synoptic) there where some people who had the same problem but no one posted fix. I know that TE is open source and I won't have any support with it. I just want to hook up a couple of wires and pop open 1 program maybe 2 and tune my ----, with out breaking the bank.

Can I datalog with the lm-1 without having to buy the auxbox or lma-2 cable?
should I convert to OBDI and go with ectune? I have a PO6 and distro.
should I keep struggling with TE and (not)


maybe I should just stick to fixing cars

sakpase

This is what I'm getting in turboedit.

*** Loading RTP environment..
*** Programmer: 2 COM: 4 Settings: 115200,n,8,1
*** --> Setting Baud Rate
*** --> Setting Read/Write Bank
*** --> Setting Emulation Bank
*** Looking for Ostrich..
*** Looking for Ostrich..
*** Looking for Ostrich..
*** Looking for Ostrich..
*** Unable to locate Ostrich. Something's wrong.

Chris Harris

Ostrich 1.0 you should have no problem if the COM ports are set correctly...

They have a newer version of TE on the PGMFI forums...talk to one of the guys here:
http://forum.pgmfi.org/viewtopic.php?f=60&t=15233

leed

I just used an Ost1.0 w/ TE.
I made sure the port settings in device Manager matched what I had set in TE options, and it connected right up.

I'm sure its just something simple.

NIGn0g

You have to get a version that support 920kbit transfert. The last version on pgmfi supported it and I made a version supporting it you can find it on pgmfi with some search

Xenocron, you are in the developper team? Do you have access to the source of TE for the last version? It's pissing me off... An open source project without source ... :1

Chris Harris

I told those guys I would help test if I could...but I dont have any OBD0 cars and they havent contacted me at all.

sakpase

which version of TE are you using, I've tried rolling the driver back for the ostrich, that didn't work so I updated it again.

and I've tried TE 3.1.4, 3.1.6. All on different baud rates and latency settings.


maybe it's this stupid laptop, i'm going to try my newer one and my desktop and see if they perform differently.

I'm sure it is also.

Thanks for the help so far guys.

sakpase

son of a...............

I got it, I got 3.1.2 to work of that link xeno sent so I went back and tried it with all the other version and it worked with each of them, I'm using com 1 920000 baud rate. I figure what I did wrong. when I made a change in device manager I didn't restart the computer. duh. damn that ---- was frustrating. especially when everyone was like, "don't know what your problem is works great for me."

now for datalogging, I have the DKU5 cable hooked up but that thing is too quarky, I'm going to put in an order for the hulog or maybe the LMA-2 cable

I hope actual tuning is a lot easier than setting up

thanks again fellas

kablammyman

the HULOG cable is a great buy. I tried teh DKU cable with very little success. I've never had an issue with the HULOG.

Glad to see that you got everythign working. Make sure to grab the latest ecuControl plug-in. Before I took my teg down, I was testing ecuControl, and suggested a few features and improvements. Its very easy to use now IMO, but its not perfect. All the features that are fully implemented seem to work great...now its just a matter of getting the rest of the features working. The only issue I can remeber is that map trace now has a feture that can tell you how far off your AFR is compared to your target AFR map. It can then make the adjustment for you, so you dont have to go back to the main turboEdit window to make the changes. However, the auctual % isnt 100% accurate, so I just see how far off my AFR is, then manually make more sensible adjustments.

Oh yeah, the latest rom (NG_62 ? ) has an issue with reading from the -3 cell. NG_62 was supposed to have the issue fixed, but according to the ecuControl map trace, the problem is still there. Theres a thread on it at the pgmfi forums.

sakpase

F.......it I'm going OBD1