SyncUpdate in logs

Discussion in 'C-Bus Toolkit and C-Gate Software' started by more-solutions, Apr 8, 2014.

  1. more-solutions

    more-solutions

    Joined:
    Apr 23, 2006
    Messages:
    283
    Likes Received:
    4
    Location:
    Peterborough, UK
    I'm looking at Level 9 logs trying to determine why a specific group address came on, as I don't think anything should have triggered it.

    The only events I can see in the log that address it are these:
    Code:
    20140408-121611 738 //PROJ/7/56/28 fa203180-a133-1031-a9f5-c700820b1ba3 SyncUpdate: level=255
20140408-121616 738 //PROJ/7/56/28 fa203180-a133-1031-a9f5-c700820b1ba3 SyncUpdate: level=0
    What does this tell me, and what else should I look at in the logs to see why this group address (28) came on briefly?

    It's associated with a fire alarm and triggers a whole load of lights to get latched on so it's quite important I find the cause!
     
    more-solutions, Apr 8, 2014
    #1
  2. more-solutions

    daniel C-Busser Moderator

    Joined:
    Jul 26, 2004
    Messages:
    770
    Likes Received:
    21
    Location:
    Adelaide
    For basic info on SyncUpdate: http://www.cbusforums.com/forums/showthread.php?t=11847

    SyncUpdate messages are produced by:

    1) During "units" stage of sync when retrieving area address and/or target levels from units.
    3) During "app" stage at end of sync (Status Report on Lighting app)

    Only the surrounding log can tell for sure which of these it is, and which units were being queried at the time.
     
    daniel, Apr 9, 2014
    #2
  3. more-solutions

    more-solutions

    Joined:
    Apr 23, 2006
    Messages:
    283
    Likes Received:
    4
    Location:
    Peterborough, UK
    I've sent you the relevant logs but I'd really like to understand which bits to look at to interpret this myself (assuming it's not some massive trade secret!).
     
    more-solutions, Apr 9, 2014
    #3
  4. more-solutions

    daniel C-Busser Moderator

    Joined:
    Jul 26, 2004
    Messages:
    770
    Likes Received:
    21
    Location:
    Adelaide
    Hi there, had a look through the logs you sent.

    Network 7 has 35 RELDN12 units (a mix of fw versions 1.1.23, 1.1.28, 1.1.44, 1.2.18, all very old firmwares but not necessarily an issue). Just about all of them (except 2) have Group 28 (0x1C) as the first Logic Group. C-Gate was syncing all these units one by one, and Unit 37 (0x25) returned FF as the level for this Group. The next Unit (0x27) returned 00 again. As a result C-Gate modelled this Group as being on for a 5 second period.

    To learn more you could investigate:
    - is there anything notable in the Logic configuration for Unit 37? Is it possible the input DID trigger?
    - were the lights latched on within C-Bus (other units/logic saw this group come on) or by software that was listening to C-Gate's events?
     
    daniel, Apr 11, 2014
    #4
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.
Similar Threads

  1. Exporting Application logs

  2. Capturing C-Gate Logs

  3. CNI get an orphaned unit message in c-gate logs

  4. What is a SyncUpdate event ?

Loading...