Unpredictable Annuciation

Discussion in 'Multi-Room Audio (MRA) and MARPA' started by tidefan, Feb 1, 2011.

  1. tidefan

    tidefan

    Joined:
    Jan 6, 2009
    Messages:
    45
    Likes Received:
    0
    Location:
    Alabama
    Looking for an answer as to what might be causing the unpredictable annuciation of an audio source for one particular zone. All is working well throughout the home which includes lighting control, touchscreens, and 3 matrix switchers with multiple zones of audio, etc.. We have a NEO DLT keypad with a button programmed to toggle between audio sources in the "Gameroom" (local, analog 1(home theater), and Tuner 1. This DLT kepad works as programmed. However, one of the audio sources (Home Theater) for this zone is being triggered by various other inputs throughout the home. Example, when a keypad is pressed to turn on a lighting load in another room, then the audio source for the "Gameroom" zone annunciates "Home Theater" for no reason? A review of the programming of the amp, marpa file, and cbus files reveals nothing. All addresses are assigned correctly it appears. Not having this issue with any other audio zone locations or audio sources. The Audio Application was used for all audio group addresses and all lighting group addresses are under the Lighting Application. Any suggestions how to troubleshoot?
     
    tidefan, Feb 1, 2011
    #1
  2. tidefan

    Newman

    Joined:
    Aug 3, 2004
    Messages:
    2,203
    Likes Received:
    0
    Location:
    Adelaide, South Australia
    The very first step is to use the Diagnostic Utility to look at the C-Bus network traffic when the misbehaviour occurs. This can be quite revealing as it can point to which unit is sending the message causing the unintended behaviour to occur.
     
    Newman, Feb 1, 2011
    #2
  3. tidefan

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,427
    Likes Received:
    64
    Location:
    Adelaide
    If you're saying that you've programming key units to use the Audio Application ($CD, or 205), then I would start by changing this to something different.

    The Audio Application is not intended for "user" configuration - it is only used by the C-Bus Multi Room Audio devices to communicate between themselves. If you have key units generating commands on this application then all sorts of strange things could happen.

    I realise this seems to go against the recommended practice of segregating function by Application address, but this practice only applies within the Lighting Address range.

    Failing that, Newman's suggestion of observing the bus traffic that causes the incorrect annunciations should shed some light.

    Nick
     
    NickD, Feb 1, 2011
    #3
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
There are no similar threads yet.
Loading...