Carly, be aware..

D

Ducklakeview

Elite
 Merseyside
Ok, after a lot of delving into the software in my car, and I mean down to actual code levels... It appears that when Carly "codes" modules, it actually doesn't.. It rewrites the software on the module to software from another module that has the required features. Yes, it works BUT it's flagged up as a checksum error by (genuine) ista, AND also changes the module software date. This causes problems with subsequent reprogramming and updating using bmw (ista) software as it generates a mismatch between vin and software date/version.

This may not cause a problem for a lot of people, but it's something to be aware of, especially if you use Carly to code cars less than 3 years old, so therefore still in warranty.

I found this out after a LOT of digging and reading code. Turns out Carly had actually changed the firmware of the footwell module in my e70 to that of a 2010 car when I used it to code a few things. This then caused a problem as ista expected a 2012 module after cross referencing the vin. Ended up having to reflash the middle to get it to communicate with ista..

Just a heads up..

Mike.
 
This is interesting. I've found, which could be related, that sometimes carly forgets some of my coding? For example I'm sure it's now forgotton to self lock at 5mph. No idea why, I'll have to decode it and then re-code it.

Not a huge overall problem IMO (back to thread topic), it's just nice if Carly did the coding... then it should be done properly!
 
Very interesting, and I'm not doubting you've found some concerning issues with the way Carly writes changes, but I'm puzzled as to how it can actually change the FW version of a module? Are you saying it writes the entire module instead of changing just the feature/item/code itself? Seems a very drastic way to make what are usually only minor changes. Unfortunately I don't have ISTA so can't check my modules. Before using Carly I used NCS (Dummies) to program, I wonder if that would show up any version mismatches?
 
enzed4 said:
Very interesting, and I'm not doubting you've found some concerning issues with the way Carly writes changes, but I'm puzzled as to how it can actually change the FW version of a module? Are you saying it writes the entire module instead of changing just the feature/item/code itself? Seems a very drastic way to make what are usually only minor changes. Unfortunately I don't have ISTA so can't check my modules. Before using Carly I used NCS (Dummies) to program, I wonder if that would show up any version mismatches?
Click to expand...

NCS will show up a mismatch as an error when reading the module, THAT'S how I initially discovered the problem..

Mike
 
Ducklakeview said:
enzed4 said:
Very interesting, and I'm not doubting you've found some concerning issues with the way Carly writes changes, but I'm puzzled as to how it can actually change the FW version of a module? Are you saying it writes the entire module instead of changing just the feature/item/code itself? Seems a very drastic way to make what are usually only minor changes. Unfortunately I don't have ISTA so can't check my modules. Before using Carly I used NCS (Dummies) to program, I wonder if that would show up any version mismatches?
Click to expand...

NCS will show up a mismatch as an error when reading the module, THAT'S how I initially discovered the problem..

Mike
Click to expand...
I'll have to fire it up (NCS) and see what it shows.
Cheers.
 
And blow the layer of dust off it? Judging by your coment? :lol:
Last time I did that with an old laptop the board fried part way through boot up... oh well! Hopefully yours goes much better!

Be interesting to see if more people can see/view the mis-match now that we know it can happen?
 
Just so we dont start another misconception Carly cannot and does not have the abiltity to overwrite or upload new firmware, what it does is makes updates to what ever firmware is installed to a perticular module. Just happened to be somthing I was looking into a while ago.
 
I don't see how it can rewrite firmware for some of the coding - it impleies that bmw somehow release software with options disabled -

On my Mini for example it has artificial engine sounds (an increasingly popular (?) feature). You cannot turn it off in the car - and BMW/Mini deny it can be turned off without disconnecting the unit / speaker.

Yet Carly can do it (thankfully - it was giving me headaches)...
 
gannet said:
I don't see how it can rewrite firmware for some of the coding - it impleies that bmw somehow release software with options disabled -

On my Mini for example it has artificial engine sounds (an increasingly popular (?) feature). You cannot turn it off in the car - and BMW/Mini deny it can be turned off without disconnecting the unit / speaker.

Yet Carly can do it (thankfully - it was giving me headaches)...
Click to expand...

That's exactly what they do, when you purchase a BMW new you can choose what function you want (some additional cost)

Mad I know.
 
Joycey said:
gannet said:
I don't see how it can rewrite firmware for some of the coding - it impleies that bmw somehow release software with options disabled -

On my Mini for example it has artificial engine sounds (an increasingly popular (?) feature). You cannot turn it off in the car - and BMW/Mini deny it can be turned off without disconnecting the unit / speaker.

Yet Carly can do it (thankfully - it was giving me headaches)...
Click to expand...

That's exactly what they do, when you purchase a BMW new you can choose what function you want (some additional cost)

Mad I know.
Click to expand...
the active sound is not amongst those options...
 
gannet said:
Joycey said:
gannet said:
I don't see how it can rewrite firmware for some of the coding - it impleies that bmw somehow release software with options disabled -

On my Mini for example it has artificial engine sounds (an increasingly popular (?) feature). You cannot turn it off in the car - and BMW/Mini deny it can be turned off without disconnecting the unit / speaker.

Yet Carly can do it (thankfully - it was giving me headaches)...
Click to expand...

That's exactly what they do, when you purchase a BMW new you can choose what function you want (some additional cost)

Mad I know.
Click to expand...
the active sound is not amongst those options...
Click to expand...

I was referring to options that can be turnt on or off from from factory.
 
I have seen it happen with my own eyes on the FRM module in my E70.

Firmware version was changed and date altered from 2013 to 2011 after programming with Carly, the module also became FRM2 when it had been FRM3. This then generated an error in NCS as the module version didn't match the VIN. Ended up having to flash the module back to the correct firmware and date, after which all was fine.

I use NCS and ISTA/P and D pretty much daily so am familiar with how they work. Spoke to my software guy, who is an absolute genius when it comes to BMW software and retrofits etc, he said he sees it regularly when Carly has been used, particularly on FRM modules.

Mike
 
You must log in or register to reply here.
Back
Top Bottom