Printable View
I'm going to be fitting a Vipec I88 standalone ECU shortly, it has OBD capability:
i88 - Eight Channels of Fuel and Ignition control ? Vi-PEC Engine ManagementQuote:
ISO 15764 OBD. Can be used to connect to scan tools or mobile devices for display of ECU parameters. Skeleton functionality is currently implemented but will be improved in the future
Will this boost controller connect to the Vipec if it was wired through to a 16 pin OBDII plug?
Sorry it will not work through that OBD2 interface. ISO9141 vs ISO15764 OBD2 interface differs greatly.
Blackstealth thanks for posting the request calls for the LCDBC ext ports. What would the function be for EVOScan logging of fuel pressure (using a LCDBC supported external pressure sensor).
Many thanks!! Awesome product!!!
Update: v3.30 now allows alarms for Ext1-Ext4. ie. if oil pressure < xx psi, it flashes the screen you with a message. If I get more feedback and it works well, I can add audible alert to it also.
The LCDBC returns a value between 0 (0 volts), and 255 (5 volts). You just need to formulate what voltage means what on the sensor you're using. I'll do an example when I come back.
The example below is for a 7BAR (~100psi) oil pressure sensor, and to input the formula into Evoscan for datalogging an External Sensor 1,2,3 or 4.
Specs:
1 BAR = 14.5037738 PSI
7bar (101.526 PSI) oil pressure sensor
0.5v = 0psi
4.5v=101.526psi
Math manipulations:
101.526psi * 5v/(4.5v-0.5v) = 126.91psi magnitude equivalent range from 0volts to 5volts
101.526psi /(4.5v-0.5v) =25.3815psi per 1 volt
25.3815psi/2 = 12.69075psi per half volt
Therefore 0 volts = -12.69psi, 5 volts=(126.91psi-12.69psi=114.22psi).
You can take a chart and map it out and verify that is a straight line.
Final PSI = (x/255*5*25.3815 ) -12.69
Someone wanted the external Oil pressure sensor results and EGT results right after the main menu. This update now takes care of that, and if the user does not have the Ext1-Ext4 sensors defined in config menu, they will not be displayed in the menus at all -- making everyone satisfied.
http://lcdbc.xp3.biz/updates/UPDATE332.zip
I no longer have an OBD1 (91-93) ECU on my car to test rear fuel trims, can someone please test this out for me and report back? Best way to verify is to unplug battery to reset all fuel trims to 100 and verify they all read the same front trims and rear trims.
http://lcdbc.xp3.biz/updates/TESTRear.zip
Iv read this entire 128 page topic now and my eyes are blurry, i have my LCDBC arriving in a few days and have got the correct serial USB logging cable as recommended and am using the ODBII/Mut cable supplied by Blackstealth, but one question if i may as i have a 96 JDM GTO TT, ....Did the issues that Fastbike76 and another user in Sweden get resolved in the end? i read quite a bit about losing connection and freezing etc and maybe to do with 94/95 ECUs, im a little worried that i might have the same issues with it being a JDM the same as fastbike76, Or have things progressed since then with new versions etc..?
When the Sweden guy replaced his ECU, the connection problem went away 100%. This may be an interesting thread to read:
Datalogging hell: Me VS. 94-95 electrical system - 3000GT/Stealth International Message Center
Im just hoping that im not one of those unlucky ones that has a connection problem because changing the ECU is not an option for me, so grounding issues is something to look at but it didnt help either of those guys, it was ECU. so is the definitive answer that for some users the ECU is not compatible with the LCDBC or is it a cabling or grounding/noise issue? Great work BTW.
I think my old ecu was simply too slow as the problem got worse as revs increased.