lekonna

if gauges on the UI hurt the logging rate then something is really wrong .. makes no sense what so ever its hard to even think up scenarios where this might be happening, only thing that i can think of is that the stream logs all the stuff from the ECU that is defined to be logged and the gauges then query their data separately. which would be pretty silly way to implement the gauges.

http://www.injectordynamics.com/ID2000.html#Dynamic Flow Rate and Dead Time Summary i used that for my EV14 2000cc injectors, they are working just fine.

atleast the part number for the igniter changes, dunno whats the difference though.

i'm running ID2000's as well. one additional thing that i did was to get complete new ecu wiring harness, when i was playing around with the coils trying to figure this out i found out that some of the coil wiring was cracked and looked generally like shit anyways. Anyways one aristo with link ecu had the same issues with sparktec coils here, he switched to using a cdi box and the problems were gone.

just thought i'd chime in,i had the exact same problem with the original ignition setup in 2jz (non vvti) could not find a solution so switched to 034 motorsport coils, no problems with these. this stuff puzzles me since local guy dynoed 1127hp with the orig coils and just the hks dli box.

here is the wiring: vipec pin 3 (white) CAN H <---> arduino shield pin 3 on the DB9 plug vipec pin 4 (green) CAN L <---> arduino shield pin 5 on the DB9 ref. http://www.sparkfun.com/datasheets/DevT ... ld-v12.pdf vts -> help -> wiring information -> communications port pinout you are correct, the code i'm referring to here is the source code for the microcontroller in the arduino that will run the can stuff and direct the display. what you do is once you have the arduino, you plug it into your pc with usb cable and use the arduino ide do flash the software to the board. At this point you can modify the parameters you want the display to show, it is quite easy to do. then you just hook everything together, setup the vipec and you are done. vipec can setup

The manual states: "A two terminal ISC solenoid may be wired to Auxiliary Channels 1 to 8. Injection channels can not be used for ISC control" (under the manual topic wiring information -> output wiring -> idle speed control ->"Two Terminal ISC Solenoid" dug this stuff up when i was wiring my 3 terminal isc, (you have to use aux1 for the slave)

you can ignore that setting, its bit confusing, would be good to get a ui option like "pwm" which would not actually change anything, but this question pops up every now and then.

that is excellent news! can you post the dyno plot? I need to think of a new turbo setup for next summer and sequential might be an option

its fairly easy to put new wires into the vipec connector. you need to get the correct pins, crimp the wires (this can be a pain without the correct tools) and insert them into the connector. When you push wires into the connector, push the white plate on the connector with a tip of a flat screw driver so that it unlocks, then you can push the wire through the back side. then lock the connector again.

added a button to flip between pages. code also updated. was initially going to add max and min value display on a double click but since i was lazy and didn't solder a small capasitor in the switch i get lots of noise and had to filter it in the interrupt handler to make the button behave better. will think of a way to implement the display for min and max also. the button is wired between digital pin 3 and ground.

here is a huge dip where the setup changes from single to parallel, the power drops like 70hp, you gotta feel that in the car also? If you can manage to get rid of that by pre-spooling the other turbo like the original does, then the same problem will appear if its really hot, or really cold ect. none the less, looks like a really fun car to drive with that setup

it is possible to get the sequential to work, but tuning it from the scratch will take so much time that if you are not doing it ourself it will cost an arm and a leg, possibly even more.

well, for this setup you are _not_ going to find a base map that works just by plugging it in. you will have to wire all of the pressure solenoids that the original system has (7 or so) and then configure them by trial and error so that the turbos work in sequential order. if you change the original setup even a little (add bigger ic) you will notice it while driving since the original ECU is so tuned to the factory setup. If the single setup is impossible, you might consider scratching the whole idea of sequential and just run the turbos parallel, you loose some of the low-end torque but can get the full hp out of the high end. as far as i can remember the waste-gate setup for the original twins is somewhat exotic so it might take some tuning to get the boost control to work properly, but definitely this is the easiest way to get the horses out of your engine. wire the valve which is under the second turbo in the y part so that it is always open and remove and disconnect all stuff that is related to controling the sequential. it will make your setup 10x simpler and easier to tune. edit: here is a description by Ray Hall on how to go about doing this http://www.turbofast.com.au/lexusturbo.html

frankly, i would get rid of the factory sequential setup and install single turbo instead. the sequential will be hell to get working properly and the gain is minimal compared to properly done single setup. you can try to modify the sequential maps to work with the vtt-i but i don't see it as being worth the effort.

i've got a map of a sequential setup somewhere.. though its not going to be easy to get working perfectly, once you deviate from the factory hardware even a bit you will notice it.

when you open the runtime panel and select the CAN tab, what does it say for CAN 1 Status ? all green ?

have you configured the can to output anything? atleast for me it was off by default and thus no data transfered.

yeah, i have also set my gp limits for fuel and oil pressure, no more limits left for the TC.

you could use both, so but the GP limit to do the fuel / ign cut and try to get the finer control with the ignition retard. I need to get my shit together and finally wire the front wheel speed sensor to test this stuff out

here you go: https://github.com/lekonna/vipec_can_display the main code is dead simple https://github.com/lekonna/vipec_can_di ... isplay.ino I'll play around with it some more during the weekend when i have some time. so far seems to work just fine. I can dig out the pin order i used to solder the serial cable to the vipec wires tomorrow.

sure thing, i'm using library made by some other guy, but the copyright states that it can be shared, so i see no problem with sharing it. i'll push it to github this way its easier to see the updates, but seriously, what i did to the example that came with the can shield was just add a function to the Canbus class that reads 4 variables and then used that to dig stuff out, vipec documentation made it quite easy to do this.

now it does what i want it to do. nice.

the can thingy, is the mcp2515 chip on the add-on board there, it communicates with the AVR micro controller through spi-bus, not exactly something you can just go and plug on a nexus tablet. you might get away with either: if you can hack the nexus to work in a usb host mode and connect some can usb dongle that actually support linux you might get data on the tablet. Also don't know if the nexus kernel is compile with module support for the usb drivers. Or: actually, as the arduino works as usb serial, and also works in linux, it might be possible to use the nexus with just usb connected to this thing, i use the serial connection to debug stuff and it works just fine under linux. but then you'd have to write the ui and all that tedious crap life is so much simpler if you just stick close enough to the hardware.

Alright, So i was looking for a very small display, just to show me couple of basic items i need to know from the ECU such as oil pressure and oil temp ect. basically everything out there was way over spec and price for this type of application. I had an arduino uno laying around and decided to play with that a bit. so what we have here is essentially, arduino uno, serial lcd and a can shield. https://www.sparkfun.com/products/11021 https://www.sparkfun.com/products/10039 https://www.sparkfun.com/products/9394 which is just bit under 100$ if you have to purchase them all trough sparkfun which is not the cheapest option out there. I soldered a pin header on the Can shield so that it sits on top of the arduino uno and hacked up some leads for the lcd. Jean delivered me a flying leads can cable for Vipec and today i finally had some time to play around with it. What i would like to know from the vipec support is that where is the data format defined in which the vipec sends the different variables? For example the TPS seems to range from 32-360 when reading it as a sequential data with 2 bytes of data with the data1 as H and data0 as L byte. Would be much easier to implement the stuff i need if i didn't have to reverse engineer the data format for each variable i possibly want to see Is there a table available somewhere in the documentation ? I will publish the code and the setup if somebody wishes to modify and take it into use for them selves, though most likely i will not have time to support it too much. the Can shield has a 4 way joystic and a SD card place also so if somebody wants to get creative and implement something more complex, it should work fine.