Jaguar 0.6-alpha Assembly Guide

[Fred]

Open the about box and find out!!! :-p :-)

[malcom2073]

Robert:

It's possible that your FTDI com port settings are messed up. try this (Thanks to DeuceEFI for the writeup, I've modified it to be a bit easier to follow.)

To change the COM port RX/TX buffer setting:

* Open the System Control Panel
* Find and open Device Manager
* Find COM and LPT Ports, and expand them
* Right click on the COM port, click on Properties
* Click on the Advanced button. (You may have to click on the "Port settings" tab first)
* Change the RX and TX buffer settings from 4096 (the defaults) to 64
* Click on Apply, then OK
It is recommended to restart the computer after making this change as sometimes Windows picks up the change instantly and sometimes it takes a reboot.

[E4ODnut]

Mike,
I got into the advanced settings for the com port but it appears to be different than what I expected.
There is a checked box "Use FIFO buffers requires 16550 compatible UART"
There is a slider for RCV and one for TCX buffers. RCV is 0-14set at 14. TX is 0-15 set at 15.

Also, com3, which is the one I am able to communicate with Jaguar on is tagged as being (in use)

Does that mean anything to you?

[malcom2073]

Mike,
I got into the advanced settings for the com port but it appears to be different than what I expected.
There is a checked box "Use FIFO buffers requires 16550 compatible UART"
There is a slider for RCV and one for TCX buffers. RCV is 0-14set at 14. TX is 0-15 set at 15.

Also, com3, which is the one I am able to communicate with Jaguar on is tagged as being (in use)

Does that mean anything to you?

It means you have the wrong driver installed. Likely when you were installing the BDM driver you selected the wrong thing in Zadig? Not sure. You could try "Roll back driver", see if that reverts it to the FTDI driver, or you may have to manually uninstall and reinstall the proper driver, which you can download from FTDI (I assume that's where you got the driver in the first place?)

[E4ODnut]

Mike,
I got the driver from the link Andy posted a few pages ago. It is for 32 bit, as he stated, but when queried in device manager it claims to be operating properly.

I tried uninstalling the driver and re-installing using Zadig but Windows appears to over-ride it and install a driver from wherever it does these things.

I can connect to Jaguar, but I still get error messages.

Any suggestions?

[E4ODnut]

Andy,
P4, BRV-12v. What should it connect to?

[DeuceEFI]

BRV-12v should be connected to your battery positive terminal through a relay that is energized when your key switch is in the "On" position. This is a switched 12v input.

[Fred]

Just to be clear, BRV should be a clean pure battery voltage unloaded by anything else. Ideally a separate wire to the power feed to the ECU for separate filtration. In your OEM setup, use whatever makes the most sense.

[E4ODnut]

Thanks.

Can you confirm my following pin outs?

Inlet Air Temperature sensor output to Jaguar IAT pad P6
Coolant temperature sensor output to Jaguar CHT pad P8
Throttle Position Sensor output to Jaguar TPS pad P10
O2 sensor output to Jaguar O2 pad P12
TFI Profile Ignition Pickup output to RPM0 in + pad P14
Profile Ignition Pickup ground to RPM0 in - pad P15
General purpose ground to Jaguar Gnd pad P3
Analog 5 volt power supply to Jaguar 5v pad P65
Analog signal return ground to Jaguar 5v gnd pad P65
12 volt switched power to Jaguar 12v-sw pad P1
General purpose ground to Jaguar Gnd-2 pad P5
TFI SParkOUTput input to Jaguar Ignitor 1 pad P85
Injector Bank 1 to Jaguar INJ 6 pad P77
Injector ground to Jaguar INJ 6 gnd pad P54
Injector Bank 2 to Jaguar INJ 7 pad P78
Injector ground to Jaguar INJ 7 gnd P53
Fuel pump relay to Jaguar Fuel pad P25

Jumper pins P20-3 to P34-5 to P34-6 (connects to CPU and parallels INJ5 and INJ6 FETs)
Jumper pins P20-4 to P34-7 to P34-8 (connects to CPU and parallels INJ7 and INJ8 FETs)

[malcom2073]

Mike,
I got the driver from the link Andy posted a few pages ago. It is for 32 bit, as he stated, but when queried in device manager it claims to be operating properly.

I tried uninstalling the driver and re-installing using Zadig but Windows appears to over-ride it and install a driver from wherever it does these things.

I can connect to Jaguar, but I still get error messages.

Any suggestions?

Andy linked a driver for the USBDM, not for the FTDI, you need the 64bit driver for windows from here: http://www.ftdichip.com/Drivers/VCP.htm

When you say it claims to be operating properly, it says the mfg is "FTDI"? Or does it say something like "libusbk"?