CNI 2 Issue

Discussion in 'C-Bus Wired Hardware' started by abg, Nov 6, 2026 at 6:17 AM.

  1. abg

    abg

    Joined:
    Dec 25, 2007
    Messages:
    209
    Likes Received:
    2
    Location:
    Sydney
    Hi and thanks in advance for any feedback....

    I have a 5500CN2 (CNI Mk 2, DIN rail) that seems to reset its C-Bus side by itself every day or two.

    Setup
    • CNI2: C-Bus firmware 5.5.00, Ethernet firmware 1.2.0, unit address 1, network voltage 27.3 V
    • C-Gate 2.11.6 (build 3271) on Linux, one client connection to the CNI on port 10001 (nothing else connects to it)
    • Network 254 with about 95 units, plus a bridged network 253 behind it
    Symptom

    C-Gate stops receiving any bus traffic (no unit events, no measurement broadcasts), but commands still reach the bus and C-Gate's polls are answered. No send retries. The TCP connection stays up the whole time, and the CNI2 web page still shows the client connected for more than 24 hours. Seen 30 Oct, 2 Nov, 3 Nov and twice on 5 Nov, at different times of day and with nothing in particular on the bus beforehand.

    What the C-Gate event log (level 9) shows
    • Each episode starts with a burst of ~ characters arriving from the CNI, for example response: ~~~~~~~\03FD09E4... processed by network.
    • After that, the CNI's replies come back in short form (8220015D accepted as short form by command: @1A2001 instead of 86010100822001D5).
    • Interface options #1 (param 0x30) read 0x11 instead of the 0x55 C-Gate normally sees, so MONITOR is off.
    • It stays that way until C-Gate rewrites the options: either at its hourly background sync ("synchronising PCIs", where it reads 0x11 and writes A3 30 ...), or when C-Gate is restarted. Traffic comes back immediately after that.
    So it looks as if the PCI part of the CNI2 resets to its power-up options while the Ethernet side carries on.

    As a workaround I now watch C-Gate's log for the ~ burst and run net sync 254 fast, which rewrites the options quickly.

    Questions
    1. Is this a known CNI2 problem? Is there newer C-Bus or Ethernet firmware than 5.5.00 / 1.2.0 that fixes it?
    2. Could something on the bus side (noise, a voltage dip) reset the PCI part like this, or does it point to a failing unit or power supply?
    3. Is there a way to make 0x55 the power-up option (param 0x41?) so a reset doesn't switch MONITOR off?

    I’m still on C-Gate 2.11.6 because HomeGate 4.12 runs through it and I believe C-Gate 3 is not compatible? I don’t think it matters here, since the CNI itself changes its options, but would C-Gate 3 handle this differently?

    Any advice appreciated - thank you.
     
    abg, Nov 6, 2026 at 6:17 AM
    #1
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.