...
| Expand | ||
|---|---|---|
| ||
All devices can be mounted either using a TAPE or with SCREWS - both included in the box  |
...
Quick start guide per model
| Expand | ||
|---|---|---|
| ||
  |
| Expand | ||
|---|---|---|
| ||
  For the complete installation instructions (eg Surface preparation for applying adhesive tape) and removal instructions: TD1060 SLIM user manual.pdf |
...
Installation of the TD-1070
...
Installation of the TD-1050
...
| Expand | ||
|---|---|---|
| ||
  |
...
Preparing the device to install the app
Step 1: Power the device
The device will launch automatically after connecting it to a power supply.
The device does not have a fixed battery; therefore, it is important to maintain a stable power supply.
Step 2: Connect to the network
Connecting to a wired network happens automatically when plugging in the (POE) Ethernet cable.
Make sure Ethernet is enabled in your POE switch.
Specific configuration such as subnet mask, fixed IP etc. can also be configured via the device's home screen.
The wireless network can be configured via the app's home screen:
In case your device seems to be stuck in the booting process, you will need to reset the device: there is a hole labelled "reset" at the back. Power on the device and push a paperclip for 10 seconds in the reset hole (you should feel a click when pushing the reset button).
Step 3: Check firmware version
Make sure the latest version required firmware version is installed.
At least version v1.0.18 must be installed.
The version can be checked on the home screen (see screenshot below):
Upgrades of the firmware can be managed via remote Device Control Platform (Kiosk App & Workplace App)
| Expand | ||
|---|---|---|
| ||
This sub-step is only required when:
Option 1
Option 2
|
Step 4: Install the app using Spacewell Device Control
You have now successfully installed the Qbic Meeting Room Display.
In order to further configure the device, install the Room Display app you can use the Device Control Platform (Kiosk App & Workplace App)
FAQ
| Expand | ||
|---|---|---|
| ||
COBUNDU API and all apps/touchpoints communicate over https i.e. 443 should be good enough. Specific to Qbic devices -> The device control platform (1st DC tab specific to Qbic) communicates to the Qbic devices for hardware control over http (port 80). This is just how Qbic exposes the API, so we can't change that. If port 80 is not available, Qbic remote hardware management won't work. This is also the reason why Qbic hardware control is only available for PCs inside the same network. It's an additional security condition so that external devices don't access the Qbic API over http. If we're talking QBIC and they want to be able to use the 1st tab in device control: they need to open port 80 + 443 If not (no qbic but standing kiosk; or they don't care about scanning qbic devices in device control): from a purely Cobundu perspective, only port 443 is needed. Yet generally PCs/devices all do have port 80 open for web communication from other apps/services, so we're not sure what impact closing it might have. Small example: if currently you enter http://go.cobundu.com/ on your browser, you are automatically redirected to httpS://go.cobundu.com/ -> you asked for an insecure URL, but either the application or the browser automatically redirected you to the secure one. On the other hand, if port 80 was disabled, your http request might just show an error "connection refused" on the browser - and not redirect anymore, because port 80 could not capture your request |
...