Software On ELM Street - OBD2 Software Development

[Tazzi]

I was informed that the 500,000 baud might not actually be working. Will double check this later. So best everyone just stick to 115200 for the moment.

[Charlescrown]

Tooooooo early Tazzi you need to post at 2AM as usual.

[Tazzi]

Tooooooo early Tazzi you need to post at 2AM as usual.

Yeah mean kinda like now?

4-5hours a night, all you need

[jca]

Hi Tazzi any chance I got get a software code to have a play

[Tazzi]

Hi Tazzi any chance I got get a software code to have a play

Suuuure can mate. Just send me a PM and Ill get back to you.

[jca]

Hi Tazzi I sent one the other day was thinking it didn't go thu I'll try again now - thanks

[Tazzi]

Soooo, I managed to get over 50+ emails over the past two days asking for licenses, tutorials or help with SOE.
(Why werent you with your mrs for valentines guys! Geez! )

Excuse any late replies! I am working through it slowly.

Anyone that hasnt already received an email for a license, please send me a Private Message incase I missed your email.
Im still working through my main emails, so send PM if you want to get a response soon!

v0.0.1.0 will be arriving shortly. Only small changes to the "baud rate change" and text output to the console log.
Also have the final implementations of the engine code clear encoded. I will be calling upon people to test this out that have fault codes lodged

Taz over and out.

[Tazzi]

Hopefully Iv gotten back to everyone now.

For everyone asking.. constantly.. and multiple times... yes the "clear faults" button will be finished soon!

[Tazzi]

Grrr.. Im STILL getting issues with the auto detect hanging/failing when in car. I honestly cannot figure out where its hanging to save myself.. since it has timeouts on all processes. It has to be some silly bug in the serial.read or something where the application hangs.

Even more weird is that when stepping through the code while in car.. theres no issues?! I speed it up abit.. still no issues!. Let it run at full speed.. and the hanging begins! Grr!

I cannot even remotely explain the frustration this causes. This is easily resolved by selecting the comport, and the default baud rate 38400. But thats not how Iv designed this...

[antus]

Yep, those bugs are a bitch. Probably is going to be a timing issue, possibly not directly in your code, but as for finding it..... I would use the debug print functionality to log when certain functions are entered or exitied, so that you can run it at full speed and sooner or later find a function that enters but does not exit. Use the VB equivalent of #ifdefs so you can compile with and without the debug code present (or a subset of it), so you can test different things without slowing you app down too much, and so that you can disable it (not compile it in) once the bug is found.