Automotive Engine Control Can Bus Tool

The main goal of our project is to create a EEPROM flashing tool that operates via the OBD2 port and our vehicle's CAN-BUS system. This tool MUST be able to communicate through the Vehicle's OBD2 port, read the data from Engine Control Unit (ECU), write back data to the read location, and erase said location. This tool must be PC based, written preferably in C/C++, and connects to the ECU via serial, BUT using a USB->RS232 module. The specific memory location to be read, written to, and erased, at this present moment is unknown. In order to obtain this information, we have purchased a CAN-BUS analyzer from Microchip that will enable us to sniff and obtain communication packets between an already known working product and the ECU. These messages will need to be decoded. The goal here is to obtain the vehicle's primary MAP(information required to allow the vehicle to operate under various conditions) and import it into a PC based program, that will allow us to edit and/or change (tune) parameters that we see fit. Then, we will need to write this new, changes, MAP back to the ECU. However, what is explained above is a future goal to be completed later down the development line. The FIRST program we are looking for is one that simply reads the data and presents it as an HEX file, re-writes/flashes new or existing HEX files, and erases(write 00) the location. Ideally, a HEX editor software with read, write, and erase capabilities that will work with our ECU. For ease, as my partner said, we would like to keep the tools here. What i can do is set up a dedicated server that will allow remote access. This server will have all the necessary attached tools and devices that will be needed, allowing you to have full control over it's devices and programs in order to obtain analyzer logs and/or other diagnostic information. In essence, i can also install any programming IDEs/compilers on our server, thus allowing the entire project to be done from our server. This way it will be easy for us to fix any bugs that may occur, instead of trying to replicate them on a different machine on our end. Ideally, what ever is easier for you, we are willing to accommodate. Preferably keeping our devices and tools here so we can continue to do our own debugging and testing. I hope that this has provided more insight to the project goal and requirements. If you have any more questions please feel free to ask. Thank you,