Software On ELM Street - OBD2 Software Development

[Tazzi]

the latest download gets blocked by Eset AV while downloading.

Yeah, Seems the installer Im using gets picked up. Put I found the actual application is fine.

If its not one thing its another!

Unless paying for expensive installers ect that are known well, pretty much any application that is relatively new will be flagged as bad these days! For now, Im just going to keep it as is.

[antus]

Try the nullsoft installer. Or dont have an installer
Nullsoft was originally developed by winamp and is very widely used still.
http://nsis.sourceforge.net/Main_Page

[Tazzi]

Try the nullsoft installer. Or dont have an installer
Nullsoft was originally developed by winamp and is very widely used still.
http://nsis.sourceforge.net/Main_Page

Thanks Ant, Ill investigate into that.
I have to utilize an installer since the application needs to be registered into the system so that it doesnt delete the license
Some AV as well as common used cleaners such as CCleaner will clear anything and everything that isnt registered within windows

[monaro308]

Tazzi, I ended up buying the usb elm you posted up and gave it a try tonight.
Initially I had no luck trying to connect as my device com port recognised it as com port 4.
I tried settings on auto detect.
When I selected "console" I noticed it trying to connect to com port 7.
After I set my device settings to com port 7 I had better luck ie the connection bar was now searching but failing to connect.
Then I deselected the "enable fast baud" with no luck.
Finally I deselected "get vehicle info on start up" and it connects every time
I'll have a little play on the weekend and report back.
cheers

soe.png

[VX L67 Getrag]

Yeah it can be picky sometimes with vehicle detection if it doesn't have some data at the right section.

I think Tazzi is away for a few weeks so I'll try & help where I can!

[Tazzi]

Tazzi, I ended up buying the usb elm you posted up and gave it a try tonight.
Initially I had no luck trying to connect as my device com port recognised it as com port 4.
I tried settings on auto detect.
When I selected "console" I noticed it trying to connect to com port 7.
After I set my device settings to com port 7 I had better luck ie the connection bar was now searching but failing to connect.
Then I deselected the "enable fast baud" with no luck.
Finally I deselected "get vehicle info on start up" and it connects every time
I'll have a little play on the weekend and report back.
cheers

Ahhh, could you copy/paste the console log when it fails? So I can see where it is failing?

Remember I built the software based on "bench ecu readings", so when getting "vehicle data" the ecu might spit out something that I have not yet received!

[monaro308]

No worries Tazzi, I'll have a play tomorrow night and copy/paste each step if you want.
cheers

[Tazzi]

Yeah that would be great mate. I can almost guarentee it will be getting stuck on the freeze frames stuff.

The freeze frame stuff is quite difficult to get working on the elm. Ill have to think about whether to remove it or not since the elm is pushed to its limits to pull that info from the ecu's hence it can fail on that part easily.

[monaro308]

Hi Tazzi,
I connected up tonight and had no issue with SOE connecting to the same port as the elm ie com port 4 but did have an issue with the lappy losing the device driver.
Last time my lappy showed the elm as com port 4 but SOE searching for com port 7. This time the l/top was still on com port 7 but I had to change the port setting to 4 and
re-install the device driver.
After the above,SOE found the correct com port 4 to the device com port...so all good there.
These are the steps I took....

def1.png

def2.png

def3.png

I also had this fault code but i'll have to check with my tech 2 if its an actual fault code present.

def code.png

Def a freeze frame issue.
Let me know if you want more testing

[Tazzi]

Yeah definately a freeze frame issue there. Looks like it's grabbed some information.. But failed right near the end.. Hmmm... I'll have to add in some more error catching there to narrow down the problem.

Stupid freeze freeze frame is causing issues in both the can and ls1 protocols!