[tinysdc]

This section may not be present in your ini file at all. This is because it only applies to a specific device (the TinySDC Device, which is a small round LCD that fits inside a 52mm pod), and all of the settings have application level defaults.

Setting	Type	Explanation
remotebrightness	String	If specified, this setting allows the brightness of a remote TinySDC device to be controlled using any of the standard touch actions that can manipulate the value of a setting. See further information below.

Controlling the brightness of a TinySDC device

TinySDC is quite small, and is not entirely suited to pages which have inputs. Although it is quite possible to create a TinySDC page that allows screen brightness to be altered using a locally connected rotary encoder and the screenbrightness setting, an alternative scenario is that a different CANBus node has an encoder connected and has the means to display a GUI for altering brightness (likely a bigger screen).

In this scenario, you can create a screen on the ‘Local’ device (the one with the encoder connected) and control the brightness on the ‘remote’ TinySDC device. To do this, take the following steps:

1. On the local device, define a setting to represent the TinySDC brightness, with range 0-255 and a step size of 10. Give this setting a unique name.
2. Define the same setting on the TinySDC device, with the same name and the same ID. (You should always keep all settings the same across all devices on the CANBus anyway).
3. On the TinySDC device, add an entry in the [tinysdc] section remotebrightness=<setting name> where the name specified is the one you just created.
4. Create whatever user interface you want to control the setting on the local device. There are some examples in the encoder modes demo pageset.

Each device on the CANBus network has its own local brightness setting. Normally, whenever a setting is changed it is broadcast on the CANBus to keep all of the devices in sync. The brightness setting however is not sent otherwise all screens would change their brightness when trying to change one of them.

By creating a new setting to represent the remote brightness, this setting will be broadcast over the CANBus and the only device that will respond to it is the one with a matching remotebrightness setting in its [tinysdc] section. Altering this setting will cause direct changes to the brightness setting on the associated device.

Note that if you have two TinySDC devices and one main device, using the same setting name in all three will result in both TinySDC devices responding to the brightness changes. If you wanted to control them separately, then you would need two user interfaces on the main local device, two separate brightness settings, and a different remotebrightness setting in each TinySDC’s [tinysdc] section. As mentioned, all devices should contain all defined settings to keep the setting IDs in sync.