C-Bus Network Automation Controller SpaceLogic, 6DIN
Item Number: 5500NAC2
Datasheet
Product Dimensions
Width93 mm
Height108 mm
Depth63 mm
Specifications
Design
Range
Product or component type
Market segment
- buildings
- residential
Physical
Communication port protocol
- C-Bus RJ45 (4000 devices)
- BACnet IP RJ45 (2000 devices)
- Modbus RTU terminal block RS485 (31 devices)
- IP (Internet Protocol) RJ45
- serial link terminal block RS232
- Modbus TCP RJ45
Power consumption in w
Local signalling
- LED (green/red) for power
- LED (green/red) for status indication
- LED (green) for relay output (REL)
- LED (multi-colour) for input status
- LED (multi-colour) for RS232 link activity
- LED (multi-colour) for serial link communication (RS485, RX, TX)
- LED (green) for C-Bus status
- LED (green/yellow) for Ethernet link
Control type
- smartphone or tablet
- RESET push-button cold restart
- by web browser
- by touch panel
- remote control
- local control
- RESET push-button
Function available
- updateable software
- visualisation
Connections - terminals
- power supply: screw terminal 3 cable(s) 1.5-1.5 mm²
- LED lamp: screw terminal 2 cable(s) 1.5-1.5 mm²
- relay digital output: screw terminal 3 cable(s) 1.5-1.5 mm²
- digital input: screw terminal 2 cable(s) 1.5-1.5 mm²
- RS232 link: screw terminal 3 cable(s) 1.5-1.5 mm²
- RS485 link: screw terminal 5 cable(s) 1.5-1.5 mm²
Mounting support
Height
Width
Depth
Ambient air temperature for operation
Relative humidity
Ip degree of protection
Standards
- EN 55032: class A
- EN 50491-5-2: class B
- EN 55035
Mercury free
Rohs exemption information
Environmental disclosure
Eu rohs directive
Reach regulation
China rohs regulation
Others
Legacy weee scope
Package 1 bare product quantity
Average percentage of recycled plastic content
Weee applicability
Weee label
Product name
[us] rated supply voltage
Port ethernet
Number of port
- 1 USB 2.0 type A
- 1 USB 1.1 type B
- 1 RS232 (serial link)
- 1 RS485 (Modbus)
- 2 RJ45 (C-Bus)
- 1 RJ45 (Ethernet)
Web services
Web server
Number of inputs
Input impedance
- 2.2 kOhm closed
- 6.9 kOhm opened
Number of outputs
Output voltage
- 24 V DC 1 A for relay
- 48 V AC 1 A for relay
Total number of 18 mm modules
Operating altitude
Unit type of package 1
Number of units in package 1
Package 1 height
Package 1 width
Package 1 length
Package 1 weight
Unit type of package 2
Number of units in package 2
Package 2 height
Package 2 width
Package 2 length
Package 2 weight
Unit type of package 3
Number of units in package 3
Package 3 height
Package 3 width
Package 3 length
Package 3 weight
Total lifecycle carbon footprint
Carbon footprint of the manufacturing phase [a1 to a3]
Carbon footprint of the manufacturing phase [a1 to a3]
Carbon footprint of the distribution phase [a4]
Carbon footprint of the distribution phase [a4]
Carbon footprint of the installation phase [a5]
Carbon footprint of the installation phase [a5]
Carbon footprint of the use phase [b2, b3, b4, b6]
Carbon footprint of the use phase [b2, b3, b4, b6]
Sustainable packaging
Carbon footprint of the end-of-life phase [c1 to c4]
Carbon footprint of the end-of-life phase [c1 to c4]
Pvc free
Halogen-free status
Take-back
Product contributes to saved and avoided emissions
Removable battery
Total lifecycle carbon footprint
Average percentage of recycled metal content
Packaging made with recycled cardboard
Packaging without single use plastic
Halogen-free status
Pvc free
End of life manual availability
Take-back
Warranty (in months)
Documents & downloads
hide show-
All
-
Product Brochures
-
End of Life Manual
-
Environmental Disclosure
-
Installation Instruction
-
Operating Manuals
-
Quick Start Guide
-
Declaration of Conformity (Sustainability)
-
Software - Release
-
Software - Utility
-
Firmware
-
Firmware - History, Utility & Others
Frequently Asked Questions
Which version of Schedule Plus is compatible with C-Gate 3?
Hide ShowSchedule plus V5.4.0 is compatible with C-Gate 3
Release note:
Download link:
How to perform C-Bus Automation Controller LUA Script logging
Hide ShowDefault Log Helper Function
The LUA Script Editor contains Helpers - under the Alerts and Logs - contains a log variables function helper which when left clicked enters an example containing some different parameters to log. The results shown in the Current logs window of running a script containing the default log helper is as follows
Logging Descriptive String and Value
Using log function can be prefixed with a string as well as the parameter(variable) to provide understanding of what it being logged. All arguments are logged to the Current logs window in example below we see argument 1 being the description and argument 2 being the variables(parameter) value.
Logging Multiple Parameters or Concatenated Strings
Using log functions containing multiple strings and/or parameters eg log('string', parameter, parameter, parameters, ....) to see descriptions and multiple variables at the specified execution point in the LUA script. Knowing what various C-Bus groups, C-Bus levels, measurement values, user defined setpoints are at a specific point in the LUA script can help determine why a block of LUA script code is or isn't being executed.
Additionally using "tostring(variable)" to convert boolean, integer, floating value's into strings and " .. " to concatenate strings allows you to condense log messages into a single line. This allows complex logic with multiple conditional statements to be checked for expected and actual execution whilst troubleshooting LUA scripting.
SwValues = 'Reed Switch: ' .. tostring(SwReed) .. ', Switch Loops: ' .. tostring(SwLoops) .. ', Switch Value: ' .. tostring(SwValue)
log('Switch Values', SwReed, SwLoops, SwValue)
returns
* string: Reed Switch: true, Switch Loops: 5, Switch Value: 83.35
How to get a C-Bus Automation Controller LUA Script IF to perform like a PASCAL Logic ONCE
Hide ShowTo avoid an if statement being executed by the C-Bus Application/Controller Event-based engine numerous times the use of an outer if (or) - then statement ensuring that the event came from visualization or from c-bus avoids the inner event-based condition being met again and again. We can use LUA script log function and the Logs window to verify expected behaviour
Without outer if (or) - then statement
Without any outer conditional check of whether the event came from either visualization or c-bus network the log windows shows that a change in state of the Group 78 (Strong Room Reed Switch) being set to ON (255) - true results in numerous executions by the event-based lua script engine which continue to occur as seen by updating timestamp.
With outer if (or) - then statement ensuring that the event came from visualization or from c-bus
With the inclusion of an outer conditional loop checking whether the event came from either visualization or c-bus network the log windows shows that a change in state of the Group 78 (Strong Room Reed Switch) being set to ON (255) - true results in one execution and that another change in state of the Group 78 (Strong Room Reed Switch) being set to OFF (0) - false results in one execution. From the Logs window we can see that the added if (or) - then ensuring that the event came from visualization or from c-bus acts similar to a ONCE statement in PICED pascal logic
How to troubleshoot C-Bus Automation Controller LUA Scripts
Hide ShowSave Script - Syntax errors are shown when saving the script
These errors relate to general LUA command/statement syntax
example 1: in following if - then - else - end condition the following LUA script is missing the closing "end" statement
if (StrRmReedSwitch == false) then
-- Turn ON the Store Room Alarm and Alarm Light
SetCBusState(0, 56, 77, true)
SetCBusState(0, 56, 79, true)
else
SetCBusState(0, 56, 77, false)
SetCBusState(0, 56, 79, false)
results in the following error when attempting to save
Show Error Logs - Logical errors are shown when "Error log" is selected (1), and from the Error log window selecting "Show errors only for current script" (2) and "Clear" (3) then running the LUA script - by changing related object statuses etc in Object Tab, Visualization or Run Script
Logic errors relate to logical issues with the LUA Script such as trying to retrieve the state of an uninitialized group or trying to retrieve the state of a group that does not exist, or performing incompatible arithmetic etc.
example 2: Library cbuslogic:0: unable to find 0/56/250 --- (check if application 56, group address 250 object exists?)
example 3: Library cbuslogic:0: unable to decode 0/56/150 --- (check if application 56, group address 150 object currently nil "un-initialized")
example 4: User script:5: attempt to perform arithmetic on global 'StmRmTempSwitch' (a nil value) stack traceback: --- (check compatibility of arithmetic)
The following LUA script tries to perform a mathematical addition of a boolean returned from GetCBusState and an integer value resulting in Error log message
-- Get state of Store Room - Reed Switch on the local network
StmRmTempSwitch = GetCBusState(0, 56, 78)
IntValue = 5
CalcValue = IntValue + StmRmTempSwtich
Log messages which can help further troubleshoot LUA script issues are shown when "Log" is selected (1), and from the Current logs window selecting "Show logs only for current script" (2) and "Clear" (3) then running the LUA script - by changing related object statuses etc in Object Tab, Visualization or Run Script
Log messages can be used to log values of c-bus states, levels, variables and determine whether expected conditional and behavior is being met or may provide answer why a condition is not met and a certain block of the LUA script is not being executed.
example 5: Running the following script shown in image and turning the Strong Room Reed Switch group OFF and ON shows script is working as expected.