MickeySw
Established Member
Happy days, did you get charged to do these updates?On the plus side, these updates in conjunction with the Charger update previously have allowed me to charge successfully at Tesla Superchargers
Happy days, did you get charged to do these updates?On the plus side, these updates in conjunction with the Charger update previously have allowed me to charge successfully at Tesla Superchargers
I booked them as part of my service (it was expensive at £180, but included this specific update).Happy days, did you get charged to do these updates?
Sounds about right.I booked them as part of my service (it was expensive at £180, but included this specific update).
Dang.just had the following updated by the dealer: BMS, EVCC, VCU. Unfortunately it seems that carscanner cannot read any of these ECUs, as there is no change at all in any of the components that it shows; the output is identical before and after the change.
I have pro but no connection to the car........ however I seem to remember the cost to upgrade to Pro was tiny.Dang.
Are there any CarScanner Pro users on here? If so, perhaps you could request an update that included these critical ECUs. Indicate to them that this is a capability that is sorely needed.
I might still pay for CanScanner Pro and see if something can be modified. That would likely be the best way, f...
Dang.
Are there any CarScanner Pro users on here? If so, perhaps you could request an update that included these critical ECUs. Indicate to them that this is a capability that is sorely needed.
I don't suppose that eZS works well enough to be used for this on the MG5? Even if it gets a few ECU addresses wrong, I can actually produce a patched version, IF I know the correct addresses. I can even guide a reasonably tech savvy user on how to get these addresses if needed. Unfortunately, the result is an Android-specific file that has to be loaded specially. But that's a once-off pain.
If time pressure eases off soon, I might still pay for CanScanner Pro and see if something can be modified. That would likely be the best way, for those that want to know the status of their firmware. It may even help speed up the firmware updating, since in some (perhaps many?) cases it may turn out that only 1 or 2 of the three firmwares actually needs updating.
I submitted a request in the app using "Contact Developer".I use CarScanner Pro. What exactly should I ask for and how?
I’d try eZS but it’s not compatible with my old android phone I’m afraid…I don't suppose that eZS works well enough to be used for this on the MG5? Even if it gets a few ECU addresses wrong, I can actually produce a patched version, IF I know the correct addresses. I can even guide a reasonably tech savvy user on how to get these addresses if needed. Unfortunately, the result is an Android-specific file that has to be loaded specially. But that's a once-off pain.
This is what I got from CarScanner. I'm not sure if it is very useful to anyone but its from my MG5 that has had an update done that fixed the Tesla problem:
That seemed a bit expensive for something that I wasn't desperate for so I tried this for £8 https://www.amazon.co.uk/dp/B07CP632CL?psc=1&ref=ppx_yo2ov_dt_b_product_details. Unsurprisingly it didn't work so I returned it and tried this one https://www.amazon.co.uk/dp/B0CJC1R5JD?ref=ppx_yo2ov_dt_b_product_details&th=1 for £12.50 and it works just fine. (I figured that if it has Bluetooth 5.0 it is probably a more recent chipset)This works on my PFL:
I thought it had but I think it must have disappeared when I was doing the cut/paste to post it here. I'll have another scan tomorrow and update the results.Did carscanner not read the "Charger" module? I'd be interested in whether yours has S005R4 or S005R5 after the update.
Got it working using an old android tablet and OBDLink LX. Had to download an apk version to overcome county coding.I’d try eZS but it’s not compatible with my old android phone I’m afraid…
I've just re-run the scan and edited the post. S005R4Did carscanner not read the "Charger" module? I'd be interested in whether yours has S005R4 or S005R5 after the update.
That just confirms what we suspected so far, the charger FW version isn’t the determining factor, any chance you try eZS and get the versions as per post #32?I've just re-run the scan and edited the post. S005R4
Does anyone know the coding used for "Programming date (HEX): 1123784001" My update was done early afternoon on 8th Jan.
I've just tried but eZS doesn't seem to connect properly. It shows a percentage dial that increases but then says "No car" and starts again. Does it know about a FL MG5?That just confirms what we suspected so far, the charger FW version isn’t the determining factor, any chance you try eZS and get the versions as per post #32?
It looks to me that the dates are decimal, not hex. I think they're trying to say it's encoded, not human readable.Does anyone know the coding used for "Programming date (HEX): 1123784001" My update was done early afternoon on 8th Jan.
time.struct_time(tm_year=2005, tm_mon=8, tm_mday=11, tm_hour=18, tm_min=13, tm_sec=21, tm_wday=3, tm_yday=223, tm_isdst=0)>> import time
>> time.gmtime(1123784001)
What version?I've just tried but eZS doesn't seem to connect properly.
Thanks for the research. Seems like there's nothing useful we can see.It looks to me that the dates are decimal, not hex. I think they're trying to say it's encoded, not human readable.
From Python:
time.struct_time(tm_year=2005, tm_mon=8, tm_mday=11, tm_hour=18, tm_min=13, tm_sec=21, tm_wday=3, tm_yday=223, tm_isdst=0)
So that's year 2005, 11th August. Could that be when the firmware was first written? More likely, there is a different epoch involved (Python seems to use the Unix 1970/Jan/01 epoch).
"Programming" time may not be when the firmware was updated; it could be when the firmware was written, or compiled, or indeed when updated to the ECU, or perhaps other interpretations.
A quick Google search didn't bring up anything hopeful.