Multiecuscan

this version does not end proxy alignment on abs and sometimes also on engine ecu tested on 2 different giulia. with version 4.7 everything works

I have informed MES Support of your report.

no I only reported here

Got same error with one stelvio 2020 and one giulia 2017. So timeout error in abs unit when running proxi. Downgraded to version 4.6 and worked fine. How is this possible, you have this kind of serious error in latest released version..?

Also sos (Emergency call) unit fails in 2020+ giulia and stelvio when running proxi. It's new unit in newer models. Hope you get support for that unit in near future cos otherwise odo is not going to stop blinking.

I know Yani is aware of the ABS Proxi issue as I immediately pointed him to this post.

For the SOS unit error I suggest you send MES an Email and use the Send Report function.

I have the 4.7R1 and I have a Giulia 2017.
I enabled, 2 days ago, the ACC+ (adaptive cruise control), while also disabling the basic cruise control, did the alignment and all went absolutely fine.
Had obviously to replace the steering wheel button sets and also to do the procedure of the ABS "Lateral and longitudinal accelerator sensor calibration" (with steering put at 0 degree angle). And now I've ACC+ fully working.

A month ago I activated the auto-high beams, did the alignment: again all fine. All with a ODBLink SX (the cable based one, as the bluetooth one has problems with proxy alignment!)

I didn't experience any problem of any sort...

Are you sure you are using a good USB adapter and not a bluetooth one? Are you sure your cable adapters are ok? I personally built mines as the ones I've found on Amazon were messed up (checked each pin of those with my multimeter).

Same bug, GIulia 2020, stelvio 2019.
@s130, do you know when will be fixed?

All I know is that I have made Yani aware.

I am not party to or informed about anything to do with MES development and fix cycles.

If your issue is the same as the original poster's then you can try V4.6 like he did.

I'm sorry I can not be of more help.

I just ran into this bug last night and had to revert to 4.6.

Got this to.