Passive Infrared detectors (5753L) showing 'No Serial #'

Discussion in 'C-Bus Toolkit and C-Gate Software' started by TDB, May 11, 2009.

  1. TDB

    TDB

    Joined:
    Jun 5, 2007
    Messages:
    7
    Likes Received:
    0
    I have recently updated my C_Bus toolkit to 1.10.3 and 2 of my 7 SENPIRIB Motion detectors are showing a Serial Number of 'No serial #' and I am unable to edit these unts.

    When I try to edit the units I get a dialogue box "Attempted to use dialogue with incompatible object"

    Any ideas ?
     
    TDB, May 11, 2009
    #1
  2. TDB

    george

    Joined:
    Jul 26, 2004
    Messages:
    158
    Likes Received:
    1
    Location:
    Adelaide
    Hi,

    You probably have SENPIRIB units with firmware 1.2.66 or older. If this is the case then it is a known problem which has already been addressed in the soon coming new release of Toolkit. Unfortunately, there is no work around so you need to wait a few days...

    Regards,
    George
     
    george, May 11, 2009
    #2
  3. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    have version 1.10.4
    fixes serial issue but the sensors 1.2.66 DO NOT WORK

    UPDATE:
    Was trying a few different versions of the toolkit, i only wish i knew which i used to program the network because i'm having problems with the PIR's Firmware 1.2.66.

    PIR's with Firmware 1.2.67 work perfect.

    Is there a way to update the firmware or would this be a warranty claim?
     
    Last edited by a moderator: May 25, 2009
    ado_civon, May 24, 2009
    #3
  4. TDB

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,396
    Likes Received:
    26
    Location:
    Adelaide, South Australia
    Firmware can't be upgraded.

    Please sit tight if you can. Clipsal are looking into this issue. TK should work with this firmware.
     
    ashleigh, May 25, 2009
    #4
  5. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    sit tight? I'm glad their website says in nice bullet point view;

    Unsupported Devices:
    PIR's with Firmware 1.2.66.

    That would have saved me a Sunday's worth of work :(
     
    ado_civon, May 25, 2009
    #5
  6. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    i want updated PIR's as a warranty replacement !!!!

    i wonder what the difference is between 1.2.66 and 1.2.67
    i bet that if their software checked the firmware it'd be able to upload the new settings to each PIR depending on its firmware and thus eliminating any issues.

    PIR (1.2.66) does not respond to night movement nor day.
    If I link it to D1_1 and a key switch turns D1_1 on, the PIR starts timing out.
    So there is some functionality but the SENSOR part doesn't seem to work.
     
    ado_civon, May 25, 2009
    #6
  7. TDB

    george

    Joined:
    Jul 26, 2004
    Messages:
    158
    Likes Received:
    1
    Location:
    Adelaide
    Hi,

    We tried to reproduce the problem you are having with this 1.2.66 sensor unit but it seems the unit is working as expected. We used Toolkit 1.10.4 when programming it.

    Can you please send us the project that has that problematic 1.2.66 sensor unit on it so we could try saving your programming to our unit and see if we can reproduce the problem?

    You can use this address: [email protected]

    Thank you,
    George
     
    george, May 25, 2009
    #7
  8. TDB

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,396
    Likes Received:
    26
    Location:
    Adelaide, South Australia
    When did you purchase these sensors?

    What is the manufacture date on them?

    Both versions are authorised for production release.

    There is one single change only between the 2 versions, and that change has a minor impact on Learn operation only.

    This is exactly how cbus Toolkit works.
     
    ashleigh, May 25, 2009
    #8
  9. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    are you saying that the toolkit version 1.10.4 should not affect the pir's ability to detect movement at night/day?

    I am not sure what the manufacturing date is, i didn't grab that off the sensor.
     
    ado_civon, May 25, 2009
    #9
  10. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    in regard to George's request for a copy of the project,

    i will try to send you a copy tomorrow, don't have my laptop on me.

    i'm having same issue with two 1.2.66 sensors
     
    ado_civon, May 25, 2009
    #10
  11. TDB

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,396
    Likes Received:
    26
    Location:
    Adelaide, South Australia
    Correct.

    When did you purchase these sensors?
     
    ashleigh, May 25, 2009
    #11
  12. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    the system was installed early last year and has been working but client requested timing to change from 5min to 2min.

    Once i uploaded the new settings, sensors stopped working.
     
    ado_civon, May 25, 2009
    #12
  13. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    i'm curious what the warranty procedure is on this gear?
     
    ado_civon, May 27, 2009
    #13
  14. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    going to put in 1.2.67 replacements for the two 1.2.66 based models.

    Will post results here as well as the warranty procedure & coverage.

    i give up trying different versions of the cbus software, no point as each time you go to a previous version you have to re-create the network project.

    thanks for the help guys see how i go with this.
     
    ado_civon, Jun 3, 2009
    #14
  15. TDB

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,396
    Likes Received:
    26
    Location:
    Adelaide, South Australia
    I have no idea how you came to this conclusion because the project database format has not changed for about 2 years. Rolling back to older versions should be simple and automagical.
     
    ashleigh, Jun 3, 2009
    #15
  16. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    i came to this conclusion by not being able to open a project that was created in version 1.10.4 in version 1.2.x or whatever.

    and to top it up; the older versions / some that i tried did not want to scan the network properly.

    hence the reason i'm giving up :)

    didn't have time to go last night, hopefully Friday night.
     
    ado_civon, Jun 4, 2009
    #16
  17. TDB

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,396
    Likes Received:
    26
    Location:
    Adelaide, South Australia
    Well, version 1.2 is about 4 years old.

    You should be able to roll from version 1.10.4 back to around version 1.8, and possibly 1.7. Thats going back about 2 years.

    As posted before - version 1.2.66 firmware in the PIR's is production approved, still sold, and supported. There is some other fault going on which is not related to the firmware version.
     
    ashleigh, Jun 4, 2009
    #17
  18. TDB

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    update on the system:

    Yeah the version i used was 1.7 and that worked wonderfully.

    Now, about the Firmware, you might be right that it wasn't the cause of my issues.

    I got the system to work again but with very random results.
    An example of the random result is:

    2 PIR's both manually adjusted light sensitivity (that bit works)
    PIR 1: turns on relay1 and dimmer21 on night movement. So the Day-Movement, Sunset and all that are NOT set to anything.

    PIR 2: turns on dimmer1 on night movement, but for this one to work i had to set both Day & Night movement to dimmer1.

    I've used the test tool to detect any burden issues and the system seems ok with that but I am getting these weird results. Also, PIR 2 will NOT work if i set more than one thing for day/night movement, maybe another relay2 or something, just doesn't want to work then.

    Even though the system seems to work "as expected" i had to tweak it in ways that for me doesn't seem right.

    any suggestions?
     
    ado_civon, Jun 9, 2009
    #18
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.