Vipec

Adam37tr
Posts: 98
Joined: Sun Oct 05, 2008 2:39 pm

Postby Adam37tr » Wed Sep 01, 2010 5:42 pm

Anymore pointers

Just trying to find time to get in to R-T notts

Cheers Adam

marcelb
Posts: 7
Joined: Wed Mar 03, 2010 10:56 pm

Postby marcelb » Fri Sep 03, 2010 10:07 pm

I have been waiting a long time for this , Can anyone tell me exactly what are the channels available to the DASH2 when it is connected to the V88 directly without the logger ?

Adam37tr
Posts: 98
Joined: Sun Oct 05, 2008 2:39 pm

Postby Adam37tr » Sat Sep 04, 2010 2:11 pm

Well spent most of today trying all diff things

Nothing

As said gps/rpm/ext sensors etc work but no ecu data

No idea at all now

Adam37tr
Posts: 98
Joined: Sun Oct 05, 2008 2:39 pm

Postby Adam37tr » Sat Sep 11, 2010 7:13 am

All sorted guys

All it was is there is another output on the board for the rs232 output
just a matter of swapping from the existing can to that

Works a treat :D

Cheers Adam

WillM
Posts: 84
Joined: Wed Dec 27, 2006 11:00 pm

Postby WillM » Sat Sep 11, 2010 3:51 pm

Hi Adam,

Glad to hear it is working!!

Do you mean that you previously had the serial cable connected to the Vi-PEC's USB port, and now you are connecting to the Vi-PEC's CAN/Serial port, successfully?

Just want to be clear in order to help others who may be searching this topic in the future. Using the CAN port, and not the USB port, was item #12 on my procedure above.

Cheers,

Will

Adam37tr
Posts: 98
Joined: Sun Oct 05, 2008 2:39 pm

Postby Adam37tr » Fri Sep 17, 2010 8:38 pm

WillM wrote:Hi Adam,

Glad to hear it is working!!

Do you mean that you previously had the serial cable connected to the Vi-PEC's USB port, and now you are connecting to the Vi-PEC's CAN/Serial port, successfully?

Just want to be clear in order to help others who may be searching this topic in the future. Using the CAN port, and not the USB port, was item #12 on my procedure above.

Cheers,

Will


Well yes and no

Basically the plug and play ecu I have only has one CAN plug, but when taken out of the ecu case(which I did not fit my tuner/mapper did) the CAN plug can be removed and plugged into the rs232 port on the circuit board itself.

So next move is to hopefully buy a CAN plug that plugs onto the board so havent got to remove ecu everytime want to map car :roll:

Why it does not come as the v44/88 with 2 plugs I will never no, as surely the part is around £10

Anyway sorted thanks all for input

Cheers Adam :D

Adam37tr
Posts: 98
Joined: Sun Oct 05, 2008 2:39 pm

Postby Adam37tr » Sun Sep 26, 2010 7:38 am

Well after setting up new ecu all seems well

Except IAT (inlet air temps) dont get anything at all

Any ideas?

Cheers Adam

WillM
Posts: 84
Joined: Wed Dec 27, 2006 11:00 pm

Postby WillM » Mon Sep 27, 2010 12:39 pm

Hi Adam,

Glad to hear it all worked out, and thanks for the update concerning the plug-and-play Vi-PEC's having an internal CAN/Serial header. That bit of info could save someone a lot of headache.

Which RT Serial channel are you using for AIT?

My Air Inlet Temp from the ECU maps to the RT serial channel named "Exhaust 2 temp [C]".

Works correctly on my setup.

Adam37tr
Posts: 98
Joined: Sun Oct 05, 2008 2:39 pm

Postby Adam37tr » Mon Sep 27, 2010 4:26 pm

Thats strange , you would think it would be post turbo or intercooler for inlet temps?

Will give it a try though mate

Thanks Adam

WillM
Posts: 84
Joined: Wed Dec 27, 2006 11:00 pm

Postby WillM » Tue Sep 28, 2010 4:15 pm

Adam,

My AIT's come in under Exhaust 2 temp, your Air Inlet Temp may use a different RT Serial Variable It depends on how your inputs are setup on your Vi-PEC ECU.

It appears that there are several variables with duplicate data too. For example, my AIT's are mapped to "Exhaust 2 temp", but are also recorded under the RT variable "Ambient air [c]".

This is how the Vi-PEC inputs are mapped to RT's Serial Variables:

Code: Select all


Vi-PEC Channel -> is mapped to RT Serial Variable

AN Temp 1  -----> Exhaust 1 temp [c]
AN Temp 2  -----> Exhaust 2 temp [c]
AN Temp 3  -----> Exhaust 3 temp [c]
AN Temp 4  -----> Exhaust 4 temp [c]

AN Volt 1  -----> Fuel Inj 1 cut [%]
AN Volt 2  -----> Fuel Inj 2 cut [%]
AN Volt 3  -----> Fuel Inj 3 cut [%]
AN Volt 4  -----> Fuel Inj 4 cut [%]
AN Volt 5  -----> Fuel Inj 5 cut [%]
AN Volt 6  -----> Fuel Inj 6 cut [%]
AN Volt 7  -----> Fuel Inj 7 cut [%]
AN Volt 8  -----> Fuel Inj 8 cut [%]
AN Volt 9  -----> Auxiliary 1
AN Volt 10 -----> Auxiliary 2
AN Volt 11 -----> Auxiliary 3


I do not know if your plug-and-play Vi-PEC has the exact same AN Temp and AN Volt inputs, but these are the ones mapped by RT.

Keep in mind that the Vi-PEC is fully customizable/configurable. You will have to know how your AN Temp and AN Volt inputs are assigned (very easy to find under "ECU Settings" within the VTS software).

It is possible that your AIT is any of the 4 Exhaust temp variables, as it all depends on how your channels are configured in VTS.

MY AIT's come over to RT's Serial Variable called "Exhaust temp 2".

Here is how my Vi-PEC channels are used. There are 4 columns:
- Vi-PEC Channel
- My current Vi-PEC configuration (yours may vary)
- The RT variable mapped to the Vi-PEC Channel
- Notes about my configuration

I can change the Vi-PEC configuration any way I want, but I can never change the mapping relationship between the Vi-PEC channel and the RT Serial Variable, as it is hard-coded into the ECU interface.

My current configuration:

Code: Select all

Vi-PEC Channel -> is setup in Vi-PEC as --> is mapped to RT Serial Variable --> My RT config notes: 

AN Temp 1  -----> Engine Coolant Temp ----> Exhaust 1 temp [c] ---------------> convert variable from °C to °F
AN Temp 2  -----> Inlet Air Temp ---------> Exhaust 2 temp [c] ---------------> convert variable from °C to °F
AN Temp 3  -----> OFF --------------------> Exhaust 3 temp [c]
AN Temp 4  -----> OFF --------------------> Exhaust 4 temp [c]

AN Volt 1  -----> MAP Sensor -------------> Fuel Inj 1 cut [%]
AN Volt 2  -----> WideBand ---------------> Fuel Inj 2 cut [%] ---------------> Use LC-1 default 7.35-22.39
AN Volt 3  -----> TPS (Main) -------------> Fuel Inj 3 cut [%]
AN Volt 4  -----> OFF --------------------> Fuel Inj 4 cut [%]
AN Volt 5  -----> OFF --------------------> Fuel Inj 5 cut [%]
AN Volt 6  -----> EGT (0-5V) -------------> Fuel Inj 6 cut [%] ---------------> EGT cly 1
AN Volt 7  -----> EGT (0-5V) -------------> Fuel Inj 7 cut [%] ---------------> EGT cly 2
AN Volt 8  -----> EGT (0-5V) -------------> Fuel Inj 8 cut [%] ---------------> EGT cly 3
AN Volt 9  -----> EGT (0-5V) -------------> Auxiliary 1 ----------------------> EGT cly 4
AN Volt 10 -----> Oil Pressure -----------> Auxiliary 2
AN Volt 11 -----> Fuel Pressure ----------> Auxiliary 3

Adam37tr
Posts: 98
Joined: Sun Oct 05, 2008 2:39 pm

Postby Adam37tr » Tue Sep 28, 2010 5:54 pm

Thanks for reply Will

I have looked at my inputs through the values table in analysis
my exhaust values copy water temp and ambient temp, dont seem to see any inlet temps at all? The inlet temps values show no volts at all

Will have another try over weekend

Be something daft

Cheers Adam

Adam37tr
Posts: 98
Joined: Sun Oct 05, 2008 2:39 pm

Postby Adam37tr » Wed Oct 06, 2010 4:57 pm

Is it possible to get IAT inlet temps to work?

Dont seem to work at all

Cheers Adam

Adam37tr
Posts: 98
Joined: Sun Oct 05, 2008 2:39 pm

Postby Adam37tr » Sun Oct 24, 2010 5:15 pm

Still no IAT inlet temps :roll: :cry: :cry:

Support

Postby Support » Wed Oct 27, 2010 4:59 pm

Hi Adam,

If you log some data on the DL1 with the engine running I could check the file if you like? Please email any files to andrew@race-...com .

Kind regards,

Andy

Support

Postby Support » Thu Oct 28, 2010 9:39 am

Hi Adam,

Thanks for the data, I checked it over and the IAT is there as expected:

Image

Is it possible you are looking on the incorrect channel?

Kind regards,

Andy[/img]


Return to “General support questions”

Who is online

Users browsing this forum: No registered users and 27 guests