<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://nurdspace.nl/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Bertrik</id>
	<title>NURDspace - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://nurdspace.nl/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Bertrik"/>
	<link rel="alternate" type="text/html" href="https://nurdspace.nl/Special:Contributions/Bertrik"/>
	<updated>2026-05-02T15:24:17Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.4</generator>
	<entry>
		<id>https://nurdspace.nl/index.php?title=Chronoshift_Celebration&amp;diff=15438</id>
		<title>Chronoshift Celebration</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=Chronoshift_Celebration&amp;diff=15438"/>
		<updated>2025-12-22T13:11:04Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Event&lt;br /&gt;
|Name=Chronoshift Celebration&lt;br /&gt;
|Date=2025/12/27&lt;br /&gt;
|DateEnd=2026/01/04&lt;br /&gt;
|Location=Spaaaace&lt;br /&gt;
|Contact=Stop&lt;br /&gt;
}}&lt;br /&gt;
Again the year is ending and we will host a small get-together for those interested and/or dear.&lt;br /&gt;
&lt;br /&gt;
== Theme song ==&lt;br /&gt;
&lt;br /&gt;
[[File:Chronoshift.wav]]&lt;br /&gt;
&lt;br /&gt;
== Who? ==&lt;br /&gt;
&lt;br /&gt;
* buZz&lt;br /&gt;
* 20h (will bring 40cm disco ball, disco light and special presents)&lt;br /&gt;
* Sparcie (except at least the 30th cuz of her bday :3)&lt;br /&gt;
* tkteun&lt;br /&gt;
* [[folkert]]&lt;br /&gt;
* r3boot&lt;br /&gt;
* Spider (tbd)&lt;br /&gt;
* bavrogar &amp;amp; Dáin &amp;lt;pre&amp;gt;18:26:17 &amp;lt;@bavrogar&amp;gt; denk dat ik namelijk wel even kom buurten :)&amp;lt;/pre&amp;gt;&lt;br /&gt;
* Melan af en toen&lt;br /&gt;
* Harksma Rakemeniet&lt;br /&gt;
* nooitaf&lt;br /&gt;
* fato42+ Psy0rz + maybe one more friend&lt;br /&gt;
&lt;br /&gt;
== Fun Proposals ==&lt;br /&gt;
&lt;br /&gt;
* @Melan | lekker een plugin voor nurdbot vibecoden :P&lt;br /&gt;
* disco ball installation for nurdspace&lt;br /&gt;
* soldering of LED building&lt;br /&gt;
* bytebeat challenge for new year ( https://arxiv.org/pdf/1112.1368 )&lt;br /&gt;
* Singstar karaoke&lt;br /&gt;
* Find the ideal position in the mustard-mayo spectrum.&lt;br /&gt;
* bitterballen catapult shooting contest (20h will bring catapult)&lt;br /&gt;
* join with the Dutch police to find the person who stole the dildo from nurdspace&lt;br /&gt;
* checkout other parties? there&#039;s a semi-rave at the footballstadion anyway&lt;br /&gt;
* als een malle geniale code schrijven met je noise cancelling koptelefoon op&lt;br /&gt;
* special cake for the space by @fato&lt;br /&gt;
* comedy club stage!! Make your jokes ready for the night!&lt;br /&gt;
* work on Hark BBS with Spacie&lt;br /&gt;
* flooding the meshcore&lt;br /&gt;
* Please add your fun proposal. :-D&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14916</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14916"/>
		<updated>2025-06-21T22:53:20Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Participants=bertrik&lt;br /&gt;
|Name=TheThingsNetwork&lt;br /&gt;
|Skills=LoRaWAN,Radio&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Radio&lt;br /&gt;
|Purpose=World domination&lt;br /&gt;
|Picture=Lorixone.png&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Category=Infra&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* current status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one&lt;br /&gt;
* how to set it upd https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
&lt;br /&gt;
Logging in: go to http://lorix-one-0f3a24.local&lt;br /&gt;
Username: admin, password: &amp;lt;SECRET&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The gateway forwards packets to TheThingsNetwork. Contact [[bertrik]] to become collaborator on TheThingsNetwork dashboard.&lt;br /&gt;
&lt;br /&gt;
At the moment the gateway is fully configured, but off-line, stored in Melan&#039;s la.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
This means it&#039;s the 256 MB flash version.&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power from the power-over-ethernet cable.&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== Forwarder setup ====&lt;br /&gt;
The gateway was fully re-installed, by flashing an entirely new image.&lt;br /&gt;
Configuration can be done through the web interface (no CLI required).&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14915</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14915"/>
		<updated>2025-06-21T22:52:55Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Participants=bertrik&lt;br /&gt;
|Name=TheThingsNetwork&lt;br /&gt;
|Skills=LoRaWAN,Radio&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Radio&lt;br /&gt;
|Purpose=World domination&lt;br /&gt;
|Picture=Lorixone.png&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Tool category=Infra&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* current status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one&lt;br /&gt;
* how to set it upd https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
&lt;br /&gt;
Logging in: go to http://lorix-one-0f3a24.local&lt;br /&gt;
Username: admin, password: &amp;lt;SECRET&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The gateway forwards packets to TheThingsNetwork. Contact [[bertrik]] to become collaborator on TheThingsNetwork dashboard.&lt;br /&gt;
&lt;br /&gt;
At the moment the gateway is fully configured, but off-line, stored in Melan&#039;s la.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
This means it&#039;s the 256 MB flash version.&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power from the power-over-ethernet cable.&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== Forwarder setup ====&lt;br /&gt;
The gateway was fully re-installed, by flashing an entirely new image.&lt;br /&gt;
Configuration can be done through the web interface (no CLI required).&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14914</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14914"/>
		<updated>2025-06-21T22:40:17Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=TheThingsNetwork&lt;br /&gt;
|Skills=LoRaWAN,Radio&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Radio&lt;br /&gt;
|Purpose=World domination&lt;br /&gt;
|Picture=Lorixone.png&lt;br /&gt;
|Tool=No&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* current status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one&lt;br /&gt;
* how to set it upd https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
&lt;br /&gt;
Logging in: go to http://lorix-one-0f3a24.local&lt;br /&gt;
Username: admin, password: &amp;lt;SECRET&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The gateway forwards packets to TheThingsNetwork. Contact [[bertrik]] to become collaborator on TheThingsNetwork dashboard.&lt;br /&gt;
&lt;br /&gt;
At the moment the gateway is fully configured, but off-line, stored in Melan&#039;s la.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
This means it&#039;s the 256 MB flash version.&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power from the power-over-ethernet cable.&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== Forwarder setup ====&lt;br /&gt;
The gateway was fully re-installed, by flashing an entirely new image.&lt;br /&gt;
Configuration can be done through the web interface (no CLI required).&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=File:Lorixone.png&amp;diff=14913</id>
		<title>File:Lorixone.png</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=File:Lorixone.png&amp;diff=14913"/>
		<updated>2025-06-21T22:39:52Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14912</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14912"/>
		<updated>2025-06-21T22:39:28Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: Add project descriptor&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=TheThingsNetwork&lt;br /&gt;
|Skills=LoRaWAN,Radio&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Radio&lt;br /&gt;
|Purpose=World domination&lt;br /&gt;
|Picture=lorixone.png&lt;br /&gt;
|Tool=No&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* current status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one&lt;br /&gt;
* how to set it upd https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
&lt;br /&gt;
Logging in: go to http://lorix-one-0f3a24.local&lt;br /&gt;
Username: admin, password: &amp;lt;SECRET&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The gateway forwards packets to TheThingsNetwork. Contact [[bertrik]] to become collaborator on TheThingsNetwork dashboard.&lt;br /&gt;
&lt;br /&gt;
At the moment the gateway is fully configured, but off-line, stored in Melan&#039;s la.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
This means it&#039;s the 256 MB flash version.&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power from the power-over-ethernet cable.&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== Forwarder setup ====&lt;br /&gt;
The gateway was fully re-installed, by flashing an entirely new image.&lt;br /&gt;
Configuration can be done through the web interface (no CLI required).&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14911</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14911"/>
		<updated>2025-06-21T22:34:47Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Intro */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* current status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one&lt;br /&gt;
* how to set it upd https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
&lt;br /&gt;
Logging in: go to http://lorix-one-0f3a24.local&lt;br /&gt;
Username: admin, password: &amp;lt;SECRET&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The gateway forwards packets to TheThingsNetwork. Contact [[bertrik]] to become collaborator on TheThingsNetwork dashboard.&lt;br /&gt;
&lt;br /&gt;
At the moment the gateway is fully configured, but off-line, stored in Melan&#039;s la.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
This means it&#039;s the 256 MB flash version.&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power from the power-over-ethernet cable.&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== Forwarder setup ====&lt;br /&gt;
The gateway was fully re-installed, by flashing an entirely new image.&lt;br /&gt;
Configuration can be done through the web interface (no CLI required).&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14910</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14910"/>
		<updated>2025-06-21T22:32:20Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* forwarder setup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
&lt;br /&gt;
Logging in: go to http://lorix-one-0f3a24.local&lt;br /&gt;
Username: admin, password: &amp;lt;SECRET&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
This means it&#039;s the 256 MB flash version.&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power from the power-over-ethernet cable.&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== Forwarder setup ====&lt;br /&gt;
The gateway was fully re-installed, by flashing an entirely new image.&lt;br /&gt;
Configuration can be done through the web interface (no CLI required).&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14909</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14909"/>
		<updated>2025-06-21T22:31:12Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Hardware */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
&lt;br /&gt;
Logging in: go to http://lorix-one-0f3a24.local&lt;br /&gt;
Username: admin, password: &amp;lt;SECRET&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
This means it&#039;s the 256 MB flash version.&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power from the power-over-ethernet cable.&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== forwarder setup ====&lt;br /&gt;
When running &#039;opkg upgrade&#039;, it logged the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
noldus-lorix-one:~$ sudo opkg upgrade        &lt;br /&gt;
Configuring packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/packet-forwarder-gw already exist.&lt;br /&gt;
Configuring ttn-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/ttn-gw already exist.&lt;br /&gt;
Configuring loriot.&lt;br /&gt;
 System startup links for /etc/init.d/loriot-gw already exist.&lt;br /&gt;
Configuring clouds-manager.&lt;br /&gt;
 System startup links for /etc/init.d/init-clouds-manager already exist.&lt;br /&gt;
Stopping cloud loriot... done.&lt;br /&gt;
Starting cloud loriot... done.&lt;br /&gt;
Configuring lora-gateway.&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/local_conf.json&lt;br /&gt;
Configuring factory-reset.&lt;br /&gt;
 System startup links for /etc/init.d/factory-reset.sh already exist.&lt;br /&gt;
Configuring kersing-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/mp-pkt-fwd/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/mp-pkt-fwd-gw already exist.&lt;br /&gt;
noldus-lorix-one:~$ &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14904</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14904"/>
		<updated>2025-06-20T20:16:09Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Intro */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
&lt;br /&gt;
Logging in: go to http://lorix-one-0f3a24.local&lt;br /&gt;
Username: admin, password: &amp;lt;SECRET&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power through a power-over-ethernet cable&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== forwarder setup ====&lt;br /&gt;
When running &#039;opkg upgrade&#039;, it logged the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
noldus-lorix-one:~$ sudo opkg upgrade        &lt;br /&gt;
Configuring packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/packet-forwarder-gw already exist.&lt;br /&gt;
Configuring ttn-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/ttn-gw already exist.&lt;br /&gt;
Configuring loriot.&lt;br /&gt;
 System startup links for /etc/init.d/loriot-gw already exist.&lt;br /&gt;
Configuring clouds-manager.&lt;br /&gt;
 System startup links for /etc/init.d/init-clouds-manager already exist.&lt;br /&gt;
Stopping cloud loriot... done.&lt;br /&gt;
Starting cloud loriot... done.&lt;br /&gt;
Configuring lora-gateway.&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/local_conf.json&lt;br /&gt;
Configuring factory-reset.&lt;br /&gt;
 System startup links for /etc/init.d/factory-reset.sh already exist.&lt;br /&gt;
Configuring kersing-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/mp-pkt-fwd/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/mp-pkt-fwd-gw already exist.&lt;br /&gt;
noldus-lorix-one:~$ &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14903</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14903"/>
		<updated>2025-06-20T20:15:30Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Intro */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
&lt;br /&gt;
Logging in: go to http://lorix-one-0f3a24.local&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power through a power-over-ethernet cable&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== forwarder setup ====&lt;br /&gt;
When running &#039;opkg upgrade&#039;, it logged the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
noldus-lorix-one:~$ sudo opkg upgrade        &lt;br /&gt;
Configuring packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/packet-forwarder-gw already exist.&lt;br /&gt;
Configuring ttn-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/ttn-gw already exist.&lt;br /&gt;
Configuring loriot.&lt;br /&gt;
 System startup links for /etc/init.d/loriot-gw already exist.&lt;br /&gt;
Configuring clouds-manager.&lt;br /&gt;
 System startup links for /etc/init.d/init-clouds-manager already exist.&lt;br /&gt;
Stopping cloud loriot... done.&lt;br /&gt;
Starting cloud loriot... done.&lt;br /&gt;
Configuring lora-gateway.&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/local_conf.json&lt;br /&gt;
Configuring factory-reset.&lt;br /&gt;
 System startup links for /etc/init.d/factory-reset.sh already exist.&lt;br /&gt;
Configuring kersing-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/mp-pkt-fwd/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/mp-pkt-fwd-gw already exist.&lt;br /&gt;
noldus-lorix-one:~$ &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14902</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14902"/>
		<updated>2025-06-20T19:55:40Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Software */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
* perhaps also relevant: https://www.thethingsindustries.com/docs/hardware/gateways/models/wifx-lorix-one/lbs/&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power through a power-over-ethernet cable&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== Network connection (easiest) ====&lt;br /&gt;
The thing does DHCP, and is reachable at&lt;br /&gt;
  lorix-one-0f3a24.local&lt;br /&gt;
e.g. http://lorix-one-0f3a24.local for the web interface&lt;br /&gt;
&lt;br /&gt;
==== Serial connection (fallback) ====&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
==== forwarder setup ====&lt;br /&gt;
When running &#039;opkg upgrade&#039;, it logged the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
noldus-lorix-one:~$ sudo opkg upgrade        &lt;br /&gt;
Configuring packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/packet-forwarder-gw already exist.&lt;br /&gt;
Configuring ttn-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/ttn-gw already exist.&lt;br /&gt;
Configuring loriot.&lt;br /&gt;
 System startup links for /etc/init.d/loriot-gw already exist.&lt;br /&gt;
Configuring clouds-manager.&lt;br /&gt;
 System startup links for /etc/init.d/init-clouds-manager already exist.&lt;br /&gt;
Stopping cloud loriot... done.&lt;br /&gt;
Starting cloud loriot... done.&lt;br /&gt;
Configuring lora-gateway.&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/local_conf.json&lt;br /&gt;
Configuring factory-reset.&lt;br /&gt;
 System startup links for /etc/init.d/factory-reset.sh already exist.&lt;br /&gt;
Configuring kersing-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/mp-pkt-fwd/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/mp-pkt-fwd-gw already exist.&lt;br /&gt;
noldus-lorix-one:~$ &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14901</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14901"/>
		<updated>2025-06-20T19:02:15Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Hardware */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
* perhaps also relevant: https://www.thethingsindustries.com/docs/hardware/gateways/models/wifx-lorix-one/lbs/&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24 v1.0d&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power through a power-over-ethernet cable&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== network ====&lt;br /&gt;
See /etc/network/interfaces. Add:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
auto eth0&lt;br /&gt;
iface eth0 inet dhcp&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== packages ====&lt;br /&gt;
Packages are maintained with opkg.&lt;br /&gt;
&lt;br /&gt;
==== forwarder setup ====&lt;br /&gt;
When running &#039;opkg upgrade&#039;, it logged the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
noldus-lorix-one:~$ sudo opkg upgrade        &lt;br /&gt;
Configuring packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/packet-forwarder-gw already exist.&lt;br /&gt;
Configuring ttn-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/ttn-gw already exist.&lt;br /&gt;
Configuring loriot.&lt;br /&gt;
 System startup links for /etc/init.d/loriot-gw already exist.&lt;br /&gt;
Configuring clouds-manager.&lt;br /&gt;
 System startup links for /etc/init.d/init-clouds-manager already exist.&lt;br /&gt;
Stopping cloud loriot... done.&lt;br /&gt;
Starting cloud loriot... done.&lt;br /&gt;
Configuring lora-gateway.&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/local_conf.json&lt;br /&gt;
Configuring factory-reset.&lt;br /&gt;
 System startup links for /etc/init.d/factory-reset.sh already exist.&lt;br /&gt;
Configuring kersing-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/mp-pkt-fwd/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/mp-pkt-fwd-gw already exist.&lt;br /&gt;
noldus-lorix-one:~$ &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14900</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14900"/>
		<updated>2025-06-20T18:29:25Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Hardware */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
* perhaps also relevant: https://www.thethingsindustries.com/docs/hardware/gateways/models/wifx-lorix-one/lbs/&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24&lt;br /&gt;
&lt;br /&gt;
You can screw off the bottom, to reveal an ethernet port and an USB-B port.&lt;br /&gt;
It gets power through a power-over-ethernet cable&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
Connect a USB A-to-B cable to the USB-B port.&lt;br /&gt;
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)&lt;br /&gt;
  screen /dev/ttyACM0 115200&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== network ====&lt;br /&gt;
See /etc/network/interfaces. Add:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
auto eth0&lt;br /&gt;
iface eth0 inet dhcp&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== packages ====&lt;br /&gt;
Packages are maintained with opkg.&lt;br /&gt;
&lt;br /&gt;
==== forwarder setup ====&lt;br /&gt;
When running &#039;opkg upgrade&#039;, it logged the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
noldus-lorix-one:~$ sudo opkg upgrade        &lt;br /&gt;
Configuring packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/packet-forwarder-gw already exist.&lt;br /&gt;
Configuring ttn-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/ttn-gw already exist.&lt;br /&gt;
Configuring loriot.&lt;br /&gt;
 System startup links for /etc/init.d/loriot-gw already exist.&lt;br /&gt;
Configuring clouds-manager.&lt;br /&gt;
 System startup links for /etc/init.d/init-clouds-manager already exist.&lt;br /&gt;
Stopping cloud loriot... done.&lt;br /&gt;
Starting cloud loriot... done.&lt;br /&gt;
Configuring lora-gateway.&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/local_conf.json&lt;br /&gt;
Configuring factory-reset.&lt;br /&gt;
 System startup links for /etc/init.d/factory-reset.sh already exist.&lt;br /&gt;
Configuring kersing-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/mp-pkt-fwd/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/mp-pkt-fwd-gw already exist.&lt;br /&gt;
noldus-lorix-one:~$ &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14899</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14899"/>
		<updated>2025-06-20T18:26:50Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
* perhaps also relevant: https://www.thethingsindustries.com/docs/hardware/gateways/models/wifx-lorix-one/lbs/&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
There&#039;s a sticker on the outside:&lt;br /&gt;
FC:C2:3D:0F:3A:24&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== network ====&lt;br /&gt;
See /etc/network/interfaces. Add:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
auto eth0&lt;br /&gt;
iface eth0 inet dhcp&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== packages ====&lt;br /&gt;
Packages are maintained with opkg.&lt;br /&gt;
&lt;br /&gt;
==== forwarder setup ====&lt;br /&gt;
When running &#039;opkg upgrade&#039;, it logged the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
noldus-lorix-one:~$ sudo opkg upgrade        &lt;br /&gt;
Configuring packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/packet-forwarder-gw already exist.&lt;br /&gt;
Configuring ttn-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/ttn-gw already exist.&lt;br /&gt;
Configuring loriot.&lt;br /&gt;
 System startup links for /etc/init.d/loriot-gw already exist.&lt;br /&gt;
Configuring clouds-manager.&lt;br /&gt;
 System startup links for /etc/init.d/init-clouds-manager already exist.&lt;br /&gt;
Stopping cloud loriot... done.&lt;br /&gt;
Starting cloud loriot... done.&lt;br /&gt;
Configuring lora-gateway.&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/local_conf.json&lt;br /&gt;
Configuring factory-reset.&lt;br /&gt;
 System startup links for /etc/init.d/factory-reset.sh already exist.&lt;br /&gt;
Configuring kersing-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/mp-pkt-fwd/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/mp-pkt-fwd-gw already exist.&lt;br /&gt;
noldus-lorix-one:~$ &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14898</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14898"/>
		<updated>2025-06-20T18:23:49Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
* perhaps also relevant: https://www.thethingsindustries.com/docs/hardware/gateways/models/wifx-lorix-one/lbs/&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
&lt;br /&gt;
==== network ====&lt;br /&gt;
See /etc/network/interfaces. Add:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
auto eth0&lt;br /&gt;
iface eth0 inet dhcp&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== packages ====&lt;br /&gt;
Packages are maintained with opkg.&lt;br /&gt;
&lt;br /&gt;
==== forwarder setup ====&lt;br /&gt;
When running &#039;opkg upgrade&#039;, it logged the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
noldus-lorix-one:~$ sudo opkg upgrade        &lt;br /&gt;
Configuring packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/packet-forwarder-gw already exist.&lt;br /&gt;
Configuring ttn-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/ttn/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/ttn-gw already exist.&lt;br /&gt;
Configuring loriot.&lt;br /&gt;
 System startup links for /etc/init.d/loriot-gw already exist.&lt;br /&gt;
Configuring clouds-manager.&lt;br /&gt;
 System startup links for /etc/init.d/init-clouds-manager already exist.&lt;br /&gt;
Stopping cloud loriot... done.&lt;br /&gt;
Starting cloud loriot... done.&lt;br /&gt;
Configuring lora-gateway.&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/local_conf.json&lt;br /&gt;
Configuring factory-reset.&lt;br /&gt;
 System startup links for /etc/init.d/factory-reset.sh already exist.&lt;br /&gt;
Configuring kersing-packet-forwarder.&lt;br /&gt;
Updating configuration files with gateway ID, type EU868&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Default global_conf.json file created from 4dBi outdoor antenna by default,&lt;br /&gt;
don&#039;t forget to chose the one corresponding to your antenna using the following command:&lt;br /&gt;
sudo cp /opt/lorix/cloud/mp-pkt-fwd/global_conf_&amp;lt;antenna&amp;gt;.json global_conf.json&lt;br /&gt;
******************************************************************************************&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_2dBi_indoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_4dBi_outdoor.json&lt;br /&gt;
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/local_conf.json&lt;br /&gt;
 System startup links for /etc/init.d/mp-pkt-fwd-gw already exist.&lt;br /&gt;
noldus-lorix-one:~$ &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14897</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14897"/>
		<updated>2025-06-20T18:06:25Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;br /&gt;
* perhaps also relevant: https://www.thethingsindustries.com/docs/hardware/gateways/models/wifx-lorix-one/lbs/&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14896</id>
		<title>TheThingsNetwork</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=TheThingsNetwork&amp;diff=14896"/>
		<updated>2025-06-20T17:52:05Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: Created page with &amp;quot;== Intro == NurdSpace has a LorixOne LoRaWAN gateway. This page is about setting it up for TheThingsNetwork.  More info: * https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Intro ==&lt;br /&gt;
NurdSpace has a LorixOne LoRaWAN gateway.&lt;br /&gt;
This page is about setting it up for TheThingsNetwork.&lt;br /&gt;
&lt;br /&gt;
More info:&lt;br /&gt;
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=OpenTherm_Gateway&amp;diff=14446</id>
		<title>OpenTherm Gateway</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=OpenTherm_Gateway&amp;diff=14446"/>
		<updated>2024-12-24T22:16:56Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Inventory&lt;br /&gt;
|Name=OpenTherm Gateway&lt;br /&gt;
|Owner=The_Niz&lt;br /&gt;
|Status=Infra&lt;br /&gt;
|Location=Kitchen wall&lt;br /&gt;
|Picture=Opentherm_spacegateway.jpg&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Category=General&lt;br /&gt;
}}&lt;br /&gt;
== What ==&lt;br /&gt;
OpenTherm gateway has been put between the heater and the thermostat. This way we are able to read the OpenTherm communication between them, and control the heater using the gateway. It is a board with a PIC controller that already came pre-flashed. It can be used with a FTDI cable or you can put an ESP8266 based NodeMCU board on it and communicate with that over Wifi. We first went for the ESP8266. The ESP8266 ran Espeasy with [https://www.letscontrolit.com/wiki/index.php/Ser2Net Ser2Net]. We later changed it with [https://www.nodo-shop.nl/nl/opentherm-gateway/207-ethernet-module-usr-tcp232-t2.html USR-TCP232-T2].&lt;br /&gt;
&lt;br /&gt;
== Wiring ==&lt;br /&gt;
Boiler: Remeha Calenta (http://www.archiproducts.com/en/products/revis/wall-mounted-condensation-boiler-remeha-calenta-25l_225443)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:Thermostat wiring.jpg|Original wiring&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
== Integration with home assistant ==&lt;br /&gt;
We do not use [https://github.com/jodur/py-otgw-mqtt py-otgw-mqtt] on [[Jarvis]] anymore but are using native OpenTherm support in Home Assistant.&lt;br /&gt;
* IP: 10.208.1.43&lt;br /&gt;
* Host name: opentherm.lan.nurd.space&lt;br /&gt;
* Port: 20108&lt;br /&gt;
&lt;br /&gt;
For the CH return water temperature to be reported successfully the serial command AA=28 has been issued (http://otgw.tclcode.com/firmware.html#dataids). This command should persist in the OTGW and only be needed once. If however the return water temperature is once again missing and the Calenta is still used the command may be issued again.&lt;br /&gt;
&lt;br /&gt;
== Todo ==&lt;br /&gt;
* Fix ethernet board that was soldered with some wires to it, but wires came loose&lt;br /&gt;
* Put it in a case to prevent wires from coming loose https://www.thingiverse.com/thing:4869506&lt;br /&gt;
* Update Remeha iSense thermostat firmware if possible&lt;br /&gt;
* Get notified when water pressure is low&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
* https://www.nodo-shop.nl/nl/opentherm-gateway/188-opentherm-gateway.html&lt;br /&gt;
* https://www.nodo-shop.nl/nl/content/10-downloads&lt;br /&gt;
* http://otgw.tclcode.com/otmonitor.html&lt;br /&gt;
* http://otgw.tclcode.com/download.html&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=OpenTherm_Gateway&amp;diff=14445</id>
		<title>OpenTherm Gateway</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=OpenTherm_Gateway&amp;diff=14445"/>
		<updated>2024-12-24T22:15:28Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Inventory&lt;br /&gt;
|Name=OpenTherm Gateway&lt;br /&gt;
|Owner=The_Niz&lt;br /&gt;
|Status=Infra&lt;br /&gt;
|Location=Kitchen wall&lt;br /&gt;
|Picture=Opentherm_spacegateway.jpg&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Category=General&lt;br /&gt;
}}&lt;br /&gt;
== What ==&lt;br /&gt;
OpenTherm gateway has been put between the heater and the thermostat. This way we are able to read the OpenTherm communication between them, and control the heater using the gateway. It is a board with a PIC controller that already came pre-flashed. It can be used with a FTDI cable or you can put an ESP8266 based NodeMCU board on it and communicate with that over Wifi. We first went for the ESP8266. The ESP8266 ran Espeasy with [https://www.letscontrolit.com/wiki/index.php/Ser2Net Ser2Net]. We later changed it with [https://www.nodo-shop.nl/nl/opentherm-gateway/207-ethernet-module-usr-tcp232-t2.html USR-TCP232-T2].&lt;br /&gt;
&lt;br /&gt;
== Wiring ==&lt;br /&gt;
Boiler: Remeha Calenta (http://www.archiproducts.com/en/products/revis/wall-mounted-condensation-boiler-remeha-calenta-25l_225443)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:Thermostat wiring.jpg|Original wiring&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
== Integration with home assistant ==&lt;br /&gt;
We do not use [https://github.com/jodur/py-otgw-mqtt py-otgw-mqtt] on [[Jarvis]] anymore but are using native OpenTherm support in Home Assistant.&lt;br /&gt;
* IP: 10.208.1.43&lt;br /&gt;
* Host name: opentherm.lan.nurd.space&lt;br /&gt;
* Port: 20108&lt;br /&gt;
&lt;br /&gt;
For the CH return water temperature to be reported successfully the serial command AA=28 has been issued (http://otgw.tclcode.com/firmware.html#dataids). This command should persist in the OTGW and only be needed once. If however the return water temperature is once again missing and the Calenta is still used the command may be issued again.&lt;br /&gt;
&lt;br /&gt;
== Todo ==&lt;br /&gt;
* Update Remeha iSense thermostat firmware if possible&lt;br /&gt;
* Get notified when water pressure is low&lt;br /&gt;
* Kastje eromheen https://www.thingiverse.com/thing:4869506&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
* https://www.nodo-shop.nl/nl/opentherm-gateway/188-opentherm-gateway.html&lt;br /&gt;
* https://www.nodo-shop.nl/nl/content/10-downloads&lt;br /&gt;
* http://otgw.tclcode.com/otmonitor.html&lt;br /&gt;
* http://otgw.tclcode.com/download.html&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ENS160&amp;diff=14074</id>
		<title>ENS160</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ENS160&amp;diff=14074"/>
		<updated>2024-06-23T17:02:19Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|ProjectParticipants=met name Bertrik maar Folkert heeft ook een schroevendraaier toegepast&lt;br /&gt;
|Name=ENS160 TVOC sensor&lt;br /&gt;
|Skills=Hacking, Electronics, Sensors&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Smelling stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=Tvoc.png&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=WC&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== What ==&lt;br /&gt;
It&#039;s a sensor that measures total volatile organic compounds (TVOC).&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
See https://nl.aliexpress.com/item/1005006125242045.html&lt;br /&gt;
&lt;br /&gt;
Sensor consists of a wemos d1 mini and an ENS160/AHT21 module.&lt;br /&gt;
The AHT21 is used to compensate the readings of the ENS160.&lt;br /&gt;
&lt;br /&gt;
Connections:&lt;br /&gt;
* Vin = wemos 5V&lt;br /&gt;
* GND = wemos GND&lt;br /&gt;
* SDA = wemos D2&lt;br /&gt;
* SCL = wemos D1&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
It is programmed with ESP-home:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
esphome:&lt;br /&gt;
  name: tvocsensor&lt;br /&gt;
  friendly_name: tvocsensor&lt;br /&gt;
&lt;br /&gt;
esp8266:&lt;br /&gt;
  board: d1_mini&lt;br /&gt;
&lt;br /&gt;
# Enable logging&lt;br /&gt;
logger:&lt;br /&gt;
  level: INFO&lt;br /&gt;
&lt;br /&gt;
i2c:&lt;br /&gt;
  &lt;br /&gt;
sensor:&lt;br /&gt;
  - platform: aht10&lt;br /&gt;
    variant: AHT20&lt;br /&gt;
    temperature:&lt;br /&gt;
      name: &amp;quot;AHT21 Temperature&amp;quot;&lt;br /&gt;
      id: tvoc_temperature&lt;br /&gt;
    humidity:&lt;br /&gt;
      name: &amp;quot;AHT21 Humidity&amp;quot;&lt;br /&gt;
      id: tvoc_humidity&lt;br /&gt;
  - platform: ens160&lt;br /&gt;
    eco2:&lt;br /&gt;
      name: &amp;quot;ENS160 eCO2&amp;quot;&lt;br /&gt;
    tvoc:&lt;br /&gt;
      name: &amp;quot;ENS160 Total Volatile Organic Compounds&amp;quot;&lt;br /&gt;
    aqi:&lt;br /&gt;
      id: ens160_air_quality_index&lt;br /&gt;
      name: &amp;quot;ENS160 Air Quality Index&amp;quot;&lt;br /&gt;
    compensation:&lt;br /&gt;
      temperature: tvoc_temperature&lt;br /&gt;
      humidity: tvoc_humidity&lt;br /&gt;
    update_interval: 10s&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ENS160&amp;diff=14071</id>
		<title>ENS160</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ENS160&amp;diff=14071"/>
		<updated>2024-06-23T16:16:53Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ENS160 TVOC sensor&lt;br /&gt;
|Skills=Hacking, Electronics, Sensors&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Smelling stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=Tvoc.png&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=WC&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== What ==&lt;br /&gt;
It&#039;s a sensor that measures volatile organic compounds (VOC).&lt;br /&gt;
See https://nl.aliexpress.com/item/1005006125242045.html&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
Sensor consists of a wemos d1 mini and an ENS160/AHT21 module&lt;br /&gt;
&lt;br /&gt;
Connections:&lt;br /&gt;
* Vin = wemos 5V&lt;br /&gt;
* GND = wemos GND&lt;br /&gt;
* SDA = wemos D2&lt;br /&gt;
* SCL = wemos D1&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
It is programmed with ESP-home:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
esphome:&lt;br /&gt;
  name: tvocsensor&lt;br /&gt;
  friendly_name: tvocsensor&lt;br /&gt;
&lt;br /&gt;
esp8266:&lt;br /&gt;
  board: d1_mini&lt;br /&gt;
&lt;br /&gt;
# Enable logging&lt;br /&gt;
logger:&lt;br /&gt;
  level: INFO&lt;br /&gt;
&lt;br /&gt;
i2c:&lt;br /&gt;
  &lt;br /&gt;
sensor:&lt;br /&gt;
  - platform: aht10&lt;br /&gt;
    variant: AHT20&lt;br /&gt;
    temperature:&lt;br /&gt;
      name: &amp;quot;AHT21 Temperature&amp;quot;&lt;br /&gt;
      id: tvoc_temperature&lt;br /&gt;
    humidity:&lt;br /&gt;
      name: &amp;quot;AHT21 Humidity&amp;quot;&lt;br /&gt;
      id: tvoc_humidity&lt;br /&gt;
  - platform: ens160&lt;br /&gt;
    eco2:&lt;br /&gt;
      name: &amp;quot;ENS160 eCO2&amp;quot;&lt;br /&gt;
    tvoc:&lt;br /&gt;
      name: &amp;quot;ENS160 Total Volatile Organic Compounds&amp;quot;&lt;br /&gt;
    aqi:&lt;br /&gt;
      id: ens160_air_quality_index&lt;br /&gt;
      name: &amp;quot;ENS160 Air Quality Index&amp;quot;&lt;br /&gt;
    compensation:&lt;br /&gt;
      temperature: tvoc_temperature&lt;br /&gt;
      humidity: tvoc_humidity&lt;br /&gt;
    update_interval: 10s&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ENS160&amp;diff=14070</id>
		<title>ENS160</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ENS160&amp;diff=14070"/>
		<updated>2024-06-23T16:12:59Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ENS160 TVOC sensor&lt;br /&gt;
|Skills=Hacking, Electronics, Sensors&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Smelling stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=Tvoc.png&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=WC&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== What ==&lt;br /&gt;
It&#039;s a sensor that measures volatile organic compounds (VOC).&lt;br /&gt;
See https://nl.aliexpress.com/item/1005006125242045.html&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
Sensor consists of a wemos d1 mini and an ENS160/AHT21 module&lt;br /&gt;
&lt;br /&gt;
Connections:&lt;br /&gt;
* Vin = wemos 5V&lt;br /&gt;
* GND = wemos GND&lt;br /&gt;
* SDA = wemos D2&lt;br /&gt;
* SCL = wemos D1&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
It is programmed with ESP-home:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
esphome:&lt;br /&gt;
  name: tvocsensor&lt;br /&gt;
  friendly_name: tvocsensor&lt;br /&gt;
&lt;br /&gt;
esp8266:&lt;br /&gt;
  board: d1_mini&lt;br /&gt;
&lt;br /&gt;
# Enable logging&lt;br /&gt;
logger:&lt;br /&gt;
  level: INFO&lt;br /&gt;
&lt;br /&gt;
i2c:&lt;br /&gt;
  &lt;br /&gt;
sensor:&lt;br /&gt;
  - platform: aht10&lt;br /&gt;
    variant: AHT20&lt;br /&gt;
    temperature:&lt;br /&gt;
      name: &amp;quot;AHT21 Temperature&amp;quot;&lt;br /&gt;
      id: tvoc_temperature&lt;br /&gt;
    humidity:&lt;br /&gt;
      name: &amp;quot;AHT21 Humidity&amp;quot;&lt;br /&gt;
      id: tvoc_humidity&lt;br /&gt;
  - platform: ens160&lt;br /&gt;
    eco2:&lt;br /&gt;
      name: &amp;quot;ENS160 eCO2&amp;quot;&lt;br /&gt;
    tvoc:&lt;br /&gt;
      name: &amp;quot;ENS160 Total Volatile Organic Compounds&amp;quot;&lt;br /&gt;
    aqi:&lt;br /&gt;
      id: ens160_air_quality_index&lt;br /&gt;
      name: &amp;quot;ENS160 Air Quality Index&amp;quot;&lt;br /&gt;
    compensation:&lt;br /&gt;
      temperature: tvoc_temperature&lt;br /&gt;
      humidity: tvoc_humidity&lt;br /&gt;
    update_interval: 60s&lt;br /&gt;
    address: 0x53&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=File:Tvoc.png&amp;diff=14069</id>
		<title>File:Tvoc.png</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=File:Tvoc.png&amp;diff=14069"/>
		<updated>2024-06-23T16:12:18Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ENS160&amp;diff=14068</id>
		<title>ENS160</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ENS160&amp;diff=14068"/>
		<updated>2024-06-23T16:12:08Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ENS160 TVOC sensor&lt;br /&gt;
|Skills=Hacking, Electronics, Sensors&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Smelling stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=tvoc.png&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=WC&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== What ==&lt;br /&gt;
It&#039;s a sensor that measures volatile organic compounds (VOC).&lt;br /&gt;
See https://nl.aliexpress.com/item/1005006125242045.html&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
Sensor consists of a wemos d1 mini and an ENS160/AHT21 module&lt;br /&gt;
&lt;br /&gt;
Connections:&lt;br /&gt;
* Vin = wemos 5V&lt;br /&gt;
* GND = wemos GND&lt;br /&gt;
* SDA = wemos D2&lt;br /&gt;
* SCL = wemos D1&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
It is programmed with ESP-home:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
esphome:&lt;br /&gt;
  name: tvocsensor&lt;br /&gt;
  friendly_name: tvocsensor&lt;br /&gt;
&lt;br /&gt;
esp8266:&lt;br /&gt;
  board: d1_mini&lt;br /&gt;
&lt;br /&gt;
# Enable logging&lt;br /&gt;
logger:&lt;br /&gt;
  level: INFO&lt;br /&gt;
&lt;br /&gt;
i2c:&lt;br /&gt;
  &lt;br /&gt;
sensor:&lt;br /&gt;
  - platform: aht10&lt;br /&gt;
    variant: AHT20&lt;br /&gt;
    temperature:&lt;br /&gt;
      name: &amp;quot;AHT21 Temperature&amp;quot;&lt;br /&gt;
      id: tvoc_temperature&lt;br /&gt;
    humidity:&lt;br /&gt;
      name: &amp;quot;AHT21 Humidity&amp;quot;&lt;br /&gt;
      id: tvoc_humidity&lt;br /&gt;
  - platform: ens160&lt;br /&gt;
    eco2:&lt;br /&gt;
      name: &amp;quot;ENS160 eCO2&amp;quot;&lt;br /&gt;
    tvoc:&lt;br /&gt;
      name: &amp;quot;ENS160 Total Volatile Organic Compounds&amp;quot;&lt;br /&gt;
    aqi:&lt;br /&gt;
      id: ens160_air_quality_index&lt;br /&gt;
      name: &amp;quot;ENS160 Air Quality Index&amp;quot;&lt;br /&gt;
    compensation:&lt;br /&gt;
      temperature: tvoc_temperature&lt;br /&gt;
      humidity: tvoc_humidity&lt;br /&gt;
    update_interval: 60s&lt;br /&gt;
    address: 0x53&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ENS160&amp;diff=14067</id>
		<title>ENS160</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ENS160&amp;diff=14067"/>
		<updated>2024-06-23T16:02:01Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ENS160 TVOC sensor&lt;br /&gt;
|Skills=Hacking, Electronics, Sensors&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Smelling stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=whyunopicture.png&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=WC&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== What ==&lt;br /&gt;
It&#039;s a sensor that measures volatile organic compounds (VOC).&lt;br /&gt;
See https://nl.aliexpress.com/item/1005006125242045.html&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
Sensor consists of a wemos d1 mini and an ENS160/AHT21 module&lt;br /&gt;
&lt;br /&gt;
Connections:&lt;br /&gt;
* Vin = wemos 5V&lt;br /&gt;
* GND = wemos GND&lt;br /&gt;
* SDA = wemos D2&lt;br /&gt;
* SCL = wemos D1&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
It is programmed with ESP-home:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
esphome:&lt;br /&gt;
  name: tvocsensor&lt;br /&gt;
  friendly_name: tvocsensor&lt;br /&gt;
&lt;br /&gt;
esp8266:&lt;br /&gt;
  board: d1_mini&lt;br /&gt;
&lt;br /&gt;
# Enable logging&lt;br /&gt;
logger:&lt;br /&gt;
  level: INFO&lt;br /&gt;
&lt;br /&gt;
i2c:&lt;br /&gt;
  &lt;br /&gt;
sensor:&lt;br /&gt;
  - platform: aht10&lt;br /&gt;
    variant: AHT20&lt;br /&gt;
    temperature:&lt;br /&gt;
      name: &amp;quot;AHT21 Temperature&amp;quot;&lt;br /&gt;
      id: tvoc_temperature&lt;br /&gt;
    humidity:&lt;br /&gt;
      name: &amp;quot;AHT21 Humidity&amp;quot;&lt;br /&gt;
      id: tvoc_humidity&lt;br /&gt;
  - platform: ens160&lt;br /&gt;
    eco2:&lt;br /&gt;
      name: &amp;quot;ENS160 eCO2&amp;quot;&lt;br /&gt;
    tvoc:&lt;br /&gt;
      name: &amp;quot;ENS160 Total Volatile Organic Compounds&amp;quot;&lt;br /&gt;
    aqi:&lt;br /&gt;
      id: ens160_air_quality_index&lt;br /&gt;
      name: &amp;quot;ENS160 Air Quality Index&amp;quot;&lt;br /&gt;
    compensation:&lt;br /&gt;
      temperature: tvoc_temperature&lt;br /&gt;
      humidity: tvoc_humidity&lt;br /&gt;
    update_interval: 60s&lt;br /&gt;
    address: 0x53&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ENS160&amp;diff=14063</id>
		<title>ENS160</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ENS160&amp;diff=14063"/>
		<updated>2024-06-08T20:52:26Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* What */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ENS160 TVOC sensor&lt;br /&gt;
|Skills=Hacking, Electronics, Sensors&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Smelling stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=whyunopicture.png&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=WC&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== What ==&lt;br /&gt;
It&#039;s a sensor that measures volatile organic compounds (VOC).&lt;br /&gt;
See https://nl.aliexpress.com/item/1005006125242045.html&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
Sensor consists of a wemos d1 mini and an ENS160/AHT21 module&lt;br /&gt;
&lt;br /&gt;
Connections:&lt;br /&gt;
* Vin = wemos 5V&lt;br /&gt;
* GND = wemos GND&lt;br /&gt;
* SDA = wemos D2&lt;br /&gt;
* SCL = wemos D1&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
It is programmed with ESP-home:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
esphome:&lt;br /&gt;
  name: tvocsensor&lt;br /&gt;
  friendly_name: tvocsensor&lt;br /&gt;
&lt;br /&gt;
esp8266:&lt;br /&gt;
  board: d1_mini&lt;br /&gt;
&lt;br /&gt;
# Enable logging&lt;br /&gt;
logger:&lt;br /&gt;
&lt;br /&gt;
i2c:&lt;br /&gt;
  &lt;br /&gt;
sensor:&lt;br /&gt;
  - platform: aht10&lt;br /&gt;
    variant: AHT20&lt;br /&gt;
    temperature:&lt;br /&gt;
      name: &amp;quot;AHT21 Temperature&amp;quot;&lt;br /&gt;
      id: tvoc_temperature&lt;br /&gt;
    humidity:&lt;br /&gt;
      name: &amp;quot;AHT21 Humidity&amp;quot;&lt;br /&gt;
      id: tvoc_humidity&lt;br /&gt;
  - platform: ens160&lt;br /&gt;
    eco2:&lt;br /&gt;
      name: &amp;quot;ENS160 eCO2&amp;quot;&lt;br /&gt;
    tvoc:&lt;br /&gt;
      name: &amp;quot;ENS160 Total Volatile Organic Compounds&amp;quot;&lt;br /&gt;
    aqi:&lt;br /&gt;
      id: ens160_air_quality_index&lt;br /&gt;
      name: &amp;quot;ENS160 Air Quality Index&amp;quot;&lt;br /&gt;
    compensation:&lt;br /&gt;
      temperature: tvoc_temperature&lt;br /&gt;
      humidity: tvoc_humidity&lt;br /&gt;
    update_interval: 60s&lt;br /&gt;
    address: 0x53&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ENS160&amp;diff=14062</id>
		<title>ENS160</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ENS160&amp;diff=14062"/>
		<updated>2024-06-08T20:47:50Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ENS160 TVOC sensor&lt;br /&gt;
|Skills=Hacking, Electronics, Sensors&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Smelling stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=whyunopicture.png&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=WC&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== What ==&lt;br /&gt;
It measures volatile organic compounds (VOC).&lt;br /&gt;
See https://nl.aliexpress.com/item/1005006125242045.html&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
Sensor consists of a wemos d1 mini and an ENS160/AHT21 module&lt;br /&gt;
&lt;br /&gt;
Connections:&lt;br /&gt;
* Vin = wemos 5V&lt;br /&gt;
* GND = wemos GND&lt;br /&gt;
* SDA = wemos D2&lt;br /&gt;
* SCL = wemos D1&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
It is programmed with ESP-home:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
esphome:&lt;br /&gt;
  name: tvocsensor&lt;br /&gt;
  friendly_name: tvocsensor&lt;br /&gt;
&lt;br /&gt;
esp8266:&lt;br /&gt;
  board: d1_mini&lt;br /&gt;
&lt;br /&gt;
# Enable logging&lt;br /&gt;
logger:&lt;br /&gt;
&lt;br /&gt;
i2c:&lt;br /&gt;
  &lt;br /&gt;
sensor:&lt;br /&gt;
  - platform: aht10&lt;br /&gt;
    variant: AHT20&lt;br /&gt;
    temperature:&lt;br /&gt;
      name: &amp;quot;AHT21 Temperature&amp;quot;&lt;br /&gt;
      id: tvoc_temperature&lt;br /&gt;
    humidity:&lt;br /&gt;
      name: &amp;quot;AHT21 Humidity&amp;quot;&lt;br /&gt;
      id: tvoc_humidity&lt;br /&gt;
  - platform: ens160&lt;br /&gt;
    eco2:&lt;br /&gt;
      name: &amp;quot;ENS160 eCO2&amp;quot;&lt;br /&gt;
    tvoc:&lt;br /&gt;
      name: &amp;quot;ENS160 Total Volatile Organic Compounds&amp;quot;&lt;br /&gt;
    aqi:&lt;br /&gt;
      id: ens160_air_quality_index&lt;br /&gt;
      name: &amp;quot;ENS160 Air Quality Index&amp;quot;&lt;br /&gt;
    compensation:&lt;br /&gt;
      temperature: tvoc_temperature&lt;br /&gt;
      humidity: tvoc_humidity&lt;br /&gt;
    update_interval: 60s&lt;br /&gt;
    address: 0x53&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ENS160&amp;diff=14061</id>
		<title>ENS160</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ENS160&amp;diff=14061"/>
		<updated>2024-06-08T20:47:02Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ENS160 TVOC sensor&lt;br /&gt;
|Skills=Hacking, Electronics, Sensors&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Smelling stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=whyunopicture.png&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=WC&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== What ==&lt;br /&gt;
It measures volatile organic compounds (VOC).&lt;br /&gt;
See https://nl.aliexpress.com/item/1005006125242045.html&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
Connections:&lt;br /&gt;
* Vin = wemos 5V&lt;br /&gt;
* GND = wemos GND&lt;br /&gt;
* SDA = wemos D2&lt;br /&gt;
* SCL = wemos D1&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
Sensor consists of a wemos d1 mini and an ENS160/AHT21 module&lt;br /&gt;
&lt;br /&gt;
It is programmed with ESP-home:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
esphome:&lt;br /&gt;
  name: tvocsensor&lt;br /&gt;
  friendly_name: tvocsensor&lt;br /&gt;
&lt;br /&gt;
esp8266:&lt;br /&gt;
  board: d1_mini&lt;br /&gt;
&lt;br /&gt;
# Enable logging&lt;br /&gt;
logger:&lt;br /&gt;
&lt;br /&gt;
i2c:&lt;br /&gt;
  &lt;br /&gt;
sensor:&lt;br /&gt;
  - platform: aht10&lt;br /&gt;
    variant: AHT20&lt;br /&gt;
    temperature:&lt;br /&gt;
      name: &amp;quot;AHT21 Temperature&amp;quot;&lt;br /&gt;
      id: tvoc_temperature&lt;br /&gt;
    humidity:&lt;br /&gt;
      name: &amp;quot;AHT21 Humidity&amp;quot;&lt;br /&gt;
      id: tvoc_humidity&lt;br /&gt;
  - platform: ens160&lt;br /&gt;
    eco2:&lt;br /&gt;
      name: &amp;quot;ENS160 eCO2&amp;quot;&lt;br /&gt;
    tvoc:&lt;br /&gt;
      name: &amp;quot;ENS160 Total Volatile Organic Compounds&amp;quot;&lt;br /&gt;
    aqi:&lt;br /&gt;
      id: ens160_air_quality_index&lt;br /&gt;
      name: &amp;quot;ENS160 Air Quality Index&amp;quot;&lt;br /&gt;
    compensation:&lt;br /&gt;
      temperature: tvoc_temperature&lt;br /&gt;
      humidity: tvoc_humidity&lt;br /&gt;
    update_interval: 60s&lt;br /&gt;
    address: 0x53&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ENS160&amp;diff=14060</id>
		<title>ENS160</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ENS160&amp;diff=14060"/>
		<updated>2024-06-08T20:42:55Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: Created page with &amp;quot;{{Project |Name=ENS160 TVOC sensor |Skills=Hacking, Electronics, Sensors |Status=Active |Niche=Smelling stuff |Purpose=Fun |Picture=whyunopicture.png |Tool=Yes |Location=WC |Category=Electronics }}&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ENS160 TVOC sensor&lt;br /&gt;
|Skills=Hacking, Electronics, Sensors&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Smelling stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=whyunopicture.png&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=WC&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=14059</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=14059"/>
		<updated>2024-06-08T20:41:04Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=Scarlett Scroller&lt;br /&gt;
|Skills=Hacking, Electronics, Programming, making, lights,&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Artsy stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=Zaal1&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0016 (3).JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0017 (1).JPG&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:ScarlettScroller.gif|right|Scarlett Scroller]]&lt;br /&gt;
&lt;br /&gt;
For questions about this project, see [[User:Bertrik]] on how to contact me.&lt;br /&gt;
&lt;br /&gt;
This page is about modifying a 80x7 pixel scrolling red LED sign with an alternative controller (ESP8266) running custom firmware.&lt;br /&gt;
This makes it possible to use the LED sign as a networked display (WiFi), with pixels that can be individually dimmed in 255 levels.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
(as viewed on the controller board)&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;br /&gt;
&lt;br /&gt;
== Integration into nurdspace infrastructure ==&lt;br /&gt;
This scroller is mounted above the door in zaal 1.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
Power to the scroller is switched along with the power to the *zaal 1 amplifier*.&lt;br /&gt;
&lt;br /&gt;
=== Network ===&lt;br /&gt;
The scroller itself has the following network configuration:&lt;br /&gt;
* host name ESP-74AAEB.dhcp.nurd.space&lt;br /&gt;
* port 5000 (UDP): accepts a text message, the message is scrolled once, right-to-left&lt;br /&gt;
* port 8888 (UDP): accepts a 560 byte (80x7 pixel) frame with 8-bit intensity data&lt;br /&gt;
&lt;br /&gt;
On ticker-proxy.vm.nurd.space port 5108 listens for UDP pixelflood (text!).&lt;br /&gt;
Port 5120 (also UDP) listens for text messages.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scarlettscroller.jpg|640px]]&lt;br /&gt;
&lt;br /&gt;
=== Audio ===&lt;br /&gt;
The plan is to show an audio waveform if music/audio is playing.&lt;br /&gt;
* snap client protocol https://github.com/badaix/snapcast/blob/master/doc/binary_protocol.md&lt;br /&gt;
&lt;br /&gt;
The display shows part of the waveform:&lt;br /&gt;
&lt;br /&gt;
Concepts/calculation:&lt;br /&gt;
* about 10 updates/second, say about 4096 bytes per frame (44100 samples/second)&lt;br /&gt;
* use FFT to find the waveform segment that best matches the currently displayed waveform&lt;br /&gt;
* algorithm: complex FFT of both current waveform and segment to search in, multitply by complex conjugate, IFFT then find largest correlation peak&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=13023</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=13023"/>
		<updated>2022-12-24T16:19:33Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Network */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=Scarlett Scroller&lt;br /&gt;
|Skills=Hacking, Electronics, Programming, making, lights,&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Artsy stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=Zaal1&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0016 (3).JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0017 (1).JPG&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:ScarlettScroller.gif|right|Scarlett Scroller]]&lt;br /&gt;
&lt;br /&gt;
For questions about this project, see [[User:Bertrik]] on how to contact me.&lt;br /&gt;
&lt;br /&gt;
This page is about modifying a 80x7 pixel scrolling red LED sign with an alternative controller (ESP8266) running custom firmware.&lt;br /&gt;
This makes it possible to use the LED sign as a networked display (WiFi), with pixels that can be individually dimmed in 255 levels.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
(as viewed on the controller board)&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;br /&gt;
&lt;br /&gt;
== Integration into nurdspace infrastructure ==&lt;br /&gt;
This scroller is mounted above the door in zaal 1.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
Power to the scroller is switched along with the power to the *zaal 1 amplifier*.&lt;br /&gt;
&lt;br /&gt;
=== Network ===&lt;br /&gt;
The scroller itself has the following network configuration:&lt;br /&gt;
* host name ESP-74AAEB.dhcp.nurd.space&lt;br /&gt;
* port 5000 (UDP): accepts a text message, the message is scrolled once, right-to-left&lt;br /&gt;
* port 8888 (UDP): accepts a 560 byte (80x7 pixel) frame with 8-bit intensity data&lt;br /&gt;
&lt;br /&gt;
On ticker-proxy.vm.nurd.space port 5108 listens for UDP pixelflood (text!).&lt;br /&gt;
Port 5120 (also UDP) listens for text messages.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scarlettscroller.jpg|640px]]&lt;br /&gt;
&lt;br /&gt;
=== Audio ===&lt;br /&gt;
The plan is to show an audio waveform if music/audio is playing.&lt;br /&gt;
* snap client protocol https://github.com/badaix/snapcast/blob/master/doc/binary_protocol.md&lt;br /&gt;
&lt;br /&gt;
The display shows part of the waveform:&lt;br /&gt;
&lt;br /&gt;
Concepts/calculation:&lt;br /&gt;
* about 10 updates/second, say about 4096 bytes per frame (44100 samples/second)&lt;br /&gt;
* use FFT to find the waveform segment that best matches the currently displayed waveform&lt;br /&gt;
* algorithm: complex FFT of both current waveform and segment to search in, multitply by complex conjugate, IFFT then find largest correlation peak&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11729</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11729"/>
		<updated>2022-05-06T12:35:14Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Integration into nurdspace infrastructure */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=Scarlett Scroller&lt;br /&gt;
|Skills=Hacking, Electronics, Programming, making, lights,&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Artsy stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=Zaal1&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0016 (3).JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0017 (1).JPG&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:ScarlettScroller.gif|right|Scarlett Scroller]]&lt;br /&gt;
&lt;br /&gt;
For questions about this project, see [[User:Bertrik]] on how to contact me.&lt;br /&gt;
&lt;br /&gt;
This page is about modifying a 80x7 pixel scrolling red LED sign with an alternative controller (ESP8266) running custom firmware.&lt;br /&gt;
This makes it possible to use the LED sign as a networked display (WiFi), with pixels that can be individually dimmed in 255 levels.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
(as viewed on the controller board)&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;br /&gt;
&lt;br /&gt;
== Integration into nurdspace infrastructure ==&lt;br /&gt;
This scroller is mounted above the door in zaal 1.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
Power to the scroller is switched along with the power to the *zaal 1 amplifier*.&lt;br /&gt;
&lt;br /&gt;
=== Network ===&lt;br /&gt;
The scroller itself has the following network configuration:&lt;br /&gt;
* host name ESP-74AAEB.dhcp.nurd.space&lt;br /&gt;
* port 5000 (UDP): accepts a text message, the message is scrolled 3 times&lt;br /&gt;
* port 8888 (UDP): accepts a 560 byte (80x7 pixel) frame with 8-bit intensity data&lt;br /&gt;
&lt;br /&gt;
On 10.208.42.159 port 5108 listens for UDP pixelflood (text!).&lt;br /&gt;
Port 5120 (also UDP) listens for text messages.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scarlettscroller.jpg|640px]]&lt;br /&gt;
&lt;br /&gt;
=== Audio ===&lt;br /&gt;
The plan is to show an audio waveform if music/audio is playing.&lt;br /&gt;
* snap client protocol https://github.com/badaix/snapcast/blob/master/doc/binary_protocol.md&lt;br /&gt;
&lt;br /&gt;
The display shows part of the waveform:&lt;br /&gt;
&lt;br /&gt;
Concepts/calculation:&lt;br /&gt;
* about 10 updates/second, say about 4096 bytes per frame (44100 samples/second)&lt;br /&gt;
* use FFT to find the waveform segment that best matches the currently displayed waveform&lt;br /&gt;
* algorithm: complex FFT of both current waveform and segment to search in, multitply by complex conjugate, IFFT then find largest correlation peak&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=User:Bertrik&amp;diff=11720</id>
		<title>User:Bertrik</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=User:Bertrik&amp;diff=11720"/>
		<updated>2022-04-30T13:57:28Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Members&lt;br /&gt;
|picture=bertrik.jpg&lt;br /&gt;
|nickname=bertrik&lt;br /&gt;
|Memberstatus=friend&lt;br /&gt;
|email=bertrik@gmail.com&lt;br /&gt;
|Project=ScarlettScroller,&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Project ideas ==&lt;br /&gt;
=== Portal mirrors ===&lt;br /&gt;
Basically two oval mirrors mounted opposite each other, one backed with orange lights, the other backed with blue lights:&lt;br /&gt;
&lt;br /&gt;
Suitable mirrors:&lt;br /&gt;
* https://www.gamma.nl/assortiment/plieger-fitline-passpiegel-zilver-27x38-cm/p/B643353&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=User:Bertrik&amp;diff=11719</id>
		<title>User:Bertrik</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=User:Bertrik&amp;diff=11719"/>
		<updated>2022-04-30T13:19:45Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Members&lt;br /&gt;
|picture=bertrik.jpg&lt;br /&gt;
|nickname=bertrik&lt;br /&gt;
|Memberstatus=friend&lt;br /&gt;
|email=bertrik@gmail.com&lt;br /&gt;
|Project=ScarlettScroller,&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Project ideas ==&lt;br /&gt;
=== Portal mirrors ===&lt;br /&gt;
Basically two oval mirrors mounted towards each other, one backed with orange lights, the other backed with blue lights:&lt;br /&gt;
&lt;br /&gt;
Suitable mirrors:&lt;br /&gt;
* https://www.gamma.nl/assortiment/plieger-fitline-passpiegel-zilver-27x38-cm/p/B643353&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11702</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11702"/>
		<updated>2022-04-24T20:21:49Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=Scarlett Scroller&lt;br /&gt;
|Skills=Hacking, Electronics, Programming, making, lights,&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Artsy stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=Zaal1&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0016 (3).JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0017 (1).JPG&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:ScarlettScroller.gif|right|Scarlett Scroller]]&lt;br /&gt;
&lt;br /&gt;
For questions about this project, see [[User:Bertrik]] on how to contact me.&lt;br /&gt;
&lt;br /&gt;
This page is about modifying a 80x7 pixel scrolling red LED sign with an alternative controller (ESP8266) running custom firmware.&lt;br /&gt;
This makes it possible to use the LED sign as a networked display (WiFi), with pixels that can be individually dimmed in 255 levels.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
(as viewed on the controller board)&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;br /&gt;
&lt;br /&gt;
== Integration into nurdspace infrastructure ==&lt;br /&gt;
This scroller is mounted above the door in zaal 1.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
Power to the scroller is switched along with the power to the *zaal 1 amplifier*.&lt;br /&gt;
&lt;br /&gt;
=== Network ===&lt;br /&gt;
The scroller itself has the following network configuration:&lt;br /&gt;
* host name ESP-74AAEB.dhcp.nurd.space&lt;br /&gt;
* port 5000 (UDP): accepts a text message, the message is scrolled 3 times&lt;br /&gt;
* port 8888 (UDP): accepts a 560 byte (80x7 pixel) frame with 8-bit intensity data&lt;br /&gt;
&lt;br /&gt;
On 10.208.42.159 port 5108 listens for UDP pixelflood (text!).&lt;br /&gt;
Port 5120 (also UDP) listens for text messages.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scarlettscroller.jpg|640px]]&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11701</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11701"/>
		<updated>2022-04-24T20:19:13Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* network */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=Scarlett Scroller&lt;br /&gt;
|Skills=Hacking, Electronics, Programming, making, lights,&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=Artsy stuff&lt;br /&gt;
|Purpose=Fun&lt;br /&gt;
|Picture=ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
|Tool=Yes&lt;br /&gt;
|Location=Zaal1&lt;br /&gt;
|Category=Electronics&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:ScarlettScroller_IMG_0015.JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0016 (3).JPG&lt;br /&gt;
Image:ScarlettScroller_IMG_0017 (1).JPG&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:ScarlettScroller.gif|right|Scarlett Scroller]]&lt;br /&gt;
&lt;br /&gt;
For questions about this project, see [[User:Bertrik]] on how to contact me.&lt;br /&gt;
&lt;br /&gt;
This page is about modifying a 80x7 pixel scrolling red LED sign with an alternative controller (ESP8266) running custom firmware.&lt;br /&gt;
This makes it possible to use the LED sign as a networked display (WiFi), with pixels that can be individually dimmed in 255 levels.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
(as viewed on the controller board)&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== network ==&lt;br /&gt;
The scroller itself has the following network configuration:&lt;br /&gt;
* host name ESP-74AAEB.dhcp.nurd.space&lt;br /&gt;
* port 5000 (UDP): accepts a text message, the message is scrolled 3 times&lt;br /&gt;
* port 8888 (UDP): accepts a 560 byte (80x7 pixel) frame with 8-bit intensity data&lt;br /&gt;
&lt;br /&gt;
On 10.208.42.159 port 5108 listens for UDP pixelflood (text!).&lt;br /&gt;
Port 5120 (also UDP) listens for text messages.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Scarlettscroller.jpg|640px]]&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11396</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11396"/>
		<updated>2022-03-29T18:32:32Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Control connector */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:ScarlettScroller.gif|right|Scarlett Scroller]]&lt;br /&gt;
&lt;br /&gt;
For questions about this project, see [[User:Bertrik]] on how to contact me.&lt;br /&gt;
&lt;br /&gt;
This page is about modifying a 80x7 pixel scrolling red LED sign with an alternative controller (ESP8266) running custom firmware.&lt;br /&gt;
This makes it possible to use the LED sign as a networked display (WiFi), with pixels that can be individually dimmed in 255 levels.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
(as viewed on the controller board)&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11368</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11368"/>
		<updated>2022-03-28T22:15:43Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:ScarlettScroller.gif|right|Scarlett Scroller]]&lt;br /&gt;
&lt;br /&gt;
For questions about this project, see [[User:Bertrik]] on how to contact me.&lt;br /&gt;
&lt;br /&gt;
This page is about modifying a 80x7 pixel scrolling red LED sign with an alternative controller (ESP8266) running custom firmware.&lt;br /&gt;
This makes it possible to use the LED sign as a networked display (WiFi), with pixels that can be individually dimmed in 255 levels.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11367</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11367"/>
		<updated>2022-03-28T22:05:38Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: Add link to user page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Picture=ScarlettScroller.gif&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=Space&lt;br /&gt;
|Participants=Bertrik&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
For questions about this project, see [[User:Bertrik]] on how to contact me.&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11366</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11366"/>
		<updated>2022-03-28T22:03:35Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: is this supposed to work?&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Picture=ScarlettScroller.gif&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=Space&lt;br /&gt;
|Participants=Bertrik&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11365</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11365"/>
		<updated>2022-03-28T22:02:09Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: try to fix project properties&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Participants=Bertrik&lt;br /&gt;
|Skills=yes&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Niche=yes&lt;br /&gt;
|Purpose=Information viewer&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Picture=ScarlettScroller.gif&lt;br /&gt;
|Location=space&lt;br /&gt;
|Cost=priceless&lt;br /&gt;
|Tool category=never gonna give you up&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11364</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11364"/>
		<updated>2022-03-28T21:59:09Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Participants=Bertrik&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Purpose=Information viewer&lt;br /&gt;
|Picture=ScarlettScroller.gif&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=space&lt;br /&gt;
|Niche=yes&lt;br /&gt;
|Cost=priceless&lt;br /&gt;
|Skills=yes&lt;br /&gt;
|Tool category=never gonna give you up&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11362</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11362"/>
		<updated>2022-03-28T21:55:54Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Participants=Bertrik,bertrik,https://nurdspace.nl/Bertrik&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Purpose=Information viewer&lt;br /&gt;
|Picture=ScarlettScroller.gif&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=space&lt;br /&gt;
|Niche=yes&lt;br /&gt;
|Cost=priceless&lt;br /&gt;
|Skills=yes&lt;br /&gt;
|Tool category=never gonna give you up&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11349</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11349"/>
		<updated>2022-03-28T09:35:26Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Theory of operation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Purpose=Information viewer&lt;br /&gt;
|Picture=ScarlettScroller.gif&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=space&lt;br /&gt;
|Participants=Bertrik,bertrik&lt;br /&gt;
|Niche=yes&lt;br /&gt;
|Cost=priceless&lt;br /&gt;
|Skills=yes&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
Selecting row 0 (A, B, C all 0) disables the display, i.e. does not light any row.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11348</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11348"/>
		<updated>2022-03-28T09:34:02Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Control connector */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Purpose=Information viewer&lt;br /&gt;
|Picture=ScarlettScroller.gif&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=space&lt;br /&gt;
|Participants=Bertrik,bertrik&lt;br /&gt;
|Niche=yes&lt;br /&gt;
|Cost=priceless&lt;br /&gt;
|Skills=yes&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select LSB&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select MSB&lt;br /&gt;
* pin 8: D = appears to not be connected to anything&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11347</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11347"/>
		<updated>2022-03-28T09:31:27Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: project metadata&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Purpose=Information viewer&lt;br /&gt;
|Picture=ScarlettScroller.gif&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=space&lt;br /&gt;
|Participants=Bertrik,bertrik&lt;br /&gt;
|Niche=yes&lt;br /&gt;
|Cost=priceless&lt;br /&gt;
|Skills=yes&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select&lt;br /&gt;
* pin 8: D = not clear what this is, perhaps this is just another bit for the row selector, not actually used for this particular board&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11340</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11340"/>
		<updated>2022-03-27T20:30:17Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Control connector */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Purpose=Information viewer&lt;br /&gt;
|Picture=ScarlettScroller.gif&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=space&lt;br /&gt;
|Participants=Bertrik&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select&lt;br /&gt;
* pin 8: D = not clear what this is, perhaps this is just another bit for the row selector, not actually used for this particular board&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP1&lt;br /&gt;
|-&lt;br /&gt;
| GND || D || B || R || SCLK&lt;br /&gt;
|-&lt;br /&gt;
| GND || C || A || G || SCLK&lt;br /&gt;
|}&lt;br /&gt;
(as viewed from the back side)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11336</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11336"/>
		<updated>2022-03-27T15:32:48Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Purpose=Information viewer&lt;br /&gt;
|Picture=&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=space&lt;br /&gt;
|Participants=Bertrik&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, e.g. as a networked display.&lt;br /&gt;
Pixels can be individually dimmed using PWM, which is not possible using the original controller.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select&lt;br /&gt;
* pin 8: D = not clear what this is, perhaps this is just another bit for the row selector, not actually used for this particular board&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
	<entry>
		<id>https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11332</id>
		<title>ScarlettScroller</title>
		<link rel="alternate" type="text/html" href="https://nurdspace.nl/index.php?title=ScarlettScroller&amp;diff=11332"/>
		<updated>2022-03-26T21:22:20Z</updated>

		<summary type="html">&lt;p&gt;Bertrik: /* Theory of operation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Project&lt;br /&gt;
|Name=ScarlettScroller&lt;br /&gt;
|Status=Active&lt;br /&gt;
|Purpose=Information viewer&lt;br /&gt;
|Picture=&lt;br /&gt;
|Tool=No&lt;br /&gt;
|Location=space&lt;br /&gt;
|Participants=Bertrik&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This page is about a 80x7 pixel scrolling red LED sign.&lt;br /&gt;
The point of the firmware is to allow it the led sign to be controlled as a framebuffer, with independent brightness control for each pixel.&lt;br /&gt;
&lt;br /&gt;
== Hardware ==&lt;br /&gt;
The model number is AM03127.&lt;br /&gt;
&lt;br /&gt;
It has 16 elements of 5x7 red LEDs each, for a total of 80x7 LEDs.&lt;br /&gt;
This particular board has monochrome LEDs only.&lt;br /&gt;
&lt;br /&gt;
The electronics consist of two boards: a controller board and a LED board.&lt;br /&gt;
&lt;br /&gt;
The LED board has the following ICs:&lt;br /&gt;
* SN74HC138: 3-to-8 line decoder/multiplexer&lt;br /&gt;
* SN74HC04: 6 inverters&lt;br /&gt;
* 10x SN74HC164: 8-bit parallel-out serial shift registers&lt;br /&gt;
* 4x APM4953: dual P-Channel Enhancement Mode Mosfet &lt;br /&gt;
&lt;br /&gt;
The boards are connected through a 10 pin connector and a 5V power connector.&lt;br /&gt;
&lt;br /&gt;
=== Control connector ===&lt;br /&gt;
[[File:lichtkrant_flok_jp7.jpg|thumb|right|Lichtkrant connector]]&lt;br /&gt;
&lt;br /&gt;
Pinout:&lt;br /&gt;
* pin 1: SCLK&lt;br /&gt;
* pin 2: SCLK (shorted to pin 1)&lt;br /&gt;
* pin 3: G = &#039;green&#039; data bit shifted into row, goes through inverter 6&lt;br /&gt;
* pin 4: R = &#039;red&#039; data bit, goes through inverter 1&lt;br /&gt;
* pin 5: A = row select&lt;br /&gt;
* pin 6: B = row select&lt;br /&gt;
* pin 7: C = row select&lt;br /&gt;
* pin 8: D = not clear what this is, perhaps this is just another bit for the row selector, not actually used for this particular board&lt;br /&gt;
* pin 9: GND&lt;br /&gt;
* pin 10: GND&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;caption-side:bottom; text-align:center;&amp;quot;&lt;br /&gt;
|+JP7&lt;br /&gt;
|-&lt;br /&gt;
|  SCLK|| SCLK&lt;br /&gt;
|-&lt;br /&gt;
| R || G&lt;br /&gt;
|-&lt;br /&gt;
| B || A&lt;br /&gt;
|-&lt;br /&gt;
| D || C&lt;br /&gt;
|-&lt;br /&gt;
| GND || GND&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Unfortunately the connector does not seem to carry 5V. If that were the case, a replacement microcontroller could be powered directly from the connector, with the main power entering through the 5V power plug.&lt;br /&gt;
&lt;br /&gt;
The display can be blanked by selecting row 0, e.g. signals A, B and C all 0.&lt;br /&gt;
&lt;br /&gt;
=== Power ===&lt;br /&gt;
The control board is powered by a 12V supply and probably contains a step-down converter to turn it into 5V internally.&lt;br /&gt;
&lt;br /&gt;
== Theory of operation ==&lt;br /&gt;
There are 80 pixels horizontally and 10 serial-parallel chips with 8 outputs each,&lt;br /&gt;
so one row of pixels can be kept in the shift registers.&lt;br /&gt;
&lt;br /&gt;
The 3-to-8 decoder selects one particular row to light, through pins A/B/C.&lt;br /&gt;
The MOSFETs are used as drivers.&lt;br /&gt;
 &lt;br /&gt;
The SCLK signal goes to the CLK input of all serial-parallel SN74HC164 chips.&lt;br /&gt;
&lt;br /&gt;
The LED board is prepared to be used with R+G LED modules, however this particular board does not have the shift register populated for the dual-color.&lt;br /&gt;
&lt;br /&gt;
It appears there is no &#039;latch&#039; signal, although the controller board has the text &#039;LAT&#039;.&lt;br /&gt;
A latch signal could activate the row data after it&#039;s been written to the shift registers, thereby avoiding the pixels showing up already as they&#039;re being written and reducing the contrast.&lt;br /&gt;
&lt;br /&gt;
== Firmware ==&lt;br /&gt;
Github archive: https://github.com/bertrik/scarlettscroller&lt;br /&gt;
&lt;br /&gt;
The firmware run this on an ESP8266 (wemos d1 mini), which is connected to the LED board through dupont-wire.&lt;br /&gt;
&lt;br /&gt;
The firmware connects to the local wifi network (sets up a captive portal when no wifi has been configured yet).&lt;br /&gt;
Then the framebuffer can be accessed over UDP port 8888. Just send a UDP frame consisting of 80x7 bytes, each byte representing a brightness.&lt;/div&gt;</summary>
		<author><name>Bertrik</name></author>
	</entry>
</feed>