My single car license testing info.

WILD_EYE · Post by **WILD_EYE** » Wed Nov 14, 2007 9:42 pm

I have not gone too far yet but.... So far I have just registered the application with my pc, registered and paired the ostrich. All done smoothly. The only thing I can think of recommending would be for a pop up message box to let the new user know that the error message (missing file: license.xml) is normal and to click continue and go to help to register. I had no issues but others that are less pc inclined might find the inital error message confusing and think the installation went bad. Might help stop some e-mails asking why is t not working right away (At work I am used to making things fool-proof). I then connected the ostrich to my pc with no issues. I have been browsing the application to get to know where everything is.... so far it has been intuitive and things are not hard to find or understand. While at work I have also been looking at the help online to know more about the features before I start playing with them. The only other thing would be what bindegal mentioned about the ostrich pairing. If you use that ostrich to attend other cars with another application then it will be a bit of a hassle to have to re-register the ostrich everytime you need to use it for another car.... which is why I am getting another ostrich

. Hopefully I can get to put it in my car tomorrow and get more data. Stay tuned...

Post by **calvin** » Wed Nov 14, 2007 10:12 pm

missing error license.xml is not normal i'll have a look

WILD_EYE · Post by **WILD_EYE** » Wed Nov 14, 2007 10:14 pm

I had made a print screen of the error. I'll post the pic when I get home.

WILD_EYE · Post by **WILD_EYE** » Thu Nov 15, 2007 12:59 am

Here is the print screen of the error.

I had found it strange but I figured it was some type of insurance for registration.

borat · Post by **borat** » Thu Nov 15, 2007 1:11 am

I had the same error. It happens when ectune is not registered yet. It popped up when I would click on pretty much any dialog/setting menu.

Minor Threat · Post by **Minor Threat** » Thu Nov 15, 2007 4:37 am

Mine didn't do that.

Post by **calvin** » Thu Nov 15, 2007 6:09 am

i'll have a look thank you. 0020 r4 version?

Post by **calvin** » Thu Nov 15, 2007 8:42 am

Fixed this

2kCivicSi · Post by **2kCivicSi** » Thu Nov 15, 2007 10:45 am

I didn't have this issue. I was already using the datalogger version and I got my license.xml before I ran the pro version the first time.

WILD_EYE · Post by **WILD_EYE** » Thu Nov 15, 2007 5:13 pm

Glad the info helped. Today I finally got to put the ostrich in with my laptop and check things out a bit more. To have things well documented I am going to give my car info first for future reference: 1996 honda civic cx (1.6L) non v-tec obd2a. stock block d16y8 intake manifold w/IAC stock fuel regulator obd1 240cc 92-95 injectors p06 ecu converted to p28 plx m300 wideband t25 turbocharger 7psi spring (I have rc 750's, a gt2871r, ross pistons and crower rods waiting to go in soon....now I'm really motivated

) I have the wideband power and ground coming from the ecu (some say that's not good, I have had no problems with it but I might change the power to direct from battery). Before starting the car I opened up ectune, connected the ostrich to my pc and ecu and chose my ecu info. p28 ecu, p2p d16y8 maps 6 columns of boost .75 retard %120 efficiency. I set the idle portion of timing in the maps to 12*. Put the base rom and calibration to the emu and started the car. The car started up and right away gave me a check engine. I remembered the error code feature so I started the datalogger and then checked the error codes. It was the oxygen sensor. There I realized I had not disabled the o2. I went to closedloop and disabled the o2. I deleted the dtc and .... mil was gone and the car was fine. Just to see I checked the PCS and inverted the output. As soon as I checked the box a hissing sound was heard right away meaning the vacuum was open so I unchecked the invert pcs box and the hissing stopped. It was interesting since I did not have to put the rom in the emu after playing with the pcs, it was a direct effect. The error code checking was great, resetting the mil without having to disconnect the battery was A++++. That's it for now... tomorrow I will do some test runs and start tuning with it. edit... I just saw the other posts. I will check if it is version 0020 r4 and post it up top with my other info.

Post by **calvin** » Thu Nov 15, 2007 5:33 pm

try using Key On Engine off & TPS to check mil, press brake to clear the codes. No laptop needed.(service check connector options)

zex_cool · Post by **zex_cool** » Thu Nov 15, 2007 8:14 pm

calvin wrote:Fixed this

i still keep getting it. we'll see what happens when i get the reg. code from you.

Post by **calvin** » Thu Nov 15, 2007 10:49 pm

i didn't release an update so you cannot have \"fixed\" version. So offcourse you will still get it

zex_cool · Post by **zex_cool** » Thu Nov 15, 2007 11:58 pm

got the code. no more error msg.

whats the point of having it unless its registered anyways ?

Post by **calvin** » Fri Nov 16, 2007 6:06 am

logger version