GROUP BUY: USB CONSULT!

[ponzy]

Jamie i tried mine using free datascan it wont connect tried com port 1,2,4. Only 3 worked but it read "ecu id 0 active". is it maybe i need 2 buy the ful version or what? Thanks for any info.

[ponzy]

I have a 94' Q with TCS, DataScan software, and all of the functions work except the timing which reads improper scale, about 50.

i hope il be lucky as u are. Got to buy the ful version. Anyone willing to share theirs or is it prohibited? Thanks all

[qsiguy]

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.

[slipnfall]

Ponzy: email sent.

QSIguy: I would say the strength of the datalogging comes in the *viewer*, not the logger itself. Most if not all will just dump the data to a CSV file(comma seperated values). DataScan does not have a 'viewer' built in, so you have to open it in excel. In order to get a good graphical look at things you really have to much with Excel/charts/graphs. The same company offers a seperate viewer program, which is worth the extra couple bux.

BTW - unless the Q runs a wideband stock, the only thing the CONSULT will tell you is the AF base, oxygen level, and lean/rich. I strongly reccomend using a dedicated wideband for full tuning.

[goody90q45]

so what's up guys.............how do we deal with this? do we have to return the interface and have a refund or we'll have to wait and try to fix it?

Jaime- I'm sitting here on the outside with my Blazt cable and a registered version of NissanDataScan that I can't get to connect either (Invalid COM port) and a couple of things aren't adding up:

> Were your cable and driver made specifically for a Q45 and this group buy? If not, shouldn't we be able to plug into the neighbor's <95 Nissan 4 or 6 cylinder and get data? I tried on my neighbor's truck but couldn't find the plug. He's the only local I know driving an older Nissan. (Note: The Blatz cable lists numerous Nissan engines that it will work with but no 8 cylinder engines are on the list)

> At least one other member that I remember (RyanH) has had complete success with your cable using all the DataScan programs available, including a full version of NissanDataScan. I know there's a couple more in this growing (6 page) thread but didn't take the time to go back and look.

I think we're jumping the gun by talking about returning the cables. There's at least a couple of members that are up and running with your cable and the Blazt cable. We should all try first to make this work on another OBD1 Nissan engine and report back.

There's lots of potential business here if you can get your cable to work. Look at how busy Jeff Williams is making FSTB's.

What are your thoughts?

[slipnfall]

I think logic tells me that if this works on at least one[active/tcs 94-95] in this thread, it will work for all. From there it's either a matter of ECU problems(I have seen it plenty of times before) or computer proficiency ( no offense intended).

No, this board and group buy was not designed specefically for the Q45. Honestly I made it for my personal use on a '92 240sx, but seen that other people could really use them. I was told the Q45 shared the same CONSULT-I protocol, so I sold a few, and they reported back no problems. According to Robert, this design should work on the entire 'line' of Q45's, including 94-95.

Yep you should have no problem taking this and pluggin into any mid-90's nissan. In fact, you should see the list of cars overseas that this(my) cable works on: sunny's, GT-R's, too many to list. Heck I've had a guy buy one for his Quest minivan.

Anyways, I only threw the refund out there because I don't want people to think they are forced to wait for a resolution.

So yes: anyone having trouble connecting, try another car/ecu if it's in your capacity. This will at least confirm that the drivers and software are working OK.

Kindly.Jamie

[goody90q45]

So yes: anyone having trouble connecting, try another car/ecu if it's in your capacity. This will at least confirm that the drivers and software are working OK. Jamie

Thanks. That's what I wanted to hear. At least that will rule out computer improficiency on my part.

[slipnfall]

Really, as long as you install the drivers, it is listed in the control panel (with no yellow ! or red X), you're OK. From there you just need to be sure the port it's assigned to is setup the same in your software. Not much to it, but I think some folks are under the impression they can fire up the software and it just automatically connects.

[Ozzie]

I kinda wish I had jumped into this thread earlier.

I will try to sort some of the points that re-occur in this thread.

Now, my experience is with the PLMS cable, as the builders/programmers of the cables and Nissan DataScan live here, in Adelaide.. (Same city as myself)I believe most of this info will apply to the Nico OBD cable.

**NOTE: The interface worked flawlessly on my car. And I am running an IMPUL ECU, so a stock ECU is not necessary for the cable to work. My car is also an active, so that won't be the cause of any problems you guys might be having either**

Pete is a really cool guy too, and the list they have on their site of compatable vehicles contains a listing for the Q45 because of me

http://www.plmsdevelopments.com/consult_if.shtml

The problems with connecting via USB to serial ports are because the right chipset is required in the converter. (The PLMS cable is OBD 1 to D9 serial)

You may be able to get a converter to suit your connection needs that will work better, as long as it contains the FT232BM chipset in the connector.On the first page of this thread, someone posted a pic of the Belkin Part # F5U409-CU USB to serial adapter......



This has been known to work well.

A cable that has the compatable chipset, which is available in the US can be found here http://www.cooldrives.com/usb-....html

I wonder if all the problems are related to connecting directly via USB?Maybe the output from the ECU doesn't agree with it?

Regarding the DataScan software, quite a few opitons are restricted in the free version. I saw the full version being used on my car, and everything worked.The possibility of knocking out more than 1 cylinder at a time is possible too. (We disabled 4 cylinders, and it kept running!!!)

As the cable was bought direct from the builders/programmers of Nissan DataScan, I have a full version of the software. I can't find it on my system, so I have just emailed Pete about getting the zip file sent to me again.I MIGHT set it up to be shared, provided it gets put onto notebooks that don't connect to the net. (I don't want to risk losing the software backup and support from these guys)

The harware/software should work on more than one car, and not need to be specifically programmed for any particular model. (Here's the list from PLMS, same cable, no special modifications to suit different cars) * AUS 200SX S14 (SR20DET) * AUS 200SX S15 (SR20DET) * AUS Maxima A32 (VQ30DE) * AUS Pulsar N14 (GA16DE) * AUS Pulsar N14 (SR20DE) * AUS Pulsar N15 (GA16DE) * AUS Pintara U12 (KA24E) * AUS NX/NXR Coupe (SR20DE) * JDM 180SX S13 (SR20DET) * JDM Silvia S14 (SR20DE) * JDM Silvia S15 (SR20DET) * JDM Pulsar RNN14 GTiR (SR20DET) * JDM Pulsar GTi (SR18DE) * JDM Bluebird U14 (SR18DE) * JDM Bluebird U15 (SR20DET) * JDM Skyline R32 (RB20DET) * JDM Skyline R32 GTR (RB26DETT) * JDM Skyline R33 (RB25DET) * JDM Skyline R33 (RB20DE) * JDM Skyline R33 GTR (RB26DETT) * JDM Skyline R34 (RB25DET NEO) * JDM '94 Cefiro A32 (VQ30DE) * JDM Avenir PWN10 (SR20DE) * JDM Infinity Q45 (VH45DE) * CAN '92 Infiniti G20 (SR20DE) * US 300Z Z32 (VG30DETT) * US Sentra B13 SE-R(SR20DE) * US NX2000 (SR20DE) * US NX1600(GA16DE) * US '94 Sentra B13 (GA16DE) * US Maxima A32 (VQ30DE) * US '93 Altima (KA24DE) * US '92 Infiniti G20 * UK Almera N15 GTI (SR20DE) * UK 200SX S14a (SR20DET) * UK Micra K11 (CG13DE/CG10DE * UK 1993 Primera P10 (SR20DE) * FRA 200SX S14 (SR20DET) * FRA '93 100NX 2.0 GTI (=NX coupe) (SR20DE) * GER Almera NX (GA16DE) * GER 200SX (SR20DET) * GER '91 300ZX Z32 (VG30DETT) * FIN 99 Maxima A32 (VQ30DE) * EDM 96-99 Primera P11 (GA16DE & SR20DE)

These listed are known to work, because the customers have given feedback indicating so.

I know many people won't bother clicking the link to the PLMS site, so I am just going to cut/paste some relevant info.

We offer the DataScan software for $AU30 with the interface.

It includes the following features:

* Compatible with Win98SE, Win2K, XP and Vista. * Real time monitoring of RPM, speed, injector pulsewidth, injector duty cycle, TPS position, AFM voltage, speed, idle valve opening %, IGN timing, coolant temp, battery volts etc. All displayed on nice pseudo-analog gauges. * Data logging on all parameters with cool inbuilt replay feature. * Read and reset fault codes * Active tests like “power balance” (knocks one cyl out at a time), fuel pump on/off, VCT control, temporary changes to values for coolant temp, IGN timing, AAC valve (for idle adjustment) etc. * ROM read * More great stuff!

What laptops will the DataScan software work with?

Most of our testing has been carried out on a P233 machine with 32Mb of RAM running WIN98SE although this should be considered an absolute minimum. It also works with Win2K/WinXP/Vista on a more capable laptop.One user has reported that he's running it successfully on a P166 laptop (64Mb RAM) under Win95!

Using a consult interface and DataScan software allows you to download the maps from your ECU.

Please note that 8 boxes appeared for the power balance when my car was connected, not 6 as shown here. (Pete must have had it hooked up to his R31 skyline for this screen capture)

[slipnfall]

Thanks for chiming in Re: Datascan. I have a hard time believing however that the SiLabs chips causes problems: it always seems to boil down to the USB->RS232 adaptor brand itself. IMHO, if one company produced both variants, and the FTDI version worked, then the SiLabs would work equally well. I'm certainly open to a technical discussion, however I have not seen anyone bring forth factual data that supports this. The SiLabs runs on a 3.3V core vs 5V for the FTDI. Either way their amplified to 12V via transistor.

I also offer an RS232 version of the board that is certainly tried and true.

Please convey my compliments to Pete on a great piece of software.

[Ozzie]

From their site.... with customer testimonial....

"I'm a flash git with a new laptop - it only has USB, no serial port. What now?

Lots of people have used USB > Serial converters successfully. But some definitely work better than others. Cameron S has given us some valuable feedback on his USB converter experiences. Thanks Cam. Here are the details:I've been playing around with numerous USB to Serial adaptors and after trying quite a few non-compatible units, I stumbled on a 100% compatible item. I tried a few different brands, Belkin and a few no name Chinese jobbies, hoping they would do the trick. After installing the drivers and working out which comm port the adaptors were using, I'd start up Nissan Data Scan and things would work fine for about 10 seconds, followed by a BSOD each time! AARRRGGGHHHH!!

I tried a few different computers, thinking it could be the OS, but it wasn't. Turn's out that not all USB to Serial adaptors are built the same and the ones to go for are the ones that use a FTDI FT232BM chipset. A UK company by the name of Easy Sync (http://www.easysync.co.uk) makes a USB to Serial adaptor using this chipset and Dontronics (http://www.dontronics.com/usb_232.html) in Victoria is an Australian distributor. One of them set me back $60, but they work flawlessly.

Ironically, a couple of days after successfully testing the adaptor, Xtronics, makers of the ROMulator hardware, made an update to their web site listing this particular USB to Serial adaptor as the only one they know of that works with their hardware too. If only I had have known this earlier, it may have saved me some money. Oh well..."

[Ozzie]

I'm not saying that I know anything about electronics..... as I couldn't build the cables to save my life.But isn't it possible that the OBD interface is "fussy"?Maybe the FTDI is more stable for this application.

All I am doing is putting forward a suggestion.......

I know you like the SiLabs chipset, but maybe if you use the FTDI, you won't have any further problems?

Maybe if you have a go at building one cable with the FTDI chipset, and exchange it with one that someone else has already bought, one of the people who lives close to other Q owners, so it could be tested on a greater number of cars without the need for making a few to spread around and test out this theory (I'm thinking in the way of saving money to try out a new idea)

I think someone posted earlier that they tried it on their car, and 2 others? Maybe try it with them, see how it goes?

[Ozzie]

The other thing is, if the RS232 setup is more reliable for you, then maybe stick to building those, and direct the buyers to the known working RS232 > USB converters.

That way it's up to the purchaser if they need/require it. Otherwise (If the D9 socket is available on their laptop) they can just plug and play.

Here's the link again to a known working adapter available in the US.http://www.cooldrives.com/usb-....html$17.79.... not too bad

Only problem is they only ship to a US address..... I might need someone to order it for me, then forward it on once it's delivered to them!

[goody90q45]

"I'm a flash git with a new laptop - it only has USB, no serial port. What now?

Ozzie I'm still a bit confused. Do we need to start with a consult cable with a serial port connection and purchase this serial>USB adapter so we can plug into the newer laptops with USB connections only? All the cables we are trying to make work are consult>male USB (Blazt) and consult>female USB (Jaime's) so do we need to trade them in and just buy the adapter? Thanks.

[Ozzie]

I can't really comment, but if there is an adapter around that you could put inline, that uses the FTDI chip..... I am GUESSING that it may solve the problems people are experiencing.

I think Jamie is better equiped to answer that question......

I was more thinking along the lines of... the FTDI chip is a known working interface.Maybe using an FTDI chipset instead of the SiLabs may make the cables more reliable.

I REALLY don't have much knowledge on the subject of building circuit boards etc.I was just sharing information to try and solve the problems, you know, putting ideas out there.

[slipnfall]

Understood: I really have nothing against the FTDI chips... at the time they were just the underdog: hard to obtain, poor documentation, more expensive, and required more parts to work. I can't say for sure if I will release a version with the FTDI chip or not: it depends how the testing goes on the G50 ECU. I honestly do not think the SiLabs chips is the problem at all, electrically. More likely is the device drivers.

Anyways, you guys are all set with what you have here in the group buy. I'm having a board shipped to Robert to test on his ECU's and hopefully work identify the problem. I do not have the appropriate bench setup to test a Q45 ECU, he does. Hang tight.

Yes some ECU's/chassis wiring may be 'pickier' and less tollerant to signal variations. There is an inherent signal tollerance in any circuit board, and I may just be hinging on that allowable threshold(from the ECUs standpoint).

[ponzy]

jamie i was able to test the software and silabs interface again. it does work for a couple minutes and just suddenly wouldnt connect at all... is there any expiration on the time to use the "software" or it just shuts down caused by incompatibility. i am pretty sure im running a good computer, xp pro intel duo core 1.83 mhz, 1gb ram 120 gb hard drive memory. i did follow all necessary procedures on this thread... uninstall install, downloaded driver kit, com port on device manager under hardware on system control panel....etc....

i was able to pull code 51 injector circuit....

thanks, pls advice..........

[slipnfall]

Ponzy: no there is no time limit. When the situation arrises that you can't connect, try to reboot the PC. Windows may be turning off the port for power savings.

Jamie

[Q451990]

I received a very unexpected email today from Isaac, the programmer behind Nissan OBD ScanTech. He sent me a beta version of a revision that has a Power Balance test routine! I haven't tried it on the Q, but I was able to try it out on the truck and it's very promising! The software stabilizes the overall RPM rate, cuts one cylinder, and measures the difference - all while plotting it in a nice chart!

There are a couple of minor glitches, but I emailed Isaac about them and I suspect he can tweak the software a little. I will let everyone know more after I test it on the Q - but even in it's current state I think it's a winner!

Heath

[ponzy]

nice work heath, you guys the reason why i am still keeping my q (pls refer my sentiments from this thread --- zerothread/241652 -----)

i haven't bought any software yet but was able to use jamie's usb-consult and ulled some saddening ecu code. i'll try it again as per jamie's instructions to reboot again if it happended again.

thanks to all and keep us posted........

[ponzy]

We offer the DataScan software for $AU30 with the interface.

that's actually a 130 au$ if you buy the combo interface+datascan plus on shipping and handling charges.

[Ozzie]

Data scan by itself for $35

please read the whole site........

(Do I have to do everything?)

Prices & Ordering

$AU130 Consult Interface with DataScan software - fully tested. $AU100 Consult Interface only.

$AU35 DataScan Software only. $AU10 Regular postage within Australia.

$AU16 Postage (Air Mail) to most other countries.

$AU6 PayPal commission.

No postage required for a program

[Q451990]

Isaac has given me permission to share the beta file... Wes, can you host it on Q45.org?

I'm still checking with him to see when the full version will be available for purchase.

Heath

[slipnfall]

Heath: nice!! This was a very easy thing to do, and I often wondered why no one included it as a feature. +1 for ODB ScanTech then.

[Q451990]

Heath: nice!! This was a very easy thing to do, and I often wondered why no one included it as a feature. +1 for ODB ScanTech then.

No doubt! I'm still amazed that I asked about something, only to see it some to life a week or two later! These guys must really love writing this software, because there's no way they're making enough $$$ on the software to justify the time.

Heath

[Jberger]

FWIW, I've tried both the USB and Serial based cables from Blazt. I had NO LUCK with the USB based cable regardless of the machine or OS used. I tried laptops, desktops, servers, etc and they just would not work with the USB cable. The serial cable worked fine, but only with a keyspan USB adapter. I also tried Belkin, Compusa store brand and a trendnet (i think) that would not work reliably. The Keyspan adapter worked fine and continues to work today. So you might try a serial cable with adapter in place of the USB if you have issues.

Also, I'm late in following up on the questions for the power balence test. NDS can cut one cylinder at a time, but I'm not sure about forcing it to keep the other items consistent between tests. If anyone has ideas, just PM me and I'll try em.

[elwesso]

Isaac has given me permission to share the beta file... Wes, can you host it on Q45.org?

I'm still checking with him to see when the full version will be available for purchase.

Heath

Yeah hit me up and I'll get it taken care of .

[Q451990]

Yeah hit me up and I'll get it taken care of .

You've got mail.

[franknitty69]

i tried the blatz cable on a 95 q45 w/active & tcs and it didn't work with usb version or the serial version. the laptop(s) and software can't recognize the ecu.

i was supposed to validate the voltage and yada, yada, yada (that was like 6 mos ago) but the issues here obviously point to differences in this year with active and/or tcs.

i hope this is figured out or i would be out of 190 aus (:

[mxr662]

Jay: with the device installed, go into the control panel->System->Device manager. Find the two instances of the adaptor: under the PORTS, and USB devices. Right click and Uninstall. Uninstall both and remove the board promptly. It's important to keep the board removed untill the time comes, below.

Reboot.

Here is a link to the manufacture's drivers. There is a new version out, which may or may not fix some problems.

http://www.silabs.com/tgwWebAp...p.htm

You need the VCP 'Driver Kit'. Download the appropriate set for you OS and run the program. This will extract the files to C:\SiLabs\MCU, and then run an installer. This installer will install drivers to C:\Program Files\Silabs\MCU\CP210x\ by default.

Durring the new driver installation, it will scan your system and then tell you that it needs to remove the other drivers (DLabs drivers). Go ahead and tell it to remove them.

Reboot when it prompts you to.

After your PC has rebooted, shut down, plug in the CONSULT cable, and start back up. The cable should be recognized automatically, but will show up differently in the control panel->system->Device Manager now. If windows bishez about certified or signed drivers, just click ignore, or continue, whatever it may be. In case it prompts you for a file, point to either of the above new directories. It should work the same(hopefully better!) from there out.

Jamie

Last week finally got around to trying my cable and I'm having problems getting it to work. I did the above procedure on my old Pentium III-800 laptop with a clean install of Windows 2000. Driver install went smooth (followed your instructions exactly. Shows up as COM4 in Hardware Manager. Software set to COM4.

Clicking connect on Nissan Data Scan does nothing. Searching for ECU returns nothing. Deleted Nissan Data Scan registry key "HKEY_CURRENT_USER\Software\VB and VBA Program Settings\NDataScan" as suggested by Data Scan website. No Luck.

Tonight tried OBD Scan Tech Nissan. Was not able to connect to ECU but when I tried to connect to A/T it worked. The screen showed battery voltage that I was able to change by turning on the headlights. Also one of the values changed when I pushed on the accelerator.

Does this indicate the cable is working properly as it allows windows to connect to the TCU but not the ECU?

The previous owner did have to have the ECU replaced. Could a newer ECU cause this problem? The numbers on my ECU are A18-A32 PO2, 0207, and a large 05.

I used trial versions of both programs.

Andy
Modified by mxr662 at 9:50 PM 4/16/2007