Multiecuscan

maunu wrote:Log file of 159 remote closing windows.
I'm not sure if the log is correct so if more info needed please let me know and I will try to make better log file.

You need to have this section inside log file:
"Reading CAN configuration data ...
CAN CONFIGURATION DATA:
05 72 9F DB 05 72 9F DB 00 00 08 00 00 00 08 00 00 00 00 00
05 72 9F DB 00 22 05 09 05 72 9F DB 00 22 05 09 00 22 05 09
32 31 31 34 30 30 30 36 31 36 31 4F 55 54 50 55 54 2D 4A 49 54 20 06 07 10 DB 9F 72 05 09 05 22 00 C3 65 00 07 B7 00 14 10 00 06 B4 06 01 00 00 06 08 00 00 42 50 67 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 42 00 02 00 00 00 00 00 00 00"

To do this there is necesary to go into Body\Can Setup PROXI but you do not need to execute the procedure

Ok I will do that.

After changing this on my car my windows will now only go up and inch at a time. I have to press the buttons over and over to get the windows to go up. The drivers side windows previously went up by itself but the passenger side one never has. I guess this is a saftey feature?

I was hoping to get the windows closing with the remote using this.

Anyway I can restore my windows to their previously automatic state?

Thanks for the great software, hope we can get this fixed

P.S.
I've tried resetting the windows by powering them down, holding down for 10-15 second, then powering them up (means pressing the button 20-30 times) and holding the up butting down for 10-15 seconds. But no luck.

I'm just leaving the battery unplugged for 20 minutes to see if that resets anything....

- return to normal action , must be reprogram eeprom 24LC02 BI.
- or use good procedure of proxy alignment.

http://img10.imageshack.us/i/windowsantytrapsensor.jpg/

Changing the trap sensor to "not present" fixed the issue. there were also errors that the passenger side sensor didn't exist. That must have been causing it to go into "limp mode".

So where/how do I fit a passenger side pinch sensor?!

- eprom 24C02 configuration for went up by itself

• 07 AA C6 18 18 20 06 11 23 51 72 35 43 AA A0 50
  50 45 41 43 45 45 45 53 49 82 80 7D 00 40 FF FF
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  04 00 C7 50 80 6B 00 3F 04 00 C7 50 80 6B 00 3F
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  48 00 C6 00 80 00 00 40 00 00 00 00 00 00 00 00
  48 00 C6 80 80 00 00 40 FF FF FF FF FF FF FF FF
  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00 CC

- hm, if y program 24c02 with solution from alfa 147 2003 y controler ?

Now I did get better data. Proxi alligment procedure had to be done. I didn't find any way to just read CAN configuration data.

- and now it 's working.
- add emulator to anti-trap sensor socket.
- a big problem for use 147 is not working Proxy alignment in FES, must go to ALFA service for examiner.

--
http://img714.imageshack.us/i/czujnikpoprawny.jpg/
--
http://img204.imageshack.us/i/czujniktylny.jpg/
--

bubu321 wrote:- a big problem for use 147 is not working Proxy alignment in FES, must go to ALFA service for examiner.

It will be working in next release. I already have success with this problem.

bubu321 wrote:- and now it 's working.
- add emulator to anti-trap sensor socket.
--

Congratulations! Nice work.

Could you tell me what you did to emulate the anti-trap sensor and where I would find the socket? Currently both of my sensor voltages report 5v so I'm guess this isn't reporting correctly?

Thanks for your help!