Settings

Updated

UPDD V6 utilises two settings files, the main settings file, updd.db, and the boot strap file updd.ini. These files are located in the driver's data folder for a given OS. These folders will exist if UPDD is installed.

Operating system Location 
 Windows %ALLUSERSPROFILE%\updd\updd.ini. Typically this means c:\programdata\updd\updd.ini 
 MacOS /Library/Preferences/updd/
 Linux /opt/updd/data/updd/

Bootstrap file

updd.ini is a bootstrap settings file that is used to alter the default behavior of UPDD components. By default it does not exist.
You should create and edit it using an appropriate ascii text editor.

On Windows the data folder will exist if updd is installed, but it may be hidden.

On Mac OS/X you will need root access to create or edit this file.

Possible values for this file are:

[updd]

toip.client=1 A value of 1 indicates that this computer is acting as a toip client
logerrors=y  logxxxx indicates messages to be logged in the debug log over a reboot 
logdebug=y  
logtrace=y  
logsql=y  
logconsole=y
 
listeningport=[port] TCP/IP port used by the driver to listen for API requests  - default 4146
dumphid=y Dump HID file. This is used to dump the HID Report Descriptor in cases where the UPDDutils dumphid command does not work because the driver finds something wrong with the HID Report Descriptor so does not retain connection to the device and hence the request to dump the HID RD via the command line interface fails.

HID descriptors are written to the same folder where updd.ini is located.

There can be multiple files because there will be one per interface.

The numbers in the name are vendor id, product id and interface e.g. updd_04f3_013e_0.hid

[server]

host=[ip address]  
port=[port]  TCP/IP port used by the API to communicate with the driver - default 4146 - or with the TCP/IP bridge.

Settings file

Many settings are used to hold information about the driver, hardware and utility programs.  The value of these setting come from various sources:

 Source Description
 Pre-configured  Pre-configured in the driver production system. These typically set up usability settings, such as names used to identify the touch device and are held in the UPDD setting file updd.db.
 Hard coded Defines the default values at a code level and are, as the term suggests, defined in the code. These typically set up the default, base line, settings for a specific function.
 Run-time Defines the values in real-time and relate to any values deduced whilst the driver is running.  These typically relate to hardware configuration values extracted directly from the touch hardware.
 User defined Set by the user as required. An end user can adjust pre-configured settings or override hard-coded or run-time default settings as required.

Settings can be related to a specific device or non-device (global / system wide).

The settings are set and updated by the driver and utility programs and can be maintained by various settings dialogs, such as those used by Gesture and the TUIO Server settings dialogs.

A driver setting dialog will be introduced in a future release of UPDD V6 to adjust common driver settings but in the meantime a command line interface is available to view and update appropriate settings - that is ones that can be adjusted post install and/or are useful to view. It is unlikely that the vast majority of the driver settings need to be adjusted as the default settings are set to the optimal value or are used for internal purposes only.

The are a number of useful settings appropriate to user adjustment as described here.

Search