GROUP BUY: USB CONSULT!

[qsiguy]

Yes, I just forced it to use com9 instead of 11. Windows gave me a warning but I forced it through and it worked. Not sure if something else will now not work but it was probably just something I installed a long time ago that wasnt used anymore.

[3Q Jay]

ECU Talk also connected to my '94 ECU. I was able to reset my knock trouble code and read all the gauges. Here's a screenshot. My O2 gauges are all over the place. I need to get this car figured out. Knock code popped back on shortly again.

1994 Q45 stock ECU

your O2's should be all over the map. more precisely, they should alternate between 0 and full scale every few seconds at hot idle, and a few times every second at 1500-2200 rpm. the faster they switch, the 'fresher' they are. you are the only one to succeed on a 94 ECU that i know of. er, maybe Ryan H did too.

is the ECU talk screen shot at 'idle'? looks like your aac valve is open too far. try for '20' at hot idle in gear under ecu control (i.e plugged in). the ecu target should be ~650 rpm in gear, some later ones are 600. Dennis may tell you 15% aac duty cycle, and i wouldn't argue, i've just found that the ECU talk seems to loose resolution on that below '20'.

[qsiguy]

I may have rev'ed it a bit, was late and I was just messing around. I just went out and did this run and saved it so Tech could check it for me. 2K rpm/60 mph (at least thats what my speedo said). Still trying to work out my emission failure issue.

I did reset my knock code and it came back shortly.

[qsiguy]

What's up with the Ignition timing? Is it messed up on everyone's? Mine is up around 50 on ECU Talk and on Nissan Data Scan

Also, Does Nissan Data Scan have the MPG reading? I couldn't find it but would be surprised if it didn't. It's got so many other cool features like the performance computer. 0-60, 40-120, etc. By the way my 0-60 time is crap right now. It was over 9 seconds, close to 10

[ponzy]

jamie.i did tried it again like 4th time today and it's still not connecting?..did the restart thing..uninstall the software and install.. same thing no conncetion or whatsoever.

no invalid port messasge..it's just not connecting .. there's no blue signals going on...do you think it's the software or the cable just seized up..thanks a lot .......

1994 q45 with tcs

[mxr662]

What's up with the Ignition timing? Is it messed up on everyone's? Mine is up around 50 on ECU Talk and on Nissan Data Scan

Mine looked messed up also:

[qsiguy]

Does anyone else have the full version of Nissan Data Scan that's got their cable working? I have an issue with one of the gauges and was curious if any of you have the same issue.

The A/F Base RH gauge shows a scale of 50-0 and always stays on 0 (which is all the way clockwise) All three of the other A/F Base gauges have a scale of 50-150 and float around 100 all the time. I think there is a glitch in the software but would like to know if anyone else has seen this issue.

[ScanTech]

Hi guys,

I am Isaac, the developer of OBD Scan Tech Nissan. I need few guys out there to test my software. I will take few who are willing to give feedbacks and report any glitches within the software. Currently, I am working on Power Balance Test and Voice Recognition. I am always open to any suggestions or feature request. If you want to participate, email me at [email protected] (without periods).

Thanks

-Isaac

[qsiguy]

Hi guys,

I am Isaac, the developer of OBD Scan Tech Nissan. I need few guys out there to test my software. I will take few who are willing to give feedbacks and report any glitches within the software. Currently, I am working on Power Balance Test and Voice Recognition. I am always open to any suggestions or feature request. If you want to participate, email me at [email protected] (without periods).

Thanks

-Isaac

E-Mail sent Isaac, count me in.

[Q451990]

I have been working with Isaac for about a month now on the Power Balance test... I think we're almost to getting some meaningful results from it with this revision, so I would absolutely jump in now!

Heath

[mxr662]

Hi guys,

I am Isaac, the developer of OBD Scan Tech Nissan. I need few guys out there to test my software. I will take few who are willing to give feedbacks and report any glitches within the software. Currently, I am working on Power Balance Test and Voice Recognition. I am always open to any suggestions or feature request. If you want to participate, email me at [email protected] (without periods).

Thanks

-Isaac

Email sent.

Andy

[3Q Jay]

i'm in!

e-mail sent.....

[NewKleer]

It's a matter of personal preference as I've used the SiLabs for many years. I've used thrm in plenty of final designs and never had an issue. The FTDI chips available at the time required more external components, ie crystal, caps, etc. PCB layout is better with the SiLabs, which is important for small board design.

yeh i guess if you're familiar with it makes things easier....and FTDI did take a long time to get the all in one FT232R chips out (think i used 1 cap and 2 resistors only for a usb/serial adaptor i made). worth a look at in the future, though

the blazt usb cables used the cp210x, so i dont think there is any inherent technical issue with them (as some people have suggested), though driver issues and other things might be a bit over the head of the average car owner.

only think i can suggest is the 12v/6k8 combo for pullup to your comparator. what voltage is comparator set up for? ive found with a 5v/10k setup, this will typically get around the 1.0v mark for low signals, thats 0.5mA collector current. 12v/6k8 is trying to push 1.75mA collector current, and more when the car is on...at a guess thats going to generate around abouts 40% of 12v as the low voltage.

so im not sure if i understand this ecu EE/EF issue - is the problem that the actual ECU is not on EF for some cars? or did people just assume EE was the ecu, but its actually something else? keep in mind the later model cars, with the consult/OBDII dual setup, not all of them have the consult plug there for the ECU (only for legacy control units, where the ECU would now be consult II). this is especially the case for any new models that came out after consult II (1999).

As for the idle timing response that's a glitch in the datascan software - 50 (0x64 hex) is the default (0 added) timing. The stock ECU has tip-in retard that the JDM and my ECU does not have. The consult interface routines in the ECU software aren't smart enough to figure it out so they report a bogus number. I suppose I could fix it but I've never bothered. Some stock ECUs do the same thing.

can you explain this more? all the consult software out there works fine for jap cars - what do the US cars do differently and how can this be handled in consult software? if we have a simple offset, would this fix it (ie offset by -50+static ign timing?)

Which software is the best for logging? I want to be able to get a graph of my fuel ratio during a dyno or street run. I know a wide band system will be best but I want to be able to get started using the consult and software prior to that investment.

ecutalk v1.3.2 (or later) hands down...logs the full 50 packets/second (about 3 times rate that datascan does). to get maximum data, turn up the minimum gauge refresh time to something high (though on a reasonably specced laptop this wouldnt be needed)

Quote »Trouble I'm having is that it assigned COM11 and if I try and change it the computer says COM3-COM10 are in use but I don't know what for[/quote]as you found out, just force it...whenever a service device is registered, it takes a port for now and forever...even if the device is gone. so if u know nothing is using it, then forcing it will be fine

Quote »Also, Does Nissan Data Scan have the MPG reading?[/quote]i just added that to ecutalk recently (since i put L/100KM on my consult lcd display, i thought i may as well put it in the software). no one else has added it yet, not too hard, though user needs to input num cylinders/injector cc size to get reasonably accurate reading.

Quote »The A/F Base RH gauge shows a scale of 50-0 and always stays on 0 (which is all the way clockwise) All three of the other A/F Base gauges have a scale of 50-150 and float around 100 all the time. I think there is a glitch in the software but would like to know if anyone else has seen this issue.[/quote]i think u mixed things up. timing is 0-50, not A/F Base. and its showing max 50 due to different way timing is reported in the weird US cars (see up more in the post)

-----

dam thats lots of words...forgot about this thread!

[Q45tech]

The consult 1/11/111 assumes that the -15 degree offset [manually set by CAS with a timing light] is always correct so at idle zero addition from ecu it displays 15. Even if you misset CAS Consult still shows 15 [the correction offset].

So your 0x64hex 50=zero addition should just report as 15 to be same as US Consult.

Some of the injector numbers look strange compared to US Consult?

Hot idle is 1.2 millisecs and cruise is 1.8-2.2. PeakWOT is ~~11msec at 4,000 rpm and declines to maybe 9.5-10 msec at redline.

[NewKleer]

whose injector numbers do u mean? bit hard to compare unless you have same mods/throttle/boost/etc (and for that reason makes it a bit meaningless to compare given car to car variations).

[qsiguy]

.....i think u mixed things up. timing is 0-50, not A/F Base. and its showing max 50 due to different way timing is reported in the weird US cars (see up more in the post)

So from the sound of it you are the programmer for ECUTalk? If so, excellent work! It's the one I've used the most so far and used it for the most logging. I didn't mix up the gauges. I'll post a screen shot below. ECUTalk is fine but Nissan Data Scan has it wrong, at least for me. It is 50-0 not 0-50 and the other A/F Base gauges are 50-150 on NDS. The guages are fine on ECUTalk. I had timing off during this screenshot as it is useless as it is. FYI, the timing numbers are off on all of the software I've tried on my car. It's not isolated to some programs.



Can you tell us more about the in car display you are working on? From the web site it appears that it's not available yet. Will it be sold any time soon and will there be diagrams available for those of us with the ability to make our own?

[NewKleer]

So from the sound of it you are the programmer for ECUTalk?

ECUTalk is fine but Nissan Data Scan has it wrong, at least for me.

FYI, the timing numbers are off on all of the software I've tried on my car. It's not isolated to some programs.

Can you tell us more about the in car display you are working on? From the web site it appears that it's not available yet. Will it be sold any time soon and will there be diagrams available for those of us with the ability to make our own?

thats right, all the ecutalk stuff is done by me. weird thing with NDS - maybe its a bug that got thru cause whoever tests it doesnt have a dual bank car setup.

looks like u just subtract 35 from all your timing numbers...ill eventually stick in the ability to change the offset/multipliers. actually i remember someone awhile ago mentioning the KA have the offset timing issue also.

most of the info about the display is on the website. at the moment it has the sensor display, read/clear fault codes, run time trials. also has a serial consult interface integrated to it (so it can act just like a normal consult cable, hook it up to your laptop and run consult programs like you are now). ive made and sold a batch of 50 late last year to people in aus (a few overseas). im busy with uni till start of july, but then ill be getting back to it and should have next lot available a couple months from then.

considering changing the format of the display from 40x2 to 20x4 (ie making it "squarer" and not as long, but still not too high, so u can fit it in a DIN space or similar. current display is 188x39mm, too wide for DIN, but can probably make it around 125x45mm, with buttons on front rather than top.

trying to get a few key things done with it, particularly make the firmware upgradable (ie download it from the site and update display with a pc) which would be pretty awesome in terms of being able to add more things to it as we go (eg active tests will probably end up in there eventually). also allow user to control backlight/contrast of LCD, and potentially set it up so that it can log to a sd card or similar (and then download logs to pc). lots of possibilities!

so hopefully have them for sale around september, price might be either side of $180 (at current exchange rates). also if you had the ability to make one, then you wouldnt need diagrams! (ie its not a simple dumb circuit like a consult interface) its a standalone unit, doesnt need a pc, just plug and play into consult port.

[qsiguy]

Until you have the offset in place for the timing we could just put a simple formula in our Excel log files to change the value.

Is there a time trial feature in the software? I've heard it mentioned on your site and you said your display has that in it but I couldn't find it in the software when I was in my car.

Last, I've read some other requests on your site about more mileage calculators and I would like that as well. Maybe some resettable averages?

[NewKleer]

no time trial in there atm, though you can do that with logs also. time trials are in the display as a test of measuring distance (as much as performing the time trial itself) which leads the way for trip meter functions (which would make their way into ecutalk software also).

so in addition to current MPG or L/100KM, i imagine things like distance, average speed, fuel used, average fuel economy can go in there. cant wait till uni is over in july, cause there's lots to do!

[ponzy]

jamie, you got mail.........

[gammer_ghn]

Soooo does this work with he 1999 Q45 or nah and it just plugs in right???

[goody90q45]

I sent Robert a '94 TCS unit to play with and see if there's a fix.

So ya know.....Plugged in my Blazt cable tonight into my newly acquired 94Q45t parts car and with the engine running NissanDataScan (NDS) could not find or connect to the ECU. Plugged in to my base 94Q45 and NDS found the ECU and connected instantly.

[Q451990]

Soooo does this work with he 1999 Q45 or nah and it just plugs in right???

I don't believe so... it's designed to work with OBD I Nissans with the grey Consult connector. For a few years, Nissan put both the OBD II connector, and the grey Consult connector on the cars. I would suspect they stopped doing that before 1999. Might not hurt to look.

You can probably use this adaptor if you have a connector that looks like this:



but not if the connector looks like this (yours may be a different color):

[3Q Jay]

So ya know.....Plugged in my Blazt cable tonight into my newly acquired 94Q45t parts car and with the engine running NissanDataScan (NDS) could not find or connect to the ECU. Plugged in to my base 94Q45 and NDS found the ECU and connected instantly.

parts car=TCSGoody mobile= no TCS.....

[qsiguy]

My cable works on my TCS '94 car with my '94 stock ECU or my '93 NICO ECU both with TCS feature. Using Jamies Consult cable. So far I've used NDS and ECUTalk, still working on getting Scan Tech working but that's not a cable issue.

FYI

[gammer_ghn]

thankz man i will check = ]

[ponzy]

My cable works on my TCS '94 car with my '94 stock ECU or my '93 NICO ECU both with TCS feature. Using Jamies Consult cable. So far I've used NDS and ECUTalk, still working on getting Scan Tech working but that's not a cable issue.

FYI

Shane, i have a 94 with TCS ecu, and jamie's cable wont work. It worked one timd with NDS v1.3 and pulled off some codes, but after that, it just wont connect at all even with isaac's scan tech. I dont know if its cable or drivers issue i dont have an idea.

So ya know.....Plugged in my Blazt cable tonight into my newly acquired 94Q45t parts car and with the engine running NissanDataScan (NDS) could not find or connect to the ECU. Plugged in to my base 94Q45 and NDS found the ECU and connected instantly.

newkleer said jamie's and blazt-usb cable use the same chip cp210x

the blazt usb cables used the cp210x, so i dont think there is any inherent technical issue with them (as some people have suggested), though driver issues and other things might be a bit over the head of the average car owner.

What could be the missing link? Is it the interface or driver's? Or the ECU?

[NewKleer]

What could be the missing link? Is it the interface or driver's? Or the ECU?

interface or ecu, or combination thereof. if you look at this post: zer...20186

then it may depend on what voltage the comparator is set up for on the TX line.

anyone with this issue, who has a multimeter or if possible, an oscilloscope, could probably check the voltages of the lines (use this to tell you which pin is which), notably:

RX: when your laptop is transmitting trying to connect, voltage here should be between 0v and 12v (but not stuck at either) briefly then return to 0/12v, forget which

TX: the most important one...if this value moves at all from 5V while program is trying to connect, then the ECU is responding, therefore the only issue lies with the interface

the solution would be to increase the resistance of the resistor between ecu TX and VCC/5V, or change the biasing resistors to lower the comparison voltage...easiest change is finding a resistor that u can lower value of, rather than increase (as you can double up resistor to lower value, so no need to remove original). jamie would have to work out what to do here, as im not sure how his circuit is done

[goody90q45]

newkleer said jamie's and blazt-usb cable use the same chip cp210x...What could be the missing link? Is it the interface or driver's? Or the ECU?

Yes and no. Blazt does use the same chipset as Jaime's cable (CP210x). It would not connect to my base ECU so Jason at Blazt sent me the latest version of the consult cable which has the MTDI chipset and connected fine. Still can't get is to read the TCS ECU.

[NewKleer]

Yes and no. Blazt does use the same chipset as Jaime's cable (CP210x). It would not connect to my base ECU so Jason at Blazt sent me the latest version of the consult cable which has the MTDI chipset and connected fine. Still can't get is to read the TCS ECU.

well thats interesting...that can still mean its either the circuit or the cp210x thats causing the problems (ie blazt might have changed their circuit as well as their chip in the newer FTDI ones).

u have one of the ECU's that people are saying dont work right? (93/94 with TCS or whatever it is...i dont know what that means)