Wideband Direct serial tester wanted(ZE, TE, Aem, FJO, PLX)

Post by **calvin** » Tue Feb 03, 2009 9:21 pm

i'll ADD PLX iMFD widebands and egt too;)

RoadXY · Post by **RoadXY** » Wed Feb 04, 2009 7:33 am

David974 wrote:Calvin i think i did some thing wrong when i install the version test so could you give me step by step i unzip it and paste file in ectune directory is it good? also remove the old ones

That's right. Just overwrite the file's in the eCtune folder with the one from the archive.

Orthello · Post by **Orthello** » Wed Feb 04, 2009 11:04 am

Bindegal wrote:David: Try verifying serial connection to the Tech Edge using TEWBlog first. If the COM port is somehow not working, eCtune will have problems as well. Another thing... I notice that sometimes Windows can mistake a wideband controller for a mouse. Thus Windows will block/use the port connected to the wideband, and eCtune/TEWBlog canÂ´t connect. Take a look in hardware manager, and if a serial mouse somehow magically appears when the wideband is connected - disable it. /Allan

The 'famous' (NOOOOOT) "ballpoint" issue... See: http://board.homeseer.com/showthread.php?p=636601 This is an RFid cardreader having the same problem. Also GPS receivers are known to experience this mouse/ballpoint behaviour. Read the text as if it is about eCtune/serial WB logging instead of RFid readers. Ignore step 2 (Shut down Homeseer)

David974 · Post by **David974** » Wed Feb 04, 2009 3:13 pm

RoadXY wrote:
David974 wrote:Calvin i think i did some thing wrong when i install the version test so could you give me step by step i unzip it and paste file in ectune directory is it good? also remove the old ones
That's right. Just overwrite the file's in the eCtune folder with the one from the archive.

this morning i had big issue with version test and didn't have my laptop with me the car stop everytime a let of the throttle, or put to much load on the engine, it stoped flooded, smell the fuel, very hard to restart after (very hard with 2 kids on the back seat too) Back at home I re connect my laptop removed version test and after 3 calibration upload , i can get the car back to normal. this evening i retried the Version test and still the same no communication , status says connected but no display should i delete the 3 old files because i put them in a new folder on my desktop instead of deleting I tried Tewblog,it worked alone, i 'll try tomorrow before , and then after on ectune regards

Orthello · Post by **Orthello** » Wed Feb 04, 2009 3:20 pm

I'll do some rigorous testing tomorrow night. I started this morning on the way to my work, but I experienced the ballpoint issue. Tonight I have to do some practicing with the band. So tomorrow night is dedicated to ectune serial WB testing with TE. And Friday I'm having a day of to do more testing.

Post by **calvin** » Wed Feb 04, 2009 8:11 pm

thanks.. btw the ectune rom version is the same as r7 so car driving different sounds strange. you don't even have to put a new rom to test this version.

Orthello · Post by **Orthello** » Thu Feb 05, 2009 6:02 pm

Well. Did a run tonight. But I'm not sure about the TE implementation. Results: First did a test with only the TE connected. Did some logging and checking with both the in car display and the TE logging software. Both were perfectly in sync and showing 14.2 AFR. Then I connected the ECU logging cable and started eCtune. Started the logging with serial WB set to TechEdge... AFR showing in eCtune was 11.0 AFR Then I switched to analog WB logging via D14 (normal O2 input) and AFR values were back to what I was used to... 14.2 AFR. Did another check on serial WB in eCtune.... still the same... 11.0 AFR Then serial with TE software.... 14.2 AFR But then.... battery of the laptop was empty

Tomorrow is another day. Should I do something else then only enable Serial Wideband Input for Tech-Edge?

David974 · Post by **David974** » Fri Feb 06, 2009 4:45 am

Update en TE started the car connect TEWBLOG, live connected shut off TEWBLOG start ectune connect HUGLOG in setting ask for TE on com9 click on connect said connected in green at the bottom of the screen but still no display click on disconnect had messag error \" can't acess to com 9\" perhaps my test version is wrong regards

RoadXY · Post by **RoadXY** » Fri Feb 06, 2009 8:01 am

What port is TEWBLOG using to connect to your WB?

David974 · Post by **David974** » Fri Feb 06, 2009 9:58 am

RoadXY wrote:What port is TEWBLOG using to connect to your WB?

the same port com 9 this port is always choosen when i plug the WB to the laptop

Post by **calvin** » Sat Feb 07, 2009 10:30 pm

post your wb trace file

Bindegal · Post by **Bindegal** » Sun Feb 08, 2009 4:48 am

TE still working here on my 3B and 3E units. 2D still not tested although IÂ´m pretty sure it will work. My older 2A has issues though, we are doing some logging to resolve this. /Allan

Post by **calvin** » Mon Feb 09, 2009 8:31 am

no body post the trace files?

David974 · Post by **David974** » Mon Feb 09, 2009 1:32 pm

we had a hurricane here sorry i didn't try again i'll, also how to get the trace file? regard

Orthello · Post by **Orthello** » Mon Feb 09, 2009 1:57 pm

calvin wrote:no body post the trace files?

view posts above.