C-Bus Send Error More Info

Discussion in 'C-Bus Toolkit and C-Gate Software' started by Cameron, Sep 7, 2006.

  1. Cameron

    Cameron

    Joined:
    Aug 3, 2004
    Messages:
    6
    Likes Received:
    0
    Location:
    Adelaide
    I am getting a communications error with CGate as follows:
    20060903-195737 827 //SEACOMBE/254 cb3befe0-8ddc-1027-9b69-917f11dd69c2 C-Bus Send Error: (#)(retrying)

    Is this a failure talking to a particular group (ie. 254) that does not exist or is it only related to voltage, burden etc as I picked up off another posting?

    Is there any other information in the error that can point me to the source of the problem?

    Communications is from PICED. If it is related to a particular group that I am trying to find the status on but does not exist, is there en easy way of searching for it in the PICED software.
     
    Cameron, Sep 7, 2006
    #1
  2. Cameron

    Darren Senior Member

    Joined:
    Jul 29, 2004
    Messages:
    2,361
    Likes Received:
    0
    Location:
    Adelaide, South Australia
    The # means that C-Gate did not receive an acknowledgement. The 254 is the network, not the group.

    Likely causes include :
    1. Communications problems (burdens, voltages, noise etc)
    2. No devices on the Application you are using, hence no acknowledgements
    3. If the message is going to a remote network, then maybe the bridge is missing

    Use the C-Bus diagnostic software to look at the messages and use the Traffic Analyser function to look for communications problems.
     
    Darren, Sep 7, 2006
    #2
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.