TIX clock - Revision history

Bertrik Sikken at 13:19, 11 May 2020

2020-05-11T13:19:29Z

← Older revision		Revision as of 13:19, 11 May 2020
Line 1:		Line 1:
	{{Project		{{Project
	\|Name=TIX clock		\|Name=TIX clock
	\|Status=~~In progress~~		\|Status=Stalled
	\|Picture=2019-11-15 181501 - DSC06467.jpg		\|Picture=2019-11-15 181501 - DSC06467.jpg
	\|Contact=Noor		\|Contact=Noor

Bertrik Sikken: /* Basic principles */

2020-01-22T12:27:38Z

Basic principles

← Older revision		Revision as of 12:27, 22 January 2020
Line 55:		Line 55:

	Framerate calculation:		Framerate calculation:
	Suppose we have 4 rows ~~(3 actual + 1 "vsync" row)~~, 4-bit intensity (16 levels) ~~and at least 100 Hz updates, we need 4x16x100 = 6400 Hz line rate.~~		At first I'm aiming at a 10 kHz line update rate (= interrupt rate).
	~~Rounded up to 10000 Hz interrupt rate, this~~ means ~~that the~~ worst case flicker is ~~156~~ Hz.		Suppose we have 3 rows, 4-bit intensity (16 levels) that means a worst case flicker is 10 kHz / 3 / 16 = 208 Hz.
	If this is still too low in practice, we can reduce the dimming resolution, or just use the LEDs at full brightness.		If this is still too low in practice, we can reduce the dimming resolution, or just use the LEDs at full brightness.
	In comparison, a MAX7219 has a "scan-rate" of 800 Hz typically.		In comparison, a MAX7219 has a "scan-rate" of 800 Hz typically.

Bertrik Sikken: /* Reverse engineering */

2020-01-21T17:59:44Z

Reverse engineering

@@ Line 17: / Line 17: @@
 There are a total of 19 transistors on the board.
 Each column has its own transistor.
 ==Schematic==

Bertrik Sikken: /* Schematic */

2020-01-21T17:57:48Z

Schematic

← Older revision		Revision as of 17:57, 21 January 2020
Line 39:		Line 39:

	[[File:TIX.pdf]]		[[File:TIX.pdf]]

			Pins from this schematic:
			* top row: RA0, pin 17
			* mid row: RA1, pin 18
			* bot row: RA2, pin 1
			* col 1 (D19/D10/D1): RA6, pin 15
			* col 2 (D20/D11/D2): RB7, pin 13
			* col 3 (D21/D12/D3): RB6, pin 12
			* col 4 (D22/D13/D4): RB5, pin 11
			* col 5 (D23/D14/D5): RB4, pin 10
			* col 6 (D24/D15/D6): RB3, pin 9
			* col 7 (D25/D16/D7): RB2, pin 8
			* col 8 (D26/D17/D8): RB1, pin 7
			* col 9 (D27/D18/D9): RB0, pin 6

	== Software ==		== Software ==

Bertrik Sikken: /* platformio */

2020-01-21T17:42:02Z

platformio

← Older revision		Revision as of 17:42, 21 January 2020
Line 75:		Line 75:

	==== platformio ====		==== platformio ====
	The software can ~~also~~ be built and uploaded using platformio:		The software can be built and uploaded to the ESP32 using platformio:
	pio run -t upload		pio run -t upload
	The toolchain and libraries will be automatically downloaded from the internet (and cached locally).		The ESP32 toolchain and required libraries will be automatically downloaded from the internet (and cached locally).

	Platformio can be installed (on Debian Linux), using:		Platformio can be installed (on Debian Linux), using:

Bertrik Sikken: /* Arduino IDE */

2020-01-21T17:14:43Z

Arduino IDE

← Older revision		Revision as of 17:14, 21 January 2020
Line 68:		Line 68:
	==== Arduino IDE ====		==== Arduino IDE ====
	The software can be compiled in the Arduino IDE.		The software can be compiled in the Arduino IDE.
	You need the ESP32 toolchain ~~plus~~ the following libraries:
			You need the ESP32 toolchain, see https://github.com/espressif/arduino-esp32/blob/master/docs/arduino-ide/boards_manager.md for the instructions.

			Also install the following libraries:
	* NtpClient, by Fabrice Weinberg, Sandeep Mistry		* NtpClient, by Fabrice Weinberg, Sandeep Mistry

Bertrik Sikken: /* Basic principles */

2020-01-21T17:10:48Z

Basic principles

← Older revision		Revision as of 17:10, 21 January 2020
Line 55:		Line 55:
	* Simple command interpreter running on the serial port @ 115200bps.		* Simple command interpreter running on the serial port @ 115200bps.
	* TIX display driver that alternates between rows and lights up the pixels in the columns		* TIX display driver that alternates between rows and lights up the pixels in the columns
	** implement dimming? because we can!
	** run it at a higher frame rate, the ESP32 is faster anyway and we have fewer pixels
	* NTP client to get UTC time from NTP + local time conversion (incl. summer time)		* NTP client to get UTC time from NTP + local time conversion (incl. summer time)
	* Main process to convert local time into TIX format (number of LEDs lit in a group indicates number)		* Main process to convert local time into TIX format (number of LEDs lit in a group indicates number)
	** Maybe some nice animation on startup
	** domino-style numbers?

	Framerate calculation:		Framerate calculation:
	Suppose we have 4 rows (3 actual + 1 "vsync" row), 4-bit intensity (16 levels) and at least 100 Hz updates, we need 4x16x100 = 6400 line rate.		Suppose we have 4 rows (3 actual + 1 "vsync" row), 4-bit intensity (16 levels) and at least 100 Hz updates, we need 4x16x100 = 6400 Hz line rate.
	Rounded up to 10000 Hz interrupt rate, this means that the worst case flicker is 156 Hz.		Rounded up to 10000 Hz interrupt rate, this means that the worst case flicker is 156 Hz.
	If this is still too low in practice, we can reduce the dimming resolution, or just use the LEDs at full brightness.		If this is still too low in practice, we can reduce the dimming resolution, or just use the LEDs at full brightness.

Bertrik Sikken: /* Basic principles */

2020-01-21T17:09:09Z

Basic principles

← Older revision		Revision as of 17:09, 21 January 2020
Line 51:		Line 51:
	=== Basic principles ===		=== Basic principles ===
	Basic principles of the software are:		Basic principles of the software are:
	* Inspired by the [LichtKrant] firmware		* Inspired by the [[LichtKrant]] firmware
	* Basic ESP32 Arduino framework		* Basic ESP32 Arduino framework
	* Simple command interpreter running on the serial port @ 115200bps.		* Simple command interpreter running on the serial port @ 115200bps.

Bertrik Sikken: /* TODO */

2020-01-21T11:36:54Z

TODO

← Older revision		Revision as of 11:36, 21 January 2020
Line 44:		Line 44:

	=== TODO ===		=== TODO ===
	- wait for hardware to finish and update the pin map in display.cpp		* wait for hardware to finish and update the pin map in display.cpp
	- power it up, can we perhaps run the entire clock from USB 5V power?		* power it up, can we perhaps run the entire clock from USB 5V power?
	- test it on actual hardware		* test it on actual hardware
	- fancy startup animations / more display modes / etc		* fancy startup animations / more display modes / etc

	=== Basic principles ===		=== Basic principles ===

Bertrik Sikken: /* Software */

2020-01-21T11:36:40Z

Software

← Older revision		Revision as of 11:36, 21 January 2020
Line 43:		Line 43:
	Github archive for the software prototype is at https://github.com/bertrik/esptixclock		Github archive for the software prototype is at https://github.com/bertrik/esptixclock

	~~My plan (bertrik) is~~ to re-~~use~~ the ~~code~~ from ~~the [Lichtkrant], adapt~~ it ~~for ESP32 (instead of ESP8266).~~		=== TODO ===
	~~It uses essentially the same concept, except with 3 rows~~ / ~~9 columns instead of 7 rows~~ / ~~80 columns.~~		- wait for hardware to finish and update the pin map in display.cpp
			- power it up, can we perhaps run the entire clock from USB 5V power?
			- test it on actual hardware
			- fancy startup animations / more display modes / etc

	Basic principles:		=== Basic principles ===
	* Basic ESP32 framework ~~with simple~~ command interpreter~~. We need ESP32, because~~ the ~~ESP8266 is short on pins (we need at least 12: 9 columns, 3 rows)~~.		Basic principles of the software are:
			* Inspired by the [LichtKrant] firmware
			* Basic ESP32 Arduino framework
			* Simple command interpreter running on the serial port @ 115200bps.
	* TIX display driver that alternates between rows and lights up the pixels in the columns		* TIX display driver that alternates between rows and lights up the pixels in the columns
	** implement dimming, because we can		** implement dimming? because we can!
	** run it at a ~~much~~ higher ~~framerate~~, the ESP32 is faster anyway and we have fewer pixels		** run it at a higher frame rate, the ESP32 is faster anyway and we have fewer pixels
	* NTP client to get UTC time from NTP + local time conversion (incl. summer time)		* NTP client to get UTC time from NTP + local time conversion (incl. summer time)
	* Main process to convert local time into TIX format (number of LEDs lit in a group indicates number)		* Main process to convert local time into TIX format (number of LEDs lit in a group indicates number)
	** Maybe some nice animation on startup.		** Maybe some nice animation on startup
			** domino-style numbers?

	Framerate calculation:		Framerate calculation: