C-Bus Network Automation Controller SpaceLogic, 6DIN

Home ProductsSmart Home SolutionsC-BusNetwork Automation Controller

C-Bus Network Automation Controller SpaceLogic, 6DIN

Item Number: 5500NAC2

Datasheet

Product Dimensions

Width icon

Width93 mm

Height icon

Height108 mm

Depth icon

Depth63 mm

Free Introductory Training Module

Available via mySchneider

Specifications

Design

Range

SpaceLogic C-Bus

Product or component type

logic controller

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

2 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

DIN rail

Height

108 mm

Width

93 mm

Depth

63 mm

Ambient air temperature for operation

-5...45 °C

Relative humidity

10...90 %

Ip degree of protection

IP20

Standards

  • EN 55032: class A
  • EN 50491-5-2: class B
  • EN 55035

Mercury free

Yes

Rohs exemption information

Yes

Environmental disclosure

ENVPEP2104025EN

Eu rohs directive

Compliant with Exemptions

Reach regulation

Reference contains Substances of Very High Concern above the threshold

China rohs regulation

X

Others

Legacy weee scope

In

Package 1 bare product quantity

1

Average percentage of recycled plastic content

0 %

Weee applicability

Finished product

Weee label

N/A

Outside of Europe

Product name

C-Bus Automation Controller

[us] rated supply voltage

24 V DC

Port ethernet

10BASE-T/100BASE-TX

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

Web server

BMS controller compatible

Number of inputs

1 dry contact

Input impedance

  • 2.2 kOhm closed
  • 6.9 kOhm opened

Number of outputs

1 relay changeover

Output voltage

  • 24 V DC 1 A for relay
  • 48 V AC 1 A for relay

Total number of 18 mm modules

6

Operating altitude

<= 2000 m

Unit type of package 1

PCE

Number of units in package 1

1

Package 1 height

9.3 cm

Package 1 width

6.3 cm

Package 1 length

10.8 cm

Package 1 weight

364.0 g

Unit type of package 2

CAR

Number of units in package 2

10

Package 2 height

30.0 cm

Package 2 width

30.0 cm

Package 2 length

40.0 cm

Package 2 weight

4330.0 g

Unit type of package 3

P12

Number of units in package 3

240

Package 3 height

95.0 cm

Package 3 width

80.0 cm

Package 3 length

120.0 cm

Package 3 weight

108.0 kg

Total lifecycle carbon footprint

192 kg CO2 eq.

Carbon footprint of the manufacturing phase [a1 to a3]

52.38205428865981

Carbon footprint of the manufacturing phase [a1 to a3]

52 kg CO2 eq.

Carbon footprint of the distribution phase [a4]

0.05113285068268079

Carbon footprint of the distribution phase [a4]

0.1 kg CO2 eq.

Carbon footprint of the installation phase [a5]

0

Carbon footprint of the installation phase [a5]

0 kg CO2 eq.

Carbon footprint of the use phase [b2, b3, b4, b6]

138.9208207246974

Carbon footprint of the use phase [b2, b3, b4, b6]

139 kg CO2 eq.

Sustainable packaging

No

Carbon footprint of the end-of-life phase [c1 to c4]

0.7813287219828513

Carbon footprint of the end-of-life phase [c1 to c4]

0.8 kg CO2 eq.

Pvc free

Yes

Halogen-free status

Product contains halogen above thresholds

Take-back

No

Product contributes to saved and avoided emissions

No

Removable battery

N/A

Total lifecycle carbon footprint

192.13533658602273

Average percentage of recycled metal content

0 %

Packaging made with recycled cardboard

Yes

Packaging without single use plastic

No

Halogen-free status

Product contains halogen above thresholds

Pvc free

Yes

End of life manual availability

ENVEOLI2104025EN

Take-back

No

Warranty (in months)

18
Show all specifications

Documents & downloads

hide show
Filter items
  • 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

Important: Some software files may need a mySchneider or Club login to download.

Frequently Asked Questions

Which version of Schedule Plus is compatible with C-Gate 3?

Hide Show

Schedule plus V5.4.0 is compatible with C-Gate 3

Release note:

1

Download link:

https://www.se.com/au/en/product-range/2216-spacelogic-cbus-home-automation-system/#software-and-firmware

2

3


 

How to perform C-Bus Automation Controller LUA Script logging

Hide Show
C-Bus LUA Script log function is usual to help determine what values various LUS Script functions including C-Bus functions including Measurement Application and User Parameter functions etc. The use of the show Logs(1) to display Current logs window and selecting Show logs for only current script(2) and Clear and running script containing log functions will display any log string messages and parameters (variables). 

Default 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
Default log variables helper

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. 

Log string and variable parameters
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
 
Logging multiple parameters or concatenated strings

How to get a C-Bus Automation Controller LUA Script IF to perform like a PASCAL Logic ONCE

Hide Show
The SpaceLogic C-Bus Application Controller/Network Automation Controller LUA script does NOT contain an inbuilt "once" statement similar to the C-Bus PICED logic code.

To 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. 

No outer if (or) - then statement checking event senders
 
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

Outer if (or) - then statement checking if event sender is visualization or c-bus network

How to troubleshoot C-Bus Automation Controller LUA Scripts

Hide Show
C-Bus Application and Network Automation Controllers utilize LUA scripting to provide an additional level of customizable functionality via LUA event-based, resident or scheduled LUA scripting. The following troubleshooting tips can assist in troubleshooting LUA script issues. 

Save 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

LUA Syntax Error

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.

Show error log  

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. 

LUA Script Current logs