Haltech HalwinX released!
06-19-04, 03:24 PM
#26
The mystery of the prize.
Originally posted by $150FC
When are you expecting to be done? (Are you doing a win32 port?)
When are you expecting to be done? (Are you doing a win32 port?)
I am redoing the gauges to work with my new engine data system (it got changed when I added support for multiple E6 ECU's (e6k, e6x, e6s, all in one program etc...)) and I will be driving to florida with a virtual dash in the car at the end of july, as the beta test of the software. When I return, early august, I will hopefully be releasing the first full version with online editing and gauges all in one.
I am waiting for my techedge wideband o2 controller to arrive so I can start writing some software for communicating with it over the serial port, and hopefully have that done before my trip. I will have a virtual dash in the car displaying all desired engine data obtained from the E6K over the serial port, in realtime, alongside iwth the wideband o2 data obtained from the techedge over the 2nd serial port, and the techedge also has 3 analog inputs which I will have oil pressure and fuel level connected to so those gauges can be displayed next to the e6k supplied data even though the e6k does not have anything to do with those inputs. The techedge also has thermocouple inputs so I might have EGT display too if I get around to it before the trip.
But this illustrates the potential when the ecu is opened up and you can customize the software for your own needs.
06-19-04, 04:01 PM
#27
Absolute Power is Awesome
Originally posted by pengarufoo
Well, GNU/Linux is my cup of tea, and it should be of interest to everyone... continuing to use closed proprietary systems and software will just keep sticking you in these STUPID situations (have ecu, software only available for old system, source unavailable, undocumented system, reverse engineering required to make it work in another system, potential for lawsuits a la DMCA is high... must ask self again, why did I pay for this equipment?)
After my software is released under the GPL, the E6K platform will be opened up more than it has ever been before. Source and documentation will be available documenting how the ECU<->software interface works and a free library will be available for using the ECU in your programs. It opens the doors for developers & hobbyists around the world to make tools which can help YOU use the equipment you bought, and all derivative works will be redistributed under the GPL ensuring their availability to all of us. If this sounds like something really good to you, free (as in free speech, libre) software is your cup of tea, which includes GNU/Linux.
Of course, this also makes it possible for those interested to make windows versions, provided they adhere to the terms of the GPL.
I have little desire in creating a win32 port, I have gone out of my way to make bootable images of the gauge software which include the linux kernel and the gauge software on one disk, so you can simply boot off the floppy and run the software without disturbing whatever system you have on your laptop. If you already have GNU/Linux on the PC you can just run the software natively without the boot image.
Some of you may get scared or think scary computer geek when you see the term GNU/Linux, or get confused when the terms free software pop up and they are not referring to simply the monetary cost of the software. I refer you to this speech by Eben Moglen which should help clear some things up:
http://moglen.law.columbia.edu/publi...ne-speech.html
As for the setup variables, I will support them, it's just not a high priority right now... They are already all reverse engineered, it's just the implementation in the library that has to be done, it's tedious work... the setup variables need a bunch of metadata describing their offsets into the ecu data, possible values, and a dependancy tree created so the software can enable/disable settings when other settings they depend on get enabled/disabled etc. With the quantity of settings, this becomes quite time consuming to create.
I apologize for the long post, if you have any further questions or comments you can post all you want on the subject over on my forum http://pengaru.com/forums under microprocessors, or keep it here if you like, I do visit this area regularly.
Well, GNU/Linux is my cup of tea, and it should be of interest to everyone... continuing to use closed proprietary systems and software will just keep sticking you in these STUPID situations (have ecu, software only available for old system, source unavailable, undocumented system, reverse engineering required to make it work in another system, potential for lawsuits a la DMCA is high... must ask self again, why did I pay for this equipment?)
After my software is released under the GPL, the E6K platform will be opened up more than it has ever been before. Source and documentation will be available documenting how the ECU<->software interface works and a free library will be available for using the ECU in your programs. It opens the doors for developers & hobbyists around the world to make tools which can help YOU use the equipment you bought, and all derivative works will be redistributed under the GPL ensuring their availability to all of us. If this sounds like something really good to you, free (as in free speech, libre) software is your cup of tea, which includes GNU/Linux.
Of course, this also makes it possible for those interested to make windows versions, provided they adhere to the terms of the GPL.
I have little desire in creating a win32 port, I have gone out of my way to make bootable images of the gauge software which include the linux kernel and the gauge software on one disk, so you can simply boot off the floppy and run the software without disturbing whatever system you have on your laptop. If you already have GNU/Linux on the PC you can just run the software natively without the boot image.
Some of you may get scared or think scary computer geek when you see the term GNU/Linux, or get confused when the terms free software pop up and they are not referring to simply the monetary cost of the software. I refer you to this speech by Eben Moglen which should help clear some things up:
http://moglen.law.columbia.edu/publi...ne-speech.html
As for the setup variables, I will support them, it's just not a high priority right now... They are already all reverse engineered, it's just the implementation in the library that has to be done, it's tedious work... the setup variables need a bunch of metadata describing their offsets into the ecu data, possible values, and a dependancy tree created so the software can enable/disable settings when other settings they depend on get enabled/disabled etc. With the quantity of settings, this becomes quite time consuming to create.
I apologize for the long post, if you have any further questions or comments you can post all you want on the subject over on my forum http://pengaru.com/forums under microprocessors, or keep it here if you like, I do visit this area regularly.
Thread
Thread Starter
Forum
Replies
Last Post
