Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: Chimes with ignition?

  1. #11
    Join Date
    May 2003
    Location
    On The Road
    Posts
    30,031
    Total Downloaded
    0
    so, it looks like the d2a's do and the early's dont?
    "How long since you've visited The Good Oil?"

    '93 V8 Rossi
    '97 to '07. sold.
    '01 V8 D2
    '06 to 10. written off.
    '03 4.6 V8 HSE D2a with Tornado ECM
    '10 to '21
    '16.5 RRS SDV8
    '21 to Infinity and Beyond!


    1988 Isuzu Bus. V10 15L NA Diesel
    Home is where you park it..

    [IMG][/IMG]

  2. #12
    Join Date
    Sep 2009
    Location
    Brisbane
    Posts
    1,317
    Total Downloaded
    0

    Normal or Not?

    After reading this thread the other day, I had the 3 amigos still remaining at startup (had not cleared from SLABS or left the ignition off for long enough). I let all the other dash warning lights go out and then started it. 3 chimes. Have to agree that they aren't there when the other dash warning lights are going through their check, but definitely still chime when either the ABS is working properly or not.

  3. #13
    Join Date
    Jan 2010
    Location
    Oslo
    Posts
    82
    Total Downloaded
    0
    It is correct that the early D2 do not chime and later ones do. There was a global recall on the SLABS ECU and mine got replaced with the later version - after which the chimes began... The reason for the recall and moreover the solution is typical, to say the least... LR found out that during the manufacturing process of the hubs, some metal particles would remain inside the hub and later-on give false ABS sensor readings causing the ABS or TC to kick-in when not required or worse: ABS or TC not working when they were supposed to work. The later SLABS ECU was made more pulse-tolerant. In a better world they would have increased QA on the hub manufacturing process, but no, firmware does the trick - sort of. So each time you hear the chimes you know: LR QA s**ks...

  4. #14
    Join Date
    May 2008
    Location
    Camp Hill, Brisbane
    Posts
    218
    Total Downloaded
    0
    Thanks to all for the discussions.
    I have access to laptop now and find the seat belt warning in the BCU set to TIMED. If I change it to any of the other options (BUCKLED, FASTENED or IGNITION2) the chimes are continuous. Shouldn't there be a DISABLE option? Even shorting what I assume is the seat belt switch socket under the driver's seat doesn't shut it up.
    Nanocom 2.05, software 2.05a
    (PS Mods - if this thread is going a bit toward the electronic diagnostics, feel free to migrate)
    Cheers,
    Steve

  5. #15
    Join Date
    Jul 2008
    Location
    UK
    Posts
    677
    Total Downloaded
    0
    This is "one" of the errors in the mk1 Nanocom.

    The options should be,
    Timed
    Buckled
    Ignition
    Disabled.

    I could turn it on and off in my friends 2 D2's, but could not do it on mine, well I did manage it once but it was a continual "bing bing" and would not go off, I managed to disable it by selecting Timed again.......... but a friend did it with a Hawkeye first time. Mine is on Timed for both light and warning sound.

    Does "timed" make it continuous or does it go off after 6 secs ?

    @Dutchviking.........

    The later SLABS unfortunately tho dont have the ability to disable the TC (with the CDL) like the earlier ones do, as its programmed to ignore it / work with it (as in D2a's) this is offcourse if you want to do that. Just mentioning thats all.

  6. #16
    Join Date
    May 2008
    Location
    Camp Hill, Brisbane
    Posts
    218
    Total Downloaded
    0
    Quote Originally Posted by Urban Panzer View Post
    This is "one" of the errors in the mk1 Nanocom.

    The options should be,
    Timed
    Buckled
    Ignition
    Disabled.
    I now have the TIMED option and chimes & warning lamp cease after 6 seconds.There is no DISABLED setting, rather a FASTENED setting which just gives continuous chimes. This TIMED state took hours to revert to after having flashing headlamps, NO starter, engine running for 2 seconds then stopping, ACE warning lamp on (I have no ACE fitted!)
    Nanocom seems to be erratic in writing to the BCU even though it says "successfully written". Reading back written settings have random errors, particularly in the A/C, SLS, transmission and other related settings. It's a dangerous tool in any hands I'm thinking.
    Now wondering why I can't just hardwire the seat belt switch to active and have the chimes go away!

    Steve

  7. #17
    Join Date
    Dec 2007
    Location
    Cambewarra, NSW
    Posts
    517
    Total Downloaded
    0
    I've found that when writing BCU settings with the nanocom that reversion to some "default" settings does occur sometimes.
    I always:
    Read the settings and record them all.
    Make the changes and write the settings.
    Read the settings to check them all.
    It would appear that occasionally communication with the BCU is interrupted during the write process.

  8. #18
    Join Date
    Jan 2010
    Location
    Oslo
    Posts
    82
    Total Downloaded
    0
    Thanks for the comment on DIFF Lock Urban Panzer!

    I find the BBS MSV2 far better than nanocom - but quality comes at a cost. All in all nanocom is a great tool for what it does. But the BBS MSV2 GUI really is 100% better than the nanocom one.

Page 2 of 2 FirstFirst 12

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search AULRO.com ONLY!
Search All the Web!