Ecu tuning simulator4/30/2024 Today a package arrived which contained the cut-off plugs from a 5AM Ducati. ![]() The last weeks - temperature has risen above 0☌ - were mostly spent in the workshop servicing the fleet and driving, so work with the ECU simulator has been stopped. The overview below is showing the CANBus data between an 5AM loaded with a Guzzi-BIN and the Guzzi dashboard. I wouldn't see the neccessity of using a text string as a heartbeat, and it's one of the IDs which is sent at a low frequency - every 100ms. There's lots of data moving on the CANBus. And take a look at what's happening on the CANBus as well.Īnd a special thanks to Robert and his support in getting the dashboard. Then the XDF describing the addresses and contents of the data can be validated. The next step will be to connect the dashboard to the ECU simulator and check if the virtual engine can now be started. And now the EEPROM could be programmed as well.Īnother quick check was made to verify if the algorithm (found for the Guzzi dashboards) for calculating the check sum protecting the mileage and other values in the EEPROM also worked with the Aprilia firmware. Another cable was added and connected to ground. So, a quick study of the EEPROM datasheet and some thinking led to the assumption, that maybe the Aprilia dashboard made use of the Write Protect pin. ![]() Alas, programming didn't work, the software gave an error message. The next step was to program the EEPROM with a Usercode and the transponder keys fitting to the ignition key used. Then a connection to the programmer and the EEPROM content could be read. The EEPROM was quickly identified and cables soldered to the SDA/SCL pins. The stepper motor stepped and the LEDs lit up. The complete dissassembly is much easier than that of the Guzzi dashboard. I knew that the mechanical condition wasn't mint, but as long as the electronics work all would be well. Some weeks ago a Aprilia fan from Poland, Robert, approached me and offered to assist in getting a Mana dashboard. The results are enhanced XDFs for the One- and Two-Lambda Guzzis (Breva, Stelvio, Norge, Griso and 1200 Sport) and the transcription of arrays, scalars and flags into a XDF for the Mana. Since the virtual engine couldn't be started, assumedly because of the missing dashboard, the last months were spent with analysing the ECU program code and running tests with Guzzi BINs. Some time since the last post, but not due to lack of interest or work. Just to be on the safe side I also ordered a clone of the Salea 8ch/25Mhz signal analyzer.ītw, I am still looking for a dashboard and TCU to complete the setup. ![]() Some research brought to light that the Rigol DS1054Z can be used as a signal analyzer with Sigrok, a splendid open source project. I plan to look a bit deeper into the stuff happening on the CAN bus, maybe this error can be eliminated also. The areas suspected to be tables are later on verified on the ECU simulator by changing values in the tables and tracking the results, if any can be seen.Įven though the dashboard is recognized by the ECU and speed, rpm, side stand LED and so on are functioning, I still get an CAN bus error with a Mana BIN loaded. As the program code used in the Mana BIN is likely to be similar to the one in Guzzi BINs, searching for the data and structure of identified tables will help me finding them in the Mana BIN. Using Tunerpro and a Hexeditor the BIN is looked at Byte by Byte, looking for tables and the content. As, with a Mana BIN loaded, the virtual engine still can't be started I'm using the existing 5AM XDF for Guzzis. This might seem superfluous, but chasing values in tables and the legend values in the maps requires a very precise setting, as the program code uses bilinear interpolation to calculate values in between breakpoints.Ĭonnecting a stepper motor eliminated the respective errors shown by the ECU. Most important is the cascaded TPS poti, which allows setting TPS by exactly 1/10 of a degree. This is neat, as the meaning of the bit changes in 0x14 (# of service resets) and 0x15 (C°/F, km/mls, service) could be determined now. The algorithm for the checksum calculation of the mileage and the other Bytes in the range 0x10-0x18 was also reverse engineered, based on the sequential data written into the EEPROM when adding one km at a time. Only a couple of percent of the 2KB in the EEPROM are used. The addresses and contents of the dashboard are now known, I don't expect any further content to appear.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |