//tunedaddy_
// faq_
// why do edited maps get rejected_

the nanocom checks the final two bytes of the .map. they must equal a byte-sum of the file. we recompute that checksum after applying the proven overlay.

// can flashing brick the ecu_

yes. writing the map erases and rewrites ecu memory. interruption, unstable voltage, a connection problem, incorrect operation or faulty equipment can leave the ecu and vehicle unusable. a compatible upload, checksum-valid output, original-map backup and saved injector codes reduce risk but do not remove it. use a proper stable power supply and follow the official nanocom guide.

// will it smoke_

the available tune is conservative. smoke control is changed modestly, but vehicle condition, boost leaks, sensors, injectors, and driving style still matter.

// do injector codes change_

injector codes live in ecu eeprom, not in the map file. save them before flashing and verify them afterwards.

// what if my map isn't compatible_

you are not charged. upload it first and we will tell you whether we can help before you choose a tune or pay.

// do i need a nanocom_

you need access to a nanocom evolution to read and write the map, but it does not need to be yours. A borrowed or workshop unit can work when its td5 map function is enabled. See the nanocom page for details.

// refunds and road use_

refund wording is on refunds. our tune files are supplied only for off-road, motorsport and closed-course use where lawful. they are not produced, tested, approved or certified for public-road use. lawful use, emissions, roadworthiness, approvals and insurance are your responsibility. see the terms.

support: support@tunedaddy.com.au · guides · faq · terms · privacy · refunds