Blazt Nissan Consult Usb Cable Software
Hi everyone, geez its been a long time since needing some help. Feels good sort of. I have a Nissan Consult unit that allows me to communicate with the car via a laptop/PC. It sends the data via a serial cable. Now this is where my issue is. I got with the Consult a USB to Serial adapter - Belkin brand.
For the life i can not get it to work with the PC. I have installed the driver disc for the converter to work, but yet nothing. On two separate Laptops BTW. I also tried directly plugging in the serial cable into a serial port on an older laptop i had. Still nothing.
The converter powers up as the power light flashes on, yet still can not get any data signal. The unit also has a TX and RX light at which in the beginning flashed but then nothing. These are the data stream signals i presume. The consult unit also works as it has a signal light too - that flashes when data is being sent. When plugged into the cars port. What do i have to do to get this to work.
The previous owner took the Consult unit into Harvey Normans and the tech agent there recommended the Belkin adapter and also installed it to work. Why cant i get it to work so simply?
Is it that the port is trying to receive the data at a faster bit rate compared to the cars output bit rate? As ive read this to be a problem on other forums (not particular to this issue with Consult though) If you have any ideas please advise as ive had this for about 6 months now and not been able to use it. Really wishing to have it work now. Check the settings on the installed software. Make sure the BAUD rate and other applicable settings are the same as the Consult Unit requires.It may be around the 9600 mark if uses the same system as the eftpos machine at work (rs232 - usb).
The Nissan DataScan I is intended for Nissan cars build between years 1989 and 2000. Majority of these cars are equipped with grey a 14 pin Consult I connecter. A list of cars that the software has been tested on is located on the NDSI Supported Vehicles page. Only poorly programmed software (which some of the older stuff may be) wont be able to handle the slightly higher response time of a quality usb/serial converter (i.e. FTDI) over a native serial port. All nissan consult software i know of works fine with a usb/serial port - since the native USB cables (i.e. Ecutalk, blazt, plms) are all.
Taiko no tatsujin ps2 iso torrent. 2nd point, these things are a nightmare to work with, sometimes you just dont get them to work until several reboots / several software maintenance repairs. TRY Unplugging the device, uninstalling drivers Turn off pc, plug in device, reboot, manually install drivers by scanning for added hardware and point to the driver disk. Reboot Install software needed for consult device (actually probably do this first) Reboot Look up configuration options, look for any repair or status options, try to make sure the device is detected and online here and in device manager.
You may have to reassign COM ports to be the same on both the software settings and the assigned device manager setting. Check the hardware all works first. Shut your software down and fire up HyperTerminal. Set a session up directly to COM x (whatever your Lappy has set the USB adapter for, could be anything between 1 and 8). Check under the Device Manager to see what random number WinDoze has chosen. Also set HyperTerminal for, 8, 1, No Parity, No Flow Control.
Then carefully bridge pins 2 and 3 on the DB9 serial port on the adapter, then type something/anything on the keyboard - what you type will come up on the screen. Remove said bridge then type some more, nothing should come up on the screen. If you can't get those end results then either there's something else running serial 'stuff' chugging away in the background (PLC programming software is notorious for this.), the software is unhappy with the USB adapter itself, the adapter is broken, you may have to disable any antiviral, etc on the Lappy, etc. Other traps to watch for with serial comms: a. Orientation of the serial port on the Consult unit actually, whether it's a DTE or DCE. If it's a DCE your serial cable 'should' be a straight one - pins 2-2, 3-3 etc. If it's a DTE then you'll need to cross the data pins as a minimum.
Check to see if your cable is only a 3-wire (2,3 and 5) and you actually need more pins than that; c. Check to see if the Consult also needs a 'Special' serial cable and not a standard straight/crossed one.
You dont want to be running USB->Serial adapters to program/play with your Cars ECU. The guys that tune them professionaly all use old school laptops to do this - I had to source a shitty laptop to do my Housemates Caprice - we put a Blower on the 5L and needed to re tune the Haltec ECU we put in it. This old Gateway lappy is a 400Mhz (beast!) had to re pack the battery, and it only runs Win98, but it does the job.