5502CDGP230 not reading DALI Groups

Discussion in 'C-Bus Wired Hardware' started by Diggerz, May 19, 2025.

  1. Diggerz

    Diggerz

    Joined:
    Jan 24, 2017
    Messages:
    95
    Likes Received:
    13
    Location:
    Australia, Vic, Melbourne
    Anyone else experienced issues with the 5500CDGP230 not reading DALI Groups from drivers after a full scan?

    After commissiong DALI networks and assigning Groups with RAPIX im finding the 5502CDGP230 will not retrieve all the groups previously asigned to the drivers and as a result will not switch the groups via the c-bus group address mappings. It grabs a couple here and there, but not all of them.

    Switching back to rapix and they all show up correctly and switch correctly.

    Updated software to 2.9.0 and updated the firmware from 1.8.0 to 1.10.0 on the gateways but same result. Manually re-assigning the groups on the gateway resolves but its a pain.

    The 5500DAL2 never skipped a beat.
     
    Diggerz, May 19, 2025
    #1
  2. Diggerz

    Weedo

    Joined:
    Mar 21, 2011
    Messages:
    40
    Likes Received:
    3
    Location:
    Toowoomba
    Hi Diggerz,

    I've had my share of bugs with the new Dali gateway however this is a new one.
    My previous issues were the Dali device could be scanned and assigned to a group address, it would then work for a few days after which the lights would just stop working. The fittings would then need to be reset and recompiled to get them responsive again. The 1.7.0 release seemed to resolve the issue as I haven't had this issue again.

    Potentially dumb question but good to establish a baseline, does broadcast control the fittings ok?
    Are you able to complete a Full Scan? I have often found quick scans will show the fittings but a full scan will identify errors.

    Something to note is, when completing a full gateway scan items on both networks, A & B, are integrated. Rather frustrating to find that out as I was thinking it only looked at the line you have selected in the tree. Its worth disconnecting the wiring to the network you aren't working on when debugging to isolate potential conflicts.

    Rapix is much more robust in error handling so it will often mask wiring issues.


    Weedo
     
    Weedo, May 20, 2025
    #2
  3. Diggerz

    Diggerz

    Joined:
    Jan 24, 2017
    Messages:
    95
    Likes Received:
    13
    Location:
    Australia, Vic, Melbourne
    Fairly confident i was perfroming a full scan, in version 2.9.0 the quick scan is tucked away under the arrow.

    is the "line view" meant to be a live representation of the Dali network? it didnt seem to marry up with what rapix was showing. Rapix was showing all the groups, and was able to switch them all correctly. C-bus commission collected the group information for at best maybe 10 fittings.

    In another instance we had a universe that was overloaded with more that 64 fittings, so had the electrical contractor remove some fittings, after which Rapix was showing 55 fittings but the comisisoning software, after a new scan, was still showing 64 in the "line view", it wasnt until i clicked "discover faults" that some of the fittings in the "line view" showed as missing and i had to manually delete them from the "line view" window. I would have thought these should simply not show up in the "line view" as they were no longer physically connected, rather than displaying phantom address's, if its supposed to show the live dali network and the "devices in project" is the mapped/modeled network? if this isnt the case then there really needs to be a way to show the live network to understand whats physically there.

    If i didnt have rapix to show me that there were now 55 fittings and not 64 i probably would have been lead up the garden path thinking the line still had over 64 fittings connected!

    upload_2025-5-21_14-21-45.png
     
    Last edited: May 21, 2025
    Diggerz, May 21, 2025
    #3
  4. Diggerz

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,417
    Likes Received:
    34
    Location:
    Adelaide, South Australia
    Hi Diggerz

    DALI can be prone to ringing on the DALI line, which messes up DALI comms - at least for some systems. That is, devices that send commands into DALI (knows as Application Controllers) have differing levels of tolerance to DALI line ringing.

    The ringing is a physical product of the line length, topology, and type of transceiver used. There's not a lot can be done to design it out.

    RAPIX people do sell a DALI damper that will squash the ringing.

    ** this may or may not solve the problem - you may after all have a firmware defect you are dealing with **

    Disclaimer: I have a fair bit to do with RAPIX.
     
    ashleigh, May 25, 2025
    #4
  5. Diggerz

    Diggerz

    Joined:
    Jan 24, 2017
    Messages:
    95
    Likes Received:
    13
    Location:
    Australia, Vic, Melbourne
    Thanks Ashleigh,


    Rapix was working fine and snappy as always, no problems there. It scanned all drivers and assigned / controlled all groups without a hiccup.

    I'll be sticking to the old 5500DAL2 gateway unless there is an inherent need for DALI2 support or until the new software workflow matures to be just as quick and painless.

    The workflow commissioning on site using Rapix and the old 5500DAL2 feels significantly smoother and faster at this point in time and there is the added benefit of being able to work on both DALI and c-bus commissioning simultaneously, having both Rapix and toolkit open at the same time..
     
    Last edited: May 25, 2025
    Diggerz, May 25, 2025
    #5
  6. Diggerz

    Weedo

    Joined:
    Mar 21, 2011
    Messages:
    40
    Likes Received:
    3
    Location:
    Toowoomba
    @ashleigh is there a way to roll back the firmware to V1.8.0?
    I have had better success in general when using this version and I know it improved my issues that were present with 1.7.0. Seems like maybe V1.10.0 has reintroduced some bugs to the controller.

    @Diggerz I feel your pain, however there is some benefits to the new controller that cant be overlooked i.e much better dimming profiles that remove the lag between long press and dimming that the old gateway had. Emergency lighting is in there but i doubt many of us are using that function for the types of integrations we are looking at.

    If you can roll back to 1.8.0 I think that's a better starting point. I think generally the front end electronics for the rapix programmer is just better filtered so it compensates much more for line issues. I havent heard of these anti-ringing devices before, might need to just give one a try.


    Weedo
     
    Weedo, May 29, 2025
    #6
  7. Diggerz

    oracle

    Joined:
    Jan 18, 2010
    Messages:
    117
    Likes Received:
    10
    Location:
    NSW
    Are you sure, sounds like an understatement MWAHAHAHAHA!
     
    oracle, May 29, 2025
    #7
  8. Diggerz

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,458
    Likes Received:
    77
    Location:
    Adelaide
    One of the traps with the 5502CDGP230 when using a tool other than SLCC to make changes on DALI is that once the gateway has read the settings from a given address/device on the DALI line.. it doesn't read them from DALI again.

    It makes the assumption that if you deployed the settings with SLCC then the gateway knows what in the device, or if you extracted the settings from the device on DALI because it was already programmed, that it won't have changed again (basically, it wasn't intended to be used with other commissioning tools*).

    So, when you do a full gateway scan
    • it will pick up any new addresses/devices on the DALI line and load these into the gateway
    • it will read the settings for the known devices from the gateway, but it doesn't actually refresh these from the device on the DALI line

    In a similar way, when it discovers a device at an address on the line, that address is reserved. If you read configuration in to the device at that address... then that configuration is preserved in the gateway until you tell it to remove it... it doesn't just delete that address/device from the gateway if if doesn't appear in a subsequent scan.. it will just show as missing (as you found).

    At present (as of SLCC 2.10.0) the only way to refresh the settings in a device from the line is to delete it from the network view and then rescan to read it back. There is an update coming to address this, but I'm not sure which SLCC release it is targeted for (firmware support is there in 1.11.0 but the software work is still underway).

    Nick

    *I'm not going to get into any discussions about whether that was a good idea or not, I'm just stating the current situation
     
    NickD, May 29, 2025
    #8
  9. Diggerz

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,417
    Likes Received:
    34
    Location:
    Adelaide, South Australia
    Gateways are funny old beasts.

    Discussions about the merits of them is probably fruitless.

    Gateways to other systems have notable quirks as well - and in some cases those render the use of RAPIX tools completely null and void.

    My personal view is that gateway vendors should design tools to suit the multi-master universe and tolerate other commissioning processes. Mainly because, on site, the initial addressing setup can be done by sparks and then handed over to an SI. This avoids the SI doing low-value work. Sparks can use whatever tool they like: the one from =S=, something KNX, RAPIX, Tridonic - whatever they have and are comfortable with.

    Unfortunately, not all gateway vendors have the same view.

    If the updated =S= gateway allows such a workflow (after future update) then everyone is a winner.

    @Weedo : Sorry, I'm unaware of how to flip firmware versions up and down.
     
    ashleigh, May 31, 2025
    #9
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.