pcmhacking.net

delcowizzid wrote:gaaaaayyyyy tried the latest version and my silly laptop doesnt have .net4????? when i open the program i have the opposite problem to kal laptops now im not new or upto date enough LOL.

Yeeaaahhhh, I can drop the frame work, its just been set by default to a later .net framework as it seems the custom gauges work a bit more smooth

I can tryyyyy drop it to about 2.5/3. Will have to check if the gauges still work correctly! Any idea what framework those kal laptops use?

ill have to boot up and find out what version im on its the bare minimum to run everything vl400 has made LOL xp installation without sp3 lol.i tried an older version too but it just crashed when trying to connect .then i used the AVT adx's after 30 minutes of pissing round got a connection that wouldnt error every 2 seconds LOL this tool is badly needed xdf's with multiple connection macros is just a pita .i did manage to find what the error code was after half an hour though so it wasnt a total loss just a massive mindf**k LOL

where do you download it from?

about 5 pages back mate

ejukated wrote:where do you download it from?

delcowizzid wrote:about 5 pages back mate

The last version *should* work. But Iv done some massive changes since then to the automatic connection/detection, I was having some error issues with configuring the baud rate to the fastest baud. This is done by default now. As well as the fault code reading and live engine data reading. And alot of fixes to bugs/errors that would occur with different elms. Would probably advise against using old versions as they will have little errors I fixed up along the way.
Im currently away from my test setup, but if the latest changes Iv done work all good, itll be time for a proper release


Ill look into dropping the framework to the minimum I can. Im fairly certain Im not using any significant things that need high framework. Just a few things were made redundant/faster when drawing/rendering objects for the custom controls. Will see what happens!

I have only recently registered as a member of the forum, but I've been following this development for the last 6 months.

I just wanted to pass on my appreciation for the absolutely herculean effort that you have put into this, Tazzi. Most of what I've read has been a little bit beyond my understanding, but I certainly appreciate the time and saint-like patience you've displayed throughout this development.

So, well-done and thank you!

Mathew

Wood300 wrote:I have only recently registered as a member of the forum, but I've been following this development for the last 6 months.

I just wanted to pass on my appreciation for the absolutely herculean effort that you have put into this, Tazzi. Most of what I've read has been a little bit beyond my understanding, but I certainly appreciate the time and saint-like patience you've displayed throughout this development.

So, well-done and thank you!

Mathew

Cheers Matt
I figured there must be a few people watching with 15K+ views. Its good to hear from some of the people lurking in the background! Hopefully, I will have something a bit more concrete for everyone to try out soon.
Im a little bit hesitate on release as I can see this freeware being abused and sold on ebay by a specific fleabayer for 180+ (You know who you are... I know your watching..) ..Nothing worse then seeing someone extorting someones hard work. So I will prevent this.. But I have full intentions of providing this version free!

Its been an interesting development with the ELM thats for sure. Will hopefully eliminate any BS being sold on ebay or false advertising saying "works with Holdens".. when they really dont! Will be very interested into moving onto the next set of cars.. Gen4 ecus, VE's ect. VEs also have another variety of modules on the CAN bus.. so this will probably be another addition to the application!

Oh oh, before I forget. Is there much interest in transmission data/diagnostics? Do people actually use this at all or is it really only engine diagnostics? I dont think Iv ever popped the tech2 on for trans diagnstics?

I dont have any transmission control modules here... I know in the VZ V6 cars, the TCM has a device header of 7E2 (I think). If anyone has a TCM thats willing to donate, or fairly cheap, itd be greatly appreciated!
Currently looks like the cheapest on ebay is $55 plus shipping.. which isnt too bad but its literally only going to ever go on the bench setup.. and once all worked out, will be useless lol.

Have got the entire main setup now fully configured and working.

Vin,Serial,freeze frames, faults and PIDs available will all be detected on connection (On by default). This can be turned off for speed, or for unsupported cars.

I currently only did the CAN section as this seemed to be the harder part.. vpw is just alot easier to do. Most of the functions can be easily applied for VPW so 99% of the work is completed there.
So whats left to do?!? Well before the next release, I would like to complete:
-fully functioning engine data section for VPW
-Startup connection info for VPW as done on CAN
-Receive/Transmit filter working on VPW for raw logging
-Ensure Iv captured all possible fault codes for both LS1 and VZ V6 ecus


Also, I believe Iv managed to be able to detect Bluetooth devices. So.. hopefully.. if a bluetooth device is used, the application *should* automatically disable the fast baud update to prevent the bluetooth ELM from going spastic.
I will need some brave soles test that out, it wont need to be connected to the car, just need a variety of bluetooth devices connected to the program to see if I have solved that annoying issue. I still hate bluetooth devices...and could easily solve this issue by not updating the baud rate.. but I rather maintain speed and reliability with the usb versions.

That was alot harder than I was expecting.. thought I had it working last night but must have been half asleep.

Obtaining the freeze frame data was causing soooo much hassle.. I almost just went to delete it and forget it! When requesting freeze data.. it sends off a "7F" response.. then it sends off the real freeze frame data. Only problem is the ELM doesnt know that theres is more data coming even when Im telling it there is! *kicks elm*

Soo.. I had to be sneaky. I fire off the frame, switch to "monitor all" mode, capture all the desired data then go back to standard mode again.

The entire process takes about 7seconds on average. This includes running through all of the PIDs that are supported. So pretty happy with that!