ColorMFA

Тема для обсуждения возможных неисправностей и заводского брака.
онлайн-консультация. куда смотреть, если что-то не работает.
как отремонтировать и стоит ли это делать самостоятельно.

- Как зайти в режим прошивки после неудачного обновления.

Сегодня обратил внимание в темное время суток - под шкалой скорости мигает синий светодиод, если это важная информация. А так монитор постоянно светится с надписью BootLoader v3.1

В общем быстрого решения проблемы нет. Отписал тебе в ЛС.

Moved from REQUEST FOR NEW FEATURES / Предложения по новым функциям:

Bug Reports:

• Currently set cruise control speed does not adhere to the offset the speedometer follows.
• Distance traveled screen is not reset with Trip Data 1 or Trip Data 2? It's been consistently off or maybe I'm doing something wrong?

Nitpicks:

• Fuel consumption doesn't really make sense when displaying both mi/gal and gal/hr, perhaps change it to fuel economy?
• This may not be fixable but radio info is extremely slow to update. Feels like 5-10 seconds.

Currently set cruise control speed does not adhere to the offset the speedometer follows.

Cruise speed does not match display speed on screen or speedometer arrow ?

Distance traveled screen is not reset with Trip Data 1 or Trip Data 2? It's been consistently off or maybe I'm doing something wrong?

Distance traveled screen below the speedometer ? ColorMFA does not reset cluster trip data. As before it need reset manually.

This may not be fixable but radio info is extremely slow to update. Feels like 5-10 seconds.

What car ? In what cluster ColorMFA installed (FullFIS, HalfFIS, w.o.FIS) ?

autopilot писал(а): ↑

23 окт 2018, 22:58

Currently set cruise control speed does not adhere to the offset the speedometer follows.

Cruise speed does not match display speed on screen or speedometer arrow?

Both even when driving uphill.

Current Speed = 70MPH
Cruise <set>, shows 68MPH

Current Speed = 80MPH
Cruise <set>, shows 78MPH

autopilot писал(а): ↑

23 окт 2018, 22:58

Distance traveled screen is not reset with Trip Data 1 or Trip Data 2? It's been consistently off or maybe I'm doing something wrong?

Distance traveled screen below the speedometer? ColorMFA does not reset cluster trip data. As before it need reset manually.

Will take additional pictures in the morning to show the difference.

autopilot писал(а): ↑

23 окт 2018, 22:58

This may not be fixable but radio info is extremely slow to update. Feels like 5-10 seconds.

What car ? In what cluster ColorMFA installed (FullFIS, HalfFIS, w.o.FIS) ?

B5.5 (3BG) Passat HalfFIS

I found exactly the same (passat B5, immo2, half fis) ! Cruise speed on ColorMFA exactlly 100km/h (Garmin GPS also shows 100km/h), current speed on ColorMFA 102 or 103 km/h.
I also found about 3 % higher traveled distance shown on ColorMFA then in original cluster km counter display.
Does gear ratio settings in ColorMFA affect traveled distance shown ?

It is small difference and I think there are alwayas some tolerances. I am not really bother about it but is interesting...

Может здесь получу ответ...
Столкнулся с такой проблемой, после выключения зажигания на час и более(иногда и раньше) происходит сброс всех настроек. И каждый раз приходиться, всё настраивать заново. В чём может быть причина?
P.S. При этом каких либо других сбоев в работе устройства не наблюдается.

rcmaehl писал(а): ↑

24 окт 2018, 07:16

autopilot писал(а): ↑

23 окт 2018, 22:58

Currently set cruise control speed does not adhere to the offset the speedometer follows.

Cruise speed does not match display speed on screen or speedometer arrow?

Both even when driving uphill.

Current Speed = 70MPH
Cruise <set>, shows 68MPH

Current Speed = 80MPH
Cruise <set>, shows 78MPH

I can observe the same thing, but when changing the speed source to ASR/ESP (I don't if you can change it also), the values ​​on the colorMFA are equal, but speedometer arrow shows higher value (like Dashboard cource is set to Dashboard) .

Buy the way, use ColorMFA also the differnt scource to calulate the traveled distance ?

About cruise and speed:
1. Need set right speed source in ColorMFA setings. Different motor ECU use different speed source for cruise (if it present in car). Possible 2 source of speed: - sensor in gearbox (used through cluster) and sensors in wheels (used through ESP). If your car not have ESP (only ABS present), always used cluster as source of speed.
2. Dashboard needle is always show bigger value then real speed. This is world practice.
3. In old ECU tolerance of cruise speed is +-2-3 km/h. Is normal if set 80, but real speed from 78 to 82.
4. On next firmware added settings to correct speed displayed on screen. It's not fix differences beetwen cruise speed and displayed current speed. But you may correct displayed speed and set it to real speed.

Gear ratio settings does not affect to displayed speed or traveled distance calculation. Used only for show current gear.

ColorMFA used speed to calculate traveled distance. The more accurately the speed source works, the more accurately it counts.

B5.5 (3BG) Passat HalfFIS

Yes. Is possible. In VW/Skoda with HalfFIS or w.o.FIS possible to slow update audio info on some audio devices. May be it fixed in one of the following updates.

Hi All,

I also noticed the same "bugs" like sg1 and rcmaehl.

First bug is related with current speed on colormfa and cruise-speed similar like rcmaehl - for me is like this: colormfa show 80km/h but cruise-speed is set to 78km/h. I do not pay attention to arrow because this is obvious that in older cars arrow was always higher for "safety" reasons.
Note: I'm using default set up sensor from ASR/ESP. When using sensor from dashboard, speed on colormfa changing like crazy between +- 3-7km/h difference. ESP sensor is most steady.

Second thing is similar like sg1 describe. Traveled/trip distance on colormfa is higher then original trip distance on dashboard. Moreover the colormfa "service reminder" also not match.
I made a test: I stopped the car and I cleared all 3 counters (colormfa travel/trip distance, colormfa service reminder, and original dashboard trip counter) and I drive 76,8 km. Results are: colormfa travel/trip dist was: 79km, colormfa service reminder had traveled 78km, original dashboard trip was: 76,8km.
I have done several such tests and the more kilometers I travel, the greater the difference between these results are. This is strange

My car: Golf IV 2003 TDI AXR with 1C0 comfort module, immo3 half-fis

autopilot already in part answered for my problems but I decided to describe them.

I'm also repeatedly check ColorMFA trip and dashboard trip.
In car where it tested it work fine.
There may be discrepancies, but not more than 5 km per 1000 km. A48E, speed from ESP, wheel radius is original.

I'm understand about this problem and check all again in VW cars.
But have one question: Who said that the data in the dashboard is correct ?

autopilot писал(а): ↑

25 окт 2018, 15:42

But have one question: Who said that the data in the dashboard is correct ?

Ha! And the answer is... Volkswagen Of course I'm kidding


Like I wrote before, I made a few tests..take a look on photos from 1 - 6. You can notice a difference. Very weird is that service reminder count on his own the distance.. It should match colormfa distance.. Don't You think?

Another issue is that I'm still getting error on newest firmware when I'm trying check (up or down) measure blocks on ABS - photos ABS1 - 2.

And the last bug (so far ) - sometimes I receive "navi" info but I don't have navigation radio This happens only when I turn-off radio - photos navi1 - 2. This is CD/MP3 radio from Skoda. I tried even turn off "navigation" option in hidden menu but still the same.

Like I wrote before, I made a few tests..take a look on photos from 1 - 6. You can notice a difference. Very weird is that service reminder count on his own the distance.. It should match colormfa distance.. Don't You think?

About service reminder: yes, calculation is changed in one of the firmware, but not tested. Bug is fixed (in next firmware). Thanks.
About distance traveled: what differences between speed displayed on screen and speed in cluster ? If differences is big, calculation of traveled distance is also have big differences.

And the last bug (so far ) - sometimes I receive "navi" info but I don't have navigation radio This happens only when I turn-off radio

Hm.. Is possible if radio show something like "VW RADIO SYSTEM" to full screen. ColorMFA thread this as navi data (all data what send from audio devices to show on full screen thread as navi data). May be your radio also show anything to full screen or is the ColorMFA bug, but it need check via logs or/and with original FullFIS.

Another issue is that I'm still getting error on newest firmware when I'm trying check (up or down) measure blocks on ABS

I'm check this.

autopilot писал(а): ↑

25 окт 2018, 01:38

.
4. On next firmware added settings to correct speed displayed on screen. It's not fix differences beetwen cruise speed and displayed current speed. But you may correct displayed speed and set it to real speed.

Gear ratio settings does not affect to displayed speed or traveled distance calculation. Used only for show current gear.

ColorMFA used speed to calculate traveled distance. The more accurately the speed source works, the more accurately it counts.

Thats exactly what i want to propose. If a correction with adjustable coeficient (like fuel consumption) will be implemented in firmware i can put in 0.97 and both the speed and traveled distance will be corrected.
I notice even before i have ColorMFA that cruise control have at least 2 km/h speed tolerance and i really dont bother about that.

About traveled distance in original display in VW passat cluster - it is inside 1% tolerances if compared to Garmin GPS. I compared this on more occasions including 500 km long trips.
I think it is more then adequate and hard be better because variations of tyre pressure and wear could easy means 1 cm diference in wheel diameter.

Now we are waiting for new fw. I hope you also saw my improved translation to include in it. It is in Immo 2 open doors display thread.

About traveled distance in original display

It was a joke... I think that in VAG they did everything quite accurately. As much as possible. Under the original wheels.

I hope you also saw my improved translation to include in it. It is in Immo 2 open doors display thread.

Yes. Thanks. I have already made changes.

autopilot писал(а): ↑

26 окт 2018, 04:15

About service reminder: yes, calculation is changed in one of the firmware, but not tested. Bug is fixed (in next firmware). Thanks.

Sounds great! Waiting for new fw then

autopilot писал(а): ↑

26 окт 2018, 04:15

About distance traveled: what differences between speed displayed on screen and speed in cluster ? If differences is big, calculation of traveled distance is also have big differences.

Tonight I'm on the road again, so I'll check this out.
But we dont have to pay attention to "arrow" speed, because we can correct/set the "arrow" as we want/need
So I will change colormfa speed sensor to "dashboard" (in this mode, speed is taking from eeprom values, right?) and then I will verify what is the diffrence between GPS speed and "cruise-speed".

Or tell me what tests You need and I will do them for You..

autopilot писал(а): ↑

26 окт 2018, 04:15

Hm.. Is possible if radio show something like "VW RADIO SYSTEM" to full screen. ColorMFA thread this as navi data (all data what send from audio devices to show on full screen thread as navi data). May be your radio also show anything to full screen or is the ColorMFA bug, but it need check via logs or/and with original FullFIS.

Well, this is "one din" (one shelf) radio . The same like here: https://www.drive2.ru/l/7853249/
It not sending any "welcome" or "goodbye" message to FIS/colormfa (radio display data is connected directly to 1C0 comfort module via CAN L/H). This issue (navi info) happens sometimes (not all the time) and only when i turn-off radio. It never appeared when I turning-on the radio.

If You need any logs - please provide me information what logs You need and how to save/retrieve them.. and I will do this.

Other thing is it would be a good idea if there was a option in colormfa that completely disables "navigation" function. This option could resolved this issue I think.

autopilot писал(а): ↑

26 окт 2018, 04:15

Another issue is that I'm still getting error on newest firmware when I'm trying check (up or down) measure blocks on ABS

I'm check this.

Great, thank You.


BTW - I don't want to litter up this thread, so if You want I can create new topic with this issues

autopilot писал(а): ↑

26 окт 2018, 04:15

About distance traveled: what differences between speed displayed on screen and speed in cluster ?

Tonight I'm on the road again, so I'll check this out.

I recorded two videos with speed differences on every speed source. "Arrow" set to 120km/h, cruise control 111km/h. Please take a look and see results,

'Dashboard' speed source:



'ASR/ESP' speed source:

Fine. ABS/ESP is a "true" speed for your car.
Dashboard.... may need a do more smooth signal. Currently there is no additional handling for speed from the dashboard.
About cruise I wrote before. Is a +-2-3 km/h on this cars.

autopilot писал(а): ↑

29 окт 2018, 00:55

Fine. ABS/ESP is a "true" speed for your car.

Yup! Agree with that

autopilot писал(а): ↑

29 окт 2018, 00:55

About cruise I wrote before. Is a +-2-3 km/h on this cars.

Roger that!


autopilot - thanks for this answers.


What about differences between dashboard trip and colormfa trip in my case?
I noticed in your photo from Audi car, that trip distance in dashboard and in colormfa match beautifully.
Any chances for resolving this issue in VW cars?

And what about "navi" issue in my case - do You want any logs? I want to note that even if this "navi" sign shows up on my colormfa - still I don't have option in settings for disabling navigation as the instruction on the page 6 says (Menu>Settings>Navigation).

Regards,

What about differences between dashboard trip and colormfa trip in my case?

I'll try to fix it. But not yet guaranteed.

And what about "navi" issue in my case

Will be fixed in the next firmware.