This repository holds
- instructions for building a Dash Gauge panel, as seen in the Delorean Time Machine,
- and a suitable firmware.
This panel is meant as an add-on for the CircuitSetup Time Circuits Display as it relies on the TCD's keypad to control many of its functions.
 |
|---|
| Click to watch the video |
For information on the hardware, please see here.
Firmware features include
- support for analog gauges (with software-controlled arbitrary pointer position) and digital gauges (Empty/Full, without arbitrary pointer position)
- selectable "full" percentages per analog gauge (besides for fun, useful for adjusting inaccurate readings)
- selectable threshold percentage for Empty/Full position for digital gauges
- Time Travel function, triggered by button, Time Circuits Display (TCD) or via MQTT
- support for Side Switch to play "empty" and "refill" sequences
- Automatic refill timer, automatic alarm mute timer (both optional)
- easy expandability to support different gauges hardware (currently implemented: variable voltage (0-5V); digital [on/off, all or separate])
- Support for door switches for playing sounds when opening/closing the car doors
- Wireless communication with Time Circuits Display; used for synchonized time travels, alarm, night mode, fake power and remote control through TCD keypad
- Music player: Play mp3 files located on an SD card [requires TCD connected wirelessly for control]
- SD card support for custom audio files for effects, and music for the Music Player
- Advanced network-accessible Config Portal for setup (http://gauges.local, hostname configurable)
- Home Assistant (MQTT 3.1.1) support
- Built-in installer for default audio files in addition to OTA firmware updates
If a previous version of the Dash Gauges firmware is installed on your device's ESP32, you can update easily using the pre-compiled binary. Enter the Config Portal, click on "Update" and select the pre-compiled binary file provided in this repository (install/dashgauges-A10001986.ino.nodemcu-32s.bin).
If you are using a fresh ESP32 board, please see dashgauges-A10001986.ino for detailed build and upload information, or, if you don't want to deal with source code, compilers and all that nerd stuff, go here and follow the instructions.
Important: After a firmware update, the "empty" LED might blink for short while after reboot. Do NOT unplug the device during this time.
The firmware comes with audio data ("sound-pack") which needs to be installed separately. The audio data is not updated as often as the firmware itself. If you have previously installed the latest version of the sound-pack, you normally don't have to re-install the audio data when you update the firmware. Only if either a new version of the sound-pack is released, or your device is quiet after a firmware update, a re-installation is needed.
The first step is to download "install/sound-pack-xxxxxxxx.zip" and extract it. It contains one file named "DGA.bin".
Then there are two alternative ways to proceed. Note that both methods require an SD card.
-
Through the Config Portal. Click on Update, select the "DGA.bin" file in the bottom file selector and click on Upload. Note that an SD card must be present during this operation.
-
Via SD card:
- Copy "DGA.bin" to the root directory of of a FAT32 formatted SD card;
- power down the Dash Gauges,
- insert this SD card into the slot and
- power up the Dash Gauges; the audio data will be installed automatically.
After installation, the SD card can be re-used for other purposes.
The following instructions only need to be followed once, on fresh Dash Gauges. They do not need to be repeated after a firmware update.
The first step is to establish access to the configuration web site ("Config Portal") in order to configure your Dash Gauges:
- Power up the device and wait until the startup sequence has completed.
- Connect your computer or handheld device to the WiFi network "DG-AP".
- Navigate your browser to http://gauges.local or http://192.168.4.1 to enter the Config Portal.
As long as the device is unconfigured, it creates a WiFi network of its own named "DG-AP". This is called "Access point mode", or "AP-mode".
It is ok to leave the Dash Gauges in this mode, especially if it run stand-alone. In a typical home setup and/or if you also have a Time Circuits Display, however, you might want to connect the Dash Gauges to a WiFi network (in case of using it together with a TCD: to the same WiFi network the TCD is connected to). If you have your Dash Gauges, along with a Time Circuits Display, mounted in a car, you might want to connect the Dash Gauges to the TCD's very own WiFi network "TCD-AP"; see here.
In order to connect your Dash Gauges to a WiFi network, click on "Configure WiFi". The bare minimum is to select an SSID (WiFi network name) and a WiFi password.
Note that the device requests an IP address via DHCP, unless you entered valid data in the fields for static IP addresses (IP, gateway, netmask, DNS). If the device is inaccessible as a result of incorrect static IPs,
- power-down the device,
- hold the Time Travel button,
- power-up the device (while still holding the Time Travel button)
- wait until the "Empty" LED flashes briefly,
- flip the Side Switch twice within 10 seconds,
- wait until the "Empty" LED lights up,
- then release the Time Travel button.
This procedure causes static IP data to be deleted; the device will return to DHCP after a reboot.
After saving the WiFi network settings, the device reboots and tries to connect to your configured WiFi network. If that fails, it will again start in access point mode.
After completing this step, your Dash Gauges are ready to be configured through the "Config Portal".
The "Config Portal" is the Dash Gauges' configuration web site.
 |
|---|
| The Config Portal's main page |
It can be accessed as follows:
- Connect your computer or handheld device to the WiFi network "DG-AP".
- Navigate your browser to http://gauges.local or http://192.168.4.1 to enter the Config Portal.
-
Connect your hand-held/computer to the same WiFi network to which the Dash Gauges are connected, and
-
navigate your browser to http://gauges.local
Accessing the Config Portal through this address requires the operating system of your hand-held/computer to support Bonjour/mDNS: Windows 10 version TH2 (1511) [other sources say 1703] and later, Android 13 and later; MacOS and iOS since the dawn of time.
If connecting to http://gauges.local fails due to a name resolution error, you need to find out the Gauges' IP address. In order to do so, hold "Button 1" on the Control Board for 2 seconds, and listen. The IP address will be spoken out loud. Then, on your handheld or computer, navigate to http://a.b.c.d (a.b.c.d being the IP address as just given by the Dash Gauges) in order to enter the Config Portal.
In the main menu, click on "Setup" to configure your Dash Gauges.
 |
|---|
| Click for full screenshot |
A full reference of the Config Portal is here.
The firmware needs to know the type of gauges installed; by default, power output to the gauges is disabled.
In order to configure the Dash Gauges for your specific hardware,
- hold the "Time Travel" button for 5 seconds (until a beep is emitted),
- then enter the Config Portal as described above, and click on "Setup".
Near the bottom of this page, there are three drop-down widgets, one for each gauge. Carefully select the type for each of your gauges, and click on "Save".
After this step, your Dash Gauges are ready to be used.
As mentioned, the Dash Gauges are an add-on for a Time Circuits Display. Their basic function is to show some values on its gauges, and to play an "empty" alarm after a time travel.
There is little to play with when the Dash Gauges aren't connected to a TCD:
- To quickly trigger the "empty" sequence, flip the side switch of your Dash Gauges. To "refill", flip that switch again.
- Press the time travel button to trigger a simple "surge" sequence.
The Dash Gauges are way more fun when other props (TCD, FC, SID) are present as well. The TCD is of special importance: When connected through BTTFN, the TCD can act as a remote control for the Dash Gauges.
| Special sequences (⏎ = ENTER key) |
|
| Function | Code on TCD |
| "Refill" | 009⏎ |
| Set "full" percentage of "Primary" gauge (01-99%) | 9101⏎ - 9199⏎ |
| Reset "full" percentage of "Primary" gauge | 9100⏎ |
| Set "full" percentage of "Percent Power" gauge (01-99%) | 9401⏎ - 9499⏎ |
| Reset "full" percentage of "Percent Power" gauge | 9400⏎ |
| Set "full" percentage of "Roentgens" gauge (01-99%) | 9701⏎ - 9799⏎ |
| Reset "full" percentage of "Roentgens" gauge | 9700⏎ |
| Set volume level (00-19) | 9300⏎ - 9319⏎ |
| Music Player: Play/Stop | 9005⏎ |
| Music Player: Previous song | 9002⏎ |
| Music Player: Next song | 9008⏎ |
| Music Player: Select music folder (0-9) | 9050⏎ - 9059⏎ |
| Music Player: Shuffle off | 9222⏎ |
| Music Player: Shuffle on | 9555⏎ |
| Music Player: Go to song 0 | 9888⏎ |
| Music Player: Go to song xxx | 9888xxx⏎ |
| Play "key1.mp3" | 9001⏎ |
| Play "key3.mp3" | 9003⏎ |
| Play "key4.mp3" | 9004⏎ |
| Play "key6.mp3" | 9006⏎ |
| Play "key7.mp3" | 9007⏎ |
| Play "key9.mp3" | 9009⏎ |
| Say current IP address | 9090⏎ |
| Reboot the device | 9064738⏎ |
| Delete static IP address and WiFi-AP password |
9123456⏎ |
| Unlock "gauge type" selection in Config Portal | 9317931⏎ |
To trigger a "time travel" stand-alone, you need to install a "Time Travel" button. Pressing that button briefly will let the Dash Gauges play their time travel sequence. Please see here for how to wire that button.
Other ways of triggering a time travel are available if a Time Circuits Display is connected.
Preface note on SD cards: For unknown reasons, some SD cards simply do not work with this device. For instance, I had no luck with Sandisk Ultra 32GB and "Intenso" cards. If your SD card is not recognized, check if it is formatted in FAT32 format (not exFAT!). Also, the size must not exceed 32GB (as larger cards cannot be formatted with FAT32). Transcend SDHC cards and those work fine in my experience.
The SD card, apart from being required for installing of the built-in audio data, can be used for substituting built-in sound effects and for music played back by the Music player. Also, it is strongly recommended to store secondary settings on the SD card to minimize Flash Wear.
Note that the SD card must be inserted before powering up the device. It is not recognized if inserted while the Dash Gauges are running. Furthermore, do not remove the SD card while the device is powered.
The Dash Gauges' built-in sound effects can be substituted by your own sound files on a FAT32-formatted SD card. These files will be played back directly from the SD card during operation, so the SD card has to remain in the slot.
Your replacements need to be put in the root (top-most) directory of the SD card, be in mp3 format (128kbps max) and named as follows:
- "startup.mp3". Played when the Dash Gauges are connected to power and finished booting;
- "refill.mp3". Played during the "refill"-sequence;
- "alarm.mp3". Played when the alarm sounds (triggered by a Time Circuits Display via BTTFN or MQTT);
- "0.mp3" through "9.mp3", "dot.mp3": Numbers for IP address read-out.
- "dooropen.mp3"/"doorclose.mp3": Played when the state of the door switch changes.
The firmware supports some additional user-provided sound effects, which it will load from the SD card. If the respective file is present, it will be used. If that file is absent, no sound will be played.
- "key1.mp3", "key3.mp3", "key4.mp3", "key6.mp3", "key7.mp3", "key9.mp3": Will be played when you type 900x (x being 1, 3, 4, 6, 7 or 9) on the TCD (connected through BTTFN).
The seemingly odd numbering is because of synchronicity with other props, especially the TCD and its keymap where the MusicPlayer occupies keys 2, 5, 8.
Those files are not provided here. You can use any mp3, with a bitrate of 128kpbs or less.
The firmware contains a simple music player to play mp3 files located on the SD card. This player requires a TCD connected through BTTFN for control.
In order to be recognized, your mp3 files need to be organized in music folders named music0 through music9. The folder number is 0 by default, ie the player starts searching for music in folder music0. This folder number can be changed in the Config Portal or through the TCD keypad (905x).
The names of the audio files must only consist of three-digit numbers, starting at 000.mp3, in consecutive order. No numbers should be left out. Each folder can hold up to 1000 files (000.mp3-999.mp3). The maximum bitrate is 128kpbs.
Since manually renaming mp3 files is somewhat cumbersome, the firmware can do this for you - provided you can live with the files being sorted in alphabetical order: Just copy your files with their original filenames to the music folder; upon boot or upon selecting a folder containing such files, they will be renamed following the 3-digit name scheme (as mentioned: in alphabetic order). You can also add files to a music folder later, they will be renamed properly; when you do so, delete the file "TCD_DONE.TXT" from the music folder on the SD card so that the firmware knows that something has changed. The renaming process can take a while (10 minutes for 1000 files in bad cases). Mac users are advised to delete the ._ files from the SD before putting it back into the control board as this speeds up the process.
To start and stop music playback, enter 9005 followed by ENTER on your TCD. Entering 9002 jumps to the previous song, 9008 to the next one.
By default, the songs are played in order, starting at 000.mp3, followed by 001.mp3 and so on. By entering 9555 on the TCD, you can switch to shuffle mode, in which the songs are played in random order. Type 9222 followed by ENTER to switch back to consecutive mode.
Entering 9888 followed by OK re-starts the player at song 000, and 9888xxx (xxx = three-digit number) jumps to song #xxx.
See here for a list of controls of the music player.
While the music player is playing music, other sound effects are disabled/muted. Initiating a time travel stops the music player. The TCD-triggered alarm will, if so configured, sound and stop the music player.
Note that a wired connection only allows for synchronized time travel sequences, no other communication takes place, and there is no way to remote-control the Gauges through the TCD by wire. A wireless connection over BTTFN/WiFi is much more powerful and therefore recommended over a wired connection.
For wiring information, please see here.
With the wiring in place, head to the Config Portal and set the option TCD connected by wire. On the TCD, the option "Control props connected by wire" must be set.
You can connect both the TCD and a Time Travel button to the Dash Gauges. But the button should not be pressed when the option TCD connected by wire is set, as it might yield unwanted results.
The TCD can communicate with the Dash Gauges wirelessly, via the built-in "Basic-Telematics-Transmission-Framework" over WiFi. It can send out information about a time travel and an alarm. Furthermore, the TCD's keypad can be used to remote-control the Dash Gauges.
 |
|---|
| Click to watch the video |
Note that the TCD's firmware must be up to date for BTTFN. You can use this one or CircuitSetup's release 2.9 or later.
In order to connect your Dash Gauges to the TCD using BTTFN, just enter the TCD's IP address or hostname in the IP address or hostname of TCD field in the Dash Gauges's Config Portal. On the TCD, no special configuration is required. Note that you need TCD firmware 2.9.1 or later for using a hostname; previous versions only work with an IP address.
Afterwards, the Dash Gauges and the TCD can communicate wirelessly and
- play time travel sequences in sync,
- both play an alarm-sequence when the TCD's alarm occurs,
- the Dash Gauges can be remote controlled through the TCD's keypad (command codes 9xxx),
- the Dash Gauges queries the TCD for fake power and night mode, in order to react accordingly if so configured,
- pressing the dash gauges' Time Travel button can trigger a synchronized Time Travel on all BTTFN-connected devices, just like if that Time Travel was triggered through the TCD.
You can use BTTF-Network and MQTT at the same time, see below.
Note that a wired connection only allows for synchronized time travel sequences, no other communication takes place, and there is no way to remote-control the Gauges through the TCD by wire. A wireless connection over BTTFN/WiFi is much more powerful and therefore recommended over a wired connection.
For wiring information, please see here.
With the wiring in place, head to the Config Portal and set the option TCD connected by wire. On the TCD, the option "Control props connected by wire" must be set.
You can connect both the TCD and a Time Travel button to the Dash Gauges. But the button should not be pressed when the option TCD connected by wire is set, as it might yield unwanted results.
The Dash Gauges support the MQTT protocol version 3.1.1 for the following features:
The Dash Gauges can - to some extent - be controlled through messages sent to topic bttf/dg/cmd. Support commands are
- TIMETRAVEL: Start a time travel
- EMPTY: "Drain" Plutonium and trigger alarm
- REFILL: Refill the Plutonium chamber
- PLAY_DOOR_OPEN, PLAY_DOOR_CLOSED: Play respective door sounds; these commands are only executed if the option Play door sounds in the Config Portal is unchecked.
- MP_PLAY: Starts the Music Player
- MP_STOP: Stops the Music Player
- MP_NEXT: Jump to next song
- MP_PREV: Jump to previous song
- MP_SHUFFLE_ON: Enables shuffle mode in Music Player
- MP_SHUFFLE_OFF: Disables shuffle mode in Music Player
- MP_FOLDER_x: x being 0-9, set Music Folder number for Music Player
If both TCD and Dash Gauges are connected to the same broker, and the option Send event notifications is checked on the TCD's side, the Dash Gauges will receive information on time travel and alarm and play their sequences in sync with the TCD. Unlike BTTFN, however, no other communication takes place.
MQTT and BTTFN can co-exist. However, the TCD only sends out time travel and alarm notifications through either MQTT or BTTFN, never both. If you have other MQTT-aware devices listening to the TCD's public topic (bttf/tcd/pub) in order to react to time travel or alarm messages, use MQTT (ie check Send event notifications). If only BTTFN-aware devices are to be used, uncheck this option to use BTTFN as it has less latency.
In order to connect to a MQTT network, a "broker" (such as mosquitto, EMQ X, Cassandana, RabbitMQ, Ejjaberd, HiveMQ to name a few) must be present in your network, and its address needs to be configured in the Config Portal. The broker can be specified either by domain or IP (IP preferred, spares us a DNS call). The default port is 1883. If a different port is to be used, append a ":" followed by the port number to the domain/IP, such as "192.168.1.5:1884".
If your broker does not allow anonymous logins, a username and password can be specified.
Limitations: MQTT Protocol version 3.1.1; TLS/SSL not supported; ".local" domains (MDNS) not supported; server/broker must respond to PING (ICMP) echo requests. For proper operation with low latency, it is recommended that the broker is on your local network.
If your Dash Gauges, along with a Time Circuits Display, is mounted in a car, the following network configuration is recommended:
- Run your TCD in car mode;
- disable WiFi power-saving on the TCD by setting WiFi power save timer (AP-mode) to 0 (zero).
Enter the Config Portal on the Dash Gauges (as described above), click on Setup and
- enter 192.168.4.1 into the field IP address or hostname of TCD
- check the option Follow TCD fake power if you have a fake power switch for the TCD (like eg a TFC switch)
- click on Save.
After the Dash Gauges have restarted, re-enter the Dash Gauges's Config Portal (while the TCD is powered and in car mode) and
- click on Configure WiFi,
- select the TCD's access point name in the list at the top or enter TCD-AP into the SSID field; if you password-protected your TCD's AP, enter this password in the password field. Leave all other fields empty,
- click on Save.
Using this setup enables the Dash Gauges to receive notifications about time travel and alarm wirelessly, and to query the TCD for data. Also, the TCD keypad can be used to remote-control the Dash Gauges.
In order to access the Dash Gauges's Config Portal in your car, connect your hand held or computer to the TCD's WiFi access point ("TCD-AP"), and direct your browser to http://gauges.local ; if that does not work, go to the TCD's keypad menu, press ENTER until "BTTFN CLIENTS" is shown, hold ENTER, and look for the Dash Gauges's IP address there; then direct your browser to that IP by using the URL http://a.b.c.d (a-d being the IP address displayed on the TCD display).
The Dash Gauges have a connector for two door switches. These switches trigger door open/close sounds.
By default, the "Door Open" sound is played when the switch is closed; "Door close" is played when the switch opens.
In the Config Portal, you can invert this setting, so that the "Door Open" sound is played when the switch is closed.
Flash memory has a somewhat limited life-time. It can be written to only between 10.000 and 100.000 times before becoming unreliable. The firmware writes to the internal flash memory when saving settings and other data. Every time you change settings, data is written to flash memory.
In order to reduce the number of write operations and thereby prolong the life of your Dash Gauges, it is recommended to use a good-quality SD card and to check Save secondary settings on SD in the Config Portal; secondary settings (eg current volume) are then stored on the SD card (which also suffers from wear but is easy to replace). See here for more information.
Clicking this leads to the WiFi configuration page. On that page, you can connect your Dash Gauges to your WiFi network by selecting/entering the SSID (WiFi network name) as well as a password (WPA2). By default, the Dash Gauges request an IP address via DHCP. However, you can also configure a static IP by entering the IP, netmask, gateway and DNS server. All four fields must be filled for a valid static IP configuration. If you want to stick to DHCP, leave those four fields empty.
Note that this page has nothing to do with Access Point mode; it is strictly for connecting your Dash Gauges to an existing WiFi network as a client.
This leads to the Setup page.
This leads to the firmware and audio update page.
In order to upload a new firmware binary (such as the ones published here in the install/ folder), select that image file in the top file selector and click "Update".
You can also install the Dash Gauges' audio data on this page; download the current sound-pack, extract it and select the resulting DGA.bin file in the bottom file selector. Finally, click "Upload". Note that an SD card is required for this operation.
Note that either a firmware or audio data can be uploaded at once, not both at the same time.
Clicking this (and saying "yes" in the confirmation dialog) erases the WiFi configuration (WiFi network and password) and reboots the device; it will restart in "access point" mode. See here.
After a time travel, the plutonium is depleted, and the chamber needs to be refilled. This timer allows for an automatic "Refill" after the given number of seconds; 0 means never. In the latter case, a manual Refill is in order: Either flip the side switch, or enter "009" on the TCD (if connected wirelessly).
The "empty" alarm's sound can be annoying if played for longer periods. This timer allows to mute it after the given number of seconds. 0 means never.
Enter the number of minutes until the Screen Saver should become active when the Dash Gauges are idle.
The Screen Saver, when active, stops the "empty" alarm sound and disables all gauges and lights, until
- the time travel button is briefly pressed (the first press when the screen saver is active will not trigger a time travel),
- on a connected TCD, a destination date is entered (only if TCD is wirelessly connected) or a time travel event is triggered (also when wired).
The music player will continue to run.
Enter a value between 0 (mute) or 19 (very loud) here. This is your starting point; you can change the volume via TCD (93xx) and that new volume will also be saved (and appear in this field when the page is reloaded in your browser).
The device's hostname in the WiFi network. Defaults to 'gauges'. This also is the domain name at which the Config Portal is accessible from a browser in the same local network. The URL of the Config Portal then is http://hostname.local (the default is http://gauges.local)
If you have several Dash Gauges in your local network, please give them unique hostnames.
By default, if the Dash Gauges create a WiFi network of its own ("AP-mode"), this network is named "DG-AP". In case you have multiple Dash Gauges in your vicinity, you can have a string appended to create a unique network name. If you, for instance, enter "-ABC" here, the WiFi network name will be "DG-AP-ABC". Characters A-Z, a-z, 0-9 and - are allowed.
By default, and if this field is empty, the Dash Gauges's own WiFi network ("AP-mode") will be unprotected. If you want to protect your access point, enter your password here. It needs to be 8 characters in length and only characters A-Z, a-z, 0-9 and - are allowed.
If you forget this password and are thereby locked out of your Dash Gauges,
- power-down the device,
- hold the Time Travel button,
- power-up the device (while still holding the Time Travel button)
- wait until the "Empty" LED flashes briefly,
- flip the Side Switch twice within 10 seconds,
- wait until the "Empty" LED lights up,
- then release the Time Travel button.
This procedure temporarily (until a reboot) clears the WiFi password, allowing unprotected access to the Config Portal. (Note that this procedure also deletes static IP addres data; the device will return to using DHCP after a reboot.)
Number of times the firmware tries to reconnect to a WiFi network, before falling back to AP-mode. See here
Number of seconds before a timeout occurs when connecting to a WiFi network. When a timeout happens, another attempt is made (see immediately above), and if all attempts fail, the device falls back to AP-mode. See here
Check this if you have a Time Circuits Display connected by wire. Note that a wired connection only allows for synchronized time travel sequences, no other communication takes place.
While you can connect both a button and the TCD to the "time travel" connector on the Dash Gauges, the button should not be pressed when this option is set, as it might yield unwanted effects.
Do NOT check this option if your TCD is connected wirelessly (BTTFN, MQTT).
Usually, the TCD signals a time travel with a 5 seconds lead, in order to give a prop a chance to play an acceleration sequence before the actual time travel takes place. Since this 5 second lead is unique to CircuitSetup props, and people sometimes want to connect third party props to the TCD, the TCD has the option of skipping this 5 seconds lead. If that is the case, and your Dash Gauges are connected by wire, you need to set this option.
If your Dash Gauges are connected wirelessly, this option has no effect.
If you want to have your Dash Gauges to communicate with a Time Circuits Display wirelessly ("BTTF-Network"), enter the IP address of the TCD here. If your TCD is running firmware version 2.9.1 or later, you can also enter the TCD's hostname here instead (eg. 'timecircuits').
If you connect your Dash Gauges to the TCD's access point ("TCD-AP"), the TCD's IP address is 192.168.4.1.
If this option is checked, and your TCD goes into night mode, the Dash Gauges will activate the Screen Saver with a very short timeout, and reduce its audio volume.
If this option is checked, and your TCD is equipped with a fake power switch, the Dash Gauges will also fake-power up/down. If fake power is off, no LED is active and the Dash Gauges will ignore all input.
If the dash gauges are connected to a TCD through BTTFN, this option allows to trigger a synchronized time travel on all BTTFN-connected devices when pressing the Time Travel button, just as if the Time Travel was triggered by the TCD. If this option is unchecked, pressing the Time Travel button only triggers a Time Travel sequence on the dash gauges.
For analog gauges only.
Here you can select the readiing the "Primary" meter should give when "full". You can enter a value between 0 and 100 here. 0 will reset the "full" percentage to a default; 1-100 select a specific percentage. Values below 10 don't really make sense, though.
The "full" percentage can be changed through the TCD keypad (91xx for the "Primary" gauge, 93xx for the "Pecent Power" one, and 97xx for the "Roentgens"). 9x00 resets the "full" position the a default value. Note that changing the "full" percentage through the TCD keypad is not persistent. The boot-up values are only set through the Config Portal.
For analog gauges only.
This allows to select the pointer position when the meter is supposed to show "empty". This should be 0 (zero), but if your hardware is either inaccurate or the pointer isn't exactly 0-adjusted, you can modify its "zero" position here. Values from 0-100 are allowed, but obviously only values < 20 make sense.
For analog gauges only. This selects whether the meter should slowly move towards zero during a time travel, or jump to zero after the time travel.
Same as this, but for the 'Percent Power' gauge
Same as this, but for the 'Percent Power' gauge
For analog gauges only. This selects whether the meter should slowly move towards zero during a time travel, or jump to zero after the time travel.
Same as this, but for the 'Roentgens' gauge. If you adjusted the pointer's zero position to the "green zero", be careful not to choose values too high; you might overshoot the pointer's physical end position.
Same as this, but for the 'Roentgens' gauge
For analog gauges only. This selects whether the meter should slowly move towards zero during a time travel, or jump to zero after the time travel.
For digital gauges only.
This defines the "virtual percentage" (0% being the left end of the scale, 100% being the right end of the scale) at which the digital gauge should switch from "full" to "empty" in animations. This value depends on the speed of pointer movement: In the time travel sequence, the pointers are virtually slowly moved from 100% towards 0% in sync with the length of the sequence. If your pointers "jump" to zero quickly, a threshold of 0 is ok. If the pointers move more slowly, the threshold should by adjusted so that the pointers are at "empty" at the end of the sequence, when the "Empty" alarm goes off. Start with "50" and work your way from there.
Note: The current OEM control board only supports one digital output for all connected digital gauges. Therefore, they can only all be "full", or all be "empty", and as a result, there can only be one Threshold for all digital gauges. If you have three digital gauges connected, the Threshold configured for "Primary" has priority.
Same as this, but for the 'Percent Power' gauge. In light of the Note above, this value is only used, if your "Primary" gauge is of analog kind, and the "Percent Power" gauge is the first digital gauge (counting from the left).
Same as this, but for the 'Roentgens' gauge. In light of the Note above, this value is only used, if your "Roentgens" gauge is your only digital gauge.
If a TCD is connected via BTTFN or MQTT, the Dash Gauges visually signals when the TCD's alarm sounds. If you want to play an alarm sound, check this option.
The Control Board has a connector for two door switches; these switches change state whenever a door is opened or closed. The firmware can play a sound for each such event. To enable door sounds, check this.
This option must be unchecked in order to use the MQTT commands PLAY_DOOR_OPEN and PLAY_DOOR_CLOSED.
This selects what type of door switch is being used. Check this, if the switch closes contact when the door closes. Leave unchecked if the switch opens when the door closes.
Depending on the position of the switch and its reaction point, a delay for sound playback might be desired. You can configure such a delay here. Enter the number of milliseconds into the text field; 0 means no delay. The maximum is 5000ms (=5 seconds).
If checked, the Dash Gauges will connect to the broker (if configured) and send and receive messages via MQTT
The broker server address. Can be a domain (eg. "myhome.me") or an IP address (eg "192.168.1.5"). The default port is 1883. If different port is to be used, it can be specified after the domain/IP and a colon ":", for example: "192.168.1.5:1884". Specifying the IP address is preferred over a domain since the DNS call adds to the network overhead. Note that ".local" (MDNS) domains are not supported.
The username (and optionally the password) to be used when connecting to the broker. Can be left empty if the broker accepts anonymous logins.
Selects the current music folder, can be 0 through 9. This can also be set/changed through a TCD keypad via BTTFN.
When checked, songs are shuffled when the device is booted. When unchecked, songs will be played in order.
If this is checked, some settings (volume, etc) are stored on the SD card (if one is present). This helps to minimize write operations to the internal flash memory and to prolong the lifetime of your Dash Gauges. See Flash Wear.
Apart from Flash Wear, there is another reason for using an SD card for settings: Writing data to internal flash memory can cause delays of up to 1.5 seconds, which interrupt sound playback and have other undesired effects. The Dash Gauges need to save data from time to time, so in order for a smooth experience without unexpected and unwanted delays, please use an SD card and check this option.
It is safe to have this option checked even with no SD card present.
If you want copy settings from one SD card to another, do as follows:
- With the old SD card still in the slot, enter the Config Portal, turn off Save secondary settings on SD, and click "SAVE".
- After the Dash Gauges have rebooted, power them down, and swap the SD card for your new one.
- Power-up the Dash Gauges, enter the Config Portal, re-enable Save secondary settings on SD, and click "SAVE".
This procedure ensures that all your settings are copied from the old to the new SD card.
This selects the type of gauge hardware and the way of connection. In order to protect your props, this is locked by default. To unlock this setting
- either hold the Time Travel button for 5 seconds, or
- enter 9317931 on a wirelessly connected TCD,
then reload the page in your browser.
Text & images: (C) Thomas Winischhofer ("A10001986"). See LICENSE. Source: https://dg.out-a-ti.me