Table of Contents

Advertisement

Quick Links

Lithernet - Casambi Gateway v1.71
System Manual
Stand: 13.04.2021

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Lithernet and is the answer not in the manual?

Questions and answers

Summary of Contents for Casambi Lithernet

  • Page 1 Lithernet - Casambi Gateway v1.71 System Manual Stand: 13.04.2021...
  • Page 2: Table Of Contents

    2.2. Gateway to the Helvar Router System (HelvarNet) ..............15 2.3. Gateway to a system via UDP / TCP commands ..............17 2.4. Bridge between individual Casambi systems ................18 2.5. Coupling to an existing BMS / visualization ................20 2.6. ArtNet Gateway ..........................22 2.7.
  • Page 3 5. Command structure in UDP Casambi Command mode ..............101 5.1. General structure of the commands ..................102 5.2. Commands from the Casambi system ..................103 5.2.1. 0x28 - Receive time from the Casambi network .............104 5.2.2. 0x0D - Scene called ......................105 5.2.3. 0x39 - Node Status ......................106 5.2.4.
  • Page 4 5.4. Demo programs ........................120 6. Command structure in BacNet / IP mode ..................121 6.1. To Casambi ..........................123 6.2. From Casambi ..........................124 6.3. Sensor Value To Casambi ......................125 7. Changelog Firmware .........................126 7.1. Firmwareversion 1.00 .......................127 7.2. Firmwareversion 1.10 .......................128 7.3. Firmwareversion 1.15 .......................129 7.4.
  • Page 5: Hardware

    1. Hardware The device has only one connection for network (RJ45). The supply takes place via POE. The gateway uses one address in the Casambi network. On the front there are 4 LEDs for status display.
  • Page 6: Led-Display

    1.1. LED-Display The module has 4 LEDs on the front. From bottom to top: 1) Operating LED - flashes green regularly (1 second) 2) Network status - lights up yellow when network is plugged in 3) UDP LED - Lights up red when there is no UDP connection, green when one is established 4) TCP / IP LED - Lights up red when there is no TCP / IP connection, green when one has been opened The LEDs can also be switched off in the software.
  • Page 7: Hardware Revision

    1.2. Hardware Revision Hardware Revision 1: Development Device for early testing of the functions Hardware Revision 2: Final layout with final housing.
  • Page 8: Watchdog

    1.3. Watchdog A watchdog runs in the gateway with a set time of 90s so that the device can be restarted automatically if necessary.
  • Page 9: Conformity

    1.4. Conformity EC declaration of conformity Lichtmanufaktur Berlin GmbH hereby declares that the radio system type "Lithernet - Casambi Gateway" complies with Directive 2014/53 / EU. The full text of the EU declaration of conformity is available at the following Internet address: https://...
  • Page 10: Bluetooth Module

    All information on this page relates only to the radio module used. Not the entire product. The CBM-002A module from Casambi Oy is used as the Bluetooth module The declaration of conformity for the radio module can be found at the following Internet address: https:// casambi.com/static/datasheets/CBM-002-DoC.pdf...
  • Page 12: Device Labeling

    There are 2 labels on the back of the device. Here you can see in the barcode: 01: Litehrnet - Casambi Gateway 41/2020: week and year of manufacture in this case week 41 in 2020 00000001: serial number of the device...
  • Page 13: Areas Of Application

    3.1 Gateway to the Eutrac Netcomposer 3.2 Gateway to the Helvar Router System (HelvarNet) 3.3 Gateway to a system via UDP / TCP commands 3.4 Bridge between individual Casambi systems 3.5 Coupling to an existing BMS / visualization 3.6 ArtNet Gateway...
  • Page 14: Gateway To The Eutrac Netcomposer

    2.1. Gateway to the Eutrac Netcomposer In this operating mode it is possible to establish a link to a system with the Eutrac netcomposers. It is possible to communicate bidirectionally between the two systems. A total of 32 triggers can be set in each direction for each gateway.
  • Page 15: Gateway To The Helvar Router System (Helvarnet)

    2.2. Gateway to the Helvar Router System (HelvarNet) In this operating mode it is possible to establish a link to a system with the Helvar router system.
  • Page 16 It is possible to communicate bidirectionally between the two systems. A total of 32 triggers can be set in each direction for each gateway. The programming uses a wizard that simplifies the creation of commands. An IP address of a router must be specified as the destination of the connection. The operating mode to be selected here would be "HelvarNet (TCP)".
  • Page 17: Gateway To A System Via Udp / Tcp Commands

    2.3. Gateway to a system via UDP / TCP commands In this operating mode it is possible to link to a system not defined in advance using UDP / TCP ASCII commands. This could e.g. Media controls (Crestron, ...) or KNX systems with which this integration via the network is possible.
  • Page 18: Bridge Between Individual Casambi Systems

    2.4. Bridge between individual Casambi systems In this operating mode it is possible to connect several self-sufficient Casambi networks via the gateway. It is possible to communicate bidirectionally between the two systems. A total of 32 triggers can be set in each direction for each gateway.
  • Page 19 The gateways communicate with each other via UDP broadcast commands on a freely adjustable port. The operating mode to be selected here would be "UDP Casambi Bridge".
  • Page 20: Coupling To An Existing Bms / Visualization

    Of course, several gateways can react to the same commands. The gateways communicate with each other via UDP broadcast commands on a freely adjustable port. The operating mode to be selected here would be "UDP Casambi Command".
  • Page 21 The command structure in "UDP Casambi Command" mode is also explained in this manual. There are also demo programs that show you the connection and use on the evaluation page.
  • Page 22: Artnet Gateway

    It is possible to control 32 Casambi commands (scenes, groups ...) using ArtNet For level-based commands, the level is sent from the ArtNet to the Casambi system. For commands that are not level-based, a value above 128 is the trigger for execution.
  • Page 23: Bacnet/Ip Gateway

    In this operating mode it is possible to address the gateway directly via BacNet / IP. It is possible to send an unlimited number of commands to the Casambi system. The commands are set via BacNet / Ip and started with a "run" value.
  • Page 24: Settings In The Gateway

    3. Settings in the gateway The settings that can be made on the gateway website are described here. The gateway is supplied with the address 192.168.1.90. With a web browser you can now go to http://192.168.1.90 and come to the corresponding start page. Here you have to enter the username and password.
  • Page 25: General Setting

    3.1. General Setting The basic settings can be made on this settings page. There are 3 subcategories. Network, user and time, configuration.
  • Page 26: Network

    3.1.1. Network...
  • Page 27: Ip Settings

    3.1.1.1. IP settings Settings for the IP configuration can be made here. In the factory state it is delivered with the IP address 192.168.1.90. DHCP: DHCP active or inactive Hostname: hostname of the device IP address: IP address of the device Subnet: Subnet mask Gateway: gateway address Name servers 1 and 2: The DNS entries for the gateway...
  • Page 28: Ntp-Client

    3.1.1.2. NTP-Client The parameters for the built-in NTP client are set here. The NTP client field can either be activated or deactivated. If it is activated, the gateway gets the current time of the NTP server when starting, as well as when querying via the "Date and Time" function. NTP server is the address / URL of the server.
  • Page 29: Restart Gateway

    3.1.1.3. Restart Gateway With this the gateway can be restarted.
  • Page 30: User And Time

    3.1.2. User and Time...
  • Page 31: User Management

    3.1.2.1. User Management Here the user name and password of the user can be set who should have access to all functions of the system. Only one user can be created. The "Change Login" button transfers the user name and password.
  • Page 32: Date And Time

    3.1.2.2. Date and Time The current time at which the gateway is set is always displayed. With "Get Date and Time from Casambi" you can get the current time from the Casambi network. Since Casambi needs sometime to send the data, the page can be reloaded with the refresh button.
  • Page 33: Configuration

    3.1.3. Configuration...
  • Page 34: Control System Wizard

    - Free commands over UDP - HelvarNet (TCP) - Free commands over TCP - UDP Casambi Command - UDP Casambi Bridge With the button "next step" you can switch to the next step in the wizard. The button "step back" allows you to...
  • Page 35 After entering all settings, the device can be rebooted directly with reboot and the set values are adopted.
  • Page 36: Netcomposer System

    3.1.3.1.1. Netcomposer System The Eutrac netcomposer system broadcasts its data on port 10009. These values are also permanently stored in the profile.
  • Page 37: Art-Net

    3.1.3.1.2. Art-Net With Art-Net it is possible to address the gateway via DMX commands. In this case, the port is fixed at 6454. The universe is freely adjustable. "Art-Net™ Designed by and Copyright Artistic Licence Holdings Ltd"...
  • Page 38: Free Commands Over Udp

    3.1.3.1.3. Free commands over UDP Here commands are broadcast to the specified port.
  • Page 39: Helvarnet (Tcp)

    3.1.3.1.4. HelvarNet (TCP) The TCP port and the delimiter between the commands are fixed according to the protocol and cannot be adjusted. For the IP address of the router, an existing HelvarNet router address must be specified, to which the gateway then connects.
  • Page 40: Free Commands Over Tcp

    3.1.3.1.5. Free commands over TCP The "System IP" is the address of the controller / server to which the gateway should connect. The delimiter is the separator between the individual commands. The ASCII number of the corresponding character must be entered here. 35 corresponds to the "#".
  • Page 41: Udp Casambi Command

    3.1.3.1.6. UDP Casambi Command The "Net ID" parameter is required to identify which bridge the command comes from. It can be selected from 0 - 255. The UDP port parameter is used to select which port is to be listened to and sent on.
  • Page 42: Udp Casambi Bridge

    3.1.3.1.7. UDP Casambi Bridge To identify which bridge the command comes from, the "Bridge ID" parameter is required. It can be selected from 0 - 254. The UDP port parameter is used to select which port should be listened to and sent.
  • Page 43: Bacnet/Ip

    3.1.3.1.8. BacNet/IP The port for communication can be adjusted here. As well as the local device ID.
  • Page 44: Led Settings

    3.1.3.2. LED Settings Various features of the LED can be deactivated or activated here. LED on inactive means that the LEDs have no function. They are always out. With the button Identify the 3 upper LEDs of the device start to go up and down.
  • Page 45: Update Firmware

    3.1.3.3. Update Firmware A firmware update of the gateway can be carried out here. The firmware file is selected with "Select file". The update button then transfers it. If the update was successful, you will be redirected to the home page after a short time.
  • Page 46: Import / Export

    3.1.3.4. Import / Export The Export button generates a file with the format "* .ceg". This file is downloaded and can then be saved as a backup. The file name of the file is always automatically "export_ [IP address with _ instead of.]. Ceg Such an * .ceg file can be selected and imported again via Import.
  • Page 47: System Memory

    3.1.3.5. System Memory With the "Reset" button, the system can be reset to the factory settings. For this, the slider "Slide for Reset" must be set to "On". With the "Diagnostic Data" button, a website is output in which the current parameterization of the gateway is output.
  • Page 48: To Casambi

    3.2. To Casambi Here you can set which actions the device should carry out in the Casambi system when a command comes to the gateway via the network. Depending on the system, you either go directly to the "Commands" page.
  • Page 49: Commands

    3.2.1. Commands Here you can set which actions the device should perform in the Casambi system when a command comes to the gateway via the network. The "Save" button saves the entry on the selected slot. The "Test" button executes the action in order to be able to check whether the correct action has been selected.
  • Page 50: Select Storage Space

    3.2.1.1. Select storage space The first step is to select a storage location on which the action should be saved: The storage space can be selected using the dropdown list and the content can be displayed on the website with the "Load ..."...
  • Page 51: Trigger

    3.2.1.2. Trigger The command to which the gateway should react is entered in the text field. For the already installed protocols (HelvarNet, NetComposer) there are wizards with which an easy creation is possible. If one of the built-in protocols is selected, the trigger area looks like this: At Art-Net the DMX address is entered instead of the trigger command.
  • Page 52: Netcomposer Command Builder

    3.2.1.2.1. Netcomposer Command Builder The wizard supports the creation of commands to which the Casambi system should react. The "NCR Address" specifies which NCR address to react to. 255 is "all". With "Command" there are various commands available that can be reacted to.
  • Page 53: Device Level

    3.2.1.2.1.1. Device Level With Device, the device address of the target is specified. The desired brightness is specified for Level. The corresponding fade time for fading. "Ignore Fading" ignores the fade time in the call.
  • Page 54: Scene

    3.2.1.2.1.2. Scene The desired scene is specified under Scene. The corresponding fade time for fading. "Ignore Fading" ignores the fade time in the call.
  • Page 55: Group With Scene

    3.2.1.2.1.3. Group with Scene With Group the group number of the destination is given. The desired scene is specified under Scene. The corresponding fade time for fading. "Ignore Fading" ignores the fade time in the call.
  • Page 56: Group With Level

    3.2.1.2.1.4. Group with Level With Device, the device address of the target is specified. The desired brightness is specified for Level. The corresponding fade time for fading. "Ignore Fading" ignores the fade time in the call.
  • Page 57: Sequence

    3.2.1.2.1.5. Sequence "Sequence" is the sequence number. "State" indicates whether the sequence is started or stopped.
  • Page 58: Helvarnet Command Builder

    3.2.1.2.2. HelvarNet Command Builder The wizard supports the creation of commands to which the Casambi system should react. With "Command there are various commands available that can be reacted to. Recall Scene (Group) Recall Scene (Device) Direct Level (Group) Direct Level (Device) With the button "next step"...
  • Page 59: Recall Scene (Group)

    3.2.1.2.2.1. Recall Scene (Group) The group number from the designer software is entered in the "Address" field "Block" and "Scene" indicate which scene is called. When the "Constant Light" slide switch is set to On, the scene is called up in the constant light control of the Helvar system.
  • Page 60: Recall Scene (Device)

    3.2.1.2.2.2. Recall Scene (Device) The device number from the designer software is entered in the "Address" field "Block" and "Scene" indicate which scene is called. "FadeTime" specifies the fade time to be used. Specification in seconds. Ignore Fading specifies that the fade time sent should be ignored when the call is made.
  • Page 61: Direct Level (Group)

    3.2.1.2.2.3. Direct Level (Group) The group number from the designer software is entered in the "Address" field Level specifies the brightness in (0-254). "FadeTime" specifies the fade time to be used. Specification in seconds. Ignore Fading specifies that the fade time sent should be ignored when the call is made.
  • Page 62: Direct Level (Device)

    3.2.1.2.2.4. Direct Level (Device) The device number from the designer software is entered in the "Address" field Level specifies the brightness in (0-254). "FadeTime" specifies the fade time to be used. Specification in seconds. Ignore Fading specifies that the fade time sent should be ignored when the call is made.
  • Page 63: Action

    3.2.1.3. Action With the button Wizard, the dialog for setting the action is called. A new page then opens: With the button "next step" you can switch to the next step in the wizard. The button "step back" allows you to take a step back.
  • Page 64: Ping

    3.2.1.3.1. Ping Sends a "ping" signal to the Casambi system. In Art-Net operating mode, the command is triggered; if the DMX level is above 128, the command is triggered.
  • Page 65: Set Level

    3.2.1.3.2. Set Level Sets the entire Casambi system to the specified level in the specified time. In Art-Net mode, the level and duration are ignored. The level is taken from the DMX signal, the duration is always 0. When connecting via HelvarNet or to a Netcomposer system, the window looks like this: Here you can switch on via "Level from Network"...
  • Page 66: Push Button Pressed

    3.2.1.3.3. Push Button Pressed Transmits the "Button pressed" status to the Casambi system, which then carries out the corresponding action. In Art-Net operating mode, the command is triggered; if the DMX level is above 128, the command is triggered.
  • Page 67: Push Button Released

    3.2.1.3.4. Push Button Released Transmits the status "button released" to the Casambi system, which then carries out the stored action. In Art-Net operating mode, the command is triggered; if the DMX level is above 128, the command is triggered.
  • Page 68: Set Presence

    3.2.1.3.5. Set Presence Transmits to the Casambi system whether a movement has been detected or not. In Art-Net operating mode, the command is triggered; if the DMX level is above 128, the command is triggered.
  • Page 69: Set Scene Level

    3.2.1.3.6. Set Scene Level Calls up a scene in the Casambi system. A scene number must be entered for the scene. The level indicates the dimming level at which the scene should be called up. Duration determines the fade time.
  • Page 70: Set Group Level

    3.2.1.3.7. Set Group Level With this action a group can be set to a certain level. Duration again specifies the fade time. In Art-Net mode, the level and duration are ignored. The level is taken from the DMX signal, the duration is always 0.
  • Page 71: Set Push Button Level

    3.2.1.3.8. Set Push Button Level Sets the level of the device that is specified as the target of the button in the Casambi app. In Art-Net mode, the level and duration are ignored. The level is taken from the DMX signal, the duration is always 1.
  • Page 72: Set Lux Sensor

    3.2.1.3.9. Set Lux Sensor Displays the lux value to be sent. In Art-Net operating mode, the command is triggered; if the DMX level is above 128, the command is triggered.
  • Page 73: Sensors

    3.2.2. Sensors A sensor can be specified here that is actively queried by the gateway. The values that the sensor delivers are then transferred to the Casambi system as light values.
  • Page 74: Helvarnet

    This value can then be scaled using a factor. The factor can be set in increments of 0.01 from 0. The value that is transmitted to the Casambi system is then in Value. This then takes into account the entered...
  • Page 75: Netcomposer

    3.2.2.2. Netcomposer Attention! The feature is still in progress and will be added in a later firmware.
  • Page 76: Bacnet/Ip

    3.2.2.3. BacNet/IP The parameters for setting sensor messages can be set here. This looks like this in the BacNet: For the light sensor part:...
  • Page 77 Here, the value for the value of the light sensor can simply be transferred at Present Value. For the part motion detector: Here, the value for the presence sensor can simply be transferred for Present Value. 0 = no presence detected 1 = presence detected...
  • Page 78: Lightsensor

    The value factor can be used to adjust the value that is delivered via BacNet / IP. With Value the value is displayed which is transferred to the Casambi system. It is calculated using the formula: Value = Raw Value * Factor.
  • Page 79: Presence

    3.2.2.3.2. Presence With the drop-down list "Presence Detection" the transfer of a value as presence detection can be started. In the case of State, an inactive or active is displayed. Depending on the parameters that are transmitted via BacNet / IP. 0 = inactive 1 = active...
  • Page 80: From Casambi

    3.3. From Casambi Here you can set what the gateway should send on the network as soon as it e.g. Scene calls from the Casambi world are available. The "Save" button saves the entry on the selected slot. The "Test" button executes the action in order to be able to check whether the correct action has been selected.
  • Page 82: Select Storage Space

    3.3.1. Select storage space The first step is to select a storage location on which the action should be saved: The storage space can be selected using the dropdown list and the content can be displayed on the website with the "Load ..."...
  • Page 83: Trigger

    3.3.2. Trigger The trigger specifies when an action should be triggered. The triggers are used to set at which scene call in Casambi the command filed under "Action" should be sent on the network. In the Casambi system, you can then choose which bits are active in the trigger for a scene. (Picture below)
  • Page 84 The entered button is saved with the Submit button. With the test button you can check whether the entered action is correct.
  • Page 85: Action

    3.3.3. Action The command that the gateway should send is entered in the text field. For the already installed protocols (HelvarNet, NetComposer, Lithernet) there are wizards with which an easy creation is possible. If one of the built-in protocols is selected, the action area looks as follows:...
  • Page 86: Netcomposer Command Builder

    3.3.3.1. Netcomposer Command Builder The wizard supports the creation of commands to which the Casambi system should react. The "NCR Address" specifies which NCR address to react to. 255 is "all". With "Command" there are various commands available that can be reacted to.
  • Page 87: Helvarnet Command Builder

    3.3.3.2. HelvarNet Command Builder The wizard supports the creation of commands to which the Casambi system should react. With "Command there are various commands available that can be reacted to. Recall Scene (Group) Recall Scene (Device) Direct Level (Group) Direct Level (Device) With the button "next step"...
  • Page 88: Bridge Mode Command Builder

    3.3.3.3. Bridge Mode Command Builder With the button "next step" you can switch to the next step in the wizard. The button "step back" allows you to take a step back. After setting the command-specific settings, the generated command is displayed. You can try it out with a test and apply it with Apply.
  • Page 89: Console

    3.4. Console...
  • Page 92: Console

    3.4.1. Console A display of the last commands exchanged between the Casambi system and the network. In the text line, a command can be sent directly to the Casambi system. The submit button transmits the command. The Refresh button updates the display.
  • Page 93: Parameter

    This information is important for scenes or group calls. Here you can assign the scenes and groups to the corresponding parameters within the Casambi app and then get out which ID is hidden behind this in order to use them in the calls.
  • Page 94: Settings In The Casambi App

    4. Settings in the Casambi app On the Casambi network side, the system behaves like a normal light / button / sensor. It can be found in the Casambi software as a Bluetooth device and can be added. It then appears on the one hand in the luminaire overview, but also as a sensor and switch.
  • Page 95: Behavior As A Lamp

    4.1. Behavior as a lamp You can pack the gateway into scenes or groups as normal. Instead of a level, it has 8 switches. With these you can perform the actions within the gateway. Depending on the status of the switches, a saved trigger can be executed.
  • Page 96: Settings As A Lamp

    4.2. Settings as a lamp The parameters can then also be set on the settings page of the lamp, e.g. Get group addresses or scene addresses.
  • Page 98: Settings As A Button

    4.3. Settings as a button In the Casambi software, the gateway can be selected in the button area on the settings page. Four buttons can now be defined here.
  • Page 99: Settings As A Pir Sensor

    4.4. Settings as a PIR sensor In the Casambi software, the gateway can be selected in the Sensor area on the settings page. This can now be set in the motion detector area.
  • Page 100: Settings As Lux Sensor

    4.5. Settings as lux sensor In the Casambi software, the gateway can be selected in the Sensor area on the settings page. This can now be set in the area of the daylight sensor.
  • Page 101: Command Structure In Udp Casambi Command Mode

    5. Command structure in UDP Casambi Command mode Description of the structure of the commands that the gateway sends in "UDP Casambi Command" mode...
  • Page 102: General Structure Of The Commands

    [length-1]; Packets with length 0 are ignored by the Casambi system. The length is currently limited to a maximum of 17 bytes and cannot be larger. In the future, Casambi reserves the right to extend the maximum length.
  • Page 103: Commands From The Casambi System

    5.2. Commands from the Casambi system When a package comes from the Casambi system, the part is 0x_Command_Direction 0x70. We only consider the part 0x_Casambi_Data [1 ... X] from the general data frame from 5.1 5.2.1) 0x28 - Receive time from the Casambi network 5.2.2) 0x0D - Scene called...
  • Page 104: 0X28 - Receive Time From The Casambi Network

    5.2.1. 0x28 - Receive time from the Casambi network Response of the Casambi system to the request to send the current time. Length: 0x08 Opcode: 0x28 0x_year_high.0x_year_low.0x_month.0x_day.0x_hour.0x_minute.0x_second Example: 0.70.8.28.7.e4.3.5.e.13.1d/r/n...
  • Page 105: 0X0D - Scene Called

    5.2.2. 0x0D - Scene called The gateway must be added to the corresponding scene. Using the slide switches Bit_1 to Bit_8, up to 255 different scenes can be encoded. Each time the scene is called, the command is sent to the network accordingly. Length: 0x09 Opcode: 0x0D 0x_Bit_1.0x_Bit_2.0x_Bit_3.0x_Bit_4.0x_Bit_5.0x_Bit_6.0x_Bit_7.0x_Bit_8...
  • Page 106: 0X39 - Node Status

    5.2.3. 0x39 - Node Status Details of the current status of a node are transmitted. The answers can come as a burst. Length: 0x6 Opcode: 0x39 0x_Unit_ID.0x_Scene.0x_Priority_Node_Type.0x_Condition.0x_Online 0x_Scene the currently active scene ID 0x_Priority_Node_Type => Priority (0..15, the 6 lower Bits) 1 = Emergency 2 = BMS override 3 = Manual control...
  • Page 107: 0X3A - Notify Node Removed

    5.2.4. 0x3A - Notify Node removed Notification that a device has been removed from the network. This answer can also come when a status of one Node was queried that does not exist. Length: 0x2 Opcode: 0x3A 0x_Unit_ID Example: 2.3a.1...
  • Page 108: Commands To The Casambi System

    5.3. Commands to the Casambi system If a package comes from the Casambi system, the part is 0x_Command_Direction 0x72. We only consider the part 0x_Casambi_Data [1 ... X] from the general data frame from 5.1 5.3.1) 0x10 - Push Button Pressed 5.3.2) 0x11 - Push Button Released...
  • Page 109: 0X10 - Push Button Pressed

    5.3.1. 0x10 - Push Button Pressed Set the state of a button [0..3] to pressed. Length: 0x02 Opcode: 0x10 0x_Button_Number Example: 0.72.2.10.0/r/n...
  • Page 110: 0X11 - Push Button Released

    5.3.2. 0x11 - Push Button Released Set the state of a button [0..3] to released. Length: 0x02 Opcode: 0x11 0x_Button_Number Example: 0.72.2.11.0/r/n...
  • Page 111: 0X1E - Set The Level Of A Scene

    5.3.3. 0x1E - Set the level of a scene Set all Casambi lights of a scene to one value. Length: 0x05 Opcode: 0x1E 0x_Scene.0x_Level.0x_Duration_low.0x_Duration_high Example: 0.72.5.1e.0.ff.0.10/r/n...
  • Page 112: 0X1F - Set The Level Of A Group

    5.3.4. 0x1F - Set the level of a group Set all Casambi lights in a group to one value. Length: 0x05 Opcode: 0x1F 0x_Group.0x_Level.0x_Duration_low.0x_Duration_high Example: 0.72.5.1f.0.ff.0.10/r/n...
  • Page 113: 0X20 - Set Level Of All Devices

    5.3.5. 0x20 - Set level of all devices Alle Casambi Leuchten eines Netzes auf einen Wert setzen. Length: 0x04 Opcode: 0x20 0x_Level.0x_Duration_low.0x_Duration_high Example: 0.72.4.20.ff.0.10/r/n...
  • Page 114: 0X21 - Set The Level Of The Target Of A Button

    5.3.6. 0x21 - Set the level of the target of a button Set the target of a button [0..3] to an absolute level. Length: 0x03 Opcode: 0x21 0x_Button_Number.0x_Level Example: 0.72.3.21.0.ff/r/n...
  • Page 115: 0X28 - Request Time From The Casambi Network

    5.3.7. 0x28 - Request time from the Casambi network Requests the Casambi network to send its current time. Length: 0x01 Opcode: 0x28 Beispiel: 0.72.1.28/r/n Example: 0x28 - Zeit aus dem Casambi Netz empfangen...
  • Page 116: 0X28 - Set Time In The Casambi Network

    5.3.8. 0x28 - Set time in the Casambi network Sets the time in the Casambi network to the specified values. Length: 0x08 Opcode: 0x28 0x_year_high.0x_year_low.0x_month.0x_day.0x_hour.0x_minute.0x_second Example: 0.72.8.28.7.e4.3.5.e.13.1d/r/n...
  • Page 117: 0X2B - Set Presence Sensor

    5.3.9. 0x2B - Set presence sensor Sets the presence sensor of the device to 0 = no presence or 1 = presence. Length: 0x02 Opcode: 0x2B 0x_sensor_state Example: 0.72.2.2B.0/r/n...
  • Page 118: 0X2C - Set Light Sensor

    5.3.10. 0x2C - Set light sensor Sets the device's light sensor to a value. Length: 0x03 Opcode: 0x2C 0x_Sensor_Value_low.0x_Sensor_Value_high Example: 0.72.3.2C.ff.0/r/n...
  • Page 119: 0X39 - Node Status

    5.3.11. 0x39 - Node Status Queries the state of a node. Attention only works with Evolution firmware. The request can be: 0x00: Deactivate automatic notification of the change of state 0x01 - 0xFB: Query of a unit based on its ID 0xFE: Activate automatic notification when all nodes change status 0xFF: automatic notification when the status of your own node changes Do not send the query command too quickly in succession and always a single unit, otherwise the system may...
  • Page 120: Demo Programs

    UDP mode using the UDP Casambi Command. https://github.com/KLKG/Casambi_Gateway_API_Test There is a program (UDP_Test) that cyclically queries all Casambi participants in a command line. Source code in C ++. The other program (UDP_WPF) is a C # application with a graphical user interface. Commands other than just the cyclical query can also be sent here.
  • Page 121: Command Structure In Bacnet / Ip Mode

    The device can be found in the network via BacNet / IP. The port and the local device ID can be freely set. The device has three structured views each with their own parameters. "To Casambi" is responsible for the communication BacNet / IP -> Casambi.
  • Page 122 Casambi" is responsible for feedback from the Casambi system. "Sensor Value To Casambi" is used to pass on light sensor values and presence reports from the BacNet a Casambi. The Structured_Views currently serve to simplify the assignment of the variables. Unfortunately not all BacNet...
  • Page 123: To Casambi

    In this operating mode, the values index and optional data 1 - 4 are set first. As soon as this is done, the value "run" can be set to 1 / true and the command is transferred to the Casambi system.
  • Page 124: From Casambi

    6.2. From Casambi If the gateway is added to a scene in the Casambi system, a binary number can be set using the gateway's 8 sliders. This number is then returned when the scene is called via the value index. With timestamp, the time in seconds that the gateway runs is set.
  • Page 125: Sensor Value To Casambi

    6.3. Sensor Value To Casambi For the light sensor part: Here, the value for the value of the light sensor can simply be transferred at Present Value. For the part motion detector: Here, the value for the presence sensor can simply be transferred for Present Value.
  • Page 126: Changelog Firmware

    7. Changelog Firmware Overview of the changes to the firmware in the individual versions.
  • Page 127: Firmwareversion 1.00

    7.1. Firmwareversion 1.00 - Installation of the wizards for HelvarNet - Installation of wizards for Netcomposer...
  • Page 128: Firmwareversion 1.10

    7.2. Firmwareversion 1.10 - Introduction of sliders in the surface - Set time and read out from the Casambi system - Error pages revised - UI elements adjusted / adjusted...
  • Page 129: Firmwareversion 1.15

    7.3. Firmwareversion 1.15 - Installation "UDP Casambi Command" mode - minor bug fixes - Redirect built in after changing IP settings and control system - "UDP Casambi Command" mode switched to completely hexadecimal...
  • Page 130: Firmwareversion 1.16

    7.4. Firmwareversion 1.16 - Added NTP client - Adjusted time settings...
  • Page 131: Firmwareversion 1.25

    7.5. Firmwareversion 1.25 - New wizards - ArtNet client...
  • Page 132: Firmwareversion 1.50

    7.6. Firmwareversion 1.50 Attention! If the firmware is updated from a version lower than 1.50, all settings are deleted. We recommend saving the previous settings once via System Memory and re-entering them later. - Increase to 32 possible entries - Internal storage layout change - Graphical bug fixes - Subdivision of the settings page with sub-pages - Installation of the possibility to export the programming and subsequently import it again...
  • Page 133: Firmwareversion 1.51

    7.7. Firmwareversion 1.51 - Dedicated bridge mode with its own wizard...
  • Page 134: Firmwareversion 1.55

    - Apply values (level) from Eutrac Netcomposer - Take values (level) from HelvarNet system - Bugfix when receiving multiple UDP packets - Automatic connection establishment for TCP / UDP connections every 60s - Fixed "From Casambi" that the triggers could not be deleted...
  • Page 135: Firmwareversion 1.5.7

    7.9. Firmwareversion 1.5.7 - Console revised - Light sensor values can be taken from the Helvar system - "To Casambi" page equipped with a submenu for the sensors - "Open points" removed from the manual...
  • Page 136 7.10. Firmwareversion 1.65 - Hardware revision 1 completed - Manual adapted accordingly to revisions - Revision 1 LED settings in the surface...
  • Page 137: Firmwareversion 1.69

    7.11. Firmwareversion 1.69 Firmware version 1.69 only exists for REV1, as there have been no changes for REV0. - Fixed problems with the LEDs in REV1...
  • Page 138: Firmwareversion 1.70 Beta

    7.12. Firmwareversion 1.70 beta Firmware 1.70 exists for REV1 and REV0 - Bacnet / IP added as a system - Watchdog introduced...
  • Page 139: Firmwareversion 1.71

    7.13. Firmwareversion 1.71 - Bacnet out of beta state - Fixed an problem settign an year bigger then 2020 - Fixed the Documentation on the API call off Node State...

Table of Contents