##### ## ## ## ## ##### ## #####
_________ \__ _/ ) ( | | | | | | |\_) ) (____/
## ## ## ## ## ## ##### ## ####
__ __ \ \/ / \ / / \ /_/\_\
IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now. Visit Preferences to set your user name Summary of change: PSITuner is an ongoing project to provide commercial quality tuning software for free to the VEMS community. Quality tuning software is necessary before hoping for any sort of commercial marketing initiative. If tuners like the product and find it easy to set up and use then they are more likely to recommend and sell the product. * PSITuner will not be everything to everyone. Instead it seeks to provide a feature-rich but easy to use interface to Windows users. There are no plans to offer a multiple OS version as 99+% of commercial tuners use a windows based laptop for their tuning needs. The software is designed to offer good performance even on very modest configurations. It is also designed not to absolutely require a complex installation procedure - ie run it off a CD or maybe even a floppy disk if you wish. * PSITuner is also designed to provide access to all features provided by the VEMS system. This way you can flash update, setup and tune your system with only one program, not a large variety that non-technical users may find difficult to deal with. --------------------------------------------------------------- Progress so far. I've begun re-writing the software using C++ Builder but every time I need more features in the original version it's easier to load up Delphi and hack it in so there are 2 versions right now... The Delphi one has been released: * I've started over. I ditched the archaic version of delphi in favour of c++ builder. This way the application framework can be made available to everyone in a portable fashion. This first implementation will support the SIP-R protocol for a more reliable ECU connection. * Framework has been completed with some basic menus entered. I'm working on porting over some of the framework. With the new protocol ECU communications will be far more straightforward. * Started designing a new Map wizard. This will be documented in VEMS/OtherTuningSoftware/PSITuner/MapWizard ---------- [http://www.vems.hu/files/hackish/psituner-snapshot.zip PSITuner-snapshot.zip] This is the delphi version Build 358. Here is what it can do: * Communicate with the VEMS. It establishes a connection at 9600 baud and then switches to the user specified rate. * It is also able to detect if the ECU is in Bootloader mode, even if at 19200 baud. * Once connected you can upload a new firmware revision. It is guaranteed to migrate your config settings but not currently the map settings :( * In the Hardware Setup dialog you have access to change all of the O2 settings, some display settings as well as a test mode where channels can be manually turned on and off. * You can config the fan outputs as well. * upon disconnection it restores the baudrate to 9600 and executes a "bye" command so it's friendly with mtx or a terminal program after you exit. * That's all I can remember... --------------------------------------------------------------- TODO: * Implement and test firmware updates as well as networked update notifications. * Complete the simple number adjustment and entry class for those of us who road tune late at night, +/- keys are so much easier to use. * Define an XML based file format to import and export settings. * Define some standard profiles for common injector and sensor types. * Import some backend datalogging and adjustment routines. * Publish a first pre-beta version ------------------------ VEMS/OtherTuningSoftware/PSITuner/DevelCode - Go here for development work in progress snapshots. Pre-Alpha testers are needed! VEMS/SerialComm/SIPR/ is a serial interface protocol that is reliable. I am implementing this so the tuning software never has to assume its command was processed by the ECU. Instead data is sent and received in a stateless fashion using a pre-defined packet format. Optional: Add document to category: Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.