DDBC320-DALI Ethernet Connectivity

The DDBC320-DALI v3 controller has an Ethernet port that can be used in several ways, including as a replacement for the PDEG as an access point or translation gateway. This gateway functionality adds many new opportunities, but also some constraints that are outlined below.

It is important to understand the DDBC320-DALI’s Ethernet capabilities and limitations if you plan to use it in place of a dedicated Ethernet gateway in your project.

Please read this page carefully before moving on to DDBC320-DALI Ethernet Configuration.

Differences Between DDBC320-DALI and PDEG/PDEB

Since the PDEG and PDEB are dedicated Ethernet gateways, they can allocate all their resources to bridge functionality, whereas the DDBC320-DALI has some limitations as it also manages DALI communication on its outputs:

  • The DDBC320-DALI supports secure TCP communication with the PDDEG-S. The PDEG and PDEB only support unsecure communication.

  • The PDEG timeclock enables deployment of schedules from System Manager that are stored and triggered locally on the device. The DDBC320-DALI and PDEB do not include this feature.

  • The PDEG has a microSD card to support a 27-day rolling log. The DDBC320-DALI and PDEB do not have include this feature.

  • The PDEG can broadcast day rhythm dimming curves, while the DDBC320-DALI can only receive these messages. The PDEB does not include this feature.

  • The PDEG hosts a webserver with a browser-based dashboard, enabling users to perform basic configuration tasks without System Manager. The DDBC320-DALI and PDEB do not include this feature.

DDBC320-DALI Common Area Ranges

The DDBC320-DALI can share a common area range with up to 3 other spurs or Ethernet devices. For example:

  • When a DDBC320-DALI is used as a translation gateway in a multi-spur project (replacing a PDEG), it is possible to create a common area across 3 spurs.

  • When all DDBC320-DALI controllers are directly connected to the Ethernet trunk, up to 3 of them can share a common area.

Secure Communication

It is possible to encrypt/secure communication on the IP trunk between a PDDEG-S translation gateway and DDBC320-DALI controller. One PDDEG-S can manage secure connections with up to 25 client devices (currently: DDBC320-DALI or PDZG-E). This architecture allows:

  • Schedules to be deployed to the PDDEG-S (but not to the DDBC320-DALI)

  • A 27-day rolling log on the PDDEG-S (but not on the DDBC320-DALI)

  • Support for common areas across more than 3 spurs.

DDBC320-DALI Replacing PDEG/PDEB as Access Point

In a single-spur project, it is possible to connect to the Dynalite system using the DDBC320-DALI Ethernet port. This eliminates the need and cost of a separate gateway device. When replacing the PDEB, there is no loss of functionality. When replacing a PDEG, the following functions are not available:

  • sb icon delete 27-day rolling log

  • sb icon delete Webserver/dashboard

  • sb icon delete Timeclock/schedule deployment

DDBC320-DALI Replacing PDEB/PDEG as Translation Gateway

The DDBC320-DALI can act as an Ethernet to RS-485 translation gateway, connected to System Builder via the Ethernet trunk and other DDBC320-DALI controllers via the RS-485 spur.

If common areas across spurs are used, the DDBC320-DALI can support common area across 3 spurs. The PDEB/PDEG support common areas across many spurs. However, it is important to keep common areas to a minimum as they increase the number of messages routed between spurs that may affect system performance.

When replacing the PDEB, there is no loss of functionality. When replacing a PDEG, the following functions are not available:

  • sb icon delete 27-day rolling log

  • sb icon delete Webserver/dashboard

  • sb icon delete Timeclock/schedule deployment

  • sb icon delete Common areas across more than 3 spurs

Ethernet-Only Topology

Currently we do not recommend an Ethernet-only topology where all DDBC320-DALI controllers (with DALI devices) are directly connected to the Ethernet trunk. This architecture potentially allows use of DALI sensors and dry contact inputs without the need for RS-485 DyNet spurs between controllers, but the performance limitations are difficult to estimate. Therefore, we recommend using a single DDBC320-DALI as a translation gateway and connecting the remaining DDBC320-DALI controllers via RS-485 until performance limitations are established.

Maintenance Connection

When a DDBC320-DALI is connected via RS-485, there are still benefits in connecting the Ethernet port to the LAN, including faster firmware upgrades and device save/load.

Without running the Bridge Configuration Wizard, it is possible to establish a TCP connection between System Builder and a DDBC320-DALI. In SB, select the DDBC320-DALI and click the Connection Settings tab. Select Connect to gateway TCP port and click the Connect button.

SB needs to know the IP address of the DDBC320-DALI to establish an Ethernet connection. The controller should either be configured with a static IP address, or have a reserved IP address on the network’s DHCP server.

If the DDBC320-DALI changes IP address after getting added to the job, the new IP address must be updated in the job, either manually or by sending a sign-on message from the device while SB is connected to the same RS-485 spur (or to the trunk if the DDBC320-DALI is a child Ethernet device connected to a PDDEG-S/PDEG).

If a new DDBC320-DALI is connected to the same Ethernet LAN as SB, you can add it to the job by clicking sb icon insert device from network Insert Device From Network (Ctrl+L), then sb icon discover network Discover Network > Discover Devices over Ethernet. If the DDBC320-DALI is discovered, SB prompts you to establish a secure TCP connection to the controller.