Tweet
@Mmmm1987: Hi again - you do indeed appear to have moved forward considerably - well done!!
As to the error in the hex42 module - here is a more readable form of the long-code string from your scan report:
I've highlighted Byte 02, Bit 0 which is currently set (as shown). This software switch tells the door module that the door-lock does NOT have a SAFELOCK motor. Australian cars have SAFELOCK - so try setting the switch status to zero (the value of Byte 02 should be 12 after the change is made).
Then clear the error and re-scan - does the fault re-appear?
If so, keep the change above and notice that Byte 06 , Bit 2 (highlighted) is set. The Bits in Byte 06 select different datasets for the window regulator motor. Try selecting a different dataset - I suggest change Bit 2 =0 and set Bit 1=1 (the value of Byte 06 should be 02 after the changes are made)
Then clear the error and re-scan - does the fault reappear?
Don
PS: as to your question about the word limit - the better way to post scan data in these forums is to use what's called "CODE Tags". In HTML speak, Tag-commands are always bounded by square brackets and having opened a Tag-command, the tag is then closed by the operator "/" followed by the same Tag-command! Don't worry if this is confusing - hopefully this procedure will become clearer in the next paragraph.
So, to use CODE Tags, start by typing [CODE], then paste your data - then type [/CODE] . I've used this exact method for pasting the long-code data above - so that's the effect of the CODE Tags (notice the vertical & horizontal sliders that allow lots of embedded information within a post - nifty!!
)
PPS: regarding the errors in your hex55 module- I don't believe that this is a lamp-out problem. The error descriptor says that you have a Basic Setting fault which is a kind-of calibration issue. Look under Basic Settings in OBD11 software after you select the module.
As to the error in the hex42 module - here is a more readable form of the long-code string from your scan report:
Code:
[B][COLOR=#0000cd]<-----------------BITS------------->[/COLOR] [COLOR=#0000cd]Byte HEX 7 6 5 4 3 2 1 0[/COLOR][/B] 00 00 0 0 0 0 0 0 0 0 01 3A 0 0 1 1 1 0 1 0 [B]02[/B] 13 0 0 0 1 0 0 1 [SIZE=3][COLOR=#0000ff][B] 1[/B][/COLOR][/SIZE] 03 20 0 0 1 0 0 0 0 0 04 80 1 0 0 0 0 0 0 0 05 01 0 0 0 0 0 0 0 1 [B]06[/B] 04 0 0 0 0 0 [B][COLOR=#0000FF]1[/COLOR][/B] 0 0 07 00 0 0 0 0 0 0 0 0 08 00 0 0 0 0 0 0 0 0 09 00 0 0 0 0 0 0 0 0 10 10 0 0 0 1 0 0 0 0 11 00 0 0 0 0 0 0 0 0
Then clear the error and re-scan - does the fault re-appear?
If so, keep the change above and notice that Byte 06 , Bit 2 (highlighted) is set. The Bits in Byte 06 select different datasets for the window regulator motor. Try selecting a different dataset - I suggest change Bit 2 =0 and set Bit 1=1 (the value of Byte 06 should be 02 after the changes are made)
Then clear the error and re-scan - does the fault reappear?
Don
PS: as to your question about the word limit - the better way to post scan data in these forums is to use what's called "CODE Tags". In HTML speak, Tag-commands are always bounded by square brackets and having opened a Tag-command, the tag is then closed by the operator "/" followed by the same Tag-command! Don't worry if this is confusing - hopefully this procedure will become clearer in the next paragraph.
So, to use CODE Tags, start by typing [CODE], then paste your data - then type [/CODE] . I've used this exact method for pasting the long-code data above - so that's the effect of the CODE Tags (notice the vertical & horizontal sliders that allow lots of embedded information within a post - nifty!!
)PPS: regarding the errors in your hex55 module- I don't believe that this is a lamp-out problem. The error descriptor says that you have a Basic Setting fault which is a kind-of calibration issue. Look under Basic Settings in OBD11 software after you select the module.
Comment