449/511 communication with ECU

What error code/s do you have?

Have not compared maps other than visual checking of the tables one against the other.

Hi Dangermouse,

Meanwhile I received the list of errors from the Husqvarna importer.
I recently installed a switch to deactivate the light relay (to save battery while riding slowly). It seems that the ECU is monitoring the relay current.
It gave me error P1615, which was unknown to TuneECU.
There were some other errors, which were discribed in TuneECU, but I think they were older...

According Alain, the .hex-files are encrypted, so they could differ by just having a different description.

Can you tell me, if I have to short the switch 12V to the battery 12V while programming a new map?

Anybody played with the "disable secondary butterfly" option in TuneECU?

BR
Florian

Regarding programming, I found on the CCM that the ECU relay was shutting down the ECU when I tried to reprogram it. Connecting pins 4 and 6 together (switched and unswitched +12v) keeps the relay powered up.
Try downloading your maps to a file then reprogram the ECU with the saved map file. If the ECU shuts down at the start of the reprogram process then try connecting pins 4 and 6.
Pin numbers are those of the diagnostics connector.

Definitely need to bridge the power wires as above.
The Husqvarna HST plug does this when connected.
If you loose power during uploaded you can potentially render the ecu dead....

The PID code is a phantom code relating to security systems in some cars.... not related to your headlight.

Someone did turn off the second butterfly motor function.
You would need to remove the butterfly and adjust the idle speed manually.
I've done both of these things but left the stepper motor operating. (the throttle cable end of the second butterfly shaft controls [at least tries to] idle speed.

I have actually done that. My Android phone froze on me, just as I started the reprogramming. I had to remove the battery from the phone to reboot it :-(
After that the ECU had no mapping, I believe that the existing map is wiped prior to installing the new one.
The bike was as dead as the proverbial Dodo.
TuneECU does have a recovery feature, on reconnecting to the ECU TuneECU recognised that there was no mapping and prompted to run a recovery routine. It prompted for a map file to use and then loaded that into the ECU.
All has been fine since.

The recovery feature is good to know

I did this brief overview of an upload using TuneEcu to a 511 ecu.

View: https://youtu.be/gHsbajz-79w

You cannot believe how happy I was when I found that there was one, and that it worked

Oh, I can imagine

I am gathering all of the connectors to use tune ECU. I hope to use it to set my TPS and idle. I already have map3 in my CPU and have still been experiencing surging while cruising. Has anyone experimented with customizing their map to eliminate this problem on a TE?

I received all of my cables and adapters to connect TuneECU to my bike, but I'm having trouble getting it to connect. I connect the ELM 327 to my phone and make sure it connects by USB. Then I plug the adapter into my diagnostic port and click ECU-connect. Intermittent lights flash on the ELM and the red indicator in TuneECU, but it never turns green or connects. I've double checked the pinouts for the AMP connector and OBD2 adapter. Any suggestions? Do I need to download drivers for the ELM 327 to my phone?

The first time it can take a long, long time. I believe that the Husky may also need a flick of the starter button to power up the ECU?
Hopefully Dangermouse may be along shortly to confirm. .

I've left it connected long enough to get a message to restart the ECU and try again. The #4 and 6 pins are jumped to keep the ECU on. I've tried bumping the starter before connecting and I've tried bumping the starter after the message. It's a little frustrating. So close........

Keep going...
The first time it does take a long time. I saw that nessage pop up a few times before it connects. There seems to be a lot going on unseen which fortunately gets stored in cache for the next time.
A great update to the app would be the ability to tell it what it is connecting to, avoiding a few layers of interrogation.

I'm still trying to connect. I've watched the blinking lights on the elm327 and blinking red indicator in the app for over 40 minutes before the app froze on my Samsung S4 phone. I ain't no quitter. I just emailed TuneECU tech support. Just waiting for a reply.

Sorry for not checking in for a while.

It may be the Elm adapter if it's a copy type unit rather than a genuine ELM unit.
I had trouble myself with a cheap eBay obd unit.
Ended up buying the Lonelec unit and connected straight away.

Most issues connecting seem to be cable related. Now that TuneECU is Amdroid only there is also the fiddliness of the micro-USB to bear in mind. I wentbthrough 3 micro-USB OTG connectors before I found one that worked with any reliability.

I had 'great fun' on my new phone on the switch to USB C.
The phone wanted to connect via Bluetooth and had to be 'forced' to connect via cable in the phone settings menu.

I received a new OBD2 adapter from OBD Innovations this week. It connected to my phone and ECU quickly with no fuss. I have read and saved map3, then made a copy to experiment with. Hopefully, I will be able to figure out where the surging lives on the map and smooth it out. Any suggestions are appreciated. I haven't found any threads or videos on modifying TuneECU android maps for Husky, yet. Only connecting, importing, and exporting maps.