Vitaliy Eremenko zmiulan

TPM2 Protocol Implementation

Introduction

Frame data is transferred inside packets (similar to DMX, for example). A frame is an image representing a matrix or a light scene.

The packets start and end with one-byte characters. In between are a few control bytes followed by the payload. There is no set size for a payload; it is transmitted with each packet. This makes the protocol quite flexible. There are enough bytes in a single packet for an RGB matrix with 21,845 pixels, but if you just want to control an RGBW lamp, that only requires 9 bytes. The variable frame size means there is no overhead, allowing for maximum transfer speed.

	# .github/workflows/hosting.yml
	name: Hosting

	on:
	# You can use other strategies here, check: https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#on
	push:
	branches:
	- production

	jobs:

	/*
	TPM2.NET protocol handler
	Works with Jinx LED software
	*/

	#include <ESP8266WiFi.h>
	#include <WiFiUdp.h>
	#include <FastLED.h>
	#include <WiFiManager.h>
	#include <Ticker.h>

	from itertools import chain

	def parse_range(rng):
	parts = rng.split('-')
	if 1 > len(parts) > 2:
	raise ValueError("Bad range: '%s'" % (rng,))
	parts = [int(i) for i in parts]
	start = parts[0]
	end = start if len(parts) == 1 else parts[1]
	if start > end:

Vitaliy Eremenko zmiulan

TPM2 Protocol Implementation

Introduction

TPM2 Packet Structure