Built your own word clock with one or four languages with an Arduino ESP32 Nano.
Use the word clock selector page to compare other software/hardware designs to make..
The clock is controlled with an app on your phone, a web page in a browser or with a serial cable connected to your PC.
Software updates can be uploaded with OTA (Over the Air).
It will keep its time within the second correct with the internet NTP time with time zone and day light saving corrections.
If no internet is available a DS3231 RTC-module can be attached to the PCB to get an accurate time. With a rotary or membrane pad time can be set.
A LDR (light-dependent resistor) is used to give the LEDs an optimal brightness.
The Arduino Nano ESP32 receives time with NTP/WIFI from the internet. The software and the PCB support an external very accurate DS3231 RTC when WIFI is unavailable.
The older Arduino MKR1000, Nano BLE 33 and all its variants with Bluetooth and WIFI has the disadvantage that only WIFI or BLE could be used. The ESP32 has an Espressif BLE/WIFI module. Bluetooth LE does not use the TI CC2541 chip but a Nordic nRF52 chip.
That means you have to use a different BLE service for the serial communication. Not FFE0 but 6e400001-b5a3-... et cetera in your serial terminal app that is used to communicate with the settings of the clock software. Depending on the app you use you probably must specify which protocol to use.
See here: Use BLE on mobile to control the ESP32
For my projects I use a Fritzing software designed PCB. This program is easy to use and it can export Gerber files that can be send to companies that print PCB's. You can also order a PCB with the Fritzing app itself.
PCBWay print 10 PCB's for $5. With +/-$25 shipping and custom charges this is very cheap. The PCB were received within a week after ordering and the quality was excellent. Just upload the Gerber files in the ZIP-file and pay the charges.
The PCB design file can be found in this repository or here: ESP32 PCB
The PCB can connect to a rotary encoder, a DS3231 RTC module or other I2C device, a DCF77-receiver module or other device that receives pulses and a LDR to measure light intensity to control the brightness of the LED-strip.
The SK6812 RGBW LED-strip operates at 5V. De data signal from the Nano is 3.3V.
I tried to use optocouplers to amplify the data signal from 3.3V to 5V but failed. see here:
https://ednieuw.home.xs4all.nl/ElecProj/OptoSK6812/OptocouplerSK6812.html
For level switching the 74HCT125 level shifter is used. It has four ports and I adapted the design of the PCB it can use the other three ports on the IC for other uses.
But the SK6812 RGBW strip, with 14 LEDs, also happily worked when the data line was connected directly to the 3.3V data line of the Nano ESP32. I have not tested strips with more LEDs in the strip.
The lesson of this story is that you can connect the SK6812 RGBW strip with a 470 ohm resistor in the data line and a 200 - 1000 uF capacitor over the 5V and GND directly to the strip without the use of a level shifter. But success is not guaranteed.
An alternative universal PCB to drive RGB(W) LEDs and /or white 2835 LED strips with shift registers can be found here: Nano ESP32 RGBW BW PCB
This PCB, with one Arduino source code, will support the colour LED clocks and the white LED clocks to run with a Arduino Nano ES32.
The design of a minimum PCB for small spaces can also be found in this repository.
Power for the LED-strip can be drawn from the VBUS-pin (5V USB) on the Nano if powered with a USB-C cable.
VBUS provides 5V whenever powered via USB. It is possible to feed the LED-strip via this connection but keep in mind the power travels through the PCB and USB-C power supplies are aable to supply over 20 A. This will probably melt the small copper lines on the PCB.
If powered via the VIN pin VBUS it is disabled. This means that while powering the board through the VIN pin, you can't get 5V from the board.
The PCB can use different power connection options.
A 5V, >1A power supply can be attached at the 5V power connection on the top left of the PCB.
If the red line shortcut (see picture below) is closed then the LED-strip is powered via the Power 6-21V (VIN) connection with 5V.
This will also power the Nano ESP32. You can connect the Vin on the ESP32 Nano with a 5V USB power supply although the minimum voltage is noted as 6V. the 1N5817 diode even lowers the voltage with 0.5V to 4.5V.
BUT KEEP IN MIND. This 5V connection is fed to the LED-strip directly. If a higher voltage power supply connected the LEDs will be destroyed but Nano will turn on happily.
If the Nano ESP32 is connected via the USB-C port then the yellow connection must be shortcut. The LEDs will be powered by this power source. This is fine with 20 LEDs but probably not for longer strips.
After connections are made the PCB and hardware looks like this:
The distance between the LEDs on the strip is suitable for making a clock of 25 x 25 cm (60 LEDs/m) or 50 x 50 cm (30 LEDs/m).
You can choose to stick the 144 LEDs of the clock in 12 rows of 12 LEDs or only behind the letter that should light up.
The advantage of the latter is that fewer LEDs are needed and that you have to drill fewer holes in the spacer plate.
But there are many more soldering points, each of which can cause malfunctions.
My experience is that imperfect soldering on the strip may loosens over time causing malfuncions.
The software has a digital time display option you cannot use if you do not install all 144 LEDs.
You can choose to cut out the words like IT WAS FIVE and so on in a 1 cm thick MDF board with a jigsaw.
Be sure to paint the insides bright white, otherwise the white light will become dingy.
It is better to use foamed PVC white 10 MM RAL 9003. It cuts easily, is white and does not discolour. (Often paint does discolours)
Stick/glue the strips starting from left to right on the odd lines and from right to left on the even lines.
(You have to turn the strip upside down every second row!)
This avoids long data lines going from the right end of the strip to the left end on the next row of a LED strip.
And the software does not have to be corrected for the new postions.
I find it useful to use tinned copper wire.
For example, you solder all 5V connections to the left side of the strip and all GND to the right side of the strip.
To do this, drill a small hole through the plate next to all 5V connections on the left side of the strip and to the GND on the right side
Bend a 90 degree angle, put the wire through the hole and solder the wire to the LED strip.
Place the spacer plate over de LEDs, then a sheet of white paper and finally the word plate.
The ESP32Arduino_WordClockVxxx.ino turns the Nano ESP32 and SK6812 or WS2812 LED strips into a Word clock with connection to your WIFI router and receives the time from a NTP server.
The software can be controlled with Bluetooth on your PC or a mobile Android or iPhone/iPad/iMac.
Several designs can be selected before compiling. (If you have a word plate ofcourse.)
Use a word plate design from this repository or use your own and adapt the position of the LEDs in the software
.
Select one of the three word clocks
//#define FOURLANGUAGECLOCK
#define NL144CLOCK
//#define NLM1M2M3M4L94 // NL clock with four extra LEDs for the minutes to light up
-
#define NL144CLOCK -> a 144 LED single language clock. Default language is Dutch. For French, German and English copy the coding from the four-language clock between the NL144CLOCK defines.
Build instruction for the clock in Dutch and English or here in this repository -
#define NLM1M2M3M4L94 -> a 144 LED single language clock with 4 extra LEDs for the minutes and a slightly different design
-
#define FOURLANGUAGECLOCK-> a 4-language clock with 625 LEDs in a 25 x 25 grid.
Build instruction of 4-language word clock with SK6812 LEDs in UK, NL, DE, FR with Nano Every..
In the libraries.zip are the libraries to compile the software. Unpack them in you libraries folder.
Download the program folder and compile for Arduino Nano ESP32.
Libraries update constantly what may result in incompatibilty with this source code after a few years. Therefore these libraries are included.
An alternative is to compile the ArduinoOTA sketch that can be found in the Examples of the Arduino IDE.
Upload it in the Nano ESP32 and note the IP-addres that is printed in the Serial monitor of the Arduino IDE.
Type this IP-address URL in a browser and enter admin/admin as user and password.
Then upload the .bin file from this repository.
At the moment of writing the Espressif ESP32 board core V3.0.7 with the Arduino Nano ESP32 selected does compile to a working program. Select the Nano ESP32 board from Arduino. The Arduino ESP32 board with core version 2.0.18 also compiles without errors. This 2.0.18 board uses the Adafruit Neopixel library. This library uses machine code to control the LED-strips and does not work (in dec 2024) with the new V3.0 boards. I made a library for the SK6812 and WS2812 that uses the RMT driver for the ESP32 V3.0 core.
#if ESP_ARDUINO_VERSION >= ESP_ARDUINO_VERSION_VAL(3, 0, 0)
#include "EdSoftLED.h" // https://github.com/ednieuw/EdSoftLED for LED strip WS2812 or SK6812
#else
#include <Adafruit_NeoPixel.h> // https://github.com/adafruit/Adafruit_NeoPixel for LED strip WS2812 or SK6812
#endif
There are two compiler pin numbering methods: One method uses the GPIO numbering of the ESP32-S3 or by Arduino pin numbering.
At the moment (Nov 2024) this code must be compiled with GPIO numbering selected!!
If LEDs do not turn on properly check this GPIO numbering setting.
When the Arduino macro numbering D1, D2, ... , D13 is used for digital pins and A0, A1, .. A7 for the analogue pins and LED_BUILTIN, LED_RED LED_GREEN, LED_BLUE for the LEDs on the Nano ESP32 board 'GPIO numbering' must be selected in the compiler.
Install Arduino Nano ESP32 board
Board: Arduino Nano ESP32
Partition Scheme: With FAT
Pin Numbering: By GPIO number (legacy) !! change this
The LEDs will probably not turn on when you use the "Arduino default pin settings" due to a bug in the Adafruit Neopixel library.
The clock receives time from the internet if a DS3231 time module is not installed.
When a DS3231 time module is attached to the circuit board an internet connection is not obliged. Select in the menu that the DS3231 is used instead of the NTP time. (J Toggle use DS3231 RTC module)
To connect to the internet the name of the WIFI station and its password must be entered in the clock software to be able to connect to a WIFI router.
The name of the WIFI-station and password has to be entered once. These credentials will be stored in memory of the microprocessor.
To make life easy it is preferred to use a phone or tablet and a Bluetooth communication app to enter the WIFI credentials into the clock.
BLESerial nRF BLE Serial Pro Serial Bluetooth Terminal
-
Download a Bluetooth UART serial terminal app on your phone, PC, or tablet.
-
For IOS iPhone or iPad: BLE Serial Pro.
Or the free less sophisticated app: BLE serial nRF.
Tip: Turn on Fast BLE with option + in the menu for a faster transmission. -
For Android use: Serial Bluetooth terminal.
Do not turn on Fast BLE in the menu. (Off = default)
If the clock is connected to the internet it will seek contact with a time server. (NTP connection can be turned off in the menu).
The time zone is set to UTC+1 Amsterdam but can be changed in the menu.
To connect to a WIFI network a SSID and password must be entered.
There are a few methods:
- Connect the MCU with a serial cable to a PC and use a serial terminal.
I use the Arduino IDE or Termite as serial terminal.
Sending the character 'I' for information will display the menu followed with the actual settings of several preferences.
 |
 |
| HTML page on iPhone. | Termite terminal on a PC. |
- USE the BLE nRF connection with an UART serial terminal app to control it with your mobile phone or tablet.
Use the IOS app for iPhone or iPad: BLE Serial Pro.
or the free app BLEserial nRF: https://apps.apple.com/nl/app/bleserial-nrf/id1632235163?l=en-GB
Turn on Fast BLE with option Z in the menu.
For Android use:Serial Bluetooth terminal.
Turn off (default) Fast BLE in the menu.
Start the app and find the MCU in the list of devices and connect to it. You can change it's beacon name in the menu with option C.
In both cases send the character I of Information and the menu shows up.
Enter the first character of the setting you want to change followed with a code.
Some entries just toggle On and Off. Like the W to set WIFI Off or On.
To change the SSID and password:
Amy-ssid and send this command. Eg AFRITZ!Box01 or aFRITZ!Box01.
Starting with an upper or lower case character is an identical instruction in the command string
Then Bmy-passwordand send the password.(for example: bSecret
Cbroadcastname will change to name displayed in the Bluetooth connection list.
If the length of the SSID and/or password is less then 5 characters the WIFI will be turned off automatically. This will speed up startup time if no internet connection is available
Use a length of minimal 8 characters for SSID and password.
Check in the menu (third row from the bottom) if WIFI and NTP are on.
If WIFI is connected the LED on the MCU will pulse green.
Enter @ to reset the MCU. It will restart and connections will be made.
To set a time zone. Send the time zone string between the quotes prefixed with the character E or e.
See the time zones at the bottom of this page.
For example; if you live in Australia/Sydney send the string: eAEST-10AEDT,M10.1.0,M4.1.0/3
___________________________________ A SSID B Password C BLE beacon name D Date (D15012021) T Time (T132145) E Timezone (E<-02>2 or E<+01>-1) F Own colour (Hex FWWRRGGBB) G Scan WIFI networks H Toggle use rotary encoder I To print this Info menu J Toggle use DS3231 RTC module K LDR reads/sec toggle On/Off N Display off between Nhhhh (N2208) O Display toggle On/Off P Status LED toggle On/Off Q Display colour choice Q0 Yellow Q1 Hourly Q2 White Q3 All Own Q4 Own Q5 Wheel Q6 Digital R Reset settings @ = Reset MCU U Demo mode (msec) (U200) --Light intensity settings (1-250)-- S Slope, L Min, M Max (S80 L5 M200) W WIFI, X NTP&, CCC BLE, + Fast BLE # Self test, ! See RTC, & Update RTC Ed Nieuwenhuys November 2024 ___________________________________ Display off between: 23h - 08h Display choice: Yellow Slope: 10 Min: 5 Max: 255 SSID: FRITZ!Box BLE name: wordclock IP-address: 192.168.178.141 (/update) Timezone:CET-1CEST,M3.5.0,M10.5.0/3 WIFI=On NTP=On BLE=On FastBLE=Off LED strip: WS2812 (Send % to switch) Software: ESP32Arduino_WordClockV056.ino ESP32 Arduino core version: 2.0.17 17/11/2024 16:01:22 ___________________________________
Menu shown in serial output.
As mentioned before the clock can be controlled with the WIFI webpage or BLE UART terminal app.
When the clock is connected to WIFI the IP-address is displayed in the menu
Enter this IP-address numbers and dots (for example: 192.168.178.31) in the browser of your mobile or PC where you type your internet addresses (URL).
Or in version V056 or higher the name of the BLE beacon can be used followed with .local
If the name of your BLE beacon is wordclock ( see in the menu -> BLE name: wordclock) Enter 'wordclock.local' as URL in the browser. if this does not work install host software:
-
For Linux, install Avahi (http://avahi.org/).
-
For Windows, install Bonjour (http://www.apple.com/support/bonjour/).
-
For Mac OSX and iOS support is built in through Bonjour already.
-
Point your browser to http://wordclock.local, you should see a response.
Or Open the BLE terminal app. Look for the WordClock to connect to and connect.
for Apple IOS devices BLE connection can be made with my app BLE Serial pro on the app store .
For Android
nRF UART terminal program and
Serial Bluetooth terminal.
Unfortunately these Android apps can not read strings longer than 20 characters.
If you see a garbled menu enter and send the character '+' to select the slower transmission mode.
Settings are set by entering the first character of a command following by parameters if necessary.
For example to set the colours of the characters in the display to white enter: Q2
Set time by entering T130245. (130245 will also work)
Turn off WIFI by sending a W.
Reset the MCU with the character @.
Reset to default setting by send R.
In the BLE connection the SSID and password will be shown.
 |
 |
| HTML page | BLE menu |
With the menu many preferences can be set.
These preferences are permanently stored in the Arduino Nano ESP32 storage space.
Enter the first character in the menu of the item to be changed followed with the parameter.
For most entries upper and lower case are identical.
Change the name of the SSID of the router to be connected to.
aFRITZ!Box or AFRITZ!Box
Then enter the password. For example: BSecret_pass
and cMywordclock as a name of the BLE beacon that will be shown in your phone. (default after a reset: wordclock )
Restart the MCU by sending @.
Entering CCC or ccc will toggle BLE on or off. Be careful turning it off. When BLE is off the clock can only be controlled with WIFI or the USB serial port.
If not connected to WIFI time and a RTC DS3231 is attached date must be set by hand.
For example enter: D06112022 to set the date to 6 November 2022.
Enter for example T132145 (or 132145 , or t132145) to set time to 45 seconds and 21 minutes past one o'clock.
At the bottom of this page you can find the time zones used in 2022.
It is a rather complicated string and it is therefore wise to copy it.
Let's pick one if you happen to live here: Antarctica/Troll,"<+00>0<+02>-2,M3.5.0/1,M10.5.0/3"
Copy the string between the " " 's and send it starting with an 'E' or 'e' in front.
E<+00>0<+02>-2,M3.5.0/1,M10.5.0/3
With option Q3 and Q4 from the menu you can set your own colours for the clock to display.
The format to be entered is hexadecimal. 0123456789ABCDEF are the characters that can be used.
The command is 2 digits for white followed with two digits for Red followed with two digits for Green and ending with two digits for Blue.
To colour the characters intense red enter FF0000 prefixed with the character F.
To set intense blue enter: F0000FF or FFF.
To set the dimmed character to dark gray enter for example: F191919.
You get gray if red, green and blue has the same intensity.
With SK6812 LEDs the extra white LED can be used besides the three RGB LEDs in the same housing.
For example: F8800FF00 is 50% white with 100% green.
Print the menu to Bluetooth and the serial monitor when connected with an USB-cable.
Prints the LDR-readings and the calculated intensity output.
With N2208 the display will be turned off between 22:00 and 08:00.
O toggles the display off and on.
Q0 Yellow Q1 hourly Q2 White Q3 All Own Q4 Own Q5 Wheel Q6 Digital display
Q0 will show the time with yellow words.
Q1 will show every hour another colour.
Q2 shows all the texts white.
Q3 and Q4 uses you own defined colours.
Q5 will follow rainbow colours every hour.
Q6 is the digital clock if you have used 12x12 = 144 LEDs in the clock
Send an 'I' to display the latest's settings
R will set all preferences to default settings and clears the SSID and password.
Enter U followed with the duration of a second in milli seconds.
M200 (200 milli second) will speed up the clock 5 times.
Sending an U will turn off the demo mode.
S=Slope L=Min M=Max (S100 L5 M200)
| To control the light intensity three parameters can be set. The values ranges between 0 and 255. The minimal light intensity is to avoid that the display turns completely off when it is dark. It also prevents flickering when the input value are very low, like 2 and 3 bits. Values ranging between 5 and 20 are suggested. When no LDR is attached the Min value can be set to 255. The maximum light intensity is 255 bits for 100% intensity. The Slope (sensitivity) controls the speed at with the maximum value is reached. It multiplies the reading as a percentage. So, entering 100 is a multiplication by one. The placement and sensitivity of your LDR can be adjusted with this parameter Slope. |
 The effect of the value of the slope on the light intensity of the LEDs or display. |
|
# @ = Restart MCU @ will restart the MCU. This is handy when the SSID, password, et cetera are changed and the program must be restarted. W=WIFI, X=NTP, Y=BLE Toggle WIFI, NTP and BLE on and off. Sending the character will toggle it on or off. At the bottom of the menu the state is printed. |
 |
The BLE UART protocol sends default packets of 20 bytes. Between every packet there is a delay of 50 msec
The IOS BLEserial app, and maybe others too, is able to receive packets of 80 bytes or more before characters are missed.
With most apps you will see these will truncate the long strings of the menu.
Then turn off Fast BLE.
Option Z toggles between the long and short packages.
Settings are stored in the SPIFFS space from the Arduino Nano ESP32
! will display the NTP, RTC and DS3231 time as they are stored in the clock in the clock. The DS3231 time module must be installed and being used to show a realistic time. Same as & option but this option will not update from the internet NTP server but only shows the time.
Sending a # will start the clock self test. This is convenient to check if all the words in the clock a functioning.
With this option the used LED strip can be changed. The clock is equipped with on of these to types of LED strips. A Reset of all settings by sending a R in the menu will not change this LED strip selection.
@ will restart the MCU. This is handy when the SSID, et cetera are changed and the program must be restarted. Settings will not be deleted.
& will get the NTP time immediately from the internet and stores it in the RTC clocks. This option is convenient to force the clock to get the proper NTP time. In other cases the program will check the time running in the clock and on the NTP server so now and then and update the RTC clocks. The DS3231 time module must be installed and being used to show a realistic time.
Enter the time as 152300 hhmmss. Same as T152300 Changing date and time only works when a DS3231 RTC module is attached.
The settings of the Arduino Nano ESP32 board is as follows.
Remember to install the ESP32 boards as explained above.
# Program explanation
The program uses the following standard libraries.
// Includes defines and initialisations#include <Preferences.h> #if ESP_ARDUINO_VERSION >= ESP_ARDUINO_VERSION_VAL(3, 0, 0) #include "EdSoftLED.h" // https://github.com/ednieuw/EdSoftLED for LED strip WS2812 or SK6812 #else #include <Adafruit_NeoPixel.h> // https://github.com/adafruit/Adafruit_NeoPixel for LED strip WS2812 or SK6812 #endif #include <NimBLEDevice.h> // For BLE communication https://github.com/h2zero/NimBLE-Arduino #include <ESPNtpClient.h> // https://github.com/gmag11/ESPNtpClient #include <WiFi.h> // Used for web page #include <AsyncTCP.h> // Used for webpage https://github.com/dvarrel/AsyncTCP #include <ESPAsyncWebServer.h> // Used for webpage https://github.com/mathieucarbou/ESPAsyncWebServer #include <ElegantOTA.h> // If a large bunch of compile error see here :https://docs.elegantota.pro/async-mode // Locate the ELEGANTOTA_USE_ASYNC_WEBSERVER macro in the ElegantOTA.h file, and set it to 1: // #define ELEGANTOTA_USE_ASYNC_WEBSERVER 1 #include <ESPmDNS.h> #include <Wire.h> // Ter zijner tijd Wire functies gaan gebruiken. Staan al klaar in de code #include <RTClib.h> // Used for connected DS3231 RTC // Reference https://adafruit.github.io/RTClib/html/class_r_t_c___d_s3231.html #include <Encoder.h>
Webpage.h is included in the program as a TAB in the IDE. It contains the web page to display in the browser.
I made the web page in the free 'Microsoft Expression Web 4'. It is not maintained anymore but has more than enough functionalities for our purposes.
To copy the code from the MS-Expression:
At the bottom line of the window of MS-Expression click 'Split'.
In the upper half the raw HTML Code is displayed and in the bottom half the
Design window.
Copy in the Code window all the HTML code
Go to the Arduino IDE and paste it in the webpage.h TAB between:
R"rawliteral( ... and ...
)rawliteral";
Or copy the the code from the webpage.h into
MSexpression Code area and redesign the page as you like
A long list if definitions and initialisations follows.
I am not a fan of passing all the variables to and from functions and like to
keep them global in one program list.
If you write a program with other people it is good practice not to use too many globals
but this program is in one large listing, for the same reason to keep it simple.
I grouped all the variables per application to keep track where they are used.
With a simple find it is easy in this one great listing to find the back.
To print the time as text and colour with the proper LEDs or characters, the
words and its position in a string of LEDs or text are defined.
The defines executes the function ColorLeds with its proper parameters.
Further in the program in the function void Dutch(void), void
English(void) et cetera it becomes clear why these defines are so useful and
handy.
...
#define PRECIES ColorLeds("precies", 16, 22, LetterColor);
#define MTIEN ColorLeds("tien", 25, 28, LetterColor);
#define KWART ColorLeds("kwart", 32, 36, LetterColor);
#define VOOR ColorLeds("voor", 38, 41, LetterColor);
...
This is the initialisation of the storage area to
store the struct EEPROMstorage.
The Struct with all its settings is saved in one command to permanent memory or SD
Preferences FLASHSTOR;
struct EEPROMstorage { // Data storage in EEPROM to maintain them after power loss
byte DisplayChoice = 0;
...
char BLEbroadcastName[30]; // Name of the BLE beacon
char Timezone[50];
int Checksum = 0;
} Mem;
The variables are adressed with a short name Mem.
For example Mem.DisplayChoice = 3;
The Struct EEPROMstorage
is stored in the function StoreStructInFlashMemory
and retrieved in the function GetStructFromFlashMemory
The menu displayed in the serial monitor and BLE app is defined here.
String may not be longer than 40 characters what can be checked with the 'ruler'
string.
// Menu
//0 1 2 3 4
//1234567890123456789012345678901234567890
char menu[][40] = {
"A SSID B Password C BLE beacon name",
"D Date (D15012021) T Time (T132145)",
...
"W=WIFI, X=NTP, Y=BLE, Z=Fast BLE",
"Nov 2022" };
The Setup happens here:
//-------------------------------------------- // ESP32-C3 Setup //-------------------------------------------- void setup()
{ Serial.begin(115200); Tekstprintln("Serial started"); // Setup the serial port to 115200 baud // ... ... msTick = LastButtonTime = millis();
}
The loop is kept almost empty and the program starts in Every SeccondCheck.
There is nothing in this program that should be executes every millisecond or less
//-------------------------------------------- // ESP32-C3 Loop //-------------------------------------------- void loop()The following routines check if something must happen every second, minute, hour and day.
{ EverySecondCheck(); }
This flow handling of the program keeps the processor for 99% free for other uses.
In this program that is almost nothing but for other purposes this can be needed.
In the serial monitor the loops per second are printed. this can be handy to check if the program spends too much time elsewhere in the program. At the moment (V056) of writing it is around 216,000 l/s.
In the Bluetooth and Serial communication functions some short delays are used
that are essential
here but the program only runs here when there is an actual communication.
(An alternative method could have been the use of an interrupt every second and an empty loop)
//--------------------------------------------
// CLOCK Update routine done every second
//--------------------------------------------
void EverySecondCheck(void)
{
static int Toggle = 0;
uint32_t msLeap = millis() - msTick;
if (msLeap >999) // Every second enter the loop
{
...
if (timeinfo.tm_min != lastminute) EveryMinuteUpdate(); // Enter the every minute routine after one minute
...
}
//--------------------------------------------
// CLOCK Update routine done every minute
//--------------------------------------------
void EveryMinuteUpdate(void)
{
...
if(timeinfo.tm_hour != lasthour) EveryHourUpdate();
}
//--------------------------------------------
// CLOCK Update routine done every hour
//--------------------------------------------
void EveryHourUpdate(void)
{
...
if (timeinfo.tm_mday != lastday) EveryDayUpdate();
}
// //
//------------------------------------------------------------------------------
// CLOCK Update routine done every day
//------------------------------------------------------------------------------
void EveryDayUpdate(void)
{
...
}
Update the LEDs on the Nano and the PCB. On the Nano analogWrite(LED_RED, 512); is OFF and analogWrite(LED_RED, 0); is ON
//-------------------------------------------- //
// COMMON Update routine for the status LEDs
//--------------------------------------------
void UpdateStatusLEDs(int Toggle)
{
if(Mem.StatusLEDOn)
{
...
void SetStatusLED(int Red, int Green, int Blue)
{
analogWrite(LED_RED, 512 - Red); // !Red (not Red) because 1 or HIGH is LED off
analogWrite(LED_GREEN, 512 - Green);
analogWrite(LED_BLUE, 512 - Blue);
}
************* tot hier corrected
Check for serial input from the serial monitor and pass the command to ReworkInputString()
//--------------------------------------------
// Common check for serial input
//--------------------------------------------
void SerialCheck(void)
{
...
ReworkInputString(SerialString+"\n"); // Rework ReworkInputString();
...
}
Restore all the default
values.
//------------------------------------------------------------------------------
// Common Reset to default settings
//------------------------------------------------------------------------------
void Reset(void)
{
Mem.Checksum = 25065;
...
}
Common common print routines.To keep all the print commands in one places it is easy to change these routines for other boards with a different 'slang'.
//--------------------------------------------
// Common common print routines
//--------------------------------------------
void Tekstprint(char const tekst[]) { if(Serial) Serial.print(tekst); SendMessageBLE(tekst);sptext[0]=0; }
void Tekstprintln(char const tekst[]) { sprintf(sptext,"%s\n",tekst); Tekstprint(sptext); }
void TekstSprint(char const tekst[]) { printf(tekst); sptext[0]=0;} // printing for Debugging purposes in serial monitor
void TekstSprintln(char const tekst[]){ sprintf(sptext,"%s\n",tekst); TekstSprint(sptext); }
//------------------------------------------------------------------------------
// Common Constrain a string with integers
// The value between the first and last character in a string is returned between the low and up bounderies
//------------------------------------------------------------------------------
int SConstrainInt(String s,byte first,byte last,int low,int up){return constrain(s.substring(first, last).toInt(), low, up);}
int SConstrainInt(String s,byte first, int low,int up){return constrain(s.substring(first).toInt(), low, up);}
The setup of storage space and control of the
validity of the settings.
In the checksum is invalid a reset() will restore the default settings
//-------------------------------------------- // Common Init and check contents of EEPROM //-------------------------------------------- void InitStorage(void)Store and retrieve the settings from SPIFFS or SD or EEPROM
the several possibilities are store here. EEPROM becomes outdated but still works.
--------------------------------------------
// COMMON Store mem.struct in FlashStorage or SD
//--------------------------------------------
void StoreStructInFlashMemory(void)
{
}
//--------------------------------------------
// COMMON Get data from FlashStorage Preferences.h
//--------------------------------------------
void GetStructFromFlashMemory(void)
{
}
Get the commands from the strings entered in the
serial monitor, Bluetooth or the webpageand perform the command in an action.
The menu letters are almost used but it possible to distinguish between lower and uppercase when more commands are needed.
(That is why there is no conversion to UpperCase or LowerCase).
/--------------------------------------------
// CLOCK Input from Bluetooth or Serial
//--------------------------------------------
void ReworkInputString(String InputString)
{
....
switch (InputString[0])
{
case 'A':
case 'a':
if (InputString.length() >5 )
...
Read the LDR and divide it with 16 to get the values
from 0 - 4096 between 0 and 255.Not all boards has a 12 bit AD converter like.
//--------------------------------------------
// LDR reading are between 0 and 255.
// ESP32 analogue read is between 0 - 4096 -- is: 4096 / 8
//--------------------------------------------
int ReadLDR(void) { return analogRead(PhotoCellPin)/16;}
Control the color and intensity of the LED on the boards in one command
//--------------------------------------------
// CLOCK Control the LEDs on the ESP32
// 0 Low is LED off. Therefore the value is inversed with the ! Not
//--------------------------------------------
void SetStatusLED(bool Red, bool Green, bool Blue)
{
This function reads the analog port and calculates an output intensity to a display or LED-strip
The readings are squared to get a hyperbolic curve that resembles you eye correction for dark and light better than a linear range
It works wonderfully well.
//--------------------------------------------
// LED Dim the leds measured by the LDR and print values
// LDR reading are between 0 and 255. The Brightness send to the LEDs is between 0 and 255
//--------------------------------------------
void DimLeds(bool print) { ... }
Here we print and colour the characters in the display or light up to proper LEDs in a String of RGB(W) LEDs.
The #define executes this functions with the proper parameters for every language and prints the texts in the serial connections.
#define QUARTER ColorLeds("quarter", 32, 38, LetterColor);
//-------------------------------------------- /
/ LED Set color for LED.
//--------------------------------------------
void ColorLeds(char const *Texkst, int FirstLed, int LastLed, uint32_t RGBColor)
{ }
To convert all characters to uppercase in a character array.
//-------------------------------------------- // COMMON String upper //-------------------------------------------- void to_upper(char* string)
Every display or strip uses other commands to regulate the brightness Therefore for all LED/Display commands a function
//------------------------------------------------------------------------------
// LED Set brightness of backlight
//------------------------------------------------------------------------------
void SetBrightnessLeds(byte Bright)
{
SetBackLight(Bright); // Set brightness of LEDs
}
A place to turn off all LEDs or clear the display
/-------------------------------------------- // LED Clear the character string //-------------------------------------------- void LedsOff(void)
Here are all the colours are set for the characters are set.
The function has changed often and it's name describes it's original purpose
For backward compatibility it's name is unchanged.
/--------------------------------------------
// LED Set second color
//--------------------------------------------
void SetSecondColour(void)
{ switch (Mem.DisplayChoice) { case DEFAULTCOLOUR: LetterColor = C_YELLOW;
...
SWversion() prints the menu and the settings of sevaral preferences
The function has changed often and it's name describes it's original purpose
For backward compatibility it's name is unchanged.
PrintLine() prints the horizontal lines in the menu.
//--------------------------------------------
// CLOCK Version and preferences info
//--------------------------------------------
void SWversion(void)
{
#define FILENAAM (strrchr(__FILE__, '\\') ? strrchr(__FILE__, '\\') + 1 : __FILE__)
PrintLine(35);
for (uint8_t i = 0; i < sizeof(menu) / sizeof(menu[0]); Tekstprintln(menu[i++]));
...
PrintLine(35);
}
void PrintLine(byte Lengte)
{... }
Displaytime() prints the time to the serial monitor as text and control wiich language is printed.
It also sends the appropriate sequence of colour and intensities to a RGB(W) LED strip.
//--------------------------------------------
// CLOCK Say the time and load the LEDs
// with the proper colour and intensity //-------------------------------------------- void Displaytime(void) {
.. switch(Language) // Print all the character in the backgound color, a sort of ClearScreen { case 0:
strncpy(Template,"HETVISOWASOVIJFQPRECIESZSTIENKPFKWARTSVOORSOVERAHALFSMIDDERTVIJFATWEESOEENOXVIERELFQTIENKTWAALFBHDRIECNEGENACHTFZESVZEVENOENVUUR",129);
ColorLeds(Template,0,127, Mem.DimmedLetter); Dutch(); Print_tijd(); break; case 1:
... }
A series of functions to get and store time.
The NTP time server puts the retrieved time in the standard C time structures.
/--------------------------- Time functions -------------------------- void GetTijd(byte printit) void Print_RTC_tijd(void) void PrintNTP_tijd(void) void PrintUTCtijd(void) void Print_tijd(void) void SetRTCTime(void)
Convert a HEX string to a unsigned 32-bits integer
/-------------------------------------------- // CLOCK Convert Hex to uint32 //-------------------------------------------- uint32_t HexToDec(String hexString)There is also a lot of slang in languages.
'Half nine' sometimes means 8:30 but can also be 9:30. (-:
/--------------------------------------------
// CLOCK Dutch clock display
//--------------------------------------------
void Dutch(void)
{
HET; // HET is always on
switch (timeinfo.tm_min)
{
case 0: IS; PRECIES; break;
case 1: IS; break;
case 2:
case 3: WAS; break;
case 4:
case 5:
...
void English(void)
void German(void)
void French(void)
The Bluetooth Low Energy Nordic nRF.. functions.
They are different from the Texas instrument CC2540/CC2541 that is used in other chipsets like the HM-10, HM16, JDY-08 et cetera.
More here on Instructables
/----------------------------- // BLE SendMessage by BLE Slow in packets of 20 chars //------------------------------ void SendMessageBLE(std::string Message)/----------------------------- // BLE Start BLE Classes //------------------------------ class MyServerCallbacks: public BLEServerCallbacks
/----------------------------- // BLE Start BLE Service //------------------------------ void StartBLEService(void)
/----------------------------- // BLE CheckBLE //------------------------------ void CheckBLE(void)
Functions to start a WIFI connection and use the webpage
/-------------------------------------------- // WIFI WEBPAGE //-------------------------------------------- void StartWIFI_NTP(void) /-------------------------------------------- // WIFI WEBPAGE //-------------------------------------------- void WebPage(void) /-------------------------------------------- // WIFI WEBPAGE Not found message //-------------------------------------------- void notFound(AsyncWebServerRequest *request)
@Ed Nieuwenhuys, May 2023
#Time zones
Copy the text between the quotes and paste them after the character E
Africa/Abidjan,"GMT0" Africa/Accra,"GMT0" Africa/Addis_Ababa,"EAT-3" Africa/Algiers,"CET-1" Africa/Asmara,"EAT-3" Africa/Bamako,"GMT0" Africa/Bangui,"WAT-1" Africa/Banjul,"GMT0" Africa/Bissau,"GMT0" Africa/Blantyre,"CAT-2" Africa/Brazzaville,"WAT-1" Africa/Bujumbura,"CAT-2" Africa/Cairo,"EET-2" Africa/Casablanca,"<+01>-1" Africa/Ceuta,"CET-1CEST,M3.5.0,M10.5.0/3" Africa/Conakry,"GMT0" Africa/Dakar,"GMT0" Africa/Dar_es_Salaam,"EAT-3" Africa/Djibouti,"EAT-3" Africa/Douala,"WAT-1" Africa/El_Aaiun,"<+01>-1" Africa/Freetown,"GMT0" Africa/Gaborone,"CAT-2" Africa/Harare,"CAT-2" Africa/Johannesburg,"SAST-2" Africa/Juba,"CAT-2" Africa/Kampala,"EAT-3" Africa/Khartoum,"CAT-2" Africa/Kigali,"CAT-2" Africa/Kinshasa,"WAT-1" Africa/Lagos,"WAT-1" Africa/Libreville,"WAT-1" Africa/Lome,"GMT0" Africa/Luanda,"WAT-1" Africa/Lubumbashi,"CAT-2" Africa/Lusaka,"CAT-2" Africa/Malabo,"WAT-1" Africa/Maputo,"CAT-2" Africa/Maseru,"SAST-2" Africa/Mbabane,"SAST-2" Africa/Mogadishu,"EAT-3" Africa/Monrovia,"GMT0" Africa/Nairobi,"EAT-3" Africa/Ndjamena,"WAT-1" Africa/Niamey,"WAT-1" Africa/Nouakchott,"GMT0" Africa/Ouagadougou,"GMT0" Africa/Porto-Novo,"WAT-1" Africa/Sao_Tome,"GMT0" Africa/Tripoli,"EET-2" Africa/Tunis,"CET-1" Africa/Windhoek,"CAT-2" America/Adak,"HST10HDT,M3.2.0,M11.1.0" America/Anchorage,"AKST9AKDT,M3.2.0,M11.1.0" America/Anguilla,"AST4" America/Antigua,"AST4" America/Araguaina,"<-03>3" America/Argentina/Buenos_Aires,"<-03>3" America/Argentina/Catamarca,"<-03>3" America/Argentina/Cordoba,"<-03>3" America/Argentina/Jujuy,"<-03>3" America/Argentina/La_Rioja,"<-03>3" America/Argentina/Mendoza,"<-03>3" America/Argentina/Rio_Gallegos,"<-03>3" America/Argentina/Salta,"<-03>3" America/Argentina/San_Juan,"<-03>3" America/Argentina/San_Luis,"<-03>3" America/Argentina/Tucuman,"<-03>3" America/Argentina/Ushuaia,"<-03>3" America/Aruba,"AST4" America/Asuncion,"<-04>4<-03>,M10.1.0/0,M3.4.0/0" America/Atikokan,"EST5" America/Bahia,"<-03>3" America/Bahia_Banderas,"CST6CDT,M4.1.0,M10.5.0" America/Barbados,"AST4" America/Belem,"<-03>3" America/Belize,"CST6" America/Blanc-Sablon,"AST4" America/Boa_Vista,"<-04>4" America/Bogota,"<-05>5" America/Boise,"MST7MDT,M3.2.0,M11.1.0" America/Cambridge_Bay,"MST7MDT,M3.2.0,M11.1.0" America/Campo_Grande,"<-04>4" America/Cancun,"EST5" America/Caracas,"<-04>4" America/Cayenne,"<-03>3" America/Cayman,"EST5" America/Chicago,"CST6CDT,M3.2.0,M11.1.0" America/Chihuahua,"MST7MDT,M4.1.0,M10.5.0" America/Costa_Rica,"CST6" America/Creston,"MST7" America/Cuiaba,"<-04>4" America/Curacao,"AST4" America/Danmarkshavn,"GMT0" America/Dawson,"MST7" America/Dawson_Creek,"MST7" America/Denver,"MST7MDT,M3.2.0,M11.1.0" America/Detroit,"EST5EDT,M3.2.0,M11.1.0" America/Dominica,"AST4" America/Edmonton,"MST7MDT,M3.2.0,M11.1.0" America/Eirunepe,"<-05>5" America/El_Salvador,"CST6" America/Fortaleza,"<-03>3" America/Fort_Nelson,"MST7" America/Glace_Bay,"AST4ADT,M3.2.0,M11.1.0" America/Godthab,"<-03>3<-02>,M3.5.0/-2,M10.5.0/-1" America/Goose_Bay,"AST4ADT,M3.2.0,M11.1.0" America/Grand_Turk,"EST5EDT,M3.2.0,M11.1.0" America/Grenada,"AST4" America/Guadeloupe,"AST4" America/Guatemala,"CST6" America/Guayaquil,"<-05>5" America/Guyana,"<-04>4" America/Halifax,"AST4ADT,M3.2.0,M11.1.0" America/Havana,"CST5CDT,M3.2.0/0,M11.1.0/1" America/Hermosillo,"MST7" America/Indiana/Indianapolis,"EST5EDT,M3.2.0,M11.1.0" America/Indiana/Knox,"CST6CDT,M3.2.0,M11.1.0" America/Indiana/Marengo,"EST5EDT,M3.2.0,M11.1.0" America/Indiana/Petersburg,"EST5EDT,M3.2.0,M11.1.0" America/Indiana/Tell_City,"CST6CDT,M3.2.0,M11.1.0" America/Indiana/Vevay,"EST5EDT,M3.2.0,M11.1.0" America/Indiana/Vincennes,"EST5EDT,M3.2.0,M11.1.0" America/Indiana/Winamac,"EST5EDT,M3.2.0,M11.1.0" America/Inuvik,"MST7MDT,M3.2.0,M11.1.0" America/Iqaluit,"EST5EDT,M3.2.0,M11.1.0" America/Jamaica,"EST5" America/Juneau,"AKST9AKDT,M3.2.0,M11.1.0" America/Kentucky/Louisville,"EST5EDT,M3.2.0,M11.1.0" America/Kentucky/Monticello,"EST5EDT,M3.2.0,M11.1.0" America/Kralendijk,"AST4" America/La_Paz,"<-04>4" America/Lima,"<-05>5" America/Los_Angeles,"PST8PDT,M3.2.0,M11.1.0" America/Lower_Princes,"AST4" America/Maceio,"<-03>3" America/Managua,"CST6" America/Manaus,"<-04>4" America/Marigot,"AST4" America/Martinique,"AST4" America/Matamoros,"CST6CDT,M3.2.0,M11.1.0" America/Mazatlan,"MST7MDT,M4.1.0,M10.5.0" America/Menominee,"CST6CDT,M3.2.0,M11.1.0" America/Merida,"CST6CDT,M4.1.0,M10.5.0" America/Metlakatla,"AKST9AKDT,M3.2.0,M11.1.0" America/Mexico_City,"CST6CDT,M4.1.0,M10.5.0" America/Miquelon,"<-03>3<-02>,M3.2.0,M11.1.0" America/Moncton,"AST4ADT,M3.2.0,M11.1.0" America/Monterrey,"CST6CDT,M4.1.0,M10.5.0" America/Montevideo,"<-03>3" America/Montreal,"EST5EDT,M3.2.0,M11.1.0" America/Montserrat,"AST4" America/Nassau,"EST5EDT,M3.2.0,M11.1.0" America/New_York,"EST5EDT,M3.2.0,M11.1.0" America/Nipigon,"EST5EDT,M3.2.0,M11.1.0" America/Nome,"AKST9AKDT,M3.2.0,M11.1.0" America/Noronha,"<-02>2" America/North_Dakota/Beulah,"CST6CDT,M3.2.0,M11.1.0" America/North_Dakota/Center,"CST6CDT,M3.2.0,M11.1.0" America/North_Dakota/New_Salem,"CST6CDT,M3.2.0,M11.1.0" America/Nuuk,"<-03>3<-02>,M3.5.0/-2,M10.5.0/-1" America/Ojinaga,"MST7MDT,M3.2.0,M11.1.0" America/Panama,"EST5" America/Pangnirtung,"EST5EDT,M3.2.0,M11.1.0" America/Paramaribo,"<-03>3" America/Phoenix,"MST7" America/Port-au-Prince,"EST5EDT,M3.2.0,M11.1.0" America/Port_of_Spain,"AST4" America/Porto_Velho,"<-04>4" America/Puerto_Rico,"AST4" America/Punta_Arenas,"<-03>3" America/Rainy_River,"CST6CDT,M3.2.0,M11.1.0" America/Rankin_Inlet,"CST6CDT,M3.2.0,M11.1.0" America/Recife,"<-03>3" America/Regina,"CST6" America/Resolute,"CST6CDT,M3.2.0,M11.1.0" America/Rio_Branco,"<-05>5" America/Santarem,"<-03>3" America/Santiago,"<-04>4<-03>,M9.1.6/24,M4.1.6/24" America/Santo_Domingo,"AST4" America/Sao_Paulo,"<-03>3" America/Scoresbysund,"<-01>1<+00>,M3.5.0/0,M10.5.0/1" America/Sitka,"AKST9AKDT,M3.2.0,M11.1.0" America/St_Barthelemy,"AST4" America/St_Johns,"NST3:30NDT,M3.2.0,M11.1.0" America/St_Kitts,"AST4" America/St_Lucia,"AST4" America/St_Thomas,"AST4" America/St_Vincent,"AST4" America/Swift_Current,"CST6" America/Tegucigalpa,"CST6" America/Thule,"AST4ADT,M3.2.0,M11.1.0" America/Thunder_Bay,"EST5EDT,M3.2.0,M11.1.0" America/Tijuana,"PST8PDT,M3.2.0,M11.1.0" America/Toronto,"EST5EDT,M3.2.0,M11.1.0" America/Tortola,"AST4" America/Vancouver,"PST8PDT,M3.2.0,M11.1.0" America/Whitehorse,"MST7" America/Winnipeg,"CST6CDT,M3.2.0,M11.1.0" America/Yakutat,"AKST9AKDT,M3.2.0,M11.1.0" America/Yellowknife,"MST7MDT,M3.2.0,M11.1.0" Antarctica/Casey,"<+11>-11" Antarctica/Davis,"<+07>-7" Antarctica/DumontDUrville,"<+10>-10" Antarctica/Macquarie,"AEST-10AEDT,M10.1.0,M4.1.0/3" Antarctica/Mawson,"<+05>-5" Antarctica/McMurdo,"NZST-12NZDT,M9.5.0,M4.1.0/3" Antarctica/Palmer,"<-03>3" Antarctica/Rothera,"<-03>3" Antarctica/Syowa,"<+03>-3" Antarctica/Troll,"<+00>0<+02>-2,M3.5.0/1,M10.5.0/3" Antarctica/Vostok,"<+06>-6" Arctic/Longyearbyen,"CET-1CEST,M3.5.0,M10.5.0/3" Asia/Aden,"<+03>-3" Asia/Almaty,"<+06>-6" Asia/Amman,"EET-2EEST,M2.5.4/24,M10.5.5/1" Asia/Anadyr,"<+12>-12" Asia/Aqtau,"<+05>-5" Asia/Aqtobe,"<+05>-5" Asia/Ashgabat,"<+05>-5" Asia/Atyrau,"<+05>-5" Asia/Baghdad,"<+03>-3" Asia/Bahrain,"<+03>-3" Asia/Baku,"<+04>-4" Asia/Bangkok,"<+07>-7" Asia/Barnaul,"<+07>-7" Asia/Beirut,"EET-2EEST,M3.5.0/0,M10.5.0/0" Asia/Bishkek,"<+06>-6" Asia/Brunei,"<+08>-8" Asia/Chita,"<+09>-9" Asia/Choibalsan,"<+08>-8" Asia/Colombo,"<+0530>-5:30" Asia/Damascus,"EET-2EEST,M3.5.5/0,M10.5.5/0" Asia/Dhaka,"<+06>-6" Asia/Dili,"<+09>-9" Asia/Dubai,"<+04>-4" Asia/Dushanbe,"<+05>-5" Asia/Famagusta,"EET-2EEST,M3.5.0/3,M10.5.0/4" Asia/Gaza,"EET-2EEST,M3.4.4/48,M10.5.5/1" Asia/Hebron,"EET-2EEST,M3.4.4/48,M10.5.5/1" Asia/Ho_Chi_Minh,"<+07>-7" Asia/Hong_Kong,"HKT-8" Asia/Hovd,"<+07>-7" Asia/Irkutsk,"<+08>-8" Asia/Jakarta,"WIB-7" Asia/Jayapura,"WIT-9" Asia/Jerusalem,"IST-2IDT,M3.4.4/26,M10.5.0" Asia/Kabul,"<+0430>-4:30" Asia/Kamchatka,"<+12>-12" Asia/Karachi,"PKT-5" Asia/Kathmandu,"<+0545>-5:45" Asia/Khandyga,"<+09>-9" Asia/Kolkata,"IST-5:30" Asia/Krasnoyarsk,"<+07>-7" Asia/Kuala_Lumpur,"<+08>-8" Asia/Kuching,"<+08>-8" Asia/Kuwait,"<+03>-3" Asia/Macau,"CST-8" Asia/Magadan,"<+11>-11" Asia/Makassar,"WITA-8" Asia/Manila,"PST-8" Asia/Muscat,"<+04>-4" Asia/Nicosia,"EET-2EEST,M3.5.0/3,M10.5.0/4" Asia/Novokuznetsk,"<+07>-7" Asia/Novosibirsk,"<+07>-7" Asia/Omsk,"<+06>-6" Asia/Oral,"<+05>-5" Asia/Phnom_Penh,"<+07>-7" Asia/Pontianak,"WIB-7" Asia/Pyongyang,"KST-9" Asia/Qatar,"<+03>-3" Asia/Qyzylorda,"<+05>-5" Asia/Riyadh,"<+03>-3" Asia/Sakhalin,"<+11>-11" Asia/Samarkand,"<+05>-5" Asia/Seoul,"KST-9" Asia/Shanghai,"CST-8" Asia/Singapore,"<+08>-8" Asia/Srednekolymsk,"<+11>-11" Asia/Taipei,"CST-8" Asia/Tashkent,"<+05>-5" Asia/Tbilisi,"<+04>-4" Asia/Tehran,"<+0330>-3:30<+0430>,J79/24,J263/24" Asia/Thimphu,"<+06>-6" Asia/Tokyo,"JST-9" Asia/Tomsk,"<+07>-7" Asia/Ulaanbaatar,"<+08>-8" Asia/Urumqi,"<+06>-6" Asia/Ust-Nera,"<+10>-10" Asia/Vientiane,"<+07>-7" Asia/Vladivostok,"<+10>-10" Asia/Yakutsk,"<+09>-9" Asia/Yangon,"<+0630>-6:30" Asia/Yekaterinburg,"<+05>-5" Asia/Yerevan,"<+04>-4" Atlantic/Azores,"<-01>1<+00>,M3.5.0/0,M10.5.0/1" Atlantic/Bermuda,"AST4ADT,M3.2.0,M11.1.0" Atlantic/Canary,"WET0WEST,M3.5.0/1,M10.5.0" Atlantic/Cape_Verde,"<-01>1" Atlantic/Faroe,"WET0WEST,M3.5.0/1,M10.5.0" Atlantic/Madeira,"WET0WEST,M3.5.0/1,M10.5.0" Atlantic/Reykjavik,"GMT0" Atlantic/South_Georgia,"<-02>2" Atlantic/Stanley,"<-03>3" Atlantic/St_Helena,"GMT0" Australia/Adelaide,"ACST-9:30ACDT,M10.1.0,M4.1.0/3" Australia/Brisbane,"AEST-10" Australia/Broken_Hill,"ACST-9:30ACDT,M10.1.0,M4.1.0/3" Australia/Currie,"AEST-10AEDT,M10.1.0,M4.1.0/3" Australia/Darwin,"ACST-9:30" Australia/Eucla,"<+0845>-8:45" Australia/Hobart,"AEST-10AEDT,M10.1.0,M4.1.0/3" Australia/Lindeman,"AEST-10" Australia/Lord_Howe,"<+1030>-10:30<+11>-11,M10.1.0,M4.1.0" Australia/Melbourne,"AEST-10AEDT,M10.1.0,M4.1.0/3" Australia/Perth,"AWST-8" Australia/Sydney,"AEST-10AEDT,M10.1.0,M4.1.0/3" Europe/Amsterdam,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Andorra,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Astrakhan,"<+04>-4" Europe/Athens,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Belgrade,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Berlin,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Bratislava,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Brussels,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Bucharest,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Budapest,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Busingen,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Chisinau,"EET-2EEST,M3.5.0,M10.5.0/3" Europe/Copenhagen,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Dublin,"IST-1GMT0,M10.5.0,M3.5.0/1" Europe/Gibraltar,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Guernsey,"GMT0BST,M3.5.0/1,M10.5.0" Europe/Helsinki,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Isle_of_Man,"GMT0BST,M3.5.0/1,M10.5.0" Europe/Istanbul,"<+03>-3" Europe/Jersey,"GMT0BST,M3.5.0/1,M10.5.0" Europe/Kaliningrad,"EET-2" Europe/Kiev,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Kirov,"<+03>-3" Europe/Lisbon,"WET0WEST,M3.5.0/1,M10.5.0" Europe/Ljubljana,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/London,"GMT0BST,M3.5.0/1,M10.5.0" Europe/Luxembourg,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Madrid,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Malta,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Mariehamn,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Minsk,"<+03>-3" Europe/Monaco,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Moscow,"MSK-3" Europe/Oslo,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Paris,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Podgorica,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Prague,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Riga,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Rome,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Samara,"<+04>-4" Europe/San_Marino,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Sarajevo,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Saratov,"<+04>-4" Europe/Simferopol,"MSK-3" Europe/Skopje,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Sofia,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Stockholm,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Tallinn,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Tirane,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Ulyanovsk,"<+04>-4" Europe/Uzhgorod,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Vaduz,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Vatican,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Vienna,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Vilnius,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Volgograd,"<+03>-3" Europe/Warsaw,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Zagreb,"CET-1CEST,M3.5.0,M10.5.0/3" Europe/Zaporozhye,"EET-2EEST,M3.5.0/3,M10.5.0/4" Europe/Zurich,"CET-1CEST,M3.5.0,M10.5.0/3" Indian/Antananarivo,"EAT-3" Indian/Chagos,"<+06>-6" Indian/Christmas,"<+07>-7" Indian/Cocos,"<+0630>-6:30" Indian/Comoro,"EAT-3" Indian/Kerguelen,"<+05>-5" Indian/Mahe,"<+04>-4" Indian/Maldives,"<+05>-5" Indian/Mauritius,"<+04>-4" Indian/Mayotte,"EAT-3" Indian/Reunion,"<+04>-4" Pacific/Apia,"<+13>-13" Pacific/Auckland,"NZST-12NZDT,M9.5.0,M4.1.0/3" Pacific/Bougainville,"<+11>-11" Pacific/Chatham,"<+1245>-12:45<+1345>,M9.5.0/2:45,M4.1.0/3:45" Pacific/Chuuk,"<+10>-10" Pacific/Easter,"<-06>6<-05>,M9.1.6/22,M4.1.6/22" Pacific/Efate,"<+11>-11" Pacific/Enderbury,"<+13>-13" Pacific/Fakaofo,"<+13>-13" Pacific/Fiji,"<+12>-12<+13>,M11.2.0,M1.2.3/99" Pacific/Funafuti,"<+12>-12" Pacific/Galapagos,"<-06>6" Pacific/Gambier,"<-09>9" Pacific/Guadalcanal,"<+11>-11" Pacific/Guam,"ChST-10" Pacific/Honolulu,"HST10" Pacific/Kiritimati,"<+14>-14" Pacific/Kosrae,"<+11>-11" Pacific/Kwajalein,"<+12>-12" Pacific/Majuro,"<+12>-12" Pacific/Marquesas,"<-0930>9:30" Pacific/Midway,"SST11" Pacific/Nauru,"<+12>-12" Pacific/Niue,"<-11>11" Pacific/Norfolk,"<+11>-11<+12>,M10.1.0,M4.1.0/3" Pacific/Noumea,"<+11>-11" Pacific/Pago_Pago,"SST11" Pacific/Palau,"<+09>-9" Pacific/Pitcairn,"<-08>8" Pacific/Pohnpei,"<+11>-11" Pacific/Port_Moresby,"<+10>-10" Pacific/Rarotonga,"<-10>10" Pacific/Saipan,"ChST-10" Pacific/Tahiti,"<-10>10" Pacific/Tarawa,"<+12>-12" Pacific/Tongatapu,"<+13>-13" Pacific/Wake,"<+12>-12" Pacific/Wallis,"<+12>-12" Etc/GMT,"GMT0" Etc/GMT-0,"GMT0" Etc/GMT-1,"<+01>-1" Etc/GMT-2,"<+02>-2" Etc/GMT-3,"<+03>-3" Etc/GMT-4,"<+04>-4" Etc/GMT-5,"<+05>-5" Etc/GMT-6,"<+06>-6" Etc/GMT-7,"<+07>-7" Etc/GMT-8,"<+08>-8" Etc/GMT-9,"<+09>-9" Etc/GMT-10,"<+10>-10" Etc/GMT-11,"<+11>-11" Etc/GMT-12,"<+12>-12" Etc/GMT-13,"<+13>-13" Etc/GMT-14,"<+14>-14" Etc/GMT0,"GMT0" Etc/GMT+0,"GMT0" Etc/GMT+1,"<-01>1" Etc/GMT+2,"<-02>2" Etc/GMT+3,"<-03>3" Etc/GMT+4,"<-04>4" Etc/GMT+5,"<-05>5" Etc/GMT+6,"<-06>6" Etc/GMT+7,"<-07>7" Etc/GMT+8,"<-08>8" Etc/GMT+9,"<-09>9" Etc/GMT+10,"<-10>10" Etc/GMT+11,"<-11>11" Etc/GMT+12,"<-12>12" Etc/UCT,"UTC0" Etc/UTC,"UTC0" Etc/Greenwich,"GMT0" Etc/Universal,"UTC0" Etc/Zulu,"UTC0"