- Cheap Software, Buy Quality Automobiles & Motorcycles Directly from China Suppliers:IMMO Universal Decoding 4.5 2017+EDC17/MED17/MEV17 EEPROM Checksum Calculator.
- The IMMOFF17 program works with eeprom of any size (32Kb, 64Kb, 128Kb). Correctly disables the immobilizer in the firmware, without affecting the data and encoding. Works without access to the Internet. It has no limits for processing dumps. OtoCheck Immo Tool v2.0 IMMO Cleaner Software Immo Killer 1.10 Software Disable IMMO Funciton.
The Why: I need to make a custom EEPROM programming software, so when I change the EEPROM values I need the checksum to be calculated. Right now, I am simulating this in MS-Excel by importing a.eep file, parsing it, and seeing if I can come up with the same checksum the compiler did.
A professional portable application designed to repair electronics.
The application is an advanced calculator for repairing electronic counters and car drivers (ECU).
NeoX is an application that offers maximum flexibility and comfort while maintaining ease of use.
A constantly growing database of solutions.
The huge number of satisfied customers shows that NEOX is the best among the available calculators.
Possibilities:
• millage repair and VIN Editor with auto CRC Aurix
PSA MD1CS003 - MERCEDES MD1CP001 - RENAULT MD1CS006 - AUDI MD1CP004 - VW MG1CS011
• millage repair with automatic checksum calculation in eeprom SID 208 Citroen Jumper, Peugeot Boxer, Fiat Ducato
• millage repair with automatic checksum calculation in eeprom SIMOS 18.1 VAG group
• Auto CRC - eeprom checksum correction Cranchi Zaffiro 36, Caterpillar model C32, Mercury Varado, Volvo Penta D6
• ECU DATABASE EEPROM + FLASH
• millage repair with automatic checksum calculation in eeprom DCM6.1 FORD
• millage repair with automatic checksum calculation in eeprom SID310 Mercedes, Renault, Nissan, Dacia
• millage repair with automatic checksum calculation in eeprom DCM3.7 Kia, Hyundai
• programming and editing in EDC17, MED17, MEV17 with CRC
• programming and editing of electronic counters
• programming and editing of tractors
• programming and editing in agricultural and combines
• programming and editing of forklift trucks
• programming and editing in construction machines
• repairing electronic counters (if data in the dashboard is corrupted)
• repairing and programming AIRBAG modules
• PIN code - reading from car's ECU (CIM, BSI, UCH, etc.)
• programming and editing on motorcycles, scooters, and quads
• reading, programming and changing code in the radio
Buying NeoX you get:
- access to the online program
- license valid for 1 year
Checksum Calculator Online
- all updates on the day of purchase
- a valid license for one stand (PC)
- 30 free tokens every month
- functional technical support in the user panel
- loyalty program
The tokens you can use for the database and technical support in the user panel in the software.
If a solution is not in the program, you can always use the support panel and send this file to be done, paying for it with tokens.
Support panel for extra files - starting price of tokens:
ADBLUE OFF - 80 tokens
AIRBAG - 10 tokens
BURBLES - 80 tokens
CRC EDC17 - 10 tokens
CRC SID208/305/307/309 - 10 tokens
CRC SID310 - 20 tokens
DPF OFF - 30 tokens
DPF+EGR OFF - 50 tokens
DTC OFF - 15 tokens
EGR OFF - 30 tokens
FLAPS OFF - 30 tokens
HOT START - 30 tokens
IMMO CLONE OTHER - 20 tokens
IMMO CLONE VAG - 20 tokens
MILAGE DASHBOARD - 10 tokens
MILAGE ECU - 10 tokens
MILAGE ECU SID208 - 40 tokens
MOD-TUNNING - 60 tokens
NOX-02 SENSOR - 30 tokens
POPCORN - 80 tokens
>>>SUPPORTED MODELS LIST<<<
Hardware requirements: computer with minimum Windows7 64bit
IMPORTANT
Edc17 2fmed17 Eeprom Checksum Calculator Software 3
After purchase, the license is activated within 24 business hours. The same applies to transfer the license to another computer.
The ability to transfer the license to other PC, laptop - 2 times for the duration of the license for free.
After using the limit, please contact the sales department to transfer the license.
The cost of transferring the license is 60 € each time if the limit is used.
Edc17/med17 Eeprom Checksum Calculator Software Download
Edc17 2fmed17 Eeprom Checksum Calculator Software 1
Information about the change of law in Poland as of 25/05/2019
Please be advised that on 25/05/2019, the amendment to the Road Traffic Act and the Penal Code Act will come into force. Please read the full text of the Act (http://orka.sejm.gov.pl/proc8.nsf/ustawy/2878_u.htm).
The Act of March 15, 2019 amending the Act - Road Traffic Law and the Penal Code
„Art. 306a.
§ 1. Who changes the indication of the odometer of a motor vehicle or interferes in the correctness of its measurement is subject to imprisonment from 3 months to 5 years.
§ 2. The same penalty shall apply to anyone who commits another person to perform an act referred to in § 1.”
In addition, we would like to remind the content of our regulations (Terms & Conditions) that should be accepted when placing the order:
§12 Legal issues and liability.
Improper use of the Neo8 program may violate the laws of the country.
The seller, distributor, and manufacturer are not responsible for improper or illegal use of the Neo8 software.
It is forbidden to use the Neo8 program for illegal acts, in particular, to blur the vehicle's proper odometer indication. The part of the software used to set new kilometer value is used only to repair the correct indication of the vehicle’s odometer.
Online Checksum Calculator Hex
CVAVR C Compiler (generates *.eep EEPROM files)
-----------------------------------------------------------
I am having great difficulty calculating the EEPROM checksum. I am assuming this is Intel Hex Format. Am I right?
If so, basically you add the 20 bytes before the checksum (16b data, 2b address, 1b record length, 1b record type). Then you do a modulus 256d. Then subtract this from 256d. Right?
Anyone help here?
The Why: I need to make a custom EEPROM programming software, so when I change the EEPROM values I need the checksum to be calculated. Right now, I am simulating this in MS-Excel by importing a *.eep file, parsing it, and seeing if I can come up with the same checksum the compiler did.
All the checksums of line addresses greater than 256 are off by 1 (why?) and all the checksums of line addresses equal to 0 are just completely wrong.