Blazt Consult Cable Is Working

[goody90q45]

I don't want to jack the Consult cable group buy thread that Wes put together with Jamie (slipnfall) but I do want to report that the consult cable and software I purchased from one of our sponsors, Blazt, is up and running.

I bought the cable and software from Blazt before Christmas and before the group buy was put together. Like most everyone else in the group buy I had the issue with invalid com port and that's about as far as I could get. With the help of Andy (mrx662) we were able to determine that the problem was cable related and not a hardware or installation issue.

Jason Dear from Blazt was very helpful from the beginning and after the last test with Andy suggested that I swap for a Blazt cable with a FTDI chipset rather than the CP2102 chipset used on his cable and Jamie's cable.

I plugged in the new cable and NissanDataScan worked great. I was also able to use ECUtalk and will probably be able to connect to the ECU using any of the free Consult software available on the net.

Jason Dear from Blazt has been very helpful through this hit and miss process and I would highly recommend his product. The Blazt consult cable, driver, a registered version of NissanDataScan, and unlimited prompt advice can be had for $130. It's worth that much just to never again have to remove the ECU to read codes.
Modified by goody94q45 at 4:07 AM 5/2/2007

[3Q Jay]

hey Mike--good news!I'm hopeful we will still find a fix between Robert and Jaime.

so, Blazt has 2 different USB cables then?

[qsiguy]

Jamies cable works fine for me with all of the software I've tried and with the '90-93 ECU as well as my '94. Didn't give me any grief except for when I first added the cable all my com ports up to 10 were used so it assigned 11 which isn't a choice on datascan. I manually changed it to 9 and it logged in without issue on both of my ECU's.

[Ozzie]

With the help of Andy (mrx662) we were able to determine that the problem was cable related and not a hardware or installation issue.

Jason Dear from Blazt was very helpful from the beginning and after the last test with Andy suggested that I swap for a Blazt cable with a FTDI chipset rather than the CP2102 chipset used on his cable and Jamie's cable.

Exactly what I said in the other thread.... looks like i was right

Congrats on the working cable, now you can have fun playing with the software

[goody90q45]

Exactly what I said in the other thread.... looks like i was right

You da man. You hit it on the button a few weeks ago when you suggested that we would have better success with the FTDI chipset instead of the CP2102 chipset. I don't have a clue what all this means (PC challenged) but the new cable works great.

Now I've got to run my cable and laptop over to Jared's house (silver2k2) to verify that it works on the active ECU as well.

[Ozzie]

It should..... had a cable working on my car before.

hey Mike--good news!I'm hopeful we will still find a fix between Robert and Jaime.

Tell them to change over to the FTDI chipset, and it will work......

[goody90q45]

.........Tell them to change over to the FTDI chipset, and it will work......

You're right Ozmeister. I messed with my cable for 5 months off and on and never got past "invalid com port". With the new cable and driver it connects to the ECU instantly and all the consult freeware is connecting and working also.

[Ozzie]

You're right Ozmeister. I messed with my cable for 5 months off and on and never got past "invalid com port". With the new cable and driver it connects to the ECU instantly and all the consult freeware is connecting and working also.

Now convince everyone else that I got something right (for once).....All these Nico cables could be fixed if the chip is replaced for the FTDI chip.....I know it will work.

[NewKleer]

or just get a serial interface with FTDI chippest usb/serial adaptor...not the most elegant solution though, but it does give u the advantage of being able to use the serial port with things that have serial ports (eg pocket pc's!)

now FTDI have the FT232R series all-in-one chip, there shouldnt be any reason for anyone to keep using the cp210x crap! the 28 pin ssop is also much easier to hand solder (if you go that way)

[Ozzie]

or just get a serial interface with FTDI chippest usb/serial adaptor...not the most elegant solution though, but it does give u the advantage of being able to use the serial port with things that have serial ports (eg pocket pc's!)

now FTDI have the FT232R series all-in-one chip, there shouldnt be any reason for anyone to keep using the cp210x crap! the 28 pin ssop is also much easier to hand solder (if you go that way)

Yeah, I mentioned using an interface that uses the FTDI chip in the other thread, and even linked to details of ones that would work.....zer...age=6

about halfway down the page......

[Nebusoku]

I have been using the blazt serial cable with a serial to USB adapter on my 94 Q since around October 06 never had a problem with it.

[NewKleer]

btw thats not to say cp210x is the cause of the problems - its highly unlikely it is, just they dont have as good driver support as FTDI (eg no drivers for windows ce, and numerous people have issues with drivers in windows). i shouldnt have said they're "crap" - ftdi have had no competing chip until they released the ft232r, but given the better driver support and flexibilty in chips (ie hand solderable), and being slightly cheaper last i checked, the ft232r should be the obvious choice for new projects. i believe blazt are looking into changing over to ftdi chip for their usb ones.