Under which condition do you get a lost connection? Driving through a bumpy patch of road? Or when you go full throttle?Quote:
Originally Posted by HLxDrummer
Printable View
Under which condition do you get a lost connection? Driving through a bumpy patch of road? Or when you go full throttle?Quote:
Originally Posted by HLxDrummer
FYI, evoscan v2.6 gave sample speed of 278 and now Evoscan v2.9 gives us 313, a nice increase in speed for free. Datalogging the LCDBC's own boost and WBO2 readings will bump the average up because it doesn't have to ask the ECU, so this brings it to 373.
http://i782.photobucket.com/albums/y...mprovement.jpg
Does evoscan work with 1st gens for logging?
Yes it does.Quote:
Originally Posted by FeaRpb
OK, I installed my 16mhz processor, and flashed in the v3.0 that you e-mailed to me... I now have no data connection to the ECU. I've got it set up as OBD1 ecu type, with a standard OBD1 cable in the menu. What am I missing?
I may have made a mistake for your custom version (ie. if I mixed up 16mhz and 20mhz it will cause what you described). I'll send you another.Quote:
Originally Posted by RealMcCoy
I don't think you did... I think there's something else going on. I still get the same thing with the one you sent me last night.Quote:
Originally Posted by BlackStealth
Here's what I have done so far: I swapped the 8mhz chip back in to confirm the hardware was OK, then reinstalled the 16mhz chip and flashed in v3.0 from your website. Still no communication. I then entertained the possibility that I was shipped 20mhz chips,(I was pretty sure you shipped these before they were available, but I wanted to make sure...) so I flashed in the 20mhz v3.0. that made no difference.
I then installed the second chip, checked it's operation right out of the box, (v2.26) and confirmed it was working fine. then flashed in the 16mhz v3.0 from your website, and I'm back to no communication...
Edit: the weirdness continues... Still no communication if I try v2.27. If I try to flash in v2.26 (which is what I confirmed working out of the box on the second chip) both chips go apeshit... Random weird ASCII characters rapidly scrolling across the screen....
Should send me email next time where I can respond quicker. Anyhow, I think the ECUclock speed is not selected as 100% in the setup config. Anything other than 100% and you will not be able to connect to the ECU. Setting up the individual setup config is time consuming so I made a program to do it for me. I do this for everyone to save some time, but I may have forgotten to do yours. I sent you an email with the program to do it for you.
I just re-read your message, and just noticed that you said it was working with the 16Mhz version (v2.26). I never released the 16mhz version because it quickly went to v3.00 soon afterwards. I'll look into this.
EDIT: If you're using my OBD1 cable, you must use "ECU cable=OBD1 Enhanced cable" instead of "ECU cable=OBD1 Normal".
I would have e-mailed if I had initially entertained the possibility that the issue was something you forgot... My assumption, and reason for posting it here, was that the problem was something I was doing wrong, and that the rest of the class could learn from my mistake.
Turns out that was exactly the case... After trying all the flashes you sent me, It turned out the problem was entirely my cable selection... Once I changed it to "enhanced OBD1" we were golden...
I have a question about the two pass knock alarm... While it has to see it twice to set the alarm, does it still record the single highest reading in Knock Peak?
Yes, Knock Peak will always record highest knock event, regardless of what knock alarm does.Quote:
Originally Posted by RealMcCoy
Glad to see it was just setup config issue only. Yeah, anyone that purchased an OBD1 cable from me needs to select "Enhanced OBD1 cable" for cable type.
I received mine today, I will get to look at it tomorrow.
Post via Tapatalk
Antero, I got the processor the other day (thanks!) but realized I'm not up-to-speed on the software, etc.
I remember when I bought it I told you I am 92 TT OBDI, and will be logging with HHH.
Can you refresh my memory on what I still need to do to have everything I need?
I'd recommend buying an FTDI-based USB-to-serial adapter, so you can interface the serial cable to your notebook and run HHH. Here's what I use:Quote:
Originally Posted by j2k4
New USB to Serial RS232 Adapter FTDI Chipset Cable | eBay
Got to look at mine today.
LCD Boost Controller Images.
I can use a standard Serial Cable tho right?Quote:
Originally Posted by BlackStealth
Notebook with builtin serial port:Quote:
Originally Posted by FeaRpb
HHH does not need it.
Evoscan still requires FTDI base adapter.
Notebook without serial port:
Both HHH and Evoscan will want the FTDI based USB-to-serial adapter.
Palm device:
A null-modem adapter is required.
Install Complete
http://i.imgur.com/uN1Kh.jpg
Looks perfect! :bigthumb:
Is the screen that washed out when looked at by eye, or is the camera just showing the backlight washing out the text?
It is my camera, it is really sensitive to light projected colors.
FeaRpb: nice install.
Firmware 3.01 is now made available. I made an emphasis on datalogging, such that you can pick whatever you like to datalog and it won't slow down. It will maintain high speed. I also took advantage of some parallel processing such that when Boost, WBO2, Oil Pressure or EGT sensor is being measured it does not halt the microprocessor, so the microprocessor can keep on working. Chrome 2.0 mod is supported for 98/99 flashECU users. This means the special 2-Byte Airflow and 2-Byte Load are supported. The Load vs Dutycycle will automatically switch to 2-Byte load when Chrome ECU is selected in the setup config.
I think your user manual is dated.
Under the Setup Config in the manual it seems to have different things listed than what are actually in the config menu. Or maybe I am just crazy..
Yup, you're correct, it's dated.Quote:
Originally Posted by FeaRpb
Do you have any plans on updating it? And also, the website seems to be down.
I update it from time to time. The website does not belong to me, it belongs to a user on here. Hopefully it comes back online soon.Quote:
Originally Posted by FeaRpb
Well I couldn't wait anymore for the original website to come back up again, so here's another website for updates:
http://www.lcdbc.xp3.biz
The new processor and firmware fixed the problems with MMcd... It absolutely screams along now. I was getting 35 hz logging 11 items. That's about 385 samples per second. That's at least three times faster than I've ever seen it communicate with the 1st gen directly.
I'm assuming the LCDBC doesn't communicate with the 1st gen ECU that fast...? It's just now able to pass info on to the logger without interrupting the primary communication? I'm probably getting some duplicate readings when the logger requests info that hasn't been re-sampled yet?
Still don't know how to log WBO2 and Boost... But it's not a big deal to me yet. I can log boost through EGRT, and I don't have a WBO2 yet.
Yes you're correct that the samples are too fast for OBD1. This is what I have done:
(1) LCDBC makes requests to OBD1 ECU (~ 72 samples/sec, whatever the maximum OBD1 ECU can produce).
(2) LCDBC stores the results into memory
(3) LCDBC accepts new requests from datalogger device, and adds it to it's list of "items to datalog" from ECU.
(4) While the LCDBC waits for response from OBD1 ECU, it checks to see if dataloger device is asking. It replies with an answer stored from memory instead of waiting. This is where crazy speed increase comes from.
So in short, yes the sample speed are too fast. I can introduce a delay at step 4 to bring the sample speed back down. I was just waiting for feedback if I should do that or not.
Im not sure if this is a feature or not, but is there a low boost and high boost setting? If not, how hard would it be to make one?
I'm planning on posting my install stuff here soon when I get a chance. If you want you can use the info in it for a new manual or just link to it. IDC whatever you want to do.Quote:
Originally Posted by BlackStealth
Antero, I was just wondering how soon Adam will be done with testing. I have no problem testing the three different cable designs and will pay for them since I will know in a hurry if they work. Just logging as few as 2-3 items I still have problems above 3k rpms. Grounds are all good too. Maybe I should ask Adam how close he is since he's cloning my ecu this weekend. I need to get a noise cancelling OBDII filter cable badly so I can datalog boost; otherwise, I have to buy another EBC or wait to wire in a boost sensor to the flashed ECU because I need to sort some issues out on my car that have been plaguing me the past 5 months. I ordered a Hallman Pro MBC to use instead since I'm pretty sure the LCD BC won't let me run a steady 25+ psi until it gets more features outside of a duty cycle based control. I tried setting up the duty cycle vs airflow but it won't work when the LCD BC doesn't get clean enough OBDII readings. Maybe once I fix that and do a 2-byte airflow vs duty cycle it will be better outside of temperature changes. For now I'm abandoning it.
When the "Auxiliary input" sees ground, it will activate. You can use this to run low boost mode. To wire it up, grab a switch and put one wire to ground, and the other lead to the Aux. input.Quote:
Originally Posted by FeaRpb
Last time I asked Adam, he did not receive it yet (slow ground shipping). That's why he was unable to provide feedback on the noise filter designs. It's been a while now, so I haven't asked him if he's received it yet or not.
I have parts to build a noise filter design #3, but none of the others. I think #3 is the best so that's why I have accumulated parts for it. So if you want try that, send me a private message.
Firmware 3.03 is available. http://lcdbc.xp3.biz/update.html
For 96-97 ECU users (OBD2): Screen changes are now nice and quick, and much improved datalogging speeds for you too.
For MUT connection users: Modified connection routine (attempts 3 and 4 now use different method of connecting).
For users with enhanced OBD2/MUT cables: If disconnected from ECU, the reconnection routine will now take advantage of the new enhanced OBD2/MUT cables by simulating a physical cable removal and reinsertion.
What cable did you send with mine?
The new enhanced OBD2/MUT cable came out about 2 months ago, so if it was purchased within that time, then that's the kind you have.Quote:
Originally Posted by 2fnloud
That I did received it last week, so only the Firmware 3.03 is what I need to down load and flash then?
Yes that is correct.Quote:
Originally Posted by 2fnloud
If I did that wouldn't I love the ability to tap my wideband into the lcd?Quote:
Originally Posted by BlackStealth
EDIT: NVM, I read that the blue wire is only for the WB02 and the white wire is the one I can ground
Can this flash be done with the devise un-installed?