MarcelB Posted February 11, 2014 Report Share Posted February 11, 2014 Hi all , I think I should post up some of my recent experiences with the Racepak dash and my V88 .Previous to the last firmware upgrade , the laptop/VTS would be bumped off by the dash when it is powered up causing me to have to run a separate kill switch for the dash, no biggie. Now, since the last upgrade I've noticed that the laptop/VTS would do the bumping causing all the sensor values on the dash to go to zero which I thought nice allowing hassle free operation but!........Since this started I also started to notice some strange behaviour by the laptop/VTS when connected .First off it would take forever to connect , the progress bar at the bottom right corner would load about 10 times before it gets online, whilst online changes entered via the keyboard would sometimes be ignored often causing it to disconnect then reconnect , when programming there would be none or partial interpolation of rows, sudden and random disconnecting and reconnecting and a weird storage error message when F4 is pressed. Finding the root cause of these issues took me one whole day , but I prevailed so all ,please BEWARE! Quote Link to comment Share on other sites More sharing options...
Simon Posted February 12, 2014 Report Share Posted February 12, 2014 The rule for any dash that is using the serial data stream is to disconnect at the ECU plug when tuning is being done. This is because the same data is being used for both tasks and having two devices connected is likely to cause issues. Quote Link to comment Share on other sites More sharing options...
Sutkale Posted February 12, 2014 Report Share Posted February 12, 2014 It seems that Haltech and Racepak have developed Racepak iq3 to work through true CAN communication. Any idea this would work with V/i88? Could anyone from "down there" be in touch with Haltech upon this?.. http://www.haltech.com/a-lot-of-dash-fo ... -dollar-2/ Quote Link to comment Share on other sites More sharing options...
Simon Posted February 12, 2014 Report Share Posted February 12, 2014 Its really Racepaks call we have provided all the info they need and I think they have even got it to prototype stage. But have not see a release version of a CAN interface. Quote Link to comment Share on other sites More sharing options...
MarcelB Posted February 13, 2014 Author Report Share Posted February 13, 2014 The rule for any dash that is using the serial data stream is to disconnect at the ECU plug when tuning is being done. This is because the same data is being used for both tasks and having two devices connected is likely to cause issues. I've never read or heard about any such rule , maybe it should be stated in the user manuals? Quote Link to comment Share on other sites More sharing options...
Dave Kriedeman Posted February 13, 2014 Report Share Posted February 13, 2014 Hi Marcel, unfortunately RS232 cant be run in parallel, (shared between 2 devices). There is a way to have the dash work while tuning when running RS232. You need to create a virtual port out (through port) on your laptop to stream the data out of the laptop to the dash. That way the laptop has it's direct connection to the ECU via RS232 and the dash is streamed the data from the laptop. This was a way around the exact same problem I used to have when tuning race boats. I had my laptop hooked up and the MOTEC dash wouldn't work, as they were setup using Serial data, no canbus available on the ECU being used. The boat driver had no way of knowing how many RPM etc he was at, other than me giving him instructions via helmet intercom. I will try to dig up how I used to set it up and let you know. Been so many years now. Regards Dave. Quote Link to comment Share on other sites More sharing options...
Simon Posted February 13, 2014 Report Share Posted February 13, 2014 Hi Marcel I've never read or heard about any such rule , maybe it should be stated in the user manuals? It is in the VTS help file. Can Not Communicate with Vi-PEC Tuning Software For help on setting up communications initially refer HERE. Check that a dash, display or logger is not connected to the ECUs Serial/CAN connector. Disconnect the dash during tuning. Dashes that use serial communications will not allow the ECU to communicate with Vi-PEC Tuning Software or do a firmware update. Reconnect the dash after tuning. Note that the dash can stay connected if it uses a CAN communication but must not have any wires connected to the ECUs serial TX/RX pins. Quote Link to comment Share on other sites More sharing options...
Sutkale Posted February 14, 2014 Report Share Posted February 14, 2014 Its really Racepaks call we have provided all the info they need and I think they have even got it to prototype stage. But have not see a release version of a CAN interface. Ok. But if Haltech version is utilizing a true CAN communication why wouldn´t it work with Vi-Pec CAN communication? Maybe a stupid question, but I´m not really familiar with CAN stuff. :roll: EDIT: Doable by generic Dash CAN setup?: The 'Transmit Generic Dash' mode sends out a range of common parameters, it is useful for dashes that are able to have a custom configuration. The parameters that are sent are in the table below. Setting up the Vi-PEC ECU: 1. Open the CAN Setup window (iVTS > ECU Controls > CAN Setup) 2. Select the CAN module to be used 3. Set the Mode to 'User Defined'. 4. Configure the Bit Rate to match what the dash requires. 5. Select a spare CAN channel. 6. Select 'Transmit Generic Dash' from the Mode drop-down menu. 7. Set the CAN ID to match what the dash expects. 8. Set the Transmit Rate to 20Hz or what the dash expects. 9. Make sure no other CAN channels are configured on the same CAN ID as the Generic Dash channel. 10. Click Apply and then OK. 11. Make sure a Store (F4) is performed. Setting up the Generic Dash: 1. The dash will need to be configured to match the data layout in the tables below. All parameters are sent as 16 bit unsigned numbers, with low byte first. Some parameters must be multiplied or offset (constant value added) to get the correct calibrated value. The limits flags are sent through as a bit field (described below). Data 0 Data 1 Data 2-3 Data 4-5 Data 6-7 Frame 1 0 0 Engine Speed Display (RPM) = Raw Range = 0 - 15000 RPM MAP Display (kPa) = Raw Range = 0 - 650 kPa MGP Display (kPa) = Raw -100 Range = -100 - 550 kPa Frame 2 1 0 Barometric Pressure Display (kPa) = Raw * 0.1 Range = 0 - 200 kPa TPS Display (%) = Raw * 0.1 Range = 0-100% Injector DC Display(%) = Raw * 0.1 Range = 0-100 % Frame 3 2 0 Injector DC (Sec) Display (%) = Raw * 0.1 Range = 0 - 100% Injector Pulse Width Display (ms) = Raw * 0.001 Range = 0 - 65 ms ECT Display (deg C) = Raw - 50 Range = -50 - 205 deg C Frame 4 3 0 IAT Display (deg C) = Raw - 50 Range = -20 - 205 deg C ECU Volts Display (V) = Raw * 0.01 Range = 0 - 65 V MAF Display (g/s) = Raw * 0.1 Range = 0 - 6500 g/s Frame 5 4 0 Gear Position Display (gear) = Raw Range = 0 - 6 Injector Timing Display (deg) = Raw Range = 0 - 719 deg Ignition Timing Display (deg) = (Raw * 0.1) - 100 Range = -100 - 100 deg Frame 6 5 0 Cam Inlet Position L Display (deg) = Raw * 0.1 Range = 0 - 60 deg Cam Inlet Position R Display (deg) = Raw * 0.1 Range = 0 - 60 deg Cam Exhaust Position L Display (deg) = Raw * -0.1 Range = -60 - 0 deg Frame 7 6 0 Cam Exhaust Position R Display (deg) = Raw * -0.1 Range = -60 - 0 deg WBO2 1 Display (AFR) = Raw * 0.01 Range = 0 - 65 AFR WBO2 2 Display (AFR) = Raw * 0.01 Range = 0 - 65 AFR Frame 8 7 0 Trig 1 Error Counter Display (counts) = Raw Range = 0 - 255 Fault Codes Display (code) = Raw Range = 0 - 255 Fuel Pressure Display (kPa) = Raw Range = 0 - 6550 kPa Frame 9 8 0 Oil Temp Display (deg C) = Raw - 50 Range = -50 - 205 deg C Oil Pressure Display (kPa) = Raw Range = 0 - 6550 kPa Speed 1 Display (kph) = Raw * 0.1 Range = 0 - 1000 kph Frame 10 9 0 Speed 2 Display (kph) = Raw * 0.1 Range = 0 - 1000 kph Speed 3 Display (kph) = Raw * 0.1 Range = 0 - 1000 kph Speed 4 Display (kph) = Raw * 0.1 Range = 0 - 1000 kph Frame 11 10 0 Knock Level 1 Display (units) = Raw * 5 Range = 0 - 1000 units Knock Level 2 Display (units) = Raw * 5 Range = 0 - 1000 units Knock Level 3 Display (units) = Raw * 5 Range = 0 - 1000 units Frame 12 11 0 Knock Level 4 Display (units) = Raw * 5 Range = 0 - 1000 units Knock Level 5 Display (units) = Raw * 5 Range = 0 - 1000 units Knock Level 6 Display (units) = Raw * 5 Range = 0 - 1000 units Frame 13 12 0 Knock Level 7 Display (units) = Raw * 5 Range = 0 - 1000 units Knock Level 8 Display (units) = Raw * 5 Range = 0 - 1000 units Limits Flags - Refer bit field definition below. Limits Flags Definition Bit 0 RPM Limit 1 MAP Limit 2 Speed Limit 3 Maximum Ignition Flag 4 Anti-lag Ignition Cut 5 High Supply Voltage Limit 6 Overrun Flag 7 Traction Limit 8 Low Supply Voltage Flag 9 Launch RPM Limit 10 Wakeup Flag 11 GP RPM Limit 1 12 CL Stepper Limit 13 GP RPM Limit 2 14 EThrottle Limit 15 Cyclic Idle Active Quote Link to comment Share on other sites More sharing options...
Simon Posted February 16, 2014 Report Share Posted February 16, 2014 I think with the Haltech the dash is a matched unit with custom firmware. I was under the impression that it looks for a specific ID from the ECU. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.