madelgado said:
Since all byte are repeated three times, I would not leave the module with two of them modified and not the third... I think that if you put three different values in the three bytes, it will give a configuration error. If two of them are the same, it will assume that configuration.
For 1J0 modules it works more or less the same, but it is not repeated one after the other, but 6 bytes later, this way:
04283 conf_byte0 conf_byte1 conf_byte2 conf_byte3 conf_byte4 conf_byte5
04289 conf_byte0 conf_byte1 conf_byte2 conf_byte3 conf_byte4 conf_byte5
04295 conf_byte0 conf_byte1 conf_byte2 conf_byte3 conf_byte4 conf_byte5
I have seen some configurations posted where there are only 2 bytes modified for the roll-up windows mod... My personal experience says that it should be three; As I say in my first paragraph, it will still work changing only two (4283 and 4289, for instance) but the module will not be fully redundant, so less resistant to any interferience that may alter one bit.
About the auto-roll-up, Mr. szkvw... do the windows roll-up right after a normal door close, or do u have to press a bit longer the close button? I ask because the second option (press longer than normal) would be ideal... otherwise I could never leave the windows open... if you want to share the conf byte and bit number... otherwise it will take to me some time to test this week-end and I will post-it on monday. BTW, I bought a couple of folding mirrors (waiting to come). I will investigate what is the difference between the normal power window motor and folding-enabled PWM... I suspect that it will be small difference ;-) so I suspect that normal PWM is adaptable to FE (folding-enabled) PWM... Anyone tried something like this? TIA!
Once that the FEPWM is working, I will look for the bit to fold/unfold when the car closes/opens.
Hi, I will correct this post (myself), because there is a small error... most of it is still valid, but not the start address of the sequence. This was possible because I got some 1J0 CCMs from Ray (many thanks!), so that I could compare and realize about my mistake.
The way it is:
04280 conf_byte0 conf_byte1 conf_byte2 conf_byte3 conf_byte4 conf_byte5
04286 conf_byte0 conf_byte1 conf_byte2 conf_byte3 conf_byte4 conf_byte5
04292 conf_byte0 conf_byte1 conf_byte2 conf_byte3 conf_byte4 conf_byte5
Another thing that I've realized is about similarities between 1J0 and 1C0 CCMs. The main difference is the distribution of replicated bytes...
To simplify, we can say that for a 1J0 CCM, the master configuration bytes are:
4280 - conf0
4281 - conf1
4282 - conf2
4283 - conf3
4284 - conf4
4285 - conf5
and for a 1C0 CCM, master conf bytes are:
4352 - conf0
4355 - conf1
4358 - conf2
4361 - conf3
4364 - conf4
4367 - conf5
Well, a common evidence is that the power windows mod is done for 1J0 on address 4283 (conf_byte3) and for 1C0 CCMs, is done at address 4361 (conf_byte3). In both cases, the functionality is activated by substracting 8, which is equivalent to set to 0 the same byte.
About the alarm horn and interior monitoring mod, it is done at address 4285 for a 1J0 CCM and at address 4367 for a 1C0 CCM, and also same bytes and values... isn't it curious? I think that everything that is done for a 1C0 CCM can be implemented on a 1J0 CCM.
Last week end I did not have time to try all combinations and find the f*** bit to enable the one touch roll-up, although I will found some other interesting bits that I will post as soon as I document the address/value pairs. Some of them explain why the trunk opens or why variants have different coding/wiring for the trunk.
I keep on working on this. Merry Christmas and Happy New Year!!!