Issue with the way the licences work when the write fails

admin@motiondynamics.com.au

I;ve got a problem. I use the correct file for the bike's ecu.

The connections are all fine, all have been tested multiple times. But the issue is that it gets to 58% writing and then it fails. Then when I go to proogram again, it asks me to aaaply the licence again, and it did this several times before it told me i needed a new licence.

I found i had to reset my machine several times and was forced to buy another license before i could get it to do a complete write. Several restarts and I was forced to buy another license. Thats NOT GOOD ENOUGH.

I had a dataloggger connected the entire time watching the attempted write. There was NO disconnection, but always failed at 58%.

You need to fix this so this stuff doesn't happen. Put a damn dongle on it or something, LOOK at all the failures people are having and you're FORCED to buy an additional license because each time you try and write and it fails it needs a new license.

You have issues with your software guys.

admin@motiondynamics.com.au

It could also be other things too, like I did swap ports on the machine several times trying to get the write to happen on anything i loaded... I updated drivers, and it would throw up an error with no reply from the ecu and says retry, but it could also have been user error too or windows being windows, but it was heavily flagged by bit defender too, though i'm pretty sure i isolated everything and just turned off the advanced threat detection stuff. So not discounting those possibilities either, especially reading through the issues people are having.