There’s a jumper with the Smartbox+ which you can find next to the screw terminals for the bus.

In case that the installation only contains 1 Smartbox+, it is necessary that in at least one of the 2 RJ11 connectors a closure resistance will be placed.

If you place a second Smartbox+ next to the first one than we close up the endings of both Smartbox+ with a closure resistance.

A non-closed CAN-bus will lead to an incorrect or instable working of the installation.

There are 6 different timer operators present in this software. However these are RELATIVE TIMER OPERATORS. Which means that the programmed times will only start working AFTER letting go of the button.

A timer which calls for daily returning routine, will be created on the LCD screen itself. These are the so called ‘TimeEvents’ and not Timers!

Edge Delay (Switch off delays on both flanks):

Retriggerable timer.

The timer triggers both rising or dropping flank of the entrance signal. The exit remains a te-time active

Input Delay (delayed switch on pos. flank) :

The timer triggers at a rising flank of the input signal.

After this switch-on time the exit remains a ti-time active as long as the entrance signal is active.

Output Delay (delayed switch off after neg. flank) :

Retriggerable timer.

The timer triggers at a lowering flank of the entrance signal. The exit follows the entrance and remains a to-time active.

Falling edge Delay(delayed switch off after neg.flank):

Retriggerable timer.

The timer triggers at a lowering flank of the entrance signal. The exit will be a tf-time active during the switch off of the entrance.

D

Delay (delayed switch off after neg. flank) :

Non retriggerable timer.

The timer triggers at a lowering flank of the entrance signal. The exit follows the entrance and remains a td-time active.

Rising Edge Delay :

Retriggerable timer.

The timer triggers at a rising flank of the entrance signal. The exit remains a tr-time active regardless of the entrance signal.

ATTN: in case one of these logic operators or timers will be used in a binding, this will become a condition binding. Both timers and conditions are limited.

The amount of timers and condition bindings can be consulted via bindingsoftware. Tabpage “node resource” of each module.

Timer operators can’t be used for IRTX and DUOSWITCH units.

For an installation with a CAN-switch, you have to measure the resistance on each bus line.

Check the polarity of the bus.

Both endings of the bus have to be closed due to a closure resistance of 120 ohm. If position 120E is selected, closure resistance will be used. This may ONLY if this interface is positioned on the last bus, in other words when the bus cable arrives and NOT leaves anymore. In this way the bus will be closed at one side.

Once the bitmaps are sent forward, the touchscreen still has to get a reset. The touchscreen will just restart. During this restart, new bitmaps are being uploaded.

Event Short Pulse :

With a short pulse on the entrance, this function will send forward the signal to the bounded exit.

Event Short Pulse + State :

It’s better to explain this one with an example.

Imagine there are 2 buttons (DT1 and DT2) and 2 light points. DT1 switches only light point 1, DT2 switches both on and off.

Several possibilities arise within this situation:

1. DT1 and DT2 will both be set up as: Event Short Pulse: In case DT1 is being pressed first, than light point 1 will burn. If you press DT2, than light point 1 will extinguish and light point 2 will burn.
2. DT1 will be set up as Event Short Pulse, DT2 will be set up as Event Short Pulse + State: in case DT1 will be pressed first, light point 1 will burn. If you press now on DT2, the status of light point 1 will be checked this ensures that both of them will be burning.
3. DT1 Will set up as Event Short Pulse + State: By making this choice it can happen that you have to press 2* on DT1 to change the brightness.

• So, solution B is the right one.

These flags can be used for visualising particular states in a binding. You can choose in the above right corner the editing frame of the bindings to set up a Binding Flag.

There are 3 kinds of Binding Flags :

• NO CHANGE : By carrying out the binding there is no status notification of the entrances visible on the LCD screen. This is used standardly. (For ex. Detectors, touchbuttons)
• 
• PRE (condition) : After carrying out the binding, there is a status notification of the entrances on the LCD screen visible. The showed status is the situation of the separate entrances in this binding. It’s used to visualize the situation of the condition (ex. Dark outside, after 10pm)
  
• POST (conditon) : After carrying out the binding, there is a status notification visible of the entrances on the LCD screen. The status of the entrances shows the situation of the exit in this binding. (ex. A virtual steers a lighting circle).
  

If you work with auto bindings than this will automatically be adapted where necessary! When an entrance shows up in 2 different bindings and the binding flags in the first binding PRE and in the second POST than will the status of the entrance be wrong.

The database will be build up by the master lcd and he will send it to all slave’s and gateway’s. In this database are all the nodes and units with their respectively name and their status (on, off, setpoint, etc.)

• Plug and Play: this function will delete the whole database in the touchscreen: it will check for new modules, it will assign a new module and it will give this one a logical address. Afterwards the database will be built up all over again.

This function may only be used for adding new modules or for deleting modules + demanding of the names + status of the exits.

• Browse Clr : This function will delete the whole database in the touchscreen. Whereupon the whole database will be build up again. This function may only be used for deleting modules + demanding of the names.
• Browse : This function will update the whole existing database in the touchscreen
• Update database : This function will only update the states of the exits in the database.

This indicates a severe CAN-bus problem.

Possible causes:

• Incorrect closure resistance.
• Mistake in the wiring
• Power supply problem.

Parameters:

• Node address = The module has noticed the CAN-bus problem. This is mostly 0xFD (modem) in the binding software.
• Unit address = always 0Xff. In the binding software it’s usually 0xFF.

Solution: check closure resistance, check on the star, check for over overload of the power supply’s, reset.

This happens when a transmitter sends a message but doesn’t get a reply from the destination. This will only happen after it has send the message more than 15 times. Out of the error you can’t check to which node this message had been sent. In the binding software Is this message usually from de modem: address=0xFD,0Xff. Via the communication tracer you can check to whom the last message was sent to. This one does has to be open before the error message has happened.

In case this happens during the browsing or during the sending of the programming, this can be checked eventually with the lower frame. Possible causes: the destination to whom the message is sent, has not replied because this one has gone off the bus

Parameters:

• Node address = the transmitter of a message who will not get a reply on the sent message. In the binding software this usually is 0xFD (=modem)
• Unit address = in case a unit has sent the message 0x00 till 0xFE, if the node then 0Xff. In the binding software this usually is the 0xFF

Solution: check the closing-up resistance, the star and check for overload of the power supplies, resetting.

This happens when a node receives a message that is not destined for him, this one will send the error message. A possible cause in case this error happens during the browsing or PNP: are there modules with a double logic address?

Parameters:

• Node address = the receiver of the wrong message
• Unit address = always 0xFF

Solution: try several times to send it forward, if it’s still not okay, you have to carry out a reset.

No, after adapting the unit properties, you have to push the single, double arrow to modify the settings, so it’s not enough to push the green ‘V’.

You may not detach the switch when there’s still voltage on it, because the switch will then be calibrated while you hold the buttons.

Solution: when you reset your automation, the switch will calibrate all over again by starting it up.

After changing the names, you have to browse with the master so that the database can be modified.

When a defect module has to be changed in the programming, it will go faster with the ‘problem solve wizard’.

You’ll have to change the module hardware reguraly. If the master asks to start a plug and play, you can just ignore this.

Go online with the binding software with the last programmed file. During it’s browse you’ll get the next notification.

Next you click on ‘next’. Now, you’ll see a few choices. The choice which is selected standardly may not be followed. You’ll have to choose for

Subsequently you see the physical address of the old (defect) module and underneath the physical address of the new module. Next, you click on ‘replace’. The software will now write the right logistic address to the new module.

ATTN: If you’d like to change more modules at the same time, then each time you’ll have to go to the drop-down menu to link the old module to the right new one. Confirm with ‘replace’ for every combination each time.

Next click ‘succeed’. The software will now scan the bus completely (browse). When it’s finished, you’ll get a notification that there are programming differences. This is correct because the new modules are not programmed yet. (a few steps back, we only gave the address)

Choose ‘next’ and let the software send all the names and bindings to all modules.

ATTN: this function only works if you change a module by one of the same kind with equal units (for example a relais module in a relais module, a dimmer in a dimmer)

There has to be a port forwarding installed in the modem.

• Telenet
  • Go to ‘my Telenet’ : https://login.prd.telenet.be/openid/login
  • Click ‘my internet’
  • Click (‘wireless settings’ and afterwards on ‘advanced’
  • Choose ‘IPv4 firewall & Port forwarding’
  • Fill in the IP address of the smartbox+ and the port.

• 
• • Proximus
    • B-box3
      • Connect the modem using the following address 192.168.1.1 in a webbrowser
      • Log in to the modem with the password which you can find on the backside of the modem.
      • Click on the option ‘entrancecontrol’
      • Select the tab ‘Portmapping’
      • Click on the button ‘Add new portmap’
      • Select ‘TCP’ and enter the portnumber 5001
      • Fill in the IP address of the smartbox+
      • Click ‘OK’ to save the settings.

   

  • B-box2
    • Connect the modem using the following address 192.168.1.1 in a browser.
    • Log in to the modem with the serial number which you can find on the backside of the modem.
    • Click on the option ‘advanced settings’
    • Select the option ‘LAN servers’
    • Click ‘New Entry’
    • Select the configuration options:
      • Server name: Duotecno TCP/IP
      • Access activated: Yes
      • Public Start Port: 5001
      • Public End Port: 5001
      • Protocol: TCP
      • LAN start Port: 5001
      • Local IP address: Ip Address of the Smartbox+
    • Click ‘Apply’ to save the settings.

When scheduling is being tested (ex. Within 5 minutes) you have to change the type of the week and then put it back.

Always use the same USB-connection to connect the modem.

Check if the driver of the CAN Modem is installed.

U have to keep in mind that every binding for an input keeps track of intern status. (0 or 1)
By touching short it toggles constantly when you push on it.

If you press shortly when using an OR, it is possible to have a situation in which there will be no change.

Example

1+1=1

1+0=1

1+1=1

1+0=1

0+0=0

While pushing, no function will be executed. You’ll keep 1 as a result. This is also visible when you combine multiple inputs through an operator with the binding flags PRE. (Here you can see the status of the inputs in the binding)

In fact, it is advised to always use the XOR with a short press. Therefore every time the condition of an input will be changed, an action will be triggered.

Example

1^1=0

1^0=1

1^1=0

0^1=1

0^0=0

By pressing longer, you may use the OR function because the status of the input will already be/ won’t be the physical pressing.