DyNet wiring and protocol guide: RS485, Ethernet and downstream lighting interfaces

Discuss the Dynalite and DyNET Protocol Based Lighting Solutions
Post Reply
User avatar
ZerOne
Site Admin
Posts: 262
Joined: Sun Dec 13, 2020 8:21 am

Do not copy generic RS485 wiring rules blindly
An RS485 physical layer tells you how electrical signalling works, not the complete device pinout, network-power arrangement or application protocol. DyNet device terminals and some connectors carry power as well as data. Use the precise controller/interface manual for cable type, polarity, topology, shielding, earthing, isolation and any termination requirements.

The technical overview describes RS485 spurs and Ethernet-connected arrangements for larger systems. That does not make arbitrary stars, rings or extra terminators acceptable on every device network. Record existing arrangements before modifications, and have a Dynalite-trained installer assess extensions. Do not connect a control connector to an Ethernet switch merely because it looks like a network socket.

Separate the three layers
  • DyNet: coordination between panels, sensors, controllers and supported gateways.
  • The load controller: interprets commands and controls its assigned channels.
  • The output interface: for example phase dimming, relay switching or a separate DALI bus to drivers.
An Ethernet gateway connects supported network/integration functions; it does not automatically expose every internal operation through an unrestricted API. A command or preset being accepted is not independent confirmation of physical light output.

Protocol concepts worth learning first
The commissioning project links area/channel identities, presets and input behaviour. These mappings matter more to an integrator than isolated packet examples without context. Keep a current channel schedule and test documented status feedback where supported. Treat read/write access to building lighting as operational access, not a harmless discovery exercise.

Specifications and access
The linked manufacturer Technical Overview is a public architecture and integration guide, not a complete normative DyNet wire-protocol specification. Its sections explain RS485, Ethernet and gateways to systems including DALI and KNX. For packet-level integration, request the applicable approved protocol/interface documentation and access terms from Dynalite or its authorised channel.

Do not substitute an unofficial reverse-engineered document and describe it as the official standard. Confirm commissioning-software availability, installer training and project handover before committing to an integration. All mains and associated fixed installation work in Australia must be performed by appropriately licensed personnel.

Official reading
Dynalite Technical Overview: network and gateway sections
Post Reply

Return to “Dynalite / DyNet Protocol Discussion”