I did clean the LOG it with Notepad++ then copy the HEX values in HXD... so it can be done in Win too.. or Phyton script.... there are many options today
DGAlexandru wrote: ↑12 Jan 2020, 21:14
I did clean the LOG it with Notepad++ then copy the HEX values in HXD... so it can be done in Win too.. or Phyton script.... there are many options today
Yeah so I am beginning to see, I wish I had started to study code when I was younger lol. You guys amaze me_
The VBF files are stored as resource in the MondeElmLoader.exe file. So you need to open the exe with a Resource Editor and save the firmwares with it.
Can I ask which resource editor to use as the one I have does not shown the resource data
The VBF files are stored as resource in the MondeElmLoader.exe file. So you need to open the exe with a Resource Editor and save the firmwares with it.
Can I ask which resource editor to use as the one I have does not shown the resource data
You can simply use dnSpye disassambler to extract resource also.
Another easy way to obtain the modified firmware is to use the MondeoElmTester program which will read the content of the firmware from the IPC and stores all the CAN messages int the log file. With a simple bash script you can regenerate the whole firmware from the CAN messages....
Based on m0rtal's tester program I also created my little program to read/write the vbs files and now there is the IPC Updater tool developed here on the forum which can also read the firmware from any Convers+ IPC
i no nothin
Last edited by Stevebe on 20 Jan 2020, 22:23, edited 5 times in total.