The display setup file contains all the information needed to configure a colour display including connection definition, channel calibration and screen layout.
The Display Module can be connected to other ECUs via CAN bus.
Display Modules also have a range of analogue and speed inputs for interfacing directly to sensors.
File Names
Dash Design supports multiple display types and setup files have file names of the form .<display_type>.gdd. Depending upon your Windows® configuration, the last part of the file extension may not be visible in File Explorer.
Subsections of Creating and Editing Display Setups
Creating a New Display Setup
Overview
To create a new display setup, select File | New Setup... from the File Menu
menu and then select a display type from the list.
Workflow Tips
Data Model
When creating a new setup it is generally best to start with the data model.
Most display setups will require acquiring data from the outside world via physical inputs such as Analogue Inputs or via CAN messages. Once data acquisition is configured then it will naturally drive the screen design process.
It can be useful to create some test screens while configuring inputs to check that data is being acquired as expected by the display.
Analogue Inputs
Analogue Inputs (Analogue to Digital Converters, ADCs) are predefined Channels and will generally be scaled in Volts. Check your display pin-out to identify the analogue channels that are connected to sensors.
Create new Channels on the Channels Tab
that use these Analogue Input channels as their Primary Input and apply any required scaling based upon the data-sheets for your sensors. There may be existing preconfigured sensors in the Sensor Library Channel
that match.
CAN Inputs
Configure the CAN bus to ensure that it is running at the correct bit rate: CAN Bus Configuration
.
Define CAN channels on the CAN Receive
. This process can be simplified if a Signal Database (DBC) files are available (or can be created) for the modules you are connecting to - see CAN Signal Database (DBC) Import
.
So that you can switch screens / pages on the display, decide how page switching will work; Is this from an analogue input (e.g. a rotary switch) or from a CAN message? Some displays may have predefined inputs like rotary switches. Configure the page select input here: Page Select
.
Logic Channels / Notifications
It may make sense at this point to define any logic channels or notifications for things like warnings for out of range conditions.
Display Setup
Speed Input / Odometer
If vehicle speed related functions are required, set up the predefined Speed Input. Setting up the Speed Input will also enable the non-resettable Odometer function. See Speed / Odometer / Trip
Lap Timing / Beacon Input
You may also want to configure the beacon input at this stage to enable lap/stage timing. See Lap Timing / GPS
. Before configuring Lap Timing, configure the Speed Input (Speed / Odometer / Trip
).
Logging
If the Display Module supports on-board logging, logging can be configured on the Logger Tab
. This may be useful whilst configuring the data model; data logs may be analysed to check that inputs are behaving as expected and have correct scaling.
Image Assets
If using a heavily image based setup, you may want to import image assets for use in screen designs at this point. See the Images Tab
.
Some images may be configured to switch between various visual states based upon the value of a channel (e.g. for a battery warning light). See Image Selectors Tab
for information on how to configure this.
Screen Design
Once input channels and image assets are prepared, screens can be designed to display data with gauges on the Design Tab
.
Simulation
If a simulator is available for your display, then it may be simulated on the Simulator Tab
so that screen layouts can be tested before the more time-consuming process of testing on the real Display Module.
Display Setup Concepts
Setup Components
A Dash Design setup primarily consists of Channels and Gauges.
Channels are comprised of Sources, Outputs and Sensors, though much of this structure is not separated in the user interface. A CAN signal for example will have a raw ‘source’ that is used for acquiring the channel data and an ‘output’ which is associated with a sensor for scaling the raw data. Logically, the ’type’ of a channel is the associated ‘sensor’ type and the raw source is an implicit input to the ‘output’.
Sources
Non-visual objects that define how data is obtained from an external source such as CAN bus, a digital input or an A/D converter. Sources can be internal to to the display such as CPU temperature.
Channels (Outputs)
Non-visual objects that obtain information from one or more sources or other outputs. An output manipulates the obtained data according to the sensor associated with the output. The result can then be used in a Gauge or another Channel.
Sensors
Non-visual objects that define how the data is manipulated by an output. Examples of sensors are linear scalars, function tables or text tables. Sensors are selected and configured by changing the ’type’ of a Channel.
Gauges
Visual objects that are placed on a screen page. There are two types of gauge; static and dynamic.
Dynamic (Variable) Gauges change their appearance to reflect data obtained from channels. Examples of variable gauges are Bar Gauges
, Tacho Gauges
and Value Gauge
.
The following diagram shows the relationship between sources, outputs, sensors and gauges:
In this example, the raw RPM value is passed to the scaled RPM output which uses a scalar sensor to provide its’ output. This is passed to both a bar tacho gauge (which displays the RPM) and the oil pressure alarm output. The oil pressure is obtained in a similar manner and passes its’ output to a bar gauge (which displays the oil pressure) and the oil pressure alarm output. The oil pressure alarm output uses the alarm sensor and its’ two inputs to generate an output used by the warning gauge to signal low oil pressure, eg Oil Pressure is less than 2 and engine RPM is greater than 500.
Opening and Saving Setups
Opening a Setup
To Open an existing colour display setup:
Select File | Open Setup.... The file open dialog is shown.
Select the required display setup file and click Open.
Recently opened or saved files can be accessed from the sub-menu File | Recent Files.
Setup files may also be opened by dragging them onto the Dash Design window.
If Configure | Open Last Setup at Startup is checked, the last setup is opened when Dash Design starts; otherwise you are asked what to do.
The Setup File Dialog
Dash Design uses its own dialog for opening and saving setup files:
The toolbar provides Back, Forward and Up navigation, New Folder and Refresh. Frequently used folders may be added to the favourites list using Add Favourite.
The Type filter selects which files are listed, for example All Setup Files, Unlocked Setup Files, Locked Setup Files or Screen Packages.
The Notes panel shows the notes stored in the selected setup file. When saving, the notes may be edited and are saved with the setup.
Thumbnails of the screens in the selected setup are shown where available.
Click OS File Dialog to use the standard Windows® file dialog instead.
If the editor is in Locked Layout mode, only certain gauge properties can be edited and the gauge positions are fixed to prevent accidental editing.
Layout Locked mode can be toggled by selecting File | Lock Layout or by clicking the Edit Layout icon at the top left of the screen design area.
Saving a Setup
To save a setup under a new filename, select File | Save Setup As...Ctrl + Shift + S, enter a file name in the file save dialog and click the Save button.
To save a setup with the current name, select File | Save SetupCtrl + S.
To save the setup under a new file name with an incremented version number, select File | Save New VersionCtrl + Alt + S.
To close the current setup, select Close Setup.
If a setup or Dash Design is closed and the setup has changed since the last save, a prompt will appear asking if the changes to the setup are to be saved. Select Save As to save the changes (possibly with a new file name), Discard to abandon the changes or Cancel to return to editing the current setup.
Uploading a Setup to a Display
Overview
Uploading a setup programs the current setup into the Display Module.
Tip
View the Setup Checker to ensure there are no setup errors or warnings prior to programming the setup.
Ensure that the Display Module is attached to the PC. Ethernet based Display Modules may be attached directly to the PC with an ethernet cable or to a Local Area Network (LAN).
Display Modules that connect using USB should show a special screen once attached to the PC.
Select File | Upload To DisplayF7. A dialog will be shown to allow selection of the Display Module that should be programmed:
Upload Setup Dialog
Select the Display Module to be programmed from the list. Typically there will only be one so the first item is selected by default.
Upload Original Setup
Depending upon the type of Display Module, there may be the option Upload original setup. When programming displays, the setup file is compiled into a more compact format that is understood by the display. If Upload Original Setup is checked, then the original setup file will also be programmed into the display to allow later recovery of the original setup used to program the display from the Display Module itself using the command File | Download From Display.
Starting the Programming Procedure
Click the Upload button to begin programming the setup into the display.
If the setup’s display type does not match the connected display, a warning is shown. Choose Continue Anyway to upload the setup (it may not function correctly) or Cancel. Some display types do not allow a mismatched setup to be programmed.
If programming requires the logged data in the display to be erased, you are asked to confirm before continuing.
Programming Progress
The progress of the procedure will be shown, along with a log of messages:
Upload Setup Progress
If the process fails, refer to the message log as it may identify the cause.
Firmware Compatibility
When programming, Dash Design checks the features used by the setup against the firmware version of the display. The firmware versions required by the setup are shown in the programming log, and warnings are shown if the setup uses features that the display firmware does not support. If the firmware version can’t be determined, these warnings are not shown.
Once the programming is complete, the Display Module may be disconnected from the PC. For USB connections, detaching the USB cable should cause the setup to run on the display.
Downloading the Original Setup
If the setup was programmed with Upload original setup checked, the original setup file can be recovered from the display using File | Download From Display.
Firmware Updates
Overview
Over time, updates to the Display Module firmware may become available that resolve bugs and add new features.
Dash Design may be used to re-flash the Display Module with new firmware.
Firmware Update Procedure
Ensure that the Display Module is attached to the PC. Ethernet based Display Modules may be attached directly to the PC with an ethernet cable or to a Local Area Network (LAN).
Display Modules that connect using USB should show a special screen once attached to the PC.
Select Tools | Upload Firmware.... A dialog will be shown to allow selection of the Display Module that should be programmed.
Select the Display Module to be programmed from the list. Typically there will only be one so the first item is selected by default.
Select a firmware file (*.bin) using the Firmware Filename picker. File paths can be pasted here or browsed using the … button. Recently used firmware files can be selected from the drop-down list.
Click the Upload button to begin programming the firmware into the display.
Programming Progress
The progress of the procedure will be shown, along with a log of messages.
Do not switch off the Display Module during the programming procedure as this may corrupt the firmware.
If the process fails, refer to the message log as it may identify the cause.
Once the programming is complete, the Display Module may be disconnected from the PC to reboot it.
CDX Model Firmware
For displays with a CDX Model processor, model firmware that is independent of the setup may be programmed using Tools | Program CDX Model Processor..., which opens the Upload CDX Model Firmware dialog, or erased using Tools | Erase Independent Model Firmware.... See CDX Model
.
Removing Unused Image Assets
Overview
During the course of editing a setup, graphic images may be added to the setup and as images are replaced or no longer required, the unused image files may be left stored in the setup, increasing both the size of the setup and the uploaded setup.
To remove unused images from the setup, see Images Tab
(Delete All Unused).
Removing unused images does not remove them from their original location on disk.
Exporting Image Assets
Overview
When an image (e.g. a bmp, png or jpeg file) is added to the setup, a copy of the original file is embedded in the setup together with the path to the original file location. This allows for the original bitmap to be updated and the bitmap in the setup to be updated by clicking the reload button.
When setups are shared with other users, the original bitmaps may not be present on the new user’s computer. The export function allows images to be exported from the setup to files on the new user’s computer. Multiple images may be exported to a folder at once.
Exporting does not change the original file locations stored in the setup. To update an image from a file in a new location, use Replace on the Images Tab
.
Setups may be saved to files that are locked from editing and may only be programmed to displays. Locked setups include thumbnails of screens for preview purposes.
Locked setups have the file extension .gddp.
Exporting Locked Setups
To export a locked setup, use the File | Export Compiled / Locked Setup... command. The Locked Setup Options dialog is shown before the file is saved.
Locked setups may be loaded into Dash Design and programmed with File | Upload To DisplayF7. When programming a locked setup, Dash Design checks that the display firmware supports the features used by the setup.
Locked Setup Options
Option
Description
Embed Setup File Name (visible to users)
Includes the original setup file name in the locked setup. The file name may be edited to remove any user information or it could be changed to a URL.
Embed Source Setup File
Embeds the original setup file in the locked setup. The original setup is LZMA compressed and AES-256 encrypted with a key cryptographically derived from the password and a ‘salt’ value.
Password / Confirm Password
The password required to extract the embedded source setup. Check Show Password to show the password as it is typed.
Lock to Serial Number?
Restricts the locked setup to one or more specific displays. Only available for displays that support serial number locked setups.
To lock the setup to specific displays, check Lock to Serial Number? and add the display serial numbers to the list. When adding serial numbers, several may be entered at once separated by commas.
When the export is complete, choose Open Setup to open the locked setup in Dash Design, Explore to show it in a new Explorer window or Close.
Automatically Saving Locked Setups
Dash Design can automatically save a locked version of the setup, for example for external simulators or scrutineering. This is configured in the Locked Setup Auto Save section of Configure | Preferences...Alt + F7:
Preference
Description
Auto Save
Never, On Save (whenever the setup is saved) or When Programming (whenever the setup is programmed into a display).
Auto Save Naming
Match Setup Name uses the setup file name, MD5 names the file using the setup binary checksum (the Checksum shown on the File Info Tab) and Match Setup.<MD5> adds the checksum to the setup file name.
Overwrite Mode
Always Ask, Always Overwrite or Never overwrite an existing locked setup file.
The locked setup is saved in the same folder as the setup file. When asked whether to overwrite an existing locked setup, check Don’t ask again this session or Don’t ask again ever to stop further prompts; the latter can be re-enabled in the preferences.
File Info Tab
The File Info tab provides information about the locked setup file. The File Info tab is only available when a locked setup file is loaded into Dash Design.
Setup Binary
The ‘compiled’ setup binary is the data that is programmed into the Display Module.
Field
Description
Size
The size of the setup binary.
Checksum
The checksum of the setup binary (a seeded MD5 checksum), which should match the checksum calculated by the display module when the setup is loaded. Shown when Show additional hashes is checked.
SHA-1
SHA-1 hash of the setup binary. Shown when Show additional hashes is checked.
Check Show additional hashes to show the SHA-1 and MD5 hashes. This choice is saved in the application preferences.
Source Setup
The source setup is the setup that was used to create the locked setup.
The file name of the source setup, if it was embedded in the locked setup.
Size
The size of the embedded source setup, or Source setup not embedded.
MD5
MD5 sum of the setup file that the locked setup was generated from. Shown when Show additional hashes is checked.
SHA-1
SHA-1 hash of the setup file that the locked setup was generated from. Shown when Show additional hashes is checked.
Click Explore to open the source setup File Name location in Windows® File Explorer.
If the original setup file is embedded in the locked setup, click Extract Setup to extract it. Enter the password that was used when the locked setup was exported, then choose where to save the extracted setup.
Notes
The Notes section shows the locked setup’s notes (read only).
Raw Setups
Overview
Setups may be saved to ‘raw’ setup files for programming with external tools. Raw setups can’t be opened or programmed from Dash Design.
Tip
If you want to make a non-editable setup that can be programmed with Dash Design, see Locked Setups
.
Exporting Raw Setups
To export a raw setup, use either the File | Export Raw | Export Raw Setup (Packaged)... or File | Export Raw | Export Raw Setup (Unpackaged)... command.
Use File | Export Raw | Export Raw Setup (Packaged)... for tools that expect packaged raw setups (e.g. commissioning / programming tools). Packaged setup files include some additional information about the setup (e.g. Display Module type) that the tool can use for file validation.
Packaged raw setups have the file extension .rawsetup.
Use File | Export Raw | Export Raw Setup (Unpackaged)... for tools that do not expect any setup packaging (e.g. a Display Module external simulator).
XML Setup Import / Export
Overview
For external editing of setup files in a text editor or comparison using a merge tool, setups can be converted to an XML based format.
Use the File | Export Setup to XML... and File | Import Setup from XML... menu actions to export / import XML based setups.
XML Format
The best way to get a feel for the XML format is to export a setup and look at the generated XML in a text editor such as VS Code.
Tip
Use a tool such as WinMerge to compare the XML files to see what has changed between versions of the file.
display_setup - the root node defines the display type and screen size.
notes - Includes any notes from the setup file entered in the ‘save setup’ dialog.
setup_name - The setup name, as set on the Setup Name
page.
on_at_startup - Initial 5V supply state: true for On, false for Off.
inputs - Optional control input, using input id=“117” and the channel name.
Zero switches the supply Off; any non-zero value switches it On.
can_ports - groups can_port nodes.
can_port - describes a single CAN Port.
index - The CAN port number, starting at 0.
bitrate - The CAN port speed setting.
termination_resistor - Enable / Disable software selectable CAN bus termination resistor.
can_xcp_device_tx_id / can_xcp_device_rx_id - The XCP device transmit / receive CAN IDs, if XCP is enabled on the port.
monitor_all - The Monitor Any CAN Message setting, for applicable displays.
monitor_defined - The Monitor All Defined CAN Messages setting, for applicable displays.
can_status_tx_id - The CAN ID of the display status message, for applicable displays.
can_channels - groups can_channel nodes.
can_channel - describes a single CAN channel.
name - The name of the CAN channel.
protected - Indicates a protected (hidden) model IPC signal.
id - The CAN ID.
rate_ms - The message rate in milliseconds, used when exporting to DBC files (the Rate [ms] property).
bit - The bit position of the data in the CAN message.
length - The length of the data in bits.
dbc_type - The data type of the data.
endian - The byte order of the data.
signed - Indicates that the raw value is signed.
factor / offset / reciprocal - The scaling of the raw value.
units - The base units of the signal.
comment - The signal comment, e.g. imported from a DBC file.
canmask - The mask to apply to the CAN ID.
can_data_type - The legacy CAN data type.
bytemask - The legacy byte mask.
comcodex - The COM codex to use.
initial_value - The initial (raw) value of the signal.
multiplex_mode / multiplex_index - The multiplexing of the signal (see CAN Message Overview
).
output - describes the output of the CAN channel.
name - The name of the output.
sensor - describes the sensor used by the output.
shared - The name of the shared sensor, if not supplying sensor values in-line. See shared_sensors node.
type - The type of the sensor.
name - The name of the sensor.
factor - The factor to apply to the sensor value.
offset - The offset to apply to the sensor value.
channels - groups channel nodes.
channel - describes a single channel.
type - The type of the channel.
output_type - The output type of the channel.
predefined - Indicates if the channel is predefined.
name - The name of the channel.
input_units / output_units / display_units - The channel’s units (see Channels Tab
).
units_mode - The display units policy: Preferences (Match Preferences), MatchOutput, Override or Disallowed.
filters - groups filter nodes describing the channel’s in-place filter chain. Each filter has a modifier_type (see Filter Channel
).
inputs - groups input nodes.
input - describes a single input.
id - The ID of the input.
For the predefined EVENT MGR channel, the page-selection input
also preserves the chosen page-numbering mode.
sensor - describes the sensor used by the channel. The properties vary depending on the sensor type. The library attribute indicates a sensor from the Sensor Library Channel
.
shared - The name of the shared sensor, if not supplying sensor values in-line. See shared_sensors node.
type - The type of the sensor.
name - The name of the sensor.
factor - The factor to apply to the sensor value.
offset - The offset to apply to the sensor value.
pre_delay - The pre-delay to apply to the sensor value.
retrigger_time - The retrigger time to apply to the sensor value.
conditions - groups condition nodes.
condition - describes a single condition.
comparator - The comparator to use.
limit - The limit to compare against.
logic - The logic to apply to the condition.
items - groups item nodes.
item - describes a single item.
value - The value of the item.
on_time - The on time of the item.
off_time - The off time of the item.
max_duration - The max duration of the item.
graphic - The graphic to use for the item.
pages - groups page nodes.
page - describes a single page.
properties - properties of the page.
screenId - The screen ID of the page.
name - The name of the page.
colour - The colour of the page.
tags - groups item nodes.
item - describes a single item.
favourite - The favourite setting of the page.
defaultBgColour - The default background colour of the page.
defaultLineColour - The default line colour of the page.
defaultFillColour - The default fill colour of the page.
defaultTextColour - The default text colour of the page.
defaultWarningColour - The default warning colour of the page.
defaultFont - groups name and size nodes.
name - The name of the font.
size - The size of the font.
keypad_events - groups keypad_event nodes.
keypad_event - describes a single keypad event.
key_id - The ID of the key.
event_type - The type of the event.
key_type - The type of the key.
priority - The priority of the event.
output - The output of the event.
events - groups event nodes.
event - describes a single event.
gauges - groups gauge nodes.
gauge - describes a single gauge.
type - The type of the gauge.
properties - groups properties nodes.
name - The name of the gauge.
input - The input of the gauge.
left - The left position of the gauge.
top - The top position of the gauge.
width - The width of the gauge.
height - The height of the gauge.
lineColour - The line colour of the gauge.
backgroundColour - The background colour of the gauge.
fillColour - The fill colour of the gauge.
startValue - The start value of the gauge.
endValue - The end value of the gauge.
segmentSize - The segment size of the gauge.
labelColour - The label colour of the gauge.
labelFont - groups name and size nodes.
name - The name of the font.
size - The size of the font.
barTachoRectangular - The bar tacho rectangular setting of the gauge.
separatorsBetweenBars - The separators between bars setting of the gauge.
smoothEdges - The smooth edges setting of the gauge.
formatString - The format string of the gauge.
labelFrequency - The label frequency of the gauge.
labelDivisor - The label divisor of the gauge.
lowerLimitEnabled - The lower limit enabled setting of the gauge.
lowerLimitEnd - The lower limit end of the gauge.
lowerLimitColour - The lower limit colour of the gauge.
upperLimitEnabled - The upper limit enabled setting of the gauge.
upperLimitStart - The upper limit start of the gauge.
upperLimitColour - The upper limit colour of the gauge.
lowerLimitFlash - The lower limit flash setting of the gauge.
upperLimitFlash - The upper limit flash setting of the gauge.
flashAllEnabled - The flash all enabled setting of the gauge.
flashAllStart - The flash all start of the gauge.
flashRate - The flash rate of the gauge.
caption - The caption of the gauge.
textColour - The text colour of the gauge.
font - groups name and size nodes.
name - The name of the font.
size - The size of the font.
textJustify - The text justify setting of the gauge.
backgroundColour - The background colour of the gauge.
formatString - The format string of the gauge.
specialFormat - The special format of the gauge.
colourMode - The colour mode of the gauge.
graphicInput - The graphic input of the gauge.
graphic - The graphic of the gauge.
animation_data - For animation gauges, the animation data, base-64 encoded.
shared_sensors - groups sensor nodes. Shared sensors are referenced by channels.
sensor - describes a single sensor. The properties vary depending on the sensor type.
name - The name of the sensor.
type - The type of the sensor.
factor - The factor to apply to the sensor value.
offset - The offset to apply to the sensor value.
pre_delay - The pre-delay to apply to the sensor value.
retrigger_time - The retrigger time to apply to the sensor value.
conditions - groups condition nodes.
condition - describes a single condition.
comparator - The comparator to use.
limit - The limit to compare against.
logic - The logic to apply to the condition.
colour_map_presets - groups preset nodes defining colour map presets used by gauges.
graphics - groups graphic nodes.
graphic - describes a single graphic.
filename - The file name of the graphic, used by references in the setup.
width - The width of the graphic.
height - The height of the graphic.
size_bytes - The total number of bytes in the image data.
data - The data of the graphic, base-64 encoded.
led_rules - For display with rule-based LED setup, defines the LED configuration.
group - LED group definition.
name - The name of the LED group.
leds - groups led nodes. The “All Screens” group is special and should not be moved/removed.
led - describes a single LED.
name - The name of the LED.
pages - JSON object containing array of page IDs that the LED group is active on.
rule - Set of conditions and LED patterns.
conditions - JSON object containing array of conditions.
A channel that performs mathematical operations on its input values. See Maths Channel
CDTimer
Countdown Timer
A channel that counts down from a time value. See Timers Tab
Stopwatch
Stopwatch
A channel that counts up from a time value. See Timers Tab
PerformanceTimer
Performance Timer
A channel that measures the time between two events. See Timers Tab
CanOutput
CAN Output
A channel that outputs its input value to a CAN message. See CAN Transmit
LapTime
Lap Time
A channel that outputs a lap timing related quantity. See Lap Timing Channels
Toggle
Toggle
A channel that toggles between two states, based upon an event. See Toggle Channel
Case
Case
A channel that outputs a value depending on which input value is ’true’. See Case Channel
If
If
A channel that outputs a value depending on the value of its input. See If Channel
OnChange
On Change
A channel that outputs a value when its input changes. See On Change Channel
Example XML Structure
This example covers most of the node types that can be exported. The structure differs considerably from version 1 of Dash Design.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><display_setuptype="CD6-43"OriginalFilename="{path}/CD6-43 Setup.cd6-43.gdd"XMLFilename="{path}/CD6-43 Setup.xml"screen_width="800"screen_height="480"><notes>Added air temperature sensing.</notes><can_ports><can_port><index>0</index><bitrate>1M</bitrate><termination_resistor>0</termination_resistor><can_channels><can_channel><name>RPM CAN</name><id>#4A9</id><bit>8</bit><length>16</length><dbc_type>unsigned</dbc_type><endian>msb_first</endian><canmask>3</canmask><comcodex>0</comcodex><outputtype="Scalar"output_type="1"><name>RPM</name><sensorshared="x1 scalar"type="Scalar"/></output></can_channel><can_channel><name>AIR TEMP CAN</name><id>#4A9</id><bit>24</bit><length>8</length><dbc_type>unsigned</dbc_type><canmask>8</canmask><outputtype="Scalar"output_type="1"><name>AIR TEMP CAN</name><sensortype="Scalar"name="AIR TEMP CAN_scalar"><factor>1.0</factor><offset>0.0</offset></sensor></output></can_channel></can_channels></can_port><can_port><index>1</index><bitrate>1M</bitrate><termination_resistor>0</termination_resistor><can_channels/></can_port></can_ports><channels><channeltype="EventManager"output_type="1"predefined="1"><name>EVENT MGR</name><inputs><inputid="1">Page Select</input><inputid="3">Brightness</input><inputid="4">Page Select</input></inputs><sensorshared="EVENT MGR"type="EventManager"/></channel><channeltype="Scalar"output_type="1"predefined="1"><name>A00 Raw</name><inputs><inputid="1">A00 A/D</input></inputs></channel><channeltype="Scalar"output_type="1"><name>Internal status</name><sensortype="Scalar"name="Internal status:Value_scalar"><factor>1.0</factor><offset>0.0</offset></sensor></channel><channeltype="Logic"output_type="1"><name>FuelAlarm</name><inputs><inputid="1">Fuel</input></inputs><sensortype="Logic"name="FuelAlarm_Alarm_"><pre_delay>0</pre_delay><retrigger_time>0</retrigger_time><conditions><condition><comparator>Less</comparator><limit>0.25</limit><logic>None</logic></condition></conditions></sensor></channel><channeltype="BitmapSelector"output_type="2"><name>FuelBitmaps</name><inputs><inputid="1">FuelAlarm</input></inputs><items><item><value>0.0</value><on_time>0.0</on_time><off_time>0.0</off_time><max_duration>0.0</max_duration><graphic>C:/Graphics/FuelIconGrey.bmp</graphic></item><item><value>1.0</value><on_time>0.0</on_time><off_time>0.0</off_time><max_duration>0.0</max_duration><graphic>C:/Graphics/FuelIconRed.bmp</graphic></item></items><sensorshared="Bitmap Sel"type="BitmapSelector"/></channel><channeltype="Notification"output_type="2"><name>Warning Message</name><items><item><message>Low Battery @</message><format>##.#</format><input>Bat Alarm</input><label_input>Batt Volts</label_input></item><item><message>Coolant High @</message><format>###</format><input>Coolant Alarm</input><label_input>Coolant T</label_input></item></items><sensorshared="Warning Message"type="Notification"/></channel><pages><pageid="0"><properties><screenIdvalue="All Screens"/><namevalue=""/><colour>#000000</colour><tags/><favouritevalue="0"/><defaultBgColour>#161D1F</defaultBgColour><defaultLineColour>#C0C0C0</defaultLineColour><defaultFillColour>#FDB813</defaultFillColour><defaultTextColour>#C0C0C0</defaultTextColour><defaultWarningColour>#FF0000</defaultWarningColour><defaultFont><name></name><size>18</size></defaultFont></properties><keypad_events><keypad_event><key_id>1</key_id><event_type>2</event_type><key_type>0</key_type><priority>1</priority><output>Distance Trip</output></keypad_event><keypad_event><key_id>1</key_id><event_type>2</event_type><key_type>1</key_type><priority>1</priority><output>Distance Trip</output></keypad_event><keypad_event><key_id>1</key_id><event_type>2</event_type><key_type>2</key_type><priority>1</priority><output>Distance Trip</output></keypad_event></keypad_events><events/><gauges/></page><pageid="1"><properties><screenIdvalue="1"/><namevalue=""/><colour>#000000</colour><enabledvalue="1"/><tags/><favouritevalue="0"/><defaultBgColour>#008001</defaultBgColour><defaultLineColour>#000001</defaultLineColour><defaultFillColour>#00FF01</defaultFillColour><defaultTextColour>#00FF01</defaultTextColour><defaultWarningColour>#FF0001</defaultWarningColour><defaultFont><name>Arial</name><size>18</size></defaultFont></properties><events/><gauges><gaugetype="TEXT_INPUT"><properties><namevalue="Value Text: Gear Posn"/><inputvalue="Gear Posn"/><leftvalue="337"/><topvalue="180"/><textColour>#00FFFF</textColour><backgroundColour>#000001</backgroundColour><font><name>Open 24 Display St</name><size>300</size></font><textJustifyvalue="Left"/><colourModevalue="Normal"/></properties></gauge><gaugetype="BAR_TACHO"><properties><namevalue="Bar Tacho: RPM"/><inputvalue="RPM"/><leftvalue="6"/><topvalue="3"/><widthvalue="785"/><heightvalue="289"/><lineColour>#1A1A1A</lineColour><backgroundColour>#252525</backgroundColour><fillColour>#FFA500</fillColour><startValuevalue="0"/><endValuevalue="9000"/><segmentSizevalue="500"/><labelColour>#A9A9A9</labelColour><labelFont><name>Open 24 Display St</name><size>30</size></labelFont><barTachoRectangularvalue="0"/><separatorsBetweenBarsvalue="1"/><smoothEdgesvalue="0"/><formatStringvalue="#"/><labelFrequencyvalue="2"/><labelDivisorvalue="1000"/><lowerLimitEnabledvalue="0"/><lowerLimitEndvalue="0"/><lowerLimitColour>#008000</lowerLimitColour><upperLimitEnabledvalue="1"/><upperLimitStartvalue="8500"/><upperLimitColour>#FF0000</upperLimitColour><lowerLimitFlashvalue="0"/><upperLimitFlashvalue="1"/><flashAllEnabledvalue="1"/><flashAllStartvalue="8500"/><flashRatevalue="100"/></properties></gauge><gaugetype="VALUE"><properties><namevalue="Value: Road Speed"/><inputvalue="Road Speed"/><leftvalue="163"/><topvalue="0"/><textColour>#FFA500</textColour><font><name>Open 24 Display St</name><size>100</size></font><textJustifyvalue="Right"/><backgroundColour>#008001</backgroundColour><formatStringvalue="#"/><specialFormatvalue="None"/><colourModevalue="Normal"/></properties></gauge><gaugetype="TEXT"><properties><namevalue="Text: KPH"/><captionvalue="KPH"/><leftvalue="171"/><topvalue="19"/><textColour>#6E6E6E</textColour><font><name>Open 24 Display St</name><size>30</size></font><textDirectionvalue="Right"/><textJustifyvalue="Left"/><colourModevalue="Normal"/></properties></gauge><gaugetype="VALUE"><properties><namevalue="Value: Fastest Lap Time Delta"/><inputvalue=""/><leftvalue="600"/><topvalue="240"/><textColour>#FF1493</textColour><font><name>Open 24 Display St</name><size>56</size></font><textJustifyvalue="Left"/><backgroundColour>#008001</backgroundColour><formatStringvalue="msff"/><specialFormatvalue=""/><colourModevalue="Normal"/></properties></gauge><gaugetype="TEXT"><properties><namevalue="Text: Δ"/><captionvalue="Δ"/><leftvalue="520"/><topvalue="260"/><textColour>#FF1493</textColour><font><name>Open 24 Display St</name><size>30</size></font><textDirectionvalue="Right"/><textJustifyvalue="Left"/><colourModevalue="Normal"/></properties></gauge><gaugetype="VALUE"><properties><namevalue="Value: Last Lap Time"/><inputvalue=""/><leftvalue="600"/><topvalue="360"/><textColour>#C0C0C0</textColour><font><name>Open 24 Display St</name><size>56</size></font><textJustifyvalue="Left"/><backgroundColour>#008001</backgroundColour><formatStringvalue="msff"/><specialFormatvalue=""/><colourModevalue="Normal"/></properties></gauge><gaugetype="TEXT"><properties><namevalue="Text: Last"/><captionvalue="Last"/><leftvalue="520"/><topvalue="380"/><textColour>#C0C0C0</textColour><font><name>Open 24 Display St</name><size>30</size></font><textDirectionvalue="Right"/><textJustifyvalue="Left"/><colourModevalue="Normal"/></properties></gauge><gaugetype="VALUE"><properties><namevalue="Value: Fastest Lap Time"/><inputvalue=""/><leftvalue="600"/><topvalue="420"/><textColour>#00FF00</textColour><font><name>Open 24 Display St</name><size>56</size></font><textJustifyvalue="Left"/><backgroundColour>#008001</backgroundColour><formatStringvalue="msff"/><specialFormatvalue=""/><colourModevalue="Normal"/></properties></gauge><gaugetype="TEXT"><properties><namevalue="Text: Best"/><captionvalue="Best"/><leftvalue="520"/><topvalue="440"/><textColour>#00FF00</textColour><font><name>Open 24 Display St</name><size>30</size></font><textDirectionvalue="Right"/><textJustifyvalue="Left"/><colourModevalue="Normal"/></properties></gauge><gaugetype="HS_BAR"><properties><namevalue="HS Bar: Fuel"/><inputvalue="Fuel"/><leftvalue="10"/><topvalue="315"/><widthvalue="250"/><heightvalue="49"/><lineColour>#121212</lineColour><backgroundColour>#1F1F1F</backgroundColour><fillColour>#FF8C00</fillColour><startValuevalue="0"/><endValuevalue="1"/><segmentSizevalue="0.1"/><fillBarFromCenterHorizontalvalue="0"/><singleLineModevalue="0"/><separatorsBetweenBarsvalue="1"/><squareModevalue="0"/><cornerRadiusvalue="0"/></properties></gauge><gaugetype="HS_BAR"><properties><namevalue="HS Bar: Coolant T"/><inputvalue="Coolant T"/><leftvalue="10"/><topvalue="370"/><widthvalue="250"/><heightvalue="49"/><lineColour>#121212</lineColour><backgroundColour>#1F1F1F</backgroundColour><fillColour>#FF8C00</fillColour><startValuevalue="0"/><endValuevalue="150"/><segmentSizevalue="15"/><fillBarFromCenterHorizontalvalue="0"/><singleLineModevalue="0"/><separatorsBetweenBarsvalue="1"/><squareModevalue="0"/><cornerRadiusvalue="0"/></properties></gauge><gaugetype="HS_BAR"><properties><namevalue="HS Bar: Batt Volts"/><inputvalue="Batt Volts"/><leftvalue="10"/><topvalue="425"/><widthvalue="250"/><heightvalue="49"/><lineColour>#121212</lineColour><backgroundColour>#1F1F1F</backgroundColour><fillColour>#FF8C00</fillColour><startValuevalue="0"/><endValuevalue="15"/><segmentSizevalue="1.5"/><fillBarFromCenterHorizontalvalue="0"/><singleLineModevalue="0"/><separatorsBetweenBarsvalue="1"/><squareModevalue="0"/><cornerRadiusvalue="0"/></properties></gauge><gaugetype="BITMAP"><properties><namevalue="Image: charging_malf.bmp"/><graphicInputvalue="{path}/charging_malf.bmp"/><leftvalue="265"/><topvalue="428"/></properties></gauge><gaugetype="VALUE"><properties><namevalue="Value: Current Lap Time"/><inputvalue=""/><leftvalue="600"/><topvalue="300"/><textColour>#FFFFFF</textColour><font><name>Open 24 Display St</name><size>56</size></font><textJustifyvalue="Left"/><backgroundColour>#008001</backgroundColour><formatStringvalue="msff"/><specialFormatvalue=""/><colourModevalue="Normal"/></properties></gauge><gaugetype="TEXT"><properties><namevalue="Text: Lap"/><captionvalue="Lap"/><leftvalue="520"/><topvalue="320"/><textColour>#FFFFFF</textColour><font><name>Open 24 Display St</name><size>30</size></font><textDirectionvalue="Right"/><textJustifyvalue="Left"/><colourModevalue="Normal"/></properties></gauge><gaugetype="BITMAP"><properties><namevalue="Image: fuel_level.bmp"/><graphicInputvalue="{path}/fuel_level.bmp"/><leftvalue="265"/><topvalue="318"/></properties></gauge><gaugetype="BITMAP"><properties><namevalue="Image: oil_pressure.bmp"/><graphicInputvalue="{path}/oil_pressure.bmp"/><leftvalue="265"/><topvalue="373"/></properties></gauge><gaugetype="HS_BAR"><properties><namevalue="HS Bar: FakeLatG"/><inputvalue="FakeLatG"/><leftvalue="518"/><topvalue="191"/><widthvalue="280"/><heightvalue="49"/><lineColour>#282828</lineColour><backgroundColour>#000000</backgroundColour><fillColour>#FF0000</fillColour><startValuevalue="-1"/><endValuevalue="1"/><segmentSizevalue="0.1"/><fillBarFromCenterHorizontalvalue="1"/><singleLineModevalue="0"/><separatorsBetweenBarsvalue="1"/><squareModevalue="0"/><cornerRadiusvalue="0"/></properties></gauge></gauges></page><pageid="2"><properties><screenIdvalue="2"/><namevalue=""/><colour>#000001</colour><enabledvalue="1"/><tagslength="1"><item>tacho</item></tags><favouritevalue="0"/><defaultBgColour>#008001</defaultBgColour><defaultLineColour>#000001</defaultLineColour><defaultFillColour>#00FF01</defaultFillColour><defaultTextColour>#00FF01</defaultTextColour><defaultWarningColour>#FF0001</defaultWarningColour><defaultFont><name>Arial</name><size>18</size></defaultFont></properties><events/><gauges><gaugetype="RTACHO_BMP"><properties><namevalue="Needle: Road Speed"/><inputvalue="Road Speed"/><leftvalue="175"/><topvalue="29"/><widthvalue="451"/><heightvalue="451"/><lineColour>#1E90FF</lineColour><backgroundImagevalue="{path}/speed-tacho-270.png"/><transparentColour>#000000</transparentColour><transparentvalue="0"/><Needle_centreXvalue="225"/><Needle_centreYvalue="225"/><Needle_centreOffsetvalue="56"/><Needle_needleLengthvalue="183"/><Needle_startAnglevalue="30"/><Needle_endAnglevalue="330"/><Needle_baseWidthvalue="3"/><Needle_drawCentrevalue="0"/><startValuevalue="0"/><endValuevalue="200"/></properties></gauge></gauges></page></pages><shared_sensors><sensortype="Scalar"name="x1 scalar"><factor>1.0</factor><signed>0</signed></sensor><sensortype="BitString"name="Gear String"><bitstringsmatch_on_value="0"mask="0"><itemslength="9"><itempriority="1"mask="8"string="7"/><itempriority="2"mask="7"string="6"/><itempriority="3"mask="6"string="5"/><itempriority="4"mask="5"string="4"/><itempriority="5"mask="4"string="3"/><itempriority="6"mask="3"string="2"/><itempriority="7"mask="2"string="1"/><itempriority="8"mask="1"string="N"/><itempriority="9"mask="0"string="R"/></items></bitstrings></sensor><sensortype="Logic"name="Warning Trigger"><conditions><condition><comparator>Greater</comparator><limit>0.0</limit><logic>Or</logic></condition><condition><comparator>Greater</comparator><limit>0.0</limit><logic>None</logic></condition></conditions></sensor><sensortype="Notification"name="Warning Message"/><sensortype="BitmapSelector"name="Bitmap Sel"/><sensortype="FunctionTable"name="Contrast"><tablelowreal_t="2"lowreal="0"highreal_t="2"highreal="2500"lowraw_t="72"lowraw="0.0"highraw_t="72"highraw="63.0"interpolate="1"signed="0"><mapraw_t="2"raw="0"real_t="72"real="0.0"/><mapraw_t="2"raw="300"real_t="72"real="10.0"/><mapraw_t="2"raw="2500"real_t="72"real="63.0"/></table></sensor></shared_sensors><graphics><graphic><filename>{path}/Small Warning Black.bmp</filename><width>83</width><height>73</height><size_bytes>113</size_bytes><data>{base-64 data}</data></graphic><graphic><filename>{path}/Small Warning Triangle.bmp</filename><width>83</width><height>73</height><size_bytes>4416</size_bytes><data>{base-64 data}</data></graphic></graphics><led_rules><groupname="All Screens"predefined="1"><pages>{pages:[0]}</pages><rulename="marshal"priority="1"bitmask="229376"><conditions><condition><channel_avalue="A08 Raw"/><comparator_avalue="="/><value_avalue="1"/><channel_bvalue=""/><value_bvalue="0"/><leds><ledid="15"><colourvalue="ON"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led></leds><right_to_leftvalue="0"/><interpolation_channelvalue=""/><fromvalue="0"/><tovalue="0"/></condition><condition><channel_avalue="A08 Raw"/><comparator_avalue="="/><value_avalue="2"/><channel_bvalue=""/><value_bvalue="0"/><leds><ledid="15"><colourvalue="OFF"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="16"><colourvalue="ON"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led></leds><right_to_leftvalue="0"/><interpolation_channelvalue=""/><fromvalue="0"/><tovalue="0"/></condition><condition><channel_avalue="A08 Raw"/><comparator_avalue="="/><value_avalue="3"/><channel_bvalue=""/><value_bvalue="0"/><leds><ledid="15"><colourvalue="OFF"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="16"><colourvalue="OFF"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="17"><colourvalue="ON"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led></leds><right_to_leftvalue="0"/><interpolation_channelvalue=""/><fromvalue="0"/><tovalue="0"/></condition></conditions></rule></group><groupname="Driver"><pages>{pages: [1,2,3,4,5,7]}</pages><rulename="Shift Lights"priority="0"bitmask="32767"><conditions><condition><channel_avalue=""/><comparator_avalue="<>"/><value_avalue="0"/><channel_bvalue=""/><value_bvalue="0"/><leds><ledid="0"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="1"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="2"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="3"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="4"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="5"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="6"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="7"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="8"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="9"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="10"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="11"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="12"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="13"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led><ledid="14"><colourvalue="Green"/><channelvalue=""/><flash_colourvalue="OFF"/><flash_ratevalue="0"/></led></leds><pattern_modevalue="Interpolate"/><right_to_leftvalue="0"/><interpolation_channelvalue="RPM"/><fromvalue="0"/><tovalue="10000"/></condition></conditions></rule></group></led_rules></display_setup>
Converting Setups
Overview
A setup created for one display type may be converted to a different display type, for example when moving to a newer display model.
Use File | Convert Setup... to select a setup file and convert it, or File | Convert Current Setup... to convert the setup that is currently open.
Converting a Setup
Select the setup to convert (for File | Convert Setup... only).
In the Convert Setup To dialog, select the target display type from the list.
Check Resize Gauges and Fonts to scale gauges and fonts to the target display’s screen resolution. Uncheck it to keep the original positions and sizes.
Click OK. The conversion progress and any warnings are shown in the Convert Setup dialog.
The converted setup is opened in Dash Design. It is named after the original setup with " Converted" added (e.g. MySetup Converted) in the same folder; it is not saved until you save it. The original setup file is not modified.
Tip
Review the conversion log and run the Setup Checker
after converting a setup.
Conversion Warnings
Display types differ in the features they support, so some items may not be converted. The conversion log reports, for example:
Gauge types that are not supported by the target display.
Screens, CAN ports or predefined channels that the target display does not have.
Channels with sensor types that are not supported by the target display. Where possible, colour function tables are converted to colour maps.
Differences in page-select numbering between the source and target displays. See Page Select
.
Display-Specific Conversions
Some conversions adjust the setup for the target display:
When converting to or from LDS4, a warning is shown because LDS4 firmware variants use different page numbering conventions. Check whether the installed firmware requires 0 or 1 to select page 1.