My LCD screen project, boost, WBO2, Knock, etc

[BlackStealth]

Do you have any tips for seeing if the lost connection is a result of the cable/hardware or software?

Under which condition do you get a lost connection? Driving through a bumpy patch of road? Or when you go full throttle?

[BlackStealth]

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.

[FeaRpb]

Does evoscan work with 1st gens for logging?

[BlackStealth]

Does evoscan work with 1st gens for logging?

Yes it does.

[RealMcCoy]

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?

[BlackStealth]

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.

[RealMcCoy]

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.

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.

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....

[BlackStealth]

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".

[RealMcCoy]

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?

[BlackStealth]

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.

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.