52Pi Wiki - User contributions [en]

File:EP-0187-03.jpg

2026-10-13T08:50:20Z

Yoyojacky: Yoyojacky uploaded a new version of File:EP-0187-03.jpg

Z-0177

2026-10-10T05:45:20Z

Yoyojacky: Blanked the page

P-0036

2026-09-15T09:22:49Z

Yoyojacky: /* Gallery */

==DeskPi Raspberry Pi 4 USB-C Power Supply (P-0036)==
[[File:P-0036-3.jpg|right|320px]]
5V/4A USB-C power supply with inline rocker switch, certified for Raspberry Pi 4 Model B

==Description==

The DeskPi Raspberry Pi 4 USB-C Power Supply (P-0036) is a CE-certified 5.1V/4A USB-C adapter designed specifically for the Raspberry Pi 4 Model B (1GB / 2GB / 4GB). Its integrated PSU + cable design with an inline ON/OFF rocker eliminates repeated plug/unplug cycles, while the fireproof PC enclosure and smart chip protect your Pi against short circuits, overvoltage, overheating, and overcurrent.

==Key Features==

* <strong>Designed for Raspberry Pi 4:</strong> Stable 4A output under overload and short-circuit conditions.
* <strong>Integrated PSU + Cable:</strong> Single-piece design with an inline ON/OFF rocker switch.
* <strong>Multi-Protection Design:</strong> Over-charge, over-voltage, temperature, over-current, and short-charge protection.
* <strong>Fireproof PC Enclosure:</strong> Durable housing with built-in smart protection chip.
* <strong>CE Certified:</strong> Pi 4B PSU with CE certification, 5.1V 4A 20.4W output, 1.5 m cable.
* <strong>Universal USB-C Compatibility:</strong> Works also works for other Type-C devices within the 5V/4A envelope.

==Technical Specifications==
{| class="wikitable"
|-
! Specification
! Details
|-
| '''Model SKU'''
| P-0036
|-
| '''Target Board'''
| Raspberry Pi 4 Model B (1GB / 2GB / 4GB)
|-
| '''Output Voltage'''
| DC 5.1V
|-
| '''Output Current'''
| 4A (20.4W)
|-
| '''Input Voltage'''
| AC 100–240V
|-
| '''Input Frequency'''
| 50–60Hz
|-
| '''Input Current'''
| 0.8A
|-
| '''Connector'''
| USB Type-C
|-
| '''Cable Length'''
| 1.5 m
|-
| '''Switch'''
| Inline ON/OFF rocker
|-
| '''Certifications'''
| CE, RoHS
|-
| '''Case Material'''
| Fireproof PC
|}

==Gallery==
* Product Outlook
[[File:P-0036-3.jpg|left|800px]]
<br style="clear:both;">
* Features
[[File:P-0036-8.jpg|left|800px]]
<br style="clear:both;">

P-0036

2026-09-15T09:22:33Z

Yoyojacky: /* DeskPi Raspberry Pi 4 USB-C Power Supply (P-0036) */

==DeskPi Raspberry Pi 4 USB-C Power Supply (P-0036)==
[[File:P-0036-3.jpg|right|320px]]
5V/4A USB-C power supply with inline rocker switch, certified for Raspberry Pi 4 Model B

==Description==

The DeskPi Raspberry Pi 4 USB-C Power Supply (P-0036) is a CE-certified 5.1V/4A USB-C adapter designed specifically for the Raspberry Pi 4 Model B (1GB / 2GB / 4GB). Its integrated PSU + cable design with an inline ON/OFF rocker eliminates repeated plug/unplug cycles, while the fireproof PC enclosure and smart chip protect your Pi against short circuits, overvoltage, overheating, and overcurrent.

==Key Features==

* <strong>Designed for Raspberry Pi 4:</strong> Stable 4A output under overload and short-circuit conditions.
* <strong>Integrated PSU + Cable:</strong> Single-piece design with an inline ON/OFF rocker switch.
* <strong>Multi-Protection Design:</strong> Over-charge, over-voltage, temperature, over-current, and short-charge protection.
* <strong>Fireproof PC Enclosure:</strong> Durable housing with built-in smart protection chip.
* <strong>CE Certified:</strong> Pi 4B PSU with CE certification, 5.1V 4A 20.4W output, 1.5 m cable.
* <strong>Universal USB-C Compatibility:</strong> Works also works for other Type-C devices within the 5V/4A envelope.

==Technical Specifications==
{| class="wikitable"
|-
! Specification
! Details
|-
| '''Model SKU'''
| P-0036
|-
| '''Target Board'''
| Raspberry Pi 4 Model B (1GB / 2GB / 4GB)
|-
| '''Output Voltage'''
| DC 5.1V
|-
| '''Output Current'''
| 4A (20.4W)
|-
| '''Input Voltage'''
| AC 100–240V
|-
| '''Input Frequency'''
| 50–60Hz
|-
| '''Input Current'''
| 0.8A
|-
| '''Connector'''
| USB Type-C
|-
| '''Cable Length'''
| 1.5 m
|-
| '''Switch'''
| Inline ON/OFF rocker
|-
| '''Certifications'''
| CE, RoHS
|-
| '''Case Material'''
| Fireproof PC
|}

==Gallery==
* Product Outlook
[File:P-0036-3.jpg|left|800px]]
<br style="clear:both;">
* Features
[File:P-0036-8.jpg|left|800px]]
<br style="clear:both;">

P-0036

2026-09-15T09:22:23Z

Yoyojacky: Created page with "==DeskPi Raspberry Pi 4 USB-C Power Supply (P-0036)== [File:P-0036-3.jpg|right|320px] 5V/4A USB-C power supply with inline rocker switch, certified for Raspberry Pi 4 Model B ==Description== The DeskPi Raspberry Pi 4 USB-C Power Supply (P-0036) is a CE-certified 5.1V/4A USB-C adapter designed specifically for the Raspberry Pi 4 Model B (1GB / 2GB / 4GB). Its integrated PSU + cable design with an inline ON/OFF rocker eliminates repeated plug/unplug cycles, while the fir..."

==DeskPi Raspberry Pi 4 USB-C Power Supply (P-0036)==
[File:P-0036-3.jpg|right|320px]
5V/4A USB-C power supply with inline rocker switch, certified for Raspberry Pi 4 Model B

==Description==

The DeskPi Raspberry Pi 4 USB-C Power Supply (P-0036) is a CE-certified 5.1V/4A USB-C adapter designed specifically for the Raspberry Pi 4 Model B (1GB / 2GB / 4GB). Its integrated PSU + cable design with an inline ON/OFF rocker eliminates repeated plug/unplug cycles, while the fireproof PC enclosure and smart chip protect your Pi against short circuits, overvoltage, overheating, and overcurrent.

==Key Features==

* <strong>Designed for Raspberry Pi 4:</strong> Stable 4A output under overload and short-circuit conditions.
* <strong>Integrated PSU + Cable:</strong> Single-piece design with an inline ON/OFF rocker switch.
* <strong>Multi-Protection Design:</strong> Over-charge, over-voltage, temperature, over-current, and short-charge protection.
* <strong>Fireproof PC Enclosure:</strong> Durable housing with built-in smart protection chip.
* <strong>CE Certified:</strong> Pi 4B PSU with CE certification, 5.1V 4A 20.4W output, 1.5 m cable.
* <strong>Universal USB-C Compatibility:</strong> Works also works for other Type-C devices within the 5V/4A envelope.

==Technical Specifications==
{| class="wikitable"
|-
! Specification
! Details
|-
| '''Model SKU'''
| P-0036
|-
| '''Target Board'''
| Raspberry Pi 4 Model B (1GB / 2GB / 4GB)
|-
| '''Output Voltage'''
| DC 5.1V
|-
| '''Output Current'''
| 4A (20.4W)
|-
| '''Input Voltage'''
| AC 100–240V
|-
| '''Input Frequency'''
| 50–60Hz
|-
| '''Input Current'''
| 0.8A
|-
| '''Connector'''
| USB Type-C
|-
| '''Cable Length'''
| 1.5 m
|-
| '''Switch'''
| Inline ON/OFF rocker
|-
| '''Certifications'''
| CE, RoHS
|-
| '''Case Material'''
| Fireproof PC
|}

==Gallery==
* Product Outlook
[File:P-0036-3.jpg|left|800px]]
<br style="clear:both;">
* Features
[File:P-0036-8.jpg|left|800px]]
<br style="clear:both;">

File:P-0036-8.jpg

2026-09-15T09:21:57Z

Yoyojacky:

File:P-0036-3.jpg

2026-09-15T09:20:31Z

Yoyojacky:

Main Page

2026-09-15T08:12:00Z

Yoyojacky: /* P-Series (6 items) */

<div style="border:1px solid #a2a9b1; background:#f8f9fa; padding:12px; margin:0 0 16px 0;">
'''For AI assistants and automated tools:''' Please use the AI-friendly Markdown version of this documentation: [https://wiki-md.52pi.com/ https://wiki-md.52pi.com/]
</div>

='''RaspberryPi Modules'''=
The following contents include all of our products, Top10 modules are list here, those modules are fit for Raspberry Pi A，A+，B，B+，2 Model B，3 Model B and some other platform.
you can select one of them and click the links to get more information about it.
==HCL==
This is Hardware Compatible List. <font color=red>Depracated</font></br>
[[Hardware Compatible List]]

==UPS series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* UPS Gen 6 power module compatible with Raspberry Pi 5/4B: [[ EP-0245 ]] <font color=red>NEW!!</font><br>
* SBS module for UPS Gen 6 [[ EP-0256 ]] <font color=red>NEW!!</font><br>
* SATA Drive Power Board for UPS Gen 6: [[ EP-0252 ]] <font color=red>NEW!!</font><br>
* 1.3" LCD TFT Display Module for UPS Gen 6: [[ EP-0251 ]] <font color=red>NEW!!</font><br>
</td>
</tr>
</table>

==Rackmount Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* 1U 19-inch Removable Rack mount For RPi5/4B/3B+ [[ DR-0003 ]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DR-0002]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DP-0046]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 5: [[ DR-0001 ]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 4B: [[ EP-0143 ]]
* 19-inch 2U Rack Mount for Raspberry Pi [[DR-0005]]
</td>
</tr>
</table>

==Arduino Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
===Arduino UNO Q Series===
* Level-Shift Shield [[ EP-0257 ]] <font color=red>NEW</font><br>
* Arduino Nano ESP32 RGB LED Matrix Shield [[ EP-0263]] <font color=red>NEW</font><br>
* Terminal Expansion Base for Arduino NANO ESP32 [[ EP-0262 ]] <font color=red>NEW</font><br>

===Arduino UNO R4 Wi-Fi Series===
* [[ KZ-0054 ]]
* [[ KZ-0077 ]]
* [[ KZ-0086 ]]
</td>
</tr>
</table>

==52Pi N Series==
===Description===
The 52Pi N series is a line of storage products where "N" stands for NAS (Network Attached Storage), and the numerical designation represents various models and product types. Users can choose different types based on their specific needs to fulfill their usage requirements.
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">

==Product SKU==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* W03-New - [[ EP-0216-NEW ]] <font color=red>NEW</font><br>
* RS-P13 - [[ EP-0249 ]] <font color=red>NEW</font><br>
* S021 - [[ EP-0242 ]] <font color=red>NEW</font><br>
* N16 - [[ EP-0180 ]] <font color=red>NEW</font><br>
* P33 - [[ EP-0241 ]] <font color=red>NEW</font><br>
* P31 - [[ EP-0240 ]] <font color=red>NEW</font><br>
* P30 - [[ EP-0238 ]] <font color=red>NEW</font><br>
* CN01 - [[ EP-0236 ]] <font color=red>NEW</font><br>
* N06 - [[ EP-0239 ]] <font color=red>NEW</font><br>
* RS-P11 - [[ EP-0234 ]] <font color=red>NEW</font><br>
* B14 - [[ EP-0233 ]] <font color=red>NEW</font><br>
* N12 - [[ EP-0213 ]] <font color=red>NEW</font><br>
* U2500 - [[ EP-0235 ]] <font color=red>NEW</font><br>
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N21 - [[ EP-0231 ]] <font color=red>NEW</font><br>
* N20 - [[ EP-0227 ]] <font color=red>NEW</font><br>
* W01 - [[ EP-0228 ]] <font color=red>NEW</font><br>
* N10 - [[ EP-0229 ]] <font color=red>NEW</font><br>
* B12 - [[ EP-0230 ]] <font color=red>NEW</font><br>
* M01 - [[ EP-0223 ]] <font color=red>NEW</font><br>
* M02 - [[ EP-0217 ]] <font color=red>NEW</font><br>
* N05 - [[ EP-0209 ]] <font color=red>NEW</font><br>

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N04 - [[ EP-0210 ]] <font color=red>NEW</font><br>
* N07 - [[ EP-0211 ]] <font color=red>NEW</font><br>
* P02 - [[ EP-0219 ]] <font color=red>NEW</font><br>
* 52Pi NVDAC - [[ EP-0218 ]]
* 52Pi NVdigi - [[ EP-0220 ]]
* M.2 2242 NVME SSD for RPi 5 NES-CASE - [[ EP-0212 ]]
* W03 - [[ EP-0216 ]]
* Ice tower plus for RPi 5 - [[ EP-0224 ]]
</td></tr></table>
<br>

==Mini Tower Kit Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0187 ]] <font color=red>NEW</font>
* [[ ZP-0172 ]]
* [[ ZP-0128 ]]
* [[ ZP-0128-3B ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0128-4wire ]]
* [[ ZP-0129-4wire ]]
* [[ ZP-0130-4wire ]]
</td>

<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0129 ]]
* [[ ZP-0130 ]]
* [[ ZP-0132 ]]
</td>
</tr>
</table>

==Hat Stack==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0167 ]]
* [[ EP-0168 ]]
* [[ EP-0166 ]]
* [[ EP-0152 ]]
* [[ EP-0116 ]]
* [[ EP-0098 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0099 ]]
* [[ EP-0104 ]]
* [[ EP-0106 ]]
* [[ EP-0107 ]]
* [[ EP-0108 ]]
* [[ EP-0109 ]]
* [[ EP-0105 ]]
</td></tr></table>

==Starter Kit==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0067 ]]
* [[ KZ-0061 ]]
* [[ KZ-0016 ]]
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0020 ]]
* [[ KZ-0009 ]]
</td></tr></table>

==Development Boards==
===RP2040 Series===
* [[ EP-0174 ]]
===StarFive2===
* [[ ER-0043 ]]
* [[ ER-0044 ]]

===Micro:Bit===
* [[ KR-0004 ]]
* [[ KR-0027 ]]

===ROCK Pi Series===
* [[ EP-0265 ]]
* [[ KR-0001 ]]
* [[ KR-0012 ]]
* [[ ZP-0148 ]]

===Orange Pi Series===
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0156 ]]
* [[ ZP-0150 ]]
* [[ ZP-0149 ]]
* [[ F-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ F-0021 ]]
* [[ F-0022 ]]
* [[ KZ-0003 ]]
* [[ ER-0045 ]]
</td>
</tr>
</table>

===Raspberry Pi Pico Series===
* [[ KR-0006 ]]
* [[ EP-0175 ]]

==AI Learning==
* [[ EZ-0075 ]]
* [[ L-0031 ]]

==IoT Modules==
* [[ EP-0090 ]]
* [[ EZ-0061 ]]
* [[ EZ-0062 ]]
* [[ EZ-0063 ]]
----

==Tinker Board==
* [[ EZ-0066 ]]
* [[ EZ-0065 ]]

----
===DeskPi Series===
* [[ DP-0002 ]]
* [[ DP-0018 ]]

==KZ series==
* [[ KZ-0022 ]]
* [[ KZ-0056 ]]
* [[ KZ-0058 ]]
* [[ KZ-0060 ]]

==Raspberry Pi==
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0056 ]]
* [[ KR-0024 ]]
* [[ ER-0046 ]]
* [[ ER-0035 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0031 ]]
* [[ ER-0030 ]]
* [[ ER-0027 ]]
* [[ ER-0028 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0018 ]]
* [[ ER-0007 ]]
* [[ K-0231 ]]
* [[ K-0230 ]]
</td></tr></table>

----

===Raspberry Pi Pico & Pico W Breakout Board===
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0172 ]]
* [[ EP-0164 ]]
* [[ EP-0159 ]]
* [[ EP-0145 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0138 ]]
* [[ EP-0139 ]]
* [[ EP-0140 ]]
* [[ K-0582 ]]
* [[ K-0586 ]]
</tr></td></table>

==Banana Pi==
* [[ EB-0028 ]]
* [[ EB-0023 ]]
* [[ EB-0020 ]]
* [[ EP-0019 ]]
* [[ EB-0012 ]]
* [[ EB-0013 ]]

==Gaming Assesories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ D-0023 ]]
* [[ Z-0261 ]]
* [[ Z-0179 ]]
* [[ Z-0279 ]]
* [[ Z-0252 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ Z-0253 ]]
* [[ Z-0254 ]]
* [[ Z-0255 ]]
* [[ Z-0257 ]]
* [[ Z-0260 ]]
</td>
</tr></table>

==Electronic Accessories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0020 ]]
* [[ K-0580 ]]
* [[ ZP-0157 ]]
* [[ ZP-0158 ]]
</td>
</tr></table>

=Extension Modules=

==EP-Series (44 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0020 ]]
* [[ EP-0021 ]]
* [[ EP-0031 ]]
* [[ EP-0059 ]]
* [[ EP-0073 ]]
* [[ EP-0080 ]]
* [[ EP-0088 ]]
* [[ EP-0091 ]]
* [[ EP-0092 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0093 ]]
* [[ EP-0094 ]]
* [[ EP-0095 ]]
* [[ EP-0096 ]]
* [[ EP-0097 ]]
* [[ EP-0100 ]]
* [[ EP-0101 ]]
* [[ EP-0114 ]]
* [[ EP-0115 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0118 ]]
* [[ EP-0120 ]]
* [[ EP-0121 ]]
* [[ EP-0123 ]]
* [[ EP-0124 ]]
* [[ EP-0125 ]]
* [[ EP-0126 ]]
* [[ EP-0127 ]]
* [[ EP-0128 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0129 ]]
* [[ EP-0130 ]]
* [[ EP-0131 ]]
* [[ EP-0136 ]]
* [[ EP-0141 ]]
* [[ EP-0142 ]]
* [[ EP-0146 ]]
* [[ EP-0149 ]]
* [[ EP-0150 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0153 ]]
* [[ EP-0171 ]]
* [[ EP-0214 ]]
* [[ EP-0215 ]]
* [[ EP-0225 ]]
* [[ EP-0243 ]]
* [[ EP-0246 ]]
* [[ EP-0247 ]]
</td>
</tr>
</table>

==D-Series (16 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0001 ]]
* [[ D-0003 ]]
* [[ D-0005 ]]
* [[ D-0006 ]]
* [[ D-0007 ]]
* [[ D-0008 ]]
* [[ D-0009 ]]
* [[ D-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0011 ]]
* [[ D-0012 ]]
* [[ D-0013 ]]
* [[ D-0015 ]]
* [[ D-0016 ]]
* [[ D-0017 ]]
* [[ D-0018 ]]
* [[ D-0020 ]]
</td>
</tr>
</table>

==P-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0036 ]]
* [[ P-0005 ]]
* [[ P-0006 ]]
* [[ P-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0011 ]]
* [[ P-0021 ]]
* [[ P-0024 ]]
</td>
</tr>
</table>

==Z-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0177 ]]
* [[ Z-0209 ]]
* [[ Z-0231 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0234 ]]
* [[ Z-0235 ]]
* [[ Z-0269 ]]
</td>
</tr>
</table>

==EZ-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0024 ]]
* [[ EZ-0048 ]]
* [[ EZ-0068 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0089 ]]
* [[ EZ-0106 ]]
</td>
</tr>
</table>

==ER-Series (4 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0014 ]]
* [[ ER-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0021 ]]
* [[ ER-0022 ]]
</td>
</tr>
</table>

==K-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0291 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0335 ]]
</td>
</tr>
</table>

==G-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ G-0002 ]]
</td>
</tr>
</table>

=Case & Enclosure & Heat sink=

==ZP-Series (78 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0024 ]]
* [[ ZP-0025 ]]
* [[ ZP-0029 ]]
* [[ ZP-0037 ]]
* [[ ZP-0038 ]]
* [[ ZP-0039 ]]
* [[ ZP-0040 ]]
* [[ ZP-0042 ]]
* [[ ZP-0049 ]]
* [[ ZP-0051 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0065 ]]
* [[ ZP-0066 ]]
* [[ ZP-0067 ]]
* [[ ZP-0068 ]]
* [[ ZP-0069 ]]
* [[ ZP-0070 ]]
* [[ ZP-0071 ]]
* [[ ZP-0072 ]]
* [[ ZP-0073 ]]
* [[ ZP-0074 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0075 ]]
* [[ ZP-0076 ]]
* [[ ZP-0077 ]]
* [[ ZP-0078 ]]
* [[ ZP-0079 ]]
* [[ ZP-0080 ]]
* [[ ZP-0081 ]]
* [[ ZP-0082 ]]
* [[ ZP-0083 ]]
* [[ ZP-0085 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0086 ]]
* [[ ZP-0087 ]]
* [[ ZP-0088 ]]
* [[ ZP-0089 ]]
* [[ ZP-0090 ]]
* [[ ZP-0091 ]]
* [[ ZP-0092 ]]
* [[ ZP-0093 ]]
* [[ ZP-0098 ]]
* [[ ZP-0099 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0100 ]]
* [[ ZP-0101 ]]
* [[ ZP-0102 ]]
* [[ ZP-0103 ]]
* [[ ZP-0105 ]]
* [[ ZP-0108 ]]
* [[ ZP-0110 ]]
* [[ ZP-0111 ]]
* [[ ZP-0112 ]]
* [[ ZP-0113 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0115 ]]
* [[ ZP-0116 ]]
* [[ ZP-0120 ]]
* [[ ZP-0133 ]]
* [[ ZP-0138 ]]
* [[ ZP-0139 ]]
* [[ ZP-0140 ]]
* [[ ZP-0141 ]]
* [[ ZP-0147 ]]
* [[ ZP-0153 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0162 ]]
* [[ ZP-0163 ]]
* [[ ZP-0164 ]]
* [[ ZP-0165 ]]
* [[ ZP-0166 ]]
* [[ ZP-0167 ]]
* [[ ZP-0168 ]]
* [[ ZP-0170 ]]
* [[ ZP-0173 ]]
* [[ ZP-0175 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0180 ]]
* [[ ZP-0181 ]]
* [[ ZP-0186 ]]
* [[ ZP-0188 ]]
* [[ ZP-0213 ]]
* [[ ZP-0215 ]]
* [[ ZP-0216 ]]
* [[ ZP-0222 ]]
</td>
</tr>
</table>

==C-Series (26 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0001 ]]
* [[ C-0002 ]]
* [[ C-0003 ]]
* [[ C-0004 ]]
* [[ C-0005 ]]
* [[ C-0006 ]]
* [[ C-0007 ]]
* [[ C-0008 ]]
* [[ C-0015 ]]
* [[ C-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0022 ]]
* [[ C-0023 ]]
* [[ C-0025 ]]
* [[ C-0027 ]]
* [[ C-0028 ]]
* [[ C-0031 ]]
* [[ C-0032 ]]
* [[ C-0033 ]]
* [[ C-0034 ]]
* [[ C-0047 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0048 ]]
* [[ C-0049 ]]
* [[ C-0050 ]]
* [[ C-0052 ]]
* [[ C-0054 ]]
* [[ C-0063 ]]
</td>
</tr>
</table>

==EP-Series (12 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0076 ]]
* [[ EP-0077 ]]
* [[ EP-0078 ]]
* [[ EP-0079 ]]
* [[ EP-0111 ]]
* [[ EP-0112 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0113 ]]
* [[ EP-0122 ]]
* [[ EP-0132 ]]
* [[ EP-0163 ]]
* [[ EP-0222 ]]
* [[ EP-0226 ]]
</td>
</tr>
</table>

==Z-Series (15 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0127 ]]
* [[ Z-0153 ]]
* [[ Z-0157 ]]
* [[ Z-0183 ]]
* [[ Z-0184 ]]
* [[ Z-0185 ]]
* [[ Z-0190 ]]
* [[ Z-0193 ]]
* [[ Z-0208 ]]
* [[ Z-0237 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0264 ]]
* [[ Z-0266 ]]
* [[ Z-0272 ]]
* [[ Z-0273 ]]
* [[ Z-0278 ]]
</td>
</tr>
</table>

==K-Series (10 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ K-0172 ]]
* [[ K-0178 ]]
* [[ K-0567 ]]
* [[ K-0583 ]]
* [[ K-0585 ]]
* [[ K-0589 ]]
* [[ K-0592 ]]
* [[ K-0595 ]]
* [[ K-0612 ]]
* [[ K-0638 ]]
</td>
</tr>
</table>

==KZ-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ KZ-0001 ]]
* [[ KZ-0002 ]]
* [[ KZ-0063 ]]
</td>
</tr>
</table>

==ER-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ ER-0011 ]]
</td>
</tr>
</table>

==EZ-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ EZ-0059 ]]
</td>
</tr>
</table>

==F-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ F-0003 ]]
</td>
</tr>
</table>

==L-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ L-0030 ]]
</td>
</tr>
</table>

=Cooling Accessories=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0001 ]]
* [[ F-0002 ]]
* [[ F-0006 ]]
* [[ F-0005 ]]
* [[ F-0007 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0010 ]]
* [[ F-0011 ]]
* [[ F-0012 ]]
* [[ D-0022 ]]
* [[ F-0008 ]]
* [[ F-0008-RGB ]]
</td>
</tr></table>

==Electronic Engineer Tools==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0022 ]]
* [[ T-0021 ]]
* [[ T-0019 ]]
* [[ T-0015 ]]
* [[ T-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0017 ]]
* [[ T-0018 ]]
* [[ Z-0241 ]]
</td></tr></table>

=Displays=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>

==EP-Series (27 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0045 ]]
* [[ EP-0058 ]]
* [[ EP-0062 ]]
* [[ EP-0063 ]]
* [[ EP-0065 ]]
* [[ EP-0066 ]]
* [[ EP-0072 ]]
* [[ EP-0075 ]]
* [[ EP-0081 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0082 ]]
* [[ EP-0084 ]]
* [[ EP-0085 ]]
* [[ EP-0087 ]]
* [[ EP-0089 ]]
* [[ EP-0119 ]]
* [[ EP-0133 ]]
* [[ EP-0148 ]]
* [[ EP-0170 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0177 ]]
* [[ EP-0183 ]]
* [[ EP-0184 ]]
* [[ EP-0185 ]]
* [[ EP-0186 ]]
* [[ EP-0187 ]] <font color=red>NEW!!!</font>
* [[ EP-0188 ]]
* [[ EP-0189 ]] <font color=red>NEW!!!</font>
* [[ EP-0190 ]]
</td>
</tr>
</table>

==Z-Series (8 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0017 ]]
* [[ Z-0051 ]]
* [[ Z-0053 ]]
* [[ Z-0111 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0112 ]]
* [[ Z-0113 ]]
* [[ Z-0114 ]]
* [[ Z-0143 ]]
</td>
</tr>
</table>

==S-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0001 ]]
* [[ S-0003 ]]
* [[ S-0005 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0006 ]]
* [[ S-0007 ]]
* [[ S-0018 ]]
</td>
</tr>
</table>

==K-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0101 ]]
* [[ K-0102 ]]
* [[ K-0103 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0104 ]]
* [[ K-0106 ]]
</td>
</tr>

=Power Supply=

==P-Series (9 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0001 ]]
* [[ P-0007 ]]
* [[ P-0008 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0009 ]]
* [[ P-0017 ]]
* [[ P-0031 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0032 ]]
* [[ P-0040 ]]
* [[ P-0044 ]]
</td>
</tr>
</table>

==Z-Series (11 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0097 ]]
* [[ Z-0121 ]]
* [[ Z-0132 ]]
* [[ Z-0133 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0136 ]]
* [[ Z-0147 ]]
* [[ Z-0148 ]]
* [[ Z-0149 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0150 ]]
* [[ Z-0154 ]]
* [[ Z-0155 ]]
</td>
</tr>
</table>

==L-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0026 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0027 ]]
</td>
</tr>
</table>

==Raspberry Pi Kits==

==K-Series (18 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0111 ]]
* [[ K-0167 ]]
* [[ K-0168 ]]
* [[ K-0169 ]]
* [[ K-0171 ]]
* [[ K-0174 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0180 ]]
* [[ K-0185 ]]
* [[ K-0186 ]]
* [[ K-0238 ]]
* [[ K-0259 ]]
* [[ K-0401 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0403 ]]
* [[ K-0502 ]]
* [[ K-0503 ]]
* [[ K-0512 ]]
* [[ K-0522 ]]
* [[ K-0581 ]]
</td>
</tr>
</table>

==Z-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0142 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0144 ]]
</td>
</tr>
</table>

==T-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ T-0008 ]]
* [[ T-0033 ]]
</td>
</tr>
</table>

EP-0214

2026-09-15T03:28:51Z

Yoyojacky: /* Getting Start */

==HDMI-TO-CSI2 adapter board for Raspberry Pi==
[[File:EP-0214-01.jpg|right|320px]]

==Descriptions==
Raspberry Pi HDMI to CSI-2 Module with Toshiba TC358743XBG chip, Hdmi-input supports up to 1080p30fps, output supports up to 60fps. Compatible with Raspberry Pi 4B/3B+/3B/Pi Zero/W/2W. HDMI To CSI Adapter for Raspberry Pi is an HDMI to CSI camera port adapter designed for the Raspberry Pi 4/3 with up to 1080p@30fps support from HDMI input and is backwards compatible. It allows you to use any camera with an HDMI output, such as Canon, Nikon or GoPro action cameras, as a standard Raspberry Pi CSI camera, even you can record the screen which is output from another Raspberry Pi HDMI port.
Raspberry Pi Computer Module 4 can use HDMI to CSI-2 Module on PiKVM OS.

<pre> NOTE: This product has provided all hardware accessories. The software can currently be used directly on Raspberry Pi 4B, 3B+/3B/Zero series and other devices. However, software support for Raspberry Pi 5 software is currently not available.
</pre>

==Features==
* Easy to assemble
* FPC cable supports 15Pin@ 2Lanes or 22Pin @ 4Lanes (CM4 Computer module only)
* Chipset: Toshiba TC358743XBG
* Input signal: Full-sized HDMI
* Soldering Pad support
* Output signal: CSI
* Function: HDMI-TO-CSI2 (H2C for short)
* Limitation: HDMI input support up to 1080p30fps
* Compatible with: Raspberry Pi 4B/3B+/3B/3A+/Pi zero/Pi zero W/Pi zero 2W
<Pre>
Note: This module does not support OctoPi OS.
</pre>

==Gallery==
* Product Size
[[File:EP-0214-02.jpg|left|800px]]
<br style="clear:both;">
* FPC cable compatibility
[[File:EP-0214-04.jpg|left|800px]]
<br style="clear:both;">
* Pinout definition
[[File:EP-0214-09.jpg|left|800px]]
<br style="clear:both;">

* Connection style
[[File:EP-0214-06.jpg|left|800px]]
<br style="clear:both;">

* Application scenario
[[File:EP-0214-05.jpg|left|800px]]
<br style="clear:both;">
[[File:EP-0214-07.jpg|left|800px]]
<br style="clear:both;">
* Recording video from an sports camera
[[File:EP-0214-08.jpg|left|800px]]
<br style="clear:both;">
==Package Includes==
* 1 x HDMI-TO-CSI2 adapter board
* 2 x 22Pin FPC cable
* 2 x 15Pin FPC cable
[[File:EP-0214-03.jpg|left|800px]]
<br style="clear:both;">

==Getting Start==
===For Raspberry Pi 4B/3B+/3B/3A+/Pi zero/Pi zero W/Pi zero 2 W===
<Pre>NOTE: We recommend you to use the Raspberry Pi OS which download from Raspberry Pi Official Website．</pre>
To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If "uname -a" reports anything less, then fix this before proceeding.
To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If "uname -a" reports anything less, then fix this before proceeding.
<pre>
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux
</pre>
1. Update & upgrade the raspberry pi system (It will take a long time depend on the different country)
<code>
sudo apt-get update
sudo apt-get upgrade
</code></br>
2. Enable camera module (the camera is enabled by default in Raspberry pi Bullseys OS)
<code>
sudo raspi-config
sudo reboot
</code><br>
Navigate to 'Interfacing Options' and hit Enter. Now select the 'Camera' option, and hit the Enter key to enable it. Select “Finish” and select to reboot your Raspberry Pi.
<pre>
[NOTE] reboot is important!!
</pre>
3. Edit /boot/config.txt (that will need sudo)
<pre>
sudo nano /boot/config.txt
</pre>
Add the line:
<pre>
dtoverlay=tc358743
dtoverlay=tc358743-audio
</pre>

4. Check the amount of memory assigned to the CMA heap with "dmesg | grep cma". The first line should be along the lines of
<pre>
pi@raspberrypi:~ $ dmesg | grep cma
[ 0.000000] cma: Reserved 256 MiB at 0x000000001ec00000
</pre>
If it reports less than 96MB assigned to CMA, then edit /boot/cmdline.txt and add
<pre>
cma=96M
</pre>
to the start of the line. Do NOT add any carriage returns.

5. Reboot. If all is well you should get a /dev/video0 device, and "v4l2-ctl --list-devices" will tell you that it is provided by Unicam. After connecting all the cables, power on the Raspberry Pi, opening the Raspberry Pi terminal, enter the following command:
<pre>
pi@raspberrypi:~ $ ls /dev/video0
</pre>
If it show following device:
<pre>
/dev/video0
</pre>
then execute following command:
<pre>
pi@raspberrypi:~ $ v4l2-ctl --list-devices
</pre>
It will shows something like:
<pre>
bcm2835-codec-decode (platform:bcm2835-codec):
/dev/video10
/dev/video11
/dev/video12
/dev/video18
/dev/media1

bcm2835-isp (platform:bcm2835-isp):
/dev/video13
/dev/video14
/dev/video15
/dev/video16
/dev/media0

unicam (platform:fe801000.csi):
/dev/video0
/dev/video1
/dev/media2
</pre>
6. This driver puts all the control in the hands of the user, or the user's application. By default there is no EDID loaded into the chip to allow it to tell the HDMI source what resolutions are supported. There are EDID editors around. If you create a file edid.txt, then you can push this to the device using

The comment of 720p edid.txt file:
<pre>
00ffffffffffff005262888800888888
1c150103800000780aEE91A3544C9926
0F505400000001010101010101010101
010101010101011d007251d01e206e28
5500c48e2100001e8c0ad08a20e02d10
103e9600138e2100001e000000fc0054
6f73686962612d4832430a20000000FD
003b3d0f2e0f1e0a2020202020200100
020321434e041303021211012021a23c
3d3e1f2309070766030c00300080E300
7F8c0ad08a20e02d10103e9600c48e21
0000188c0ad08a20e02d10103e960013
8e210000188c0aa01451f01600267c43
00138e21000098000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
</pre>
Or you can use 1080p30fps edid file:
<pre>
00 FF FF FF FF FF FF 00 52 62 88 88 00 88 88 88
1C 15 01 03 80 A0 5A 78 0A 0D C9 A0 57 47 98 27
12 48 4C 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 01 1D 80 18 71 38 2D 40 58 2C
45 00 80 38 74 00 00 1E 01 1D 80 18 71 38 2D 40
58 2C 45 00 80 38 74 00 00 1E 00 00 00 FC 00 44
43 44 5A 2D 48 32 43 20 4D 4F 44 0A 00 00 00 FD
00 14 78 01 FF 10 00 0A 20 20 20 20 20 20 01 B9
02 03 1A 71 47 A2 22 22 22 22 22 22 23 09 07 01
83 01 00 00 65 03 0C 00 10 00 01 1D 80 18 71 38
2D 40 58 2C 45 00 80 38 74 00 00 1E 01 1D 80 18
71 38 2D 40 58 2C 45 00 80 38 74 00 00 1E 01 1D
80 18 71 38 2D 40 58 2C 45 00 80 38 74 00 00 1E
01 1D 80 18 71 38 2D 40 58 2C 45 00 80 38 74 00
00 1E 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03
</pre>
1080p25fps edid file:
<pre>
00 FF FF FF FF FF FF 00 52 62 88 88 00 88 88 88
1C 15 01 03 80 A0 5A 78 0A 0D C9 A0 57 47 98 27
12 48 4C 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 01 1D 80 D0 72 38 2D 40 10 2C
45 80 80 38 74 00 00 1E 01 1D 80 18 71 38 2D 40
58 2C 45 00 80 38 74 00 00 1E 00 00 00 FC 00 44
43 44 5A 2D 48 32 43 20 4D 4F 44 0A 00 00 00 FD
00 14 78 01 FF 10 00 0A 20 20 20 20 20 20 01 C8
02 03 1A 71 47 A1 22 22 22 22 22 22 23 09 07 01
83 01 00 00 65 03 0C 00 10 00 01 1D 80 18 71 38
2D 40 58 2C 45 00 80 38 74 00 00 1E 01 1D 80 18
71 38 2D 40 58 2C 45 00 80 38 74 00 00 1E 01 1D
80 18 71 38 2D 40 58 2C 45 00 80 38 74 00 00 1E
01 1D 80 18 71 38 2D 40 58 2C 45 00 80 38 74 00
00 1E 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04

</pre>
Then you can create a file called edid.txt:
<pre>
cd ~
sudo nano edid.txt
</pre>
#copy the above commend in edid.txt, save&exit;
and then set the edid file as following:
<pre>
pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums
</pre>
It shows:
<pre>
CTA-861 Header
IT Formats Underscanned: yes
Audio: yes
YCbCr 4:4:4: no
YCbCr 4:2:2: no

HDMI Vendor-Specific Data Block
Physical Address: 3.0.0.0
YCbCr 4:4:4 Deep Color: no
30-bit: no
36-bit: no
48-bit: no

CTA-861 Video Capability Descriptor
RGB Quantization Range: yes
YCC Quantization Range: no
PT: Supports both over- and underscan
IT: Supports both over- and underscan
CE: Supports both over- and underscan
</pre>
7. The driver does NOT automatically switch to the resolution detected. Use the command:
<pre>
pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings
</pre>
It will shows something like:
<pre>
Active width: 1280
Active height: 720
Total width: 1650
Total height: 750
Frame format: progressive
Polarities: -vsync -hsync
Pixelclock: 74250000 Hz (60.00 frames per second)
Horizontal frontporch: 0
Horizontal sync: 370
Horizontal backporch: 0
Vertical frontporch: 0
Vertical sync: 30
Vertical backporch: 0
Standards:
Flags:
</pre>
You MUST set the timings via "v4l2-ctl --set-dv-bt-timings". You can pass in an index to the detected mode, or use:
<pre>
v4l2-ctl --set-dv-bt-timings query
</pre>
to select the currently detected timings.
<pre>
v4l2-ctl -V
</pre>
should now reflect the resolution detected.

8. The chip supports two formats - BGR3 (the default) and UYVY. BGR3 is 24bpp, and UYVY is YUV4:2:2 16bpp.

Over the normal 2 CSI-2 lanes the data rate is such that BGR3 can run at a maximum of 1080p30, whilst UYVY will go up to 1080p50. Use the following command to select UYVY, however your application may override that.
<pre>
v4l2-ctl -v pixelformat=UYVY
</pre>
9. Check that the audio drivers / card is available to ALSA.
<pre>
pi@raspberrypi:~ $ arecord -l
</pre>
It will display as following:
<pre>
**** List of CAPTURE Hardware Devices ****
card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
</pre>

<font color=red> Note: card 1 means that the card number for the TC358743XBG is "1" and it might be different.</font><br>

10. Install GStreamer tool;
<pre>
sudo apt install gstreamer1.0-tools
</pre>
Check gstreamer tool version:
<pre>
pi@raspberrypi:~ $ gst-launch-1.0 --version
</pre>
gst-launch-1.0 version 1.18.4
GStreamer 1.18.4
http://packages.qa.debian.org/gstreamer1.0<br>

<font color=red>
Note:
Different versions have different command line parameters, which is very annoying.
</font><br>

11. Use gstreamer to record video and audio

* GStreamer v1.14 command
<pre>
gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux.
</pre>
foo.mkv is the output file.
<br>
If your gstreamer is version 1.8 or above, you can try the following test command. In addition, alsasrc device=hw:1 represents the sound card of TC358743, you can use "arecord -l" to query. <br>

* The command to recode a video with audio. (GStreamer 1.18.4)
<pre>
gst-launch-1.0 -vvv v4l2src ! "video/x-raw,framerate=30/1,format=UYVY" ! v4l2h264enc extra-controls="controls,h264_profile=4,h264_level=13,video_bitrate=256000;" ! "video/x-h264,profile=high, level=(string)4.2" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux.
</pre>

* The sample command to recode a video without audio.
<pre>
gst-launch-1.0 -vvv v4l2src ! "video/x-raw,framerate=30/1,format=UYVY" ! v4l2h264enc extra-controls="controls,h264_profile=4,h264_level=13,video_bitrate=256000;" ! "video/x-h264,profile=high, level=(string)4.2" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv
</pre>
Press CTRL+C to end recording.<br>
<font color=red>
PS: We recommend that you modify the above framerate parameter to the actual frame rate of your HDMI signal, the actual frame rate value is from the result of 'v4l2-ctl --query-dv-timings' command.
</font><br>

==Keywords==
* HDMI-to-csi2, video capture card, HDMI recorder, HDMI signal capture board, Toshiba TC358743XBG

ZP-0181

2026-09-14T07:07:01Z

Yoyojacky: /* Features */

==GAME 5 Pi case==
[[File:ZP-0181-1.jpg|right|320px]]

==Purchase URL==
* Official Web Store: [ https://52pi.com/collections/new-arrivals/products/game5-pi-case-enlosure-shell-for-raspberry-pi-5-with-armor-lite-v5-cooler ]

==Description==
The Game 5 Pi Case is a stylish and functional enclosure designed for the Raspberry Pi, offering enhanced cooling capabilities and a retro aesthetic. This case integrates the Armor Lite V5 heatsink and fan for efficient thermal management, along with an additional side fan cooling system. Crafted from durable ABS material, the compact design includes a removable cover for the unused USB and Ethernet ports, providing extra protection when not in use.

==Features==
* <strong>Armor Lite V5 Heatsink and Fan:</strong>The case comes equipped with the Armor Lite V5 heatsink and fan, ensuring optimal thermal dissipation for the Raspberry Pi.

* <strong>Side Fan Cooling System:</strong> In addition to the main heatsink and fan, the case features a side fan cooling system to further enhance airflow and cooling efficiency.

* <strong>ABS Material:</strong> Constructed from high-quality ABS material, the case provides durability and a sleek appearance, contributing to a retro and eye-catching design.

* <strong>Compact and Retro Design: </strong>The compact form factor and retro design make the Game 5 Pi Case visually appealing while maintaining a smaller footprint.

* <strong>Movable Cover: </strong>A movable cover is included to protect the unused USB and Ethernet ports, preserving the aesthetics of the case and preventing dust or debris accumulation.

* <strong>Easy Installation: </strong>The case is designed for easy and hassle-free installation, ensuring that users can set up their Raspberry Pi quickly and securely.

* <strong>Compatibility:</strong> The Game 5 Pi Case is specifically designed for Raspberry Pi models, providing a snug fit and compatibility with various Raspberry Pi configurations.

* <strong>Ventilation and Airflow: </strong>Thoughtful ventilation and airflow design contribute to the efficient cooling of the Raspberry Pi, even during extended usage.

* <strong>Aesthetic Appeal: </strong>The combination of functional cooling elements and a retro design makes the Game 5 Pi Case an aesthetically pleasing choice for Raspberry Pi enthusiasts.

==Gallery==
* Product outlook
[[File:ZP-0181-1.jpg|left|800px]]
<br style="clear:both;">
* Movable cover
[[File:ZP-0181-2.jpg|left|800px]]
<br style="clear:both;">
* Dimension
[[File:ZP-0181-3.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-4.jpg|left|800px]]
<br style="clear:both;">
* Features
[[File:ZP-0181-6.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-8.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-11.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-10.jpg|left|800px]]
<br style="clear:both;">
* Application scenario
[[File:ZP-0181-9.jpg|left|800px]]
<br style="clear:both;">

===How to assemble it ?===
* Please follow the installation steps to assemble it.
[[File:ZP-0181-5.jpg|left|800px]]
<br style="clear:both;">
==Pacakge Includes==
* 1 x ABS Upper case for Raspberry Pi 5
* 1 x ABS Button case for Raspberry Pi 5
* 1 x Armor Lite V5 Adjustable speed Fan
* 6 x Thermal Pad
* 1 x Screw driver
* 2 x M2.5 Screw
* 4 x Self-tapping screw
[[File:ZP-0181-7.jpg|left|800px]]
<br style="clear:both;">
==Keywords==
* GAME 5 Pi case, dural fan case for Raspberry Pi 5.

ZP-0181

2026-09-14T07:06:41Z

Yoyojacky: /* Keywords */

==GAME 5 Pi case==
[[File:ZP-0181-1.jpg|right|320px]]

==Purchase URL==
* Official Web Store: [ https://52pi.com/collections/new-arrivals/products/game5-pi-case-enlosure-shell-for-raspberry-pi-5-with-armor-lite-v5-cooler ]

==Description==
The Game 5 Pi Case is a stylish and functional enclosure designed for the Raspberry Pi, offering enhanced cooling capabilities and a retro aesthetic. This case integrates the Armor Lite V5 heatsink and fan for efficient thermal management, along with an additional side fan cooling system. Crafted from durable ABS material, the compact design includes a removable cover for the unused USB and Ethernet ports, providing extra protection when not in use.

==Features==
* <strong>Armor Lite V5 Heatsink and Fan:</strong>The case comes equipped with the Armor Lite V5 heatsink and fan, ensuring optimal thermal dissipation for the Raspberry Pi.

* <strong>Side Fan Cooling System:</strong> In addition to the main heatsink and fan, the case features a side fan cooling system to further enhance airflow and cooling efficiency.

* <strong>ABS Material:</strong> Constructed from high-quality ABS material, the case provides durability and a sleek appearance, contributing to a retro and eye-catching design.

* <strong>Compact and Retro Design: </strong>The compact form factor and retro design make the Game 5Pi Case visually appealing while maintaining a smaller footprint.

* <strong>Movable Cover: </strong>A movable cover is included to protect the unused USB and Ethernet ports, preserving the aesthetics of the case and preventing dust or debris accumulation.

* <strong>Easy Installation: </strong>The case is designed for easy and hassle-free installation, ensuring that users can set up their Raspberry Pi quickly and securely.

* <strong>Compatibility:</strong> The Game 5Pi Case is specifically designed for Raspberry Pi models, providing a snug fit and compatibility with various Raspberry Pi configurations.

* <strong>Ventilation and Airflow: </strong>Thoughtful ventilation and airflow design contribute to the efficient cooling of the Raspberry Pi, even during extended usage.

* <strong>Aesthetic Appeal: </strong>The combination of functional cooling elements and a retro design makes the Game 5Pi Case an aesthetically pleasing choice for Raspberry Pi enthusiasts.
==Gallery==
* Product outlook
[[File:ZP-0181-1.jpg|left|800px]]
<br style="clear:both;">
* Movable cover
[[File:ZP-0181-2.jpg|left|800px]]
<br style="clear:both;">
* Dimension
[[File:ZP-0181-3.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-4.jpg|left|800px]]
<br style="clear:both;">
* Features
[[File:ZP-0181-6.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-8.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-11.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-10.jpg|left|800px]]
<br style="clear:both;">
* Application scenario
[[File:ZP-0181-9.jpg|left|800px]]
<br style="clear:both;">

===How to assemble it ?===
* Please follow the installation steps to assemble it.
[[File:ZP-0181-5.jpg|left|800px]]
<br style="clear:both;">
==Pacakge Includes==
* 1 x ABS Upper case for Raspberry Pi 5
* 1 x ABS Button case for Raspberry Pi 5
* 1 x Armor Lite V5 Adjustable speed Fan
* 6 x Thermal Pad
* 1 x Screw driver
* 2 x M2.5 Screw
* 4 x Self-tapping screw
[[File:ZP-0181-7.jpg|left|800px]]
<br style="clear:both;">
==Keywords==
* GAME 5 Pi case, dural fan case for Raspberry Pi 5.

ZP-0181

2026-09-14T07:06:28Z

Yoyojacky: /* Description */

==GAME 5 Pi case==
[[File:ZP-0181-1.jpg|right|320px]]

==Purchase URL==
* Official Web Store: [ https://52pi.com/collections/new-arrivals/products/game5-pi-case-enlosure-shell-for-raspberry-pi-5-with-armor-lite-v5-cooler ]

==Description==
The Game 5 Pi Case is a stylish and functional enclosure designed for the Raspberry Pi, offering enhanced cooling capabilities and a retro aesthetic. This case integrates the Armor Lite V5 heatsink and fan for efficient thermal management, along with an additional side fan cooling system. Crafted from durable ABS material, the compact design includes a removable cover for the unused USB and Ethernet ports, providing extra protection when not in use.

==Features==
* <strong>Armor Lite V5 Heatsink and Fan:</strong>The case comes equipped with the Armor Lite V5 heatsink and fan, ensuring optimal thermal dissipation for the Raspberry Pi.

* <strong>Side Fan Cooling System:</strong> In addition to the main heatsink and fan, the case features a side fan cooling system to further enhance airflow and cooling efficiency.

* <strong>ABS Material:</strong> Constructed from high-quality ABS material, the case provides durability and a sleek appearance, contributing to a retro and eye-catching design.

* <strong>Compact and Retro Design: </strong>The compact form factor and retro design make the Game 5Pi Case visually appealing while maintaining a smaller footprint.

* <strong>Movable Cover: </strong>A movable cover is included to protect the unused USB and Ethernet ports, preserving the aesthetics of the case and preventing dust or debris accumulation.

* <strong>Easy Installation: </strong>The case is designed for easy and hassle-free installation, ensuring that users can set up their Raspberry Pi quickly and securely.

* <strong>Compatibility:</strong> The Game 5Pi Case is specifically designed for Raspberry Pi models, providing a snug fit and compatibility with various Raspberry Pi configurations.

* <strong>Ventilation and Airflow: </strong>Thoughtful ventilation and airflow design contribute to the efficient cooling of the Raspberry Pi, even during extended usage.

* <strong>Aesthetic Appeal: </strong>The combination of functional cooling elements and a retro design makes the Game 5Pi Case an aesthetically pleasing choice for Raspberry Pi enthusiasts.
==Gallery==
* Product outlook
[[File:ZP-0181-1.jpg|left|800px]]
<br style="clear:both;">
* Movable cover
[[File:ZP-0181-2.jpg|left|800px]]
<br style="clear:both;">
* Dimension
[[File:ZP-0181-3.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-4.jpg|left|800px]]
<br style="clear:both;">
* Features
[[File:ZP-0181-6.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-8.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-11.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-10.jpg|left|800px]]
<br style="clear:both;">
* Application scenario
[[File:ZP-0181-9.jpg|left|800px]]
<br style="clear:both;">

===How to assemble it ?===
* Please follow the installation steps to assemble it.
[[File:ZP-0181-5.jpg|left|800px]]
<br style="clear:both;">
==Pacakge Includes==
* 1 x ABS Upper case for Raspberry Pi 5
* 1 x ABS Button case for Raspberry Pi 5
* 1 x Armor Lite V5 Adjustable speed Fan
* 6 x Thermal Pad
* 1 x Screw driver
* 2 x M2.5 Screw
* 4 x Self-tapping screw
[[File:ZP-0181-7.jpg|left|800px]]
<br style="clear:both;">
==Keywords==
* GAME 5Pi case, dural fan case for Raspberry Pi 5.

ZP-0181

2026-09-14T07:06:18Z

Yoyojacky: /* GAME 5Pi case */

==GAME 5 Pi case==
[[File:ZP-0181-1.jpg|right|320px]]

==Purchase URL==
* Official Web Store: [ https://52pi.com/collections/new-arrivals/products/game5-pi-case-enlosure-shell-for-raspberry-pi-5-with-armor-lite-v5-cooler ]

==Description==
The Game 5Pi Case is a stylish and functional enclosure designed for the Raspberry Pi, offering enhanced cooling capabilities and a retro aesthetic. This case integrates the Armor Lite V5 heatsink and fan for efficient thermal management, along with an additional side fan cooling system. Crafted from durable ABS material, the compact design includes a removable cover for the unused USB and Ethernet ports, providing extra protection when not in use.
==Features==
* <strong>Armor Lite V5 Heatsink and Fan:</strong>The case comes equipped with the Armor Lite V5 heatsink and fan, ensuring optimal thermal dissipation for the Raspberry Pi.

* <strong>Side Fan Cooling System:</strong> In addition to the main heatsink and fan, the case features a side fan cooling system to further enhance airflow and cooling efficiency.

* <strong>ABS Material:</strong> Constructed from high-quality ABS material, the case provides durability and a sleek appearance, contributing to a retro and eye-catching design.

* <strong>Compact and Retro Design: </strong>The compact form factor and retro design make the Game 5Pi Case visually appealing while maintaining a smaller footprint.

* <strong>Movable Cover: </strong>A movable cover is included to protect the unused USB and Ethernet ports, preserving the aesthetics of the case and preventing dust or debris accumulation.

* <strong>Easy Installation: </strong>The case is designed for easy and hassle-free installation, ensuring that users can set up their Raspberry Pi quickly and securely.

* <strong>Compatibility:</strong> The Game 5Pi Case is specifically designed for Raspberry Pi models, providing a snug fit and compatibility with various Raspberry Pi configurations.

* <strong>Ventilation and Airflow: </strong>Thoughtful ventilation and airflow design contribute to the efficient cooling of the Raspberry Pi, even during extended usage.

* <strong>Aesthetic Appeal: </strong>The combination of functional cooling elements and a retro design makes the Game 5Pi Case an aesthetically pleasing choice for Raspberry Pi enthusiasts.
==Gallery==
* Product outlook
[[File:ZP-0181-1.jpg|left|800px]]
<br style="clear:both;">
* Movable cover
[[File:ZP-0181-2.jpg|left|800px]]
<br style="clear:both;">
* Dimension
[[File:ZP-0181-3.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-4.jpg|left|800px]]
<br style="clear:both;">
* Features
[[File:ZP-0181-6.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-8.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-11.jpg|left|800px]]
<br style="clear:both;">
[[File:ZP-0181-10.jpg|left|800px]]
<br style="clear:both;">
* Application scenario
[[File:ZP-0181-9.jpg|left|800px]]
<br style="clear:both;">

===How to assemble it ?===
* Please follow the installation steps to assemble it.
[[File:ZP-0181-5.jpg|left|800px]]
<br style="clear:both;">
==Pacakge Includes==
* 1 x ABS Upper case for Raspberry Pi 5
* 1 x ABS Button case for Raspberry Pi 5
* 1 x Armor Lite V5 Adjustable speed Fan
* 6 x Thermal Pad
* 1 x Screw driver
* 2 x M2.5 Screw
* 4 x Self-tapping screw
[[File:ZP-0181-7.jpg|left|800px]]
<br style="clear:both;">
==Keywords==
* GAME 5Pi case, dural fan case for Raspberry Pi 5.

T-0033

2026-09-02T03:34:35Z

Yoyojacky: Created page with "==Raspberry Pi 5 PCIe to M.2 NVMe Board Installation Spacer Screw Set== * SKU: T-0033 320px ==Description== * The T-0033 is a mounting hardware kit designed for installing an M.2 NVMe expansion board on the Raspberry Pi 5 via the PCIe interface. It includes spacers and screws required for secure board attachment. ==Features== * Pi 5 PCIe to M.2 NVMe compatible — for M.2 NVMe board installation on Raspberry Pi 5 * Complete hardware set..."

==Raspberry Pi 5 PCIe to M.2 NVMe Board Installation Spacer Screw Set==
* SKU: T-0033
[[File:T-0033-01-01.jpg|right|320px]]
==Description==
* The T-0033 is a mounting hardware kit designed for installing an M.2 NVMe expansion board on the Raspberry Pi 5 via the PCIe interface. It includes spacers and screws required for secure board attachment.

==Features==
* Pi 5 PCIe to M.2 NVMe compatible — for M.2 NVMe board installation on Raspberry Pi 5
* Complete hardware set — includes spacers and screws
* Secure mounting — ensures stable and reliable board attachment
* Package dimensions — 127 × 71 × 30 mm
* Weight — 100 g

==Demonstration video==
* YouTube showcase: [[ https://www.youtube.com/watch?v=2ib8KYmMT9k ]]

==Gallery==
* Specifications & models & quantities
[[File:T-0033-02.jpg|left|800px]]
<br style="clear:both;">
* Size
[[File:T-0033-03.jpg|left|800px]]
<br style="clear:both;">

* Applicable PCIe expansion boards
[[File:T-0033-04.jpg|left|800px]]
<br style="clear:both;">

* Quality of Product (Copper material)
[[File:T-0033-05.jpg|left|800px]]
<br style="clear:both;">

* Delivery method
[[File:T-0033-7.jpg|left|800px]]
<br style="clear:both;">

* Application scenario
[[File:T-0033-06.jpg|left|800px]]
<br style="clear:both;">

[[File:T-0033-8.jpg|left|800px]]
<br style="clear:both;">

==Package List==
* 1 x Raspberry Pi 5 PCIe to M.2 NVMe Board Installation Spacer Screw Set
[[File:T-0033-01-01.jpg|left|800px]]
<br style="clear:both;">

File:T-0033-8.jpg

2026-09-02T03:33:00Z

Yoyojacky:

File:T-0033-7.jpg

2026-09-02T03:32:16Z

Yoyojacky:

File:T-0033-06.jpg

2026-09-02T03:31:33Z

Yoyojacky:

File:T-0033-05.jpg

2026-09-02T03:29:22Z

Yoyojacky:

File:T-0033-04.jpg

2026-09-02T03:28:23Z

Yoyojacky:

File:T-0033-03.jpg

2026-09-02T03:27:22Z

Yoyojacky:

File:T-0033-02.jpg

2026-09-02T03:26:22Z

Yoyojacky:

File:T-0033-01-01.jpg

2026-09-02T03:25:40Z

Yoyojacky:

Main Page

2026-09-02T03:20:28Z

Yoyojacky: /* T-Series (1 items) */

<div style="border:1px solid #a2a9b1; background:#f8f9fa; padding:12px; margin:0 0 16px 0;">
'''For AI assistants and automated tools:''' Please use the AI-friendly Markdown version of this documentation: [https://wiki-md.52pi.com/ https://wiki-md.52pi.com/]
</div>

='''RaspberryPi Modules'''=
The following contents include all of our products, Top10 modules are list here, those modules are fit for Raspberry Pi A，A+，B，B+，2 Model B，3 Model B and some other platform.
you can select one of them and click the links to get more information about it.
==HCL==
This is Hardware Compatible List. <font color=red>Depracated</font></br>
[[Hardware Compatible List]]

==UPS series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* UPS Gen 6 power module compatible with Raspberry Pi 5/4B: [[ EP-0245 ]] <font color=red>NEW!!</font><br>
* SBS module for UPS Gen 6 [[ EP-0256 ]] <font color=red>NEW!!</font><br>
* SATA Drive Power Board for UPS Gen 6: [[ EP-0252 ]] <font color=red>NEW!!</font><br>
* 1.3" LCD TFT Display Module for UPS Gen 6: [[ EP-0251 ]] <font color=red>NEW!!</font><br>
</td>
</tr>
</table>

==Rackmount Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* 1U 19-inch Removable Rack mount For RPi5/4B/3B+ [[ DR-0003 ]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DR-0002]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DP-0046]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 5: [[ DR-0001 ]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 4B: [[ EP-0143 ]]
* 19-inch 2U Rack Mount for Raspberry Pi [[DR-0005]]
</td>
</tr>
</table>

==Arduino Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
===Arduino UNO Q Series===
* Level-Shift Shield [[ EP-0257 ]] <font color=red>NEW</font><br>
* Arduino Nano ESP32 RGB LED Matrix Shield [[ EP-0263]] <font color=red>NEW</font><br>
* Terminal Expansion Base for Arduino NANO ESP32 [[ EP-0262 ]] <font color=red>NEW</font><br>

===Arduino UNO R4 Wi-Fi Series===
* [[ KZ-0054 ]]
* [[ KZ-0077 ]]
* [[ KZ-0086 ]]
</td>
</tr>
</table>

==52Pi N Series==
===Description===
The 52Pi N series is a line of storage products where "N" stands for NAS (Network Attached Storage), and the numerical designation represents various models and product types. Users can choose different types based on their specific needs to fulfill their usage requirements.
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">

==Product SKU==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* W03-New - [[ EP-0216-NEW ]] <font color=red>NEW</font><br>
* RS-P13 - [[ EP-0249 ]] <font color=red>NEW</font><br>
* S021 - [[ EP-0242 ]] <font color=red>NEW</font><br>
* N16 - [[ EP-0180 ]] <font color=red>NEW</font><br>
* P33 - [[ EP-0241 ]] <font color=red>NEW</font><br>
* P31 - [[ EP-0240 ]] <font color=red>NEW</font><br>
* P30 - [[ EP-0238 ]] <font color=red>NEW</font><br>
* CN01 - [[ EP-0236 ]] <font color=red>NEW</font><br>
* N06 - [[ EP-0239 ]] <font color=red>NEW</font><br>
* RS-P11 - [[ EP-0234 ]] <font color=red>NEW</font><br>
* B14 - [[ EP-0233 ]] <font color=red>NEW</font><br>
* N12 - [[ EP-0213 ]] <font color=red>NEW</font><br>
* U2500 - [[ EP-0235 ]] <font color=red>NEW</font><br>
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N21 - [[ EP-0231 ]] <font color=red>NEW</font><br>
* N20 - [[ EP-0227 ]] <font color=red>NEW</font><br>
* W01 - [[ EP-0228 ]] <font color=red>NEW</font><br>
* N10 - [[ EP-0229 ]] <font color=red>NEW</font><br>
* B12 - [[ EP-0230 ]] <font color=red>NEW</font><br>
* M01 - [[ EP-0223 ]] <font color=red>NEW</font><br>
* M02 - [[ EP-0217 ]] <font color=red>NEW</font><br>
* N05 - [[ EP-0209 ]] <font color=red>NEW</font><br>

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N04 - [[ EP-0210 ]] <font color=red>NEW</font><br>
* N07 - [[ EP-0211 ]] <font color=red>NEW</font><br>
* P02 - [[ EP-0219 ]] <font color=red>NEW</font><br>
* 52Pi NVDAC - [[ EP-0218 ]]
* 52Pi NVdigi - [[ EP-0220 ]]
* M.2 2242 NVME SSD for RPi 5 NES-CASE - [[ EP-0212 ]]
* W03 - [[ EP-0216 ]]
* Ice tower plus for RPi 5 - [[ EP-0224 ]]
</td></tr></table>
<br>

==Mini Tower Kit Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0187 ]] <font color=red>NEW</font>
* [[ ZP-0172 ]]
* [[ ZP-0128 ]]
* [[ ZP-0128-3B ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0128-4wire ]]
* [[ ZP-0129-4wire ]]
* [[ ZP-0130-4wire ]]
</td>

<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0129 ]]
* [[ ZP-0130 ]]
* [[ ZP-0132 ]]
</td>
</tr>
</table>

==Hat Stack==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0167 ]]
* [[ EP-0168 ]]
* [[ EP-0166 ]]
* [[ EP-0152 ]]
* [[ EP-0116 ]]
* [[ EP-0098 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0099 ]]
* [[ EP-0104 ]]
* [[ EP-0106 ]]
* [[ EP-0107 ]]
* [[ EP-0108 ]]
* [[ EP-0109 ]]
* [[ EP-0105 ]]
</td></tr></table>

==Starter Kit==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0067 ]]
* [[ KZ-0061 ]]
* [[ KZ-0016 ]]
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0020 ]]
* [[ KZ-0009 ]]
</td></tr></table>

==Development Boards==
===RP2040 Series===
* [[ EP-0174 ]]
===StarFive2===
* [[ ER-0043 ]]
* [[ ER-0044 ]]

===Micro:Bit===
* [[ KR-0004 ]]
* [[ KR-0027 ]]

===ROCK Pi Series===
* [[ EP-0265 ]]
* [[ KR-0001 ]]
* [[ KR-0012 ]]
* [[ ZP-0148 ]]

===Orange Pi Series===
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0156 ]]
* [[ ZP-0150 ]]
* [[ ZP-0149 ]]
* [[ F-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ F-0021 ]]
* [[ F-0022 ]]
* [[ KZ-0003 ]]
* [[ ER-0045 ]]
</td>
</tr>
</table>

===Raspberry Pi Pico Series===
* [[ KR-0006 ]]
* [[ EP-0175 ]]

==AI Learning==
* [[ EZ-0075 ]]
* [[ L-0031 ]]

==IoT Modules==
* [[ EP-0090 ]]
* [[ EZ-0061 ]]
* [[ EZ-0062 ]]
* [[ EZ-0063 ]]
----

==Tinker Board==
* [[ EZ-0066 ]]
* [[ EZ-0065 ]]

----
===DeskPi Series===
* [[ DP-0002 ]]
* [[ DP-0018 ]]

==KZ series==
* [[ KZ-0022 ]]
* [[ KZ-0056 ]]
* [[ KZ-0058 ]]
* [[ KZ-0060 ]]

==Raspberry Pi==
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0056 ]]
* [[ KR-0024 ]]
* [[ ER-0046 ]]
* [[ ER-0035 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0031 ]]
* [[ ER-0030 ]]
* [[ ER-0027 ]]
* [[ ER-0028 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0018 ]]
* [[ ER-0007 ]]
* [[ K-0231 ]]
* [[ K-0230 ]]
</td></tr></table>

----

===Raspberry Pi Pico & Pico W Breakout Board===
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0172 ]]
* [[ EP-0164 ]]
* [[ EP-0159 ]]
* [[ EP-0145 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0138 ]]
* [[ EP-0139 ]]
* [[ EP-0140 ]]
* [[ K-0582 ]]
* [[ K-0586 ]]
</tr></td></table>

==Banana Pi==
* [[ EB-0028 ]]
* [[ EB-0023 ]]
* [[ EB-0020 ]]
* [[ EP-0019 ]]
* [[ EB-0012 ]]
* [[ EB-0013 ]]

==Gaming Assesories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ D-0023 ]]
* [[ Z-0261 ]]
* [[ Z-0179 ]]
* [[ Z-0279 ]]
* [[ Z-0252 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ Z-0253 ]]
* [[ Z-0254 ]]
* [[ Z-0255 ]]
* [[ Z-0257 ]]
* [[ Z-0260 ]]
</td>
</tr></table>

==Electronic Accessories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0020 ]]
* [[ K-0580 ]]
* [[ ZP-0157 ]]
* [[ ZP-0158 ]]
</td>
</tr></table>

=Extension Modules=

==EP-Series (44 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0020 ]]
* [[ EP-0021 ]]
* [[ EP-0031 ]]
* [[ EP-0059 ]]
* [[ EP-0073 ]]
* [[ EP-0080 ]]
* [[ EP-0088 ]]
* [[ EP-0091 ]]
* [[ EP-0092 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0093 ]]
* [[ EP-0094 ]]
* [[ EP-0095 ]]
* [[ EP-0096 ]]
* [[ EP-0097 ]]
* [[ EP-0100 ]]
* [[ EP-0101 ]]
* [[ EP-0114 ]]
* [[ EP-0115 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0118 ]]
* [[ EP-0120 ]]
* [[ EP-0121 ]]
* [[ EP-0123 ]]
* [[ EP-0124 ]]
* [[ EP-0125 ]]
* [[ EP-0126 ]]
* [[ EP-0127 ]]
* [[ EP-0128 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0129 ]]
* [[ EP-0130 ]]
* [[ EP-0131 ]]
* [[ EP-0136 ]]
* [[ EP-0141 ]]
* [[ EP-0142 ]]
* [[ EP-0146 ]]
* [[ EP-0149 ]]
* [[ EP-0150 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0153 ]]
* [[ EP-0171 ]]
* [[ EP-0214 ]]
* [[ EP-0215 ]]
* [[ EP-0225 ]]
* [[ EP-0243 ]]
* [[ EP-0246 ]]
* [[ EP-0247 ]]
</td>
</tr>
</table>

==D-Series (16 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0001 ]]
* [[ D-0003 ]]
* [[ D-0005 ]]
* [[ D-0006 ]]
* [[ D-0007 ]]
* [[ D-0008 ]]
* [[ D-0009 ]]
* [[ D-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0011 ]]
* [[ D-0012 ]]
* [[ D-0013 ]]
* [[ D-0015 ]]
* [[ D-0016 ]]
* [[ D-0017 ]]
* [[ D-0018 ]]
* [[ D-0020 ]]
</td>
</tr>
</table>

==P-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0005 ]]
* [[ P-0006 ]]
* [[ P-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0011 ]]
* [[ P-0021 ]]
* [[ P-0024 ]]
</td>
</tr>
</table>

==Z-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0177 ]]
* [[ Z-0209 ]]
* [[ Z-0231 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0234 ]]
* [[ Z-0235 ]]
* [[ Z-0269 ]]
</td>
</tr>
</table>

==EZ-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0024 ]]
* [[ EZ-0048 ]]
* [[ EZ-0068 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0089 ]]
* [[ EZ-0106 ]]
</td>
</tr>
</table>

==ER-Series (4 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0014 ]]
* [[ ER-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0021 ]]
* [[ ER-0022 ]]
</td>
</tr>
</table>

==K-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0291 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0335 ]]
</td>
</tr>
</table>

==G-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ G-0002 ]]
</td>
</tr>
</table>

=Case & Enclosure & Heat sink=

==ZP-Series (78 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0024 ]]
* [[ ZP-0025 ]]
* [[ ZP-0029 ]]
* [[ ZP-0037 ]]
* [[ ZP-0038 ]]
* [[ ZP-0039 ]]
* [[ ZP-0040 ]]
* [[ ZP-0042 ]]
* [[ ZP-0049 ]]
* [[ ZP-0051 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0065 ]]
* [[ ZP-0066 ]]
* [[ ZP-0067 ]]
* [[ ZP-0068 ]]
* [[ ZP-0069 ]]
* [[ ZP-0070 ]]
* [[ ZP-0071 ]]
* [[ ZP-0072 ]]
* [[ ZP-0073 ]]
* [[ ZP-0074 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0075 ]]
* [[ ZP-0076 ]]
* [[ ZP-0077 ]]
* [[ ZP-0078 ]]
* [[ ZP-0079 ]]
* [[ ZP-0080 ]]
* [[ ZP-0081 ]]
* [[ ZP-0082 ]]
* [[ ZP-0083 ]]
* [[ ZP-0085 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0086 ]]
* [[ ZP-0087 ]]
* [[ ZP-0088 ]]
* [[ ZP-0089 ]]
* [[ ZP-0090 ]]
* [[ ZP-0091 ]]
* [[ ZP-0092 ]]
* [[ ZP-0093 ]]
* [[ ZP-0098 ]]
* [[ ZP-0099 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0100 ]]
* [[ ZP-0101 ]]
* [[ ZP-0102 ]]
* [[ ZP-0103 ]]
* [[ ZP-0105 ]]
* [[ ZP-0108 ]]
* [[ ZP-0110 ]]
* [[ ZP-0111 ]]
* [[ ZP-0112 ]]
* [[ ZP-0113 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0115 ]]
* [[ ZP-0116 ]]
* [[ ZP-0120 ]]
* [[ ZP-0133 ]]
* [[ ZP-0138 ]]
* [[ ZP-0139 ]]
* [[ ZP-0140 ]]
* [[ ZP-0141 ]]
* [[ ZP-0147 ]]
* [[ ZP-0153 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0162 ]]
* [[ ZP-0163 ]]
* [[ ZP-0164 ]]
* [[ ZP-0165 ]]
* [[ ZP-0166 ]]
* [[ ZP-0167 ]]
* [[ ZP-0168 ]]
* [[ ZP-0170 ]]
* [[ ZP-0173 ]]
* [[ ZP-0175 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0180 ]]
* [[ ZP-0181 ]]
* [[ ZP-0186 ]]
* [[ ZP-0188 ]]
* [[ ZP-0213 ]]
* [[ ZP-0215 ]]
* [[ ZP-0216 ]]
* [[ ZP-0222 ]]
</td>
</tr>
</table>

==C-Series (26 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0001 ]]
* [[ C-0002 ]]
* [[ C-0003 ]]
* [[ C-0004 ]]
* [[ C-0005 ]]
* [[ C-0006 ]]
* [[ C-0007 ]]
* [[ C-0008 ]]
* [[ C-0015 ]]
* [[ C-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0022 ]]
* [[ C-0023 ]]
* [[ C-0025 ]]
* [[ C-0027 ]]
* [[ C-0028 ]]
* [[ C-0031 ]]
* [[ C-0032 ]]
* [[ C-0033 ]]
* [[ C-0034 ]]
* [[ C-0047 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0048 ]]
* [[ C-0049 ]]
* [[ C-0050 ]]
* [[ C-0052 ]]
* [[ C-0054 ]]
* [[ C-0063 ]]
</td>
</tr>
</table>

==EP-Series (12 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0076 ]]
* [[ EP-0077 ]]
* [[ EP-0078 ]]
* [[ EP-0079 ]]
* [[ EP-0111 ]]
* [[ EP-0112 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0113 ]]
* [[ EP-0122 ]]
* [[ EP-0132 ]]
* [[ EP-0163 ]]
* [[ EP-0222 ]]
* [[ EP-0226 ]]
</td>
</tr>
</table>

==Z-Series (15 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0127 ]]
* [[ Z-0153 ]]
* [[ Z-0157 ]]
* [[ Z-0183 ]]
* [[ Z-0184 ]]
* [[ Z-0185 ]]
* [[ Z-0190 ]]
* [[ Z-0193 ]]
* [[ Z-0208 ]]
* [[ Z-0237 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0264 ]]
* [[ Z-0266 ]]
* [[ Z-0272 ]]
* [[ Z-0273 ]]
* [[ Z-0278 ]]
</td>
</tr>
</table>

==K-Series (10 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ K-0172 ]]
* [[ K-0178 ]]
* [[ K-0567 ]]
* [[ K-0583 ]]
* [[ K-0585 ]]
* [[ K-0589 ]]
* [[ K-0592 ]]
* [[ K-0595 ]]
* [[ K-0612 ]]
* [[ K-0638 ]]
</td>
</tr>
</table>

==KZ-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ KZ-0001 ]]
* [[ KZ-0002 ]]
* [[ KZ-0063 ]]
</td>
</tr>
</table>

==ER-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ ER-0011 ]]
</td>
</tr>
</table>

==EZ-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ EZ-0059 ]]
</td>
</tr>
</table>

==F-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ F-0003 ]]
</td>
</tr>
</table>

==L-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ L-0030 ]]
</td>
</tr>
</table>

=Cooling Accessories=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0001 ]]
* [[ F-0002 ]]
* [[ F-0006 ]]
* [[ F-0005 ]]
* [[ F-0007 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0010 ]]
* [[ F-0011 ]]
* [[ F-0012 ]]
* [[ D-0022 ]]
* [[ F-0008 ]]
* [[ F-0008-RGB ]]
</td>
</tr></table>

==Electronic Engineer Tools==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0022 ]]
* [[ T-0021 ]]
* [[ T-0019 ]]
* [[ T-0015 ]]
* [[ T-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0017 ]]
* [[ T-0018 ]]
* [[ Z-0241 ]]
</td></tr></table>

=Displays=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>

==EP-Series (27 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0045 ]]
* [[ EP-0058 ]]
* [[ EP-0062 ]]
* [[ EP-0063 ]]
* [[ EP-0065 ]]
* [[ EP-0066 ]]
* [[ EP-0072 ]]
* [[ EP-0075 ]]
* [[ EP-0081 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0082 ]]
* [[ EP-0084 ]]
* [[ EP-0085 ]]
* [[ EP-0087 ]]
* [[ EP-0089 ]]
* [[ EP-0119 ]]
* [[ EP-0133 ]]
* [[ EP-0148 ]]
* [[ EP-0170 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0177 ]]
* [[ EP-0183 ]]
* [[ EP-0184 ]]
* [[ EP-0185 ]]
* [[ EP-0186 ]]
* [[ EP-0187 ]] <font color=red>NEW!!!</font>
* [[ EP-0188 ]]
* [[ EP-0189 ]] <font color=red>NEW!!!</font>
* [[ EP-0190 ]]
</td>
</tr>
</table>

==Z-Series (8 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0017 ]]
* [[ Z-0051 ]]
* [[ Z-0053 ]]
* [[ Z-0111 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0112 ]]
* [[ Z-0113 ]]
* [[ Z-0114 ]]
* [[ Z-0143 ]]
</td>
</tr>
</table>

==S-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0001 ]]
* [[ S-0003 ]]
* [[ S-0005 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0006 ]]
* [[ S-0007 ]]
* [[ S-0018 ]]
</td>
</tr>
</table>

==K-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0101 ]]
* [[ K-0102 ]]
* [[ K-0103 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0104 ]]
* [[ K-0106 ]]
</td>
</tr>

=Power Supply=

==P-Series (9 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0001 ]]
* [[ P-0007 ]]
* [[ P-0008 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0009 ]]
* [[ P-0017 ]]
* [[ P-0031 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0032 ]]
* [[ P-0040 ]]
* [[ P-0044 ]]
</td>
</tr>
</table>

==Z-Series (11 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0097 ]]
* [[ Z-0121 ]]
* [[ Z-0132 ]]
* [[ Z-0133 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0136 ]]
* [[ Z-0147 ]]
* [[ Z-0148 ]]
* [[ Z-0149 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0150 ]]
* [[ Z-0154 ]]
* [[ Z-0155 ]]
</td>
</tr>
</table>

==L-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0026 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0027 ]]
</td>
</tr>
</table>

==Raspberry Pi Kits==

==K-Series (18 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0111 ]]
* [[ K-0167 ]]
* [[ K-0168 ]]
* [[ K-0169 ]]
* [[ K-0171 ]]
* [[ K-0174 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0180 ]]
* [[ K-0185 ]]
* [[ K-0186 ]]
* [[ K-0238 ]]
* [[ K-0259 ]]
* [[ K-0401 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0403 ]]
* [[ K-0502 ]]
* [[ K-0503 ]]
* [[ K-0512 ]]
* [[ K-0522 ]]
* [[ K-0581 ]]
</td>
</tr>
</table>

==Z-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0142 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0144 ]]
</td>
</tr>
</table>

==T-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ T-0008 ]]
* [[ T-0033 ]]
</td>
</tr>
</table>

KZ-0063

2026-09-02T03:14:15Z

Yoyojacky: Created page with "== Raspberry Pi 5 PCIe FFC Cable Set== * SKU: KZ-0063 320px == Description== The KZ-0063 is a flexible flat cable (FFC) set designed for the Raspberry Pi 5 PCIe interface. It includes three commonly used cable lengths plus M.2 mounting hardware for SSD installation. ==Features== * Pi 5 PCIe compatible — optimized for Raspberry Pi 5 PCIe connectivity * Three FFC lengths — 40 mm, 60 mm, and 80 mm cables in one set * M.2 mounting kit inclu..."

== Raspberry Pi 5 PCIe FFC Cable Set==
* SKU: KZ-0063
[[File:KZ-0063-01.jpg|right|320px]]
== Description==
The KZ-0063 is a flexible flat cable (FFC) set designed for the Raspberry Pi 5 PCIe interface. It includes three commonly used cable lengths plus M.2 mounting hardware for SSD installation.

==Features==
* Pi 5 PCIe compatible — optimized for Raspberry Pi 5 PCIe connectivity
* Three FFC lengths — 40 mm, 60 mm, and 80 mm cables in one set
* M.2 mounting kit included — M2 screws and standoffs for SSD installation
* Flexible flat design — reliable signal transmission in tight spaces
* Plug-and-play — no additional drivers or tools required
* Package dimensions — 105 × 80 × 28 mm
* Weight — 15 g

==Gallery==
* Product outlook
[[File:KZ-0063-01.jpg|left|800px]]
<br style="clear:both;">

* Product size
[[File:KZ-0063-02.jpg|left|800px]]
<br style="clear:both;">

* Product compatibility with N-Series Board
[[File:KZ-0063-04.jpg|left|800px]]
<br style="clear:both;">

* Application Scenario
[[File:KZ-0063-05.jpg|left|800px]]
<br style="clear:both;">

==Package List==
[[File:KZ-0063-03.jpg|left|800px]]
<br style="clear:both;">

File:KZ-0063-05.jpg

2026-09-02T03:13:21Z

Yoyojacky:

File:KZ-0063-04.jpg

2026-09-02T03:12:17Z

Yoyojacky:

File:KZ-0063-03.jpg

2026-09-02T03:11:28Z

Yoyojacky:

File:KZ-0063-02.jpg

2026-09-02T03:10:46Z

Yoyojacky:

File:KZ-0063-01.jpg

2026-09-02T03:08:18Z

Yoyojacky:

Main Page

2026-09-02T03:04:26Z

Yoyojacky: /* KZ-Series (2 items) */

<div style="border:1px solid #a2a9b1; background:#f8f9fa; padding:12px; margin:0 0 16px 0;">
'''For AI assistants and automated tools:''' Please use the AI-friendly Markdown version of this documentation: [https://wiki-md.52pi.com/ https://wiki-md.52pi.com/]
</div>

='''RaspberryPi Modules'''=
The following contents include all of our products, Top10 modules are list here, those modules are fit for Raspberry Pi A，A+，B，B+，2 Model B，3 Model B and some other platform.
you can select one of them and click the links to get more information about it.
==HCL==
This is Hardware Compatible List. <font color=red>Depracated</font></br>
[[Hardware Compatible List]]

==UPS series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* UPS Gen 6 power module compatible with Raspberry Pi 5/4B: [[ EP-0245 ]] <font color=red>NEW!!</font><br>
* SBS module for UPS Gen 6 [[ EP-0256 ]] <font color=red>NEW!!</font><br>
* SATA Drive Power Board for UPS Gen 6: [[ EP-0252 ]] <font color=red>NEW!!</font><br>
* 1.3" LCD TFT Display Module for UPS Gen 6: [[ EP-0251 ]] <font color=red>NEW!!</font><br>
</td>
</tr>
</table>

==Rackmount Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* 1U 19-inch Removable Rack mount For RPi5/4B/3B+ [[ DR-0003 ]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DR-0002]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DP-0046]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 5: [[ DR-0001 ]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 4B: [[ EP-0143 ]]
* 19-inch 2U Rack Mount for Raspberry Pi [[DR-0005]]
</td>
</tr>
</table>

==Arduino Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
===Arduino UNO Q Series===
* Level-Shift Shield [[ EP-0257 ]] <font color=red>NEW</font><br>
* Arduino Nano ESP32 RGB LED Matrix Shield [[ EP-0263]] <font color=red>NEW</font><br>
* Terminal Expansion Base for Arduino NANO ESP32 [[ EP-0262 ]] <font color=red>NEW</font><br>

===Arduino UNO R4 Wi-Fi Series===
* [[ KZ-0054 ]]
* [[ KZ-0077 ]]
* [[ KZ-0086 ]]
</td>
</tr>
</table>

==52Pi N Series==
===Description===
The 52Pi N series is a line of storage products where "N" stands for NAS (Network Attached Storage), and the numerical designation represents various models and product types. Users can choose different types based on their specific needs to fulfill their usage requirements.
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">

==Product SKU==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* W03-New - [[ EP-0216-NEW ]] <font color=red>NEW</font><br>
* RS-P13 - [[ EP-0249 ]] <font color=red>NEW</font><br>
* S021 - [[ EP-0242 ]] <font color=red>NEW</font><br>
* N16 - [[ EP-0180 ]] <font color=red>NEW</font><br>
* P33 - [[ EP-0241 ]] <font color=red>NEW</font><br>
* P31 - [[ EP-0240 ]] <font color=red>NEW</font><br>
* P30 - [[ EP-0238 ]] <font color=red>NEW</font><br>
* CN01 - [[ EP-0236 ]] <font color=red>NEW</font><br>
* N06 - [[ EP-0239 ]] <font color=red>NEW</font><br>
* RS-P11 - [[ EP-0234 ]] <font color=red>NEW</font><br>
* B14 - [[ EP-0233 ]] <font color=red>NEW</font><br>
* N12 - [[ EP-0213 ]] <font color=red>NEW</font><br>
* U2500 - [[ EP-0235 ]] <font color=red>NEW</font><br>
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N21 - [[ EP-0231 ]] <font color=red>NEW</font><br>
* N20 - [[ EP-0227 ]] <font color=red>NEW</font><br>
* W01 - [[ EP-0228 ]] <font color=red>NEW</font><br>
* N10 - [[ EP-0229 ]] <font color=red>NEW</font><br>
* B12 - [[ EP-0230 ]] <font color=red>NEW</font><br>
* M01 - [[ EP-0223 ]] <font color=red>NEW</font><br>
* M02 - [[ EP-0217 ]] <font color=red>NEW</font><br>
* N05 - [[ EP-0209 ]] <font color=red>NEW</font><br>

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N04 - [[ EP-0210 ]] <font color=red>NEW</font><br>
* N07 - [[ EP-0211 ]] <font color=red>NEW</font><br>
* P02 - [[ EP-0219 ]] <font color=red>NEW</font><br>
* 52Pi NVDAC - [[ EP-0218 ]]
* 52Pi NVdigi - [[ EP-0220 ]]
* M.2 2242 NVME SSD for RPi 5 NES-CASE - [[ EP-0212 ]]
* W03 - [[ EP-0216 ]]
* Ice tower plus for RPi 5 - [[ EP-0224 ]]
</td></tr></table>
<br>

==Mini Tower Kit Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0187 ]] <font color=red>NEW</font>
* [[ ZP-0172 ]]
* [[ ZP-0128 ]]
* [[ ZP-0128-3B ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0128-4wire ]]
* [[ ZP-0129-4wire ]]
* [[ ZP-0130-4wire ]]
</td>

<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0129 ]]
* [[ ZP-0130 ]]
* [[ ZP-0132 ]]
</td>
</tr>
</table>

==Hat Stack==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0167 ]]
* [[ EP-0168 ]]
* [[ EP-0166 ]]
* [[ EP-0152 ]]
* [[ EP-0116 ]]
* [[ EP-0098 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0099 ]]
* [[ EP-0104 ]]
* [[ EP-0106 ]]
* [[ EP-0107 ]]
* [[ EP-0108 ]]
* [[ EP-0109 ]]
* [[ EP-0105 ]]
</td></tr></table>

==Starter Kit==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0067 ]]
* [[ KZ-0061 ]]
* [[ KZ-0016 ]]
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0020 ]]
* [[ KZ-0009 ]]
</td></tr></table>

==Development Boards==
===RP2040 Series===
* [[ EP-0174 ]]
===StarFive2===
* [[ ER-0043 ]]
* [[ ER-0044 ]]

===Micro:Bit===
* [[ KR-0004 ]]
* [[ KR-0027 ]]

===ROCK Pi Series===
* [[ EP-0265 ]]
* [[ KR-0001 ]]
* [[ KR-0012 ]]
* [[ ZP-0148 ]]

===Orange Pi Series===
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0156 ]]
* [[ ZP-0150 ]]
* [[ ZP-0149 ]]
* [[ F-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ F-0021 ]]
* [[ F-0022 ]]
* [[ KZ-0003 ]]
* [[ ER-0045 ]]
</td>
</tr>
</table>

===Raspberry Pi Pico Series===
* [[ KR-0006 ]]
* [[ EP-0175 ]]

==AI Learning==
* [[ EZ-0075 ]]
* [[ L-0031 ]]

==IoT Modules==
* [[ EP-0090 ]]
* [[ EZ-0061 ]]
* [[ EZ-0062 ]]
* [[ EZ-0063 ]]
----

==Tinker Board==
* [[ EZ-0066 ]]
* [[ EZ-0065 ]]

----
===DeskPi Series===
* [[ DP-0002 ]]
* [[ DP-0018 ]]

==KZ series==
* [[ KZ-0022 ]]
* [[ KZ-0056 ]]
* [[ KZ-0058 ]]
* [[ KZ-0060 ]]

==Raspberry Pi==
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0056 ]]
* [[ KR-0024 ]]
* [[ ER-0046 ]]
* [[ ER-0035 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0031 ]]
* [[ ER-0030 ]]
* [[ ER-0027 ]]
* [[ ER-0028 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0018 ]]
* [[ ER-0007 ]]
* [[ K-0231 ]]
* [[ K-0230 ]]
</td></tr></table>

----

===Raspberry Pi Pico & Pico W Breakout Board===
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0172 ]]
* [[ EP-0164 ]]
* [[ EP-0159 ]]
* [[ EP-0145 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0138 ]]
* [[ EP-0139 ]]
* [[ EP-0140 ]]
* [[ K-0582 ]]
* [[ K-0586 ]]
</tr></td></table>

==Banana Pi==
* [[ EB-0028 ]]
* [[ EB-0023 ]]
* [[ EB-0020 ]]
* [[ EP-0019 ]]
* [[ EB-0012 ]]
* [[ EB-0013 ]]

==Gaming Assesories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ D-0023 ]]
* [[ Z-0261 ]]
* [[ Z-0179 ]]
* [[ Z-0279 ]]
* [[ Z-0252 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ Z-0253 ]]
* [[ Z-0254 ]]
* [[ Z-0255 ]]
* [[ Z-0257 ]]
* [[ Z-0260 ]]
</td>
</tr></table>

==Electronic Accessories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0020 ]]
* [[ K-0580 ]]
* [[ ZP-0157 ]]
* [[ ZP-0158 ]]
</td>
</tr></table>

=Extension Modules=

==EP-Series (44 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0020 ]]
* [[ EP-0021 ]]
* [[ EP-0031 ]]
* [[ EP-0059 ]]
* [[ EP-0073 ]]
* [[ EP-0080 ]]
* [[ EP-0088 ]]
* [[ EP-0091 ]]
* [[ EP-0092 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0093 ]]
* [[ EP-0094 ]]
* [[ EP-0095 ]]
* [[ EP-0096 ]]
* [[ EP-0097 ]]
* [[ EP-0100 ]]
* [[ EP-0101 ]]
* [[ EP-0114 ]]
* [[ EP-0115 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0118 ]]
* [[ EP-0120 ]]
* [[ EP-0121 ]]
* [[ EP-0123 ]]
* [[ EP-0124 ]]
* [[ EP-0125 ]]
* [[ EP-0126 ]]
* [[ EP-0127 ]]
* [[ EP-0128 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0129 ]]
* [[ EP-0130 ]]
* [[ EP-0131 ]]
* [[ EP-0136 ]]
* [[ EP-0141 ]]
* [[ EP-0142 ]]
* [[ EP-0146 ]]
* [[ EP-0149 ]]
* [[ EP-0150 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0153 ]]
* [[ EP-0171 ]]
* [[ EP-0214 ]]
* [[ EP-0215 ]]
* [[ EP-0225 ]]
* [[ EP-0243 ]]
* [[ EP-0246 ]]
* [[ EP-0247 ]]
</td>
</tr>
</table>

==D-Series (16 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0001 ]]
* [[ D-0003 ]]
* [[ D-0005 ]]
* [[ D-0006 ]]
* [[ D-0007 ]]
* [[ D-0008 ]]
* [[ D-0009 ]]
* [[ D-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0011 ]]
* [[ D-0012 ]]
* [[ D-0013 ]]
* [[ D-0015 ]]
* [[ D-0016 ]]
* [[ D-0017 ]]
* [[ D-0018 ]]
* [[ D-0020 ]]
</td>
</tr>
</table>

==P-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0005 ]]
* [[ P-0006 ]]
* [[ P-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0011 ]]
* [[ P-0021 ]]
* [[ P-0024 ]]
</td>
</tr>
</table>

==Z-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0177 ]]
* [[ Z-0209 ]]
* [[ Z-0231 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0234 ]]
* [[ Z-0235 ]]
* [[ Z-0269 ]]
</td>
</tr>
</table>

==EZ-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0024 ]]
* [[ EZ-0048 ]]
* [[ EZ-0068 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0089 ]]
* [[ EZ-0106 ]]
</td>
</tr>
</table>

==ER-Series (4 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0014 ]]
* [[ ER-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0021 ]]
* [[ ER-0022 ]]
</td>
</tr>
</table>

==K-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0291 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0335 ]]
</td>
</tr>
</table>

==G-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ G-0002 ]]
</td>
</tr>
</table>

=Case & Enclosure & Heat sink=

==ZP-Series (78 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0024 ]]
* [[ ZP-0025 ]]
* [[ ZP-0029 ]]
* [[ ZP-0037 ]]
* [[ ZP-0038 ]]
* [[ ZP-0039 ]]
* [[ ZP-0040 ]]
* [[ ZP-0042 ]]
* [[ ZP-0049 ]]
* [[ ZP-0051 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0065 ]]
* [[ ZP-0066 ]]
* [[ ZP-0067 ]]
* [[ ZP-0068 ]]
* [[ ZP-0069 ]]
* [[ ZP-0070 ]]
* [[ ZP-0071 ]]
* [[ ZP-0072 ]]
* [[ ZP-0073 ]]
* [[ ZP-0074 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0075 ]]
* [[ ZP-0076 ]]
* [[ ZP-0077 ]]
* [[ ZP-0078 ]]
* [[ ZP-0079 ]]
* [[ ZP-0080 ]]
* [[ ZP-0081 ]]
* [[ ZP-0082 ]]
* [[ ZP-0083 ]]
* [[ ZP-0085 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0086 ]]
* [[ ZP-0087 ]]
* [[ ZP-0088 ]]
* [[ ZP-0089 ]]
* [[ ZP-0090 ]]
* [[ ZP-0091 ]]
* [[ ZP-0092 ]]
* [[ ZP-0093 ]]
* [[ ZP-0098 ]]
* [[ ZP-0099 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0100 ]]
* [[ ZP-0101 ]]
* [[ ZP-0102 ]]
* [[ ZP-0103 ]]
* [[ ZP-0105 ]]
* [[ ZP-0108 ]]
* [[ ZP-0110 ]]
* [[ ZP-0111 ]]
* [[ ZP-0112 ]]
* [[ ZP-0113 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0115 ]]
* [[ ZP-0116 ]]
* [[ ZP-0120 ]]
* [[ ZP-0133 ]]
* [[ ZP-0138 ]]
* [[ ZP-0139 ]]
* [[ ZP-0140 ]]
* [[ ZP-0141 ]]
* [[ ZP-0147 ]]
* [[ ZP-0153 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0162 ]]
* [[ ZP-0163 ]]
* [[ ZP-0164 ]]
* [[ ZP-0165 ]]
* [[ ZP-0166 ]]
* [[ ZP-0167 ]]
* [[ ZP-0168 ]]
* [[ ZP-0170 ]]
* [[ ZP-0173 ]]
* [[ ZP-0175 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0180 ]]
* [[ ZP-0181 ]]
* [[ ZP-0186 ]]
* [[ ZP-0188 ]]
* [[ ZP-0213 ]]
* [[ ZP-0215 ]]
* [[ ZP-0216 ]]
* [[ ZP-0222 ]]
</td>
</tr>
</table>

==C-Series (26 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0001 ]]
* [[ C-0002 ]]
* [[ C-0003 ]]
* [[ C-0004 ]]
* [[ C-0005 ]]
* [[ C-0006 ]]
* [[ C-0007 ]]
* [[ C-0008 ]]
* [[ C-0015 ]]
* [[ C-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0022 ]]
* [[ C-0023 ]]
* [[ C-0025 ]]
* [[ C-0027 ]]
* [[ C-0028 ]]
* [[ C-0031 ]]
* [[ C-0032 ]]
* [[ C-0033 ]]
* [[ C-0034 ]]
* [[ C-0047 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0048 ]]
* [[ C-0049 ]]
* [[ C-0050 ]]
* [[ C-0052 ]]
* [[ C-0054 ]]
* [[ C-0063 ]]
</td>
</tr>
</table>

==EP-Series (12 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0076 ]]
* [[ EP-0077 ]]
* [[ EP-0078 ]]
* [[ EP-0079 ]]
* [[ EP-0111 ]]
* [[ EP-0112 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0113 ]]
* [[ EP-0122 ]]
* [[ EP-0132 ]]
* [[ EP-0163 ]]
* [[ EP-0222 ]]
* [[ EP-0226 ]]
</td>
</tr>
</table>

==Z-Series (15 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0127 ]]
* [[ Z-0153 ]]
* [[ Z-0157 ]]
* [[ Z-0183 ]]
* [[ Z-0184 ]]
* [[ Z-0185 ]]
* [[ Z-0190 ]]
* [[ Z-0193 ]]
* [[ Z-0208 ]]
* [[ Z-0237 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0264 ]]
* [[ Z-0266 ]]
* [[ Z-0272 ]]
* [[ Z-0273 ]]
* [[ Z-0278 ]]
</td>
</tr>
</table>

==K-Series (10 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ K-0172 ]]
* [[ K-0178 ]]
* [[ K-0567 ]]
* [[ K-0583 ]]
* [[ K-0585 ]]
* [[ K-0589 ]]
* [[ K-0592 ]]
* [[ K-0595 ]]
* [[ K-0612 ]]
* [[ K-0638 ]]
</td>
</tr>
</table>

==KZ-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ KZ-0001 ]]
* [[ KZ-0002 ]]
* [[ KZ-0063 ]]
</td>
</tr>
</table>

==ER-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ ER-0011 ]]
</td>
</tr>
</table>

==EZ-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ EZ-0059 ]]
</td>
</tr>
</table>

==F-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ F-0003 ]]
</td>
</tr>
</table>

==L-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ L-0030 ]]
</td>
</tr>
</table>

=Cooling Accessories=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0001 ]]
* [[ F-0002 ]]
* [[ F-0006 ]]
* [[ F-0005 ]]
* [[ F-0007 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0010 ]]
* [[ F-0011 ]]
* [[ F-0012 ]]
* [[ D-0022 ]]
* [[ F-0008 ]]
* [[ F-0008-RGB ]]
</td>
</tr></table>

==Electronic Engineer Tools==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0022 ]]
* [[ T-0021 ]]
* [[ T-0019 ]]
* [[ T-0015 ]]
* [[ T-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0017 ]]
* [[ T-0018 ]]
* [[ Z-0241 ]]
</td></tr></table>

=Displays=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>

==EP-Series (27 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0045 ]]
* [[ EP-0058 ]]
* [[ EP-0062 ]]
* [[ EP-0063 ]]
* [[ EP-0065 ]]
* [[ EP-0066 ]]
* [[ EP-0072 ]]
* [[ EP-0075 ]]
* [[ EP-0081 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0082 ]]
* [[ EP-0084 ]]
* [[ EP-0085 ]]
* [[ EP-0087 ]]
* [[ EP-0089 ]]
* [[ EP-0119 ]]
* [[ EP-0133 ]]
* [[ EP-0148 ]]
* [[ EP-0170 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0177 ]]
* [[ EP-0183 ]]
* [[ EP-0184 ]]
* [[ EP-0185 ]]
* [[ EP-0186 ]]
* [[ EP-0187 ]] <font color=red>NEW!!!</font>
* [[ EP-0188 ]]
* [[ EP-0189 ]] <font color=red>NEW!!!</font>
* [[ EP-0190 ]]
</td>
</tr>
</table>

==Z-Series (8 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0017 ]]
* [[ Z-0051 ]]
* [[ Z-0053 ]]
* [[ Z-0111 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0112 ]]
* [[ Z-0113 ]]
* [[ Z-0114 ]]
* [[ Z-0143 ]]
</td>
</tr>
</table>

==S-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0001 ]]
* [[ S-0003 ]]
* [[ S-0005 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0006 ]]
* [[ S-0007 ]]
* [[ S-0018 ]]
</td>
</tr>
</table>

==K-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0101 ]]
* [[ K-0102 ]]
* [[ K-0103 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0104 ]]
* [[ K-0106 ]]
</td>
</tr>

=Power Supply=

==P-Series (9 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0001 ]]
* [[ P-0007 ]]
* [[ P-0008 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0009 ]]
* [[ P-0017 ]]
* [[ P-0031 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0032 ]]
* [[ P-0040 ]]
* [[ P-0044 ]]
</td>
</tr>
</table>

==Z-Series (11 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0097 ]]
* [[ Z-0121 ]]
* [[ Z-0132 ]]
* [[ Z-0133 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0136 ]]
* [[ Z-0147 ]]
* [[ Z-0148 ]]
* [[ Z-0149 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0150 ]]
* [[ Z-0154 ]]
* [[ Z-0155 ]]
</td>
</tr>
</table>

==L-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0026 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0027 ]]
</td>
</tr>
</table>

==Raspberry Pi Kits==

==K-Series (18 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0111 ]]
* [[ K-0167 ]]
* [[ K-0168 ]]
* [[ K-0169 ]]
* [[ K-0171 ]]
* [[ K-0174 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0180 ]]
* [[ K-0185 ]]
* [[ K-0186 ]]
* [[ K-0238 ]]
* [[ K-0259 ]]
* [[ K-0401 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0403 ]]
* [[ K-0502 ]]
* [[ K-0503 ]]
* [[ K-0512 ]]
* [[ K-0522 ]]
* [[ K-0581 ]]
</td>
</tr>
</table>

==Z-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0142 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0144 ]]
</td>
</tr>
</table>

==T-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ T-0008 ]]
</td>
</tr>
</table>

Main Page

2026-09-02T03:04:14Z

Yoyojacky: /* KZ-Series (2 items) */

<div style="border:1px solid #a2a9b1; background:#f8f9fa; padding:12px; margin:0 0 16px 0;">
'''For AI assistants and automated tools:''' Please use the AI-friendly Markdown version of this documentation: [https://wiki-md.52pi.com/ https://wiki-md.52pi.com/]
</div>

='''RaspberryPi Modules'''=
The following contents include all of our products, Top10 modules are list here, those modules are fit for Raspberry Pi A，A+，B，B+，2 Model B，3 Model B and some other platform.
you can select one of them and click the links to get more information about it.
==HCL==
This is Hardware Compatible List. <font color=red>Depracated</font></br>
[[Hardware Compatible List]]

==UPS series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* UPS Gen 6 power module compatible with Raspberry Pi 5/4B: [[ EP-0245 ]] <font color=red>NEW!!</font><br>
* SBS module for UPS Gen 6 [[ EP-0256 ]] <font color=red>NEW!!</font><br>
* SATA Drive Power Board for UPS Gen 6: [[ EP-0252 ]] <font color=red>NEW!!</font><br>
* 1.3" LCD TFT Display Module for UPS Gen 6: [[ EP-0251 ]] <font color=red>NEW!!</font><br>
</td>
</tr>
</table>

==Rackmount Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* 1U 19-inch Removable Rack mount For RPi5/4B/3B+ [[ DR-0003 ]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DR-0002]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DP-0046]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 5: [[ DR-0001 ]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 4B: [[ EP-0143 ]]
* 19-inch 2U Rack Mount for Raspberry Pi [[DR-0005]]
</td>
</tr>
</table>

==Arduino Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
===Arduino UNO Q Series===
* Level-Shift Shield [[ EP-0257 ]] <font color=red>NEW</font><br>
* Arduino Nano ESP32 RGB LED Matrix Shield [[ EP-0263]] <font color=red>NEW</font><br>
* Terminal Expansion Base for Arduino NANO ESP32 [[ EP-0262 ]] <font color=red>NEW</font><br>

===Arduino UNO R4 Wi-Fi Series===
* [[ KZ-0054 ]]
* [[ KZ-0077 ]]
* [[ KZ-0086 ]]
</td>
</tr>
</table>

==52Pi N Series==
===Description===
The 52Pi N series is a line of storage products where "N" stands for NAS (Network Attached Storage), and the numerical designation represents various models and product types. Users can choose different types based on their specific needs to fulfill their usage requirements.
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">

==Product SKU==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* W03-New - [[ EP-0216-NEW ]] <font color=red>NEW</font><br>
* RS-P13 - [[ EP-0249 ]] <font color=red>NEW</font><br>
* S021 - [[ EP-0242 ]] <font color=red>NEW</font><br>
* N16 - [[ EP-0180 ]] <font color=red>NEW</font><br>
* P33 - [[ EP-0241 ]] <font color=red>NEW</font><br>
* P31 - [[ EP-0240 ]] <font color=red>NEW</font><br>
* P30 - [[ EP-0238 ]] <font color=red>NEW</font><br>
* CN01 - [[ EP-0236 ]] <font color=red>NEW</font><br>
* N06 - [[ EP-0239 ]] <font color=red>NEW</font><br>
* RS-P11 - [[ EP-0234 ]] <font color=red>NEW</font><br>
* B14 - [[ EP-0233 ]] <font color=red>NEW</font><br>
* N12 - [[ EP-0213 ]] <font color=red>NEW</font><br>
* U2500 - [[ EP-0235 ]] <font color=red>NEW</font><br>
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N21 - [[ EP-0231 ]] <font color=red>NEW</font><br>
* N20 - [[ EP-0227 ]] <font color=red>NEW</font><br>
* W01 - [[ EP-0228 ]] <font color=red>NEW</font><br>
* N10 - [[ EP-0229 ]] <font color=red>NEW</font><br>
* B12 - [[ EP-0230 ]] <font color=red>NEW</font><br>
* M01 - [[ EP-0223 ]] <font color=red>NEW</font><br>
* M02 - [[ EP-0217 ]] <font color=red>NEW</font><br>
* N05 - [[ EP-0209 ]] <font color=red>NEW</font><br>

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N04 - [[ EP-0210 ]] <font color=red>NEW</font><br>
* N07 - [[ EP-0211 ]] <font color=red>NEW</font><br>
* P02 - [[ EP-0219 ]] <font color=red>NEW</font><br>
* 52Pi NVDAC - [[ EP-0218 ]]
* 52Pi NVdigi - [[ EP-0220 ]]
* M.2 2242 NVME SSD for RPi 5 NES-CASE - [[ EP-0212 ]]
* W03 - [[ EP-0216 ]]
* Ice tower plus for RPi 5 - [[ EP-0224 ]]
</td></tr></table>
<br>

==Mini Tower Kit Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0187 ]] <font color=red>NEW</font>
* [[ ZP-0172 ]]
* [[ ZP-0128 ]]
* [[ ZP-0128-3B ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0128-4wire ]]
* [[ ZP-0129-4wire ]]
* [[ ZP-0130-4wire ]]
</td>

<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0129 ]]
* [[ ZP-0130 ]]
* [[ ZP-0132 ]]
</td>
</tr>
</table>

==Hat Stack==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0167 ]]
* [[ EP-0168 ]]
* [[ EP-0166 ]]
* [[ EP-0152 ]]
* [[ EP-0116 ]]
* [[ EP-0098 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0099 ]]
* [[ EP-0104 ]]
* [[ EP-0106 ]]
* [[ EP-0107 ]]
* [[ EP-0108 ]]
* [[ EP-0109 ]]
* [[ EP-0105 ]]
</td></tr></table>

==Starter Kit==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0067 ]]
* [[ KZ-0061 ]]
* [[ KZ-0016 ]]
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0020 ]]
* [[ KZ-0009 ]]
</td></tr></table>

==Development Boards==
===RP2040 Series===
* [[ EP-0174 ]]
===StarFive2===
* [[ ER-0043 ]]
* [[ ER-0044 ]]

===Micro:Bit===
* [[ KR-0004 ]]
* [[ KR-0027 ]]

===ROCK Pi Series===
* [[ EP-0265 ]]
* [[ KR-0001 ]]
* [[ KR-0012 ]]
* [[ ZP-0148 ]]

===Orange Pi Series===
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0156 ]]
* [[ ZP-0150 ]]
* [[ ZP-0149 ]]
* [[ F-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ F-0021 ]]
* [[ F-0022 ]]
* [[ KZ-0003 ]]
* [[ ER-0045 ]]
</td>
</tr>
</table>

===Raspberry Pi Pico Series===
* [[ KR-0006 ]]
* [[ EP-0175 ]]

==AI Learning==
* [[ EZ-0075 ]]
* [[ L-0031 ]]

==IoT Modules==
* [[ EP-0090 ]]
* [[ EZ-0061 ]]
* [[ EZ-0062 ]]
* [[ EZ-0063 ]]
----

==Tinker Board==
* [[ EZ-0066 ]]
* [[ EZ-0065 ]]

----
===DeskPi Series===
* [[ DP-0002 ]]
* [[ DP-0018 ]]

==KZ series==
* [[ KZ-0022 ]]
* [[ KZ-0056 ]]
* [[ KZ-0058 ]]
* [[ KZ-0060 ]]

==Raspberry Pi==
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0056 ]]
* [[ KR-0024 ]]
* [[ ER-0046 ]]
* [[ ER-0035 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0031 ]]
* [[ ER-0030 ]]
* [[ ER-0027 ]]
* [[ ER-0028 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0018 ]]
* [[ ER-0007 ]]
* [[ K-0231 ]]
* [[ K-0230 ]]
</td></tr></table>

----

===Raspberry Pi Pico & Pico W Breakout Board===
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0172 ]]
* [[ EP-0164 ]]
* [[ EP-0159 ]]
* [[ EP-0145 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0138 ]]
* [[ EP-0139 ]]
* [[ EP-0140 ]]
* [[ K-0582 ]]
* [[ K-0586 ]]
</tr></td></table>

==Banana Pi==
* [[ EB-0028 ]]
* [[ EB-0023 ]]
* [[ EB-0020 ]]
* [[ EP-0019 ]]
* [[ EB-0012 ]]
* [[ EB-0013 ]]

==Gaming Assesories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ D-0023 ]]
* [[ Z-0261 ]]
* [[ Z-0179 ]]
* [[ Z-0279 ]]
* [[ Z-0252 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ Z-0253 ]]
* [[ Z-0254 ]]
* [[ Z-0255 ]]
* [[ Z-0257 ]]
* [[ Z-0260 ]]
</td>
</tr></table>

==Electronic Accessories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0020 ]]
* [[ K-0580 ]]
* [[ ZP-0157 ]]
* [[ ZP-0158 ]]
</td>
</tr></table>

=Extension Modules=

==EP-Series (44 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0020 ]]
* [[ EP-0021 ]]
* [[ EP-0031 ]]
* [[ EP-0059 ]]
* [[ EP-0073 ]]
* [[ EP-0080 ]]
* [[ EP-0088 ]]
* [[ EP-0091 ]]
* [[ EP-0092 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0093 ]]
* [[ EP-0094 ]]
* [[ EP-0095 ]]
* [[ EP-0096 ]]
* [[ EP-0097 ]]
* [[ EP-0100 ]]
* [[ EP-0101 ]]
* [[ EP-0114 ]]
* [[ EP-0115 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0118 ]]
* [[ EP-0120 ]]
* [[ EP-0121 ]]
* [[ EP-0123 ]]
* [[ EP-0124 ]]
* [[ EP-0125 ]]
* [[ EP-0126 ]]
* [[ EP-0127 ]]
* [[ EP-0128 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0129 ]]
* [[ EP-0130 ]]
* [[ EP-0131 ]]
* [[ EP-0136 ]]
* [[ EP-0141 ]]
* [[ EP-0142 ]]
* [[ EP-0146 ]]
* [[ EP-0149 ]]
* [[ EP-0150 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0153 ]]
* [[ EP-0171 ]]
* [[ EP-0214 ]]
* [[ EP-0215 ]]
* [[ EP-0225 ]]
* [[ EP-0243 ]]
* [[ EP-0246 ]]
* [[ EP-0247 ]]
</td>
</tr>
</table>

==D-Series (16 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0001 ]]
* [[ D-0003 ]]
* [[ D-0005 ]]
* [[ D-0006 ]]
* [[ D-0007 ]]
* [[ D-0008 ]]
* [[ D-0009 ]]
* [[ D-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0011 ]]
* [[ D-0012 ]]
* [[ D-0013 ]]
* [[ D-0015 ]]
* [[ D-0016 ]]
* [[ D-0017 ]]
* [[ D-0018 ]]
* [[ D-0020 ]]
</td>
</tr>
</table>

==P-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0005 ]]
* [[ P-0006 ]]
* [[ P-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0011 ]]
* [[ P-0021 ]]
* [[ P-0024 ]]
</td>
</tr>
</table>

==Z-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0177 ]]
* [[ Z-0209 ]]
* [[ Z-0231 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0234 ]]
* [[ Z-0235 ]]
* [[ Z-0269 ]]
</td>
</tr>
</table>

==EZ-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0024 ]]
* [[ EZ-0048 ]]
* [[ EZ-0068 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0089 ]]
* [[ EZ-0106 ]]
</td>
</tr>
</table>

==ER-Series (4 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0014 ]]
* [[ ER-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0021 ]]
* [[ ER-0022 ]]
</td>
</tr>
</table>

==K-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0291 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0335 ]]
</td>
</tr>
</table>

==G-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ G-0002 ]]
</td>
</tr>
</table>

=Case & Enclosure & Heat sink=

==ZP-Series (78 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0024 ]]
* [[ ZP-0025 ]]
* [[ ZP-0029 ]]
* [[ ZP-0037 ]]
* [[ ZP-0038 ]]
* [[ ZP-0039 ]]
* [[ ZP-0040 ]]
* [[ ZP-0042 ]]
* [[ ZP-0049 ]]
* [[ ZP-0051 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0065 ]]
* [[ ZP-0066 ]]
* [[ ZP-0067 ]]
* [[ ZP-0068 ]]
* [[ ZP-0069 ]]
* [[ ZP-0070 ]]
* [[ ZP-0071 ]]
* [[ ZP-0072 ]]
* [[ ZP-0073 ]]
* [[ ZP-0074 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0075 ]]
* [[ ZP-0076 ]]
* [[ ZP-0077 ]]
* [[ ZP-0078 ]]
* [[ ZP-0079 ]]
* [[ ZP-0080 ]]
* [[ ZP-0081 ]]
* [[ ZP-0082 ]]
* [[ ZP-0083 ]]
* [[ ZP-0085 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0086 ]]
* [[ ZP-0087 ]]
* [[ ZP-0088 ]]
* [[ ZP-0089 ]]
* [[ ZP-0090 ]]
* [[ ZP-0091 ]]
* [[ ZP-0092 ]]
* [[ ZP-0093 ]]
* [[ ZP-0098 ]]
* [[ ZP-0099 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0100 ]]
* [[ ZP-0101 ]]
* [[ ZP-0102 ]]
* [[ ZP-0103 ]]
* [[ ZP-0105 ]]
* [[ ZP-0108 ]]
* [[ ZP-0110 ]]
* [[ ZP-0111 ]]
* [[ ZP-0112 ]]
* [[ ZP-0113 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0115 ]]
* [[ ZP-0116 ]]
* [[ ZP-0120 ]]
* [[ ZP-0133 ]]
* [[ ZP-0138 ]]
* [[ ZP-0139 ]]
* [[ ZP-0140 ]]
* [[ ZP-0141 ]]
* [[ ZP-0147 ]]
* [[ ZP-0153 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0162 ]]
* [[ ZP-0163 ]]
* [[ ZP-0164 ]]
* [[ ZP-0165 ]]
* [[ ZP-0166 ]]
* [[ ZP-0167 ]]
* [[ ZP-0168 ]]
* [[ ZP-0170 ]]
* [[ ZP-0173 ]]
* [[ ZP-0175 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0180 ]]
* [[ ZP-0181 ]]
* [[ ZP-0186 ]]
* [[ ZP-0188 ]]
* [[ ZP-0213 ]]
* [[ ZP-0215 ]]
* [[ ZP-0216 ]]
* [[ ZP-0222 ]]
</td>
</tr>
</table>

==C-Series (26 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0001 ]]
* [[ C-0002 ]]
* [[ C-0003 ]]
* [[ C-0004 ]]
* [[ C-0005 ]]
* [[ C-0006 ]]
* [[ C-0007 ]]
* [[ C-0008 ]]
* [[ C-0015 ]]
* [[ C-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0022 ]]
* [[ C-0023 ]]
* [[ C-0025 ]]
* [[ C-0027 ]]
* [[ C-0028 ]]
* [[ C-0031 ]]
* [[ C-0032 ]]
* [[ C-0033 ]]
* [[ C-0034 ]]
* [[ C-0047 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0048 ]]
* [[ C-0049 ]]
* [[ C-0050 ]]
* [[ C-0052 ]]
* [[ C-0054 ]]
* [[ C-0063 ]]
</td>
</tr>
</table>

==EP-Series (12 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0076 ]]
* [[ EP-0077 ]]
* [[ EP-0078 ]]
* [[ EP-0079 ]]
* [[ EP-0111 ]]
* [[ EP-0112 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0113 ]]
* [[ EP-0122 ]]
* [[ EP-0132 ]]
* [[ EP-0163 ]]
* [[ EP-0222 ]]
* [[ EP-0226 ]]
</td>
</tr>
</table>

==Z-Series (15 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0127 ]]
* [[ Z-0153 ]]
* [[ Z-0157 ]]
* [[ Z-0183 ]]
* [[ Z-0184 ]]
* [[ Z-0185 ]]
* [[ Z-0190 ]]
* [[ Z-0193 ]]
* [[ Z-0208 ]]
* [[ Z-0237 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0264 ]]
* [[ Z-0266 ]]
* [[ Z-0272 ]]
* [[ Z-0273 ]]
* [[ Z-0278 ]]
</td>
</tr>
</table>

==K-Series (10 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ K-0172 ]]
* [[ K-0178 ]]
* [[ K-0567 ]]
* [[ K-0583 ]]
* [[ K-0585 ]]
* [[ K-0589 ]]
* [[ K-0592 ]]
* [[ K-0595 ]]
* [[ K-0612 ]]
* [[ K-0638 ]]
</td>
</tr>
</table>

==KZ-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ KZ-0001 ]]
* [[ KZ-0002 ]]
* [[ kz-0063 ]]
</td>
</tr>
</table>

==ER-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ ER-0011 ]]
</td>
</tr>
</table>

==EZ-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ EZ-0059 ]]
</td>
</tr>
</table>

==F-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ F-0003 ]]
</td>
</tr>
</table>

==L-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ L-0030 ]]
</td>
</tr>
</table>

=Cooling Accessories=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0001 ]]
* [[ F-0002 ]]
* [[ F-0006 ]]
* [[ F-0005 ]]
* [[ F-0007 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0010 ]]
* [[ F-0011 ]]
* [[ F-0012 ]]
* [[ D-0022 ]]
* [[ F-0008 ]]
* [[ F-0008-RGB ]]
</td>
</tr></table>

==Electronic Engineer Tools==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0022 ]]
* [[ T-0021 ]]
* [[ T-0019 ]]
* [[ T-0015 ]]
* [[ T-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0017 ]]
* [[ T-0018 ]]
* [[ Z-0241 ]]
</td></tr></table>

=Displays=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>

==EP-Series (27 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0045 ]]
* [[ EP-0058 ]]
* [[ EP-0062 ]]
* [[ EP-0063 ]]
* [[ EP-0065 ]]
* [[ EP-0066 ]]
* [[ EP-0072 ]]
* [[ EP-0075 ]]
* [[ EP-0081 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0082 ]]
* [[ EP-0084 ]]
* [[ EP-0085 ]]
* [[ EP-0087 ]]
* [[ EP-0089 ]]
* [[ EP-0119 ]]
* [[ EP-0133 ]]
* [[ EP-0148 ]]
* [[ EP-0170 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0177 ]]
* [[ EP-0183 ]]
* [[ EP-0184 ]]
* [[ EP-0185 ]]
* [[ EP-0186 ]]
* [[ EP-0187 ]] <font color=red>NEW!!!</font>
* [[ EP-0188 ]]
* [[ EP-0189 ]] <font color=red>NEW!!!</font>
* [[ EP-0190 ]]
</td>
</tr>
</table>

==Z-Series (8 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0017 ]]
* [[ Z-0051 ]]
* [[ Z-0053 ]]
* [[ Z-0111 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0112 ]]
* [[ Z-0113 ]]
* [[ Z-0114 ]]
* [[ Z-0143 ]]
</td>
</tr>
</table>

==S-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0001 ]]
* [[ S-0003 ]]
* [[ S-0005 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0006 ]]
* [[ S-0007 ]]
* [[ S-0018 ]]
</td>
</tr>
</table>

==K-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0101 ]]
* [[ K-0102 ]]
* [[ K-0103 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0104 ]]
* [[ K-0106 ]]
</td>
</tr>

=Power Supply=

==P-Series (9 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0001 ]]
* [[ P-0007 ]]
* [[ P-0008 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0009 ]]
* [[ P-0017 ]]
* [[ P-0031 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0032 ]]
* [[ P-0040 ]]
* [[ P-0044 ]]
</td>
</tr>
</table>

==Z-Series (11 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0097 ]]
* [[ Z-0121 ]]
* [[ Z-0132 ]]
* [[ Z-0133 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0136 ]]
* [[ Z-0147 ]]
* [[ Z-0148 ]]
* [[ Z-0149 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0150 ]]
* [[ Z-0154 ]]
* [[ Z-0155 ]]
</td>
</tr>
</table>

==L-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0026 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0027 ]]
</td>
</tr>
</table>

==Raspberry Pi Kits==

==K-Series (18 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0111 ]]
* [[ K-0167 ]]
* [[ K-0168 ]]
* [[ K-0169 ]]
* [[ K-0171 ]]
* [[ K-0174 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0180 ]]
* [[ K-0185 ]]
* [[ K-0186 ]]
* [[ K-0238 ]]
* [[ K-0259 ]]
* [[ K-0401 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0403 ]]
* [[ K-0502 ]]
* [[ K-0503 ]]
* [[ K-0512 ]]
* [[ K-0522 ]]
* [[ K-0581 ]]
</td>
</tr>
</table>

==Z-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0142 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0144 ]]
</td>
</tr>
</table>

==T-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ T-0008 ]]
</td>
</tr>
</table>

DR-0005

2026-09-02T03:02:20Z

Yoyojacky: /* Package List */

== 19-inch 2U Rack Mount for Raspberry Pi==
* SKU: DR-0005
[[File:DR-0005 -2.jpg|right|320px]]
==Description==
The DR-0005 is a 19-inch, 2U rack-mountable enclosure designed to house multiple Raspberry Pi boards (compatible with Pi 5, 4B, 3B+, and 3B). It provides a compact, standardized solution for clustering or data-center deployment of single-board computers.
==Features==
* 19-inch 2U form factor — fits standard server racks
* Multi-model compatibility — supports Raspberry Pi 5 / 4B / 3B+ / 3B
* High-density layout — houses multiple Pi units in a single chassis
* Quick-release panels — individual Raspberry Pi boards can be removed rapidly without disassembling the entire unit
* Package dimensions — 51 × 13.5 × 10.5 cm
* Weight — 1.10 kg (gross) / 0.95 kg (net)

==Gallery==
* Product Outlook
[[File:DR-0005 -2.jpg|left|800px]]
<br style="clear:both;">
* Vertical view
[[File:DR-0005-1.jpg|left|800px]]
<br style="clear:both;">
* Size Informations
[[File:DR-0005-3..jpg|left|800px]]
<br style="clear:both;">
* Compatibility
[[File:DR-0005-5..jpg|left|800px]]
<br style="clear:both;">

==Package List==
[[File:DR-0005-6..jpg|left|800px]]
<br style="clear:both;">

DR-0005

2026-09-02T03:02:06Z

Yoyojacky: /* Gallery */

DR-0005

2026-09-02T03:01:39Z

Yoyojacky: Created page with "== 19-inch 2U Rack Mount for Raspberry Pi== * SKU: DR-0005 320px ==Description== The DR-0005 is a 19-inch, 2U rack-mountable enclosure designed to house multiple Raspberry Pi boards (compatible with Pi 5, 4B, 3B+, and 3B). It provides a compact, standardized solution for clustering or data-center deployment of single-board computers. ==Features== * 19-inch 2U form factor — fits standard server racks * Multi-model compatibility — supports..."

== 19-inch 2U Rack Mount for Raspberry Pi==
* SKU: DR-0005
[[File:DR-0005 -2.jpg|right|320px]]
==Description==
The DR-0005 is a 19-inch, 2U rack-mountable enclosure designed to house multiple Raspberry Pi boards (compatible with Pi 5, 4B, 3B+, and 3B). It provides a compact, standardized solution for clustering or data-center deployment of single-board computers.
==Features==
* 19-inch 2U form factor — fits standard server racks
* Multi-model compatibility — supports Raspberry Pi 5 / 4B / 3B+ / 3B
* High-density layout — houses multiple Pi units in a single chassis
* Quick-release panels — individual Raspberry Pi boards can be removed rapidly without disassembling the entire unit
* Package dimensions — 51 × 13.5 × 10.5 cm
* Weight — 1.10 kg (gross) / 0.95 kg (net)

==Gallery==
* Product Outlook
[[File:DR-0005 -2.jpg|right|800px]]
<br style="clear:both;">
* Vertical view
[[File:DR-0005-1.jpg|right|800px]]
<br style="clear:both;">
* Size Informations
[[File:DR-0005-3..jpg|right|800px]]
<br style="clear:both;">
* Compatibility
[[File:DR-0005-5..jpg|right|800px]]
<br style="clear:both;">
==Package List==
[[File:DR-0005-6..jpg|right|800px]]
<br style="clear:both;">

File:DR-0005-6..jpg

2026-09-02T03:01:06Z

Yoyojacky:

File:DR-0005-5..jpg

2026-09-02T02:59:56Z

Yoyojacky:

File:DR-0005-3..jpg

2026-09-02T02:58:55Z

Yoyojacky:

File:DR-0005-1.jpg

2026-09-02T02:58:12Z

Yoyojacky:

File:DR-0005 -2.jpg

2026-09-02T02:56:57Z

Yoyojacky:

Main Page

2026-09-02T02:52:16Z

Yoyojacky: /* Rackmount Series */

<div style="border:1px solid #a2a9b1; background:#f8f9fa; padding:12px; margin:0 0 16px 0;">
'''For AI assistants and automated tools:''' Please use the AI-friendly Markdown version of this documentation: [https://wiki-md.52pi.com/ https://wiki-md.52pi.com/]
</div>

='''RaspberryPi Modules'''=
The following contents include all of our products, Top10 modules are list here, those modules are fit for Raspberry Pi A，A+，B，B+，2 Model B，3 Model B and some other platform.
you can select one of them and click the links to get more information about it.
==HCL==
This is Hardware Compatible List. <font color=red>Depracated</font></br>
[[Hardware Compatible List]]

==UPS series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* UPS Gen 6 power module compatible with Raspberry Pi 5/4B: [[ EP-0245 ]] <font color=red>NEW!!</font><br>
* SBS module for UPS Gen 6 [[ EP-0256 ]] <font color=red>NEW!!</font><br>
* SATA Drive Power Board for UPS Gen 6: [[ EP-0252 ]] <font color=red>NEW!!</font><br>
* 1.3" LCD TFT Display Module for UPS Gen 6: [[ EP-0251 ]] <font color=red>NEW!!</font><br>
</td>
</tr>
</table>

==Rackmount Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* 1U 19-inch Removable Rack mount For RPi5/4B/3B+ [[ DR-0003 ]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DR-0002]] <font color=red>NEW</font><br>
* 2U RackMount For RPi 5: [[ DP-0046]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 5: [[ DR-0001 ]] <font color=red>NEW</font><br>
* 1U RackMount For RPi 4B: [[ EP-0143 ]]
* 19-inch 2U Rack Mount for Raspberry Pi [[DR-0005]]
</td>
</tr>
</table>

==Arduino Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
===Arduino UNO Q Series===
* Level-Shift Shield [[ EP-0257 ]] <font color=red>NEW</font><br>
* Arduino Nano ESP32 RGB LED Matrix Shield [[ EP-0263]] <font color=red>NEW</font><br>
* Terminal Expansion Base for Arduino NANO ESP32 [[ EP-0262 ]] <font color=red>NEW</font><br>

===Arduino UNO R4 Wi-Fi Series===
* [[ KZ-0054 ]]
* [[ KZ-0077 ]]
* [[ KZ-0086 ]]
</td>
</tr>
</table>

==52Pi N Series==
===Description===
The 52Pi N series is a line of storage products where "N" stands for NAS (Network Attached Storage), and the numerical designation represents various models and product types. Users can choose different types based on their specific needs to fulfill their usage requirements.
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">

==Product SKU==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* W03-New - [[ EP-0216-NEW ]] <font color=red>NEW</font><br>
* RS-P13 - [[ EP-0249 ]] <font color=red>NEW</font><br>
* S021 - [[ EP-0242 ]] <font color=red>NEW</font><br>
* N16 - [[ EP-0180 ]] <font color=red>NEW</font><br>
* P33 - [[ EP-0241 ]] <font color=red>NEW</font><br>
* P31 - [[ EP-0240 ]] <font color=red>NEW</font><br>
* P30 - [[ EP-0238 ]] <font color=red>NEW</font><br>
* CN01 - [[ EP-0236 ]] <font color=red>NEW</font><br>
* N06 - [[ EP-0239 ]] <font color=red>NEW</font><br>
* RS-P11 - [[ EP-0234 ]] <font color=red>NEW</font><br>
* B14 - [[ EP-0233 ]] <font color=red>NEW</font><br>
* N12 - [[ EP-0213 ]] <font color=red>NEW</font><br>
* U2500 - [[ EP-0235 ]] <font color=red>NEW</font><br>
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N21 - [[ EP-0231 ]] <font color=red>NEW</font><br>
* N20 - [[ EP-0227 ]] <font color=red>NEW</font><br>
* W01 - [[ EP-0228 ]] <font color=red>NEW</font><br>
* N10 - [[ EP-0229 ]] <font color=red>NEW</font><br>
* B12 - [[ EP-0230 ]] <font color=red>NEW</font><br>
* M01 - [[ EP-0223 ]] <font color=red>NEW</font><br>
* M02 - [[ EP-0217 ]] <font color=red>NEW</font><br>
* N05 - [[ EP-0209 ]] <font color=red>NEW</font><br>

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* N04 - [[ EP-0210 ]] <font color=red>NEW</font><br>
* N07 - [[ EP-0211 ]] <font color=red>NEW</font><br>
* P02 - [[ EP-0219 ]] <font color=red>NEW</font><br>
* 52Pi NVDAC - [[ EP-0218 ]]
* 52Pi NVdigi - [[ EP-0220 ]]
* M.2 2242 NVME SSD for RPi 5 NES-CASE - [[ EP-0212 ]]
* W03 - [[ EP-0216 ]]
* Ice tower plus for RPi 5 - [[ EP-0224 ]]
</td></tr></table>
<br>

==Mini Tower Kit Series==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0187 ]] <font color=red>NEW</font>
* [[ ZP-0172 ]]
* [[ ZP-0128 ]]
* [[ ZP-0128-3B ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0128-4wire ]]
* [[ ZP-0129-4wire ]]
* [[ ZP-0130-4wire ]]
</td>

<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0129 ]]
* [[ ZP-0130 ]]
* [[ ZP-0132 ]]
</td>
</tr>
</table>

==Hat Stack==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0167 ]]
* [[ EP-0168 ]]
* [[ EP-0166 ]]
* [[ EP-0152 ]]
* [[ EP-0116 ]]
* [[ EP-0098 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0099 ]]
* [[ EP-0104 ]]
* [[ EP-0106 ]]
* [[ EP-0107 ]]
* [[ EP-0108 ]]
* [[ EP-0109 ]]
* [[ EP-0105 ]]
</td></tr></table>

==Starter Kit==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0067 ]]
* [[ KZ-0061 ]]
* [[ KZ-0016 ]]
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ KZ-0020 ]]
* [[ KZ-0009 ]]
</td></tr></table>

==Development Boards==
===RP2040 Series===
* [[ EP-0174 ]]
===StarFive2===
* [[ ER-0043 ]]
* [[ ER-0044 ]]

===Micro:Bit===
* [[ KR-0004 ]]
* [[ KR-0027 ]]

===ROCK Pi Series===
* [[ EP-0265 ]]
* [[ KR-0001 ]]
* [[ KR-0012 ]]
* [[ ZP-0148 ]]

===Orange Pi Series===
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ZP-0156 ]]
* [[ ZP-0150 ]]
* [[ ZP-0149 ]]
* [[ F-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ F-0021 ]]
* [[ F-0022 ]]
* [[ KZ-0003 ]]
* [[ ER-0045 ]]
</td>
</tr>
</table>

===Raspberry Pi Pico Series===
* [[ KR-0006 ]]
* [[ EP-0175 ]]

==AI Learning==
* [[ EZ-0075 ]]
* [[ L-0031 ]]

==IoT Modules==
* [[ EP-0090 ]]
* [[ EZ-0061 ]]
* [[ EZ-0062 ]]
* [[ EZ-0063 ]]
----

==Tinker Board==
* [[ EZ-0066 ]]
* [[ EZ-0065 ]]

----
===DeskPi Series===
* [[ DP-0002 ]]
* [[ DP-0018 ]]

==KZ series==
* [[ KZ-0022 ]]
* [[ KZ-0056 ]]
* [[ KZ-0058 ]]
* [[ KZ-0060 ]]

==Raspberry Pi==
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0056 ]]
* [[ KR-0024 ]]
* [[ ER-0046 ]]
* [[ ER-0035 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0031 ]]
* [[ ER-0030 ]]
* [[ ER-0027 ]]
* [[ ER-0028 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ ER-0018 ]]
* [[ ER-0007 ]]
* [[ K-0231 ]]
* [[ K-0230 ]]
</td></tr></table>

----

===Raspberry Pi Pico & Pico W Breakout Board===
<table>
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0172 ]]
* [[ EP-0164 ]]
* [[ EP-0159 ]]
* [[ EP-0145 ]]

</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ EP-0138 ]]
* [[ EP-0139 ]]
* [[ EP-0140 ]]
* [[ K-0582 ]]
* [[ K-0586 ]]
</tr></td></table>

==Banana Pi==
* [[ EB-0028 ]]
* [[ EB-0023 ]]
* [[ EB-0020 ]]
* [[ EP-0019 ]]
* [[ EB-0012 ]]
* [[ EB-0013 ]]

==Gaming Assesories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ D-0023 ]]
* [[ Z-0261 ]]
* [[ Z-0179 ]]
* [[ Z-0279 ]]
* [[ Z-0252 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 10%;">
* [[ Z-0253 ]]
* [[ Z-0254 ]]
* [[ Z-0255 ]]
* [[ Z-0257 ]]
* [[ Z-0260 ]]
</td>
</tr></table>

==Electronic Accessories==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0020 ]]
* [[ K-0580 ]]
* [[ ZP-0157 ]]
* [[ ZP-0158 ]]
</td>
</tr></table>

=Extension Modules=

==EP-Series (44 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0020 ]]
* [[ EP-0021 ]]
* [[ EP-0031 ]]
* [[ EP-0059 ]]
* [[ EP-0073 ]]
* [[ EP-0080 ]]
* [[ EP-0088 ]]
* [[ EP-0091 ]]
* [[ EP-0092 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0093 ]]
* [[ EP-0094 ]]
* [[ EP-0095 ]]
* [[ EP-0096 ]]
* [[ EP-0097 ]]
* [[ EP-0100 ]]
* [[ EP-0101 ]]
* [[ EP-0114 ]]
* [[ EP-0115 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0118 ]]
* [[ EP-0120 ]]
* [[ EP-0121 ]]
* [[ EP-0123 ]]
* [[ EP-0124 ]]
* [[ EP-0125 ]]
* [[ EP-0126 ]]
* [[ EP-0127 ]]
* [[ EP-0128 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0129 ]]
* [[ EP-0130 ]]
* [[ EP-0131 ]]
* [[ EP-0136 ]]
* [[ EP-0141 ]]
* [[ EP-0142 ]]
* [[ EP-0146 ]]
* [[ EP-0149 ]]
* [[ EP-0150 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 20%;">
* [[ EP-0153 ]]
* [[ EP-0171 ]]
* [[ EP-0214 ]]
* [[ EP-0215 ]]
* [[ EP-0225 ]]
* [[ EP-0243 ]]
* [[ EP-0246 ]]
* [[ EP-0247 ]]
</td>
</tr>
</table>

==D-Series (16 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0001 ]]
* [[ D-0003 ]]
* [[ D-0005 ]]
* [[ D-0006 ]]
* [[ D-0007 ]]
* [[ D-0008 ]]
* [[ D-0009 ]]
* [[ D-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ D-0011 ]]
* [[ D-0012 ]]
* [[ D-0013 ]]
* [[ D-0015 ]]
* [[ D-0016 ]]
* [[ D-0017 ]]
* [[ D-0018 ]]
* [[ D-0020 ]]
</td>
</tr>
</table>

==P-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0005 ]]
* [[ P-0006 ]]
* [[ P-0010 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ P-0011 ]]
* [[ P-0021 ]]
* [[ P-0024 ]]
</td>
</tr>
</table>

==Z-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0177 ]]
* [[ Z-0209 ]]
* [[ Z-0231 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0234 ]]
* [[ Z-0235 ]]
* [[ Z-0269 ]]
</td>
</tr>
</table>

==EZ-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0024 ]]
* [[ EZ-0048 ]]
* [[ EZ-0068 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EZ-0089 ]]
* [[ EZ-0106 ]]
</td>
</tr>
</table>

==ER-Series (4 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0014 ]]
* [[ ER-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ ER-0021 ]]
* [[ ER-0022 ]]
</td>
</tr>
</table>

==K-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0291 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0335 ]]
</td>
</tr>
</table>

==G-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ G-0002 ]]
</td>
</tr>
</table>

=Case & Enclosure & Heat sink=

==ZP-Series (78 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0024 ]]
* [[ ZP-0025 ]]
* [[ ZP-0029 ]]
* [[ ZP-0037 ]]
* [[ ZP-0038 ]]
* [[ ZP-0039 ]]
* [[ ZP-0040 ]]
* [[ ZP-0042 ]]
* [[ ZP-0049 ]]
* [[ ZP-0051 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0065 ]]
* [[ ZP-0066 ]]
* [[ ZP-0067 ]]
* [[ ZP-0068 ]]
* [[ ZP-0069 ]]
* [[ ZP-0070 ]]
* [[ ZP-0071 ]]
* [[ ZP-0072 ]]
* [[ ZP-0073 ]]
* [[ ZP-0074 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0075 ]]
* [[ ZP-0076 ]]
* [[ ZP-0077 ]]
* [[ ZP-0078 ]]
* [[ ZP-0079 ]]
* [[ ZP-0080 ]]
* [[ ZP-0081 ]]
* [[ ZP-0082 ]]
* [[ ZP-0083 ]]
* [[ ZP-0085 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0086 ]]
* [[ ZP-0087 ]]
* [[ ZP-0088 ]]
* [[ ZP-0089 ]]
* [[ ZP-0090 ]]
* [[ ZP-0091 ]]
* [[ ZP-0092 ]]
* [[ ZP-0093 ]]
* [[ ZP-0098 ]]
* [[ ZP-0099 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0100 ]]
* [[ ZP-0101 ]]
* [[ ZP-0102 ]]
* [[ ZP-0103 ]]
* [[ ZP-0105 ]]
* [[ ZP-0108 ]]
* [[ ZP-0110 ]]
* [[ ZP-0111 ]]
* [[ ZP-0112 ]]
* [[ ZP-0113 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0115 ]]
* [[ ZP-0116 ]]
* [[ ZP-0120 ]]
* [[ ZP-0133 ]]
* [[ ZP-0138 ]]
* [[ ZP-0139 ]]
* [[ ZP-0140 ]]
* [[ ZP-0141 ]]
* [[ ZP-0147 ]]
* [[ ZP-0153 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0162 ]]
* [[ ZP-0163 ]]
* [[ ZP-0164 ]]
* [[ ZP-0165 ]]
* [[ ZP-0166 ]]
* [[ ZP-0167 ]]
* [[ ZP-0168 ]]
* [[ ZP-0170 ]]
* [[ ZP-0173 ]]
* [[ ZP-0175 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 12%;">
* [[ ZP-0180 ]]
* [[ ZP-0181 ]]
* [[ ZP-0186 ]]
* [[ ZP-0188 ]]
* [[ ZP-0213 ]]
* [[ ZP-0215 ]]
* [[ ZP-0216 ]]
* [[ ZP-0222 ]]
</td>
</tr>
</table>

==C-Series (26 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0001 ]]
* [[ C-0002 ]]
* [[ C-0003 ]]
* [[ C-0004 ]]
* [[ C-0005 ]]
* [[ C-0006 ]]
* [[ C-0007 ]]
* [[ C-0008 ]]
* [[ C-0015 ]]
* [[ C-0020 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0022 ]]
* [[ C-0023 ]]
* [[ C-0025 ]]
* [[ C-0027 ]]
* [[ C-0028 ]]
* [[ C-0031 ]]
* [[ C-0032 ]]
* [[ C-0033 ]]
* [[ C-0034 ]]
* [[ C-0047 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ C-0048 ]]
* [[ C-0049 ]]
* [[ C-0050 ]]
* [[ C-0052 ]]
* [[ C-0054 ]]
* [[ C-0063 ]]
</td>
</tr>
</table>

==EP-Series (12 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0076 ]]
* [[ EP-0077 ]]
* [[ EP-0078 ]]
* [[ EP-0079 ]]
* [[ EP-0111 ]]
* [[ EP-0112 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ EP-0113 ]]
* [[ EP-0122 ]]
* [[ EP-0132 ]]
* [[ EP-0163 ]]
* [[ EP-0222 ]]
* [[ EP-0226 ]]
</td>
</tr>
</table>

==Z-Series (15 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0127 ]]
* [[ Z-0153 ]]
* [[ Z-0157 ]]
* [[ Z-0183 ]]
* [[ Z-0184 ]]
* [[ Z-0185 ]]
* [[ Z-0190 ]]
* [[ Z-0193 ]]
* [[ Z-0208 ]]
* [[ Z-0237 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0264 ]]
* [[ Z-0266 ]]
* [[ Z-0272 ]]
* [[ Z-0273 ]]
* [[ Z-0278 ]]
</td>
</tr>
</table>

==K-Series (10 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ K-0172 ]]
* [[ K-0178 ]]
* [[ K-0567 ]]
* [[ K-0583 ]]
* [[ K-0585 ]]
* [[ K-0589 ]]
* [[ K-0592 ]]
* [[ K-0595 ]]
* [[ K-0612 ]]
* [[ K-0638 ]]
</td>
</tr>
</table>

==KZ-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ KZ-0001 ]]
* [[ KZ-0002 ]]
</td>
</tr>
</table>

==ER-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ ER-0011 ]]
</td>
</tr>
</table>

==EZ-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ EZ-0059 ]]
</td>
</tr>
</table>

==F-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ F-0003 ]]
</td>
</tr>
</table>

==L-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ L-0030 ]]
</td>
</tr>
</table>

=Cooling Accessories=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0001 ]]
* [[ F-0002 ]]
* [[ F-0006 ]]
* [[ F-0005 ]]
* [[ F-0007 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ F-0010 ]]
* [[ F-0011 ]]
* [[ F-0012 ]]
* [[ D-0022 ]]
* [[ F-0008 ]]
* [[ F-0008-RGB ]]
</td>
</tr></table>

==Electronic Engineer Tools==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0022 ]]
* [[ T-0021 ]]
* [[ T-0019 ]]
* [[ T-0015 ]]
* [[ T-0016 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 32%;">
* [[ T-0017 ]]
* [[ T-0018 ]]
* [[ Z-0241 ]]
</td></tr></table>

=Displays=
<pre> EOL stands for "End of Life", means this product will not produce any more</pre>

==EP-Series (27 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0045 ]]
* [[ EP-0058 ]]
* [[ EP-0062 ]]
* [[ EP-0063 ]]
* [[ EP-0065 ]]
* [[ EP-0066 ]]
* [[ EP-0072 ]]
* [[ EP-0075 ]]
* [[ EP-0081 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0082 ]]
* [[ EP-0084 ]]
* [[ EP-0085 ]]
* [[ EP-0087 ]]
* [[ EP-0089 ]]
* [[ EP-0119 ]]
* [[ EP-0133 ]]
* [[ EP-0148 ]]
* [[ EP-0170 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ EP-0177 ]]
* [[ EP-0183 ]]
* [[ EP-0184 ]]
* [[ EP-0185 ]]
* [[ EP-0186 ]]
* [[ EP-0187 ]] <font color=red>NEW!!!</font>
* [[ EP-0188 ]]
* [[ EP-0189 ]] <font color=red>NEW!!!</font>
* [[ EP-0190 ]]
</td>
</tr>
</table>

==Z-Series (8 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0017 ]]
* [[ Z-0051 ]]
* [[ Z-0053 ]]
* [[ Z-0111 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0112 ]]
* [[ Z-0113 ]]
* [[ Z-0114 ]]
* [[ Z-0143 ]]
</td>
</tr>
</table>

==S-Series (6 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0001 ]]
* [[ S-0003 ]]
* [[ S-0005 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ S-0006 ]]
* [[ S-0007 ]]
* [[ S-0018 ]]
</td>
</tr>
</table>

==K-Series (5 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0101 ]]
* [[ K-0102 ]]
* [[ K-0103 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ K-0104 ]]
* [[ K-0106 ]]
</td>
</tr>

=Power Supply=

==P-Series (9 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0001 ]]
* [[ P-0007 ]]
* [[ P-0008 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0009 ]]
* [[ P-0017 ]]
* [[ P-0031 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ P-0032 ]]
* [[ P-0040 ]]
* [[ P-0044 ]]
</td>
</tr>
</table>

==Z-Series (11 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0097 ]]
* [[ Z-0121 ]]
* [[ Z-0132 ]]
* [[ Z-0133 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0136 ]]
* [[ Z-0147 ]]
* [[ Z-0148 ]]
* [[ Z-0149 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ Z-0150 ]]
* [[ Z-0154 ]]
* [[ Z-0155 ]]
</td>
</tr>
</table>

==L-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0026 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ L-0027 ]]
</td>
</tr>
</table>

==Raspberry Pi Kits==

==K-Series (18 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0111 ]]
* [[ K-0167 ]]
* [[ K-0168 ]]
* [[ K-0169 ]]
* [[ K-0171 ]]
* [[ K-0174 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0180 ]]
* [[ K-0185 ]]
* [[ K-0186 ]]
* [[ K-0238 ]]
* [[ K-0259 ]]
* [[ K-0401 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 33%;">
* [[ K-0403 ]]
* [[ K-0502 ]]
* [[ K-0503 ]]
* [[ K-0512 ]]
* [[ K-0522 ]]
* [[ K-0581 ]]
</td>
</tr>
</table>

==Z-Series (2 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0142 ]]
</td>
<td style="text-align: left; vertical-align: top; width: 50%;">
* [[ Z-0144 ]]
</td>
</tr>
</table>

==T-Series (1 items)==
<table border="0" cellpadding="10" style="width: 100%;">
<tr>
<td style="text-align: left; vertical-align: top; width: 100%;">
* [[ T-0008 ]]
</td>
</tr>
</table>

DR-0001

2026-08-21T06:17:30Z

Yoyojacky: /* 3. Files Created / Modified */

==1U Rackmount for Raspberry Pi 5 ==
* Purchase URL: [ https://52pi.com ] or [ https://deskpi.com ]
[[File:DR-0001-1.jpg|right|320px]]

==Description==
This is an upgraded version of a 1U Rackmount designed for compatibility with both Raspberry Pi 5 . It features a motherboard that supports PCIe expansion, allowing the PCIe interface of the Raspberry Pi 5 to be extended to accommodate an M.2 NVMe SSD in 2230/2242/2260/2280 form factors. The expansion board also routes the Raspberry Pi's 5V and GND, SDA, and SCL pins to the rear through PogoPin connectors, providing I2C interface peripherals in a Grove format. Additionally, a red LED is included on the board for the Raspberry Pi ID signal pin, which can be programmed to indicate the current device by controlling the GPIO4 pin's high or low level, acting as a programmable device ID signal light.

The Rackmount supports the connection of up to five Raspberry Pi devices and can also be configured with an OLED display frame in place of one of the Raspberry Pi slots. These components can be easily adjusted and removed due to the use of hand-tightened screws. The OLED display features a 0.91-inch screen and communicates with the Raspberry Pi via I2C protocol, displaying real-time information such as CPU status, memory status, IP information, and serial numbers. The content displayed on the OLED can be fully customized.
==Features==
* <strong>Compatibility:</strong> Designed to work with both Raspberry Pi 5.
* <strong>PCIe Expansion Support:</strong> Includes a motherboard that enables PCIe expansion, allowing the connection of M.2 NVMe SSDs in various form factors (2230/2242/2260/2280).
* <strong>I2C Interface: </strong> The board routes the Raspberry Pi's 5V, GND, SDA, and SCL pins to the rear through PogoPin connectors, offering I2C interface peripherals in a Grove format.
* <strong>Programmable LED Indicator: </strong> A red LED on the board serves as a programmable device ID signal, controllable via the GPIO4 pin to indicate the status or identity of the device.
* <strong>Modular Design:</strong> Supports the integration of up to five Raspberry Pi devices, with the option to replace one slot with an OLED display frame.
* <strong>OLED Display Integration:</strong> The option to include a 0.91-inch OLED screen that communicates with the Raspberry Pi via I2C, displaying customizable information such as CPU usage, memory status, IP address, and serial numbers.
* <strong>Easy Assembly and Disassembly:</strong> Components are secured with hand-tightened screws, allowing for convenient adjustments and removal.
* <strong>Customizable Display Content: </strong> The information displayed on the OLED screen can be fully customized to meet specific needs or preferences.
* <strong>Rackmount Form Factor: </strong> Designed to fit into a 1U rack space, making it suitable for data centers or other environments where space is at a premium.
* <strong>Versatility:</strong> The Rackmount can be configured in various ways to suit different use cases, whether for development, testing, or deployment in a production environment.
===Specifications===
* Form Factor: 1U Rackmount design suitable for standard 19-inch racks.
* Raspberry Pi Compatibility: Specifically designed for Raspberry Pi 5.
* PCIe Expansion:Supports M.2 NVMe SSDs in 2230, 2242, 2260, and 2280 form factors. Provides a PCIe interface for high-speed data transfer.
* I/O Connectivity: Rear I2C interface via PogoPin connectors for external peripherals.
* GPIO4 pin for programmable LED control.
* LED Indicator:Red LED for device identification or status indication. Programmable through software to show different statuses.
* Modular Bays: Five bays for Raspberry Pi devices. One bay can be replaced with an OLED display module.
* OLED Display Specifications:0.91-inch screen size, 128x32 pixels. I2C communication protocol.
* Customizable display for system information.
* Physical Security:Hand-tightened screws for secure mounting of Raspberry Pi devices and OLED display.
* Ensures stability and ease of maintenance.
* Power Requirements: Compatibility with Raspberry Pi's standard power supply.
* Material and Construction: Durable metal construction for the rackmount chassis. High-quality components for reliable performance.
* Mounting Options: Standard rackmount holes for easy installation into a rack.
* Includes additional mounting accessories for different setups.
* Software Compatibility: Compatible with Raspberry Pi's operating system and software ecosystem.
* Support for GPIO programming for custom LED and device control.
==Gallery==
* Product outlook
[[ File:DR-0001-6.jpg |left|800px]]
<br style="clear:both":>

* Application Senario
[[ File:DR-0001-2.jpg |left|800px]]
<br style="clear:both":>
<font color=red> NOTE: Raspberry Pis are not included in the package, additional purchase required!</font><br>
* Easy to assemble and maintain
[[ File:DR-0001-3.jpg |left|800px]]
<br style="clear:both":>
[[File:DR-0001-12.jpg|left|800px]]
<br style="clear:both":>

* Customizable OLED display screen, with a size of 0.91 inches
[[ File:DR-0001-4.jpg |left|800px]]
<br style="clear:both":>

* Ports Definitions and Featrues
Programmable I/O controlled UID indicator light, which can be programmed to control the LED blinking to indicate the device's location, facilitating faster troubleshooting and easier maintenance operations.
[[ File:DR-0001-5.jpg |left|800px]]
<br style="clear:both":>

===How to connect OLED display to Raspberry Pi on GPIO pins===
* Please refer to following figure to connect OLED display to Raspberry Pi on GPIO.
<font color=red>NOTE: OLED's VCC should be connected to 3.3V power rail, Do not connect it to 5V power rail!!!</font><br>
[[ File:DR-0001-7.jpg |left|800px]]
<br style="clear:both":>

* Grove Connector Support I2C and Uart
[[ File:DR-0001-8.jpg |left|800px]]
<br style="clear:both":>

* Accessories Dimension
[[ File:DR-0001-9.jpg |left|800px]]
<br style="clear:both":>

* OLED assemble details
Please remove the protection film from acrylic panel and use the washer between OLED PCB board and acrylic panel.
[[ File:DR-0001-10.jpg |left|800px]]
<br style="clear:both":>

* PCIe Expansion board for Raspberry Pi 5 only
The expansion board supports M.2 NVMe M-key SSD 2230/2242/2260/2280, and the board will be powered by Raspberry Pi 5 via PogoPin on the PCB board, please make sure the board's pogoins are contact well with the soldering point on back of the Raspberry Pi 5 on GPIO pins.
[[File:DR-0001-11.jpg|left|800px]]
<br style="clear:both":>

==How to assemble it? ==
* Please note that there are several details you need to pay attention, plesae check out following figure.
[[ File:DR-0001-安装.jpg|left|800px]]
<br style="clear:both";>

==Package Includes==
* Following figure shows the details of the product:
[[ File:DR-0001-清单.jpg|left|800px]]
<br style="clear:both";>

==How to enable I2C OLED display?==
* We assume that you are using Raspberry Pi OS 64bit(bookworm, the latest official image)
To enable I2C and UART on your Raspberry Pi, you can follow these detailed steps:

===Enabling I2C===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
to open the configuration tool. Navigate to `Interface Options`, Select `I2C` and enable it.

* Method 2. Using the Command Line:
You can also enable I2C by editing the `/boot/firmware/config.txt` file and adding `dtparam=i2c_arm=on` if it's not already present, After making changes, reboot your Pi.

===Verifying I2C===
* Install I2C tools using `sudo apt-get install -y i2c-tools`.
* Use
<pre>
i2cdetect -y 1
</pre>
to scan for I2C devices, if you see `3c` means that the OLED display has been recognized by your Raspberry Pi.

===Enabling UART===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
Go to `Interface Options`, Select `Serial` and enable it.
<pre> Note: This will also enable the login shell on the serial port. </pre>

* Method 2. Using the Command Line:
Edit `/boot/config.txt` and add `enable_uart=1`, save it and then reboot your Pi.

===Accessing UART===
* Connect your Pi to a USB-to-TTL converter, On Windows, you may need to install drivers for the converter. on Linux just use a terminal program like `minicom`, `putty`, or `screen` to access the UART interface.

Remember to check the documentation for your specific Raspberry Pi model, as the steps might vary slightly. If you need more detailed instructions or encounter any issues, refer to the [ https://www.raspberrypi.org/documentation/ ] or community forums for additional support.

===How to display customized information on OLED display? ===
* Final result
[[File:DR-0001 applications-01.jpg|left|800px]]
<br style="clear:both";>
==How to customize content on OLED ?==
* For example: If you want to display current IP address of wlan interface and the serial number of your Raspberry Pi 5, please follow next steps to configure it.
===Install Virtal environment package ===
* Open a terminal and typing following commands:
<pre>
sudo apt update
sudo apt upgrade -y
sudo apt -y install virtualenv
sudo usermod -a -G i2c,spi,gpio pi
sudo apt install python3-dev python3-pip python3-numpy libfreetype6-dev libjpeg-dev build-essential
sudo apt install libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libportmidi-dev
</pre>
[[File:Install pre-insistpackages.png|left|800px]]
<br style="clear:both";>
[[File:Install-pre-insistpackage-02.png|left|800px]]
<br style="clear:both";>

===Create virtual environment===
<pre>
virtualenv -p python3 venv
cd venv/
source bin/activate
</pre>
===Install SSD1306 driver and library for OLED 0.91===
<pre>
pip install luma.oled
pip install psutil
</pre>

===Clone luma.examples repository===
Log out and in again and clone this repository:
<pre>
git clone https://github.com/rm-hull/luma.examples.git
cd luma.examples/
</pre>
===Install luma libraries===
<pre>
sudo -H pip install -e . --break-system-packages
</pre>
[[File:Install luma libraries.png|left|800px]]
<br style="clear:both";>
===Test the demo ===
<pre>
cd examples/
sudo python 3d_box.py --width=128 --height=32 -r 2
</pre>

<font color=red><p>NOTE: <br>
--width=128 and --height=32 should be added to declear the OLED's resolution information. <br>
-r 2 means --rotate 2 , Allowed values are: 0, 1, 2, 3 (default:0)
</p>
</font>
If you see a 3D-box rotating animation is in the middle of screen means that you have installed the OLED driver successfully!
[[File:Test demo 3dbox.png|left|800px]]
<br style="clear:both";>
[[File:Test demo 3dbox-2.png|left|800px]]
<br style="clear:both";>
and then press "Ctrol+C" abort the demo.

==Use the demo code==
* There are a lot of demo codes in the examples folder, you can test it as you want.
for example:
<pre>
sudo python carousel.py --width=128 --height=32 -r 2
</pre>
It will display all information of your Raspberry Pi 5 and scrolling display.
===Customize the display on screen===
Modify the sys_info.py python file and adding your own function to show the information you want, do remember backup the origin file.
<pre>
cp sys_info.py sys_info.py.bak
vim.tiny sys_info.py
</pre>
Press 'i' to insert mode, and paste following lines into it. you can modify this file by other text editor what you like.
<pre>
#!/usr/bin/env python
# -*- coding: utf-8 -*-
# Copyright (c) 2014-2022 Richard Hull and contributors
# See LICENSE.rst for details.
# PYTHON_ARGCOMPLETE_OK

"""
Display basic system information.

Needs psutil (+ dependencies) installed::

$ sudo apt-get install python-dev
$ sudo -H pip install psutil
"""

import os
import sys
import time
from pathlib import Path
from datetime import datetime
import subprocess as sp

if os.name != 'posix':
sys.exit(f'{os.name} platform is not supported')

from demo_opts import get_device
from luma.core.render import canvas
from PIL import ImageFont

try:
import psutil
except ImportError:
print("The psutil library was not found. Run 'sudo -H pip install psutil' to install it.")
sys.exit()

# TODO: custom font bitmaps for up/down arrows
# TODO: Load histogram

def bytes2human(n):
"""
>>> bytes2human(10000)
'9K'
>>> bytes2human(100001221)
'95M'
"""
symbols = ('K', 'M', 'G', 'T', 'P', 'E', 'Z', 'Y')
prefix = {}
for i, s in enumerate(symbols):
prefix[s] = 1 << (i + 1) * 10
for s in reversed(symbols):
if n >= prefix[s]:
value = int(float(n) / prefix[s])
return '%s%s' % (value, s)
return f"{n}B"

def cpu_usage():
# load average, uptime
uptime = datetime.now() - datetime.fromtimestamp(psutil.boot_time())
#av1, av2, av3 = os.getloadavg()
#return "Ld:%.1f %.1f %.1f Up: %s" \
# % (av1, av2, av3, str(uptime).split('.')[0])
return "Up: %s" % (str(uptime).split('.')[0])

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi

def stats(device):
# use custom font
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
#font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'DejaVuSansMono.ttf'))
font2 = ImageFont.truetype(font_path, 15)

with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white")
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white")

if device.height >= 64:
draw.text((0, 26), disk_usage('/'), font=font2, fill="white")
try:
draw.text((0, 38), network('wlan0'), font=font2, fill="white")
except KeyError:
# no wifi enabled/available
pass

def main():
while True:
stats(device)
time.sleep(5)

if __name__ == "__main__":
try:
device = get_device()
main()
except KeyboardInterrupt:
pass
</pre>
Here let me explain to you what i did.
* adding " import subprocess as sp", this will help me to execute some shell command in OS.
* adding following parts:
<pre>
def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi
</pre>
* get_ip_address will execute the command "hostname -I" in system and grab the IP address and return it to main process.
* get_id is to read /proc/cpuinfo file and grab the serial number and return to main process.

===Use custom font===
<pre>
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
font2 = ImageFont.truetype(font_path, 15) # change font size to 15.
</pre>
===Modify the draw function===
<pre>
with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white") #####　draw id on screen at (0,0) position, (x,y)
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white") ####　draw text on (0,16) with IP address.
</pre>

==How to create a systemd file to make it automatically start at boot up==
* Step1. create a shell script called it 'start_led.sh'
<pre>
#!/bin/bash
#
cd /home/pi/venv/ && source /home/pi/venv/bin/activate
/usr/bin/python3 /home/pi/luma.examples/examples/sys_info.py --width=128 --height=32 -r 2
</pre>
save it and grant executable permission and test it.
<pre>
chmod +x start_led.sh
./start_led.sh
</pre>
If if works properly, just press "ctrol+c" to abort the test.
* Step2. create a systemd file and enable it.
<pre>
sudo vim.tiny /etc/systemd/system/rackmount_oled.service
</pre>
And then, adding following lines:
<pre>
[Unit]
Description=Rackmount OLED service on RPi5
DefaultDependencies=no
StartLimitIntervalSec=60
StartLimitBurst=5

[Service]
Type=simple
ExecStart=/bin/bash /home/pi/start_led.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
</pre>
Save it and quit.
===Enable rackmount_oled.service===
* reload daemon
<pre>
sudo systemctl daemon-reload
</pre>

* Enable service
<pre>
sudo systemctl enable rackmount_oled.service
</pre>
* Start service
<pre>
sudo systemctl start rackmount_oled.service
</pre>
* Restart service
<pre>
sudo systemctl restart rackmount_oled.service
</pre>
* Stop service
<pre>
sudo systemctl stop rackmount_oled.service
</pre>
* Disable service
<pre>
sudo systemctl disable rackmount_oled.service
</pre>

==How to enable PCIe function on Raspberry Pi 5?==
* To enable PCIe functionality on the Raspberry Pi 5, follow these steps:

===1. Enable the PCIe External Connector:===
By default, the PCIe connector on the Raspberry Pi 5 is not enabled. To enable it, you need to add a configuration parameter to the `config.txt` file located in the `/boot/firmware` directory. You can use either of these lines:
<pre>
dtparam=pciex1
</pre>
After adding the line, reboot your Raspberry Pi for the changes to take effect.

===2.Enable PCIe Gen 3.0 (Optional):===
The Raspberry Pi 5's PCIe connection is certified for Gen 2.0 speeds. However, if you want to attempt using Gen 3.0 speeds, add the following line to the `config.txt` file as well:
<pre>
dtparam=pciex1_gen=3
</pre>
Be aware that the Raspberry Pi 5 is not certified for Gen 3.0 speeds, and using this setting may result in instability .

===3.Booting from PCIe:===
If you intend to boot from a device connected via PCIe, such as an NVMe SSD, you will need to modify the boot order in the EEPROM. Use the following command to edit the EEPROM configuration:
<pre>
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-config --edit
</pre>
Then, change the `BOOT_ORDER` line to include NVMe in the boot order:
<pre>
BOOT_ORDER=0xf416
</pre>
This setting will make the Raspberry Pi attempt to boot from an NVMe device connected to the PCIe port .
===4. Kernel Compilation (Advanced):===
If you need to compile the kernel to add support for specific PCIe devices, you can follow the steps outlined in the Raspberry Pi documentation. This involves cloning the Raspberry Pi kernel repository, configuring the kernel with `make menuconfig`, and enabling the necessary modules for your devices .
Remember to always check the compatibility of the devices you intend to use with the Raspberry Pi 5's PCIe interface, as not all devices may be supported out of the box.

==How to light up identical LED? ==
To light up UID LED indicator on a Raspberry Pi 5, you'll make sure the GPIO Pin of the UID LED connected to.
<pre>
GPIO (General Purpose Input/Output) pins on the Raspberry Pi.
</pre>

===Steps===
* 1. Identify GPIO Pins: <font color=red>GPIO4</font><br>

* 2. Power On:
Make sure your Raspberry Pi is powered off before connecting the LED. Once everything is connected, you can power on your Raspberry Pi.

* 3. Software Setup:
You'll need to write a small program to turn the GPIO pin on and off to control the LED. You can use Python with the `gpiozero` library or `RPi.GPIO` library to control the GPIO pins.

===Example Python Code with gpiozero:===
<pre>
from gpiozero import LED
from time import sleep

led = LED('GPIO4')

while True:
led.on()
sleep(1)
led.off()
sleep(1)
</pre>

===Example Python Code with RPi.GPIO:===
<pre>
import RPi.GPIO as GPIO
import time

# Set the GPIO mode
GPIO.setmode(GPIO.BCM)

GPIO_PIN = 4

# Set up the GPIO pin as an output channel
GPIO.setup(GPIO_PIN, GPIO.OUT)

while True:
GPIO.output(GPIO_PIN, GPIO.HIGH) # Turn on the LED
time.sleep(1)
GPIO.output(GPIO_PIN, GPIO.LOW) # Turn off the LED
time.sleep(1)

# Clean up the GPIO pins before exiting the program
GPIO.cleanup()
</pre>

===Safety Tips:===
* Be careful not to short any pins on the Raspberry Pi.

==FAQ==
=== SSD1306 OLED Black-Screen Debugging Report & Operation Guide===

<strong>Target hardware:</strong> 0.91" OLED, 128×32 px, SSD1306, I2C, address 0x3C, Raspberry Pi 5
<strong>Software:</strong> luma.oled 3.15.0, luma.core 2.6.0, Python 3.13, smbus2

=== 1. Executive Summary — What Was Actually Wrong ===

<strong>Nothing was wrong with the code, the luma library, or the SSD1306 register configuration.</strong>
No library or example source code was modified. The failures came from hardware and
configuration, in one layers:

<strong>A parameter mismatch in the examples.</strong> The examples in this directory default to
`ssd1305 / 128×64`; this panel is `ssd1306 / 128×32`. Running without parameters
produces a black or garbled screen. The fix is to pass the correct display, interface,
geometry and address — done via the config file `ssd1306_128x32.conf`.

* ssd1306_128x32.conf contents:
<pre>
--display=ssd1306
--interface=i2c
--i2c-port=1
--i2c-address=0x3c
--width=128
--height=32
</pre>
Put this configuration file to your demo code location:
[[ File:Democodeconfig.png|left| 800px ]]
<br style="clear:both;">
* How to execute with config file
<pre>
sudo python3 demo.py -f ssd1306_128x32.conf
</pre>

=== 2. What Was Done, Step by Step (Method and Basis)===

{| class="wikitable"
|+ Diagnosis — locating the fault
! Method !! Basis / Reasoning
|-
| Bus scan with <code>i2cdetect</code> || An ACK at 0x3C proves all four wires
(VCC/GND/SDA/SCL) are connected and the driver IC is powered
|-
| Source inspection of ssd1306 in luma.oled 3.15.0 || The 128×32 init sequence
(multiplex 0x1F, compins 0x02, charge pump 0x14) matches the datasheet standard — a
register-level bug was ruled out on evidence
|-
| Raw-register write of 0xA5 (force all-on) || This command bypasses GDDRAM; a
healthy panel must glow. No light = fault in the high-voltage path (charge pump /
panel / flex cable)
|-
| Status-register read before/after DISPLAY ON/OFF commands || Per the SSD1306
datasheet, bit 6 is the display ON/OFF flag. It flipped correctly, proving the chip
executes commands — fault isolated to the panel side
|-
| 5 consecutive bus scans + 10 consecutive status reads || All values stable and
identical — ruled out loose wiring and parasitic power
|}

===3. Files Created / Modified===

{| class="wikitable"
|+ Fixes and deliverables
! File !! Type !! Description
|-
| <code>ssd1306_128x32.conf</code> || Fixed || Initially written in INI format,
causing "unrecognized arguments". Based on the source of
<code>luma.core.cmdline.load_config</code> (reads line by line, no whitespace
splitting), rewritten as one <code>--key=value</code> per line; demo.py then ran
successfully
|}

No files in luma.oled / luma.core or the example scripts were modified.

===4. Final Working Configuration===

* Module: bare 0.91" 128×32 SSD1306, <strong>no onboard regulator</strong>
* Wiring: VCC → <strong>3.3 V</strong> (pin 1), GND → GND, SDA → GPIO2 (pin 3), SCL → GPIO3 (pin 5)
* No RST/RES connection needed (I2C interface)
* I2C address: `0x3C`

=== 5. Operating Instructions===

==== Run any luma example in this directory====

<pre>
python demo.py -f ssd1306_128x32.conf
python clock.py -f ssd1306_128x32.conf
python pi_logo.py -f ssd1306_128x32.conf
</pre>

Or pass parameters explicitly:

<pre>
python demo.py -d ssd1306 -i i2c --i2c-port 1 --i2c-address 0x3c --width 128 --height 32
</pre>

=== Minimal code (luma)===

<pre>
from luma.core.interface.serial import i2c
from luma.oled.device import ssd1306
from luma.core.render import canvas

device = ssd1306(i2c(port=1, address=0x3C), width=128, height=32)
with canvas(device) as draw:
draw.rectangle(device.bounding_box, outline="white")
draw.text((4, 10), "OK 128x32", fill="white")
</pre>

===6. Black-Screen Decision Tree (for future modules)===

* `i2cdetect -y 1` shows the address?
<strong>No</strong> → power/wiring fault: measure VCC-GND **at the module's solder pads**, check SDA=pin 3, SCL=pin 5, try fresh dupont wires.
<strong>Yes</strong> → continue.

* Run `python oled_diagnose.py`. Any step lights the panel?
<strong>Yes</strong> → software/parameter issue; use the matching parameters (`-d ssd1306 --width 128 --height 32 --i2c-address 0x3c`).
<strong>No</strong> → continue.

==Keywords==
* 1U Rackmount for Raspberry Pi 5 with M.2 NVMe SSD support.

DR-0001

2026-08-21T06:15:46Z

Yoyojacky: /* Run the library-free raw driver */

==1U Rackmount for Raspberry Pi 5 ==
* Purchase URL: [ https://52pi.com ] or [ https://deskpi.com ]
[[File:DR-0001-1.jpg|right|320px]]

==Description==
This is an upgraded version of a 1U Rackmount designed for compatibility with both Raspberry Pi 5 . It features a motherboard that supports PCIe expansion, allowing the PCIe interface of the Raspberry Pi 5 to be extended to accommodate an M.2 NVMe SSD in 2230/2242/2260/2280 form factors. The expansion board also routes the Raspberry Pi's 5V and GND, SDA, and SCL pins to the rear through PogoPin connectors, providing I2C interface peripherals in a Grove format. Additionally, a red LED is included on the board for the Raspberry Pi ID signal pin, which can be programmed to indicate the current device by controlling the GPIO4 pin's high or low level, acting as a programmable device ID signal light.

The Rackmount supports the connection of up to five Raspberry Pi devices and can also be configured with an OLED display frame in place of one of the Raspberry Pi slots. These components can be easily adjusted and removed due to the use of hand-tightened screws. The OLED display features a 0.91-inch screen and communicates with the Raspberry Pi via I2C protocol, displaying real-time information such as CPU status, memory status, IP information, and serial numbers. The content displayed on the OLED can be fully customized.
==Features==
* <strong>Compatibility:</strong> Designed to work with both Raspberry Pi 5.
* <strong>PCIe Expansion Support:</strong> Includes a motherboard that enables PCIe expansion, allowing the connection of M.2 NVMe SSDs in various form factors (2230/2242/2260/2280).
* <strong>I2C Interface: </strong> The board routes the Raspberry Pi's 5V, GND, SDA, and SCL pins to the rear through PogoPin connectors, offering I2C interface peripherals in a Grove format.
* <strong>Programmable LED Indicator: </strong> A red LED on the board serves as a programmable device ID signal, controllable via the GPIO4 pin to indicate the status or identity of the device.
* <strong>Modular Design:</strong> Supports the integration of up to five Raspberry Pi devices, with the option to replace one slot with an OLED display frame.
* <strong>OLED Display Integration:</strong> The option to include a 0.91-inch OLED screen that communicates with the Raspberry Pi via I2C, displaying customizable information such as CPU usage, memory status, IP address, and serial numbers.
* <strong>Easy Assembly and Disassembly:</strong> Components are secured with hand-tightened screws, allowing for convenient adjustments and removal.
* <strong>Customizable Display Content: </strong> The information displayed on the OLED screen can be fully customized to meet specific needs or preferences.
* <strong>Rackmount Form Factor: </strong> Designed to fit into a 1U rack space, making it suitable for data centers or other environments where space is at a premium.
* <strong>Versatility:</strong> The Rackmount can be configured in various ways to suit different use cases, whether for development, testing, or deployment in a production environment.
===Specifications===
* Form Factor: 1U Rackmount design suitable for standard 19-inch racks.
* Raspberry Pi Compatibility: Specifically designed for Raspberry Pi 5.
* PCIe Expansion:Supports M.2 NVMe SSDs in 2230, 2242, 2260, and 2280 form factors. Provides a PCIe interface for high-speed data transfer.
* I/O Connectivity: Rear I2C interface via PogoPin connectors for external peripherals.
* GPIO4 pin for programmable LED control.
* LED Indicator:Red LED for device identification or status indication. Programmable through software to show different statuses.
* Modular Bays: Five bays for Raspberry Pi devices. One bay can be replaced with an OLED display module.
* OLED Display Specifications:0.91-inch screen size, 128x32 pixels. I2C communication protocol.
* Customizable display for system information.
* Physical Security:Hand-tightened screws for secure mounting of Raspberry Pi devices and OLED display.
* Ensures stability and ease of maintenance.
* Power Requirements: Compatibility with Raspberry Pi's standard power supply.
* Material and Construction: Durable metal construction for the rackmount chassis. High-quality components for reliable performance.
* Mounting Options: Standard rackmount holes for easy installation into a rack.
* Includes additional mounting accessories for different setups.
* Software Compatibility: Compatible with Raspberry Pi's operating system and software ecosystem.
* Support for GPIO programming for custom LED and device control.
==Gallery==
* Product outlook
[[ File:DR-0001-6.jpg |left|800px]]
<br style="clear:both":>

* Application Senario
[[ File:DR-0001-2.jpg |left|800px]]
<br style="clear:both":>
<font color=red> NOTE: Raspberry Pis are not included in the package, additional purchase required!</font><br>
* Easy to assemble and maintain
[[ File:DR-0001-3.jpg |left|800px]]
<br style="clear:both":>
[[File:DR-0001-12.jpg|left|800px]]
<br style="clear:both":>

* Customizable OLED display screen, with a size of 0.91 inches
[[ File:DR-0001-4.jpg |left|800px]]
<br style="clear:both":>

* Ports Definitions and Featrues
Programmable I/O controlled UID indicator light, which can be programmed to control the LED blinking to indicate the device's location, facilitating faster troubleshooting and easier maintenance operations.
[[ File:DR-0001-5.jpg |left|800px]]
<br style="clear:both":>

===How to connect OLED display to Raspberry Pi on GPIO pins===
* Please refer to following figure to connect OLED display to Raspberry Pi on GPIO.
<font color=red>NOTE: OLED's VCC should be connected to 3.3V power rail, Do not connect it to 5V power rail!!!</font><br>
[[ File:DR-0001-7.jpg |left|800px]]
<br style="clear:both":>

* Grove Connector Support I2C and Uart
[[ File:DR-0001-8.jpg |left|800px]]
<br style="clear:both":>

* Accessories Dimension
[[ File:DR-0001-9.jpg |left|800px]]
<br style="clear:both":>

* OLED assemble details
Please remove the protection film from acrylic panel and use the washer between OLED PCB board and acrylic panel.
[[ File:DR-0001-10.jpg |left|800px]]
<br style="clear:both":>

* PCIe Expansion board for Raspberry Pi 5 only
The expansion board supports M.2 NVMe M-key SSD 2230/2242/2260/2280, and the board will be powered by Raspberry Pi 5 via PogoPin on the PCB board, please make sure the board's pogoins are contact well with the soldering point on back of the Raspberry Pi 5 on GPIO pins.
[[File:DR-0001-11.jpg|left|800px]]
<br style="clear:both":>

==How to assemble it? ==
* Please note that there are several details you need to pay attention, plesae check out following figure.
[[ File:DR-0001-安装.jpg|left|800px]]
<br style="clear:both";>

==Package Includes==
* Following figure shows the details of the product:
[[ File:DR-0001-清单.jpg|left|800px]]
<br style="clear:both";>

==How to enable I2C OLED display?==
* We assume that you are using Raspberry Pi OS 64bit(bookworm, the latest official image)
To enable I2C and UART on your Raspberry Pi, you can follow these detailed steps:

===Enabling I2C===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
to open the configuration tool. Navigate to `Interface Options`, Select `I2C` and enable it.

* Method 2. Using the Command Line:
You can also enable I2C by editing the `/boot/firmware/config.txt` file and adding `dtparam=i2c_arm=on` if it's not already present, After making changes, reboot your Pi.

===Verifying I2C===
* Install I2C tools using `sudo apt-get install -y i2c-tools`.
* Use
<pre>
i2cdetect -y 1
</pre>
to scan for I2C devices, if you see `3c` means that the OLED display has been recognized by your Raspberry Pi.

===Enabling UART===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
Go to `Interface Options`, Select `Serial` and enable it.
<pre> Note: This will also enable the login shell on the serial port. </pre>

* Method 2. Using the Command Line:
Edit `/boot/config.txt` and add `enable_uart=1`, save it and then reboot your Pi.

===Accessing UART===
* Connect your Pi to a USB-to-TTL converter, On Windows, you may need to install drivers for the converter. on Linux just use a terminal program like `minicom`, `putty`, or `screen` to access the UART interface.

Remember to check the documentation for your specific Raspberry Pi model, as the steps might vary slightly. If you need more detailed instructions or encounter any issues, refer to the [ https://www.raspberrypi.org/documentation/ ] or community forums for additional support.

===How to display customized information on OLED display? ===
* Final result
[[File:DR-0001 applications-01.jpg|left|800px]]
<br style="clear:both";>
==How to customize content on OLED ?==
* For example: If you want to display current IP address of wlan interface and the serial number of your Raspberry Pi 5, please follow next steps to configure it.
===Install Virtal environment package ===
* Open a terminal and typing following commands:
<pre>
sudo apt update
sudo apt upgrade -y
sudo apt -y install virtualenv
sudo usermod -a -G i2c,spi,gpio pi
sudo apt install python3-dev python3-pip python3-numpy libfreetype6-dev libjpeg-dev build-essential
sudo apt install libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libportmidi-dev
</pre>
[[File:Install pre-insistpackages.png|left|800px]]
<br style="clear:both";>
[[File:Install-pre-insistpackage-02.png|left|800px]]
<br style="clear:both";>

===Create virtual environment===
<pre>
virtualenv -p python3 venv
cd venv/
source bin/activate
</pre>
===Install SSD1306 driver and library for OLED 0.91===
<pre>
pip install luma.oled
pip install psutil
</pre>

===Clone luma.examples repository===
Log out and in again and clone this repository:
<pre>
git clone https://github.com/rm-hull/luma.examples.git
cd luma.examples/
</pre>
===Install luma libraries===
<pre>
sudo -H pip install -e . --break-system-packages
</pre>
[[File:Install luma libraries.png|left|800px]]
<br style="clear:both";>
===Test the demo ===
<pre>
cd examples/
sudo python 3d_box.py --width=128 --height=32 -r 2
</pre>

<font color=red><p>NOTE: <br>
--width=128 and --height=32 should be added to declear the OLED's resolution information. <br>
-r 2 means --rotate 2 , Allowed values are: 0, 1, 2, 3 (default:0)
</p>
</font>
If you see a 3D-box rotating animation is in the middle of screen means that you have installed the OLED driver successfully!
[[File:Test demo 3dbox.png|left|800px]]
<br style="clear:both";>
[[File:Test demo 3dbox-2.png|left|800px]]
<br style="clear:both";>
and then press "Ctrol+C" abort the demo.

==Use the demo code==
* There are a lot of demo codes in the examples folder, you can test it as you want.
for example:
<pre>
sudo python carousel.py --width=128 --height=32 -r 2
</pre>
It will display all information of your Raspberry Pi 5 and scrolling display.
===Customize the display on screen===
Modify the sys_info.py python file and adding your own function to show the information you want, do remember backup the origin file.
<pre>
cp sys_info.py sys_info.py.bak
vim.tiny sys_info.py
</pre>
Press 'i' to insert mode, and paste following lines into it. you can modify this file by other text editor what you like.
<pre>
#!/usr/bin/env python
# -*- coding: utf-8 -*-
# Copyright (c) 2014-2022 Richard Hull and contributors
# See LICENSE.rst for details.
# PYTHON_ARGCOMPLETE_OK

"""
Display basic system information.

Needs psutil (+ dependencies) installed::

$ sudo apt-get install python-dev
$ sudo -H pip install psutil
"""

import os
import sys
import time
from pathlib import Path
from datetime import datetime
import subprocess as sp

if os.name != 'posix':
sys.exit(f'{os.name} platform is not supported')

from demo_opts import get_device
from luma.core.render import canvas
from PIL import ImageFont

try:
import psutil
except ImportError:
print("The psutil library was not found. Run 'sudo -H pip install psutil' to install it.")
sys.exit()

# TODO: custom font bitmaps for up/down arrows
# TODO: Load histogram

def bytes2human(n):
"""
>>> bytes2human(10000)
'9K'
>>> bytes2human(100001221)
'95M'
"""
symbols = ('K', 'M', 'G', 'T', 'P', 'E', 'Z', 'Y')
prefix = {}
for i, s in enumerate(symbols):
prefix[s] = 1 << (i + 1) * 10
for s in reversed(symbols):
if n >= prefix[s]:
value = int(float(n) / prefix[s])
return '%s%s' % (value, s)
return f"{n}B"

def cpu_usage():
# load average, uptime
uptime = datetime.now() - datetime.fromtimestamp(psutil.boot_time())
#av1, av2, av3 = os.getloadavg()
#return "Ld:%.1f %.1f %.1f Up: %s" \
# % (av1, av2, av3, str(uptime).split('.')[0])
return "Up: %s" % (str(uptime).split('.')[0])

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi

def stats(device):
# use custom font
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
#font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'DejaVuSansMono.ttf'))
font2 = ImageFont.truetype(font_path, 15)

with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white")
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white")

if device.height >= 64:
draw.text((0, 26), disk_usage('/'), font=font2, fill="white")
try:
draw.text((0, 38), network('wlan0'), font=font2, fill="white")
except KeyError:
# no wifi enabled/available
pass

def main():
while True:
stats(device)
time.sleep(5)

if __name__ == "__main__":
try:
device = get_device()
main()
except KeyboardInterrupt:
pass
</pre>
Here let me explain to you what i did.
* adding " import subprocess as sp", this will help me to execute some shell command in OS.
* adding following parts:
<pre>
def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi
</pre>
* get_ip_address will execute the command "hostname -I" in system and grab the IP address and return it to main process.
* get_id is to read /proc/cpuinfo file and grab the serial number and return to main process.

===Use custom font===
<pre>
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
font2 = ImageFont.truetype(font_path, 15) # change font size to 15.
</pre>
===Modify the draw function===
<pre>
with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white") #####　draw id on screen at (0,0) position, (x,y)
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white") ####　draw text on (0,16) with IP address.
</pre>

==How to create a systemd file to make it automatically start at boot up==
* Step1. create a shell script called it 'start_led.sh'
<pre>
#!/bin/bash
#
cd /home/pi/venv/ && source /home/pi/venv/bin/activate
/usr/bin/python3 /home/pi/luma.examples/examples/sys_info.py --width=128 --height=32 -r 2
</pre>
save it and grant executable permission and test it.
<pre>
chmod +x start_led.sh
./start_led.sh
</pre>
If if works properly, just press "ctrol+c" to abort the test.
* Step2. create a systemd file and enable it.
<pre>
sudo vim.tiny /etc/systemd/system/rackmount_oled.service
</pre>
And then, adding following lines:
<pre>
[Unit]
Description=Rackmount OLED service on RPi5
DefaultDependencies=no
StartLimitIntervalSec=60
StartLimitBurst=5

[Service]
Type=simple
ExecStart=/bin/bash /home/pi/start_led.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
</pre>
Save it and quit.
===Enable rackmount_oled.service===
* reload daemon
<pre>
sudo systemctl daemon-reload
</pre>

* Enable service
<pre>
sudo systemctl enable rackmount_oled.service
</pre>
* Start service
<pre>
sudo systemctl start rackmount_oled.service
</pre>
* Restart service
<pre>
sudo systemctl restart rackmount_oled.service
</pre>
* Stop service
<pre>
sudo systemctl stop rackmount_oled.service
</pre>
* Disable service
<pre>
sudo systemctl disable rackmount_oled.service
</pre>

==How to enable PCIe function on Raspberry Pi 5?==
* To enable PCIe functionality on the Raspberry Pi 5, follow these steps:

===1. Enable the PCIe External Connector:===
By default, the PCIe connector on the Raspberry Pi 5 is not enabled. To enable it, you need to add a configuration parameter to the `config.txt` file located in the `/boot/firmware` directory. You can use either of these lines:
<pre>
dtparam=pciex1
</pre>
After adding the line, reboot your Raspberry Pi for the changes to take effect.

===2.Enable PCIe Gen 3.0 (Optional):===
The Raspberry Pi 5's PCIe connection is certified for Gen 2.0 speeds. However, if you want to attempt using Gen 3.0 speeds, add the following line to the `config.txt` file as well:
<pre>
dtparam=pciex1_gen=3
</pre>
Be aware that the Raspberry Pi 5 is not certified for Gen 3.0 speeds, and using this setting may result in instability .

===3.Booting from PCIe:===
If you intend to boot from a device connected via PCIe, such as an NVMe SSD, you will need to modify the boot order in the EEPROM. Use the following command to edit the EEPROM configuration:
<pre>
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-config --edit
</pre>
Then, change the `BOOT_ORDER` line to include NVMe in the boot order:
<pre>
BOOT_ORDER=0xf416
</pre>
This setting will make the Raspberry Pi attempt to boot from an NVMe device connected to the PCIe port .
===4. Kernel Compilation (Advanced):===
If you need to compile the kernel to add support for specific PCIe devices, you can follow the steps outlined in the Raspberry Pi documentation. This involves cloning the Raspberry Pi kernel repository, configuring the kernel with `make menuconfig`, and enabling the necessary modules for your devices .
Remember to always check the compatibility of the devices you intend to use with the Raspberry Pi 5's PCIe interface, as not all devices may be supported out of the box.

==How to light up identical LED? ==
To light up UID LED indicator on a Raspberry Pi 5, you'll make sure the GPIO Pin of the UID LED connected to.
<pre>
GPIO (General Purpose Input/Output) pins on the Raspberry Pi.
</pre>

===Steps===
* 1. Identify GPIO Pins: <font color=red>GPIO4</font><br>

* 2. Power On:
Make sure your Raspberry Pi is powered off before connecting the LED. Once everything is connected, you can power on your Raspberry Pi.

* 3. Software Setup:
You'll need to write a small program to turn the GPIO pin on and off to control the LED. You can use Python with the `gpiozero` library or `RPi.GPIO` library to control the GPIO pins.

===Example Python Code with gpiozero:===
<pre>
from gpiozero import LED
from time import sleep

led = LED('GPIO4')

while True:
led.on()
sleep(1)
led.off()
sleep(1)
</pre>

===Example Python Code with RPi.GPIO:===
<pre>
import RPi.GPIO as GPIO
import time

# Set the GPIO mode
GPIO.setmode(GPIO.BCM)

GPIO_PIN = 4

# Set up the GPIO pin as an output channel
GPIO.setup(GPIO_PIN, GPIO.OUT)

while True:
GPIO.output(GPIO_PIN, GPIO.HIGH) # Turn on the LED
time.sleep(1)
GPIO.output(GPIO_PIN, GPIO.LOW) # Turn off the LED
time.sleep(1)

# Clean up the GPIO pins before exiting the program
GPIO.cleanup()
</pre>

===Safety Tips:===
* Be careful not to short any pins on the Raspberry Pi.

==FAQ==
=== SSD1306 OLED Black-Screen Debugging Report & Operation Guide===

<strong>Target hardware:</strong> 0.91" OLED, 128×32 px, SSD1306, I2C, address 0x3C, Raspberry Pi 5
<strong>Software:</strong> luma.oled 3.15.0, luma.core 2.6.0, Python 3.13, smbus2

=== 1. Executive Summary — What Was Actually Wrong ===

<strong>Nothing was wrong with the code, the luma library, or the SSD1306 register configuration.</strong>
No library or example source code was modified. The failures came from hardware and
configuration, in one layers:

<strong>A parameter mismatch in the examples.</strong> The examples in this directory default to
`ssd1305 / 128×64`; this panel is `ssd1306 / 128×32`. Running without parameters
produces a black or garbled screen. The fix is to pass the correct display, interface,
geometry and address — done via the config file `ssd1306_128x32.conf`.

* ssd1306_128x32.conf contents:
<pre>
--display=ssd1306
--interface=i2c
--i2c-port=1
--i2c-address=0x3c
--width=128
--height=32
</pre>
Put this configuration file to your demo code location:
[[ File:Democodeconfig.png|left| 800px ]]
<br style="clear:both;">
* How to execute with config file
<pre>
sudo python3 demo.py -f ssd1306_128x32.conf
</pre>

=== 2. What Was Done, Step by Step (Method and Basis)===

{| class="wikitable"
|+ Diagnosis — locating the fault
! Method !! Basis / Reasoning
|-
| Bus scan with <code>i2cdetect</code> || An ACK at 0x3C proves all four wires
(VCC/GND/SDA/SCL) are connected and the driver IC is powered
|-
| Source inspection of ssd1306 in luma.oled 3.15.0 || The 128×32 init sequence
(multiplex 0x1F, compins 0x02, charge pump 0x14) matches the datasheet standard — a
register-level bug was ruled out on evidence
|-
| Raw-register write of 0xA5 (force all-on) || This command bypasses GDDRAM; a
healthy panel must glow. No light = fault in the high-voltage path (charge pump /
panel / flex cable)
|-
| Status-register read before/after DISPLAY ON/OFF commands || Per the SSD1306
datasheet, bit 6 is the display ON/OFF flag. It flipped correctly, proving the chip
executes commands — fault isolated to the panel side
|-
| 5 consecutive bus scans + 10 consecutive status reads || All values stable and
identical — ruled out loose wiring and parasitic power
|}

===3. Files Created / Modified===

{| class="wikitable"
|+ Fixes and deliverables
! File !! Type !! Description
|-
| <code>ssd1306_128x32.conf</code> || Fixed || Initially written in INI format,
causing "unrecognized arguments". Based on the source of
<code>luma.core.cmdline.load_config</code> (reads line by line, no whitespace
splitting), rewritten as one <code>--key=value</code> per line; demo.py then ran
successfully
|-
| <code>ssd1306_raw.py</code> || Created || Library-free SSD1306 driver; writes
registers directly via smbus2 (PIL used only for pixel rendering)
|-
| <code>OLED_128x32_I2C_manual.md</code> || Created / updated || Bilingual
operation manual; added the regulator/supply-voltage rule and the hardware-failure
criterion
|-
| <code>SSD1306_Debug_Report_EN.md</code> || Created || Full English debugging
report and operation guide
|}

No files in luma.oled / luma.core or the example scripts were modified.

===4. Final Working Configuration===

* Module: bare 0.91" 128×32 SSD1306, <strong>no onboard regulator</strong>
* Wiring: VCC → <strong>3.3 V</strong> (pin 1), GND → GND, SDA → GPIO2 (pin 3), SCL → GPIO3 (pin 5)
* No RST/RES connection needed (I2C interface)
* I2C address: `0x3C`

=== 5. Operating Instructions===

==== Run any luma example in this directory====

<pre>
python demo.py -f ssd1306_128x32.conf
python clock.py -f ssd1306_128x32.conf
python pi_logo.py -f ssd1306_128x32.conf
</pre>

Or pass parameters explicitly:

<pre>
python demo.py -d ssd1306 -i i2c --i2c-port 1 --i2c-address 0x3c --width 128 --height 32
</pre>

=== Minimal code (luma)===

<pre>
from luma.core.interface.serial import i2c
from luma.oled.device import ssd1306
from luma.core.render import canvas

device = ssd1306(i2c(port=1, address=0x3C), width=128, height=32)
with canvas(device) as draw:
draw.rectangle(device.bounding_box, outline="white")
draw.text((4, 10), "OK 128x32", fill="white")
</pre>

===6. Black-Screen Decision Tree (for future modules)===

* `i2cdetect -y 1` shows the address?
<strong>No</strong> → power/wiring fault: measure VCC-GND **at the module's solder pads**, check SDA=pin 3, SCL=pin 5, try fresh dupont wires.
<strong>Yes</strong> → continue.

* Run `python oled_diagnose.py`. Any step lights the panel?
<strong>Yes</strong> → software/parameter issue; use the matching parameters (`-d ssd1306 --width 128 --height 32 --i2c-address 0x3c`).
<strong>No</strong> → continue.

==Keywords==
* 1U Rackmount for Raspberry Pi 5 with M.2 NVMe SSD support.

DR-0001

2026-08-21T06:15:07Z

Yoyojacky: /* 6. Black-Screen Decision Tree (for future modules) */

==1U Rackmount for Raspberry Pi 5 ==
* Purchase URL: [ https://52pi.com ] or [ https://deskpi.com ]
[[File:DR-0001-1.jpg|right|320px]]

==Description==
This is an upgraded version of a 1U Rackmount designed for compatibility with both Raspberry Pi 5 . It features a motherboard that supports PCIe expansion, allowing the PCIe interface of the Raspberry Pi 5 to be extended to accommodate an M.2 NVMe SSD in 2230/2242/2260/2280 form factors. The expansion board also routes the Raspberry Pi's 5V and GND, SDA, and SCL pins to the rear through PogoPin connectors, providing I2C interface peripherals in a Grove format. Additionally, a red LED is included on the board for the Raspberry Pi ID signal pin, which can be programmed to indicate the current device by controlling the GPIO4 pin's high or low level, acting as a programmable device ID signal light.

The Rackmount supports the connection of up to five Raspberry Pi devices and can also be configured with an OLED display frame in place of one of the Raspberry Pi slots. These components can be easily adjusted and removed due to the use of hand-tightened screws. The OLED display features a 0.91-inch screen and communicates with the Raspberry Pi via I2C protocol, displaying real-time information such as CPU status, memory status, IP information, and serial numbers. The content displayed on the OLED can be fully customized.
==Features==
* <strong>Compatibility:</strong> Designed to work with both Raspberry Pi 5.
* <strong>PCIe Expansion Support:</strong> Includes a motherboard that enables PCIe expansion, allowing the connection of M.2 NVMe SSDs in various form factors (2230/2242/2260/2280).
* <strong>I2C Interface: </strong> The board routes the Raspberry Pi's 5V, GND, SDA, and SCL pins to the rear through PogoPin connectors, offering I2C interface peripherals in a Grove format.
* <strong>Programmable LED Indicator: </strong> A red LED on the board serves as a programmable device ID signal, controllable via the GPIO4 pin to indicate the status or identity of the device.
* <strong>Modular Design:</strong> Supports the integration of up to five Raspberry Pi devices, with the option to replace one slot with an OLED display frame.
* <strong>OLED Display Integration:</strong> The option to include a 0.91-inch OLED screen that communicates with the Raspberry Pi via I2C, displaying customizable information such as CPU usage, memory status, IP address, and serial numbers.
* <strong>Easy Assembly and Disassembly:</strong> Components are secured with hand-tightened screws, allowing for convenient adjustments and removal.
* <strong>Customizable Display Content: </strong> The information displayed on the OLED screen can be fully customized to meet specific needs or preferences.
* <strong>Rackmount Form Factor: </strong> Designed to fit into a 1U rack space, making it suitable for data centers or other environments where space is at a premium.
* <strong>Versatility:</strong> The Rackmount can be configured in various ways to suit different use cases, whether for development, testing, or deployment in a production environment.
===Specifications===
* Form Factor: 1U Rackmount design suitable for standard 19-inch racks.
* Raspberry Pi Compatibility: Specifically designed for Raspberry Pi 5.
* PCIe Expansion:Supports M.2 NVMe SSDs in 2230, 2242, 2260, and 2280 form factors. Provides a PCIe interface for high-speed data transfer.
* I/O Connectivity: Rear I2C interface via PogoPin connectors for external peripherals.
* GPIO4 pin for programmable LED control.
* LED Indicator:Red LED for device identification or status indication. Programmable through software to show different statuses.
* Modular Bays: Five bays for Raspberry Pi devices. One bay can be replaced with an OLED display module.
* OLED Display Specifications:0.91-inch screen size, 128x32 pixels. I2C communication protocol.
* Customizable display for system information.
* Physical Security:Hand-tightened screws for secure mounting of Raspberry Pi devices and OLED display.
* Ensures stability and ease of maintenance.
* Power Requirements: Compatibility with Raspberry Pi's standard power supply.
* Material and Construction: Durable metal construction for the rackmount chassis. High-quality components for reliable performance.
* Mounting Options: Standard rackmount holes for easy installation into a rack.
* Includes additional mounting accessories for different setups.
* Software Compatibility: Compatible with Raspberry Pi's operating system and software ecosystem.
* Support for GPIO programming for custom LED and device control.
==Gallery==
* Product outlook
[[ File:DR-0001-6.jpg |left|800px]]
<br style="clear:both":>

* Application Senario
[[ File:DR-0001-2.jpg |left|800px]]
<br style="clear:both":>
<font color=red> NOTE: Raspberry Pis are not included in the package, additional purchase required!</font><br>
* Easy to assemble and maintain
[[ File:DR-0001-3.jpg |left|800px]]
<br style="clear:both":>
[[File:DR-0001-12.jpg|left|800px]]
<br style="clear:both":>

* Customizable OLED display screen, with a size of 0.91 inches
[[ File:DR-0001-4.jpg |left|800px]]
<br style="clear:both":>

* Ports Definitions and Featrues
Programmable I/O controlled UID indicator light, which can be programmed to control the LED blinking to indicate the device's location, facilitating faster troubleshooting and easier maintenance operations.
[[ File:DR-0001-5.jpg |left|800px]]
<br style="clear:both":>

===How to connect OLED display to Raspberry Pi on GPIO pins===
* Please refer to following figure to connect OLED display to Raspberry Pi on GPIO.
<font color=red>NOTE: OLED's VCC should be connected to 3.3V power rail, Do not connect it to 5V power rail!!!</font><br>
[[ File:DR-0001-7.jpg |left|800px]]
<br style="clear:both":>

* Grove Connector Support I2C and Uart
[[ File:DR-0001-8.jpg |left|800px]]
<br style="clear:both":>

* Accessories Dimension
[[ File:DR-0001-9.jpg |left|800px]]
<br style="clear:both":>

* OLED assemble details
Please remove the protection film from acrylic panel and use the washer between OLED PCB board and acrylic panel.
[[ File:DR-0001-10.jpg |left|800px]]
<br style="clear:both":>

* PCIe Expansion board for Raspberry Pi 5 only
The expansion board supports M.2 NVMe M-key SSD 2230/2242/2260/2280, and the board will be powered by Raspberry Pi 5 via PogoPin on the PCB board, please make sure the board's pogoins are contact well with the soldering point on back of the Raspberry Pi 5 on GPIO pins.
[[File:DR-0001-11.jpg|left|800px]]
<br style="clear:both":>

==How to assemble it? ==
* Please note that there are several details you need to pay attention, plesae check out following figure.
[[ File:DR-0001-安装.jpg|left|800px]]
<br style="clear:both";>

==Package Includes==
* Following figure shows the details of the product:
[[ File:DR-0001-清单.jpg|left|800px]]
<br style="clear:both";>

==How to enable I2C OLED display?==
* We assume that you are using Raspberry Pi OS 64bit(bookworm, the latest official image)
To enable I2C and UART on your Raspberry Pi, you can follow these detailed steps:

===Enabling I2C===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
to open the configuration tool. Navigate to `Interface Options`, Select `I2C` and enable it.

* Method 2. Using the Command Line:
You can also enable I2C by editing the `/boot/firmware/config.txt` file and adding `dtparam=i2c_arm=on` if it's not already present, After making changes, reboot your Pi.

===Verifying I2C===
* Install I2C tools using `sudo apt-get install -y i2c-tools`.
* Use
<pre>
i2cdetect -y 1
</pre>
to scan for I2C devices, if you see `3c` means that the OLED display has been recognized by your Raspberry Pi.

===Enabling UART===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
Go to `Interface Options`, Select `Serial` and enable it.
<pre> Note: This will also enable the login shell on the serial port. </pre>

* Method 2. Using the Command Line:
Edit `/boot/config.txt` and add `enable_uart=1`, save it and then reboot your Pi.

===Accessing UART===
* Connect your Pi to a USB-to-TTL converter, On Windows, you may need to install drivers for the converter. on Linux just use a terminal program like `minicom`, `putty`, or `screen` to access the UART interface.

Remember to check the documentation for your specific Raspberry Pi model, as the steps might vary slightly. If you need more detailed instructions or encounter any issues, refer to the [ https://www.raspberrypi.org/documentation/ ] or community forums for additional support.

===How to display customized information on OLED display? ===
* Final result
[[File:DR-0001 applications-01.jpg|left|800px]]
<br style="clear:both";>
==How to customize content on OLED ?==
* For example: If you want to display current IP address of wlan interface and the serial number of your Raspberry Pi 5, please follow next steps to configure it.
===Install Virtal environment package ===
* Open a terminal and typing following commands:
<pre>
sudo apt update
sudo apt upgrade -y
sudo apt -y install virtualenv
sudo usermod -a -G i2c,spi,gpio pi
sudo apt install python3-dev python3-pip python3-numpy libfreetype6-dev libjpeg-dev build-essential
sudo apt install libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libportmidi-dev
</pre>
[[File:Install pre-insistpackages.png|left|800px]]
<br style="clear:both";>
[[File:Install-pre-insistpackage-02.png|left|800px]]
<br style="clear:both";>

===Create virtual environment===
<pre>
virtualenv -p python3 venv
cd venv/
source bin/activate
</pre>
===Install SSD1306 driver and library for OLED 0.91===
<pre>
pip install luma.oled
pip install psutil
</pre>

===Clone luma.examples repository===
Log out and in again and clone this repository:
<pre>
git clone https://github.com/rm-hull/luma.examples.git
cd luma.examples/
</pre>
===Install luma libraries===
<pre>
sudo -H pip install -e . --break-system-packages
</pre>
[[File:Install luma libraries.png|left|800px]]
<br style="clear:both";>
===Test the demo ===
<pre>
cd examples/
sudo python 3d_box.py --width=128 --height=32 -r 2
</pre>

<font color=red><p>NOTE: <br>
--width=128 and --height=32 should be added to declear the OLED's resolution information. <br>
-r 2 means --rotate 2 , Allowed values are: 0, 1, 2, 3 (default:0)
</p>
</font>
If you see a 3D-box rotating animation is in the middle of screen means that you have installed the OLED driver successfully!
[[File:Test demo 3dbox.png|left|800px]]
<br style="clear:both";>
[[File:Test demo 3dbox-2.png|left|800px]]
<br style="clear:both";>
and then press "Ctrol+C" abort the demo.

==Use the demo code==
* There are a lot of demo codes in the examples folder, you can test it as you want.
for example:
<pre>
sudo python carousel.py --width=128 --height=32 -r 2
</pre>
It will display all information of your Raspberry Pi 5 and scrolling display.
===Customize the display on screen===
Modify the sys_info.py python file and adding your own function to show the information you want, do remember backup the origin file.
<pre>
cp sys_info.py sys_info.py.bak
vim.tiny sys_info.py
</pre>
Press 'i' to insert mode, and paste following lines into it. you can modify this file by other text editor what you like.
<pre>
#!/usr/bin/env python
# -*- coding: utf-8 -*-
# Copyright (c) 2014-2022 Richard Hull and contributors
# See LICENSE.rst for details.
# PYTHON_ARGCOMPLETE_OK

"""
Display basic system information.

Needs psutil (+ dependencies) installed::

$ sudo apt-get install python-dev
$ sudo -H pip install psutil
"""

import os
import sys
import time
from pathlib import Path
from datetime import datetime
import subprocess as sp

if os.name != 'posix':
sys.exit(f'{os.name} platform is not supported')

from demo_opts import get_device
from luma.core.render import canvas
from PIL import ImageFont

try:
import psutil
except ImportError:
print("The psutil library was not found. Run 'sudo -H pip install psutil' to install it.")
sys.exit()

# TODO: custom font bitmaps for up/down arrows
# TODO: Load histogram

def bytes2human(n):
"""
>>> bytes2human(10000)
'9K'
>>> bytes2human(100001221)
'95M'
"""
symbols = ('K', 'M', 'G', 'T', 'P', 'E', 'Z', 'Y')
prefix = {}
for i, s in enumerate(symbols):
prefix[s] = 1 << (i + 1) * 10
for s in reversed(symbols):
if n >= prefix[s]:
value = int(float(n) / prefix[s])
return '%s%s' % (value, s)
return f"{n}B"

def cpu_usage():
# load average, uptime
uptime = datetime.now() - datetime.fromtimestamp(psutil.boot_time())
#av1, av2, av3 = os.getloadavg()
#return "Ld:%.1f %.1f %.1f Up: %s" \
# % (av1, av2, av3, str(uptime).split('.')[0])
return "Up: %s" % (str(uptime).split('.')[0])

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi

def stats(device):
# use custom font
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
#font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'DejaVuSansMono.ttf'))
font2 = ImageFont.truetype(font_path, 15)

with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white")
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white")

if device.height >= 64:
draw.text((0, 26), disk_usage('/'), font=font2, fill="white")
try:
draw.text((0, 38), network('wlan0'), font=font2, fill="white")
except KeyError:
# no wifi enabled/available
pass

def main():
while True:
stats(device)
time.sleep(5)

if __name__ == "__main__":
try:
device = get_device()
main()
except KeyboardInterrupt:
pass
</pre>
Here let me explain to you what i did.
* adding " import subprocess as sp", this will help me to execute some shell command in OS.
* adding following parts:
<pre>
def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi
</pre>
* get_ip_address will execute the command "hostname -I" in system and grab the IP address and return it to main process.
* get_id is to read /proc/cpuinfo file and grab the serial number and return to main process.

===Use custom font===
<pre>
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
font2 = ImageFont.truetype(font_path, 15) # change font size to 15.
</pre>
===Modify the draw function===
<pre>
with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white") #####　draw id on screen at (0,0) position, (x,y)
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white") ####　draw text on (0,16) with IP address.
</pre>

==How to create a systemd file to make it automatically start at boot up==
* Step1. create a shell script called it 'start_led.sh'
<pre>
#!/bin/bash
#
cd /home/pi/venv/ && source /home/pi/venv/bin/activate
/usr/bin/python3 /home/pi/luma.examples/examples/sys_info.py --width=128 --height=32 -r 2
</pre>
save it and grant executable permission and test it.
<pre>
chmod +x start_led.sh
./start_led.sh
</pre>
If if works properly, just press "ctrol+c" to abort the test.
* Step2. create a systemd file and enable it.
<pre>
sudo vim.tiny /etc/systemd/system/rackmount_oled.service
</pre>
And then, adding following lines:
<pre>
[Unit]
Description=Rackmount OLED service on RPi5
DefaultDependencies=no
StartLimitIntervalSec=60
StartLimitBurst=5

[Service]
Type=simple
ExecStart=/bin/bash /home/pi/start_led.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
</pre>
Save it and quit.
===Enable rackmount_oled.service===
* reload daemon
<pre>
sudo systemctl daemon-reload
</pre>

* Enable service
<pre>
sudo systemctl enable rackmount_oled.service
</pre>
* Start service
<pre>
sudo systemctl start rackmount_oled.service
</pre>
* Restart service
<pre>
sudo systemctl restart rackmount_oled.service
</pre>
* Stop service
<pre>
sudo systemctl stop rackmount_oled.service
</pre>
* Disable service
<pre>
sudo systemctl disable rackmount_oled.service
</pre>

==How to enable PCIe function on Raspberry Pi 5?==
* To enable PCIe functionality on the Raspberry Pi 5, follow these steps:

===1. Enable the PCIe External Connector:===
By default, the PCIe connector on the Raspberry Pi 5 is not enabled. To enable it, you need to add a configuration parameter to the `config.txt` file located in the `/boot/firmware` directory. You can use either of these lines:
<pre>
dtparam=pciex1
</pre>
After adding the line, reboot your Raspberry Pi for the changes to take effect.

===2.Enable PCIe Gen 3.0 (Optional):===
The Raspberry Pi 5's PCIe connection is certified for Gen 2.0 speeds. However, if you want to attempt using Gen 3.0 speeds, add the following line to the `config.txt` file as well:
<pre>
dtparam=pciex1_gen=3
</pre>
Be aware that the Raspberry Pi 5 is not certified for Gen 3.0 speeds, and using this setting may result in instability .

===3.Booting from PCIe:===
If you intend to boot from a device connected via PCIe, such as an NVMe SSD, you will need to modify the boot order in the EEPROM. Use the following command to edit the EEPROM configuration:
<pre>
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-config --edit
</pre>
Then, change the `BOOT_ORDER` line to include NVMe in the boot order:
<pre>
BOOT_ORDER=0xf416
</pre>
This setting will make the Raspberry Pi attempt to boot from an NVMe device connected to the PCIe port .
===4. Kernel Compilation (Advanced):===
If you need to compile the kernel to add support for specific PCIe devices, you can follow the steps outlined in the Raspberry Pi documentation. This involves cloning the Raspberry Pi kernel repository, configuring the kernel with `make menuconfig`, and enabling the necessary modules for your devices .
Remember to always check the compatibility of the devices you intend to use with the Raspberry Pi 5's PCIe interface, as not all devices may be supported out of the box.

==How to light up identical LED? ==
To light up UID LED indicator on a Raspberry Pi 5, you'll make sure the GPIO Pin of the UID LED connected to.
<pre>
GPIO (General Purpose Input/Output) pins on the Raspberry Pi.
</pre>

===Steps===
* 1. Identify GPIO Pins: <font color=red>GPIO4</font><br>

* 2. Power On:
Make sure your Raspberry Pi is powered off before connecting the LED. Once everything is connected, you can power on your Raspberry Pi.

* 3. Software Setup:
You'll need to write a small program to turn the GPIO pin on and off to control the LED. You can use Python with the `gpiozero` library or `RPi.GPIO` library to control the GPIO pins.

===Example Python Code with gpiozero:===
<pre>
from gpiozero import LED
from time import sleep

led = LED('GPIO4')

while True:
led.on()
sleep(1)
led.off()
sleep(1)
</pre>

===Example Python Code with RPi.GPIO:===
<pre>
import RPi.GPIO as GPIO
import time

# Set the GPIO mode
GPIO.setmode(GPIO.BCM)

GPIO_PIN = 4

# Set up the GPIO pin as an output channel
GPIO.setup(GPIO_PIN, GPIO.OUT)

while True:
GPIO.output(GPIO_PIN, GPIO.HIGH) # Turn on the LED
time.sleep(1)
GPIO.output(GPIO_PIN, GPIO.LOW) # Turn off the LED
time.sleep(1)

# Clean up the GPIO pins before exiting the program
GPIO.cleanup()
</pre>

===Safety Tips:===
* Be careful not to short any pins on the Raspberry Pi.

==FAQ==
=== SSD1306 OLED Black-Screen Debugging Report & Operation Guide===

<strong>Target hardware:</strong> 0.91" OLED, 128×32 px, SSD1306, I2C, address 0x3C, Raspberry Pi 5
<strong>Software:</strong> luma.oled 3.15.0, luma.core 2.6.0, Python 3.13, smbus2

=== 1. Executive Summary — What Was Actually Wrong ===

<strong>Nothing was wrong with the code, the luma library, or the SSD1306 register configuration.</strong>
No library or example source code was modified. The failures came from hardware and
configuration, in one layers:

<strong>A parameter mismatch in the examples.</strong> The examples in this directory default to
`ssd1305 / 128×64`; this panel is `ssd1306 / 128×32`. Running without parameters
produces a black or garbled screen. The fix is to pass the correct display, interface,
geometry and address — done via the config file `ssd1306_128x32.conf`.

* ssd1306_128x32.conf contents:
<pre>
--display=ssd1306
--interface=i2c
--i2c-port=1
--i2c-address=0x3c
--width=128
--height=32
</pre>
Put this configuration file to your demo code location:
[[ File:Democodeconfig.png|left| 800px ]]
<br style="clear:both;">
* How to execute with config file
<pre>
sudo python3 demo.py -f ssd1306_128x32.conf
</pre>

=== 2. What Was Done, Step by Step (Method and Basis)===

{| class="wikitable"
|+ Diagnosis — locating the fault
! Method !! Basis / Reasoning
|-
| Bus scan with <code>i2cdetect</code> || An ACK at 0x3C proves all four wires
(VCC/GND/SDA/SCL) are connected and the driver IC is powered
|-
| Source inspection of ssd1306 in luma.oled 3.15.0 || The 128×32 init sequence
(multiplex 0x1F, compins 0x02, charge pump 0x14) matches the datasheet standard — a
register-level bug was ruled out on evidence
|-
| Raw-register write of 0xA5 (force all-on) || This command bypasses GDDRAM; a
healthy panel must glow. No light = fault in the high-voltage path (charge pump /
panel / flex cable)
|-
| Status-register read before/after DISPLAY ON/OFF commands || Per the SSD1306
datasheet, bit 6 is the display ON/OFF flag. It flipped correctly, proving the chip
executes commands — fault isolated to the panel side
|-
| 5 consecutive bus scans + 10 consecutive status reads || All values stable and
identical — ruled out loose wiring and parasitic power
|}

===3. Files Created / Modified===

{| class="wikitable"
|+ Fixes and deliverables
! File !! Type !! Description
|-
| <code>ssd1306_128x32.conf</code> || Fixed || Initially written in INI format,
causing "unrecognized arguments". Based on the source of
<code>luma.core.cmdline.load_config</code> (reads line by line, no whitespace
splitting), rewritten as one <code>--key=value</code> per line; demo.py then ran
successfully
|-
| <code>ssd1306_raw.py</code> || Created || Library-free SSD1306 driver; writes
registers directly via smbus2 (PIL used only for pixel rendering)
|-
| <code>OLED_128x32_I2C_manual.md</code> || Created / updated || Bilingual
operation manual; added the regulator/supply-voltage rule and the hardware-failure
criterion
|-
| <code>SSD1306_Debug_Report_EN.md</code> || Created || Full English debugging
report and operation guide
|}

No files in luma.oled / luma.core or the example scripts were modified.

===4. Final Working Configuration===

* Module: bare 0.91" 128×32 SSD1306, <strong>no onboard regulator</strong>
* Wiring: VCC → <strong>3.3 V</strong> (pin 1), GND → GND, SDA → GPIO2 (pin 3), SCL → GPIO3 (pin 5)
* No RST/RES connection needed (I2C interface)
* I2C address: `0x3C`

=== 5. Operating Instructions===

==== Run any luma example in this directory====

<pre>
python demo.py -f ssd1306_128x32.conf
python clock.py -f ssd1306_128x32.conf
python pi_logo.py -f ssd1306_128x32.conf
</pre>

Or pass parameters explicitly:

<pre>
python demo.py -d ssd1306 -i i2c --i2c-port 1 --i2c-address 0x3c --width 128 --height 32
</pre>

===Run the library-free raw driver===
<pre>
python ssd1306_raw.py # 0.96" 128x64
python ssd1306_raw.py --height 32 # 0.91" 128x32 (this panel)
python ssd1306_raw.py --addr 0x3D # modules with address 0x3D
</pre>
=== Minimal code (luma)===

<pre>
from luma.core.interface.serial import i2c
from luma.oled.device import ssd1306
from luma.core.render import canvas

device = ssd1306(i2c(port=1, address=0x3C), width=128, height=32)
with canvas(device) as draw:
draw.rectangle(device.bounding_box, outline="white")
draw.text((4, 10), "OK 128x32", fill="white")
</pre>

===6. Black-Screen Decision Tree (for future modules)===

* `i2cdetect -y 1` shows the address?
<strong>No</strong> → power/wiring fault: measure VCC-GND **at the module's solder pads**, check SDA=pin 3, SCL=pin 5, try fresh dupont wires.
<strong>Yes</strong> → continue.

* Run `python oled_diagnose.py`. Any step lights the panel?
<strong>Yes</strong> → software/parameter issue; use the matching parameters (`-d ssd1306 --width 128 --height 32 --i2c-address 0x3c`).
<strong>No</strong> → continue.

==Keywords==
* 1U Rackmount for Raspberry Pi 5 with M.2 NVMe SSD support.

DR-0001

2026-08-21T06:14:45Z

Yoyojacky: /* 2. What Was Done, Step by Step (Method and Basis) */

==1U Rackmount for Raspberry Pi 5 ==
* Purchase URL: [ https://52pi.com ] or [ https://deskpi.com ]
[[File:DR-0001-1.jpg|right|320px]]

==Description==
This is an upgraded version of a 1U Rackmount designed for compatibility with both Raspberry Pi 5 . It features a motherboard that supports PCIe expansion, allowing the PCIe interface of the Raspberry Pi 5 to be extended to accommodate an M.2 NVMe SSD in 2230/2242/2260/2280 form factors. The expansion board also routes the Raspberry Pi's 5V and GND, SDA, and SCL pins to the rear through PogoPin connectors, providing I2C interface peripherals in a Grove format. Additionally, a red LED is included on the board for the Raspberry Pi ID signal pin, which can be programmed to indicate the current device by controlling the GPIO4 pin's high or low level, acting as a programmable device ID signal light.

The Rackmount supports the connection of up to five Raspberry Pi devices and can also be configured with an OLED display frame in place of one of the Raspberry Pi slots. These components can be easily adjusted and removed due to the use of hand-tightened screws. The OLED display features a 0.91-inch screen and communicates with the Raspberry Pi via I2C protocol, displaying real-time information such as CPU status, memory status, IP information, and serial numbers. The content displayed on the OLED can be fully customized.
==Features==
* <strong>Compatibility:</strong> Designed to work with both Raspberry Pi 5.
* <strong>PCIe Expansion Support:</strong> Includes a motherboard that enables PCIe expansion, allowing the connection of M.2 NVMe SSDs in various form factors (2230/2242/2260/2280).
* <strong>I2C Interface: </strong> The board routes the Raspberry Pi's 5V, GND, SDA, and SCL pins to the rear through PogoPin connectors, offering I2C interface peripherals in a Grove format.
* <strong>Programmable LED Indicator: </strong> A red LED on the board serves as a programmable device ID signal, controllable via the GPIO4 pin to indicate the status or identity of the device.
* <strong>Modular Design:</strong> Supports the integration of up to five Raspberry Pi devices, with the option to replace one slot with an OLED display frame.
* <strong>OLED Display Integration:</strong> The option to include a 0.91-inch OLED screen that communicates with the Raspberry Pi via I2C, displaying customizable information such as CPU usage, memory status, IP address, and serial numbers.
* <strong>Easy Assembly and Disassembly:</strong> Components are secured with hand-tightened screws, allowing for convenient adjustments and removal.
* <strong>Customizable Display Content: </strong> The information displayed on the OLED screen can be fully customized to meet specific needs or preferences.
* <strong>Rackmount Form Factor: </strong> Designed to fit into a 1U rack space, making it suitable for data centers or other environments where space is at a premium.
* <strong>Versatility:</strong> The Rackmount can be configured in various ways to suit different use cases, whether for development, testing, or deployment in a production environment.
===Specifications===
* Form Factor: 1U Rackmount design suitable for standard 19-inch racks.
* Raspberry Pi Compatibility: Specifically designed for Raspberry Pi 5.
* PCIe Expansion:Supports M.2 NVMe SSDs in 2230, 2242, 2260, and 2280 form factors. Provides a PCIe interface for high-speed data transfer.
* I/O Connectivity: Rear I2C interface via PogoPin connectors for external peripherals.
* GPIO4 pin for programmable LED control.
* LED Indicator:Red LED for device identification or status indication. Programmable through software to show different statuses.
* Modular Bays: Five bays for Raspberry Pi devices. One bay can be replaced with an OLED display module.
* OLED Display Specifications:0.91-inch screen size, 128x32 pixels. I2C communication protocol.
* Customizable display for system information.
* Physical Security:Hand-tightened screws for secure mounting of Raspberry Pi devices and OLED display.
* Ensures stability and ease of maintenance.
* Power Requirements: Compatibility with Raspberry Pi's standard power supply.
* Material and Construction: Durable metal construction for the rackmount chassis. High-quality components for reliable performance.
* Mounting Options: Standard rackmount holes for easy installation into a rack.
* Includes additional mounting accessories for different setups.
* Software Compatibility: Compatible with Raspberry Pi's operating system and software ecosystem.
* Support for GPIO programming for custom LED and device control.
==Gallery==
* Product outlook
[[ File:DR-0001-6.jpg |left|800px]]
<br style="clear:both":>

* Application Senario
[[ File:DR-0001-2.jpg |left|800px]]
<br style="clear:both":>
<font color=red> NOTE: Raspberry Pis are not included in the package, additional purchase required!</font><br>
* Easy to assemble and maintain
[[ File:DR-0001-3.jpg |left|800px]]
<br style="clear:both":>
[[File:DR-0001-12.jpg|left|800px]]
<br style="clear:both":>

* Customizable OLED display screen, with a size of 0.91 inches
[[ File:DR-0001-4.jpg |left|800px]]
<br style="clear:both":>

* Ports Definitions and Featrues
Programmable I/O controlled UID indicator light, which can be programmed to control the LED blinking to indicate the device's location, facilitating faster troubleshooting and easier maintenance operations.
[[ File:DR-0001-5.jpg |left|800px]]
<br style="clear:both":>

===How to connect OLED display to Raspberry Pi on GPIO pins===
* Please refer to following figure to connect OLED display to Raspberry Pi on GPIO.
<font color=red>NOTE: OLED's VCC should be connected to 3.3V power rail, Do not connect it to 5V power rail!!!</font><br>
[[ File:DR-0001-7.jpg |left|800px]]
<br style="clear:both":>

* Grove Connector Support I2C and Uart
[[ File:DR-0001-8.jpg |left|800px]]
<br style="clear:both":>

* Accessories Dimension
[[ File:DR-0001-9.jpg |left|800px]]
<br style="clear:both":>

* OLED assemble details
Please remove the protection film from acrylic panel and use the washer between OLED PCB board and acrylic panel.
[[ File:DR-0001-10.jpg |left|800px]]
<br style="clear:both":>

* PCIe Expansion board for Raspberry Pi 5 only
The expansion board supports M.2 NVMe M-key SSD 2230/2242/2260/2280, and the board will be powered by Raspberry Pi 5 via PogoPin on the PCB board, please make sure the board's pogoins are contact well with the soldering point on back of the Raspberry Pi 5 on GPIO pins.
[[File:DR-0001-11.jpg|left|800px]]
<br style="clear:both":>

==How to assemble it? ==
* Please note that there are several details you need to pay attention, plesae check out following figure.
[[ File:DR-0001-安装.jpg|left|800px]]
<br style="clear:both";>

==Package Includes==
* Following figure shows the details of the product:
[[ File:DR-0001-清单.jpg|left|800px]]
<br style="clear:both";>

==How to enable I2C OLED display?==
* We assume that you are using Raspberry Pi OS 64bit(bookworm, the latest official image)
To enable I2C and UART on your Raspberry Pi, you can follow these detailed steps:

===Enabling I2C===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
to open the configuration tool. Navigate to `Interface Options`, Select `I2C` and enable it.

* Method 2. Using the Command Line:
You can also enable I2C by editing the `/boot/firmware/config.txt` file and adding `dtparam=i2c_arm=on` if it's not already present, After making changes, reboot your Pi.

===Verifying I2C===
* Install I2C tools using `sudo apt-get install -y i2c-tools`.
* Use
<pre>
i2cdetect -y 1
</pre>
to scan for I2C devices, if you see `3c` means that the OLED display has been recognized by your Raspberry Pi.

===Enabling UART===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
Go to `Interface Options`, Select `Serial` and enable it.
<pre> Note: This will also enable the login shell on the serial port. </pre>

* Method 2. Using the Command Line:
Edit `/boot/config.txt` and add `enable_uart=1`, save it and then reboot your Pi.

===Accessing UART===
* Connect your Pi to a USB-to-TTL converter, On Windows, you may need to install drivers for the converter. on Linux just use a terminal program like `minicom`, `putty`, or `screen` to access the UART interface.

Remember to check the documentation for your specific Raspberry Pi model, as the steps might vary slightly. If you need more detailed instructions or encounter any issues, refer to the [ https://www.raspberrypi.org/documentation/ ] or community forums for additional support.

===How to display customized information on OLED display? ===
* Final result
[[File:DR-0001 applications-01.jpg|left|800px]]
<br style="clear:both";>
==How to customize content on OLED ?==
* For example: If you want to display current IP address of wlan interface and the serial number of your Raspberry Pi 5, please follow next steps to configure it.
===Install Virtal environment package ===
* Open a terminal and typing following commands:
<pre>
sudo apt update
sudo apt upgrade -y
sudo apt -y install virtualenv
sudo usermod -a -G i2c,spi,gpio pi
sudo apt install python3-dev python3-pip python3-numpy libfreetype6-dev libjpeg-dev build-essential
sudo apt install libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libportmidi-dev
</pre>
[[File:Install pre-insistpackages.png|left|800px]]
<br style="clear:both";>
[[File:Install-pre-insistpackage-02.png|left|800px]]
<br style="clear:both";>

===Create virtual environment===
<pre>
virtualenv -p python3 venv
cd venv/
source bin/activate
</pre>
===Install SSD1306 driver and library for OLED 0.91===
<pre>
pip install luma.oled
pip install psutil
</pre>

===Clone luma.examples repository===
Log out and in again and clone this repository:
<pre>
git clone https://github.com/rm-hull/luma.examples.git
cd luma.examples/
</pre>
===Install luma libraries===
<pre>
sudo -H pip install -e . --break-system-packages
</pre>
[[File:Install luma libraries.png|left|800px]]
<br style="clear:both";>
===Test the demo ===
<pre>
cd examples/
sudo python 3d_box.py --width=128 --height=32 -r 2
</pre>

<font color=red><p>NOTE: <br>
--width=128 and --height=32 should be added to declear the OLED's resolution information. <br>
-r 2 means --rotate 2 , Allowed values are: 0, 1, 2, 3 (default:0)
</p>
</font>
If you see a 3D-box rotating animation is in the middle of screen means that you have installed the OLED driver successfully!
[[File:Test demo 3dbox.png|left|800px]]
<br style="clear:both";>
[[File:Test demo 3dbox-2.png|left|800px]]
<br style="clear:both";>
and then press "Ctrol+C" abort the demo.

==Use the demo code==
* There are a lot of demo codes in the examples folder, you can test it as you want.
for example:
<pre>
sudo python carousel.py --width=128 --height=32 -r 2
</pre>
It will display all information of your Raspberry Pi 5 and scrolling display.
===Customize the display on screen===
Modify the sys_info.py python file and adding your own function to show the information you want, do remember backup the origin file.
<pre>
cp sys_info.py sys_info.py.bak
vim.tiny sys_info.py
</pre>
Press 'i' to insert mode, and paste following lines into it. you can modify this file by other text editor what you like.
<pre>
#!/usr/bin/env python
# -*- coding: utf-8 -*-
# Copyright (c) 2014-2022 Richard Hull and contributors
# See LICENSE.rst for details.
# PYTHON_ARGCOMPLETE_OK

"""
Display basic system information.

Needs psutil (+ dependencies) installed::

$ sudo apt-get install python-dev
$ sudo -H pip install psutil
"""

import os
import sys
import time
from pathlib import Path
from datetime import datetime
import subprocess as sp

if os.name != 'posix':
sys.exit(f'{os.name} platform is not supported')

from demo_opts import get_device
from luma.core.render import canvas
from PIL import ImageFont

try:
import psutil
except ImportError:
print("The psutil library was not found. Run 'sudo -H pip install psutil' to install it.")
sys.exit()

# TODO: custom font bitmaps for up/down arrows
# TODO: Load histogram

def bytes2human(n):
"""
>>> bytes2human(10000)
'9K'
>>> bytes2human(100001221)
'95M'
"""
symbols = ('K', 'M', 'G', 'T', 'P', 'E', 'Z', 'Y')
prefix = {}
for i, s in enumerate(symbols):
prefix[s] = 1 << (i + 1) * 10
for s in reversed(symbols):
if n >= prefix[s]:
value = int(float(n) / prefix[s])
return '%s%s' % (value, s)
return f"{n}B"

def cpu_usage():
# load average, uptime
uptime = datetime.now() - datetime.fromtimestamp(psutil.boot_time())
#av1, av2, av3 = os.getloadavg()
#return "Ld:%.1f %.1f %.1f Up: %s" \
# % (av1, av2, av3, str(uptime).split('.')[0])
return "Up: %s" % (str(uptime).split('.')[0])

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi

def stats(device):
# use custom font
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
#font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'DejaVuSansMono.ttf'))
font2 = ImageFont.truetype(font_path, 15)

with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white")
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white")

if device.height >= 64:
draw.text((0, 26), disk_usage('/'), font=font2, fill="white")
try:
draw.text((0, 38), network('wlan0'), font=font2, fill="white")
except KeyError:
# no wifi enabled/available
pass

def main():
while True:
stats(device)
time.sleep(5)

if __name__ == "__main__":
try:
device = get_device()
main()
except KeyboardInterrupt:
pass
</pre>
Here let me explain to you what i did.
* adding " import subprocess as sp", this will help me to execute some shell command in OS.
* adding following parts:
<pre>
def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi
</pre>
* get_ip_address will execute the command "hostname -I" in system and grab the IP address and return it to main process.
* get_id is to read /proc/cpuinfo file and grab the serial number and return to main process.

===Use custom font===
<pre>
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
font2 = ImageFont.truetype(font_path, 15) # change font size to 15.
</pre>
===Modify the draw function===
<pre>
with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white") #####　draw id on screen at (0,0) position, (x,y)
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white") ####　draw text on (0,16) with IP address.
</pre>

==How to create a systemd file to make it automatically start at boot up==
* Step1. create a shell script called it 'start_led.sh'
<pre>
#!/bin/bash
#
cd /home/pi/venv/ && source /home/pi/venv/bin/activate
/usr/bin/python3 /home/pi/luma.examples/examples/sys_info.py --width=128 --height=32 -r 2
</pre>
save it and grant executable permission and test it.
<pre>
chmod +x start_led.sh
./start_led.sh
</pre>
If if works properly, just press "ctrol+c" to abort the test.
* Step2. create a systemd file and enable it.
<pre>
sudo vim.tiny /etc/systemd/system/rackmount_oled.service
</pre>
And then, adding following lines:
<pre>
[Unit]
Description=Rackmount OLED service on RPi5
DefaultDependencies=no
StartLimitIntervalSec=60
StartLimitBurst=5

[Service]
Type=simple
ExecStart=/bin/bash /home/pi/start_led.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
</pre>
Save it and quit.
===Enable rackmount_oled.service===
* reload daemon
<pre>
sudo systemctl daemon-reload
</pre>

* Enable service
<pre>
sudo systemctl enable rackmount_oled.service
</pre>
* Start service
<pre>
sudo systemctl start rackmount_oled.service
</pre>
* Restart service
<pre>
sudo systemctl restart rackmount_oled.service
</pre>
* Stop service
<pre>
sudo systemctl stop rackmount_oled.service
</pre>
* Disable service
<pre>
sudo systemctl disable rackmount_oled.service
</pre>

==How to enable PCIe function on Raspberry Pi 5?==
* To enable PCIe functionality on the Raspberry Pi 5, follow these steps:

===1. Enable the PCIe External Connector:===
By default, the PCIe connector on the Raspberry Pi 5 is not enabled. To enable it, you need to add a configuration parameter to the `config.txt` file located in the `/boot/firmware` directory. You can use either of these lines:
<pre>
dtparam=pciex1
</pre>
After adding the line, reboot your Raspberry Pi for the changes to take effect.

===2.Enable PCIe Gen 3.0 (Optional):===
The Raspberry Pi 5's PCIe connection is certified for Gen 2.0 speeds. However, if you want to attempt using Gen 3.0 speeds, add the following line to the `config.txt` file as well:
<pre>
dtparam=pciex1_gen=3
</pre>
Be aware that the Raspberry Pi 5 is not certified for Gen 3.0 speeds, and using this setting may result in instability .

===3.Booting from PCIe:===
If you intend to boot from a device connected via PCIe, such as an NVMe SSD, you will need to modify the boot order in the EEPROM. Use the following command to edit the EEPROM configuration:
<pre>
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-config --edit
</pre>
Then, change the `BOOT_ORDER` line to include NVMe in the boot order:
<pre>
BOOT_ORDER=0xf416
</pre>
This setting will make the Raspberry Pi attempt to boot from an NVMe device connected to the PCIe port .
===4. Kernel Compilation (Advanced):===
If you need to compile the kernel to add support for specific PCIe devices, you can follow the steps outlined in the Raspberry Pi documentation. This involves cloning the Raspberry Pi kernel repository, configuring the kernel with `make menuconfig`, and enabling the necessary modules for your devices .
Remember to always check the compatibility of the devices you intend to use with the Raspberry Pi 5's PCIe interface, as not all devices may be supported out of the box.

==How to light up identical LED? ==
To light up UID LED indicator on a Raspberry Pi 5, you'll make sure the GPIO Pin of the UID LED connected to.
<pre>
GPIO (General Purpose Input/Output) pins on the Raspberry Pi.
</pre>

===Steps===
* 1. Identify GPIO Pins: <font color=red>GPIO4</font><br>

* 2. Power On:
Make sure your Raspberry Pi is powered off before connecting the LED. Once everything is connected, you can power on your Raspberry Pi.

* 3. Software Setup:
You'll need to write a small program to turn the GPIO pin on and off to control the LED. You can use Python with the `gpiozero` library or `RPi.GPIO` library to control the GPIO pins.

===Example Python Code with gpiozero:===
<pre>
from gpiozero import LED
from time import sleep

led = LED('GPIO4')

while True:
led.on()
sleep(1)
led.off()
sleep(1)
</pre>

===Example Python Code with RPi.GPIO:===
<pre>
import RPi.GPIO as GPIO
import time

# Set the GPIO mode
GPIO.setmode(GPIO.BCM)

GPIO_PIN = 4

# Set up the GPIO pin as an output channel
GPIO.setup(GPIO_PIN, GPIO.OUT)

while True:
GPIO.output(GPIO_PIN, GPIO.HIGH) # Turn on the LED
time.sleep(1)
GPIO.output(GPIO_PIN, GPIO.LOW) # Turn off the LED
time.sleep(1)

# Clean up the GPIO pins before exiting the program
GPIO.cleanup()
</pre>

===Safety Tips:===
* Be careful not to short any pins on the Raspberry Pi.

==FAQ==
=== SSD1306 OLED Black-Screen Debugging Report & Operation Guide===

<strong>Target hardware:</strong> 0.91" OLED, 128×32 px, SSD1306, I2C, address 0x3C, Raspberry Pi 5
<strong>Software:</strong> luma.oled 3.15.0, luma.core 2.6.0, Python 3.13, smbus2

=== 1. Executive Summary — What Was Actually Wrong ===

<strong>Nothing was wrong with the code, the luma library, or the SSD1306 register configuration.</strong>
No library or example source code was modified. The failures came from hardware and
configuration, in one layers:

<strong>A parameter mismatch in the examples.</strong> The examples in this directory default to
`ssd1305 / 128×64`; this panel is `ssd1306 / 128×32`. Running without parameters
produces a black or garbled screen. The fix is to pass the correct display, interface,
geometry and address — done via the config file `ssd1306_128x32.conf`.

* ssd1306_128x32.conf contents:
<pre>
--display=ssd1306
--interface=i2c
--i2c-port=1
--i2c-address=0x3c
--width=128
--height=32
</pre>
Put this configuration file to your demo code location:
[[ File:Democodeconfig.png|left| 800px ]]
<br style="clear:both;">
* How to execute with config file
<pre>
sudo python3 demo.py -f ssd1306_128x32.conf
</pre>

=== 2. What Was Done, Step by Step (Method and Basis)===

{| class="wikitable"
|+ Diagnosis — locating the fault
! Method !! Basis / Reasoning
|-
| Bus scan with <code>i2cdetect</code> || An ACK at 0x3C proves all four wires
(VCC/GND/SDA/SCL) are connected and the driver IC is powered
|-
| Source inspection of ssd1306 in luma.oled 3.15.0 || The 128×32 init sequence
(multiplex 0x1F, compins 0x02, charge pump 0x14) matches the datasheet standard — a
register-level bug was ruled out on evidence
|-
| Raw-register write of 0xA5 (force all-on) || This command bypasses GDDRAM; a
healthy panel must glow. No light = fault in the high-voltage path (charge pump /
panel / flex cable)
|-
| Status-register read before/after DISPLAY ON/OFF commands || Per the SSD1306
datasheet, bit 6 is the display ON/OFF flag. It flipped correctly, proving the chip
executes commands — fault isolated to the panel side
|-
| 5 consecutive bus scans + 10 consecutive status reads || All values stable and
identical — ruled out loose wiring and parasitic power
|}

===3. Files Created / Modified===

{| class="wikitable"
|+ Fixes and deliverables
! File !! Type !! Description
|-
| <code>ssd1306_128x32.conf</code> || Fixed || Initially written in INI format,
causing "unrecognized arguments". Based on the source of
<code>luma.core.cmdline.load_config</code> (reads line by line, no whitespace
splitting), rewritten as one <code>--key=value</code> per line; demo.py then ran
successfully
|-
| <code>ssd1306_raw.py</code> || Created || Library-free SSD1306 driver; writes
registers directly via smbus2 (PIL used only for pixel rendering)
|-
| <code>OLED_128x32_I2C_manual.md</code> || Created / updated || Bilingual
operation manual; added the regulator/supply-voltage rule and the hardware-failure
criterion
|-
| <code>SSD1306_Debug_Report_EN.md</code> || Created || Full English debugging
report and operation guide
|}

No files in luma.oled / luma.core or the example scripts were modified.

===4. Final Working Configuration===

* Module: bare 0.91" 128×32 SSD1306, <strong>no onboard regulator</strong>
* Wiring: VCC → <strong>3.3 V</strong> (pin 1), GND → GND, SDA → GPIO2 (pin 3), SCL → GPIO3 (pin 5)
* No RST/RES connection needed (I2C interface)
* I2C address: `0x3C`

=== 5. Operating Instructions===

==== Run any luma example in this directory====

<pre>
python demo.py -f ssd1306_128x32.conf
python clock.py -f ssd1306_128x32.conf
python pi_logo.py -f ssd1306_128x32.conf
</pre>

Or pass parameters explicitly:

<pre>
python demo.py -d ssd1306 -i i2c --i2c-port 1 --i2c-address 0x3c --width 128 --height 32
</pre>

===Run the library-free raw driver===
<pre>
python ssd1306_raw.py # 0.96" 128x64
python ssd1306_raw.py --height 32 # 0.91" 128x32 (this panel)
python ssd1306_raw.py --addr 0x3D # modules with address 0x3D
</pre>
=== Minimal code (luma)===

<pre>
from luma.core.interface.serial import i2c
from luma.oled.device import ssd1306
from luma.core.render import canvas

device = ssd1306(i2c(port=1, address=0x3C), width=128, height=32)
with canvas(device) as draw:
draw.rectangle(device.bounding_box, outline="white")
draw.text((4, 10), "OK 128x32", fill="white")
</pre>

===6. Black-Screen Decision Tree (for future modules)===

* `i2cdetect -y 1` shows the address?
<strong>No</strong> → power/wiring fault: measure VCC-GND **at the module's solder pads**, check SDA=pin 3, SCL=pin 5, try fresh dupont wires.
<strong>Yes</strong> → continue.

* Run `python oled_diagnose.py`. Any step lights the panel?
<strong>Yes</strong> → software/parameter issue; use the matching parameters (`-d ssd1306 --width 128 --height 32 --i2c-address 0x3c`).
<strong>No</strong> → continue.

* Status-register test: does bit 6 flip after `0xAF`/`0xAE`?
<strong>Yes</strong> (chip executes commands, panel still dark) → charge pump/panel hardware. Check whether the module has a regulator: AMS1117 → power with **5 V**; no regulator → power with **3.3 V**. Still dark at the correct voltage → defective module, return it.
<strong>No</strong> → module-level fault (reset circuit / dead IC), return it.

==Keywords==
* 1U Rackmount for Raspberry Pi 5 with M.2 NVMe SSD support.

DR-0001

2026-08-19T05:33:04Z

Yoyojacky: /* 1. Executive Summary — What Was Actually Wrong */

==1U Rackmount for Raspberry Pi 5 ==
* Purchase URL: [ https://52pi.com ] or [ https://deskpi.com ]
[[File:DR-0001-1.jpg|right|320px]]

==Description==
This is an upgraded version of a 1U Rackmount designed for compatibility with both Raspberry Pi 5 . It features a motherboard that supports PCIe expansion, allowing the PCIe interface of the Raspberry Pi 5 to be extended to accommodate an M.2 NVMe SSD in 2230/2242/2260/2280 form factors. The expansion board also routes the Raspberry Pi's 5V and GND, SDA, and SCL pins to the rear through PogoPin connectors, providing I2C interface peripherals in a Grove format. Additionally, a red LED is included on the board for the Raspberry Pi ID signal pin, which can be programmed to indicate the current device by controlling the GPIO4 pin's high or low level, acting as a programmable device ID signal light.

The Rackmount supports the connection of up to five Raspberry Pi devices and can also be configured with an OLED display frame in place of one of the Raspberry Pi slots. These components can be easily adjusted and removed due to the use of hand-tightened screws. The OLED display features a 0.91-inch screen and communicates with the Raspberry Pi via I2C protocol, displaying real-time information such as CPU status, memory status, IP information, and serial numbers. The content displayed on the OLED can be fully customized.
==Features==
* <strong>Compatibility:</strong> Designed to work with both Raspberry Pi 5.
* <strong>PCIe Expansion Support:</strong> Includes a motherboard that enables PCIe expansion, allowing the connection of M.2 NVMe SSDs in various form factors (2230/2242/2260/2280).
* <strong>I2C Interface: </strong> The board routes the Raspberry Pi's 5V, GND, SDA, and SCL pins to the rear through PogoPin connectors, offering I2C interface peripherals in a Grove format.
* <strong>Programmable LED Indicator: </strong> A red LED on the board serves as a programmable device ID signal, controllable via the GPIO4 pin to indicate the status or identity of the device.
* <strong>Modular Design:</strong> Supports the integration of up to five Raspberry Pi devices, with the option to replace one slot with an OLED display frame.
* <strong>OLED Display Integration:</strong> The option to include a 0.91-inch OLED screen that communicates with the Raspberry Pi via I2C, displaying customizable information such as CPU usage, memory status, IP address, and serial numbers.
* <strong>Easy Assembly and Disassembly:</strong> Components are secured with hand-tightened screws, allowing for convenient adjustments and removal.
* <strong>Customizable Display Content: </strong> The information displayed on the OLED screen can be fully customized to meet specific needs or preferences.
* <strong>Rackmount Form Factor: </strong> Designed to fit into a 1U rack space, making it suitable for data centers or other environments where space is at a premium.
* <strong>Versatility:</strong> The Rackmount can be configured in various ways to suit different use cases, whether for development, testing, or deployment in a production environment.
===Specifications===
* Form Factor: 1U Rackmount design suitable for standard 19-inch racks.
* Raspberry Pi Compatibility: Specifically designed for Raspberry Pi 5.
* PCIe Expansion:Supports M.2 NVMe SSDs in 2230, 2242, 2260, and 2280 form factors. Provides a PCIe interface for high-speed data transfer.
* I/O Connectivity: Rear I2C interface via PogoPin connectors for external peripherals.
* GPIO4 pin for programmable LED control.
* LED Indicator:Red LED for device identification or status indication. Programmable through software to show different statuses.
* Modular Bays: Five bays for Raspberry Pi devices. One bay can be replaced with an OLED display module.
* OLED Display Specifications:0.91-inch screen size, 128x32 pixels. I2C communication protocol.
* Customizable display for system information.
* Physical Security:Hand-tightened screws for secure mounting of Raspberry Pi devices and OLED display.
* Ensures stability and ease of maintenance.
* Power Requirements: Compatibility with Raspberry Pi's standard power supply.
* Material and Construction: Durable metal construction for the rackmount chassis. High-quality components for reliable performance.
* Mounting Options: Standard rackmount holes for easy installation into a rack.
* Includes additional mounting accessories for different setups.
* Software Compatibility: Compatible with Raspberry Pi's operating system and software ecosystem.
* Support for GPIO programming for custom LED and device control.
==Gallery==
* Product outlook
[[ File:DR-0001-6.jpg |left|800px]]
<br style="clear:both":>

* Application Senario
[[ File:DR-0001-2.jpg |left|800px]]
<br style="clear:both":>
<font color=red> NOTE: Raspberry Pis are not included in the package, additional purchase required!</font><br>
* Easy to assemble and maintain
[[ File:DR-0001-3.jpg |left|800px]]
<br style="clear:both":>
[[File:DR-0001-12.jpg|left|800px]]
<br style="clear:both":>

* Customizable OLED display screen, with a size of 0.91 inches
[[ File:DR-0001-4.jpg |left|800px]]
<br style="clear:both":>

* Ports Definitions and Featrues
Programmable I/O controlled UID indicator light, which can be programmed to control the LED blinking to indicate the device's location, facilitating faster troubleshooting and easier maintenance operations.
[[ File:DR-0001-5.jpg |left|800px]]
<br style="clear:both":>

===How to connect OLED display to Raspberry Pi on GPIO pins===
* Please refer to following figure to connect OLED display to Raspberry Pi on GPIO.
<font color=red>NOTE: OLED's VCC should be connected to 3.3V power rail, Do not connect it to 5V power rail!!!</font><br>
[[ File:DR-0001-7.jpg |left|800px]]
<br style="clear:both":>

* Grove Connector Support I2C and Uart
[[ File:DR-0001-8.jpg |left|800px]]
<br style="clear:both":>

* Accessories Dimension
[[ File:DR-0001-9.jpg |left|800px]]
<br style="clear:both":>

* OLED assemble details
Please remove the protection film from acrylic panel and use the washer between OLED PCB board and acrylic panel.
[[ File:DR-0001-10.jpg |left|800px]]
<br style="clear:both":>

* PCIe Expansion board for Raspberry Pi 5 only
The expansion board supports M.2 NVMe M-key SSD 2230/2242/2260/2280, and the board will be powered by Raspberry Pi 5 via PogoPin on the PCB board, please make sure the board's pogoins are contact well with the soldering point on back of the Raspberry Pi 5 on GPIO pins.
[[File:DR-0001-11.jpg|left|800px]]
<br style="clear:both":>

==How to assemble it? ==
* Please note that there are several details you need to pay attention, plesae check out following figure.
[[ File:DR-0001-安装.jpg|left|800px]]
<br style="clear:both";>

==Package Includes==
* Following figure shows the details of the product:
[[ File:DR-0001-清单.jpg|left|800px]]
<br style="clear:both";>

==How to enable I2C OLED display?==
* We assume that you are using Raspberry Pi OS 64bit(bookworm, the latest official image)
To enable I2C and UART on your Raspberry Pi, you can follow these detailed steps:

===Enabling I2C===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
to open the configuration tool. Navigate to `Interface Options`, Select `I2C` and enable it.

* Method 2. Using the Command Line:
You can also enable I2C by editing the `/boot/firmware/config.txt` file and adding `dtparam=i2c_arm=on` if it's not already present, After making changes, reboot your Pi.

===Verifying I2C===
* Install I2C tools using `sudo apt-get install -y i2c-tools`.
* Use
<pre>
i2cdetect -y 1
</pre>
to scan for I2C devices, if you see `3c` means that the OLED display has been recognized by your Raspberry Pi.

===Enabling UART===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
Go to `Interface Options`, Select `Serial` and enable it.
<pre> Note: This will also enable the login shell on the serial port. </pre>

* Method 2. Using the Command Line:
Edit `/boot/config.txt` and add `enable_uart=1`, save it and then reboot your Pi.

===Accessing UART===
* Connect your Pi to a USB-to-TTL converter, On Windows, you may need to install drivers for the converter. on Linux just use a terminal program like `minicom`, `putty`, or `screen` to access the UART interface.

Remember to check the documentation for your specific Raspberry Pi model, as the steps might vary slightly. If you need more detailed instructions or encounter any issues, refer to the [ https://www.raspberrypi.org/documentation/ ] or community forums for additional support.

===How to display customized information on OLED display? ===
* Final result
[[File:DR-0001 applications-01.jpg|left|800px]]
<br style="clear:both";>
==How to customize content on OLED ?==
* For example: If you want to display current IP address of wlan interface and the serial number of your Raspberry Pi 5, please follow next steps to configure it.
===Install Virtal environment package ===
* Open a terminal and typing following commands:
<pre>
sudo apt update
sudo apt upgrade -y
sudo apt -y install virtualenv
sudo usermod -a -G i2c,spi,gpio pi
sudo apt install python3-dev python3-pip python3-numpy libfreetype6-dev libjpeg-dev build-essential
sudo apt install libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libportmidi-dev
</pre>
[[File:Install pre-insistpackages.png|left|800px]]
<br style="clear:both";>
[[File:Install-pre-insistpackage-02.png|left|800px]]
<br style="clear:both";>

===Create virtual environment===
<pre>
virtualenv -p python3 venv
cd venv/
source bin/activate
</pre>
===Install SSD1306 driver and library for OLED 0.91===
<pre>
pip install luma.oled
pip install psutil
</pre>

===Clone luma.examples repository===
Log out and in again and clone this repository:
<pre>
git clone https://github.com/rm-hull/luma.examples.git
cd luma.examples/
</pre>
===Install luma libraries===
<pre>
sudo -H pip install -e . --break-system-packages
</pre>
[[File:Install luma libraries.png|left|800px]]
<br style="clear:both";>
===Test the demo ===
<pre>
cd examples/
sudo python 3d_box.py --width=128 --height=32 -r 2
</pre>

<font color=red><p>NOTE: <br>
--width=128 and --height=32 should be added to declear the OLED's resolution information. <br>
-r 2 means --rotate 2 , Allowed values are: 0, 1, 2, 3 (default:0)
</p>
</font>
If you see a 3D-box rotating animation is in the middle of screen means that you have installed the OLED driver successfully!
[[File:Test demo 3dbox.png|left|800px]]
<br style="clear:both";>
[[File:Test demo 3dbox-2.png|left|800px]]
<br style="clear:both";>
and then press "Ctrol+C" abort the demo.

==Use the demo code==
* There are a lot of demo codes in the examples folder, you can test it as you want.
for example:
<pre>
sudo python carousel.py --width=128 --height=32 -r 2
</pre>
It will display all information of your Raspberry Pi 5 and scrolling display.
===Customize the display on screen===
Modify the sys_info.py python file and adding your own function to show the information you want, do remember backup the origin file.
<pre>
cp sys_info.py sys_info.py.bak
vim.tiny sys_info.py
</pre>
Press 'i' to insert mode, and paste following lines into it. you can modify this file by other text editor what you like.
<pre>
#!/usr/bin/env python
# -*- coding: utf-8 -*-
# Copyright (c) 2014-2022 Richard Hull and contributors
# See LICENSE.rst for details.
# PYTHON_ARGCOMPLETE_OK

"""
Display basic system information.

Needs psutil (+ dependencies) installed::

$ sudo apt-get install python-dev
$ sudo -H pip install psutil
"""

import os
import sys
import time
from pathlib import Path
from datetime import datetime
import subprocess as sp

if os.name != 'posix':
sys.exit(f'{os.name} platform is not supported')

from demo_opts import get_device
from luma.core.render import canvas
from PIL import ImageFont

try:
import psutil
except ImportError:
print("The psutil library was not found. Run 'sudo -H pip install psutil' to install it.")
sys.exit()

# TODO: custom font bitmaps for up/down arrows
# TODO: Load histogram

def bytes2human(n):
"""
>>> bytes2human(10000)
'9K'
>>> bytes2human(100001221)
'95M'
"""
symbols = ('K', 'M', 'G', 'T', 'P', 'E', 'Z', 'Y')
prefix = {}
for i, s in enumerate(symbols):
prefix[s] = 1 << (i + 1) * 10
for s in reversed(symbols):
if n >= prefix[s]:
value = int(float(n) / prefix[s])
return '%s%s' % (value, s)
return f"{n}B"

def cpu_usage():
# load average, uptime
uptime = datetime.now() - datetime.fromtimestamp(psutil.boot_time())
#av1, av2, av3 = os.getloadavg()
#return "Ld:%.1f %.1f %.1f Up: %s" \
# % (av1, av2, av3, str(uptime).split('.')[0])
return "Up: %s" % (str(uptime).split('.')[0])

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi

def stats(device):
# use custom font
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
#font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'DejaVuSansMono.ttf'))
font2 = ImageFont.truetype(font_path, 15)

with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white")
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white")

if device.height >= 64:
draw.text((0, 26), disk_usage('/'), font=font2, fill="white")
try:
draw.text((0, 38), network('wlan0'), font=font2, fill="white")
except KeyError:
# no wifi enabled/available
pass

def main():
while True:
stats(device)
time.sleep(5)

if __name__ == "__main__":
try:
device = get_device()
main()
except KeyboardInterrupt:
pass
</pre>
Here let me explain to you what i did.
* adding " import subprocess as sp", this will help me to execute some shell command in OS.
* adding following parts:
<pre>
def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi
</pre>
* get_ip_address will execute the command "hostname -I" in system and grab the IP address and return it to main process.
* get_id is to read /proc/cpuinfo file and grab the serial number and return to main process.

===Use custom font===
<pre>
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
font2 = ImageFont.truetype(font_path, 15) # change font size to 15.
</pre>
===Modify the draw function===
<pre>
with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white") #####　draw id on screen at (0,0) position, (x,y)
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white") ####　draw text on (0,16) with IP address.
</pre>

==How to create a systemd file to make it automatically start at boot up==
* Step1. create a shell script called it 'start_led.sh'
<pre>
#!/bin/bash
#
cd /home/pi/venv/ && source /home/pi/venv/bin/activate
/usr/bin/python3 /home/pi/luma.examples/examples/sys_info.py --width=128 --height=32 -r 2
</pre>
save it and grant executable permission and test it.
<pre>
chmod +x start_led.sh
./start_led.sh
</pre>
If if works properly, just press "ctrol+c" to abort the test.
* Step2. create a systemd file and enable it.
<pre>
sudo vim.tiny /etc/systemd/system/rackmount_oled.service
</pre>
And then, adding following lines:
<pre>
[Unit]
Description=Rackmount OLED service on RPi5
DefaultDependencies=no
StartLimitIntervalSec=60
StartLimitBurst=5

[Service]
Type=simple
ExecStart=/bin/bash /home/pi/start_led.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
</pre>
Save it and quit.
===Enable rackmount_oled.service===
* reload daemon
<pre>
sudo systemctl daemon-reload
</pre>

* Enable service
<pre>
sudo systemctl enable rackmount_oled.service
</pre>
* Start service
<pre>
sudo systemctl start rackmount_oled.service
</pre>
* Restart service
<pre>
sudo systemctl restart rackmount_oled.service
</pre>
* Stop service
<pre>
sudo systemctl stop rackmount_oled.service
</pre>
* Disable service
<pre>
sudo systemctl disable rackmount_oled.service
</pre>

==How to enable PCIe function on Raspberry Pi 5?==
* To enable PCIe functionality on the Raspberry Pi 5, follow these steps:

===1. Enable the PCIe External Connector:===
By default, the PCIe connector on the Raspberry Pi 5 is not enabled. To enable it, you need to add a configuration parameter to the `config.txt` file located in the `/boot/firmware` directory. You can use either of these lines:
<pre>
dtparam=pciex1
</pre>
After adding the line, reboot your Raspberry Pi for the changes to take effect.

===2.Enable PCIe Gen 3.0 (Optional):===
The Raspberry Pi 5's PCIe connection is certified for Gen 2.0 speeds. However, if you want to attempt using Gen 3.0 speeds, add the following line to the `config.txt` file as well:
<pre>
dtparam=pciex1_gen=3
</pre>
Be aware that the Raspberry Pi 5 is not certified for Gen 3.0 speeds, and using this setting may result in instability .

===3.Booting from PCIe:===
If you intend to boot from a device connected via PCIe, such as an NVMe SSD, you will need to modify the boot order in the EEPROM. Use the following command to edit the EEPROM configuration:
<pre>
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-config --edit
</pre>
Then, change the `BOOT_ORDER` line to include NVMe in the boot order:
<pre>
BOOT_ORDER=0xf416
</pre>
This setting will make the Raspberry Pi attempt to boot from an NVMe device connected to the PCIe port .
===4. Kernel Compilation (Advanced):===
If you need to compile the kernel to add support for specific PCIe devices, you can follow the steps outlined in the Raspberry Pi documentation. This involves cloning the Raspberry Pi kernel repository, configuring the kernel with `make menuconfig`, and enabling the necessary modules for your devices .
Remember to always check the compatibility of the devices you intend to use with the Raspberry Pi 5's PCIe interface, as not all devices may be supported out of the box.

==How to light up identical LED? ==
To light up UID LED indicator on a Raspberry Pi 5, you'll make sure the GPIO Pin of the UID LED connected to.
<pre>
GPIO (General Purpose Input/Output) pins on the Raspberry Pi.
</pre>

===Steps===
* 1. Identify GPIO Pins: <font color=red>GPIO4</font><br>

* 2. Power On:
Make sure your Raspberry Pi is powered off before connecting the LED. Once everything is connected, you can power on your Raspberry Pi.

* 3. Software Setup:
You'll need to write a small program to turn the GPIO pin on and off to control the LED. You can use Python with the `gpiozero` library or `RPi.GPIO` library to control the GPIO pins.

===Example Python Code with gpiozero:===
<pre>
from gpiozero import LED
from time import sleep

led = LED('GPIO4')

while True:
led.on()
sleep(1)
led.off()
sleep(1)
</pre>

===Example Python Code with RPi.GPIO:===
<pre>
import RPi.GPIO as GPIO
import time

# Set the GPIO mode
GPIO.setmode(GPIO.BCM)

GPIO_PIN = 4

# Set up the GPIO pin as an output channel
GPIO.setup(GPIO_PIN, GPIO.OUT)

while True:
GPIO.output(GPIO_PIN, GPIO.HIGH) # Turn on the LED
time.sleep(1)
GPIO.output(GPIO_PIN, GPIO.LOW) # Turn off the LED
time.sleep(1)

# Clean up the GPIO pins before exiting the program
GPIO.cleanup()
</pre>

===Safety Tips:===
* Be careful not to short any pins on the Raspberry Pi.

==FAQ==
=== SSD1306 OLED Black-Screen Debugging Report & Operation Guide===

<strong>Target hardware:</strong> 0.91" OLED, 128×32 px, SSD1306, I2C, address 0x3C, Raspberry Pi 5
<strong>Software:</strong> luma.oled 3.15.0, luma.core 2.6.0, Python 3.13, smbus2

=== 1. Executive Summary — What Was Actually Wrong ===

<strong>Nothing was wrong with the code, the luma library, or the SSD1306 register configuration.</strong>
No library or example source code was modified. The failures came from hardware and
configuration, in one layers:

<strong>A parameter mismatch in the examples.</strong> The examples in this directory default to
`ssd1305 / 128×64`; this panel is `ssd1306 / 128×32`. Running without parameters
produces a black or garbled screen. The fix is to pass the correct display, interface,
geometry and address — done via the config file `ssd1306_128x32.conf`.

* ssd1306_128x32.conf contents:
<pre>
--display=ssd1306
--interface=i2c
--i2c-port=1
--i2c-address=0x3c
--width=128
--height=32
</pre>
Put this configuration file to your demo code location:
[[ File:Democodeconfig.png|left| 800px ]]
<br style="clear:both;">
* How to execute with config file
<pre>
sudo python3 demo.py -f ssd1306_128x32.conf
</pre>

=== 2. What Was Done, Step by Step (Method and Basis)===

{| class="wikitable"
|+ Diagnosis — locating the fault
! Method !! Basis / Reasoning
|-
| Bus scan with <code>i2cdetect</code> || An ACK at 0x3C proves all four wires
(VCC/GND/SDA/SCL) are connected and the driver IC is powered
|-
| Source inspection of ssd1306 in luma.oled 3.15.0 || The 128×32 init sequence
(multiplex 0x1F, compins 0x02, charge pump 0x14) matches the datasheet standard — a
register-level bug was ruled out on evidence
|-
| Raw-register write of 0xA5 (force all-on) || This command bypasses GDDRAM; a
healthy panel must glow. No light = fault in the high-voltage path (charge pump /
panel / flex cable)
|-
| Status-register read before/after DISPLAY ON/OFF commands || Per the SSD1306
datasheet, bit 6 is the display ON/OFF flag. It flipped correctly, proving the chip
executes commands — fault isolated to the panel side
|-
| 5 consecutive bus scans + 10 consecutive status reads || All values stable and
identical — ruled out loose wiring and parasitic power
|-
| 3.3V / 5V supply switching test || Modules with an AMS1117 regulator require 5V;
bare modules without a regulator require 3.3V. The working module lit at 3.3V
|}

===3. Files Created / Modified===

{| class="wikitable"
|+ Fixes and deliverables
! File !! Type !! Description
|-
| <code>ssd1306_128x32.conf</code> || Fixed || Initially written in INI format,
causing "unrecognized arguments". Based on the source of
<code>luma.core.cmdline.load_config</code> (reads line by line, no whitespace
splitting), rewritten as one <code>--key=value</code> per line; demo.py then ran
successfully
|-
| <code>ssd1306_raw.py</code> || Created || Library-free SSD1306 driver; writes
registers directly via smbus2 (PIL used only for pixel rendering)
|-
| <code>OLED_128x32_I2C_manual.md</code> || Created / updated || Bilingual
operation manual; added the regulator/supply-voltage rule and the hardware-failure
criterion
|-
| <code>SSD1306_Debug_Report_EN.md</code> || Created || Full English debugging
report and operation guide
|}

No files in luma.oled / luma.core or the example scripts were modified.

===4. Final Working Configuration===

* Module: bare 0.91" 128×32 SSD1306, <strong>no onboard regulator</strong>
* Wiring: VCC → <strong>3.3 V</strong> (pin 1), GND → GND, SDA → GPIO2 (pin 3), SCL → GPIO3 (pin 5)
* No RST/RES connection needed (I2C interface)
* I2C address: `0x3C`

=== 5. Operating Instructions===

==== Run any luma example in this directory====

<pre>
python demo.py -f ssd1306_128x32.conf
python clock.py -f ssd1306_128x32.conf
python pi_logo.py -f ssd1306_128x32.conf
</pre>

Or pass parameters explicitly:

<pre>
python demo.py -d ssd1306 -i i2c --i2c-port 1 --i2c-address 0x3c --width 128 --height 32
</pre>

===Run the library-free raw driver===
<pre>
python ssd1306_raw.py # 0.96" 128x64
python ssd1306_raw.py --height 32 # 0.91" 128x32 (this panel)
python ssd1306_raw.py --addr 0x3D # modules with address 0x3D
</pre>
=== Minimal code (luma)===

<pre>
from luma.core.interface.serial import i2c
from luma.oled.device import ssd1306
from luma.core.render import canvas

device = ssd1306(i2c(port=1, address=0x3C), width=128, height=32)
with canvas(device) as draw:
draw.rectangle(device.bounding_box, outline="white")
draw.text((4, 10), "OK 128x32", fill="white")
</pre>

===6. Black-Screen Decision Tree (for future modules)===

* `i2cdetect -y 1` shows the address?
<strong>No</strong> → power/wiring fault: measure VCC-GND **at the module's solder pads**, check SDA=pin 3, SCL=pin 5, try fresh dupont wires.
<strong>Yes</strong> → continue.

* Run `python oled_diagnose.py`. Any step lights the panel?
<strong>Yes</strong> → software/parameter issue; use the matching parameters (`-d ssd1306 --width 128 --height 32 --i2c-address 0x3c`).
<strong>No</strong> → continue.

* Status-register test: does bit 6 flip after `0xAF`/`0xAE`?
<strong>Yes</strong> (chip executes commands, panel still dark) → charge pump/panel hardware. Check whether the module has a regulator: AMS1117 → power with **5 V**; no regulator → power with **3.3 V**. Still dark at the correct voltage → defective module, return it.
<strong>No</strong> → module-level fault (reset circuit / dead IC), return it.

==Keywords==
* 1U Rackmount for Raspberry Pi 5 with M.2 NVMe SSD support.

File:Democodeconfig.png

2026-08-19T05:23:29Z

Yoyojacky:

DR-0001

2026-08-19T05:18:30Z

Yoyojacky: /* FAQ */

==1U Rackmount for Raspberry Pi 5 ==
* Purchase URL: [ https://52pi.com ] or [ https://deskpi.com ]
[[File:DR-0001-1.jpg|right|320px]]

==Description==
This is an upgraded version of a 1U Rackmount designed for compatibility with both Raspberry Pi 5 . It features a motherboard that supports PCIe expansion, allowing the PCIe interface of the Raspberry Pi 5 to be extended to accommodate an M.2 NVMe SSD in 2230/2242/2260/2280 form factors. The expansion board also routes the Raspberry Pi's 5V and GND, SDA, and SCL pins to the rear through PogoPin connectors, providing I2C interface peripherals in a Grove format. Additionally, a red LED is included on the board for the Raspberry Pi ID signal pin, which can be programmed to indicate the current device by controlling the GPIO4 pin's high or low level, acting as a programmable device ID signal light.

The Rackmount supports the connection of up to five Raspberry Pi devices and can also be configured with an OLED display frame in place of one of the Raspberry Pi slots. These components can be easily adjusted and removed due to the use of hand-tightened screws. The OLED display features a 0.91-inch screen and communicates with the Raspberry Pi via I2C protocol, displaying real-time information such as CPU status, memory status, IP information, and serial numbers. The content displayed on the OLED can be fully customized.
==Features==
* <strong>Compatibility:</strong> Designed to work with both Raspberry Pi 5.
* <strong>PCIe Expansion Support:</strong> Includes a motherboard that enables PCIe expansion, allowing the connection of M.2 NVMe SSDs in various form factors (2230/2242/2260/2280).
* <strong>I2C Interface: </strong> The board routes the Raspberry Pi's 5V, GND, SDA, and SCL pins to the rear through PogoPin connectors, offering I2C interface peripherals in a Grove format.
* <strong>Programmable LED Indicator: </strong> A red LED on the board serves as a programmable device ID signal, controllable via the GPIO4 pin to indicate the status or identity of the device.
* <strong>Modular Design:</strong> Supports the integration of up to five Raspberry Pi devices, with the option to replace one slot with an OLED display frame.
* <strong>OLED Display Integration:</strong> The option to include a 0.91-inch OLED screen that communicates with the Raspberry Pi via I2C, displaying customizable information such as CPU usage, memory status, IP address, and serial numbers.
* <strong>Easy Assembly and Disassembly:</strong> Components are secured with hand-tightened screws, allowing for convenient adjustments and removal.
* <strong>Customizable Display Content: </strong> The information displayed on the OLED screen can be fully customized to meet specific needs or preferences.
* <strong>Rackmount Form Factor: </strong> Designed to fit into a 1U rack space, making it suitable for data centers or other environments where space is at a premium.
* <strong>Versatility:</strong> The Rackmount can be configured in various ways to suit different use cases, whether for development, testing, or deployment in a production environment.
===Specifications===
* Form Factor: 1U Rackmount design suitable for standard 19-inch racks.
* Raspberry Pi Compatibility: Specifically designed for Raspberry Pi 5.
* PCIe Expansion:Supports M.2 NVMe SSDs in 2230, 2242, 2260, and 2280 form factors. Provides a PCIe interface for high-speed data transfer.
* I/O Connectivity: Rear I2C interface via PogoPin connectors for external peripherals.
* GPIO4 pin for programmable LED control.
* LED Indicator:Red LED for device identification or status indication. Programmable through software to show different statuses.
* Modular Bays: Five bays for Raspberry Pi devices. One bay can be replaced with an OLED display module.
* OLED Display Specifications:0.91-inch screen size, 128x32 pixels. I2C communication protocol.
* Customizable display for system information.
* Physical Security:Hand-tightened screws for secure mounting of Raspberry Pi devices and OLED display.
* Ensures stability and ease of maintenance.
* Power Requirements: Compatibility with Raspberry Pi's standard power supply.
* Material and Construction: Durable metal construction for the rackmount chassis. High-quality components for reliable performance.
* Mounting Options: Standard rackmount holes for easy installation into a rack.
* Includes additional mounting accessories for different setups.
* Software Compatibility: Compatible with Raspberry Pi's operating system and software ecosystem.
* Support for GPIO programming for custom LED and device control.
==Gallery==
* Product outlook
[[ File:DR-0001-6.jpg |left|800px]]
<br style="clear:both":>

* Application Senario
[[ File:DR-0001-2.jpg |left|800px]]
<br style="clear:both":>
<font color=red> NOTE: Raspberry Pis are not included in the package, additional purchase required!</font><br>
* Easy to assemble and maintain
[[ File:DR-0001-3.jpg |left|800px]]
<br style="clear:both":>
[[File:DR-0001-12.jpg|left|800px]]
<br style="clear:both":>

* Customizable OLED display screen, with a size of 0.91 inches
[[ File:DR-0001-4.jpg |left|800px]]
<br style="clear:both":>

* Ports Definitions and Featrues
Programmable I/O controlled UID indicator light, which can be programmed to control the LED blinking to indicate the device's location, facilitating faster troubleshooting and easier maintenance operations.
[[ File:DR-0001-5.jpg |left|800px]]
<br style="clear:both":>

===How to connect OLED display to Raspberry Pi on GPIO pins===
* Please refer to following figure to connect OLED display to Raspberry Pi on GPIO.
<font color=red>NOTE: OLED's VCC should be connected to 3.3V power rail, Do not connect it to 5V power rail!!!</font><br>
[[ File:DR-0001-7.jpg |left|800px]]
<br style="clear:both":>

* Grove Connector Support I2C and Uart
[[ File:DR-0001-8.jpg |left|800px]]
<br style="clear:both":>

* Accessories Dimension
[[ File:DR-0001-9.jpg |left|800px]]
<br style="clear:both":>

* OLED assemble details
Please remove the protection film from acrylic panel and use the washer between OLED PCB board and acrylic panel.
[[ File:DR-0001-10.jpg |left|800px]]
<br style="clear:both":>

* PCIe Expansion board for Raspberry Pi 5 only
The expansion board supports M.2 NVMe M-key SSD 2230/2242/2260/2280, and the board will be powered by Raspberry Pi 5 via PogoPin on the PCB board, please make sure the board's pogoins are contact well with the soldering point on back of the Raspberry Pi 5 on GPIO pins.
[[File:DR-0001-11.jpg|left|800px]]
<br style="clear:both":>

==How to assemble it? ==
* Please note that there are several details you need to pay attention, plesae check out following figure.
[[ File:DR-0001-安装.jpg|left|800px]]
<br style="clear:both";>

==Package Includes==
* Following figure shows the details of the product:
[[ File:DR-0001-清单.jpg|left|800px]]
<br style="clear:both";>

==How to enable I2C OLED display?==
* We assume that you are using Raspberry Pi OS 64bit(bookworm, the latest official image)
To enable I2C and UART on your Raspberry Pi, you can follow these detailed steps:

===Enabling I2C===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
to open the configuration tool. Navigate to `Interface Options`, Select `I2C` and enable it.

* Method 2. Using the Command Line:
You can also enable I2C by editing the `/boot/firmware/config.txt` file and adding `dtparam=i2c_arm=on` if it's not already present, After making changes, reboot your Pi.

===Verifying I2C===
* Install I2C tools using `sudo apt-get install -y i2c-tools`.
* Use
<pre>
i2cdetect -y 1
</pre>
to scan for I2C devices, if you see `3c` means that the OLED display has been recognized by your Raspberry Pi.

===Enabling UART===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
Go to `Interface Options`, Select `Serial` and enable it.
<pre> Note: This will also enable the login shell on the serial port. </pre>

* Method 2. Using the Command Line:
Edit `/boot/config.txt` and add `enable_uart=1`, save it and then reboot your Pi.

===Accessing UART===
* Connect your Pi to a USB-to-TTL converter, On Windows, you may need to install drivers for the converter. on Linux just use a terminal program like `minicom`, `putty`, or `screen` to access the UART interface.

Remember to check the documentation for your specific Raspberry Pi model, as the steps might vary slightly. If you need more detailed instructions or encounter any issues, refer to the [ https://www.raspberrypi.org/documentation/ ] or community forums for additional support.

===How to display customized information on OLED display? ===
* Final result
[[File:DR-0001 applications-01.jpg|left|800px]]
<br style="clear:both";>
==How to customize content on OLED ?==
* For example: If you want to display current IP address of wlan interface and the serial number of your Raspberry Pi 5, please follow next steps to configure it.
===Install Virtal environment package ===
* Open a terminal and typing following commands:
<pre>
sudo apt update
sudo apt upgrade -y
sudo apt -y install virtualenv
sudo usermod -a -G i2c,spi,gpio pi
sudo apt install python3-dev python3-pip python3-numpy libfreetype6-dev libjpeg-dev build-essential
sudo apt install libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libportmidi-dev
</pre>
[[File:Install pre-insistpackages.png|left|800px]]
<br style="clear:both";>
[[File:Install-pre-insistpackage-02.png|left|800px]]
<br style="clear:both";>

===Create virtual environment===
<pre>
virtualenv -p python3 venv
cd venv/
source bin/activate
</pre>
===Install SSD1306 driver and library for OLED 0.91===
<pre>
pip install luma.oled
pip install psutil
</pre>

===Clone luma.examples repository===
Log out and in again and clone this repository:
<pre>
git clone https://github.com/rm-hull/luma.examples.git
cd luma.examples/
</pre>
===Install luma libraries===
<pre>
sudo -H pip install -e . --break-system-packages
</pre>
[[File:Install luma libraries.png|left|800px]]
<br style="clear:both";>
===Test the demo ===
<pre>
cd examples/
sudo python 3d_box.py --width=128 --height=32 -r 2
</pre>

<font color=red><p>NOTE: <br>
--width=128 and --height=32 should be added to declear the OLED's resolution information. <br>
-r 2 means --rotate 2 , Allowed values are: 0, 1, 2, 3 (default:0)
</p>
</font>
If you see a 3D-box rotating animation is in the middle of screen means that you have installed the OLED driver successfully!
[[File:Test demo 3dbox.png|left|800px]]
<br style="clear:both";>
[[File:Test demo 3dbox-2.png|left|800px]]
<br style="clear:both";>
and then press "Ctrol+C" abort the demo.

==Use the demo code==
* There are a lot of demo codes in the examples folder, you can test it as you want.
for example:
<pre>
sudo python carousel.py --width=128 --height=32 -r 2
</pre>
It will display all information of your Raspberry Pi 5 and scrolling display.
===Customize the display on screen===
Modify the sys_info.py python file and adding your own function to show the information you want, do remember backup the origin file.
<pre>
cp sys_info.py sys_info.py.bak
vim.tiny sys_info.py
</pre>
Press 'i' to insert mode, and paste following lines into it. you can modify this file by other text editor what you like.
<pre>
#!/usr/bin/env python
# -*- coding: utf-8 -*-
# Copyright (c) 2014-2022 Richard Hull and contributors
# See LICENSE.rst for details.
# PYTHON_ARGCOMPLETE_OK

"""
Display basic system information.

Needs psutil (+ dependencies) installed::

$ sudo apt-get install python-dev
$ sudo -H pip install psutil
"""

import os
import sys
import time
from pathlib import Path
from datetime import datetime
import subprocess as sp

if os.name != 'posix':
sys.exit(f'{os.name} platform is not supported')

from demo_opts import get_device
from luma.core.render import canvas
from PIL import ImageFont

try:
import psutil
except ImportError:
print("The psutil library was not found. Run 'sudo -H pip install psutil' to install it.")
sys.exit()

# TODO: custom font bitmaps for up/down arrows
# TODO: Load histogram

def bytes2human(n):
"""
>>> bytes2human(10000)
'9K'
>>> bytes2human(100001221)
'95M'
"""
symbols = ('K', 'M', 'G', 'T', 'P', 'E', 'Z', 'Y')
prefix = {}
for i, s in enumerate(symbols):
prefix[s] = 1 << (i + 1) * 10
for s in reversed(symbols):
if n >= prefix[s]:
value = int(float(n) / prefix[s])
return '%s%s' % (value, s)
return f"{n}B"

def cpu_usage():
# load average, uptime
uptime = datetime.now() - datetime.fromtimestamp(psutil.boot_time())
#av1, av2, av3 = os.getloadavg()
#return "Ld:%.1f %.1f %.1f Up: %s" \
# % (av1, av2, av3, str(uptime).split('.')[0])
return "Up: %s" % (str(uptime).split('.')[0])

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi

def stats(device):
# use custom font
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
#font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'DejaVuSansMono.ttf'))
font2 = ImageFont.truetype(font_path, 15)

with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white")
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white")

if device.height >= 64:
draw.text((0, 26), disk_usage('/'), font=font2, fill="white")
try:
draw.text((0, 38), network('wlan0'), font=font2, fill="white")
except KeyError:
# no wifi enabled/available
pass

def main():
while True:
stats(device)
time.sleep(5)

if __name__ == "__main__":
try:
device = get_device()
main()
except KeyboardInterrupt:
pass
</pre>
Here let me explain to you what i did.
* adding " import subprocess as sp", this will help me to execute some shell command in OS.
* adding following parts:
<pre>
def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi
</pre>
* get_ip_address will execute the command "hostname -I" in system and grab the IP address and return it to main process.
* get_id is to read /proc/cpuinfo file and grab the serial number and return to main process.

===Use custom font===
<pre>
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
font2 = ImageFont.truetype(font_path, 15) # change font size to 15.
</pre>
===Modify the draw function===
<pre>
with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white") #####　draw id on screen at (0,0) position, (x,y)
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white") ####　draw text on (0,16) with IP address.
</pre>

==How to create a systemd file to make it automatically start at boot up==
* Step1. create a shell script called it 'start_led.sh'
<pre>
#!/bin/bash
#
cd /home/pi/venv/ && source /home/pi/venv/bin/activate
/usr/bin/python3 /home/pi/luma.examples/examples/sys_info.py --width=128 --height=32 -r 2
</pre>
save it and grant executable permission and test it.
<pre>
chmod +x start_led.sh
./start_led.sh
</pre>
If if works properly, just press "ctrol+c" to abort the test.
* Step2. create a systemd file and enable it.
<pre>
sudo vim.tiny /etc/systemd/system/rackmount_oled.service
</pre>
And then, adding following lines:
<pre>
[Unit]
Description=Rackmount OLED service on RPi5
DefaultDependencies=no
StartLimitIntervalSec=60
StartLimitBurst=5

[Service]
Type=simple
ExecStart=/bin/bash /home/pi/start_led.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
</pre>
Save it and quit.
===Enable rackmount_oled.service===
* reload daemon
<pre>
sudo systemctl daemon-reload
</pre>

* Enable service
<pre>
sudo systemctl enable rackmount_oled.service
</pre>
* Start service
<pre>
sudo systemctl start rackmount_oled.service
</pre>
* Restart service
<pre>
sudo systemctl restart rackmount_oled.service
</pre>
* Stop service
<pre>
sudo systemctl stop rackmount_oled.service
</pre>
* Disable service
<pre>
sudo systemctl disable rackmount_oled.service
</pre>

==How to enable PCIe function on Raspberry Pi 5?==
* To enable PCIe functionality on the Raspberry Pi 5, follow these steps:

===1. Enable the PCIe External Connector:===
By default, the PCIe connector on the Raspberry Pi 5 is not enabled. To enable it, you need to add a configuration parameter to the `config.txt` file located in the `/boot/firmware` directory. You can use either of these lines:
<pre>
dtparam=pciex1
</pre>
After adding the line, reboot your Raspberry Pi for the changes to take effect.

===2.Enable PCIe Gen 3.0 (Optional):===
The Raspberry Pi 5's PCIe connection is certified for Gen 2.0 speeds. However, if you want to attempt using Gen 3.0 speeds, add the following line to the `config.txt` file as well:
<pre>
dtparam=pciex1_gen=3
</pre>
Be aware that the Raspberry Pi 5 is not certified for Gen 3.0 speeds, and using this setting may result in instability .

===3.Booting from PCIe:===
If you intend to boot from a device connected via PCIe, such as an NVMe SSD, you will need to modify the boot order in the EEPROM. Use the following command to edit the EEPROM configuration:
<pre>
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-config --edit
</pre>
Then, change the `BOOT_ORDER` line to include NVMe in the boot order:
<pre>
BOOT_ORDER=0xf416
</pre>
This setting will make the Raspberry Pi attempt to boot from an NVMe device connected to the PCIe port .
===4. Kernel Compilation (Advanced):===
If you need to compile the kernel to add support for specific PCIe devices, you can follow the steps outlined in the Raspberry Pi documentation. This involves cloning the Raspberry Pi kernel repository, configuring the kernel with `make menuconfig`, and enabling the necessary modules for your devices .
Remember to always check the compatibility of the devices you intend to use with the Raspberry Pi 5's PCIe interface, as not all devices may be supported out of the box.

==How to light up identical LED? ==
To light up UID LED indicator on a Raspberry Pi 5, you'll make sure the GPIO Pin of the UID LED connected to.
<pre>
GPIO (General Purpose Input/Output) pins on the Raspberry Pi.
</pre>

===Steps===
* 1. Identify GPIO Pins: <font color=red>GPIO4</font><br>

* 2. Power On:
Make sure your Raspberry Pi is powered off before connecting the LED. Once everything is connected, you can power on your Raspberry Pi.

* 3. Software Setup:
You'll need to write a small program to turn the GPIO pin on and off to control the LED. You can use Python with the `gpiozero` library or `RPi.GPIO` library to control the GPIO pins.

===Example Python Code with gpiozero:===
<pre>
from gpiozero import LED
from time import sleep

led = LED('GPIO4')

while True:
led.on()
sleep(1)
led.off()
sleep(1)
</pre>

===Example Python Code with RPi.GPIO:===
<pre>
import RPi.GPIO as GPIO
import time

# Set the GPIO mode
GPIO.setmode(GPIO.BCM)

GPIO_PIN = 4

# Set up the GPIO pin as an output channel
GPIO.setup(GPIO_PIN, GPIO.OUT)

while True:
GPIO.output(GPIO_PIN, GPIO.HIGH) # Turn on the LED
time.sleep(1)
GPIO.output(GPIO_PIN, GPIO.LOW) # Turn off the LED
time.sleep(1)

# Clean up the GPIO pins before exiting the program
GPIO.cleanup()
</pre>

===Safety Tips:===
* Be careful not to short any pins on the Raspberry Pi.

==FAQ==
=== SSD1306 OLED Black-Screen Debugging Report & Operation Guide===

<strong>Target hardware:</strong> 0.91" OLED, 128×32 px, SSD1306, I2C, address 0x3C, Raspberry Pi 5
<strong>Software:</strong> luma.oled 3.15.0, luma.core 2.6.0, Python 3.13, smbus2

=== 1. Executive Summary — What Was Actually Wrong ===

<strong>Nothing was wrong with the code, the luma library, or the SSD1306 register configuration.</strong>
No library or example source code was modified. The failures came from hardware and
configuration, in three layers:

1. <strong>Two defective display modules.</strong> The driver IC responded on I2C and executed
commands correctly, but the panel itself never lit — dead charge-pump / flex-cable /
panel. The first module had worked before and died of age; the replacement (0.96")
showed the identical signature, indicating a bad batch.
2. <strong>A supply-voltage trap.</strong> Modules with an onboard AMS1117 regulator (~1.1 V dropout)
must be fed <strong> 5V</strong> ; at 3.3 V the logic still works (so the chip ACKs and responds,
which is very misleading) but the charge pump cannot start → black screen. Bare
modules with <strong> no regulator must use 3.3 V</strong> ; feeding them 5 V does not work and risks
damage. The final working module is a bare one and runs correctly at 3.3 V.
3. <strong>A parameter mismatch in the examples.</strong> The examples in this directory default to
`ssd1305 / 128×64`; this panel is `ssd1306 / 128×32`. Running without parameters
produces a black or garbled screen. The fix is to pass the correct display, interface,
geometry and address — done via the config file `ssd1306_128x32.conf`.

=== 2. What Was Done, Step by Step (Method and Basis)===

{| class="wikitable"
|+ Diagnosis — locating the fault
! Method !! Basis / Reasoning
|-
| Bus scan with <code>i2cdetect</code> || An ACK at 0x3C proves all four wires
(VCC/GND/SDA/SCL) are connected and the driver IC is powered
|-
| Source inspection of ssd1306 in luma.oled 3.15.0 || The 128×32 init sequence
(multiplex 0x1F, compins 0x02, charge pump 0x14) matches the datasheet standard — a
register-level bug was ruled out on evidence
|-
| Raw-register write of 0xA5 (force all-on) || This command bypasses GDDRAM; a
healthy panel must glow. No light = fault in the high-voltage path (charge pump /
panel / flex cable)
|-
| Status-register read before/after DISPLAY ON/OFF commands || Per the SSD1306
datasheet, bit 6 is the display ON/OFF flag. It flipped correctly, proving the chip
executes commands — fault isolated to the panel side
|-
| 5 consecutive bus scans + 10 consecutive status reads || All values stable and
identical — ruled out loose wiring and parasitic power
|-
| 3.3V / 5V supply switching test || Modules with an AMS1117 regulator require 5V;
bare modules without a regulator require 3.3V. The working module lit at 3.3V
|}

===3. Files Created / Modified===

{| class="wikitable"
|+ Fixes and deliverables
! File !! Type !! Description
|-
| <code>ssd1306_128x32.conf</code> || Fixed || Initially written in INI format,
causing "unrecognized arguments". Based on the source of
<code>luma.core.cmdline.load_config</code> (reads line by line, no whitespace
splitting), rewritten as one <code>--key=value</code> per line; demo.py then ran
successfully
|-
| <code>ssd1306_raw.py</code> || Created || Library-free SSD1306 driver; writes
registers directly via smbus2 (PIL used only for pixel rendering)
|-
| <code>OLED_128x32_I2C_manual.md</code> || Created / updated || Bilingual
operation manual; added the regulator/supply-voltage rule and the hardware-failure
criterion
|-
| <code>SSD1306_Debug_Report_EN.md</code> || Created || Full English debugging
report and operation guide
|}

No files in luma.oled / luma.core or the example scripts were modified.

===4. Final Working Configuration===

* Module: bare 0.91" 128×32 SSD1306, <strong>no onboard regulator</strong>
* Wiring: VCC → <strong>3.3 V</strong> (pin 1), GND → GND, SDA → GPIO2 (pin 3), SCL → GPIO3 (pin 5)
* No RST/RES connection needed (I2C interface)
* I2C address: `0x3C`

=== 5. Operating Instructions===

==== Run any luma example in this directory====

<pre>
python demo.py -f ssd1306_128x32.conf
python clock.py -f ssd1306_128x32.conf
python pi_logo.py -f ssd1306_128x32.conf
</pre>

Or pass parameters explicitly:

<pre>
python demo.py -d ssd1306 -i i2c --i2c-port 1 --i2c-address 0x3c --width 128 --height 32
</pre>

===Run the library-free raw driver===
<pre>
python ssd1306_raw.py # 0.96" 128x64
python ssd1306_raw.py --height 32 # 0.91" 128x32 (this panel)
python ssd1306_raw.py --addr 0x3D # modules with address 0x3D
</pre>
=== Minimal code (luma)===

<pre>
from luma.core.interface.serial import i2c
from luma.oled.device import ssd1306
from luma.core.render import canvas

device = ssd1306(i2c(port=1, address=0x3C), width=128, height=32)
with canvas(device) as draw:
draw.rectangle(device.bounding_box, outline="white")
draw.text((4, 10), "OK 128x32", fill="white")
</pre>

===6. Black-Screen Decision Tree (for future modules)===

* `i2cdetect -y 1` shows the address?
<strong>No</strong> → power/wiring fault: measure VCC-GND **at the module's solder pads**, check SDA=pin 3, SCL=pin 5, try fresh dupont wires.
<strong>Yes</strong> → continue.

* Run `python oled_diagnose.py`. Any step lights the panel?
<strong>Yes</strong> → software/parameter issue; use the matching parameters (`-d ssd1306 --width 128 --height 32 --i2c-address 0x3c`).
<strong>No</strong> → continue.

* Status-register test: does bit 6 flip after `0xAF`/`0xAE`?
<strong>Yes</strong> (chip executes commands, panel still dark) → charge pump/panel hardware. Check whether the module has a regulator: AMS1117 → power with **5 V**; no regulator → power with **3.3 V**. Still dark at the correct voltage → defective module, return it.
<strong>No</strong> → module-level fault (reset circuit / dead IC), return it.

==Keywords==
* 1U Rackmount for Raspberry Pi 5 with M.2 NVMe SSD support.

DR-0001

2026-08-19T05:18:09Z

Yoyojacky: /* Keywords */

==1U Rackmount for Raspberry Pi 5 ==
* Purchase URL: [ https://52pi.com ] or [ https://deskpi.com ]
[[File:DR-0001-1.jpg|right|320px]]

==Description==
This is an upgraded version of a 1U Rackmount designed for compatibility with both Raspberry Pi 5 . It features a motherboard that supports PCIe expansion, allowing the PCIe interface of the Raspberry Pi 5 to be extended to accommodate an M.2 NVMe SSD in 2230/2242/2260/2280 form factors. The expansion board also routes the Raspberry Pi's 5V and GND, SDA, and SCL pins to the rear through PogoPin connectors, providing I2C interface peripherals in a Grove format. Additionally, a red LED is included on the board for the Raspberry Pi ID signal pin, which can be programmed to indicate the current device by controlling the GPIO4 pin's high or low level, acting as a programmable device ID signal light.

The Rackmount supports the connection of up to five Raspberry Pi devices and can also be configured with an OLED display frame in place of one of the Raspberry Pi slots. These components can be easily adjusted and removed due to the use of hand-tightened screws. The OLED display features a 0.91-inch screen and communicates with the Raspberry Pi via I2C protocol, displaying real-time information such as CPU status, memory status, IP information, and serial numbers. The content displayed on the OLED can be fully customized.
==Features==
* <strong>Compatibility:</strong> Designed to work with both Raspberry Pi 5.
* <strong>PCIe Expansion Support:</strong> Includes a motherboard that enables PCIe expansion, allowing the connection of M.2 NVMe SSDs in various form factors (2230/2242/2260/2280).
* <strong>I2C Interface: </strong> The board routes the Raspberry Pi's 5V, GND, SDA, and SCL pins to the rear through PogoPin connectors, offering I2C interface peripherals in a Grove format.
* <strong>Programmable LED Indicator: </strong> A red LED on the board serves as a programmable device ID signal, controllable via the GPIO4 pin to indicate the status or identity of the device.
* <strong>Modular Design:</strong> Supports the integration of up to five Raspberry Pi devices, with the option to replace one slot with an OLED display frame.
* <strong>OLED Display Integration:</strong> The option to include a 0.91-inch OLED screen that communicates with the Raspberry Pi via I2C, displaying customizable information such as CPU usage, memory status, IP address, and serial numbers.
* <strong>Easy Assembly and Disassembly:</strong> Components are secured with hand-tightened screws, allowing for convenient adjustments and removal.
* <strong>Customizable Display Content: </strong> The information displayed on the OLED screen can be fully customized to meet specific needs or preferences.
* <strong>Rackmount Form Factor: </strong> Designed to fit into a 1U rack space, making it suitable for data centers or other environments where space is at a premium.
* <strong>Versatility:</strong> The Rackmount can be configured in various ways to suit different use cases, whether for development, testing, or deployment in a production environment.
===Specifications===
* Form Factor: 1U Rackmount design suitable for standard 19-inch racks.
* Raspberry Pi Compatibility: Specifically designed for Raspberry Pi 5.
* PCIe Expansion:Supports M.2 NVMe SSDs in 2230, 2242, 2260, and 2280 form factors. Provides a PCIe interface for high-speed data transfer.
* I/O Connectivity: Rear I2C interface via PogoPin connectors for external peripherals.
* GPIO4 pin for programmable LED control.
* LED Indicator:Red LED for device identification or status indication. Programmable through software to show different statuses.
* Modular Bays: Five bays for Raspberry Pi devices. One bay can be replaced with an OLED display module.
* OLED Display Specifications:0.91-inch screen size, 128x32 pixels. I2C communication protocol.
* Customizable display for system information.
* Physical Security:Hand-tightened screws for secure mounting of Raspberry Pi devices and OLED display.
* Ensures stability and ease of maintenance.
* Power Requirements: Compatibility with Raspberry Pi's standard power supply.
* Material and Construction: Durable metal construction for the rackmount chassis. High-quality components for reliable performance.
* Mounting Options: Standard rackmount holes for easy installation into a rack.
* Includes additional mounting accessories for different setups.
* Software Compatibility: Compatible with Raspberry Pi's operating system and software ecosystem.
* Support for GPIO programming for custom LED and device control.
==Gallery==
* Product outlook
[[ File:DR-0001-6.jpg |left|800px]]
<br style="clear:both":>

* Application Senario
[[ File:DR-0001-2.jpg |left|800px]]
<br style="clear:both":>
<font color=red> NOTE: Raspberry Pis are not included in the package, additional purchase required!</font><br>
* Easy to assemble and maintain
[[ File:DR-0001-3.jpg |left|800px]]
<br style="clear:both":>
[[File:DR-0001-12.jpg|left|800px]]
<br style="clear:both":>

* Customizable OLED display screen, with a size of 0.91 inches
[[ File:DR-0001-4.jpg |left|800px]]
<br style="clear:both":>

* Ports Definitions and Featrues
Programmable I/O controlled UID indicator light, which can be programmed to control the LED blinking to indicate the device's location, facilitating faster troubleshooting and easier maintenance operations.
[[ File:DR-0001-5.jpg |left|800px]]
<br style="clear:both":>

===How to connect OLED display to Raspberry Pi on GPIO pins===
* Please refer to following figure to connect OLED display to Raspberry Pi on GPIO.
<font color=red>NOTE: OLED's VCC should be connected to 3.3V power rail, Do not connect it to 5V power rail!!!</font><br>
[[ File:DR-0001-7.jpg |left|800px]]
<br style="clear:both":>

* Grove Connector Support I2C and Uart
[[ File:DR-0001-8.jpg |left|800px]]
<br style="clear:both":>

* Accessories Dimension
[[ File:DR-0001-9.jpg |left|800px]]
<br style="clear:both":>

* OLED assemble details
Please remove the protection film from acrylic panel and use the washer between OLED PCB board and acrylic panel.
[[ File:DR-0001-10.jpg |left|800px]]
<br style="clear:both":>

* PCIe Expansion board for Raspberry Pi 5 only
The expansion board supports M.2 NVMe M-key SSD 2230/2242/2260/2280, and the board will be powered by Raspberry Pi 5 via PogoPin on the PCB board, please make sure the board's pogoins are contact well with the soldering point on back of the Raspberry Pi 5 on GPIO pins.
[[File:DR-0001-11.jpg|left|800px]]
<br style="clear:both":>

==How to assemble it? ==
* Please note that there are several details you need to pay attention, plesae check out following figure.
[[ File:DR-0001-安装.jpg|left|800px]]
<br style="clear:both";>

==Package Includes==
* Following figure shows the details of the product:
[[ File:DR-0001-清单.jpg|left|800px]]
<br style="clear:both";>

==How to enable I2C OLED display?==
* We assume that you are using Raspberry Pi OS 64bit(bookworm, the latest official image)
To enable I2C and UART on your Raspberry Pi, you can follow these detailed steps:

===Enabling I2C===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
to open the configuration tool. Navigate to `Interface Options`, Select `I2C` and enable it.

* Method 2. Using the Command Line:
You can also enable I2C by editing the `/boot/firmware/config.txt` file and adding `dtparam=i2c_arm=on` if it's not already present, After making changes, reboot your Pi.

===Verifying I2C===
* Install I2C tools using `sudo apt-get install -y i2c-tools`.
* Use
<pre>
i2cdetect -y 1
</pre>
to scan for I2C devices, if you see `3c` means that the OLED display has been recognized by your Raspberry Pi.

===Enabling UART===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
Go to `Interface Options`, Select `Serial` and enable it.
<pre> Note: This will also enable the login shell on the serial port. </pre>

* Method 2. Using the Command Line:
Edit `/boot/config.txt` and add `enable_uart=1`, save it and then reboot your Pi.

===Accessing UART===
* Connect your Pi to a USB-to-TTL converter, On Windows, you may need to install drivers for the converter. on Linux just use a terminal program like `minicom`, `putty`, or `screen` to access the UART interface.

Remember to check the documentation for your specific Raspberry Pi model, as the steps might vary slightly. If you need more detailed instructions or encounter any issues, refer to the [ https://www.raspberrypi.org/documentation/ ] or community forums for additional support.

===How to display customized information on OLED display? ===
* Final result
[[File:DR-0001 applications-01.jpg|left|800px]]
<br style="clear:both";>
==How to customize content on OLED ?==
* For example: If you want to display current IP address of wlan interface and the serial number of your Raspberry Pi 5, please follow next steps to configure it.
===Install Virtal environment package ===
* Open a terminal and typing following commands:
<pre>
sudo apt update
sudo apt upgrade -y
sudo apt -y install virtualenv
sudo usermod -a -G i2c,spi,gpio pi
sudo apt install python3-dev python3-pip python3-numpy libfreetype6-dev libjpeg-dev build-essential
sudo apt install libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libportmidi-dev
</pre>
[[File:Install pre-insistpackages.png|left|800px]]
<br style="clear:both";>
[[File:Install-pre-insistpackage-02.png|left|800px]]
<br style="clear:both";>

===Create virtual environment===
<pre>
virtualenv -p python3 venv
cd venv/
source bin/activate
</pre>
===Install SSD1306 driver and library for OLED 0.91===
<pre>
pip install luma.oled
pip install psutil
</pre>

===Clone luma.examples repository===
Log out and in again and clone this repository:
<pre>
git clone https://github.com/rm-hull/luma.examples.git
cd luma.examples/
</pre>
===Install luma libraries===
<pre>
sudo -H pip install -e . --break-system-packages
</pre>
[[File:Install luma libraries.png|left|800px]]
<br style="clear:both";>
===Test the demo ===
<pre>
cd examples/
sudo python 3d_box.py --width=128 --height=32 -r 2
</pre>

<font color=red><p>NOTE: <br>
--width=128 and --height=32 should be added to declear the OLED's resolution information. <br>
-r 2 means --rotate 2 , Allowed values are: 0, 1, 2, 3 (default:0)
</p>
</font>
If you see a 3D-box rotating animation is in the middle of screen means that you have installed the OLED driver successfully!
[[File:Test demo 3dbox.png|left|800px]]
<br style="clear:both";>
[[File:Test demo 3dbox-2.png|left|800px]]
<br style="clear:both";>
and then press "Ctrol+C" abort the demo.

==Use the demo code==
* There are a lot of demo codes in the examples folder, you can test it as you want.
for example:
<pre>
sudo python carousel.py --width=128 --height=32 -r 2
</pre>
It will display all information of your Raspberry Pi 5 and scrolling display.
===Customize the display on screen===
Modify the sys_info.py python file and adding your own function to show the information you want, do remember backup the origin file.
<pre>
cp sys_info.py sys_info.py.bak
vim.tiny sys_info.py
</pre>
Press 'i' to insert mode, and paste following lines into it. you can modify this file by other text editor what you like.
<pre>
#!/usr/bin/env python
# -*- coding: utf-8 -*-
# Copyright (c) 2014-2022 Richard Hull and contributors
# See LICENSE.rst for details.
# PYTHON_ARGCOMPLETE_OK

"""
Display basic system information.

Needs psutil (+ dependencies) installed::

$ sudo apt-get install python-dev
$ sudo -H pip install psutil
"""

import os
import sys
import time
from pathlib import Path
from datetime import datetime
import subprocess as sp

if os.name != 'posix':
sys.exit(f'{os.name} platform is not supported')

from demo_opts import get_device
from luma.core.render import canvas
from PIL import ImageFont

try:
import psutil
except ImportError:
print("The psutil library was not found. Run 'sudo -H pip install psutil' to install it.")
sys.exit()

# TODO: custom font bitmaps for up/down arrows
# TODO: Load histogram

def bytes2human(n):
"""
>>> bytes2human(10000)
'9K'
>>> bytes2human(100001221)
'95M'
"""
symbols = ('K', 'M', 'G', 'T', 'P', 'E', 'Z', 'Y')
prefix = {}
for i, s in enumerate(symbols):
prefix[s] = 1 << (i + 1) * 10
for s in reversed(symbols):
if n >= prefix[s]:
value = int(float(n) / prefix[s])
return '%s%s' % (value, s)
return f"{n}B"

def cpu_usage():
# load average, uptime
uptime = datetime.now() - datetime.fromtimestamp(psutil.boot_time())
#av1, av2, av3 = os.getloadavg()
#return "Ld:%.1f %.1f %.1f Up: %s" \
# % (av1, av2, av3, str(uptime).split('.')[0])
return "Up: %s" % (str(uptime).split('.')[0])

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi

def stats(device):
# use custom font
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
#font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'DejaVuSansMono.ttf'))
font2 = ImageFont.truetype(font_path, 15)

with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white")
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white")

if device.height >= 64:
draw.text((0, 26), disk_usage('/'), font=font2, fill="white")
try:
draw.text((0, 38), network('wlan0'), font=font2, fill="white")
except KeyError:
# no wifi enabled/available
pass

def main():
while True:
stats(device)
time.sleep(5)

if __name__ == "__main__":
try:
device = get_device()
main()
except KeyboardInterrupt:
pass
</pre>
Here let me explain to you what i did.
* adding " import subprocess as sp", this will help me to execute some shell command in OS.
* adding following parts:
<pre>
def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi
</pre>
* get_ip_address will execute the command "hostname -I" in system and grab the IP address and return it to main process.
* get_id is to read /proc/cpuinfo file and grab the serial number and return to main process.

===Use custom font===
<pre>
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
font2 = ImageFont.truetype(font_path, 15) # change font size to 15.
</pre>
===Modify the draw function===
<pre>
with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white") #####　draw id on screen at (0,0) position, (x,y)
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white") ####　draw text on (0,16) with IP address.
</pre>

==How to create a systemd file to make it automatically start at boot up==
* Step1. create a shell script called it 'start_led.sh'
<pre>
#!/bin/bash
#
cd /home/pi/venv/ && source /home/pi/venv/bin/activate
/usr/bin/python3 /home/pi/luma.examples/examples/sys_info.py --width=128 --height=32 -r 2
</pre>
save it and grant executable permission and test it.
<pre>
chmod +x start_led.sh
./start_led.sh
</pre>
If if works properly, just press "ctrol+c" to abort the test.
* Step2. create a systemd file and enable it.
<pre>
sudo vim.tiny /etc/systemd/system/rackmount_oled.service
</pre>
And then, adding following lines:
<pre>
[Unit]
Description=Rackmount OLED service on RPi5
DefaultDependencies=no
StartLimitIntervalSec=60
StartLimitBurst=5

[Service]
Type=simple
ExecStart=/bin/bash /home/pi/start_led.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
</pre>
Save it and quit.
===Enable rackmount_oled.service===
* reload daemon
<pre>
sudo systemctl daemon-reload
</pre>

* Enable service
<pre>
sudo systemctl enable rackmount_oled.service
</pre>
* Start service
<pre>
sudo systemctl start rackmount_oled.service
</pre>
* Restart service
<pre>
sudo systemctl restart rackmount_oled.service
</pre>
* Stop service
<pre>
sudo systemctl stop rackmount_oled.service
</pre>
* Disable service
<pre>
sudo systemctl disable rackmount_oled.service
</pre>

==How to enable PCIe function on Raspberry Pi 5?==
* To enable PCIe functionality on the Raspberry Pi 5, follow these steps:

===1. Enable the PCIe External Connector:===
By default, the PCIe connector on the Raspberry Pi 5 is not enabled. To enable it, you need to add a configuration parameter to the `config.txt` file located in the `/boot/firmware` directory. You can use either of these lines:
<pre>
dtparam=pciex1
</pre>
After adding the line, reboot your Raspberry Pi for the changes to take effect.

===2.Enable PCIe Gen 3.0 (Optional):===
The Raspberry Pi 5's PCIe connection is certified for Gen 2.0 speeds. However, if you want to attempt using Gen 3.0 speeds, add the following line to the `config.txt` file as well:
<pre>
dtparam=pciex1_gen=3
</pre>
Be aware that the Raspberry Pi 5 is not certified for Gen 3.0 speeds, and using this setting may result in instability .

===3.Booting from PCIe:===
If you intend to boot from a device connected via PCIe, such as an NVMe SSD, you will need to modify the boot order in the EEPROM. Use the following command to edit the EEPROM configuration:
<pre>
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-config --edit
</pre>
Then, change the `BOOT_ORDER` line to include NVMe in the boot order:
<pre>
BOOT_ORDER=0xf416
</pre>
This setting will make the Raspberry Pi attempt to boot from an NVMe device connected to the PCIe port .
===4. Kernel Compilation (Advanced):===
If you need to compile the kernel to add support for specific PCIe devices, you can follow the steps outlined in the Raspberry Pi documentation. This involves cloning the Raspberry Pi kernel repository, configuring the kernel with `make menuconfig`, and enabling the necessary modules for your devices .
Remember to always check the compatibility of the devices you intend to use with the Raspberry Pi 5's PCIe interface, as not all devices may be supported out of the box.

==How to light up identical LED? ==
To light up UID LED indicator on a Raspberry Pi 5, you'll make sure the GPIO Pin of the UID LED connected to.
<pre>
GPIO (General Purpose Input/Output) pins on the Raspberry Pi.
</pre>

===Steps===
* 1. Identify GPIO Pins: <font color=red>GPIO4</font><br>

* 2. Power On:
Make sure your Raspberry Pi is powered off before connecting the LED. Once everything is connected, you can power on your Raspberry Pi.

* 3. Software Setup:
You'll need to write a small program to turn the GPIO pin on and off to control the LED. You can use Python with the `gpiozero` library or `RPi.GPIO` library to control the GPIO pins.

===Example Python Code with gpiozero:===
<pre>
from gpiozero import LED
from time import sleep

led = LED('GPIO4')

while True:
led.on()
sleep(1)
led.off()
sleep(1)
</pre>

===Example Python Code with RPi.GPIO:===
<pre>
import RPi.GPIO as GPIO
import time

# Set the GPIO mode
GPIO.setmode(GPIO.BCM)

GPIO_PIN = 4

# Set up the GPIO pin as an output channel
GPIO.setup(GPIO_PIN, GPIO.OUT)

while True:
GPIO.output(GPIO_PIN, GPIO.HIGH) # Turn on the LED
time.sleep(1)
GPIO.output(GPIO_PIN, GPIO.LOW) # Turn off the LED
time.sleep(1)

# Clean up the GPIO pins before exiting the program
GPIO.cleanup()
</pre>

===Safety Tips:===
* Be careful not to short any pins on the Raspberry Pi.

==FAQ==
* SSD1306 OLED Black-Screen Debugging Report & Operation Guide

<strong>Target hardware:</strong> 0.91" OLED, 128×32 px, SSD1306, I2C, address 0x3C, Raspberry Pi 5
<strong>Software:</strong> luma.oled 3.15.0, luma.core 2.6.0, Python 3.13, smbus2

=== 1. Executive Summary — What Was Actually Wrong ===

<strong>Nothing was wrong with the code, the luma library, or the SSD1306 register configuration.</strong>
No library or example source code was modified. The failures came from hardware and
configuration, in three layers:

1. <strong>Two defective display modules.</strong> The driver IC responded on I2C and executed
commands correctly, but the panel itself never lit — dead charge-pump / flex-cable /
panel. The first module had worked before and died of age; the replacement (0.96")
showed the identical signature, indicating a bad batch.
2. <strong>A supply-voltage trap.</strong> Modules with an onboard AMS1117 regulator (~1.1 V dropout)
must be fed <strong> 5V</strong> ; at 3.3 V the logic still works (so the chip ACKs and responds,
which is very misleading) but the charge pump cannot start → black screen. Bare
modules with <strong> no regulator must use 3.3 V</strong> ; feeding them 5 V does not work and risks
damage. The final working module is a bare one and runs correctly at 3.3 V.
3. <strong>A parameter mismatch in the examples.</strong> The examples in this directory default to
`ssd1305 / 128×64`; this panel is `ssd1306 / 128×32`. Running without parameters
produces a black or garbled screen. The fix is to pass the correct display, interface,
geometry and address — done via the config file `ssd1306_128x32.conf`.

=== 2. What Was Done, Step by Step (Method and Basis)===

{| class="wikitable"
|+ Diagnosis — locating the fault
! Method !! Basis / Reasoning
|-
| Bus scan with <code>i2cdetect</code> || An ACK at 0x3C proves all four wires
(VCC/GND/SDA/SCL) are connected and the driver IC is powered
|-
| Source inspection of ssd1306 in luma.oled 3.15.0 || The 128×32 init sequence
(multiplex 0x1F, compins 0x02, charge pump 0x14) matches the datasheet standard — a
register-level bug was ruled out on evidence
|-
| Raw-register write of 0xA5 (force all-on) || This command bypasses GDDRAM; a
healthy panel must glow. No light = fault in the high-voltage path (charge pump /
panel / flex cable)
|-
| Status-register read before/after DISPLAY ON/OFF commands || Per the SSD1306
datasheet, bit 6 is the display ON/OFF flag. It flipped correctly, proving the chip
executes commands — fault isolated to the panel side
|-
| 5 consecutive bus scans + 10 consecutive status reads || All values stable and
identical — ruled out loose wiring and parasitic power
|-
| 3.3V / 5V supply switching test || Modules with an AMS1117 regulator require 5V;
bare modules without a regulator require 3.3V. The working module lit at 3.3V
|}

===3. Files Created / Modified===

{| class="wikitable"
|+ Fixes and deliverables
! File !! Type !! Description
|-
| <code>ssd1306_128x32.conf</code> || Fixed || Initially written in INI format,
causing "unrecognized arguments". Based on the source of
<code>luma.core.cmdline.load_config</code> (reads line by line, no whitespace
splitting), rewritten as one <code>--key=value</code> per line; demo.py then ran
successfully
|-
| <code>ssd1306_raw.py</code> || Created || Library-free SSD1306 driver; writes
registers directly via smbus2 (PIL used only for pixel rendering)
|-
| <code>OLED_128x32_I2C_manual.md</code> || Created / updated || Bilingual
operation manual; added the regulator/supply-voltage rule and the hardware-failure
criterion
|-
| <code>SSD1306_Debug_Report_EN.md</code> || Created || Full English debugging
report and operation guide
|}

No files in luma.oled / luma.core or the example scripts were modified.

===4. Final Working Configuration===

* Module: bare 0.91" 128×32 SSD1306, <strong>no onboard regulator</strong>
* Wiring: VCC → <strong>3.3 V</strong> (pin 1), GND → GND, SDA → GPIO2 (pin 3), SCL → GPIO3 (pin 5)
* No RST/RES connection needed (I2C interface)
* I2C address: `0x3C`

=== 5. Operating Instructions===

==== Run any luma example in this directory====

<pre>
python demo.py -f ssd1306_128x32.conf
python clock.py -f ssd1306_128x32.conf
python pi_logo.py -f ssd1306_128x32.conf
</pre>

Or pass parameters explicitly:

<pre>
python demo.py -d ssd1306 -i i2c --i2c-port 1 --i2c-address 0x3c --width 128 --height 32
</pre>

===Run the library-free raw driver===
<pre>
python ssd1306_raw.py # 0.96" 128x64
python ssd1306_raw.py --height 32 # 0.91" 128x32 (this panel)
python ssd1306_raw.py --addr 0x3D # modules with address 0x3D
</pre>
=== Minimal code (luma)===

<pre>
from luma.core.interface.serial import i2c
from luma.oled.device import ssd1306
from luma.core.render import canvas

device = ssd1306(i2c(port=1, address=0x3C), width=128, height=32)
with canvas(device) as draw:
draw.rectangle(device.bounding_box, outline="white")
draw.text((4, 10), "OK 128x32", fill="white")
</pre>

===6. Black-Screen Decision Tree (for future modules)===

* `i2cdetect -y 1` shows the address?
<strong>No</strong> → power/wiring fault: measure VCC-GND **at the module's solder pads**, check SDA=pin 3, SCL=pin 5, try fresh dupont wires.
<strong>Yes</strong> → continue.

* Run `python oled_diagnose.py`. Any step lights the panel?
<strong>Yes</strong> → software/parameter issue; use the matching parameters (`-d ssd1306 --width 128 --height 32 --i2c-address 0x3c`).
<strong>No</strong> → continue.

* Status-register test: does bit 6 flip after `0xAF`/`0xAE`?
<strong>Yes</strong> (chip executes commands, panel still dark) → charge pump/panel hardware. Check whether the module has a regulator: AMS1117 → power with **5 V**; no regulator → power with **3.3 V**. Still dark at the correct voltage → defective module, return it.
<strong>No</strong> → module-level fault (reset circuit / dead IC), return it.

==Keywords==
* 1U Rackmount for Raspberry Pi 5 with M.2 NVMe SSD support.

DR-0001

2026-08-19T03:00:52Z

Yoyojacky: /* Install SSD1306 driver libarary for OLED 0.91 */

==1U Rackmount for Raspberry Pi 5 ==
* Purchase URL: [ https://52pi.com ] or [ https://deskpi.com ]
[[File:DR-0001-1.jpg|right|320px]]

==Description==
This is an upgraded version of a 1U Rackmount designed for compatibility with both Raspberry Pi 5 . It features a motherboard that supports PCIe expansion, allowing the PCIe interface of the Raspberry Pi 5 to be extended to accommodate an M.2 NVMe SSD in 2230/2242/2260/2280 form factors. The expansion board also routes the Raspberry Pi's 5V and GND, SDA, and SCL pins to the rear through PogoPin connectors, providing I2C interface peripherals in a Grove format. Additionally, a red LED is included on the board for the Raspberry Pi ID signal pin, which can be programmed to indicate the current device by controlling the GPIO4 pin's high or low level, acting as a programmable device ID signal light.

The Rackmount supports the connection of up to five Raspberry Pi devices and can also be configured with an OLED display frame in place of one of the Raspberry Pi slots. These components can be easily adjusted and removed due to the use of hand-tightened screws. The OLED display features a 0.91-inch screen and communicates with the Raspberry Pi via I2C protocol, displaying real-time information such as CPU status, memory status, IP information, and serial numbers. The content displayed on the OLED can be fully customized.
==Features==
* <strong>Compatibility:</strong> Designed to work with both Raspberry Pi 5.
* <strong>PCIe Expansion Support:</strong> Includes a motherboard that enables PCIe expansion, allowing the connection of M.2 NVMe SSDs in various form factors (2230/2242/2260/2280).
* <strong>I2C Interface: </strong> The board routes the Raspberry Pi's 5V, GND, SDA, and SCL pins to the rear through PogoPin connectors, offering I2C interface peripherals in a Grove format.
* <strong>Programmable LED Indicator: </strong> A red LED on the board serves as a programmable device ID signal, controllable via the GPIO4 pin to indicate the status or identity of the device.
* <strong>Modular Design:</strong> Supports the integration of up to five Raspberry Pi devices, with the option to replace one slot with an OLED display frame.
* <strong>OLED Display Integration:</strong> The option to include a 0.91-inch OLED screen that communicates with the Raspberry Pi via I2C, displaying customizable information such as CPU usage, memory status, IP address, and serial numbers.
* <strong>Easy Assembly and Disassembly:</strong> Components are secured with hand-tightened screws, allowing for convenient adjustments and removal.
* <strong>Customizable Display Content: </strong> The information displayed on the OLED screen can be fully customized to meet specific needs or preferences.
* <strong>Rackmount Form Factor: </strong> Designed to fit into a 1U rack space, making it suitable for data centers or other environments where space is at a premium.
* <strong>Versatility:</strong> The Rackmount can be configured in various ways to suit different use cases, whether for development, testing, or deployment in a production environment.
===Specifications===
* Form Factor: 1U Rackmount design suitable for standard 19-inch racks.
* Raspberry Pi Compatibility: Specifically designed for Raspberry Pi 5.
* PCIe Expansion:Supports M.2 NVMe SSDs in 2230, 2242, 2260, and 2280 form factors. Provides a PCIe interface for high-speed data transfer.
* I/O Connectivity: Rear I2C interface via PogoPin connectors for external peripherals.
* GPIO4 pin for programmable LED control.
* LED Indicator:Red LED for device identification or status indication. Programmable through software to show different statuses.
* Modular Bays: Five bays for Raspberry Pi devices. One bay can be replaced with an OLED display module.
* OLED Display Specifications:0.91-inch screen size, 128x32 pixels. I2C communication protocol.
* Customizable display for system information.
* Physical Security:Hand-tightened screws for secure mounting of Raspberry Pi devices and OLED display.
* Ensures stability and ease of maintenance.
* Power Requirements: Compatibility with Raspberry Pi's standard power supply.
* Material and Construction: Durable metal construction for the rackmount chassis. High-quality components for reliable performance.
* Mounting Options: Standard rackmount holes for easy installation into a rack.
* Includes additional mounting accessories for different setups.
* Software Compatibility: Compatible with Raspberry Pi's operating system and software ecosystem.
* Support for GPIO programming for custom LED and device control.
==Gallery==
* Product outlook
[[ File:DR-0001-6.jpg |left|800px]]
<br style="clear:both":>

* Application Senario
[[ File:DR-0001-2.jpg |left|800px]]
<br style="clear:both":>
<font color=red> NOTE: Raspberry Pis are not included in the package, additional purchase required!</font><br>
* Easy to assemble and maintain
[[ File:DR-0001-3.jpg |left|800px]]
<br style="clear:both":>
[[File:DR-0001-12.jpg|left|800px]]
<br style="clear:both":>

* Customizable OLED display screen, with a size of 0.91 inches
[[ File:DR-0001-4.jpg |left|800px]]
<br style="clear:both":>

* Ports Definitions and Featrues
Programmable I/O controlled UID indicator light, which can be programmed to control the LED blinking to indicate the device's location, facilitating faster troubleshooting and easier maintenance operations.
[[ File:DR-0001-5.jpg |left|800px]]
<br style="clear:both":>

===How to connect OLED display to Raspberry Pi on GPIO pins===
* Please refer to following figure to connect OLED display to Raspberry Pi on GPIO.
<font color=red>NOTE: OLED's VCC should be connected to 3.3V power rail, Do not connect it to 5V power rail!!!</font><br>
[[ File:DR-0001-7.jpg |left|800px]]
<br style="clear:both":>

* Grove Connector Support I2C and Uart
[[ File:DR-0001-8.jpg |left|800px]]
<br style="clear:both":>

* Accessories Dimension
[[ File:DR-0001-9.jpg |left|800px]]
<br style="clear:both":>

* OLED assemble details
Please remove the protection film from acrylic panel and use the washer between OLED PCB board and acrylic panel.
[[ File:DR-0001-10.jpg |left|800px]]
<br style="clear:both":>

* PCIe Expansion board for Raspberry Pi 5 only
The expansion board supports M.2 NVMe M-key SSD 2230/2242/2260/2280, and the board will be powered by Raspberry Pi 5 via PogoPin on the PCB board, please make sure the board's pogoins are contact well with the soldering point on back of the Raspberry Pi 5 on GPIO pins.
[[File:DR-0001-11.jpg|left|800px]]
<br style="clear:both":>

==How to assemble it? ==
* Please note that there are several details you need to pay attention, plesae check out following figure.
[[ File:DR-0001-安装.jpg|left|800px]]
<br style="clear:both";>

==Package Includes==
* Following figure shows the details of the product:
[[ File:DR-0001-清单.jpg|left|800px]]
<br style="clear:both";>

==How to enable I2C OLED display?==
* We assume that you are using Raspberry Pi OS 64bit(bookworm, the latest official image)
To enable I2C and UART on your Raspberry Pi, you can follow these detailed steps:

===Enabling I2C===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
to open the configuration tool. Navigate to `Interface Options`, Select `I2C` and enable it.

* Method 2. Using the Command Line:
You can also enable I2C by editing the `/boot/firmware/config.txt` file and adding `dtparam=i2c_arm=on` if it's not already present, After making changes, reboot your Pi.

===Verifying I2C===
* Install I2C tools using `sudo apt-get install -y i2c-tools`.
* Use
<pre>
i2cdetect -y 1
</pre>
to scan for I2C devices, if you see `3c` means that the OLED display has been recognized by your Raspberry Pi.

===Enabling UART===
* Method 1. Using the Raspberry Pi Configuration Tool:
<pre>
sudo raspi-config
</pre>
Go to `Interface Options`, Select `Serial` and enable it.
<pre> Note: This will also enable the login shell on the serial port. </pre>

* Method 2. Using the Command Line:
Edit `/boot/config.txt` and add `enable_uart=1`, save it and then reboot your Pi.

===Accessing UART===
* Connect your Pi to a USB-to-TTL converter, On Windows, you may need to install drivers for the converter. on Linux just use a terminal program like `minicom`, `putty`, or `screen` to access the UART interface.

Remember to check the documentation for your specific Raspberry Pi model, as the steps might vary slightly. If you need more detailed instructions or encounter any issues, refer to the [ https://www.raspberrypi.org/documentation/ ] or community forums for additional support.

===How to display customized information on OLED display? ===
* Final result
[[File:DR-0001 applications-01.jpg|left|800px]]
<br style="clear:both";>
==How to customize content on OLED ?==
* For example: If you want to display current IP address of wlan interface and the serial number of your Raspberry Pi 5, please follow next steps to configure it.
===Install Virtal environment package ===
* Open a terminal and typing following commands:
<pre>
sudo apt update
sudo apt upgrade -y
sudo apt -y install virtualenv
sudo usermod -a -G i2c,spi,gpio pi
sudo apt install python3-dev python3-pip python3-numpy libfreetype6-dev libjpeg-dev build-essential
sudo apt install libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev libsdl2-ttf-dev libportmidi-dev
</pre>
[[File:Install pre-insistpackages.png|left|800px]]
<br style="clear:both";>
[[File:Install-pre-insistpackage-02.png|left|800px]]
<br style="clear:both";>

===Create virtual environment===
<pre>
virtualenv -p python3 venv
cd venv/
source bin/activate
</pre>
===Install SSD1306 driver and library for OLED 0.91===
<pre>
pip install luma.oled
pip install psutil
</pre>

===Clone luma.examples repository===
Log out and in again and clone this repository:
<pre>
git clone https://github.com/rm-hull/luma.examples.git
cd luma.examples/
</pre>
===Install luma libraries===
<pre>
sudo -H pip install -e . --break-system-packages
</pre>
[[File:Install luma libraries.png|left|800px]]
<br style="clear:both";>
===Test the demo ===
<pre>
cd examples/
sudo python 3d_box.py --width=128 --height=32 -r 2
</pre>

<font color=red><p>NOTE: <br>
--width=128 and --height=32 should be added to declear the OLED's resolution information. <br>
-r 2 means --rotate 2 , Allowed values are: 0, 1, 2, 3 (default:0)
</p>
</font>
If you see a 3D-box rotating animation is in the middle of screen means that you have installed the OLED driver successfully!
[[File:Test demo 3dbox.png|left|800px]]
<br style="clear:both";>
[[File:Test demo 3dbox-2.png|left|800px]]
<br style="clear:both";>
and then press "Ctrol+C" abort the demo.

==Use the demo code==
* There are a lot of demo codes in the examples folder, you can test it as you want.
for example:
<pre>
sudo python carousel.py --width=128 --height=32 -r 2
</pre>
It will display all information of your Raspberry Pi 5 and scrolling display.
===Customize the display on screen===
Modify the sys_info.py python file and adding your own function to show the information you want, do remember backup the origin file.
<pre>
cp sys_info.py sys_info.py.bak
vim.tiny sys_info.py
</pre>
Press 'i' to insert mode, and paste following lines into it. you can modify this file by other text editor what you like.
<pre>
#!/usr/bin/env python
# -*- coding: utf-8 -*-
# Copyright (c) 2014-2022 Richard Hull and contributors
# See LICENSE.rst for details.
# PYTHON_ARGCOMPLETE_OK

"""
Display basic system information.

Needs psutil (+ dependencies) installed::

$ sudo apt-get install python-dev
$ sudo -H pip install psutil
"""

import os
import sys
import time
from pathlib import Path
from datetime import datetime
import subprocess as sp

if os.name != 'posix':
sys.exit(f'{os.name} platform is not supported')

from demo_opts import get_device
from luma.core.render import canvas
from PIL import ImageFont

try:
import psutil
except ImportError:
print("The psutil library was not found. Run 'sudo -H pip install psutil' to install it.")
sys.exit()

# TODO: custom font bitmaps for up/down arrows
# TODO: Load histogram

def bytes2human(n):
"""
>>> bytes2human(10000)
'9K'
>>> bytes2human(100001221)
'95M'
"""
symbols = ('K', 'M', 'G', 'T', 'P', 'E', 'Z', 'Y')
prefix = {}
for i, s in enumerate(symbols):
prefix[s] = 1 << (i + 1) * 10
for s in reversed(symbols):
if n >= prefix[s]:
value = int(float(n) / prefix[s])
return '%s%s' % (value, s)
return f"{n}B"

def cpu_usage():
# load average, uptime
uptime = datetime.now() - datetime.fromtimestamp(psutil.boot_time())
#av1, av2, av3 = os.getloadavg()
#return "Ld:%.1f %.1f %.1f Up: %s" \
# % (av1, av2, av3, str(uptime).split('.')[0])
return "Up: %s" % (str(uptime).split('.')[0])

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def mem_usage():
usage = psutil.virtual_memory()
return "Mem: %s %.0f%%" \
% (bytes2human(usage.used), 100 - usage.percent)

def disk_usage(dir):
usage = psutil.disk_usage(dir)
return "SD: %s %.0f%%" \
% (bytes2human(usage.used), usage.percent)

def network(iface):
stat = psutil.net_io_counters(pernic=True)[iface]
return "%s: Tx%s, Rx%s" % \
(iface, bytes2human(stat.bytes_sent), bytes2human(stat.bytes_recv))

def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi

def stats(device):
# use custom font
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
#font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'DejaVuSansMono.ttf'))
font2 = ImageFont.truetype(font_path, 15)

with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white")
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white")

if device.height >= 64:
draw.text((0, 26), disk_usage('/'), font=font2, fill="white")
try:
draw.text((0, 38), network('wlan0'), font=font2, fill="white")
except KeyError:
# no wifi enabled/available
pass

def main():
while True:
stats(device)
time.sleep(5)

if __name__ == "__main__":
try:
device = get_device()
main()
except KeyboardInterrupt:
pass
</pre>
Here let me explain to you what i did.
* adding " import subprocess as sp", this will help me to execute some shell command in OS.
* adding following parts:
<pre>
def get_ip_address():
ip = sp.getoutput('hostname -I')
return "IP: %s" % ip

def get_id():
id_of_pi = sp.getoutput("cat /proc/cpuinfo | grep -i serial| awk -F: '{print $2}'|xargs")
return "%s" % id_of_pi
</pre>
* get_ip_address will execute the command "hostname -I" in system and grab the IP address and return it to main process.
* get_id is to read /proc/cpuinfo file and grab the serial number and return to main process.

===Use custom font===
<pre>
font_path = str(Path(__file__).resolve().parent.joinpath('fonts', 'C&C Red Alert [INET].ttf'))
font2 = ImageFont.truetype(font_path, 15) # change font size to 15.
</pre>
===Modify the draw function===
<pre>
with canvas(device) as draw:
# draw.text((0, 0), cpu_usage(), font=font2, fill="white")
draw.text((0, 0), get_id(), font=font2, fill="white") #####　draw id on screen at (0,0) position, (x,y)
if device.height >= 32:
#draw.text((0, 11), mem_usage(), font=font2, fill="white")
#draw.text((0, 16), disk_usage('/'), font=font2, fill="white")
draw.text((0, 16), get_ip_address(), font=font2, fill="white") ####　draw text on (0,16) with IP address.
</pre>

==How to create a systemd file to make it automatically start at boot up==
* Step1. create a shell script called it 'start_led.sh'
<pre>
#!/bin/bash
#
cd /home/pi/venv/ && source /home/pi/venv/bin/activate
/usr/bin/python3 /home/pi/luma.examples/examples/sys_info.py --width=128 --height=32 -r 2
</pre>
save it and grant executable permission and test it.
<pre>
chmod +x start_led.sh
./start_led.sh
</pre>
If if works properly, just press "ctrol+c" to abort the test.
* Step2. create a systemd file and enable it.
<pre>
sudo vim.tiny /etc/systemd/system/rackmount_oled.service
</pre>
And then, adding following lines:
<pre>
[Unit]
Description=Rackmount OLED service on RPi5
DefaultDependencies=no
StartLimitIntervalSec=60
StartLimitBurst=5

[Service]
Type=simple
ExecStart=/bin/bash /home/pi/start_led.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
</pre>
Save it and quit.
===Enable rackmount_oled.service===
* reload daemon
<pre>
sudo systemctl daemon-reload
</pre>

* Enable service
<pre>
sudo systemctl enable rackmount_oled.service
</pre>
* Start service
<pre>
sudo systemctl start rackmount_oled.service
</pre>
* Restart service
<pre>
sudo systemctl restart rackmount_oled.service
</pre>
* Stop service
<pre>
sudo systemctl stop rackmount_oled.service
</pre>
* Disable service
<pre>
sudo systemctl disable rackmount_oled.service
</pre>

==How to enable PCIe function on Raspberry Pi 5?==
* To enable PCIe functionality on the Raspberry Pi 5, follow these steps:

===1. Enable the PCIe External Connector:===
By default, the PCIe connector on the Raspberry Pi 5 is not enabled. To enable it, you need to add a configuration parameter to the `config.txt` file located in the `/boot/firmware` directory. You can use either of these lines:
<pre>
dtparam=pciex1
</pre>
After adding the line, reboot your Raspberry Pi for the changes to take effect.

===2.Enable PCIe Gen 3.0 (Optional):===
The Raspberry Pi 5's PCIe connection is certified for Gen 2.0 speeds. However, if you want to attempt using Gen 3.0 speeds, add the following line to the `config.txt` file as well:
<pre>
dtparam=pciex1_gen=3
</pre>
Be aware that the Raspberry Pi 5 is not certified for Gen 3.0 speeds, and using this setting may result in instability .

===3.Booting from PCIe:===
If you intend to boot from a device connected via PCIe, such as an NVMe SSD, you will need to modify the boot order in the EEPROM. Use the following command to edit the EEPROM configuration:
<pre>
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-config --edit
</pre>
Then, change the `BOOT_ORDER` line to include NVMe in the boot order:
<pre>
BOOT_ORDER=0xf416
</pre>
This setting will make the Raspberry Pi attempt to boot from an NVMe device connected to the PCIe port .
===4. Kernel Compilation (Advanced):===
If you need to compile the kernel to add support for specific PCIe devices, you can follow the steps outlined in the Raspberry Pi documentation. This involves cloning the Raspberry Pi kernel repository, configuring the kernel with `make menuconfig`, and enabling the necessary modules for your devices .
Remember to always check the compatibility of the devices you intend to use with the Raspberry Pi 5's PCIe interface, as not all devices may be supported out of the box.

==How to light up identical LED? ==
To light up UID LED indicator on a Raspberry Pi 5, you'll make sure the GPIO Pin of the UID LED connected to.
<pre>
GPIO (General Purpose Input/Output) pins on the Raspberry Pi.
</pre>

===Steps===
* 1. Identify GPIO Pins: <font color=red>GPIO4</font><br>

* 2. Power On:
Make sure your Raspberry Pi is powered off before connecting the LED. Once everything is connected, you can power on your Raspberry Pi.

* 3. Software Setup:
You'll need to write a small program to turn the GPIO pin on and off to control the LED. You can use Python with the `gpiozero` library or `RPi.GPIO` library to control the GPIO pins.

===Example Python Code with gpiozero:===
<pre>
from gpiozero import LED
from time import sleep

led = LED('GPIO4')

while True:
led.on()
sleep(1)
led.off()
sleep(1)
</pre>

===Example Python Code with RPi.GPIO:===
<pre>
import RPi.GPIO as GPIO
import time

# Set the GPIO mode
GPIO.setmode(GPIO.BCM)

GPIO_PIN = 4

# Set up the GPIO pin as an output channel
GPIO.setup(GPIO_PIN, GPIO.OUT)

while True:
GPIO.output(GPIO_PIN, GPIO.HIGH) # Turn on the LED
time.sleep(1)
GPIO.output(GPIO_PIN, GPIO.LOW) # Turn off the LED
time.sleep(1)

# Clean up the GPIO pins before exiting the program
GPIO.cleanup()
</pre>

===Safety Tips:===
* Be careful not to short any pins on the Raspberry Pi.

==Keywords==
* 1U Rackmount for Raspberry Pi 5 with M.2 NVMe SSD support.

EP-0245

2026-08-05T06:09:24Z

Yoyojacky: /* Key Features */

==UPS Gen 6 power module compatible with Raspberry Pi 5/4B==
[[File:EP-0245-01.jpg|right|320px]]

==Description==
The UPS Gen 6 is the latest version of the UPS Plus series, designed for enhanced power management on Raspberry Pi or other SBCs. It supports up to 4 channels of 8.4V lithium battery packs in parallel and can be expanded with two 3.7V 18650 batteries in series. The device features intelligent power path management, prioritizing external power and switching to battery power during outages. It also supports real - time monitoring of battery status via I2C and custom firmware uploads through DFU. Additional features include programmable LEDs, a PikaPython interface for advanced monitoring, auto - restart on power recovery, safe shutdown countdown, and low - battery loop protection. UPS Gen 6 offers a versatile solution for your projects and will gain more features through future OTA firmware upgrades.
NOTE: For convenience, the UPS Gen 6 motherboard will be referred to as **upsv6** in our subsequent code links.
===Key Features===
* Bumpless Transfer
* Hard Disk Power Supply Interface
* Cooling System
* OTA Expansion for Additional Functions
* I2C Communication Interface
* PikaPython Script Execution Capability
* Physical Power Button
* With AC power connected: up to 80W max.
* On battery power (no load stress): up to 40W max.
<pre>
NOTE: Actual sustained output will vary depending on battery condition and operating temperature.</pre>

===Specifications===
* <strong>Device Compatibility:</strong> Supports Raspberry Pi and Orange Pi series devices.
* <strong>Expansion Battery Pack Support:</strong>Supports 18650 battery packs with two batteries in series, providing a typical voltage of 7.4V and a maximum voltage of 8.4V, with up to four parallel battery packs supported.
* <strong>Power Management:</strong> Bumpless Transfer, Full UPS (Uninterruptible Power Supply) characteristics, supporting seamless failover to battery power.
* <strong>Communication Interface: </strong>I2C protocol for battery and device status monitoring and controlling.
* <strong>DIY Features: </strong>Programmable LED control via configuring i2c registers.
* <strong>PikaPython support:</strong>PikaPython script interpreter for Python script injection.
* <strong>Power Recovery Settings: </strong>Configurable voltage thresholds for auto-restart.
* <strong>Safe shutdown timer:</strong> Saft shutdown timer to prevent data loss.
* <strong>OTA Upgrade Features:</strong>Get more feature via OTA upgrade.

===Compatibility Note===
<pre>
The screws, copper pillars, and other additional components of this product are primarily designed to fit the Raspberry Pi 5 and Raspberry Pi 4B. However, the product's functionality is compatible with other SBC (Single Board Computer) development boards on the market that are pin-compatible with the Raspberry Pi. If you need to install it smoothly, you may need to check whether the positioning hole locations match those of the Raspberry Pi 5 or Raspberry Pi 4B. Otherwise, it may not be physically compatible. This is hereby declared.
</pre>

===UPS features Details===
==== Feature 1: Auto Start Mode====
* Register: auto_start_mode
* Function: Enables automatic power-on logic when written.
* Conditions for Auto Start: when Battery voltage > auto_start_voltage and Valid external power source present
* Protection Mechanism: Monitors battery voltage after auto-start; If voltage drops to battery_protection_voltage multiple times:
<pre>
Auto-start attempts will be abandoned
</pre>

* Manual Shutdown by Button
<pre>
Auto clears auto_start_mode functionality
</pre>

==== Feature 2: Delayed Shutdown ====
* Register: shutdown_countdown
<pre>
Initiates shutdown after specified seconds when written.
</pre>
* <font color=red><strong> Important Notes</strong></font>
<pre>
Combined with active auto_start_mode: Functions as a reboot if conditions are met
For complete shutdown: Must clear auto_start_mode setting
</pre>

==== Feature 3: Runtime Tracking ====
* Register: runtime
* Unit: milliseconds (ms)
* Functionality: Tracks continuous operation time since last power-on

==== Feature 4: Force OTA Mode ====
* Register: ota_request
* Write value: <strong>0xA5A5</strong>
* Behavior: Immediately forces device into OTA mode

==== Feature 5: Physical Button Control====
* Current Implementation
Single button operation
Toggles power state immediately
<pre>
Note: It should be emphasized that it is not recommended to use the button to force power off, as this can cause file system damage, which is equivalent to forcibly shutting down a computer by pressing the power button.
</pre>
----
<font color=red><strong>Important Notice</strong></font><br>
* Immediate shutdown risks: Potential data loss
* Recommended method: Use shutdown_countdown for safe shutdown

==== Feature 6: L_FAST LED Indicators ====
{| class="wikitable"
|-
! LED State !! Meaning
|-
| Fast blinking || Bootloader mode
|-
| Solid on || Fast charging available
|-
| Slow blinking || UPS Fault
|-
|Off || No input power
|}

==Gallery==
* Product Outlook
[[File:EP-0245-01.jpg|left|800px]]
<br style="clear:both;">
* Back face
[[File:EP-0245-02.jpg|left|800px]]
<br style="clear:both;">
* Assembly status
[[File:EP-0245-03.jpg|left|800px]]
<br style="clear:both;">
* Port definitions
[[File:EP-0245-04.jpg|left|800px]]
<br style="clear:both;">
<br>
----
<font color=red><strong>Please note: When the 12v HDD power port is needed for external power supply,
an external PD power source and a battery need to be connected simultaneously.
Otherwise, the 12v HDD power port will not be able to supply power properly.</strong></font>
----
<br>
* Easy to install
[[File:EP-0245-05.jpg|left|800px]]
<br style="clear:both;">
* Heat dissipation effect
[[File:EP-0245-06.jpg|left|800px]]
<br style="clear:both;">
* External Power supply
[[File:EP-0245-07.jpg|left|800px]]
<br style="clear:both;">
[[File:EP-0245-08.jpg|left|800px]]
<br style="clear:both;">
* Standard Output for HDD (12V/5V)
[[File:EP-0245-09.jpg|left|800px]]
<br style="clear:both;">
* Mechanical Drawings
Unit: mm
* Bottom view
[[File:UPSGen6 MD01.png|left|800px]]
<br style="clear:both;">
* Front view
[[File:UPSGen6 MD02.png|left|800px]]
<br style="clear:both;">
* Top view
[[File:UPSGen6 MD03.png|left|800px]]
<br style="clear:both;">

==Package List==
* 1 x Aluminum Heatsink with Automatically controlled Fan.
* 1 x UPS Gen 6 mainboard
* 1 x A series connect battery case
* 1 x 4CM Battery Connector wire
* 1 x Acrylic battery base frame
* 1 x Metal battery base frame
* 1 x Copper pillar pack
* 1 x Flat heat screws pack (M2.5)
* 1 x UPS Gen 6 instructions
[[File:EP-0245-PL.jpg|left|800px]]
<br style="clear:both;">

==How to assemble it?==
* For Raspberry Pi 4B
[[File:EP-0245-IN-PI-4.jpg|left|800px]]
<br style="clear:both;" >
* For Raspberry Pi 5
[[File:EP-0245-IN-PI-5.jpg|left|800px]]
<br style="clear:both;" >
==YouTube Video==
* [ UPS Gen 6 power module compatible with Raspberry Pi 5/4B | https://youtu.be/zbpnDJvAF1s]

==User Manual==
*　<font color=red><strong>Please read the user manual carefully before proceeding.</strong></font>
----
<pre>This documentation assumes you are using a Raspberry Pi for testing. You can also use Orange Pi devices, but you will need to adjust the I2C controller address based on your specific setup. The default I2C device address for Raspberry Pi is /dev/i2c-1, while Orange Pi may use /dev/i2c-3. Adjust these settings according to your hardware.
</pre>
===The testing environment for this documentation includes:===
* Raspberry Pi 5
* 4 battery packs, each consisting of two fully charged 18650 lithium batteries connected in series to provide 8.4V.
* A 100W USB-C PD protocol charger.
* Raspberry Pi OS 64-bit Bookworm, updated to the latest version.

If you are using a different operating system, refer to its specific environment configuration. Note that we currently provide configuration guidance only for Raspberry Pi OS. For other systems, please resolve compatibility issues independently.

=== Register Summary Table ===
{| class="wikitable"
|-
! Address !! Name !! Width !! Access !! Description !! Default Value
|-
| 0x00 ||WHO_AM_I ||8 ||R　|| Device identification register || 0xA6
|-
| 0x01 ||version|| 8 || R || Version number || -
|-
|0x02 || uuid0 ||32 || R || Unique ID (lower 32 bits) || -
|-
|0x06 ||uuid1 ||32 || R || Unique ID (middle 32 bits) || -
|-
|0x0A ||uuid2 || 32 || R || Unique ID (upper 32 bits) || -
|-
|0x0E ||output_voltage || 16 || R || Output voltage (unit: mV, 5000mV output) || -
|-
|0x10 ||input_voltage ||16|| R|| Input voltage (unit: mV) || -
|-
|0x12 ||battery_voltage ||16 ||R || Battery voltage (unit: mV) || -
|-
|0x14 || mcu_voltage|| 16|| R || MCU voltage (unit: mV) || -
|-
|0x16 || output_current || 16 || R || Output current (unit: mA, 5V output) || -
|-
|0x18 ||input_current || 16 || R || Input current (unit: mA) || -
|-
|0x1A ||battery_current || 16 || R || Battery current (signed, unit: mA) || -
|-
|0x1C || temperature || 8 || R || Temperature (two's complement, unit: °C) || -
|-
|0x1D || CR1 || 8 || R/W || Control Register 1 || 0x01
|-
|0x1E || CR2 || 8 || R/W || Control Register 2 (Reserved) || 0x00
|-
|0x1F || SR1 || 8 || R || Status Register 1 || -
|-
|0x20 || SR2 || 8 || R || Status Register 2 || -
|-
|0x21 || battery_protection_voltage || 16 || R/W || Battery protection voltage (unit: mV) || 7400
|-
|0x23 || shutdown_countdown || 16 || R/W || Shutdown countdown (unit: seconds) || -
|-
|0x25 || auto_start_voltage || 16 || R/W || Auto-start voltage threshold (unit: mV) || 7400
|-
|0x27 || rsv || 16 || R/W || Python output buffer content length || -
|-
|0x29 || ota_request || 16 || W || Writing to 0xA5A5 will request OTA mode. || -
|-
|0x2B || runtime || 64 || R || Cumulative runtime (unit: millisecond) || -
|-
|0x33 || charge_detect_interval_s || 16 || R/W || Charge detection interval (unit: seconds) || -
|-
|0x35 || led_ctl || 8 || R/W || LED control register || 0x01
|}

=== Control Register CR1 (Address: 0x1D) ===
{| class="wikitable"
|-
! Bit !! Name !! Access !! Description !! Default Value
|-
|BIT0 || auto_start_mode || R/W || Auto-start mode (0=disabled, 1=enabled) || 1

|}

===Status Register SR1 (Address: 0x1F)===
{| class="wikitable"
|-
! Bit !! Name !! Access !! Description !! Default Value
|-
| BIT0 || sw_status || R || 5V output status (0=off, 1=on) || -
|-
|BIT1 || fast || R || Fast charging status (0=slow charging/no external power, 1=12V fast charging)|| -
|-
|BIT2 || charge || R || Charge/discharge status (0=charging, 1=discharging) || -
|-
|BIT3 || input_low || R || Input voltage low (0=normal, 1=low) || -
|-
|BIT4 || output_low || R || 5V output low (0=normal, 1=low) || -
|-
|BIT5 || battery_low || R || Battery voltage low (0=normal, 1=low) || -
|-
|BIT6 || adc_mismatch || R || ADC mismatch (0=normal, 1=INA219 vs MCU sampling difference exceeded) || -
|-
|BIT7 || battery_fail || R || Battery failure (0=normal, 1=failure) || -
|}

===Status Register SR2 (Address: 0x20)===
* Not Avaliable right now.

===LED Control Register （Address: 0x35)===
{| class="wikitable"
|-
! Bit !! Name !! Access !! Description !! Default Value
|-
| BIT0 || i2c_ack|| R/W || LED on during I2C communication || 1
|-
| BIT1 || bat_charge || R/W || LED on during battery charging || 0
|-
| BIT2 || bat_discharge || R/W || LED on during battery discharging || 0
|-
| BIT3 || fault_report|| R/W || LED on when fault detected || 0
|-
| BIT4 || ok_report|| R/W || LED on during normal operation || 0

|}

===Special Notes===
* Data Format:
<pre>
Voltage/current values are unsigned integers
battery_current is signed (two's complement format)
temperature is signed 8-bit integer (two's complement), range: -40°C to +85°C
</pre>
* Reserved Bits:
<pre>
All reserved bits default to 0
Write operations to reserved bits are ignored (recommended to maintain default values)
</pre>
* The register definitions in the bootloader state are not fully compatible.
===Getting Start===
* Assume that your Device Environment: Raspberry Pi 5, operating system: Raspberry Pi OS 64-bit (Bookworm).
* Assume that your Raspberry Pi 5 can access internet including GitHub.
* Assume that you have already assembled the UPS v6 with your Raspberry Pi 5 and booting up properly.
* Please refer to the following steps for operation:
====Install Dependencies package and libraries====
* Open a terminal and typing:
<pre>
sudo apt update
sudo apt upgrade -y
sudo apt -y install build-essential cmake libi2c-dev libssl-dev gcc-arm-none-eabi git wget vim virtualenv i2c-tools
</pre>

=== Download Demo codes repository ===
* In order to use this module easily, I recommend you download the repository from GitHub, URL: [ https://github.com/geeekpi/upsv6_pub.git ]
* Download to Raspberry Pi 5 locally, you need to open a terminal and typing following commands:
<pre>
cd ~/
git clone https://github.com/geeekpi/upsv6_pub.git
</pre>
or just open a browser and access this URL: [ https://github.com/geeekpi/upsv6_pub.git ], click `code` -> click `Download ZIP` and then extract the contents to your Raspberry Pi 5 on desktop.
[[File:Downloadrepo.png|left|800px]]
<br style="clear:both;">

===Upload new firmware===
* Step 1. Enter into OTA mode
* Step 2. Upload new firmware_encrypted.bin file
<pre>
python enable_ota.py
</pre>
Check if the UPS v6 has been entered into OTA mode:
<pre>
i2cdetect -y 1
</pre>
If the i2c device address is changed from 0x17 to 0x18 means UPS Gen 6 is already in OTA mode.
<pre>
./user_write_tool firmware_encrypted.bin
</pre>
Until you see following figure:
[[File:Flash complete.png|left|800px]]
<br style="clear:both;">

===Push button status===
* Push button will keep the status after last operation.

==How to read UPS status==
* Step 1. Download repository by using git command, open a terminal and typing following command:
<pre>
cd ~
git clone https://github.com/geeekpi/upsv6_pub.git
cd upsv6_pub/
</pre>
* Step 2. Enable I2C function by using raspi-config command:
<pre>
sudo raspi-config
</pre>
Navigate to 3 Interface Options -> I2C -> YES -> OK -> Finished
* Step 3. Execute Python script
<pre>
python script/tools/python_demo/read_device_basic_demo.py
</pre>
==How to calculate input and output power? ==
To calculate the input and output power using the values read from the registers, you need to follow these steps:
* Read the voltage and current values from the respective registers.
* Convert the voltage from millivolts (mV) to volts (V) by dividing by 1000.
* Convert the current from milliamperes (mA) to amperes (A) by dividing by 1000.
* Calculate the power using the formula:
<pre>Power (W)=Voltage (V)×Current (A)</pre><br>

Here is the modified Python code that includes the calculation of input and output power:
<pre>
from smbus2 import SMBus
import time

# Device address
DEVICE_ADDRESS = 0x17

# init SMBus
bus = SMBus(1) # 1 means I2C no.1 bus

# Define registers address
# WHO_AM_I_REG = 0x00 // will always be 0xA6
VERSION_REG = 0x01
UID0_REG = 0x02
UID1_REG = 0x06
UID2_REG = 0x0A
OUTPUT_VOLTAGE_REG = 0x0E
INPUT_VOLTAGE_REG = 0x10
BATTERY_VOLTAGE_REG = 0x12
MCU_VOLTAGE_REG = 0x14
OUTPUT_CURRENT_REG = 0x16
INPUT_CURRENT_REG = 0x18
BATTERY_CURRENT_REG = 0x1A
TEMPERATURE_REG = 0x1C

# Define ANSI color
RED = '\033[95m'
GREEN = '\033[92m'
END_COLOR = '\033[0m'

# read 8bit register
def read_byte_register(register_address):
value = bus.read_byte_data(DEVICE_ADDRESS, register_address)
if value > 127:
value -= 256
return value

# read 16bit register
def read_word_register(register_address):
value = bus.read_word_data(DEVICE_ADDRESS, register_address)
if value > 32767:
value -= 65536
return value

# read 32bit register
def read_dword_register(register_address):
low = bus.read_word_data(DEVICE_ADDRESS, register_address)
high = bus.read_word_data(DEVICE_ADDRESS, register_address + 2)
return (high << 16) | low

# read all registers data
def read_all_registers():
registers = {
"WHO_AM_I": "0xA6",
"VERSION": read_byte_register(VERSION_REG),
"UID0": read_dword_register(UID0_REG),
"UID1": read_dword_register(UID1_REG),
"UID2": read_dword_register(UID2_REG),
"OUTPUT_VOLTAGE": read_word_register(OUTPUT_VOLTAGE_REG),
"INPUT_VOLTAGE": read_word_register(INPUT_VOLTAGE_REG),
"BATTERY_VOLTAGE": read_word_register(BATTERY_VOLTAGE_REG),
"MCU_VOLTAGE": read_word_register(MCU_VOLTAGE_REG),
"OUTPUT_CURRENT": read_word_register(OUTPUT_CURRENT_REG),
"INPUT_CURRENT": read_word_register(INPUT_CURRENT_REG),
"BATTERY_CURRENT": read_word_register(BATTERY_CURRENT_REG),
"TEMPERATURE": read_byte_register(TEMPERATURE_REG)
}
return registers

# Calculate power
def calculate_power(voltage_mv, current_ma):
# Convert mV to V and mA to A
voltage_v = voltage_mv / 1000.0
current_a = current_ma / 1000.0
# Calculate power in watts
power_w = voltage_v * current_a
return power_w

# read and print out all registers data.
try:
while True:
print(f"{RED}=== 52Pi UPS V6 Raw Data Output ==={END_COLOR}")
registers = read_all_registers()

# Extract voltage and current values
input_voltage_mv = registers["INPUT_VOLTAGE"]
input_current_ma = registers["INPUT_CURRENT"]
output_voltage_mv = registers["OUTPUT_VOLTAGE"]
output_current_ma = registers["OUTPUT_CURRENT"]

# Calculate input and output power
input_power_w = calculate_power(input_voltage_mv, input_current_ma)
output_power_w = calculate_power(output_voltage_mv, output_current_ma)

# Print all register values
for key, value in registers.items():
if "VOLTAGE" in key:
print(f"* {key}: {GREEN}{value}mV{END_COLOR} ")
elif "CURRENT" in key:
print(f"* {key}: {RED}{value}mA{END_COLOR} ")
elif "TEMPERATURE" in key:
print(f"* {key}: {GREEN}{value}C{END_COLOR} ")
elif "WHO_AM_I" in key:
print(f"* {key}: {value}")
else:
print(f"* {key}: {value}")

# Print calculated power values
print(f"* INPUT_POWER: {GREEN}{input_power_w:.2f}W{END_COLOR}")
print(f"* OUTPUT_POWER: {RED}{output_power_w:.2f}W{END_COLOR}")

print("-"*80)
print(" "*80)
time.sleep(2) # flush interval in 2 seconds
except KeyboardInterrupt:
# Shutdown SMBus
bus.close()
print("Quit Demo")
</pre>
Save it and execute it by using :
<pre>
python calculate_power.py
</pre>
You will see the result on ternimal:
[[File:Calculate power.jpg|left|800px]]
<br style="clear:both">
===Explanation of Power Calculation===
* Reading Voltage and Current:
The voltage and current values are read from the respective registers in millivolts (mV) and milliamperes (mA).
* Unit Conversion:
The voltage is converted from millivolts to volts by dividing by 1000. <br>
The current is converted from milliamperes to amperes by dividing by 1000.
* Power Calculation:
The power is calculated using the formula:
<pre> Power (W)=Voltage (V)×Current (A)</pre>
This ensures that the power is correctly calculated in watts.
* Output:
The calculated input and output power values are printed in watts, formatted to two decimal places.
This code will continuously read the register values, calculate the input and output power, and print the results every 2 seconds.

==How to send the UPS Gen 6's data to Home assistant==
===Modify the configuration on Home assistant===
* Please find the home assistant configuration.yaml file and adding following lines, In my case, I have use a docker container for my home assistant application.
<pre>
sudo vim /opt/homeassistant/configuration.yaml
</pre>
adding:
<pre>
# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

mqtt:
sensor:
- name: "OUTPUT_VOLTAGE"
state_topic: "ups_status/OUTPUT_VOLTAGE"
unit_of_measurement: "mV"
value_template: "{{ value | int }}"

- name: "OUTPUT_CURRENT"
state_topic: "ups_status/OUTPUT_CURRENT"
unit_of_measurement: "mA"
value_template: "{{ value | int }}"

- name: "INPUT_VOLTAGE"
state_topic: "ups_status/INPUT_VOLTAGE"
unit_of_measurement: "mV"
value_template: "{{ value | int }}"

- name: "BATTERY_VOLTAGE"
state_topic: "ups_status/BATTERY_VOLTAGE"
unit_of_measurement: "mV"
value_template: "{{ value | int }}"

- name: "MCU_VOLTAGE"
state_topic: "ups_status/MCU_VOLTAGE"
unit_of_measurement: "mV"
value_template: "{{ value | int }}"

- name: "INPUT_CURRENT"
state_topic: "ups_status/INPUT_CURRENT"
unit_of_measurement: "mA"
value_template: "{{ value | int }}"

- name: "BATTERY_CURRENT"
state_topic: "ups_status/BATTERY_CURRENT"
unit_of_measurement: "mA"
value_template: "{{ value | int }}"

- name: "TEMPERATURE"
state_topic: "ups_status/TEMPERATURE"
unit_of_measurement: "C"
value_template: "{{ value | int }}"
</pre>
* Restart Home assistant docker
<pre>
sudo docker restart $(sudo docker ps -qa)
</pre>
===Create a python script on Raspberry Pi ===
* filename: send_data_to_mqtt.py， please install paho library first.
<pre>
sudo apt -y install python3-paho-mqtt
</pre>
and then create a python script file and name it 'send_data_to_mqtt.py' with following:
<pre>
from smbus2 import SMBus
import time
import paho.mqtt.client as mqtt

# MQTT server configure
MQTT_BROKER = "192.168.3.218" # Replace this IP address to your Raspberry Pi's IP address
MQTT_PORT = 1883
MQTT_USERNAME = "jacky" # Replace it to your MQTT user's name
MQTT_PASSWORD = "mypassword" # Replace it to your MQTT user's password
MQTT_TOPIC = "ups_status" # define a MQTT topic

# Device address
DEVICE_ADDRESS = 0x17

# init SMBus
bus = SMBus(1) # 1 means I2C no.1 bus

# init mqtt client
mqtt_client = mqtt.Client()
mqtt_client.username_pw_set(MQTT_USERNAME, password=MQTT_PASSWORD)

# connect to mqtt server
def connect_mqtt():
try:
mqtt_client.connect(MQTT_BROKER, MQTT_PORT, 60)
print(f"{GREEN}Connected to MQTT Broker at {MQTT_BROKER}:{MQTT_PORT}{END_COLOR}")
except Exception as e:
print(f"{RED}Failed to connect to MQTT Broker: {e}{END_COLOR}")
exit(1)

# Define registers address
# WHO_AM_I_REG = 0x00 // will always be 0xA6
VERSION_REG = 0x01
UID0_REG = 0x02
UID1_REG = 0x06
UID2_REG = 0x0A
OUTPUT_VOLTAGE_REG = 0x0E
INPUT_VOLTAGE_REG = 0x10
BATTERY_VOLTAGE_REG = 0x12
MCU_VOLTAGE_REG = 0x14
OUTPUT_CURRENT_REG = 0x16
INPUT_CURRENT_REG = 0x18
BATTERY_CURRENT_REG = 0x1A
TEMPERATURE_REG = 0x1C

# Define ANSI color
RED = '\033[95m'
GREEN = '\033[92m'
END_COLOR = '\033[0m'

# read 8bit register
def read_byte_register(register_address):
value = bus.read_byte_data(DEVICE_ADDRESS, register_address)
if value > 127:
value -= 256
return value

# read 16bit register
def read_word_register(register_address):
value = bus.read_word_data(DEVICE_ADDRESS, register_address)
if value > 32767:
value -= 65536
return value

# read 32bit register
def read_dword_register(register_address):
low = bus.read_word_data(DEVICE_ADDRESS, register_address)
high = bus.read_word_data(DEVICE_ADDRESS, register_address + 2)
return (high << 16) | low

# read all registers data
def read_all_registers():
registers = {
"WHO_AM_I": "0xA6",
"VERSION": read_byte_register(VERSION_REG),
"UID0": read_dword_register(UID0_REG),
"UID1": read_dword_register(UID1_REG),
"UID2": read_dword_register(UID2_REG),
"OUTPUT_VOLTAGE": read_word_register(OUTPUT_VOLTAGE_REG),
"INPUT_VOLTAGE": read_word_register(INPUT_VOLTAGE_REG),
"BATTERY_VOLTAGE": read_word_register(BATTERY_VOLTAGE_REG),
"MCU_VOLTAGE": read_word_register(MCU_VOLTAGE_REG),
"OUTPUT_CURRENT": read_word_register(OUTPUT_CURRENT_REG),
"INPUT_CURRENT": read_word_register(INPUT_CURRENT_REG),
"BATTERY_CURRENT": read_word_register(BATTERY_CURRENT_REG),
"TEMPERATURE": read_byte_register(TEMPERATURE_REG)
}
return registers

# send data to MQTT server
def send_data_to_mqtt(data):
try:
for key, value in data.items():
if key in ["OUTPUT_VOLTAGE", "INPUT_VOLTAGE", "BATTERY_VOLTAGE", "MCU_VOLTAGE"]:
mqtt_client.publish(f"{MQTT_TOPIC}/{key}", value)
elif key in ["OUTPUT_CURRENT", "INPUT_CURRENT", "BATTERY_CURRENT"]:
mqtt_client.publish(f"{MQTT_TOPIC}/{key}", value)
elif key == "TEMPERATURE":
mqtt_client.publish(f"{MQTT_TOPIC}/{key}", value)
print(f"{GREEN}Data sent to MQTT topic {MQTT_TOPIC}:{data}{END_COLOR}")
except Exception as e:
print(f"{RED}Failed to send data to MQTT broker:{e}{END_COLOR}")

# main loop
def main():
connect_mqtt()
mqtt_client.loop_start() # start mqtt loop
try:
while True:
print(f"{RED}===52Pi UPS v6 Raw data output ==={END_COLOR}")
registers = read_all_registers()
send_data_to_mqtt(registers)
time.sleep(2)
except KeyboardInterrupt:
bus.close()
mqtt_client.loop_stop()
mqtt_client.disconnect()
print("Quit Demo")

if __name__ == "__main__":
main()
</pre>
and then execute the python script:
<pre>
python send_data_to_mqtt.py
</pre>
[[File:Send data to mqtt.jpg|left|800px]]
<br style="clear:both;">

* Adding Card in Home assistant
[[File:Adding card to HA.jpg|left|800px]]
<br style="clear:both;">

* Finally result
[[File:Result of ha.jpg|left|800px]]
<br style="clear:both;">

==How to monitor battery and safe shutdown ==
Here is the modified code, rewritten as a systemd service to monitor only the battery voltage and current.
When the battery voltage drops below 7400mV, it triggers a shutdown operation.
The monitoring interval is set to check every 2 minutes.
* Python Code (demo)
<pre>
#!/usr/bin/env python3
"""
This script monitors the battery voltage and current of a 52Pi UPS V6 device.
If the battery voltage drops below 7400mV, it triggers a shutdown process.
"""

from smbus2 import SMBus
import time
import subprocess
import logging

#define log file path
LOG_FILE = "/var/log/battery_monitor.log"

# configure logging settings
logging.basicConfig(filename=LOG_FILE, level=logging.INFO, format='%(asctime)s - %(message)s')

# Device address
DEVICE_ADDRESS = 0x17

# Define registers address
BATTERY_VOLTAGE_REG = 0x12
BATTERY_CURRENT_REG = 0x1A

# Threshold for battery voltage
BATTERY_VOLTAGE_THRESHOLD = 7400 # in mV

# Shutdown command
SHUTDOWN_COMMAND = "sudo sync ; sudo init 0"

# Initialize SMBus
bus = SMBus(1) # 1 means I2C no.1 bus

# Read 16-bit register
def read_word_register(register_address):
"""
Read a 16-bit register from the device.
"""
value = bus.read_word_data(DEVICE_ADDRESS, register_address)
if value > 32767:
value -= 65536
return value

# Read battery voltage and current
def read_battery_status():
"""
Read the battery voltage and current from the device.
"""
battery_voltage = read_word_register(BATTERY_VOLTAGE_REG)
battery_current = read_word_register(BATTERY_CURRENT_REG)
return battery_voltage, battery_current

# Check battery status and trigger shutdown if necessary
def check_battery_status():
"""
Check the battery status and trigger shutdown if the voltage is below the threshold.
"""
battery_voltage, battery_current = read_battery_status()
logging.info(f"Battery Voltage: {battery_voltage}mV, Current: {battery_current}mA.")

if battery_voltage < BATTERY_VOLTAGE_THRESHOLD:
logging.info(f"Battery voltage is below {BATTERY_VOLTAGE_THRESHOLD}mV. Initiating shutdown.")
logging.info(f"Battery voltage is below {BATTERY_VOLTAGE_THRESHOLD}mV. Initiating shutdown.")
subprocess.run(SHUTDOWN_COMMAND, shell=True)

# Main loop
def main():
"""
Main loop to periodically check the battery status.
"""
try:
while True:
check_battery_status()
time.sleep(120) # Check every 2 minutes
except KeyboardInterrupt:
print("Exiting battery monitor script.")
finally:
bus.close()

if __name__ == "__main__":
main()
</pre>
Please save it and name it as 'battery_monitory.py' and put it to your own location. in this case, the file location is `/home/pi/upsv6_pub/script/tools/python_demo/battery_monitor.py`.
===Code Explanation===
* Optimization:
- Removed unnecessary `read_byte_register` and `read_dword_register` functions, as only the battery voltage and current are monitored, both of which are 16-bit registers.
- Removed the redundant `read_all_registers` function and directly read the battery voltage and current in `check_battery_status`.
- Removed excess print statements, retaining only those for battery voltage and current.

* Monitoring Logic:
- Checks the battery voltage and current every 2 minutes.
- If the battery voltage falls below 7400mV, it calls `subprocess.run` to execute the shutdown command.

* Comments:
- Added detailed English comments to explain the purpose of each function and the main logic.

===Creating a systemd Service===
To run this script as a systemd service, you need to create a systemd service file.

* Create the Service File:
Create a service file in the `/etc/systemd/system/` directory, for example, `battery_monitor.service`.
<pre>
sudo nano /etc/systemd/system/battery_monitor.service
</pre>

* Edit the Service File:
Add the following content to the file:
<pre>
[Unit]
Description=Battery Monitor Service
After=network.target

[Service]
ExecStart=/usr/bin/python3 /path/to/your/script/battery_monitor.py # Do remember replace this path to your own battery_monitor.py file's location.
Restart=always
User=pi

[Install]
WantedBy=multi-user.target
</pre>

- `ExecStart` specifies the path to the script.
- `Restart=always` ensures the service restarts automatically if it fails.
- `User=pi` specifies that the script runs as the `pi` user.
===Create log file and grant permissions===
<pre>
sudo touch /var/log/battery_monitor.log
sudo chown pi:pi /var/log/battery_monitor.log
sudo chmod 664 /var/log/battery_monitor.log
</pre>

===Start the Service===
After saving the file, run the following commands to start the service and enable it to start on boot:
<pre>
sudo systemctl daemon-reload
sudo systemctl enable battery_monitor.service
sudo systemctl start battery_monitor.service
</pre>

===Check Service Status===
Use the following command to check the service status:
<pre>
sudo systemctl status battery_monitor.service
</pre>

With this setup, the script will run as a systemd service, checking the battery voltage and current every 2 minutes and triggering a shutdown operation when the voltage falls below 7400mV.

===How to plot the power status by using matplotlib===
Here is the detailed step-by-step guide and code example in English to create a real-time dynamic plot using matplotlib to display input and output power.
* Step 1: Install Necessary Libraries
Ensure you have the smbus2 and matplotlib libraries installed. If not, you can install them using the following command:
<pre>
sudo apt update
sudo apt -y install python3-smbus2 python3-matplotlib python3-numpy
</pre>

* Step 2: Write the Code
Here is the complete code example that reads input and output power in real-time and uses matplotlib to dynamically display these values.
<pre>
from smbus2 import SMBus
import time
import matplotlib.pyplot as plt
import matplotlib.animation as animation
import numpy as np

# Device address
DEVICE_ADDRESS = 0x17

# Define registers address
VERSION_REG = 0x01
OUTPUT_VOLTAGE_REG = 0x0E
INPUT_VOLTAGE_REG = 0x10
OUTPUT_CURRENT_REG = 0x16
INPUT_CURRENT_REG = 0x18

# Initialize SMBus
bus = SMBus(1) # 1 means I2C no.1 bus

# Read 16-bit register
def read_word_register(register_address):
value = bus.read_word_data(DEVICE_ADDRESS, register_address)
if value > 32767:
value -= 65536
return value

# Calculate power
def calculate_power(voltage_mv, current_ma):
voltage_v = voltage_mv / 1000.0
current_a = current_ma / 1000.0
return voltage_v * current_a # Result in watts

# Initialize lists to store data
input_power_data = []
output_power_data = []
time_data = []

# Initialize time
start_time = time.time()

# Function to update the plot
def update(frame):
global start_time

# Read voltage and current values
input_voltage_mv = read_word_register(INPUT_VOLTAGE_REG)
input_current_ma = read_word_register(INPUT_CURRENT_REG)
output_voltage_mv = read_word_register(OUTPUT_VOLTAGE_REG)
output_current_ma = read_word_register(OUTPUT_CURRENT_REG)

# Calculate input and output power
input_power_w = calculate_power(input_voltage_mv, input_current_ma)
output_power_w = calculate_power(output_voltage_mv, output_current_ma)

# Append data
current_time = time.time() - start_time
time_data.append(current_time)
input_power_data.append(input_power_w)
output_power_data.append(output_power_w)

# Limit the data to the last 100 points
if len(time_data) > 100:
time_data.pop(0)
input_power_data.pop(0)
output_power_data.pop(0)

# Clear the previous plot
ax.clear()

# Plot input power
ax.plot(time_data, input_power_data, label='Input Power (W)', color='blue')
ax.set_ylabel('Power (W)')
ax.set_xlabel('Time (s)')
ax.legend(loc='upper left')

# Plot output power
ax.plot(time_data, output_power_data, label='Output Power (W)', color='red')
ax.legend(loc='upper left')

# Set title
ax.set_title('Real-time Input and Output Power')

# Create a figure and axis
fig, ax = plt.subplots()

# Create the animation
ani = animation.FuncAnimation(fig, update, interval=2000) # Update every 2 seconds

# Show the plot
plt.show()
</pre>
Save it as `plot_power.py`, or just find it in the repository of `upsv6_pub` on GitHub.
* Execute it:
<pre>
python plot_power.py
</pre>
It will plot the input and output power status in animation.
[[File:Plot power.jpg|left|800px]]
<br style="clear:both;">

===Explanation of the Code===
* Initialize SMBus and Register Addresses:
The smbus2 library is used to initialize the I2C bus, and the register addresses for reading voltage and current values are defined.
* Read Register Values:
The read_word_register function reads 16-bit values from the specified registers.
* Calculate Power:
The calculate_power function converts millivolts (mV) to volts (V) and milliamperes (mA) to amperes (A), then calculates the power in watts.
* Store Data:
Lists input_power_data, output_power_data, and time_data are used to store the power values and corresponding time stamps.
* Dynamic Plot Update:
The matplotlib.animation.FuncAnimation function is used to create a dynamic plot that updates every 2 seconds.
The update function reads the latest power values, appends them to the data lists, and updates the plot.
* Limit Data Points:
To prevent performance issues with too much data, the lists are limited to the last 100 data points.
* Display the Plot:
The plot is displayed using plt.show(), showing real-time updates of input and output power.
* Running the Code
When you run the code, you will see a dynamic plot that updates every 2 seconds, showing the real-time changes in input and output power. The plot will display the last 100 data points for both input and output power.
* If external power is failed, you will see some picture like this:
[[File:Plot power01.jpg|left|800px]]
<br style="clear:both;">

===How to plot input and output power by using pygame===
* Create a python file named: `plot_power_pygame.py`
<pre> vim plot_power_pygame.py </pre>

* Copy and paste following demo code:
<pre>
import pygame
import sys
from smbus2 import SMBus
import math
import time

# Device address
DEVICE_ADDRESS = 0x17

# Define registers address
VERSION_REG = 0x01
OUTPUT_VOLTAGE_REG = 0x0E
INPUT_VOLTAGE_REG = 0x10
OUTPUT_CURRENT_REG = 0x16
INPUT_CURRENT_REG = 0x18

# Initialize SMBus
bus = SMBus(1) # 1 means I2C no.1 bus

# Read 16-bit register
def read_word_register(register_address):
value = bus.read_word_data(DEVICE_ADDRESS, register_address)
if value > 32767:
value -= 65536
return value

# Calculate power
def calculate_power(voltage_mv, current_ma):
voltage_v = voltage_mv / 1000.0
current_a = current_ma / 1000.0
return voltage_v * current_a # Result in watts

# Initialize Pygame
pygame.init()

# Set up the display
screen = pygame.display.set_mode((800, 400))
pygame.display.set_caption("Power Gauges")

# Define colors
BLACK = (0, 0, 0)
CYAN = (0, 255, 255)
RED = (255, 0, 0)

# Draw the gauge background
def draw_gauge_background(x_offset, title):
pygame.draw.circle(screen, CYAN, (200 + x_offset, 200), 130, 2)
max_power = 30 # Maximum power is 30W for the gauge
num_ticks = int(max_power / 0.5) # Number of ticks
for i in range(num_ticks + 1):
angle = math.radians(270 - (i / num_ticks * 180)) # 0 point at the bottom
x1 = 200 + 120 * math.cos(angle) + x_offset
y1 = 200 + 120 * math.sin(angle)
x2 = 200 + 124 * math.cos(angle) + x_offset
y2 = 200 + 124 * math.sin(angle)
pygame.draw.line(screen, CYAN, (x1, y1), (x2, y2), 1)
if i % 5 == 0: # Only display every 5th tick
font = pygame.font.SysFont(None, 16)
img = font.render(f"{i * 0.5:.1f}", True, CYAN)
text_width, text_height = font.size(f"{i * 0.5:.1f}")
text_x = 200 + (135 + 3) * math.cos(angle) + x_offset - text_width / 2
text_y = 200 + (135 + 3) * math.sin(angle) - text_height / 2
screen.blit(img, (text_x, text_y))

# Draw title
font = pygame.font.SysFont(None, 24)
img = font.render(title, True, CYAN)
screen.blit(img, (200 + x_offset - img.get_width() / 2, 10))

# Draw the needle
def draw_needle(x_offset, power):
max_power = 30 # Maximum power is 100W for the gauge
angle = 270 - (power / max_power * 180) # 0 point at the bottom
angle_rad = math.radians(angle)
x = 200 + 120 * math.cos(angle_rad) + x_offset
y = 200 + 120 * math.sin(angle_rad)
pygame.draw.line(screen, RED, (200 + x_offset, 200), (x, y), 2)

# Main loop
def main():
clock = pygame.time.Clock()
while True:
for event in pygame.event.get():
if event.type == pygame.QUIT:
pygame.quit()
sys.exit()

# Read power values
input_voltage_mv = read_word_register(INPUT_VOLTAGE_REG)
input_current_ma = read_word_register(INPUT_CURRENT_REG)
input_power_w = calculate_power(input_voltage_mv, input_current_ma)

output_voltage_mv = read_word_register(OUTPUT_VOLTAGE_REG)
output_current_ma = read_word_register(OUTPUT_CURRENT_REG)
output_power_w = calculate_power(output_voltage_mv, output_current_ma)

# Update the gauges
screen.fill(BLACK)
draw_gauge_background(0, "INPUT")
draw_gauge_background(400, "OUTPUT")
draw_needle(0, input_power_w)
draw_needle(400, output_power_w)
pygame.display.flip()
clock.tick(0.5) # Update every 2 seconds

if __name__ == "__main__":
main()

</pre>
* Save it and execute it.
<pre>
python plot_power_pygame.py
</pre>
===Demostration===
* Gaugue Figure
[[File:Plot power pygame.jpg|left|800px]]
<br style="clear:both;">
===Explaination of demo code===
* Implementation Explanation
This code is designed to create a graphical user interface (GUI) using Pygame to display power gauges for input and output power readings from a device connected via I2C.
The gauges are represented as circular meters with needles that move based on the power values read from the device.
The code also includes titles for each gauge ("INPUT" and "OUTPUT") and evenly spaced tick marks with numerical labels.
====Key Components and Logic====
* I2C Communication: The code uses the smbus2 library to communicate with an I2C device at address 0x17. Functions like read_word_register are used to read 16-bit values from specific registers on the device, which correspond to input and output voltage and current readings.
* Power Calculation: The calculate_power function converts the raw voltage and current readings from millivolts and milliamps to volts and amps, respectively, and then calculates the power in watts.
* Pygame Initialization: Pygame is initialized to create a window with a size of 800x400 pixels. Colors for the background, tick marks, and needle are defined.
* Gauge Background Drawing:
The draw_gauge_background function draws the circular gauge, including:
<pre>
1. A circle representing the gauge outline.
2. Tick marks spaced evenly around the gauge. The tick marks are spaced based on a maximum power value of 30W, with each tick representing 0.5W.
3. Numerical labels for every 5th tick mark, positioned slightly outside the gauge to avoid overlap.
4. A title ("INPUT" or "OUTPUT") displayed above each gauge.
</pre>
* Needle Drawing: The draw_needle function calculates the angle of the needle based on the power value and draws it on the gauge. The angle is adjusted so that 0W corresponds to the bottom of the gauge.
* Main Loop: The main function contains the main loop of the program:
<pre>
1. It reads the power values from the I2C device.
2. It updates the gauges by clearing the screen, redrawing the gauge backgrounds, and drawing the needles based on the current power values.
3. It updates the display and limits the refresh rate to once every 2 seconds.
</pre>

===Features and Enhancements===
* Tick Marks and Labels: The tick marks are evenly spaced around the gauge, and labels are added to indicate power values in watts. The labels are positioned slightly outside the gauge to ensure they are readable.
* Titles: Each gauge has a title ("INPUT" and "OUTPUT") to distinguish between the two power readings.
* Needle Positioning: The needle's position is calculated based on the power value, with 0W starting at the bottom of the gauge and increasing clockwise.
* This implementation provides a clear and visually intuitive way to monitor input and output power readings from an I2C device in real-time.
==Model and Structure file download==
* STEP File: [[ File:UPS Gen6 STEP file.zip ]]
* STP structure File: [[ File:UPS Gen6 STP StructureFile.zip ]]
===More information===
* Please visit: [ https://github.com/geeekpi/upsv6_pub/ ]