Setup Checker

Overview

The setup checker identifies and in some cases automatically fixes common setup errors and warnings.

Showing the Setup Checker

The setup checker may be shown by using the View | Setup Check menu action or by double clicking on the setup check status indicator on the application status bar at the right-hand side:

Setup Checker Messages

Messages are listed with a severity:

Severity	Description
Error	Indicates a major issue in the setup that must be resolved prior to programming.
Warning	Indicates a minor issue that ought to be addressed otherwise the display may not behave as expected.
Info	Typically indicates something minor that has been fixed automatically.

Goto Location

Messages may be associated with an item in the setup. Double clicking on messages will attempt to locate the item in Dash Design and show it. For example, if the message relates to a Channel then Dash Design will display the Channels Tab and select the Channel.

Refresh

Some setup check messages are ‘sticky’ and will remain in the list until acknowledged (typically these are automatic fix notifications). Other messages are removed automatically when the offending condition has been resolved.

Click the Refresh button to clear all Setup check messages and re-run the setup check; this will clear any ‘sticky’ messages.

Checked Items

• CAN RX: ID range validity.
• CAN-FD data bit rate equals or exceeds port bit rate.
• CAN TX: Data Specification completeness.
• CAN TX: Do any signals exceed message DLC?
• CAN TX: Are any signals missing an input channel.
• Invalid keypad event trigger removal.
• Gauge charset conflicts (only applicable for display that support vector fonts).
• Refactoring of CAN sources from prior software versions for 1:1 link to outputs.
• Remove non-loggable channels from logging configuration on applicable display types.
• Logic channels: Validate that logic channel can reach both the on/off state. Misconfiguration of initial/retrigger delays or the logic itself may result in logic channels that will never ‘fire’. This includes issues where floating point rounding errors can result in non-functional logic channels.
• Monitored channels - Add monitoring on channels that require it for correct functioning and remove any dangling references from prior software versions.
• Remove any broken channel definitions that are not accessible in the software, typically from issues in prior software versions.
• Fix any predefined channels that were named/scaled differently in prior software versions.
• Validate that the Odometer channel is correctly configured with appropriate input units.
• Validate distance trip configuration.
• Validate and fix internal channel/gauge references.
• Check that maths channels have valid inputs.
• Check that ECU Text channels are directly derived from a Raw CAN source channel (otherwise they do not work in the display).
• Validate that unit conversions can be applied e.g. from channel Output Units => Display Units.
• Check that the Speed Input channel has units of speed specified.
• Check and remove invalid alarm page triggers.
• Check compatibility of bar gauge input data type - warn if time inputs are used directly.
• Check for valid Format property on gauges.
• Check that gauges have valid input channels and warn if missing.
• Validate that image gauges have a valid image (e.g. the image was not removed from the setup).
• Check for out-of-bounds rendering (e.g. on Needle gauge).