https://wiki.52pi.com/api.php?action=feedcontributions&feedformat=atom&user=TaterLi52Pi Wiki - User contributions [en]2026-11-04T21:56:45ZUser contributionsMediaWiki 1.39.2https://wiki.52pi.com/index.php?title=Main_Page&diff=16277Main Page2026-03-30T07:31:37Z<p>TaterLi: </p>
<hr />
<div><div style="border:1px solid #a2a9b1; background:#f8f9fa; padding:12px; margin:0 0 16px 0;"><br />
'''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/]<br />
</div><br />
<br />
='''RaspberryPi Modules'''=<br />
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. <br />
you can select one of them and click the links to get more information about it.<br />
==HCL==<br />
This is Hardware Compatible List. <font color=red>Depracated</font></br> <br />
[[Hardware Compatible List]]<br />
<br />
==UPS series==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* UPS Gen 6 power module compatible with Raspberry Pi 5/4B: [[ EP-0245 ]] <font color=red>NEW!!</font><br> <br />
* SBS module for UPS Gen 6 [[ EP-0256 ]] <font color=red>NEW!!</font><br> <br />
* SATA Drive Power Board for UPS Gen 6: [[ EP-0252 ]] <font color=red>NEW!!</font><br> <br />
* 1.3" LCD TFT Display Module for UPS Gen 6: [[ EP-0251 ]] <font color=red>NEW!!</font><br> <br />
</td><br />
</tr><br />
</table><br />
<br />
==Rackmount Series==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* 1U 19-inch Removable Rack mount For RPi5/4B/3B+ [[ DR-0003 ]] <font color=red>NEW</font><br> <br />
* 2U RackMount For RPi 5: [[ DR-0002]] <font color=red>NEW</font><br> <br />
* 2U RackMount For RPi 5: [[ DP-0046]] <font color=red>NEW</font><br><br />
* 1U RackMount For RPi 5: [[ DR-0001 ]] <font color=red>NEW</font><br><br />
* 1U RackMount For RPi 4B: [[ EP-0143 ]]<br />
<br />
</td><br />
</tr><br />
</table><br />
<br />
==Arduino Series==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
===Arduino UNO R4 Wi-Fi Series===<br />
* [[ KZ-0054 ]]<br />
* [[ KZ-0077 ]]<br />
* [[ KZ-0086 ]]<br />
</td><br />
</tr><br />
</table><br />
<br />
==52Pi N Series==<br />
===Description===<br />
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.<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
<br />
==Product SKU==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* W03-New - [[ EP-0216-NEW ]] <font color=red>NEW</font><br><br />
* RS-P13 - [[ EP-0249 ]] <font color=red>NEW</font><br><br />
* S021 - [[ EP-0242 ]] <font color=red>NEW</font><br><br />
* N16 - [[ EP-0180 ]] <font color=red>NEW</font><br><br />
* P33 - [[ EP-0241 ]] <font color=red>NEW</font><br><br />
* P31 - [[ EP-0240 ]] <font color=red>NEW</font><br><br />
* P30 - [[ EP-0238 ]] <font color=red>NEW</font><br><br />
* CN01 - [[ EP-0236 ]] <font color=red>NEW</font><br><br />
* N06 - [[ EP-0239 ]] <font color=red>NEW</font><br><br />
* RS-P11 - [[ EP-0234 ]] <font color=red>NEW</font><br><br />
* B14 - [[ EP-0233 ]] <font color=red>NEW</font><br><br />
* N12 - [[ EP-0213 ]] <font color=red>NEW</font><br><br />
* U2500 - [[ EP-0235 ]] <font color=red>NEW</font><br><br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* N21 - [[ EP-0231 ]] <font color=red>NEW</font><br><br />
* N20 - [[ EP-0227 ]] <font color=red>NEW</font><br><br />
* W01 - [[ EP-0228 ]] <font color=red>NEW</font><br><br />
* N10 - [[ EP-0229 ]] <font color=red>NEW</font><br><br />
* B12 - [[ EP-0230 ]] <font color=red>NEW</font><br><br />
* M01 - [[ EP-0223 ]] <font color=red>NEW</font><br><br />
* M02 - [[ EP-0217 ]] <font color=red>NEW</font><br><br />
* N05 - [[ EP-0209 ]] <font color=red>NEW</font><br><br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* N04 - [[ EP-0210 ]] <font color=red>NEW</font><br><br />
* N07 - [[ EP-0211 ]] <font color=red>NEW</font><br><br />
* P02 - [[ EP-0219 ]] <font color=red>NEW</font><br><br />
* 52Pi NVDAC - [[ EP-0218 ]]<br />
* 52Pi NVdigi - [[ EP-0220 ]]<br />
* M.2 2242 NVME SSD for RPi 5 NES-CASE - [[ EP-0212 ]] <br />
* W03 - [[ EP-0216 ]] <br />
* Ice tower plus for RPi 5 - [[ EP-0224 ]] <br />
</td></tr></table><br />
<br><br />
<br />
==Mini Tower Kit Series==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0187 ]] <font color=red>NEW</font><br />
* [[ ZP-0172 ]]<br />
* [[ ZP-0128 ]]<br />
* [[ ZP-0128-3B ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0128-4wire ]]<br />
* [[ ZP-0129-4wire ]]<br />
* [[ ZP-0130-4wire ]]<br />
</td><br />
<br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0129 ]]<br />
* [[ ZP-0130 ]]<br />
* [[ ZP-0132 ]]<br />
</td><br />
</tr><br />
</table><br />
<br />
==Hat Stack==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0167 ]]<br />
* [[ EP-0168 ]]<br />
* [[ EP-0166 ]]<br />
* [[ EP-0152 ]]<br />
* [[ EP-0117 ]]<br />
* [[ EP-0116 ]]<br />
* [[ EP-0098 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0099 ]]<br />
* [[ EP-0104 ]]<br />
* [[ EP-0106 ]]<br />
* [[ EP-0107 ]]<br />
* [[ EP-0108 ]]<br />
* [[ EP-0109 ]]<br />
* [[ EP-0105 ]]<br />
</td></tr></table><br />
<br />
==Starter Kit==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ KZ-0067 ]] <br />
* [[ KZ-0061 ]]<br />
* [[ KZ-0016 ]]<br />
* [[ KZ-0020 ]]<br />
* [[ KZ-0009 ]]<br />
</td></tr></table><br />
<br />
==Development Boards==<br />
===RP2040 Series===<br />
* [[ EP-0174 ]] <br />
===StarFive2===<br />
* [[ ER-0043 ]] <br />
* [[ ER-0044 ]]<br />
<br />
===Micro:Bit===<br />
* [[ KR-0004 ]]<br />
* [[ KR-0027 ]]<br />
<br />
===ROCK Pi Series===<br />
* [[ KR-0001 ]]<br />
* [[ KR-0012 ]]<br />
* [[ ZP-0148 ]]<br />
<br />
===Orange Pi Series===<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0156 ]]<br />
* [[ ZP-0150 ]]<br />
* [[ ZP-0149 ]]<br />
* [[ F-0020 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ F-0021 ]]<br />
* [[ F-0022 ]]<br />
* [[ KZ-0003 ]]<br />
* [[ ER-0045 ]]<br />
</td><br />
</tr><br />
</table><br />
<br />
===Raspberry Pi Pico Series===<br />
* [[ KR-0006 ]]<br />
* [[ EP-0175 ]]<br />
<br />
==AI Learning==<br />
* [[ EZ-0075 ]]<br />
* [[ L-0031 ]]<br />
<br />
==IoT Modules==<br />
* [[ EP-0090 ]]<br />
* [[ EZ-0061 ]]<br />
* [[ EZ-0062 ]]<br />
* [[ EZ-0063 ]]<br />
----<br />
<br />
==Tinker Board==<br />
* [[ EZ-0066 ]]<br />
* [[ EZ-0065 ]]<br />
<br />
----<br />
===DeskPi Series===<br />
* [[ DP-0002 ]]<br />
* [[ DP-0018 ]]<br />
<br />
==KZ series==<br />
* [[ KZ-0022 ]]<br />
* [[ KZ-0056 ]]<br />
* [[ KZ-0058 ]]<br />
* [[ KZ-0060 ]]<br />
<br />
==Raspberry Pi==<br />
<table><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ER-0056 ]]<br />
* [[ KR-0024 ]]<br />
* [[ ER-0046 ]]<br />
* [[ ER-0035 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ER-0031 ]]<br />
* [[ ER-0030 ]]<br />
* [[ ER-0027 ]]<br />
* [[ ER-0028 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ER-0018 ]]<br />
* [[ ER-0007 ]]<br />
* [[ K-0231 ]]<br />
* [[ K-0230 ]]<br />
</td></tr></table> <br />
<br />
----<br />
<br />
===Raspberry Pi Pico & Pico W Breakout Board===<br />
<table><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0172 ]]<br />
* [[ EP-0164 ]]<br />
* [[ EP-0159 ]]<br />
* [[ EP-0145 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0138 ]]<br />
* [[ EP-0139 ]]<br />
* [[ EP-0140 ]]<br />
* [[ K-0582 ]]<br />
* [[ K-0586 ]]<br />
</tr></td></table><br />
<br />
==Banana Pi==<br />
* [[ EB-0028 ]]<br />
* [[ EB-0023 ]]<br />
* [[ EB-0020 ]]<br />
* [[ EP-0019 ]]<br />
* [[ EB-0012 ]]<br />
* [[ EB-0013 ]]<br />
<br />
==Gaming Assesories==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ D-0023 ]]<br />
* [[ Z-0261 ]]<br />
* [[ Z-0179 ]]<br />
* [[ Z-0279 ]]<br />
* [[ Z-0252 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ Z-0253 ]]<br />
* [[ Z-0254 ]]<br />
* [[ Z-0255 ]]<br />
* [[ Z-0257 ]]<br />
* [[ Z-0260 ]]<br />
</td><br />
</tr></table><br />
<br />
==Electronic Accessories==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ T-0020 ]]<br />
* [[ K-0580 ]]<br />
* [[ ZP-0157 ]]<br />
* [[ ZP-0158 ]]<br />
</td><br />
</tr></table><br />
<br />
==Extension Modules==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0243 ]] <br />
* [[ EP-0246 ]]<br />
* [[ EP-0247 ]]<br />
* [[ EP-0225 ]]<br />
* [[ EP-0215 ]]<br />
* [[ EP-0214 ]]<br />
* [[ EP-0171 ]]<br />
* [[ D-0001 ]]<br />
* [[ EZ-0106 ]]<br />
* [[ EP-0153 ]]<br />
* [[ EP-0150 ]]<br />
* [[ EP-0146 ]]<br />
* [[ EP-0149 ]]<br />
* [[ P-0021 ]]<br />
* [[ P-0024 ]]<br />
* [[ EP-0142 ]] <br />
* [[ EP-0141 ]]<br />
<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0136 ]]<br />
* [[ EP-0131 ]]<br />
* [[ EP-0130 ]]<br />
* [[ D-0020 ]]<br />
* [[ ER-0014 ]]<br />
* [[ EP-0129 ]]<br />
* [[ EP-0128 ]]<br />
* [[ EP-0127 ]]<br />
* [[ EP-0123 ]]<br />
* [[ EP-0124 ]]<br />
* [[ EP-0125 ]]<br />
* [[ EP-0126 ]]<br />
* [[ K-0335 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ER-0022 ]]<br />
* [[ D-0018 ]]<br />
* [[ G-0002 ]]<br />
* [[ D-0010 ]]<br />
* [[ D-0012 ]]<br />
* [[ D-0013 ]]<br />
* [[ D-0015 ]]<br />
* [[ D-0016 ]]<br />
* [[ D-0017 ]]<br />
* [[ EP-0120 ]]<br />
* [[ EP-0121 ]]<br />
* [[ EP-0118 ]]<br />
* [[ D-0008 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ D-0009 ]]<br />
* [[ D-0011 ]]<br />
* [[ D-0005 ]]<br />
* [[ D-0006 ]]<br />
* [[ D-0007 ]]<br />
* [[ P-0010 ]]<br />
* [[ P-0011 ]]<br />
* [[ D-0003 ]]<br />
* [[ EZ-0089 ]]<br />
* [[ EP-0115 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ER-0021 ]]<br />
* [[ P-0005 ]]<br />
* [[ P-0006 ]]<br />
* [[ Z-0269 ]]<br />
* [[ Z-0231 ]]<br />
* [[ Z-0209 ]]<br />
* [[ ER-0016 ]]<br />
* [[ Z-0234 ]]<br />
* [[ Z-0235 ]]<br />
* [[ EP-0101 ]]<br />
</td><br />
</tr><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0097 ]] <br />
* [[ EP-0095 ]]<br />
* [[ EP-0096 ]]<br />
* [[ EZ-0068 ]]<br />
* [[ EP-0094 ]]<br />
* [[ K-0291 ]]<br />
* [[ EP-0091 ]]<br />
* [[ EP-0092 ]]<br />
* [[ EP-0093 ]]<br />
* [[ EP-0088 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0114 ]]<br />
* [[ EP-0100 ]]<br />
* [[ EP-0080 ]]<br />
* [[ EP-0031 ]]<br />
* [[ EP-0059 ]]<br />
* [[ Z-0177 ]]<br />
* [[ EP-0021 ]]<br />
* [[ EP-0020 ]]<br />
* [[ EZ-0024 ]]<br />
* [[ EZ-0048 ]]<br />
</td><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0073 ]]<br />
</td></tr></table><br />
<br />
==Case & Enclosure & Heat sink==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ C-0063 ]]<br />
* [[ ZP-0215 ]]<br />
* [[ ZP-0213 ]]<br />
* [[ ZP-0188 ]]<br />
* [[ EP-0226 ]]<br />
* [[ EP-0222 ]]<br />
* [[ C-0052 ]]<br />
* [[ ZP-0186 ]]<br />
* [[ ZP-0175 ]]<br />
* [[ C-0054 ]]<br />
* [[ ZP-0181 ]]<br />
* [[ ZP-0173 ]]<br />
* [[ ZP-0170 ]]<br />
* [[ C-0050 ]]<br />
* [[ ZP-0167 ]]<br />
* [[ C-0047 ]]<br />
* [[ C-0048 ]]<br />
* [[ C-0049 ]]<br />
* [[ ZP-0163 ]]<br />
* [[ ZP-0166 ]]<br />
* [[ ZP-0162 ]]<br />
* [[ ZP-0180 ]]<br />
* [[ ZP-0164 ]]<br />
* [[ ZP-0153 ]]<br />
* [[ ZP-0147 ]]<br />
* [[ K-0638 ]]<br />
* [[ KZ-0001 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ KZ-0002 ]]<br />
* [[ ZP-0138 ]]<br />
* [[ ZP-0139 ]]<br />
* [[ ZP-0140 ]]<br />
* [[ ZP-0141 ]]<br />
* [[ EP-0163 ]]<br />
* [[ ZP-0120 ]]<br />
* [[ K-0612 ]]<br />
* [[ C-0031 ]]<br />
* [[ K-0595 ]]<br />
* [[ ZP-0165 ]]<br />
* [[ ZP-0168 ]]<br />
* [[ K-0583 ]]<br />
* [[ K-0585 ]]<br />
* [[ ZP-0115 ]]<br />
* [[ ZP-0113 ]]<br />
* [[ ZP-0111 ]]<br />
* [[ ZP-0112 ]]<br />
* [[ C-0027 ]]<br />
* [[ ZP-0110 ]]<br />
* [[ C-0023 ]]<br />
* [[ C-0025 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0132 ]]<br />
* [[ K-0567 ]]<br />
* [[ C-0022 ]]<br />
* [[ C-0020]]<br />
* [[ ZP-0105 ]]<br />
* [[ ZP-0133 ]]<br />
* [[ C-0032 ]]<br />
* [[ C-0033 ]]<br />
* [[ C-0034 ]]<br />
* [[ ZP-0103 ]]<br />
* [[ C-0015 ]]<br />
* [[ ZP-0108 ]]<br />
* [[ ZP-0089 ]]<br />
* [[ F-0003 ]]<br />
* [[ ZP-0102 ]]<br />
* [[ ZP-0101 ]]<br />
* [[ ZP-0040 ]]<br />
* [[ ZP-0039 ]]<br />
* [[ EP-0122 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0100 ]]<br />
* [[ ZP-0099 ]]<br />
* [[ EP-0077 ]]<br />
* [[ EP-0078 ]]<br />
* [[ EP-0079 ]]<br />
* [[ ER-0011 ]]<br />
* [[ EZ-0059 ]]<br />
* [[ Z-0153 ]]<br />
* [[ EP-0076 ]]<br />
* [[ ZP-0098 ]]<br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0092 ]]<br />
* [[ ZP-0093 ]]<br />
* [[ C-0008 ]]<br />
* [[ C-0006 ]]<br />
* [[ C-0003 ]]<br />
* [[ ZP-0090 ]]<br />
* [[ ZP-0091 ]]<br />
* [[ C-0005 ]]<br />
* [[ C-0004 ]]<br />
* [[ ZP-0088 ]]<br />
* [[ K-0592 ]]<br />
* [[ K-0589 ]]<br />
* [[ ZP-0116 ]]<br />
* [[ C-0028 ]]<br />
</td><br />
</tr><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0087 ]] <br />
* [[ C-0002 ]]<br />
* [[ C-0001 ]]<br />
* [[ EP-0112 ]]<br />
* [[ ZP-0086 ]]<br />
* [[ ZP-0079 ]]<br />
* [[ ZP-0078 ]]<br />
* [[ ZP-0068 ]]<br />
* [[ Z-0278 ]]<br />
* [[ ZP-0085 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0113 ]]<br />
* [[ EP-0111 ]]<br />
* [[ ZP-0081 ]]<br />
* [[ ZP-0082 ]]<br />
* [[ ZP-0083 ]]<br />
* [[ Z-0272 ]]<br />
* [[ C-0007 ]]<br />
* [[ Z-0273 ]]<br />
* [[ ZP-0080 ]]<br />
* [[ ZP-0077 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0074 ]]<br />
* [[ ZP-0075 ]]<br />
* [[ ZP-0073 ]]<br />
* [[ ZP-0076 ]]<br />
* [[ ZP-0067 ]]<br />
* [[ ZP-0066 ]]<br />
* [[ ZP-0065 ]]<br />
* [[ ZP-0038 ]]<br />
* [[ ZP-0072 ]]<br />
* [[ Z-0266 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0070 ]]<br />
* [[ ZP-0071 ]]<br />
* [[ Z-0264 ]]<br />
* [[ ZP-0051 ]]<br />
* [[ Z-0237 ]]<br />
* [[ ZP-0025 ]]<br />
* [[ ZP-0069 ]]<br />
* [[ ZP-0042 ]]<br />
* [[ Z-0185 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ ZP-0037 ]]<br />
* [[ Z-0183 ]] <br />
* [[ Z-0127 ]]<br />
* [[ K-0172 ]]<br />
* [[ K-0178 ]]<br />
* [[ Z-0157 ]]<br />
* [[ ZP-0024 ]]<br />
* [[ L-0030 ]]<br />
* [[ ZP-0029 ]]<br />
* [[ ZP-0049 ]]<br />
</td><br />
</tr><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ Z-0193 ]]<br />
* [[ Z-0208 ]]<br />
* [[ Z-0190 ]]<br />
* [[ Z-0184 ]]<br />
</td><br />
</tr></table><br />
<br />
==Cooling Accessories==<br />
<pre> EOL stands for "End of Life", means this product will not produce any more</pre><br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ F-0001 ]]<br />
* [[ F-0002 ]]<br />
* [[ F-0006 ]]<br />
* [[ F-0005 ]]<br />
* [[ F-0007 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ F-0010 ]]<br />
* [[ F-0011 ]]<br />
* [[ F-0012 ]]<br />
* [[ D-0022 ]]<br />
* [[ F-0008 ]]<br />
* [[ F-0008-RGB ]]<br />
</td><br />
</tr></table><br />
<br />
==Electronic Engineer Tools==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ T-0022 ]]<br />
* [[ T-0021 ]]<br />
* [[ T-0019 ]]<br />
* [[ T-0015 ]]<br />
* [[ T-0016 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ T-0017 ]]<br />
* [[ T-0018 ]]<br />
* [[ Z-0241 ]]<br />
</td></tr></table><br />
<br />
==Displays==<br />
<pre> EOL stands for "End of Life", means this product will not produce any more</pre><br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0189 ]] <font color=red>NEW!!!</font><br><br />
* [[ EP-0187 ]] <font color=red>NEW!!!</font><br><br />
* [[ EP-0190 ]]<br />
* [[ EP-0188 ]]<br />
* [[ EP-0185 ]]<br />
* [[ EP-0186 ]]<br />
* [[ EP-0183 ]]<br />
* [[ EP-0184 ]]<br />
* [[ EP-0177 ]]<br />
* [[ EP-0170 ]]<br />
* [[ S-0018 ]] <br />
* [[ EP-0133 ]]<br />
* [[ EP-0119 ]]<br />
* [[ S-0007 ]]<br />
* [[ S-0006 ]]<br />
* [[ S-0005 ]]<br />
* [[ EP-0060 ]]<font color=red>EOL</font><br />
* [[ EP-0049 ]] <font color=red>EOL</font><br />
* [[ EP-0045 ]]<br />
* [[ EP-0058 ]]<br />
* [[ EP-0075 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0148 ]]<br />
* [[ EP-0062 ]]<br />
* [[ EP-0063 ]]<br />
* [[ EP-0066 ]]<br />
* [[ EP-0065 ]]<br />
* [[ Z-0053 ]]<br />
* [[ EP-0072 ]]<br />
* [[ EP-0081 ]]<br />
* [[ EP-0089 ]]<br />
* [[ EP-0087 ]]<br />
* [[ EP-0085 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ EP-0084 ]]<br />
* [[ EP-0082 ]]<br />
* [[ Z-0017 ]]<br />
* [[ Z-0051 ]]<br />
* [[ K-0106 ]]<br />
* [[ Z-0111 ]]<br />
* [[ Z-0112 ]]<br />
* [[ K-0101 ]]<br />
* [[ K-0102 ]]<br />
* [[ S-0003 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ S-0001 ]]<br />
* [[ Z-0113 ]]<br />
* [[ Z-0114 ]]<br />
* [[ Z-0143 ]]<br />
* [[ K-0103 ]]<br />
* [[ K-0104 ]]<br />
</td></tr></table><br />
<br />
==Power Supply==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ P-0044 ]]<br />
* [[ P-0040 ]]<br />
* [[ P-0031 ]]<br />
* [[ P-0032 ]]<br />
* [[ P-0017 ]]<br />
* [[ P-0007 ]] <br />
* [[ P-0008 ]] <br />
* [[ P-0009 ]] <br />
* [[ P-0004 ]] <font color=red>EOL</font><br />
* [[ P-0003 ]] <font color=red>EOL</font><br />
* [[ P-0002 ]] <font color=red>EOL</font><br />
* [[ P-0001 ]]<br />
* [[ Z-0132 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ Z-0147 ]]<br />
* [[ Z-0148 ]]<br />
* [[ Z-0149 ]]<br />
* [[ Z-0150 ]]<br />
* [[ Z-0154 ]]<br />
* [[ Z-0155 ]]<br />
* [[ L-0026 ]]<br />
* [[ L-0027 ]]<br />
* [[ Z-0133 ]]<br />
* [[ Z-0121 ]]<br />
* [[ Z-0097 ]]<br />
* [[ Z-0136 ]]<br />
</td></tr></table><br />
<br />
==Raspberry Pi Kits==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ K-0401 ]]<br />
* [[ K-0503 ]]<br />
* [[ K-0581 ]]<br />
* [[ K-0522 ]]<br />
* [[ T-0008 ]]<br />
* [[ K-0512 ]]<br />
* [[ K-0502 ]]<br />
* [[ K-0403 ]]<br />
* [[ K-0167 ]]<br />
* [[ K-0168 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ K-0169 ]]<br />
* [[ K-0259 ]]<br />
* [[ K-0238 ]]<br />
* [[ K-0185 ]]<br />
* [[ K-0186 ]]<br />
* [[ Z-0142 ]]<br />
* [[ K-0111 ]]<br />
* [[ Z-0144 ]]<br />
* [[ K-0171 ]]<br />
* [[ K-0174 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 10%;"><br />
* [[ K-0180 ]]<br />
</td></tr></table><br />
<br />
==Official Support Products==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ Z-0104 ]]<br />
* [[ Z-0088 ]]<br />
</td></tr></table><br />
<br />
==X-Series Expansion Board==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<b><font color=red>New Products 2022.08.23 updated</font></b><br><br />
* [[ EZ-0105 ]]<br />
* [[ EZ-0099 ]]<br />
* [[ EZ-0096 ]]<br />
* [[ EZ-0094 ]]<br />
* [[ EZ-0095 ]]<br />
* [[ EZ-0090 ]]<br />
* [[ EZ-0087 ]]<br />
* [[ EZ-0088 ]]<br />
* [[ EZ-0086 ]]<br />
* [[ EZ-0083 ]]<br />
* [[ EZ-0082 ]]<br />
* [[ EZ-0076 ]]<br />
* [[ EZ-0077 ]]<br />
* [[ EZ-0078 ]]<br />
* [[ EZ-0079 ]]<br />
* [[ EZ-0080 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<b><font color=Green>Old Products 2018.6.6 updated</font></b><br><br />
* [[ X720 SKU: EZ-0072]]<br />
* [[ X730 SKU: EZ-0073]]<br />
* [[ X830 SKU: EZ-0064]]<br />
* [[ X105 SKU: EZ-0008]]<br />
* [[ X200 SKU: EZ-0002]]<br />
* [[ X300 SKU: EZ-0003]]<br />
* [[ X205 SKU: EZ-0046]]<br />
* [[ X400 SKU: EZ-0044]]<br />
* [[ X600 SKU:EZ-0045]]<br />
* [[ X3000 SKU:EZ-0051]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ X6000P SKU:EZ-0052 ]]<br />
* [[ X5000P SKU:EZ-0053 ]]<br />
* [[ X4000P SKU:EZ-0054 ]]<br />
* [[ X4000K SKU:EZ-0055 ]]<br />
* [[ X6000K SKU:EZ-0056 ]]<br />
* [[ X5000K SKU:EZ-0057 ]]<br />
* [[ X1000K SKU:EZ-0058 ]]<br />
</td></tr></table><br />
===X series Acrylic Case===<br />
* [[ ZP-0096 ]]<br />
* [[ ZP-0097 ]]</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0172&diff=13312EP-01722023-06-16T06:04:03Z<p>TaterLi: /* Specifications */</p>
<hr />
<div>==Pico Breadboard Kit Plus version==<br />
==Description==<br />
The Pico Breadboard Kit with a 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, and two buttons is a versatile electronics kit designed for prototyping and experimentation. This compact kit combines various components to create interactive projects and offers a user-friendly interface.<br />
==Features==<br />
* <strong>3.5-inch Capacitive Touch Screen:</strong> The kit includes a high-resolution touch screen for displaying visual outputs and receiving user input.<br />
* <strong>Mini PSP Joystick:</strong> The built-in mini joystick provides precise analog control for navigating menus and controlling movement in projects.<br />
* <strong>RGB Light:</strong> The kit features an RGB light that can emit various colors, allowing for dynamic visual effects and status indicators.<br />
* <strong>Buzzer:</strong> An integrated buzzer produces audible feedback, enabling sound effects or alerts in your projects.<br />
* <strong>Two Buttons:</strong> The kit includes two buttons for user input, providing additional control options and interactivity.<br />
* <strong>Label:</strong> Drop the jumper, all the information is marked on the PCB and can also be disconnected by removing the 0R resistor.<br />
===Specifications===<br />
* Joystick: Mini PSP joystick for analog control<br />
* Light: RGB light for color output<br />
* Buzzer: Integrated buzzer for audible feedback<br />
* Buttons: Two buttons for user input<br />
* TFT Size: 3.5 inches TFT<br />
* TFT Resolution: 320x480 Pixels<br />
* TFT IC: ST7796SU1 (*May vary with lot*)<br />
* TFT Touch Type: Capacitive Touch Screen<br />
<br />
==Gallery==<br />
TBD.<br />
==Package Include==<br />
* 1 x Pico Breadboard Kit Plus version<br />
* 1 x 3.5" Capacitive Touch TFT (already installed on the kit)<br />
<br />
==Getting Start==<br />
* Install CMake (at least version 3.13), and GCC cross compiler '''(Raspberry Pi OSis pre-installed by default, other systems please install it yourself.)'''<br />
<pre><br />
sudo apt install cmake gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib<br />
</pre><br />
<br />
* Install Pico-SDK in Your OS(like Raspberry Pi OS).<br />
<br />
<pre><br />
wget https://github.com/raspberrypi/pico-setup/blob/master/pico_setup.sh -O pico_setup.sh<br />
chmod a+x pico_setup.sh<br />
./pico_setup.sh<br />
</pre><br />
<br />
* Download the demo project directly and build it.<br />
<br />
<pre><br />
cd /home/pi/<br />
git clone --recursive https://github.com/geeekpi/pico_breakboard_kit.git<br />
Build Projects<br />
cd pico_breakboard_kit/<br />
mkdir build<br />
cd build/<br />
cmake --no-warn-unused-cli -DPICO_OPTIMIZED_DEBUG=1 -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug ../<br />
make -j4<br />
</pre><br />
<br />
Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi. Execute following command to copy the *.uf2 file to Pico.<br />
<pre><br />
cp firmware.uf2 /media/pi/RPI-RP2/<br />
</pre><br />
<br />
After a while, when the firmware has been uploaded to Pico, it will restart automatically, you can test the demo code according to the information on screen. Have fun!<br />
<br />
''If you want to do UI development, please refer to the LVGL development guide, we have implemented the screen and touch driver, you can use it directly.''<br />
<br />
==FAQ==<br />
* Q: Why is is so slow when I drag the circle ring on screen? <br />
<pre>Because of the memory of pico is just 264KB, and graphic interface may consume a lot of memory to show the graphic widget.</pre><br />
* Q: Can I use MicroPython with LVGL to drive the screen? <br />
<pre>No, it is lack of memory, so it may stack when you upload the firmware.</pre><br />
==Firmware Download==<br />
* Firmware Demo: [[ File:Pico breadboard kit Plus verison demo firmware.zip ]]<br />
===How to use it?===<br />
* Download the firmware demo and unzip it.<br />
* Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi.<br />
* Copy the *.uf2 file to RPI-RP2 folder, that's it. <br />
==GitHub==<br />
* Repository on GitHub: [ https://github.com/geeekpi/pico_breakboard_kit ]<br />
==Keywords==<br />
* Pico Breadboard Kit, 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, buttons, prototyping, experimentation, interactive projects, user-friendly interface.</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0172&diff=13311EP-01722023-06-16T06:02:54Z<p>TaterLi: /* Package Include */</p>
<hr />
<div>==Pico Breadboard Kit Plus version==<br />
==Description==<br />
The Pico Breadboard Kit with a 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, and two buttons is a versatile electronics kit designed for prototyping and experimentation. This compact kit combines various components to create interactive projects and offers a user-friendly interface.<br />
==Features==<br />
* <strong>3.5-inch Capacitive Touch Screen:</strong> The kit includes a high-resolution touch screen for displaying visual outputs and receiving user input.<br />
* <strong>Mini PSP Joystick:</strong> The built-in mini joystick provides precise analog control for navigating menus and controlling movement in projects.<br />
* <strong>RGB Light:</strong> The kit features an RGB light that can emit various colors, allowing for dynamic visual effects and status indicators.<br />
* <strong>Buzzer:</strong> An integrated buzzer produces audible feedback, enabling sound effects or alerts in your projects.<br />
* <strong>Two Buttons:</strong> The kit includes two buttons for user input, providing additional control options and interactivity.<br />
* <strong>Label:</strong> Drop the jumper, all the information is marked on the PCB and can also be disconnected by removing the 0R resistor.<br />
===Specifications===<br />
* Screen Size: 3.5 inches TFT <br />
* Joystick: Mini PSP joystick for analog control<br />
* Light: RGB light for color output<br />
* Buzzer: Integrated buzzer for audible feedback<br />
* Buttons: Two buttons for user input<br />
* Resolution: 320x480 Pixels<br />
* Screen IC: ST7796SU1<br />
* Input Voltage: 3.3V<br />
* Touch Type: Capacitive Touch Screen<br />
<br />
==Gallery==<br />
TBD.<br />
==Package Include==<br />
* 1 x Pico Breadboard Kit Plus version<br />
* 1 x 3.5" Capacitive Touch TFT (already installed on the kit)<br />
<br />
==Getting Start==<br />
* Install CMake (at least version 3.13), and GCC cross compiler '''(Raspberry Pi OSis pre-installed by default, other systems please install it yourself.)'''<br />
<pre><br />
sudo apt install cmake gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib<br />
</pre><br />
<br />
* Install Pico-SDK in Your OS(like Raspberry Pi OS).<br />
<br />
<pre><br />
wget https://github.com/raspberrypi/pico-setup/blob/master/pico_setup.sh -O pico_setup.sh<br />
chmod a+x pico_setup.sh<br />
./pico_setup.sh<br />
</pre><br />
<br />
* Download the demo project directly and build it.<br />
<br />
<pre><br />
cd /home/pi/<br />
git clone --recursive https://github.com/geeekpi/pico_breakboard_kit.git<br />
Build Projects<br />
cd pico_breakboard_kit/<br />
mkdir build<br />
cd build/<br />
cmake --no-warn-unused-cli -DPICO_OPTIMIZED_DEBUG=1 -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug ../<br />
make -j4<br />
</pre><br />
<br />
Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi. Execute following command to copy the *.uf2 file to Pico.<br />
<pre><br />
cp firmware.uf2 /media/pi/RPI-RP2/<br />
</pre><br />
<br />
After a while, when the firmware has been uploaded to Pico, it will restart automatically, you can test the demo code according to the information on screen. Have fun!<br />
<br />
''If you want to do UI development, please refer to the LVGL development guide, we have implemented the screen and touch driver, you can use it directly.''<br />
<br />
==FAQ==<br />
* Q: Why is is so slow when I drag the circle ring on screen? <br />
<pre>Because of the memory of pico is just 264KB, and graphic interface may consume a lot of memory to show the graphic widget.</pre><br />
* Q: Can I use MicroPython with LVGL to drive the screen? <br />
<pre>No, it is lack of memory, so it may stack when you upload the firmware.</pre><br />
==Firmware Download==<br />
* Firmware Demo: [[ File:Pico breadboard kit Plus verison demo firmware.zip ]]<br />
===How to use it?===<br />
* Download the firmware demo and unzip it.<br />
* Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi.<br />
* Copy the *.uf2 file to RPI-RP2 folder, that's it. <br />
==GitHub==<br />
* Repository on GitHub: [ https://github.com/geeekpi/pico_breakboard_kit ]<br />
==Keywords==<br />
* Pico Breadboard Kit, 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, buttons, prototyping, experimentation, interactive projects, user-friendly interface.</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0172&diff=13310EP-01722023-06-16T06:02:04Z<p>TaterLi: /* Getting Start */</p>
<hr />
<div>==Pico Breadboard Kit Plus version==<br />
==Description==<br />
The Pico Breadboard Kit with a 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, and two buttons is a versatile electronics kit designed for prototyping and experimentation. This compact kit combines various components to create interactive projects and offers a user-friendly interface.<br />
==Features==<br />
* <strong>3.5-inch Capacitive Touch Screen:</strong> The kit includes a high-resolution touch screen for displaying visual outputs and receiving user input.<br />
* <strong>Mini PSP Joystick:</strong> The built-in mini joystick provides precise analog control for navigating menus and controlling movement in projects.<br />
* <strong>RGB Light:</strong> The kit features an RGB light that can emit various colors, allowing for dynamic visual effects and status indicators.<br />
* <strong>Buzzer:</strong> An integrated buzzer produces audible feedback, enabling sound effects or alerts in your projects.<br />
* <strong>Two Buttons:</strong> The kit includes two buttons for user input, providing additional control options and interactivity.<br />
* <strong>Label:</strong> Drop the jumper, all the information is marked on the PCB and can also be disconnected by removing the 0R resistor.<br />
===Specifications===<br />
* Screen Size: 3.5 inches TFT <br />
* Joystick: Mini PSP joystick for analog control<br />
* Light: RGB light for color output<br />
* Buzzer: Integrated buzzer for audible feedback<br />
* Buttons: Two buttons for user input<br />
* Resolution: 320x480 Pixels<br />
* Screen IC: ST7796SU1<br />
* Input Voltage: 3.3V<br />
* Touch Type: Capacitive Touch Screen<br />
<br />
==Gallery==<br />
TBD.<br />
==Package Include==<br />
* 1 x Pico Breadboard Kit Plus version<br />
==Getting Start==<br />
* Install CMake (at least version 3.13), and GCC cross compiler '''(Raspberry Pi OSis pre-installed by default, other systems please install it yourself.)'''<br />
<pre><br />
sudo apt install cmake gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib<br />
</pre><br />
<br />
* Install Pico-SDK in Your OS(like Raspberry Pi OS).<br />
<br />
<pre><br />
wget https://github.com/raspberrypi/pico-setup/blob/master/pico_setup.sh -O pico_setup.sh<br />
chmod a+x pico_setup.sh<br />
./pico_setup.sh<br />
</pre><br />
<br />
* Download the demo project directly and build it.<br />
<br />
<pre><br />
cd /home/pi/<br />
git clone --recursive https://github.com/geeekpi/pico_breakboard_kit.git<br />
Build Projects<br />
cd pico_breakboard_kit/<br />
mkdir build<br />
cd build/<br />
cmake --no-warn-unused-cli -DPICO_OPTIMIZED_DEBUG=1 -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug ../<br />
make -j4<br />
</pre><br />
<br />
Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi. Execute following command to copy the *.uf2 file to Pico.<br />
<pre><br />
cp firmware.uf2 /media/pi/RPI-RP2/<br />
</pre><br />
<br />
After a while, when the firmware has been uploaded to Pico, it will restart automatically, you can test the demo code according to the information on screen. Have fun!<br />
<br />
''If you want to do UI development, please refer to the LVGL development guide, we have implemented the screen and touch driver, you can use it directly.''<br />
<br />
==FAQ==<br />
* Q: Why is is so slow when I drag the circle ring on screen? <br />
<pre>Because of the memory of pico is just 264KB, and graphic interface may consume a lot of memory to show the graphic widget.</pre><br />
* Q: Can I use MicroPython with LVGL to drive the screen? <br />
<pre>No, it is lack of memory, so it may stack when you upload the firmware.</pre><br />
==Firmware Download==<br />
* Firmware Demo: [[ File:Pico breadboard kit Plus verison demo firmware.zip ]]<br />
===How to use it?===<br />
* Download the firmware demo and unzip it.<br />
* Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi.<br />
* Copy the *.uf2 file to RPI-RP2 folder, that's it. <br />
==GitHub==<br />
* Repository on GitHub: [ https://github.com/geeekpi/pico_breakboard_kit ]<br />
==Keywords==<br />
* Pico Breadboard Kit, 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, buttons, prototyping, experimentation, interactive projects, user-friendly interface.</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0172&diff=13309EP-01722023-06-16T06:01:16Z<p>TaterLi: /* Features */</p>
<hr />
<div>==Pico Breadboard Kit Plus version==<br />
==Description==<br />
The Pico Breadboard Kit with a 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, and two buttons is a versatile electronics kit designed for prototyping and experimentation. This compact kit combines various components to create interactive projects and offers a user-friendly interface.<br />
==Features==<br />
* <strong>3.5-inch Capacitive Touch Screen:</strong> The kit includes a high-resolution touch screen for displaying visual outputs and receiving user input.<br />
* <strong>Mini PSP Joystick:</strong> The built-in mini joystick provides precise analog control for navigating menus and controlling movement in projects.<br />
* <strong>RGB Light:</strong> The kit features an RGB light that can emit various colors, allowing for dynamic visual effects and status indicators.<br />
* <strong>Buzzer:</strong> An integrated buzzer produces audible feedback, enabling sound effects or alerts in your projects.<br />
* <strong>Two Buttons:</strong> The kit includes two buttons for user input, providing additional control options and interactivity.<br />
* <strong>Label:</strong> Drop the jumper, all the information is marked on the PCB and can also be disconnected by removing the 0R resistor.<br />
===Specifications===<br />
* Screen Size: 3.5 inches TFT <br />
* Joystick: Mini PSP joystick for analog control<br />
* Light: RGB light for color output<br />
* Buzzer: Integrated buzzer for audible feedback<br />
* Buttons: Two buttons for user input<br />
* Resolution: 320x480 Pixels<br />
* Screen IC: ST7796SU1<br />
* Input Voltage: 3.3V<br />
* Touch Type: Capacitive Touch Screen<br />
<br />
==Gallery==<br />
TBD.<br />
==Package Include==<br />
* 1 x Pico Breadboard Kit Plus version<br />
==Getting Start==<br />
* Install CMake (at least version 3.13), and GCC cross compiler '''(Raspberry Pi OSis pre-installed by default, other systems please install it yourself.)'''<br />
<pre><br />
sudo apt install cmake gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib<br />
</pre><br />
<br />
* Install Pico-SDK in Your OS(like Raspberry Pi OS).<br />
<br />
<pre><br />
wget https://github.com/raspberrypi/pico-setup/blob/master/pico_setup.sh -O pico_setup.sh<br />
chmod a+x pico_setup.sh<br />
./pico_setup.sh<br />
</pre><br />
<br />
* Download the demo project directly and build it.<br />
<br />
<pre><br />
cd /home/pi/<br />
git clone --recursive https://github.com/geeekpi/pico_breakboard_kit.git<br />
Build Projects<br />
cd pico_breakboard_kit/<br />
mkdir build<br />
cd build/<br />
cmake --no-warn-unused-cli -DPICO_OPTIMIZED_DEBUG=1 -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug ../<br />
make -j4<br />
</pre><br />
<br />
Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi. Execute following command to copy the *.uf2 file to Pico.<br />
<pre><br />
cp firmware.uf2 /media/pi/RPI-RP2/<br />
</pre><br />
<br />
After a while, when the firmware has been uploaded to Pico, it will restart automatically, you can test the demo code according to the information on screen. Have fun!<br />
<br />
==FAQ==<br />
* Q: Why is is so slow when I drag the circle ring on screen? <br />
<pre>Because of the memory of pico is just 264KB, and graphic interface may consume a lot of memory to show the graphic widget.</pre><br />
* Q: Can I use MicroPython with LVGL to drive the screen? <br />
<pre>No, it is lack of memory, so it may stack when you upload the firmware.</pre><br />
==Firmware Download==<br />
* Firmware Demo: [[ File:Pico breadboard kit Plus verison demo firmware.zip ]]<br />
===How to use it?===<br />
* Download the firmware demo and unzip it.<br />
* Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi.<br />
* Copy the *.uf2 file to RPI-RP2 folder, that's it. <br />
==GitHub==<br />
* Repository on GitHub: [ https://github.com/geeekpi/pico_breakboard_kit ]<br />
==Keywords==<br />
* Pico Breadboard Kit, 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, buttons, prototyping, experimentation, interactive projects, user-friendly interface.</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0172&diff=13308EP-01722023-06-16T05:59:29Z<p>TaterLi: /* Getting Start */</p>
<hr />
<div>==Pico Breadboard Kit Plus version==<br />
==Description==<br />
The Pico Breadboard Kit with a 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, and two buttons is a versatile electronics kit designed for prototyping and experimentation. This compact kit combines various components to create interactive projects and offers a user-friendly interface.<br />
==Features==<br />
* <strong>3.5-inch Touch Screen:</strong> The kit includes a high-resolution touch screen for displaying visual outputs and receiving user input.<br />
* <strong>Mini PSP Joystick:</strong> The built-in mini joystick provides precise analog control for navigating menus and controlling movement in projects.<br />
* <strong>RGB Light:</strong> The kit features an RGB light that can emit various colors, allowing for dynamic visual effects and status indicators.<br />
* <strong>Buzzer:</strong> An integrated buzzer produces audible feedback, enabling sound effects or alerts in your projects.<br />
* <strong>Two Buttons:</strong> The kit includes two buttons for user input, providing additional control options and interactivity.<br />
===Specifications===<br />
* Screen Size: 3.5 inches TFT <br />
* Joystick: Mini PSP joystick for analog control<br />
* Light: RGB light for color output<br />
* Buzzer: Integrated buzzer for audible feedback<br />
* Buttons: Two buttons for user input<br />
* Resolution: 320x480 Pixels<br />
* Screen IC: ST7796SU1<br />
* Input Voltage: 3.3V<br />
* Touch Type: Capacitive Touch Screen<br />
==Gallery==<br />
TBD.<br />
==Package Include==<br />
* 1 x Pico Breadboard Kit Plus version<br />
==Getting Start==<br />
* Install CMake (at least version 3.13), and GCC cross compiler '''(Raspberry Pi OSis pre-installed by default, other systems please install it yourself.)'''<br />
<pre><br />
sudo apt install cmake gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib<br />
</pre><br />
<br />
* Install Pico-SDK in Your OS(like Raspberry Pi OS).<br />
<br />
<pre><br />
wget https://github.com/raspberrypi/pico-setup/blob/master/pico_setup.sh -O pico_setup.sh<br />
chmod a+x pico_setup.sh<br />
./pico_setup.sh<br />
</pre><br />
<br />
* Download the demo project directly and build it.<br />
<br />
<pre><br />
cd /home/pi/<br />
git clone --recursive https://github.com/geeekpi/pico_breakboard_kit.git<br />
Build Projects<br />
cd pico_breakboard_kit/<br />
mkdir build<br />
cd build/<br />
cmake --no-warn-unused-cli -DPICO_OPTIMIZED_DEBUG=1 -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug ../<br />
make -j4<br />
</pre><br />
<br />
Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi. Execute following command to copy the *.uf2 file to Pico.<br />
<pre><br />
cp firmware.uf2 /media/pi/RPI-RP2/<br />
</pre><br />
<br />
After a while, when the firmware has been uploaded to Pico, it will restart automatically, you can test the demo code according to the information on screen. Have fun!<br />
<br />
==FAQ==<br />
* Q: Why is is so slow when I drag the circle ring on screen? <br />
<pre>Because of the memory of pico is just 264KB, and graphic interface may consume a lot of memory to show the graphic widget.</pre><br />
* Q: Can I use MicroPython with LVGL to drive the screen? <br />
<pre>No, it is lack of memory, so it may stack when you upload the firmware.</pre><br />
==Firmware Download==<br />
* Firmware Demo: [[ File:Pico breadboard kit Plus verison demo firmware.zip ]]<br />
===How to use it?===<br />
* Download the firmware demo and unzip it.<br />
* Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi.<br />
* Copy the *.uf2 file to RPI-RP2 folder, that's it. <br />
==GitHub==<br />
* Repository on GitHub: [ https://github.com/geeekpi/pico_breakboard_kit ]<br />
==Keywords==<br />
* Pico Breadboard Kit, 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, buttons, prototyping, experimentation, interactive projects, user-friendly interface.</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0172&diff=13307EP-01722023-06-16T05:58:42Z<p>TaterLi: /* Getting Start */</p>
<hr />
<div>==Pico Breadboard Kit Plus version==<br />
==Description==<br />
The Pico Breadboard Kit with a 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, and two buttons is a versatile electronics kit designed for prototyping and experimentation. This compact kit combines various components to create interactive projects and offers a user-friendly interface.<br />
==Features==<br />
* <strong>3.5-inch Touch Screen:</strong> The kit includes a high-resolution touch screen for displaying visual outputs and receiving user input.<br />
* <strong>Mini PSP Joystick:</strong> The built-in mini joystick provides precise analog control for navigating menus and controlling movement in projects.<br />
* <strong>RGB Light:</strong> The kit features an RGB light that can emit various colors, allowing for dynamic visual effects and status indicators.<br />
* <strong>Buzzer:</strong> An integrated buzzer produces audible feedback, enabling sound effects or alerts in your projects.<br />
* <strong>Two Buttons:</strong> The kit includes two buttons for user input, providing additional control options and interactivity.<br />
===Specifications===<br />
* Screen Size: 3.5 inches TFT <br />
* Joystick: Mini PSP joystick for analog control<br />
* Light: RGB light for color output<br />
* Buzzer: Integrated buzzer for audible feedback<br />
* Buttons: Two buttons for user input<br />
* Resolution: 320x480 Pixels<br />
* Screen IC: ST7796SU1<br />
* Input Voltage: 3.3V<br />
* Touch Type: Capacitive Touch Screen<br />
==Gallery==<br />
TBD.<br />
==Package Include==<br />
* 1 x Pico Breadboard Kit Plus version<br />
==Getting Start==<br />
* Install CMake (at least version 3.13), and GCC cross compiler '''(Raspbian is pre-installed by default, other systems please install it yourself.)'''<br />
<pre><br />
sudo apt install cmake gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib<br />
</pre><br />
<br />
* Install Pico-SDK in Raspberry Pi Assume that you are using Raspberry Pi OS 64bit (Bullseye) as operating system on Raspberry Pi. Here we are using Raspberry Pi 4B as PC to compile the project.<br />
<br />
<pre><br />
wget https://github.com/raspberrypi/pico-setup/blob/master/pico_setup.sh -O pico_setup.sh<br />
chmod a+x pico_setup.sh<br />
./pico_setup.sh<br />
</pre><br />
<br />
* Download the demo project directly and build it.<br />
<br />
<pre><br />
cd /home/pi/<br />
git clone --recursive https://github.com/geeekpi/pico_breakboard_kit.git<br />
Build Projects<br />
cd pico_breakboard_kit/<br />
mkdir build<br />
cd build/<br />
cmake --no-warn-unused-cli -DPICO_OPTIMIZED_DEBUG=1 -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug ../<br />
make -j4<br />
</pre><br />
<br />
Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi. Execute following command to copy the *.uf2 file to Pico.<br />
<pre><br />
cp firmware.uf2 /media/pi/RPI-RP2/<br />
</pre><br />
<br />
After a while, when the firmware has been uploaded to Pico, it will restart automatically, you can test the demo code according to the information on screen. Have fun!<br />
<br />
==FAQ==<br />
* Q: Why is is so slow when I drag the circle ring on screen? <br />
<pre>Because of the memory of pico is just 264KB, and graphic interface may consume a lot of memory to show the graphic widget.</pre><br />
* Q: Can I use MicroPython with LVGL to drive the screen? <br />
<pre>No, it is lack of memory, so it may stack when you upload the firmware.</pre><br />
==Firmware Download==<br />
* Firmware Demo: [[ File:Pico breadboard kit Plus verison demo firmware.zip ]]<br />
===How to use it?===<br />
* Download the firmware demo and unzip it.<br />
* Upload firmware to Pico Unplug Raspberry Pi Pico from Raspberry Pi and press boot_sel button and then connect the Raspberry Pi Pico back to Raspberry Pi.<br />
* Copy the *.uf2 file to RPI-RP2 folder, that's it. <br />
==GitHub==<br />
* Repository on GitHub: [ https://github.com/geeekpi/pico_breakboard_kit ]<br />
==Keywords==<br />
* Pico Breadboard Kit, 3.5-inch touch screen, mini PSP joystick, RGB light, buzzer, buttons, prototyping, experimentation, interactive projects, user-friendly interface.</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0168&diff=12874EP-01682023-04-14T02:03:11Z<p>TaterLi: Update the compatibilty</p>
<hr />
<div>==LED Screw Terminal Hat for Raspberry Pi==<br />
[[File:EP-0168-7.jpg|right|320px]]<br />
<br />
==Descriptions==<br />
LED Screw Terminal Hat for Raspberry Pi is a GPIO expansion board which is for easy connecting to the 40-Pins GPIO of Raspberry Pi and it can be observing the Pin status via LED indicators, once the GPIO has level changed, the led indicator will be blinking.<br />
<pre> <br />
NOTE: Raspberry Pi board dose not include in the package, additional purchase required!!<br />
</pre><br />
<br />
==Features==<br />
* Compatibility: Raspberry Pi 40Pin GPIO (Raspberry Pi 4B/3B/3B+/zero/zero w/zero 2w)<br />
* Easy to assemble<br />
* Screw terminal <br />
* GPIO LED indicator <br />
* Stable connection for wiring circuit<br />
* GPIO function mark sticky<br />
<br />
==Specifications==<br />
* GPIO status LED and power 5V / 3.3V indication. <br />
* GPIO output level high LED on, output level low LED off. <br />
* 5V Red , 3.3V Red, GPIOs Light blue. <br />
* The driving current of each LED is 4-6mA. <br />
* Terminal block pitch 2.54mm/0.1", wire size range 28AWG to 18AWG, strip length 4.5mm, screw M1.6 steel, pin header and cage copper.<br />
* 2x20 positions header connect to Raspberry Pi board<br />
* FR-4 fiber glass PCB, dual copper layers.<br />
* M2.5 Mounting Hole<br />
* Dimension: 61mm x 35mm x 20mm<br />
[[File:EP-0168-13.jpg|left|800px]]<br />
<br style="clear:both;"><br />
<br />
==Gallery==<br />
* Product Outlook<br />
{|<br />
|[[File:EP-0168-10.jpg|left|320px]]<br />
|[[File:EP-0168-9.jpg|none|320px]]<br />
|[[File:EP-0168-8.jpg|none|320px]]<br />
|}<br />
* Application scenario <br />
[[File:EP-0168-6.jpg|left|800px]]<br />
<br style="clear:both;"><br />
[[File:EP-0168-4.jpg|left|800px]]<br />
<br style="clear:both;"><br />
* Assembled Status<br />
{|<br />
|[[File:EP-0168-1.jpg|left|320px]]<br />
|[[File:EP-0168-2.jpg|none|320px]]<br />
|[[File:EP-0168-3.jpg|none|320px]]<br />
|}<br />
<font color=red >Note: Please make sure the white dot is against to GPIO Pin 2 (Physical Number 2，which is 5V), wrong direction may damage your Pi!!!</font><br />
<br />
==How to assemble it==<br />
* Peel off the protection film from both side of acrylic panel.<br />
* Fix copper pillar to acrylic panel with M2.5 screws.<br />
* Fix Raspberry Pi to acrylic panel with copper pillar and screws.<br />
* Connect LED screw terminal hat to GPIO Pins.(make sure the white dot facing 5V on GPIO Pin) please Note that mark point position.<br />
* Fix screw terminal hat with screws. <br />
* Unscrew the terminal and insert jump wire, and screw it tight. (make sure the copper wire is connect to screw terminal properly)<br />
<font color=red> The LED screw terminal hat does not have any protection circuit on the board, please double check the circuit that you build, wrong connection may damage your Pi, it is on your own risk.</font><br />
[[File:EP-0168-14.jpg|left|800px]]<br />
<br style="clear:both;"><br />
<br />
==Package Includes==<br />
* 1 x LED screw terminal hat pack<br />
[[File:EP-0168-11.jpg|left|800px]]<br />
<br style="clear:both;"><br />
<br />
==Keywords==<br />
* LED Screw Terminal Hat for Raspberry Pi, Screw terminal hat, 40pin screw terminal hat</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0136&diff=11742EP-01362021-12-01T02:44:32Z<p>TaterLi: </p>
<hr />
<div>==UPS Plus==<br />
[[File:UPS V2 1.jpg|right|320px]]<br />
==Descriptions==<br />
UPS Plus is a new generation of UPS power management module which supports OTA firmware upgrade and supports RTC onboard. <br><br />
And there are two INA219 chip onboard to detect batteries voltage and the voltage output from UPS Plus to Raspberry Pi.<br><br />
<br />
==Compatibility==<br />
{| class="wikitable"<br />
|-<br />
! Raspberry Model !! Compatibility <br />
|-<br />
| Raspberry Pi A || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi A+ ||<font color=green>YES</font><br />
|-<br />
| Raspberry Pi B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi B+ ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 2B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B+ || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 4B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi Zero || <font color=red>NO</font><br />
|-<br />
|Raspberry Pi Zero W ||<font color=red>NO</font><br />
|}<br />
<br />
==Features==<br />
* Easy to install<br />
* Enhanced power management<br />
* Remote OTA firmware upgrade<br />
* Programmable BACK-TO-AC auto power up<br />
* Programmable sample period<br />
* I2C communication<br />
* Standalone RTC<br />
* Support stacked battery design<br />
===Specifications===<br />
* Current/voltage monitoring of Raspberry Pi power supply port.<br />
* Battery terminal current/voltage monitoring, supports two-way monitoring of charge and discharge.<br />
* Independent RTC function.<br />
* OTA function (supports forced upgrade mode and active upgrade mode).<br />
* Power estimation<br />
<pre>Note: At least one full charge and discharge cycle must be completed!)</pre><br />
* Adjustable sampling period.<br />
* Support FCP, AFC, SFCP fast charge protocol.<br />
* Support BC1.2 charging protocol.<br />
* Battery temperature monitoring <br />
<pre>Note: the forced temperature protection cannot be turned off, threshold: 65 degrees!</pre><br />
* Programmable Power Voltage Detector(PVD) function, Default value: 3.6V <br />
* Incoming call self-start function.<br />
* Power down memory function.<br />
* Programmable shutdown / forced restart.<br />
* Running time statistics <br />
* Electrostatic protection.<br />
* Linear compensation range discharge capacity: 5V 4.5A.<br />
* Non-linear compensation range discharge capacity: 5V 8A.<br />
* Charging capacity 4.5V 5A/5V 2.5A/9V 2A/12V 1.5A.<br />
* Stacked battery design<br />
<pre>NOTE: Stacked power board need to be special accessories.Can not support None official accessories.</pre><br />
* Use I2C communication without occupying additional ports.<br />
* Support 4.2V 4.35V 4.4V 4.5V 18650 lithium battery <br />
<pre>Note: Different types of batteries cannot be mixed!</pre><br />
* After-sales data telemetry.<br />
<br />
===Register Mapping===<br />
===USB Plus V5.0 Register Mapping Chart===<br />
* 0x17 - Operation Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function !! Range !! Unit<br />
|-<br />
| 0x01 - 0x02 || Voltage of UPS's MCU || 2400 - 3600 || mV <br />
|-<br />
| 0x03 - 0x04 || Voltage of Pogopin's Bottom || 0 - 5500 || mV <br />
|-<br />
| 0x05 - 0x06 || Voltage of Batteries' Terminal || 0 - 4500 || mV <br />
|-<br />
| 0x07 - 0x08 || Voltage of USB-C Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x09 - 0x0A || Voltage of MicroUSB Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x0B - 0x0C || Batteries Temperature || -20 - 65 || ℃ <br />
|-<br />
| 0x0D - 0x0E || Full Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x0F - 0x10 || Empty Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x11 - 0x12 || Protection Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x13 - 0x14 || Battery Remaining || 0 - 100 || % <br />
|-<br />
| 0x15 - 0x16 || Sample Period || 1 - 1440 || Min<br />
|-<br />
| 0x17 || Power Status/Operation Mode || 0/1 || Bool <br />
|-<br />
| 0x18 || Shutdown Countdown || 0(False)/10 - 255 || Bool/Sec <br />
|-<br />
| 0x19 || Back-To-AC Auto Power up || 0/1 || Bool<br />
|-<br />
| 0x1A || Restart Countdown || 0(False)/10- 255 || Bool/Sec<br />
|-<br />
| 0x1B || Reset to Factory Defaults || 0/1 || Bool <br />
|-<br />
| 0x1C - 0x1F || Cumulative Running Time || 0 - 2147483647 || Sec <br />
|-<br />
| 0x20 - 0x23 || Accumulated Charging Time || 0 - 2147483647|| Sec<br />
|-<br />
| 0x24 - 0x27 || Running Time || 0 - 2147483647 || Sec<br />
|-<br />
| 0x28 - 0x29 || Version || 1 || Fixed <br />
|-<br />
| 0x2A || (FW.V5+) Battery Parameters self-programmed by user|| 0/1 || Bool<br />
|-<br />
| 0x2B - 0xEF || [Reserved] || NA || NA<br />
|-<br />
| 0xF0 - 0xFB || Serial Number || Device UID || Fixed<br />
|-<br />
| 0xFC - 0xFF || Factory Testing || NA || NA<br />
|}<br />
* 0x18 - OTA Firmware Upgrade Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function <br />
|-<br />
| 0x01 - 0x10 || Encrypted buffer<br />
|-<br />
| 0x11 - 0xEF || [Reserved]<br />
|-<br />
| 0xF0 - 0xFB || Serial Number<br />
|-<br />
| 0xFC - 0xFF || Factory Test<br />
|}<br />
<br />
==Gallery==<br />
* Product Outlook<br />
{|<br />
|[[File:UPS V2 1.jpg|left|320px]]<br />
|[[File:UPS V2 2.jpg|left|320px]]<br />
|[[File:UPS V2 3.jpg|left|320px]]<br />
|}<br />
* Application scenario<br />
[[File:UPS V2 13.jpg|left|800px]]<br />
<br style="clear:both;"><br />
===PCB Drawing===<br />
* PCBDOC File: [[ File:UPS PLUS PCBDOC.zip ]]<br />
<br />
===Function Area Display===<br />
* Function Details <br />
{|<br />
|[[File:UPS V2 10.jpg|left|320px]]<br />
|[[File:UPS V2 11.jpg|none|320px]]<br />
|[[File:UPS V2 12.jpg|none|320px]]<br />
|}<br />
<br />
===LED light status definition===<br />
* Discharge Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| C >= 75% || ON || ON || ON || ON <br />
|-<br />
| 50% <= C <75% || ON || ON || ON || OFF <br />
|-<br />
| 25% <= C <50% || ON || ON || OFF || OFF <br />
|-<br />
| 0% <= C < 25% || ON || OFF || OFF || OFF <br />
|-<br />
| Wrong Batteries Parameters || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br style="clear:both;"><br />
<br />
* Charging Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| 100% || ON || ON || ON || ON <br />
|-<br />
| 75% <= C|| ON || ON || ON || 1.5Hz Blink<br />
|-<br />
| 50% <= C <75% || ON || ON || 1.5Hz Blink || OFF <br />
|-<br />
| 25% <= C < 50% || ON || 1.5Hz Blink || OFF || OFF <br />
|-<br />
| C < 25% || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br />
==How To Assemble==<br />
* How to Assemble<br />
[[File:UPS V2 4-2.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==How To Use==<br />
===General Settings===<br />
* Download the latest Raspbian OS image from: [ https://www.raspberrypi.org/software/operating-systems/ ]<br />
* Unzip it and flash it to MicroSD card(TF card) with Etcher imaging tool. [ https://www.balena.io/etcher/ ]<br />
* Follow the installation method to assemble the Raspberry Pi and UPS Plus.<br />
* After booting up and make sure Raspberry Pi can access internet.<br />
* Enable <font color=red>I2C function</font> by using "raspi-config" tool, Navigate to "interface options" and select "I2C" and enable it follow the instructions.<br />
<pre> NOTE: It is very important to enable I2C function on Raspberry Pi, If miss this step, Raspberry Pi will not detect UPSPLUS module.</pre><br />
<pre> sudo raspi-config</pre> <br />
* Install smbus2 library.<br />
<pre>pip install smbus2</pre><br />
* Download repository from GitHub and entering the folder that contains demo code.<br />
<pre><br />
cd ~ <br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd upsplus/<br />
</pre><br />
<br />
===Automatic Shutdown Protection===<br />
* If you want to use one script to install upsplus's demo code, just follow the steps below.<br />
* Open a terminal by press "Ctrl+ALT+T" or just click terminal icon on the task bar.<br />
<pre>curl -Lso- https://git.io/JLygb | bash </pre><br />
or<br />
<pre>curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash</pre><br />
* When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Update UPS Firmware via OTA ===<br />
* Enter the OTA firmware upgrade mode:<br />
===Method 1===<br />
<font color=red>NOTE: Do not power off or disconnect the network during the upgrade process. If the upgrade fails, the UPS Pro will not work normally.</font><br />
* Power off the Raspberry Pi.<br />
* Cut off the external charging power (MicroUSB and USB-C)<br />
* Take out all the batteries.<br />
* Press and hold the UPS Pro switch key and insert the battery into the battery compartment.<br />
At this time, the device will be forced to enter OTA mode.<br><br />
<pre>The function of the switch button will no longer be available at this time.</pre><br />
The Raspberry Pi will be running and please execute the following python script in the system terminal to complete the upgrade. <br />
* Download python scripts from github:<br />
<pre><br />
cd ~<br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd ~/upsplus<br />
python3 OTA_firmware_upgrade.py<br />
</pre><br />
<font color=red><b>The first time it runs, it may prompt that the device is not registered.If it is a legal device, just wait a few seconds and try again.</b></font><br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===Method 2===<br />
* Open a terminal and typing: <br />
<pre>i2cset -y 1 0x17 50 127 b</pre><br />
* Shutdown Raspberry Pi and remove all batteries and power supply.<br />
* Insert batteries back into the battery slot.<br />
* Execute OTA_firmware_upgrade.py python script in a terminal.<br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===How To Collect Data===<br />
* Data Collection<br />
Data collection will only collect information on abnormal voltage changes and battery charging and discharging status during equipment operation through UPS in order to provide better after-sales service, and will not collect your private information. <br><br />
Please rest assured that every UPS we sell will Have a unique serial number so that we can provide battery quality analysis and feedback.<br><br />
It submits your UPS Pro operating status information to the server provided by us through a python script.<br><br />
* Download Repository and execute:<br />
<pre><br />
cd ~<br />
curl -Lso- https://git.io/JLygb | bash<br />
</pre><br />
When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Setup RTC===<br />
====Using Overlays====<br />
* Overlays are loaded using the "dtoverlay" config.txt setting. <br />
As an example,consider I2C Real Time Clock drivers. In the pre-DT world these would be loaded<br />
by writing a magic string comprising a device identifier and an I2C address to<br />
a special file in /sys/class/i2c-adapter, having first loaded the driver for<br />
the I2C interface and the RTC device - something like this:<br />
PS: sudo su means use root user to operate the system file, otherwise you may encount an error: "Permission denied"<br><br />
<pre><br />
sudo modprobe i2c-bcm2835<br />
sudo modprobe rtc-ds1307<br />
sudo su <br />
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device<br />
</pre><br />
With DT enabled, this becomes a line in config.txt:<br><br />
Edit /boot/config.txt file via vim.tiny tool or nano in a terminal:<br />
<code> sudo vim.tiny /boot/config.txt</code></br> <br />
And then add this parameter:<br><br />
<pre><br />
dtoverlay=i2c-rtc,ds1307<br />
</pre><br />
This causes the file /boot/overlays/i2c-rtc.dtbo to be loaded and a "node"<br />
describing the DS1307 I2C device to be added to the Device Tree for the Pi. By<br />
default it uses address 0x68, but this can be modified with an additional DT<br />
parameter:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307,addr=0x68<br />
</pre><br />
Parameters usually have default values, although certain parameters are<br />
mandatory. See the list of overlays below for a description of the parameters<br />
and their defaults.<br />
<br />
===For Raspberry Pi 4B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:DS1307-4B(1).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
[[File:DS1307-4B(2).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
please ensure that /boot/config.txt file include two paramaters:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307 <br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:DS1307-4B(6).png|thumb|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
----<br />
===How to test RTC===<br />
* Open terminal and typing: <br />
<pre>sudo hwclock -w </pre><br />
<pre>sudo hwclock </pre><br />
* Result will be like:<br />
<pre><br />
pi@upstest:~ $ sudo hwclock -w<br />
pi@upstest:~ $ sudo hwclock<br />
2021-05-12 11:41:23.601270+08:00<br />
</pre><br />
<br />
===For Raspberry Pi 3B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:Ds13076.png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
<pre>Name: i2c-rtc<br />
Info: Adds support for a number of I2C Real Time Clock devices<br />
Load: dtoverlay=i2c-rtc,<param>=<val><br />
Params: ds1307 Select the DS1307 device</pre><br />
please ensure that /boot/config.txt file include those three paramaters:<br />
<pre><br />
device_tree=bcm2710-rpi-3-b.dtb<br />
dtoverlay=i2c-rtc,ds1307<br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:Raspberry pi hwclock-set.png|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
<br />
===How To Adjust The Sampling Period===<br />
* If you want to change the sampling interval, you can change it with the following demo code in python:<br />
<font color=red>NOTE: Change the number of `SAMPLE_TIME` will adjust the sampling period: range from 2 to 60, unit minute. If the quality of the charger is not good, you need to increase the period, for example: adjust to 3~5, if the quality of the battery is not good, you need to decrease the sampling period, for example: 1~2 </font><br><br />
* Demo code:<br />
<pre><br />
import smbus<br />
<br />
DEVICE_BUS = 1<br />
DEVICE_ADDR = 0x17<br />
SAMPLE_TIME = 2 <br />
<br />
bus = smbus.SMBus(DEVICE_BUS)<br />
<br />
aReceiveBuf = []<br />
aReceiveBuf.append(0x00) <br />
<br />
bus.write_byte_data(DEVICE_ADDR, 21,SAMPLE_TIME & 0xFF)<br />
bus.write_byte_data(DEVICE_ADDR, 22,(SAMPLE_TIME >> 8)& 0xFF)<br />
<br />
print("Setting Sampling Period to: %d Min" % SAMPLE_TIME)<br />
</pre><br />
* Save it to a file and execute it:<br />
<pre>python3 ups_change_sample_period.py</pre><br />
=== How to detect if the battery is dead ===<br />
* There are two python scripts in the location /home/pi/bin/ after executing command "curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash" , as following picture:<br />
[[File:Ups location.jpg|left|320px]]<br />
<br style="clear:both;"><br />
* Execute the `upsPlus.py` script <font color=red><strong>2-3</strong></font>times through the following commands to determine whether the battery is continuously discharging, and if the charge is less than the discharge, the battery will soon be lower than the set shutdown threshold and shut down.<br />
At this time, you need to replace the battery, or change the sampling period, or replace the high-quality fast charger plug<br />
<pre> python3 /home/pi/bin/upsPlus.py </pre><br />
* For example:<br />
[[File:Ups batteries status.jpg|left|320px]]<br />
<br style="clear:both;"><br />
The battery shown in the figure：<font color=red>Battery Current (discharge) Rate: 1553.902 mA</font>, But the last information was: <font color=red>Currently charging via Micro USB Port.</font> <br />
There is a charging port inserted, but the battery discharge is displayed, which means the battery is bad.<br />
<br />
===How to Setup back-to-ac function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 25 1</pre><br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
===How to Setup shuting down countdown function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 24 20</pre><br />
PS: 20 means countdown number is 20 seconds, you can change to another integer number. <br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
<br />
===How to self-diagnose UPS PLUS ===<br />
* Please visit this URL in browser: [ https://api.52pi.com/ ]<br />
[[File:Ups diagnosistool.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Filling the blank with your Deivce UIDs which can be getting from /home/pi/bin/upsPlus_iot.py script, open a terminal and typing:<br />
<pre> python3 /home/pi/bin/upsPlus_iot.py </pre><br />
[[File:Ups uids.jpg|left | 500px]]<br />
<br style="clear:both;"><br />
* Copy UID0, UID1, UID2 to browser and press "Diagnosis" button on the page:<br />
[[File:Ups dignosis.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Then you will get the test results and suggestions on the page.<br />
[[File:Dignosis result.png|left|500px]]<br />
<br style="clear:both;"><br />
<font color=red> Pink color means it is critical message and Blue color means suggestion.</font><br />
<br />
==Parameter freezing issue==<br />
According to our tracking test, about 0.8% of users after a period of time, read the UPS parameters found that the value no longer changes, the cause of this is complex, and the number of users is small, we are working to solve this problem, if you encounter this problem, please try to completely reinstall the battery, power supply and Raspberry Pi and observe again, usually the problem is solved, if there are still problems, please contact us.<br />
<br />
==Battery Logger==<br />
* Thanks for Nordln's help.<br />
* UPS Plus Battery Logger: [ https://github.com/Nordln/upsplusv5-battery-logger.git ]<br />
[[File:Ups logger.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Package Includes==<br />
* 1 x UPS Plus For Raspberry Pi<br />
* 4 x M2.5 copper pillar <br />
* 4 x M2.5 screws<br />
* 4 x M2.5 long copper stick<br />
* 4 x M2.5 nuts<br />
* 1 x Acrylic shield<br />
* 1 x Instructions<br />
[[File:UPS V2 9.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Tutorial Video==<br />
* Youtube link:<br />
[ https://youtu.be/jQljQJ41I5A ]<br />
* QRCODE:<br />
[[File:Upsplus tutorial1.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: How to set battery capacity, Full voltage, low voltage?<br />
** A: It only affects the charging method and the calculation of the charge level, the protection threshold, and does not change the actual battery parameters. more info please refer to: [ https://github.com/geeekpi/upsplus/issues/80 ]<br />
* Q: Why it will turn on my Raspberry Pi once I plug the power supply into the charging port? <br />
** A: When the BACK-TO-AC function of the Raspberry Pi is turned on, the Raspberry Pi will be automatically activated when the external power supply is connected to the charging port. This setting is for some applications that use the Raspberry Pi as a server scenario, because the external power supply After the power is supplied, the UPS detects the charging status and executes the automatic startup operation, so that some scenes where the Raspberry Pi is placed in the computer room can easily start the Raspberry Pi, no need to press the button to start the UPS, if you want Using BACK-TO-AC, you can also turn off this function. After turning off this function, you need to press the power button again every time you start it. <br />
<br />
* Q: Why does my UPS shut down suddently and I can not turn it on? <br />
** A: Please use power supply with QC protocol and try to change batteries with better quality. we recommend you to connect QC power supply while your UPS need to provide service at 7x24. <br />
* Q: Why does the battery light go off sometime and lights up in a while? <br />
** A: This is because the power chip performs battery re-sampling, and the purpose is that the data of inferior batteries is inaccurate during the sampling process.<br />
* Q: Why is the power cut off every once in a while? <br />
** A: Please check the battery charging current, the data discharge direction or the charging direction. If the load is too large, the charging may not be enough, which will cause this problem.<br />
* Q: What kind of wall charger should I use? <br />
** A: If the load is normal, it is recommended to use an ordinary 5V@2A charging head. If you need to carry a slightly higher load, it is recommended to use a fast charging source. We support FCP, AFC, SFCP protocols Fast charging source.<br />
* Q: Can I directly input 9V and 12V to the USB port?<br />
** A: No, if you must do this, you must remove the DP, DM and other related detection pins, and ensure that the power supply is stable.<br />
* Q: I heard howling, why is this? <br />
** A: Because of the no-load protection mechanism, the howling will disappear after the load is installed.<br />
* Q: using firmware v. 4, when AC power comes back on during the shutdown countdown, I realized that the 5V supply for the raspberry pi is not switched off at the end of the countdown. so, after shutdown of the operating system, the raspberry pi will never restart automatically.<br />
IMHO the following would be better: once a shutdown countdown starts, and we have the Back-To-AC Auto Power UP flag set, then:<br />
the shutdown sequence should proceed to its end,<br />
switch off the 5V-power for a certain time (a couple of seconds maybe), regardless of AC Power.<br />
switch the 5V back on when AC power is restored.<br />
otherwise, I am very happy with the product.<br />
one more thing: would be nice to have some sort of alert for new firmware releases and release notes for these.<br />
** A: Please refer to this URL: https://github.com/geeekpi/upsplus/issues/7<br />
<br />
==Keywords==<br />
* UPS Plus, GeeekPi UPS V5, UPS for Raspberry Pi</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0136&diff=10484EP-01362021-06-20T11:36:13Z<p>TaterLi: /* How to self-diagnose UPS PLUS */</p>
<hr />
<div>==UPS Plus==<br />
[[File:UPS V2 1.jpg|right|320px]]<br />
==Descriptions==<br />
UPS Plus is a new generation of UPS power management module which supports OTA firmware upgrade and supports RTC onboard. <br><br />
And there are two INA219 chip onboard to detect batteries voltage and the voltage output from UPS Plus to Raspberry Pi.<br><br />
<br />
==Compatibility==<br />
{| class="wikitable"<br />
|-<br />
! Raspberry Model !! Compatibility <br />
|-<br />
| Raspberry Pi A || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi A+ ||<font color=green>YES</font><br />
|-<br />
| Raspberry Pi B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi B+ ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 2B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B+ || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 4B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi Zero || <font color=red>NO</font><br />
|-<br />
|Raspberry Pi Zero W ||<font color=red>NO</font><br />
|}<br />
<br />
==Features==<br />
* Easy to install<br />
* Enhanced power management<br />
* Remote OTA firmware upgrade<br />
* Programmable BACK-TO-AC auto power up<br />
* Programmable sample period<br />
* I2C communication<br />
* Standalone RTC<br />
* Support stacked battery design<br />
===Specifications===<br />
* Current/voltage monitoring of Raspberry Pi power supply port.<br />
* Battery terminal current/voltage monitoring, supports two-way monitoring of charge and discharge.<br />
* Independent RTC function.<br />
* OTA function (supports forced upgrade mode and active upgrade mode).<br />
* Power estimation<br />
<pre>Note: At least one full charge and discharge cycle must be completed!)</pre><br />
* Adjustable sampling period.<br />
* Support FCP, AFC, SFCP fast charge protocol.<br />
* Support BC1.2 charging protocol.<br />
* Battery temperature monitoring <br />
<pre>Note: the forced temperature protection cannot be turned off, threshold: 65 degrees!</pre><br />
* Programmable Power Voltage Detector(PVD) function, Default value: 3.6V <br />
* Incoming call self-start function.<br />
* Power down memory function.<br />
* Programmable shutdown / forced restart.<br />
* Running time statistics <br />
* Electrostatic protection.<br />
* Linear compensation range discharge capacity: 5V 4.5A.<br />
* Non-linear compensation range discharge capacity: 5V 8A.<br />
* Charging capacity 4.5V 5A/5V 2.5A/9V 2A/12V 1.5A.<br />
* Stacked battery design<br />
<pre>NOTE: Stacked power board need to be special accessories.Can not support None official accessories.</pre><br />
* Use I2C communication without occupying additional ports.<br />
* Support 4.2V 4.35V 4.4V 4.5V lithium battery <br />
<pre>Note: Different types of batteries cannot be mixed!</pre><br />
* After-sales data telemetry.<br />
<br />
===Register Mapping===<br />
===USB Plus V5.0 Register Mapping Chart===<br />
* 0x17 - Operation Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function !! Range !! Unit<br />
|-<br />
| 0x01 - 0x02 || Voltage of UPS's MCU || 2400 - 3600 || mV <br />
|-<br />
| 0x03 - 0x04 || Voltage of Pogopin's Bottom || 0 - 5500 || mV <br />
|-<br />
| 0x05 - 0x06 || Voltage of Batteries' Terminal || 0 - 4500 || mV <br />
|-<br />
| 0x07 - 0x08 || Voltage of USB-C Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x09 - 0x0A || Voltage of MicroUSB Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x0B - 0x0C || Batteries Temperature || -20 - 65 || ℃ <br />
|-<br />
| 0x0D - 0x0E || Full Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x0F - 0x10 || Empty Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x11 - 0x12 || Protection Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x13 - 0x14 || Battery Remaining || 0 - 100 || % <br />
|-<br />
| 0x15 - 0x16 || Sample Period || 1 - 1440 || Min<br />
|-<br />
| 0x17 || Power Status/Operation Mode || 0/1 || Bool <br />
|-<br />
| 0x18 || Shutdown Countdown || 0(False)/10 - 255 || Bool/Sec <br />
|-<br />
| 0x19 || Back-To-AC Auto Power up || 0/1 || Bool<br />
|-<br />
| 0x1A || Restart Countdown || 0(False)/10- 255 || Bool/Sec<br />
|-<br />
| 0x1B || Reset to Factory Defaults || 0/1 || Bool <br />
|-<br />
| 0x1C - 0x1F || Cumulative Running Time || 0 - 2147483647 || Sec <br />
|-<br />
| 0x20 - 0x23 || Accumulated Charging Time || 0 - 2147483647|| Sec<br />
|-<br />
| 0x24 - 0x27 || Running Time || 0 - 2147483647 || Sec<br />
|-<br />
| 0x28 - 0x29 || Version || 1 || Fixed <br />
|-<br />
| 0x2A || (FW.V5+) Battery Parameters self-programmed by user|| 0/1 || Bool<br />
|-<br />
| 0x2B - 0xEF || [Reserved] || NA || NA<br />
|-<br />
| 0xF0 - 0xFB || Serial Number || Device UID || Fixed<br />
|-<br />
| 0xFC - 0xFF || Factory Testing || NA || NA<br />
|}<br />
* 0x18 - OTA Firmware Upgrade Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function <br />
|-<br />
| 0x01 - 0x10 || Encrypted buffer<br />
|-<br />
| 0x11 - 0xEF || [Reserved]<br />
|-<br />
| 0xF0 - 0xFB || Serial Number<br />
|-<br />
| 0xFC - 0xFF || Factory Test<br />
|}<br />
<br />
==Gallery==<br />
* Product Outlook<br />
{|<br />
|[[File:UPS V2 1.jpg|left|320px]]<br />
|[[File:UPS V2 2.jpg|left|320px]]<br />
|[[File:UPS V2 3.jpg|left|320px]]<br />
|}<br />
* Application scenario<br />
[[File:UPS V2 13.jpg|left|800px]]<br />
<br style="clear:both;"><br />
===PCB Drawing===<br />
* PCBDOC File: [[ File:UPS PLUS PCBDOC.zip ]]<br />
<br />
===Function Area Display===<br />
* Function Details <br />
{|<br />
|[[File:UPS V2 10.jpg|left|320px]]<br />
|[[File:UPS V2 11.jpg|none|320px]]<br />
|[[File:UPS V2 12.jpg|none|320px]]<br />
|}<br />
<br />
===LED light status definition===<br />
* Discharge Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| C >= 75% || ON || ON || ON || ON <br />
|-<br />
| 50% <= C <75% || ON || ON || ON || OFF <br />
|-<br />
| 25% <= C <50% || ON || ON || OFF || OFF <br />
|-<br />
| 0% <= C < 25% || ON || OFF || OFF || OFF <br />
|-<br />
| Wrong Batteries Parameters || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br style="clear:both;"><br />
<br />
* Charging Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| 100% || ON || ON || ON || ON <br />
|-<br />
| 75% <= C|| ON || ON || ON || 1.5Hz Blink<br />
|-<br />
| 50% <= C <75% || ON || ON || 1.5Hz Blink || OFF <br />
|-<br />
| 25% <= C < 50% || ON || 1.5Hz Blink || OFF || OFF <br />
|-<br />
| C < 25% || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br />
==How To Assemble==<br />
* How to Assemble<br />
[[File:UPS V2 4-2.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==How To Use==<br />
===General Settings===<br />
* Download the latest Raspbian OS image from: [ https://www.raspberrypi.org/software/operating-systems/ ]<br />
* Unzip it and flash it to MicroSD card(TF card) with Etcher imaging tool. [ https://www.balena.io/etcher/ ]<br />
* Follow the installation method to assemble the Raspberry Pi and UPS Plus.<br />
* After booting up and make sure Raspberry Pi can access internet.<br />
* Enable <font color=red>I2C function</font> by using "raspi-config" tool, Navigate to "interface options" and select "I2C" and enable it follow the instructions.<br />
<pre> NOTE: It is very important to enable I2C function on Raspberry Pi, If miss this step, Raspberry Pi will not detect UPSPLUS module.</pre><br />
<pre> sudo raspi-config</pre> <br />
* Install smbus2 library.<br />
<pre>pip install smbus2</pre><br />
* Download repository from GitHub and entering the folder that contains demo code.<br />
<pre><br />
cd ~ <br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd upsplus/<br />
</pre><br />
<br />
===Automatic Shutdown Protection===<br />
* If you want to use one script to install upsplus's demo code, just follow the steps below.<br />
* Open a terminal by press "Ctrl+ALT+T" or just click terminal icon on the task bar.<br />
<pre>curl -Lso- https://git.io/JLygb | bash </pre><br />
or<br />
<pre>curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash</pre><br />
* When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Update UPS Firmware via OTA ===<br />
* Enter the OTA firmware upgrade mode:<br />
===Method 1===<br />
<font color=red>NOTE: Do not power off or disconnect the network during the upgrade process. If the upgrade fails, the UPS Pro will not work normally.</font><br />
* Power off the Raspberry Pi.<br />
* Cut off the external charging power (MicroUSB and USB-C)<br />
* Take out all the batteries.<br />
* Press and hold the UPS Pro switch key and insert the battery into the battery compartment.<br />
At this time, the device will be forced to enter OTA mode.<br><br />
<pre>The function of the switch button will no longer be available at this time.</pre><br />
The Raspberry Pi will be running and please execute the following python script in the system terminal to complete the upgrade. <br />
* Download python scripts from github:<br />
<pre><br />
cd ~<br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd ~/upsplus<br />
python3 OTA_firmware_upgrade.py<br />
</pre><br />
<font color=red><b>The first time it runs, it may prompt that the device is not registered.If it is a legal device, just wait a few seconds and try again.</b></font><br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===Method 2===<br />
* Open a terminal and typing: <br />
<pre>i2cset -y 1 0x17 50 127 b</pre><br />
* Shutdown Raspberry Pi and remove all batteries and power supply.<br />
* Insert batteries back into the battery slot.<br />
* Execute OTA_firmware_upgrade.py python script in a terminal.<br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===How To Collect Data===<br />
* Data Collection<br />
Data collection will only collect information on abnormal voltage changes and battery charging and discharging status during equipment operation through UPS in order to provide better after-sales service, and will not collect your private information. <br><br />
Please rest assured that every UPS we sell will Have a unique serial number so that we can provide battery quality analysis and feedback.<br><br />
It submits your UPS Pro operating status information to the server provided by us through a python script.<br><br />
* Download Repository and execute:<br />
<pre><br />
cd ~<br />
curl -Lso- https://git.io/JLygb | bash<br />
</pre><br />
When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Setup RTC===<br />
====Using Overlays====<br />
* Overlays are loaded using the "dtoverlay" config.txt setting. <br />
As an example,consider I2C Real Time Clock drivers. In the pre-DT world these would be loaded<br />
by writing a magic string comprising a device identifier and an I2C address to<br />
a special file in /sys/class/i2c-adapter, having first loaded the driver for<br />
the I2C interface and the RTC device - something like this:<br />
PS: sudo su means use root user to operate the system file, otherwise you may encount an error: "Permission denied"<br><br />
<pre><br />
sudo modprobe i2c-bcm2835<br />
sudo modprobe rtc-ds1307<br />
sudo su <br />
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device<br />
</pre><br />
With DT enabled, this becomes a line in config.txt:<br><br />
Edit /boot/config.txt file via vim.tiny tool or nano in a terminal:<br />
<code> sudo vim.tiny /boot/config.txt</code></br> <br />
And then add this parameter:<br><br />
<pre><br />
dtoverlay=i2c-rtc,ds1307<br />
</pre><br />
This causes the file /boot/overlays/i2c-rtc.dtbo to be loaded and a "node"<br />
describing the DS1307 I2C device to be added to the Device Tree for the Pi. By<br />
default it uses address 0x68, but this can be modified with an additional DT<br />
parameter:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307,addr=0x68<br />
</pre><br />
Parameters usually have default values, although certain parameters are<br />
mandatory. See the list of overlays below for a description of the parameters<br />
and their defaults.<br />
<br />
===For Raspberry Pi 4B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:DS1307-4B(1).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
[[File:DS1307-4B(2).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
please ensure that /boot/config.txt file include two paramaters:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307 <br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:DS1307-4B(6).png|thumb|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
----<br />
===How to test RTC===<br />
* Open terminal and typing: <br />
<pre>sudo hwclock -w </pre><br />
<pre>sudo hwclock </pre><br />
* Result will be like:<br />
<pre><br />
pi@upstest:~ $ sudo hwclock -w<br />
pi@upstest:~ $ sudo hwclock<br />
2021-05-12 11:41:23.601270+08:00<br />
</pre><br />
<br />
===For Raspberry Pi 3B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:Ds13076.png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
<pre>Name: i2c-rtc<br />
Info: Adds support for a number of I2C Real Time Clock devices<br />
Load: dtoverlay=i2c-rtc,<param>=<val><br />
Params: ds1307 Select the DS1307 device</pre><br />
please ensure that /boot/config.txt file include those three paramaters:<br />
<pre><br />
device_tree=bcm2710-rpi-3-b.dtb<br />
dtoverlay=i2c-rtc,ds1307<br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:Raspberry pi hwclock-set.png|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
<br />
===How To Adjust The Sampling Period===<br />
* If you want to change the sampling interval, you can change it with the following demo code in python:<br />
<font color=red>NOTE: Change the number of `SAMPLE_TIME` will adjust the sampling period: range from 2 to 60, unit minute. If the quality of the charger is not good, you need to increase the period, for example: adjust to 3~5, if the quality of the battery is not good, you need to decrease the sampling period, for example: 1~2 </font><br><br />
* Demo code:<br />
<pre><br />
import smbus<br />
<br />
DEVICE_BUS = 1<br />
DEVICE_ADDR = 0x17<br />
SAMPLE_TIME = 2 <br />
<br />
bus = smbus.SMBus(DEVICE_BUS)<br />
<br />
aReceiveBuf = []<br />
aReceiveBuf.append(0x00) <br />
<br />
bus.write_byte_data(DEVICE_ADDR, 21,SAMPLE_TIME & 0xFF)<br />
bus.write_byte_data(DEVICE_ADDR, 22,(SAMPLE_TIME >> 8)& 0xFF)<br />
<br />
print("Setting Sampling Period to: %d Min" % SAMPLE_TIME)<br />
</pre><br />
* Save it to a file and execute it:<br />
<pre>python3 ups_change_sample_period.py</pre><br />
=== How to detect if the battery is dead ===<br />
* There are two python scripts in the location /home/pi/bin/ after executing command "curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash" , as following picture:<br />
[[File:Ups location.jpg|left|320px]]<br />
<br style="clear:both;"><br />
* Execute the `upsPlus.py` script <font color=red><strong>2-3</strong></font>times through the following commands to determine whether the battery is continuously discharging, and if the charge is less than the discharge, the battery will soon be lower than the set shutdown threshold and shut down.<br />
At this time, you need to replace the battery, or change the sampling period, or replace the high-quality fast charger plug<br />
<pre> python3 /home/pi/bin/upsPlus.py </pre><br />
* For example:<br />
[[File:Ups batteries status.jpg|left|320px]]<br />
<br style="clear:both;"><br />
The battery shown in the figure：<font color=red>Battery Current (discharge) Rate: 1553.902 mA</font>, But the last information was: <font color=red>Currently charging via Micro USB Port.</font> <br />
There is a charging port inserted, but the battery discharge is displayed, which means the battery is bad.<br />
<br />
===How to Setup back-to-ac function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 25 1</pre><br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
===How to Setup shutting down countdown function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 24 20</pre><br />
PS: 20 means countdown number is 20 seconds, you can change to another integer number. <br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
===How to self-diagnose UPS PLUS ===<br />
* Please visit this URL in browser: [ https://api.52pi.com/ ]<br />
[[File:Ups diagnosistool.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Filling the blank with your Deivce UIDs which can be getting from /home/pi/bin/upsPlus_iot.py script, open a terminal and typing:<br />
<pre> python3 /home/pi/bin/upsPlus_iot.py </pre><br />
[[File:Ups uids.jpg|left | 500px]]<br />
<br style="clear:both;"><br />
* Copy UID0, UID1, UID2 to browser and press "Diagnosis" button on the page:<br />
[[File:Ups dignosis.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Then you will get the test results and suggestions on the page.<br />
[[File:Dignosis result.png|left|500px]]<br />
<br style="clear:both;"><br />
<font color=red> Pink color means it is critical message and Blue color means suggestion.</font><br />
<br />
==Parameter freezing issue==<br />
According to our tracking test, about 0.8% of users after a period of time, read the UPS parameters found that the value no longer changes, the cause of this is complex, and the number of users is small, we are working to solve this problem, if you encounter this problem, please try to completely reinstall the battery, power supply and Raspberry Pi and observe again, usually the problem is solved, if there are still problems, please contact us.<br />
<br />
==Battery Logger==<br />
* Thanks for Nordln's help.<br />
* UPS Plus Battery Logger: [ https://github.com/Nordln/upsplusv5-battery-logger.git ]<br />
[[File:Ups logger.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Package Includes==<br />
* 1 x UPS Plus For Raspberry Pi<br />
* 4 x M2.5 copper pillar <br />
* 4 x M2.5 screws<br />
* 4 x M2.5 long copper stick<br />
* 4 x M2.5 nuts<br />
* 1 x Acrylic shield<br />
* 1 x Instructions<br />
[[File:UPS V2 9.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Tutorial Video==<br />
* Youtube link:<br />
[ https://youtu.be/jQljQJ41I5A ]<br />
* QRCODE:<br />
[[File:Upsplus tutorial1.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Why does the battery light go off sometime and lights up in a while? <br />
** A: This is because the power chip performs battery re-sampling, and the purpose is that the data of inferior batteries is inaccurate during the sampling process.<br />
* Q: Why is the power cut off every once in a while? <br />
** A: Please check the battery charging current, the data discharge direction or the charging direction. If the load is too large, the charging may not be enough, which will cause this problem.<br />
* Q: What kind of wall charger should I use? <br />
** A: If the load is normal, it is recommended to use an ordinary 5V@2A charging head. If you need to carry a slightly higher load, it is recommended to use a fast charging source. We support FCP, AFC, SFCP protocols Fast charging source.<br />
* Q: Can I directly input 9V and 12V to the USB port?<br />
** A: No, if you must do this, you must remove the DP, DM and other related detection pins, and ensure that the power supply is stable.<br />
* Q: I heard howling, why is this? <br />
** A: Because of the no-load protection mechanism, the howling will disappear after the load is installed.<br />
* Q: using firmware v. 4, when AC power comes back on during the shutdown countdown, I realized that the 5V supply for the raspberry pi is not switched off at the end of the countdown. so, after shutdown of the operating system, the raspberry pi will never restart automatically.<br />
IMHO the following would be better: once a shutdown countdown starts, and we have the Back-To-AC Auto Power UP flag set, then:<br />
the shutdown sequence should proceed to its end,<br />
switch off the 5V-power for a certain time (a couple of seconds maybe), regardless of AC Power.<br />
switch the 5V back on when AC power is restored.<br />
otherwise, I am very happy with the product.<br />
one more thing: would be nice to have some sort of alert for new firmware releases and release notes for these.<br />
** A: Please refer to this URL: https://github.com/geeekpi/upsplus/issues/7<br />
<br />
==Keywords==<br />
* UPS Plus, GeeekPi UPS V5, UPS for Raspberry Pi</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0136&diff=10383EP-01362021-06-01T09:08:58Z<p>TaterLi: /* Battery Logger */</p>
<hr />
<div>==UPS Plus==<br />
[[File:UPS V2 1.jpg|right|320px]]<br />
==Descriptions==<br />
UPS Plus is a new generation of UPS power management module which supports OTA firmware upgrade and supports RTC onboard. <br><br />
And there are two INA219 chip onboard to detect batteries voltage and the voltage output from UPS Plus to Raspberry Pi.<br><br />
<br />
==Compatibility==<br />
{| class="wikitable"<br />
|-<br />
! Raspberry Model !! Compatibility <br />
|-<br />
| Raspberry Pi A || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi A+ ||<font color=green>YES</font><br />
|-<br />
| Raspberry Pi B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi B+ ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 2B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B+ || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 4B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi Zero || <font color=red>NO</font><br />
|-<br />
|Raspberry Pi Zero W ||<font color=red>NO</font><br />
|}<br />
<br />
==Features==<br />
* Easy to install<br />
* Enhanced power management<br />
* Remote OTA firmware upgrade<br />
* Programmable BACK-TO-AC auto power up<br />
* Programmable sample period<br />
* I2C communication<br />
* Standalone RTC<br />
* Support stacked battery design<br />
===Specifications===<br />
* Current/voltage monitoring of Raspberry Pi power supply port.<br />
* Battery terminal current/voltage monitoring, supports two-way monitoring of charge and discharge.<br />
* Independent RTC function.<br />
* OTA function (supports forced upgrade mode and active upgrade mode).<br />
* Power estimation<br />
<pre>Note: At least one full charge and discharge cycle must be completed!)</pre><br />
* Adjustable sampling period.<br />
* Support FCP, AFC, SFCP fast charge protocol.<br />
* Support BC1.2 charging protocol.<br />
* Battery temperature monitoring <br />
<pre>Note: the forced temperature protection cannot be turned off, threshold: 65 degrees!</pre><br />
* Programmable Power Voltage Detector(PVD) function, Default value: 3.6V <br />
* Incoming call self-start function.<br />
* Power down memory function.<br />
* Programmable shutdown / forced restart.<br />
* Running time statistics <br />
* Electrostatic protection.<br />
* Linear compensation range discharge capacity: 5V 4.5A.<br />
* Non-linear compensation range discharge capacity: 5V 8A.<br />
* Charging capacity 4.5V 5A/5V 2.5A/9V 2A/12V 1.5A.<br />
* Stacked battery design<br />
<pre>NOTE: Stacked power board need to be special accessories.Can not support None official accessories.</pre><br />
* Use I2C communication without occupying additional ports.<br />
* Support 4.2V 4.35V 4.4V 4.5V lithium battery <br />
<pre>Note: Different types of batteries cannot be mixed!</pre><br />
* After-sales data telemetry.<br />
<br />
===Register Mapping===<br />
===USB Plus V5.0 Register Mapping Chart===<br />
* 0x17 - Operation Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function !! Range !! Unit<br />
|-<br />
| 0x01 - 0x02 || Voltage of UPS's MCU || 2400 - 3600 || mV <br />
|-<br />
| 0x03 - 0x04 || Voltage of Pogopin's Bottom || 0 - 5500 || mV <br />
|-<br />
| 0x05 - 0x06 || Voltage of Batteries' Terminal || 0 - 4500 || mV <br />
|-<br />
| 0x07 - 0x08 || Voltage of USB-C Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x09 - 0x0A || Voltage of MicroUSB Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x0B - 0x0C || Batteries Temperature || -20 - 65 || ℃ <br />
|-<br />
| 0x0D - 0x0E || Full Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x0F - 0x10 || Empty Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x11 - 0x12 || Protection Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x13 - 0x14 || Battery Remaining || 0 - 100 || % <br />
|-<br />
| 0x15 - 0x16 || Sample Period || 1 - 1440 || Min<br />
|-<br />
| 0x17 || Power Status/Operation Mode || 0/1 || Bool <br />
|-<br />
| 0x18 || Shutdown Countdown || 0(False)/10 - 255 || Bool/Sec <br />
|-<br />
| 0x19 || Back-To-AC Auto Power up || 0/1 || Bool<br />
|-<br />
| 0x1A || Restart Countdown || 0(False)/10- 255 || Bool/Sec<br />
|-<br />
| 0x1B || Reset to Factory Defaults || 0/1 || Bool <br />
|-<br />
| 0x1C - 0x1F || Cumulative Running Time || 0 - 2147483647 || Sec <br />
|-<br />
| 0x20 - 0x23 || Accumulated Charging Time || 0 - 2147483647|| Sec<br />
|-<br />
| 0x24 - 0x27 || Running Time || 0 - 2147483647 || Sec<br />
|-<br />
| 0x28 - 0x29 || Version || 1 || Fixed <br />
|-<br />
| 0x2A || (FW.V5+) Battery Parameters self-programmed by user|| 0/1 || Bool<br />
|-<br />
| 0x2B - 0xEF || [Reserved] || NA || NA<br />
|-<br />
| 0xF0 - 0xFB || Serial Number || Device UID || Fixed<br />
|-<br />
| 0xFC - 0xFF || Factory Testing || NA || NA<br />
|}<br />
* 0x18 - OTA Firmware Upgrade Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function <br />
|-<br />
| 0x01 - 0x10 || Encrypted buffer<br />
|-<br />
| 0x11 - 0xEF || [Reserved]<br />
|-<br />
| 0xF0 - 0xFB || Serial Number<br />
|-<br />
| 0xFC - 0xFF || Factory Test<br />
|}<br />
<br />
==Gallery==<br />
* Product Outlook<br />
{|<br />
|[[File:UPS V2 1.jpg|left|320px]]<br />
|[[File:UPS V2 2.jpg|left|320px]]<br />
|[[File:UPS V2 3.jpg|left|320px]]<br />
|}<br />
* Application scenario<br />
[[File:UPS V2 13.jpg|left|800px]]<br />
<br style="clear:both;"><br />
===PCB Drawing===<br />
* PCBDOC File: [[ File:UPS PLUS PCBDOC.zip ]]<br />
<br />
===Function Area Display===<br />
* Function Details <br />
{|<br />
|[[File:UPS V2 10.jpg|left|320px]]<br />
|[[File:UPS V2 11.jpg|none|320px]]<br />
|[[File:UPS V2 12.jpg|none|320px]]<br />
|}<br />
<br />
===LED light status definition===<br />
* Discharge Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| C >= 75% || ON || ON || ON || ON <br />
|-<br />
| 50% <= C <75% || ON || ON || ON || OFF <br />
|-<br />
| 25% <= C <50% || ON || ON || OFF || OFF <br />
|-<br />
| 0% <= C < 25% || ON || OFF || OFF || OFF <br />
|-<br />
| Wrong Batteries Parameters || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br style="clear:both;"><br />
<br />
* Charging Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| 100% || ON || ON || ON || ON <br />
|-<br />
| 75% <= C|| ON || ON || ON || 1.5Hz Blink<br />
|-<br />
| 50% <= C <75% || ON || ON || 1.5Hz Blink || OFF <br />
|-<br />
| 25% <= C < 50% || ON || 1.5Hz Blink || OFF || OFF <br />
|-<br />
| C < 25% || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br />
==How To Assemble==<br />
* How to Assemble<br />
[[File:UPS V2 4-2.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==How To Use==<br />
===General Settings===<br />
* Download the latest Raspbian OS image from: [ https://www.raspberrypi.org/software/operating-systems/ ]<br />
* Unzip it and flash it to MicroSD card(TF card) with Etcher imaging tool. [ https://www.balena.io/etcher/ ]<br />
* Follow the installation method to assemble the Raspberry Pi and UPS Plus.<br />
* After booting up and make sure Raspberry Pi can access internet.<br />
* Enable <font color=red>I2C function</font> by using "raspi-config" tool, Navigate to "interface options" and select "I2C" and enable it follow the instructions.<br />
<pre> NOTE: It is very important to enable I2C function on Raspberry Pi, If miss this step, Raspberry Pi will not detect UPSPLUS module.</pre><br />
<pre> sudo raspi-config</pre> <br />
* Install smbus2 library.<br />
<pre>pip install smbus2</pre><br />
* Download repository from GitHub and entering the folder that contains demo code.<br />
<pre><br />
cd ~ <br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd upsplus/<br />
</pre><br />
<br />
===Automatic Shutdown Protection===<br />
* If you want to use one script to install upsplus's demo code, just follow the steps below.<br />
* Open a terminal by press "Ctrl+ALT+T" or just click terminal icon on the task bar.<br />
<pre>curl -Lso- https://git.io/JLygb | bash </pre><br />
or<br />
<pre>curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash</pre><br />
* When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Update UPS Firmware via OTA ===<br />
* Enter the OTA firmware upgrade mode:<br />
===Method 1===<br />
<font color=red>NOTE: Do not power off or disconnect the network during the upgrade process. If the upgrade fails, the UPS Pro will not work normally.</font><br />
* Power off the Raspberry Pi.<br />
* Cut off the external charging power (MicroUSB and USB-C)<br />
* Take out all the batteries.<br />
* Press and hold the UPS Pro switch key and insert the battery into the battery compartment.<br />
At this time, the device will be forced to enter OTA mode.<br><br />
<pre>The function of the switch button will no longer be available at this time.</pre><br />
The Raspberry Pi will be running and please execute the following python script in the system terminal to complete the upgrade. <br />
* Download python scripts from github:<br />
<pre><br />
cd ~<br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd ~/upsplus<br />
python3 OTA_firmware_upgrade.py<br />
</pre><br />
<font color=red><b>The first time it runs, it may prompt that the device is not registered.If it is a legal device, just wait a few seconds and try again.</b></font><br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===Method 2===<br />
* Open a terminal and typing: <br />
<pre>i2cset -y 1 0x17 50 127 b</pre><br />
* Shutdown Raspberry Pi and remove all batteries and power supply.<br />
* Insert batteries back into the battery slot.<br />
* Execute OTA_firmware_upgrade.py python script in a terminal.<br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===How To Collect Data===<br />
* Data Collection<br />
Data collection will only collect information on abnormal voltage changes and battery charging and discharging status during equipment operation through UPS in order to provide better after-sales service, and will not collect your private information. <br><br />
Please rest assured that every UPS we sell will Have a unique serial number so that we can provide battery quality analysis and feedback.<br><br />
It submits your UPS Pro operating status information to the server provided by us through a python script.<br><br />
* Download Repository and execute:<br />
<pre><br />
cd ~<br />
curl -Lso- https://git.io/JLygb | bash<br />
</pre><br />
When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Setup RTC===<br />
====Using Overlays====<br />
* Overlays are loaded using the "dtoverlay" config.txt setting. <br />
As an example,consider I2C Real Time Clock drivers. In the pre-DT world these would be loaded<br />
by writing a magic string comprising a device identifier and an I2C address to<br />
a special file in /sys/class/i2c-adapter, having first loaded the driver for<br />
the I2C interface and the RTC device - something like this:<br />
PS: sudo su means use root user to operate the system file, otherwise you may encount an error: "Permission denied"<br><br />
<pre><br />
sudo modprobe i2c-bcm2835<br />
sudo modprobe rtc-ds1307<br />
sudo su <br />
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device<br />
</pre><br />
With DT enabled, this becomes a line in config.txt:<br><br />
Edit /boot/config.txt file via vim.tiny tool or nano in a terminal:<br />
<code> sudo vim.tiny /boot/config.txt</code></br> <br />
And then add this parameter:<br><br />
<pre><br />
dtoverlay=i2c-rtc,ds1307<br />
</pre><br />
This causes the file /boot/overlays/i2c-rtc.dtbo to be loaded and a "node"<br />
describing the DS1307 I2C device to be added to the Device Tree for the Pi. By<br />
default it uses address 0x68, but this can be modified with an additional DT<br />
parameter:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307,addr=0x68<br />
</pre><br />
Parameters usually have default values, although certain parameters are<br />
mandatory. See the list of overlays below for a description of the parameters<br />
and their defaults.<br />
<br />
===For Raspberry Pi 4B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:DS1307-4B(1).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
[[File:DS1307-4B(2).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
please ensure that /boot/config.txt file include two paramaters:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307 <br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:DS1307-4B(6).png|thumb|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
----<br />
===How to test RTC===<br />
* Open terminal and typing: <br />
<pre>sudo hwclock -w </pre><br />
<pre>sudo hwclock </pre><br />
* Result will be like:<br />
<pre><br />
pi@upstest:~ $ sudo hwclock -w<br />
pi@upstest:~ $ sudo hwclock<br />
2021-05-12 11:41:23.601270+08:00<br />
</pre><br />
<br />
===For Raspberry Pi 3B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:Ds13076.png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
<pre>Name: i2c-rtc<br />
Info: Adds support for a number of I2C Real Time Clock devices<br />
Load: dtoverlay=i2c-rtc,<param>=<val><br />
Params: ds1307 Select the DS1307 device</pre><br />
please ensure that /boot/config.txt file include those three paramaters:<br />
<pre><br />
device_tree=bcm2710-rpi-3-b.dtb<br />
dtoverlay=i2c-rtc,ds1307<br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:Raspberry pi hwclock-set.png|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
<br />
===How To Adjust The Sampling Period===<br />
* If you want to change the sampling interval, you can change it with the following demo code in python:<br />
<font color=red>NOTE: Change the number of `SAMPLE_TIME` will adjust the sampling period: range from 2 to 60, unit minute. If the quality of the charger is not good, you need to increase the period, for example: adjust to 3~5, if the quality of the battery is not good, you need to decrease the sampling period, for example: 1~2 </font><br><br />
* Demo code:<br />
<pre><br />
import smbus<br />
<br />
DEVICE_BUS = 1<br />
DEVICE_ADDR = 0x17<br />
SAMPLE_TIME = 2 <br />
<br />
bus = smbus.SMBus(DEVICE_BUS)<br />
<br />
aReceiveBuf = []<br />
aReceiveBuf.append(0x00) <br />
<br />
bus.write_byte_data(DEVICE_ADDR, 21,SAMPLE_TIME & 0xFF)<br />
bus.write_byte_data(DEVICE_ADDR, 22,(SAMPLE_TIME >> 8)& 0xFF)<br />
<br />
print("Setting Sampling Period to: %d Min" % SAMPLE_TIME)<br />
</pre><br />
* Save it to a file and execute it:<br />
<pre>python3 ups_change_sample_period.py</pre><br />
=== How to detect if the battery is dead ===<br />
* There are two python scripts in the location /home/pi/bin/ after executing command "curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash" , as following picture:<br />
[[File:Ups location.jpg|left|320px]]<br />
<br style="clear:both;"><br />
* Execute the `upsPlus.py` script <font color=red><strong>2-3</strong></font>times through the following commands to determine whether the battery is continuously discharging, and if the charge is less than the discharge, the battery will soon be lower than the set shutdown threshold and shut down.<br />
At this time, you need to replace the battery, or change the sampling period, or replace the high-quality fast charger plug<br />
<pre> python3 /home/pi/bin/upsPlus.py </pre><br />
* For example:<br />
[[File:Ups batteries status.jpg|left|320px]]<br />
<br style="clear:both;"><br />
The battery shown in the figure：<font color=red>Battery Current (discharge) Rate: 1553.902 mA</font>, But the last information was: <font color=red>Currently charging via Micro USB Port.</font> <br />
There is a charging port inserted, but the battery discharge is displayed, which means the battery is bad.<br />
<br />
===How to Setup back-to-ac function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 25 1</pre><br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
===How to Setup shutting down countdown function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 24 20</pre><br />
PS: 20 means countdown number is 20 seconds, you can change to another integer number. <br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
===How to self-diagnose UPS PLUS ===<br />
* Please visit this URL in browser: [ https://api.thekoziolfoundation.com/ ]<br />
[[File:Ups diagnosistool.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Filling the blank with your Deivce UIDs which can be getting from /home/pi/bin/upsPlus_iot.py script, open a terminal and typing:<br />
<pre> python3 /home/pi/bin/upsPlus_iot.py </pre><br />
[[File:Ups uids.jpg|left | 500px]]<br />
<br style="clear:both;"><br />
* Copy UID0, UID1, UID2 to browser and press "Diagnosis" button on the page:<br />
[[File:Ups dignosis.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Then you will get the test results and suggestions on the page.<br />
[[File:Dignosis result.png|left|500px]]<br />
<br style="clear:both;"><br />
<font color=red> Pink color means it is critical message and Blue color means suggestion.</font><br />
<br />
==Parameter freezing issue==<br />
According to our tracking test, about 0.8% of users after a period of time, read the UPS parameters found that the value no longer changes, the cause of this is complex, and the number of users is small, we are working to solve this problem, if you encounter this problem, please try to completely reinstall the battery, power supply and Raspberry Pi and observe again, usually the problem is solved, if there are still problems, please contact us.<br />
<br />
==Battery Logger==<br />
* Thanks for Nordln's help.<br />
* UPS Plus Battery Logger: [ https://github.com/Nordln/upsplusv5-battery-logger.git ]<br />
[[File:Ups logger.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Package Includes==<br />
* 1 x UPS Plus For Raspberry Pi<br />
* 4 x M2.5 copper pillar <br />
* 4 x M2.5 screws<br />
* 4 x M2.5 long copper stick<br />
* 4 x M2.5 nuts<br />
* 1 x Acrylic shield<br />
* 1 x Instructions<br />
[[File:UPS V2 9.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Tutorial Video==<br />
* Youtube link:<br />
[ https://youtu.be/jQljQJ41I5A ]<br />
* QRCODE:<br />
[[File:Upsplus tutorial1.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Why does the battery light go off sometime and lights up in a while? <br />
** A: This is because the power chip performs battery re-sampling, and the purpose is that the data of inferior batteries is inaccurate during the sampling process.<br />
* Q: Why is the power cut off every once in a while? <br />
** A: Please check the battery charging current, the data discharge direction or the charging direction. If the load is too large, the charging may not be enough, which will cause this problem.<br />
* Q: What kind of wall charger should I use? <br />
** A: If the load is normal, it is recommended to use an ordinary 5V@2A charging head. If you need to carry a slightly higher load, it is recommended to use a fast charging source. We support FCP, AFC, SFCP protocols Fast charging source.<br />
* Q: Can I directly input 9V and 12V to the USB port?<br />
** A: No, if you must do this, you must remove the DP, DM and other related detection pins, and ensure that the power supply is stable.<br />
* Q: I heard howling, why is this? <br />
** A: Because of the no-load protection mechanism, the howling will disappear after the load is installed.<br />
* Q: using firmware v. 4, when AC power comes back on during the shutdown countdown, I realized that the 5V supply for the raspberry pi is not switched off at the end of the countdown. so, after shutdown of the operating system, the raspberry pi will never restart automatically.<br />
IMHO the following would be better: once a shutdown countdown starts, and we have the Back-To-AC Auto Power UP flag set, then:<br />
the shutdown sequence should proceed to its end,<br />
switch off the 5V-power for a certain time (a couple of seconds maybe), regardless of AC Power.<br />
switch the 5V back on when AC power is restored.<br />
otherwise, I am very happy with the product.<br />
one more thing: would be nice to have some sort of alert for new firmware releases and release notes for these.<br />
** A: Please refer to this URL: https://github.com/geeekpi/upsplus/issues/7<br />
<br />
==Keywords==<br />
* UPS Plus, GeeekPi UPS V5, UPS for Raspberry Pi</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0136&diff=10382EP-01362021-06-01T09:04:41Z<p>TaterLi: /* USB Plus V5.0 Register Mapping Chart */</p>
<hr />
<div>==UPS Plus==<br />
[[File:UPS V2 1.jpg|right|320px]]<br />
==Descriptions==<br />
UPS Plus is a new generation of UPS power management module which supports OTA firmware upgrade and supports RTC onboard. <br><br />
And there are two INA219 chip onboard to detect batteries voltage and the voltage output from UPS Plus to Raspberry Pi.<br><br />
<br />
==Compatibility==<br />
{| class="wikitable"<br />
|-<br />
! Raspberry Model !! Compatibility <br />
|-<br />
| Raspberry Pi A || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi A+ ||<font color=green>YES</font><br />
|-<br />
| Raspberry Pi B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi B+ ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 2B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B+ || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 4B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi Zero || <font color=red>NO</font><br />
|-<br />
|Raspberry Pi Zero W ||<font color=red>NO</font><br />
|}<br />
<br />
==Features==<br />
* Easy to install<br />
* Enhanced power management<br />
* Remote OTA firmware upgrade<br />
* Programmable BACK-TO-AC auto power up<br />
* Programmable sample period<br />
* I2C communication<br />
* Standalone RTC<br />
* Support stacked battery design<br />
===Specifications===<br />
* Current/voltage monitoring of Raspberry Pi power supply port.<br />
* Battery terminal current/voltage monitoring, supports two-way monitoring of charge and discharge.<br />
* Independent RTC function.<br />
* OTA function (supports forced upgrade mode and active upgrade mode).<br />
* Power estimation<br />
<pre>Note: At least one full charge and discharge cycle must be completed!)</pre><br />
* Adjustable sampling period.<br />
* Support FCP, AFC, SFCP fast charge protocol.<br />
* Support BC1.2 charging protocol.<br />
* Battery temperature monitoring <br />
<pre>Note: the forced temperature protection cannot be turned off, threshold: 65 degrees!</pre><br />
* Programmable Power Voltage Detector(PVD) function, Default value: 3.6V <br />
* Incoming call self-start function.<br />
* Power down memory function.<br />
* Programmable shutdown / forced restart.<br />
* Running time statistics <br />
* Electrostatic protection.<br />
* Linear compensation range discharge capacity: 5V 4.5A.<br />
* Non-linear compensation range discharge capacity: 5V 8A.<br />
* Charging capacity 4.5V 5A/5V 2.5A/9V 2A/12V 1.5A.<br />
* Stacked battery design<br />
<pre>NOTE: Stacked power board need to be special accessories.Can not support None official accessories.</pre><br />
* Use I2C communication without occupying additional ports.<br />
* Support 4.2V 4.35V 4.4V 4.5V lithium battery <br />
<pre>Note: Different types of batteries cannot be mixed!</pre><br />
* After-sales data telemetry.<br />
<br />
===Register Mapping===<br />
===USB Plus V5.0 Register Mapping Chart===<br />
* 0x17 - Operation Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function !! Range !! Unit<br />
|-<br />
| 0x01 - 0x02 || Voltage of UPS's MCU || 2400 - 3600 || mV <br />
|-<br />
| 0x03 - 0x04 || Voltage of Pogopin's Bottom || 0 - 5500 || mV <br />
|-<br />
| 0x05 - 0x06 || Voltage of Batteries' Terminal || 0 - 4500 || mV <br />
|-<br />
| 0x07 - 0x08 || Voltage of USB-C Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x09 - 0x0A || Voltage of MicroUSB Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x0B - 0x0C || Batteries Temperature || -20 - 65 || ℃ <br />
|-<br />
| 0x0D - 0x0E || Full Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x0F - 0x10 || Empty Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x11 - 0x12 || Protection Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x13 - 0x14 || Battery Remaining || 0 - 100 || % <br />
|-<br />
| 0x15 - 0x16 || Sample Period || 1 - 1440 || Min<br />
|-<br />
| 0x17 || Power Status/Operation Mode || 0/1 || Bool <br />
|-<br />
| 0x18 || Shutdown Countdown || 0(False)/10 - 255 || Bool/Sec <br />
|-<br />
| 0x19 || Back-To-AC Auto Power up || 0/1 || Bool<br />
|-<br />
| 0x1A || Restart Countdown || 0(False)/10- 255 || Bool/Sec<br />
|-<br />
| 0x1B || Reset to Factory Defaults || 0/1 || Bool <br />
|-<br />
| 0x1C - 0x1F || Cumulative Running Time || 0 - 2147483647 || Sec <br />
|-<br />
| 0x20 - 0x23 || Accumulated Charging Time || 0 - 2147483647|| Sec<br />
|-<br />
| 0x24 - 0x27 || Running Time || 0 - 2147483647 || Sec<br />
|-<br />
| 0x28 - 0x29 || Version || 1 || Fixed <br />
|-<br />
| 0x2A || (FW.V5+) Battery Parameters self-programmed by user|| 0/1 || Bool<br />
|-<br />
| 0x2B - 0xEF || [Reserved] || NA || NA<br />
|-<br />
| 0xF0 - 0xFB || Serial Number || Device UID || Fixed<br />
|-<br />
| 0xFC - 0xFF || Factory Testing || NA || NA<br />
|}<br />
* 0x18 - OTA Firmware Upgrade Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function <br />
|-<br />
| 0x01 - 0x10 || Encrypted buffer<br />
|-<br />
| 0x11 - 0xEF || [Reserved]<br />
|-<br />
| 0xF0 - 0xFB || Serial Number<br />
|-<br />
| 0xFC - 0xFF || Factory Test<br />
|}<br />
<br />
==Gallery==<br />
* Product Outlook<br />
{|<br />
|[[File:UPS V2 1.jpg|left|320px]]<br />
|[[File:UPS V2 2.jpg|left|320px]]<br />
|[[File:UPS V2 3.jpg|left|320px]]<br />
|}<br />
* Application scenario<br />
[[File:UPS V2 13.jpg|left|800px]]<br />
<br style="clear:both;"><br />
===PCB Drawing===<br />
* PCBDOC File: [[ File:UPS PLUS PCBDOC.zip ]]<br />
<br />
===Function Area Display===<br />
* Function Details <br />
{|<br />
|[[File:UPS V2 10.jpg|left|320px]]<br />
|[[File:UPS V2 11.jpg|none|320px]]<br />
|[[File:UPS V2 12.jpg|none|320px]]<br />
|}<br />
<br />
===LED light status definition===<br />
* Discharge Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| C >= 75% || ON || ON || ON || ON <br />
|-<br />
| 50% <= C <75% || ON || ON || ON || OFF <br />
|-<br />
| 25% <= C <50% || ON || ON || OFF || OFF <br />
|-<br />
| 0% <= C < 25% || ON || OFF || OFF || OFF <br />
|-<br />
| Wrong Batteries Parameters || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br style="clear:both;"><br />
<br />
* Charging Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| 100% || ON || ON || ON || ON <br />
|-<br />
| 75% <= C|| ON || ON || ON || 1.5Hz Blink<br />
|-<br />
| 50% <= C <75% || ON || ON || 1.5Hz Blink || OFF <br />
|-<br />
| 25% <= C < 50% || ON || 1.5Hz Blink || OFF || OFF <br />
|-<br />
| C < 25% || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br />
==How To Assemble==<br />
* How to Assemble<br />
[[File:UPS V2 4-2.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==How To Use==<br />
===General Settings===<br />
* Download the latest Raspbian OS image from: [ https://www.raspberrypi.org/software/operating-systems/ ]<br />
* Unzip it and flash it to MicroSD card(TF card) with Etcher imaging tool. [ https://www.balena.io/etcher/ ]<br />
* Follow the installation method to assemble the Raspberry Pi and UPS Plus.<br />
* After booting up and make sure Raspberry Pi can access internet.<br />
* Enable <font color=red>I2C function</font> by using "raspi-config" tool, Navigate to "interface options" and select "I2C" and enable it follow the instructions.<br />
<pre> NOTE: It is very important to enable I2C function on Raspberry Pi, If miss this step, Raspberry Pi will not detect UPSPLUS module.</pre><br />
<pre> sudo raspi-config</pre> <br />
* Install smbus2 library.<br />
<pre>pip install smbus2</pre><br />
* Download repository from GitHub and entering the folder that contains demo code.<br />
<pre><br />
cd ~ <br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd upsplus/<br />
</pre><br />
<br />
===Automatic Shutdown Protection===<br />
* If you want to use one script to install upsplus's demo code, just follow the steps below.<br />
* Open a terminal by press "Ctrl+ALT+T" or just click terminal icon on the task bar.<br />
<pre>curl -Lso- https://git.io/JLygb | bash </pre><br />
or<br />
<pre>curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash</pre><br />
* When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Update UPS Firmware via OTA ===<br />
* Enter the OTA firmware upgrade mode:<br />
===Method 1===<br />
<font color=red>NOTE: Do not power off or disconnect the network during the upgrade process. If the upgrade fails, the UPS Pro will not work normally.</font><br />
* Power off the Raspberry Pi.<br />
* Cut off the external charging power (MicroUSB and USB-C)<br />
* Take out all the batteries.<br />
* Press and hold the UPS Pro switch key and insert the battery into the battery compartment.<br />
At this time, the device will be forced to enter OTA mode.<br><br />
<pre>The function of the switch button will no longer be available at this time.</pre><br />
The Raspberry Pi will be running and please execute the following python script in the system terminal to complete the upgrade. <br />
* Download python scripts from github:<br />
<pre><br />
cd ~<br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd ~/upsplus<br />
python3 OTA_firmware_upgrade.py<br />
</pre><br />
<font color=red><b>The first time it runs, it may prompt that the device is not registered.If it is a legal device, just wait a few seconds and try again.</b></font><br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===Method 2===<br />
* Open a terminal and typing: <br />
<pre>i2cset -y 1 0x17 50 127 b</pre><br />
* Shutdown Raspberry Pi and remove all batteries and power supply.<br />
* Insert batteries back into the battery slot.<br />
* Execute OTA_firmware_upgrade.py python script in a terminal.<br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===How To Collect Data===<br />
* Data Collection<br />
Data collection will only collect information on abnormal voltage changes and battery charging and discharging status during equipment operation through UPS in order to provide better after-sales service, and will not collect your private information. <br><br />
Please rest assured that every UPS we sell will Have a unique serial number so that we can provide battery quality analysis and feedback.<br><br />
It submits your UPS Pro operating status information to the server provided by us through a python script.<br><br />
* Download Repository and execute:<br />
<pre><br />
cd ~<br />
curl -Lso- https://git.io/JLygb | bash<br />
</pre><br />
When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Setup RTC===<br />
====Using Overlays====<br />
* Overlays are loaded using the "dtoverlay" config.txt setting. <br />
As an example,consider I2C Real Time Clock drivers. In the pre-DT world these would be loaded<br />
by writing a magic string comprising a device identifier and an I2C address to<br />
a special file in /sys/class/i2c-adapter, having first loaded the driver for<br />
the I2C interface and the RTC device - something like this:<br />
PS: sudo su means use root user to operate the system file, otherwise you may encount an error: "Permission denied"<br><br />
<pre><br />
sudo modprobe i2c-bcm2835<br />
sudo modprobe rtc-ds1307<br />
sudo su <br />
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device<br />
</pre><br />
With DT enabled, this becomes a line in config.txt:<br><br />
Edit /boot/config.txt file via vim.tiny tool or nano in a terminal:<br />
<code> sudo vim.tiny /boot/config.txt</code></br> <br />
And then add this parameter:<br><br />
<pre><br />
dtoverlay=i2c-rtc,ds1307<br />
</pre><br />
This causes the file /boot/overlays/i2c-rtc.dtbo to be loaded and a "node"<br />
describing the DS1307 I2C device to be added to the Device Tree for the Pi. By<br />
default it uses address 0x68, but this can be modified with an additional DT<br />
parameter:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307,addr=0x68<br />
</pre><br />
Parameters usually have default values, although certain parameters are<br />
mandatory. See the list of overlays below for a description of the parameters<br />
and their defaults.<br />
<br />
===For Raspberry Pi 4B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:DS1307-4B(1).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
[[File:DS1307-4B(2).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
please ensure that /boot/config.txt file include two paramaters:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307 <br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:DS1307-4B(6).png|thumb|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
----<br />
===How to test RTC===<br />
* Open terminal and typing: <br />
<pre>sudo hwclock -w </pre><br />
<pre>sudo hwclock </pre><br />
* Result will be like:<br />
<pre><br />
pi@upstest:~ $ sudo hwclock -w<br />
pi@upstest:~ $ sudo hwclock<br />
2021-05-12 11:41:23.601270+08:00<br />
</pre><br />
<br />
===For Raspberry Pi 3B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:Ds13076.png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
<pre>Name: i2c-rtc<br />
Info: Adds support for a number of I2C Real Time Clock devices<br />
Load: dtoverlay=i2c-rtc,<param>=<val><br />
Params: ds1307 Select the DS1307 device</pre><br />
please ensure that /boot/config.txt file include those three paramaters:<br />
<pre><br />
device_tree=bcm2710-rpi-3-b.dtb<br />
dtoverlay=i2c-rtc,ds1307<br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:Raspberry pi hwclock-set.png|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
<br />
===How To Adjust The Sampling Period===<br />
* If you want to change the sampling interval, you can change it with the following demo code in python:<br />
<font color=red>NOTE: Change the number of `SAMPLE_TIME` will adjust the sampling period: range from 2 to 60, unit minute. If the quality of the charger is not good, you need to increase the period, for example: adjust to 3~5, if the quality of the battery is not good, you need to decrease the sampling period, for example: 1~2 </font><br><br />
* Demo code:<br />
<pre><br />
import smbus<br />
<br />
DEVICE_BUS = 1<br />
DEVICE_ADDR = 0x17<br />
SAMPLE_TIME = 2 <br />
<br />
bus = smbus.SMBus(DEVICE_BUS)<br />
<br />
aReceiveBuf = []<br />
aReceiveBuf.append(0x00) <br />
<br />
bus.write_byte_data(DEVICE_ADDR, 21,SAMPLE_TIME & 0xFF)<br />
bus.write_byte_data(DEVICE_ADDR, 22,(SAMPLE_TIME >> 8)& 0xFF)<br />
<br />
print("Setting Sampling Period to: %d Min" % SAMPLE_TIME)<br />
</pre><br />
* Save it to a file and execute it:<br />
<pre>python3 ups_change_sample_period.py</pre><br />
=== How to detect if the battery is dead ===<br />
* There are two python scripts in the location /home/pi/bin/ after executing command "curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash" , as following picture:<br />
[[File:Ups location.jpg|left|320px]]<br />
<br style="clear:both;"><br />
* Execute the `upsPlus.py` script <font color=red><strong>2-3</strong></font>times through the following commands to determine whether the battery is continuously discharging, and if the charge is less than the discharge, the battery will soon be lower than the set shutdown threshold and shut down.<br />
At this time, you need to replace the battery, or change the sampling period, or replace the high-quality fast charger plug<br />
<pre> python3 /home/pi/bin/upsPlus.py </pre><br />
* For example:<br />
[[File:Ups batteries status.jpg|left|320px]]<br />
<br style="clear:both;"><br />
The battery shown in the figure：<font color=red>Battery Current (discharge) Rate: 1553.902 mA</font>, But the last information was: <font color=red>Currently charging via Micro USB Port.</font> <br />
There is a charging port inserted, but the battery discharge is displayed, which means the battery is bad.<br />
<br />
===How to Setup back-to-ac function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 25 1</pre><br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
===How to Setup shutting down countdown function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 24 20</pre><br />
PS: 20 means countdown number is 20 seconds, you can change to another integer number. <br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
===How to self-diagnose UPS PLUS ===<br />
* Please visit this URL in browser: [ https://api.thekoziolfoundation.com/ ]<br />
[[File:Ups diagnosistool.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Filling the blank with your Deivce UIDs which can be getting from /home/pi/bin/upsPlus_iot.py script, open a terminal and typing:<br />
<pre> python3 /home/pi/bin/upsPlus_iot.py </pre><br />
[[File:Ups uids.jpg|left | 500px]]<br />
<br style="clear:both;"><br />
* Copy UID0, UID1, UID2 to browser and press "Diagnosis" button on the page:<br />
[[File:Ups dignosis.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Then you will get the test results and suggestions on the page.<br />
[[File:Dignosis result.png|left|500px]]<br />
<br style="clear:both;"><br />
<font color=red> Pink color means it is critical message and Blue color means suggestion.</font><br />
<br />
==Battery Logger==<br />
* Thanks for Nordln's help.<br />
* UPS Plus Battery Logger: [ https://github.com/Nordln/upsplusv5-battery-logger.git ]<br />
[[File:Ups logger.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Package Includes==<br />
* 1 x UPS Plus For Raspberry Pi<br />
* 4 x M2.5 copper pillar <br />
* 4 x M2.5 screws<br />
* 4 x M2.5 long copper stick<br />
* 4 x M2.5 nuts<br />
* 1 x Acrylic shield<br />
* 1 x Instructions<br />
[[File:UPS V2 9.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Tutorial Video==<br />
* Youtube link:<br />
[ https://youtu.be/jQljQJ41I5A ]<br />
* QRCODE:<br />
[[File:Upsplus tutorial1.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Why does the battery light go off sometime and lights up in a while? <br />
** A: This is because the power chip performs battery re-sampling, and the purpose is that the data of inferior batteries is inaccurate during the sampling process.<br />
* Q: Why is the power cut off every once in a while? <br />
** A: Please check the battery charging current, the data discharge direction or the charging direction. If the load is too large, the charging may not be enough, which will cause this problem.<br />
* Q: What kind of wall charger should I use? <br />
** A: If the load is normal, it is recommended to use an ordinary 5V@2A charging head. If you need to carry a slightly higher load, it is recommended to use a fast charging source. We support FCP, AFC, SFCP protocols Fast charging source.<br />
* Q: Can I directly input 9V and 12V to the USB port?<br />
** A: No, if you must do this, you must remove the DP, DM and other related detection pins, and ensure that the power supply is stable.<br />
* Q: I heard howling, why is this? <br />
** A: Because of the no-load protection mechanism, the howling will disappear after the load is installed.<br />
* Q: using firmware v. 4, when AC power comes back on during the shutdown countdown, I realized that the 5V supply for the raspberry pi is not switched off at the end of the countdown. so, after shutdown of the operating system, the raspberry pi will never restart automatically.<br />
IMHO the following would be better: once a shutdown countdown starts, and we have the Back-To-AC Auto Power UP flag set, then:<br />
the shutdown sequence should proceed to its end,<br />
switch off the 5V-power for a certain time (a couple of seconds maybe), regardless of AC Power.<br />
switch the 5V back on when AC power is restored.<br />
otherwise, I am very happy with the product.<br />
one more thing: would be nice to have some sort of alert for new firmware releases and release notes for these.<br />
** A: Please refer to this URL: https://github.com/geeekpi/upsplus/issues/7<br />
<br />
==Keywords==<br />
* UPS Plus, GeeekPi UPS V5, UPS for Raspberry Pi</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0136&diff=10381EP-01362021-06-01T09:04:26Z<p>TaterLi: /* USB Plus V5.0 Register Mapping Chart */</p>
<hr />
<div>==UPS Plus==<br />
[[File:UPS V2 1.jpg|right|320px]]<br />
==Descriptions==<br />
UPS Plus is a new generation of UPS power management module which supports OTA firmware upgrade and supports RTC onboard. <br><br />
And there are two INA219 chip onboard to detect batteries voltage and the voltage output from UPS Plus to Raspberry Pi.<br><br />
<br />
==Compatibility==<br />
{| class="wikitable"<br />
|-<br />
! Raspberry Model !! Compatibility <br />
|-<br />
| Raspberry Pi A || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi A+ ||<font color=green>YES</font><br />
|-<br />
| Raspberry Pi B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi B+ ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 2B ||<font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 3B+ || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi 4B || <font color=green>YES</font><br />
|-<br />
|Raspberry Pi Zero || <font color=red>NO</font><br />
|-<br />
|Raspberry Pi Zero W ||<font color=red>NO</font><br />
|}<br />
<br />
==Features==<br />
* Easy to install<br />
* Enhanced power management<br />
* Remote OTA firmware upgrade<br />
* Programmable BACK-TO-AC auto power up<br />
* Programmable sample period<br />
* I2C communication<br />
* Standalone RTC<br />
* Support stacked battery design<br />
===Specifications===<br />
* Current/voltage monitoring of Raspberry Pi power supply port.<br />
* Battery terminal current/voltage monitoring, supports two-way monitoring of charge and discharge.<br />
* Independent RTC function.<br />
* OTA function (supports forced upgrade mode and active upgrade mode).<br />
* Power estimation<br />
<pre>Note: At least one full charge and discharge cycle must be completed!)</pre><br />
* Adjustable sampling period.<br />
* Support FCP, AFC, SFCP fast charge protocol.<br />
* Support BC1.2 charging protocol.<br />
* Battery temperature monitoring <br />
<pre>Note: the forced temperature protection cannot be turned off, threshold: 65 degrees!</pre><br />
* Programmable Power Voltage Detector(PVD) function, Default value: 3.6V <br />
* Incoming call self-start function.<br />
* Power down memory function.<br />
* Programmable shutdown / forced restart.<br />
* Running time statistics <br />
* Electrostatic protection.<br />
* Linear compensation range discharge capacity: 5V 4.5A.<br />
* Non-linear compensation range discharge capacity: 5V 8A.<br />
* Charging capacity 4.5V 5A/5V 2.5A/9V 2A/12V 1.5A.<br />
* Stacked battery design<br />
<pre>NOTE: Stacked power board need to be special accessories.Can not support None official accessories.</pre><br />
* Use I2C communication without occupying additional ports.<br />
* Support 4.2V 4.35V 4.4V 4.5V lithium battery <br />
<pre>Note: Different types of batteries cannot be mixed!</pre><br />
* After-sales data telemetry.<br />
<br />
===Register Mapping===<br />
===USB Plus V5.0 Register Mapping Chart===<br />
* 0x17 - Operation Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function !! Range !! Unit<br />
|-<br />
| 0x01 - 0x02 || Voltage of UPS's MCU || 2400 - 3600 || mV <br />
|-<br />
| 0x03 - 0x04 || Voltage of Pogopin's Bottom || 0 - 5500 || mV <br />
|-<br />
| 0x05 - 0x06 || Voltage of Batteries' Terminal || 0 - 4500 || mV <br />
|-<br />
| 0x07 - 0x08 || Voltage of USB-C Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x09 - 0x0A || Voltage of MicroUSB Charging Port || 0 - 13500 || mV <br />
|-<br />
| 0x0B - 0x0C || Batteries Temperature || -20 - 65 || ℃ <br />
|-<br />
| 0x0D - 0x0E || Full Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x0F - 0x10 || Empty Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x11 - 0x12 || Protection Voltage || 0 - 4500 || mV <br />
|-<br />
| 0x13 - 0x14 || Battery Remaining || 0 - 100 || % <br />
|-<br />
| 0x15 - 0x16 || Sample Period || 1 - 1440 || Min<br />
|-<br />
| 0x17 || Power Status/Operation Mode || 0/1 || Bool <br />
|-<br />
| 0x18 || Shutdown Countdown || 0(False)/10 - 255 || Bool/Sec <br />
|-<br />
| 0x19 || Back-To-AC Auto Power up || 0/1 || Bool<br />
|-<br />
| 0x1A || Restart Countdown || 0(False)/10- 255 || Bool/Sec<br />
|-<br />
| 0x1B || Reset to Factory Defaults || 0/1 || Bool <br />
|-<br />
| 0x1C - 0x1F || Cumulative Running Time || 0 - 2147483647 || Sec <br />
|-<br />
| 0x20 - 0x23 || Accumulated Charging Time || 0 - 2147483647|| Sec<br />
|-<br />
| 0x24 - 0x27 || Running Time || 0 - 2147483647 || Sec<br />
|-<br />
| 0x28 - 0x29 || Version || 1 || Fixed <br />
|-<br />
| 0x2A || FixedVbat || 0/1 || (FW.V5+) Battery Parameters self-programmed by user<br />
|-<br />
| 0x2B - 0xEF || [Reserved] || NA || NA<br />
|-<br />
| 0xF0 - 0xFB || Serial Number || Device UID || Fixed<br />
|-<br />
| 0xFC - 0xFF || Factory Testing || NA || NA<br />
|}<br />
* 0x18 - OTA Firmware Upgrade Mode<br />
{| class="wikitable"<br />
|-<br />
! Address !! Function <br />
|-<br />
| 0x01 - 0x10 || Encrypted buffer<br />
|-<br />
| 0x11 - 0xEF || [Reserved]<br />
|-<br />
| 0xF0 - 0xFB || Serial Number<br />
|-<br />
| 0xFC - 0xFF || Factory Test<br />
|}<br />
<br />
==Gallery==<br />
* Product Outlook<br />
{|<br />
|[[File:UPS V2 1.jpg|left|320px]]<br />
|[[File:UPS V2 2.jpg|left|320px]]<br />
|[[File:UPS V2 3.jpg|left|320px]]<br />
|}<br />
* Application scenario<br />
[[File:UPS V2 13.jpg|left|800px]]<br />
<br style="clear:both;"><br />
===PCB Drawing===<br />
* PCBDOC File: [[ File:UPS PLUS PCBDOC.zip ]]<br />
<br />
===Function Area Display===<br />
* Function Details <br />
{|<br />
|[[File:UPS V2 10.jpg|left|320px]]<br />
|[[File:UPS V2 11.jpg|none|320px]]<br />
|[[File:UPS V2 12.jpg|none|320px]]<br />
|}<br />
<br />
===LED light status definition===<br />
* Discharge Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| C >= 75% || ON || ON || ON || ON <br />
|-<br />
| 50% <= C <75% || ON || ON || ON || OFF <br />
|-<br />
| 25% <= C <50% || ON || ON || OFF || OFF <br />
|-<br />
| 0% <= C < 25% || ON || OFF || OFF || OFF <br />
|-<br />
| Wrong Batteries Parameters || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br style="clear:both;"><br />
<br />
* Charging Status <br />
{| class="wikitable"<br />
!Power C(%) !! LED1 !! LED2 !! LED3 !! LED4<br />
|-<br />
| 100% || ON || ON || ON || ON <br />
|-<br />
| 75% <= C|| ON || ON || ON || 1.5Hz Blink<br />
|-<br />
| 50% <= C <75% || ON || ON || 1.5Hz Blink || OFF <br />
|-<br />
| 25% <= C < 50% || ON || 1.5Hz Blink || OFF || OFF <br />
|-<br />
| C < 25% || 1.5Hz Blinking || OFF || OFF || OFF<br />
|}<br />
<br />
==How To Assemble==<br />
* How to Assemble<br />
[[File:UPS V2 4-2.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==How To Use==<br />
===General Settings===<br />
* Download the latest Raspbian OS image from: [ https://www.raspberrypi.org/software/operating-systems/ ]<br />
* Unzip it and flash it to MicroSD card(TF card) with Etcher imaging tool. [ https://www.balena.io/etcher/ ]<br />
* Follow the installation method to assemble the Raspberry Pi and UPS Plus.<br />
* After booting up and make sure Raspberry Pi can access internet.<br />
* Enable <font color=red>I2C function</font> by using "raspi-config" tool, Navigate to "interface options" and select "I2C" and enable it follow the instructions.<br />
<pre> NOTE: It is very important to enable I2C function on Raspberry Pi, If miss this step, Raspberry Pi will not detect UPSPLUS module.</pre><br />
<pre> sudo raspi-config</pre> <br />
* Install smbus2 library.<br />
<pre>pip install smbus2</pre><br />
* Download repository from GitHub and entering the folder that contains demo code.<br />
<pre><br />
cd ~ <br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd upsplus/<br />
</pre><br />
<br />
===Automatic Shutdown Protection===<br />
* If you want to use one script to install upsplus's demo code, just follow the steps below.<br />
* Open a terminal by press "Ctrl+ALT+T" or just click terminal icon on the task bar.<br />
<pre>curl -Lso- https://git.io/JLygb | bash </pre><br />
or<br />
<pre>curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash</pre><br />
* When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Update UPS Firmware via OTA ===<br />
* Enter the OTA firmware upgrade mode:<br />
===Method 1===<br />
<font color=red>NOTE: Do not power off or disconnect the network during the upgrade process. If the upgrade fails, the UPS Pro will not work normally.</font><br />
* Power off the Raspberry Pi.<br />
* Cut off the external charging power (MicroUSB and USB-C)<br />
* Take out all the batteries.<br />
* Press and hold the UPS Pro switch key and insert the battery into the battery compartment.<br />
At this time, the device will be forced to enter OTA mode.<br><br />
<pre>The function of the switch button will no longer be available at this time.</pre><br />
The Raspberry Pi will be running and please execute the following python script in the system terminal to complete the upgrade. <br />
* Download python scripts from github:<br />
<pre><br />
cd ~<br />
git clone https://github.com/geeekpi/upsplus.git<br />
cd ~/upsplus<br />
python3 OTA_firmware_upgrade.py<br />
</pre><br />
<font color=red><b>The first time it runs, it may prompt that the device is not registered.If it is a legal device, just wait a few seconds and try again.</b></font><br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===Method 2===<br />
* Open a terminal and typing: <br />
<pre>i2cset -y 1 0x17 50 127 b</pre><br />
* Shutdown Raspberry Pi and remove all batteries and power supply.<br />
* Insert batteries back into the battery slot.<br />
* Execute OTA_firmware_upgrade.py python script in a terminal.<br />
* UPS Pro Will be turned off after upgrading, Please unplug the power supply, remove the batteries from UPS Pro.<br />
* Insert the batteries back to UPS Pro and then connect power supply and turn it on by press power switch.<br />
<br />
===How To Collect Data===<br />
* Data Collection<br />
Data collection will only collect information on abnormal voltage changes and battery charging and discharging status during equipment operation through UPS in order to provide better after-sales service, and will not collect your private information. <br><br />
Please rest assured that every UPS we sell will Have a unique serial number so that we can provide battery quality analysis and feedback.<br><br />
It submits your UPS Pro operating status information to the server provided by us through a python script.<br><br />
* Download Repository and execute:<br />
<pre><br />
cd ~<br />
curl -Lso- https://git.io/JLygb | bash<br />
</pre><br />
When encountering low battery, it will automatically shut down and turn off the UPS and it will restart when AC power comes.<br />
<br />
===How To Setup RTC===<br />
====Using Overlays====<br />
* Overlays are loaded using the "dtoverlay" config.txt setting. <br />
As an example,consider I2C Real Time Clock drivers. In the pre-DT world these would be loaded<br />
by writing a magic string comprising a device identifier and an I2C address to<br />
a special file in /sys/class/i2c-adapter, having first loaded the driver for<br />
the I2C interface and the RTC device - something like this:<br />
PS: sudo su means use root user to operate the system file, otherwise you may encount an error: "Permission denied"<br><br />
<pre><br />
sudo modprobe i2c-bcm2835<br />
sudo modprobe rtc-ds1307<br />
sudo su <br />
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device<br />
</pre><br />
With DT enabled, this becomes a line in config.txt:<br><br />
Edit /boot/config.txt file via vim.tiny tool or nano in a terminal:<br />
<code> sudo vim.tiny /boot/config.txt</code></br> <br />
And then add this parameter:<br><br />
<pre><br />
dtoverlay=i2c-rtc,ds1307<br />
</pre><br />
This causes the file /boot/overlays/i2c-rtc.dtbo to be loaded and a "node"<br />
describing the DS1307 I2C device to be added to the Device Tree for the Pi. By<br />
default it uses address 0x68, but this can be modified with an additional DT<br />
parameter:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307,addr=0x68<br />
</pre><br />
Parameters usually have default values, although certain parameters are<br />
mandatory. See the list of overlays below for a description of the parameters<br />
and their defaults.<br />
<br />
===For Raspberry Pi 4B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:DS1307-4B(1).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
[[File:DS1307-4B(2).png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
please ensure that /boot/config.txt file include two paramaters:<br />
<pre><br />
dtoverlay=i2c-rtc,ds1307 <br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:DS1307-4B(6).png|thumb|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
----<br />
===How to test RTC===<br />
* Open terminal and typing: <br />
<pre>sudo hwclock -w </pre><br />
<pre>sudo hwclock </pre><br />
* Result will be like:<br />
<pre><br />
pi@upstest:~ $ sudo hwclock -w<br />
pi@upstest:~ $ sudo hwclock<br />
2021-05-12 11:41:23.601270+08:00<br />
</pre><br />
<br />
===For Raspberry Pi 3B ===<br />
Here we assume that you have already burned the Raspbian Image into TF card and connect to your PC and logged in.<br />
Open a terminal and modify /boot/config.txt file using what you favorate editor such as vim.tiny or nano, add parameters as following picture:<br />
[[File:Ds13076.png|thumb|left|500px]]<br />
<br style="clear:both;" ><br />
'''You can read /boot/overlay/README and find this info to add support for ds1307 I2C Real Time Clock device.'''<br />
<pre>Name: i2c-rtc<br />
Info: Adds support for a number of I2C Real Time Clock devices<br />
Load: dtoverlay=i2c-rtc,<param>=<val><br />
Params: ds1307 Select the DS1307 device</pre><br />
please ensure that /boot/config.txt file include those three paramaters:<br />
<pre><br />
device_tree=bcm2710-rpi-3-b.dtb<br />
dtoverlay=i2c-rtc,ds1307<br />
dtparam=i2c_arm=on<br />
</pre><br />
After that, please make sure you have disabled the "fake hwclock" which interferes with the 'real' hwclock<br><br />
<pre><br />
sudo apt-get -y remove fake-hwclock<br />
sudo update-rc.d -f fake-hwclock remove<br />
</pre><br />
Now with the fake-hw clock off, you can start the original 'hardware clock' script.<br><br />
Edit the script file /lib/udev/hwclock-set with nano or vim editor and comment out these three lines:<br><br />
<pre><br />
if [ -e /run/systemd/system ] ; then<br />
exit 0<br />
fi<br />
</pre><br />
Finally result like this: <br><br />
[[File:Raspberry pi hwclock-set.png|left|500px]]<br />
<br style="clear:both;"><br />
save and reboot your RPi.<br />
<br />
===How To Adjust The Sampling Period===<br />
* If you want to change the sampling interval, you can change it with the following demo code in python:<br />
<font color=red>NOTE: Change the number of `SAMPLE_TIME` will adjust the sampling period: range from 2 to 60, unit minute. If the quality of the charger is not good, you need to increase the period, for example: adjust to 3~5, if the quality of the battery is not good, you need to decrease the sampling period, for example: 1~2 </font><br><br />
* Demo code:<br />
<pre><br />
import smbus<br />
<br />
DEVICE_BUS = 1<br />
DEVICE_ADDR = 0x17<br />
SAMPLE_TIME = 2 <br />
<br />
bus = smbus.SMBus(DEVICE_BUS)<br />
<br />
aReceiveBuf = []<br />
aReceiveBuf.append(0x00) <br />
<br />
bus.write_byte_data(DEVICE_ADDR, 21,SAMPLE_TIME & 0xFF)<br />
bus.write_byte_data(DEVICE_ADDR, 22,(SAMPLE_TIME >> 8)& 0xFF)<br />
<br />
print("Setting Sampling Period to: %d Min" % SAMPLE_TIME)<br />
</pre><br />
* Save it to a file and execute it:<br />
<pre>python3 ups_change_sample_period.py</pre><br />
=== How to detect if the battery is dead ===<br />
* There are two python scripts in the location /home/pi/bin/ after executing command "curl -Lso- https://raw.githubusercontent.com/geeekpi/upsplus/main/install.sh | bash" , as following picture:<br />
[[File:Ups location.jpg|left|320px]]<br />
<br style="clear:both;"><br />
* Execute the `upsPlus.py` script <font color=red><strong>2-3</strong></font>times through the following commands to determine whether the battery is continuously discharging, and if the charge is less than the discharge, the battery will soon be lower than the set shutdown threshold and shut down.<br />
At this time, you need to replace the battery, or change the sampling period, or replace the high-quality fast charger plug<br />
<pre> python3 /home/pi/bin/upsPlus.py </pre><br />
* For example:<br />
[[File:Ups batteries status.jpg|left|320px]]<br />
<br style="clear:both;"><br />
The battery shown in the figure：<font color=red>Battery Current (discharge) Rate: 1553.902 mA</font>, But the last information was: <font color=red>Currently charging via Micro USB Port.</font> <br />
There is a charging port inserted, but the battery discharge is displayed, which means the battery is bad.<br />
<br />
===How to Setup back-to-ac function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 25 1</pre><br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
===How to Setup shutting down countdown function manully===<br />
* Login to Raspberry Pi and open a terminal, Typing following command:<br />
<pre> i2cset -y 1 0x17 24 20</pre><br />
PS: 20 means countdown number is 20 seconds, you can change to another integer number. <br />
* Check if the command is enabled the function by read the register value:<br />
<pre> i2cget -y 1 0x17 25 </pre><br />
===How to self-diagnose UPS PLUS ===<br />
* Please visit this URL in browser: [ https://api.thekoziolfoundation.com/ ]<br />
[[File:Ups diagnosistool.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Filling the blank with your Deivce UIDs which can be getting from /home/pi/bin/upsPlus_iot.py script, open a terminal and typing:<br />
<pre> python3 /home/pi/bin/upsPlus_iot.py </pre><br />
[[File:Ups uids.jpg|left | 500px]]<br />
<br style="clear:both;"><br />
* Copy UID0, UID1, UID2 to browser and press "Diagnosis" button on the page:<br />
[[File:Ups dignosis.jpg|left|500px]]<br />
<br style="clear:both;"><br />
* Then you will get the test results and suggestions on the page.<br />
[[File:Dignosis result.png|left|500px]]<br />
<br style="clear:both;"><br />
<font color=red> Pink color means it is critical message and Blue color means suggestion.</font><br />
<br />
==Battery Logger==<br />
* Thanks for Nordln's help.<br />
* UPS Plus Battery Logger: [ https://github.com/Nordln/upsplusv5-battery-logger.git ]<br />
[[File:Ups logger.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Package Includes==<br />
* 1 x UPS Plus For Raspberry Pi<br />
* 4 x M2.5 copper pillar <br />
* 4 x M2.5 screws<br />
* 4 x M2.5 long copper stick<br />
* 4 x M2.5 nuts<br />
* 1 x Acrylic shield<br />
* 1 x Instructions<br />
[[File:UPS V2 9.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Tutorial Video==<br />
* Youtube link:<br />
[ https://youtu.be/jQljQJ41I5A ]<br />
* QRCODE:<br />
[[File:Upsplus tutorial1.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Why does the battery light go off sometime and lights up in a while? <br />
** A: This is because the power chip performs battery re-sampling, and the purpose is that the data of inferior batteries is inaccurate during the sampling process.<br />
* Q: Why is the power cut off every once in a while? <br />
** A: Please check the battery charging current, the data discharge direction or the charging direction. If the load is too large, the charging may not be enough, which will cause this problem.<br />
* Q: What kind of wall charger should I use? <br />
** A: If the load is normal, it is recommended to use an ordinary 5V@2A charging head. If you need to carry a slightly higher load, it is recommended to use a fast charging source. We support FCP, AFC, SFCP protocols Fast charging source.<br />
* Q: Can I directly input 9V and 12V to the USB port?<br />
** A: No, if you must do this, you must remove the DP, DM and other related detection pins, and ensure that the power supply is stable.<br />
* Q: I heard howling, why is this? <br />
** A: Because of the no-load protection mechanism, the howling will disappear after the load is installed.<br />
* Q: using firmware v. 4, when AC power comes back on during the shutdown countdown, I realized that the 5V supply for the raspberry pi is not switched off at the end of the countdown. so, after shutdown of the operating system, the raspberry pi will never restart automatically.<br />
IMHO the following would be better: once a shutdown countdown starts, and we have the Back-To-AC Auto Power UP flag set, then:<br />
the shutdown sequence should proceed to its end,<br />
switch off the 5V-power for a certain time (a couple of seconds maybe), regardless of AC Power.<br />
switch the 5V back on when AC power is restored.<br />
otherwise, I am very happy with the product.<br />
one more thing: would be nice to have some sort of alert for new firmware releases and release notes for these.<br />
** A: Please refer to this URL: https://github.com/geeekpi/upsplus/issues/7<br />
<br />
==Keywords==<br />
* UPS Plus, GeeekPi UPS V5, UPS for Raspberry Pi</div>TaterLihttps://wiki.52pi.com/index.php?title=Main_Page&diff=10079Main Page2021-04-14T03:04:24Z<p>TaterLi: /* Case & Enclosure & Heat sink */</p>
<hr />
<div>='''RaspberryPi Modules'''=<br />
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. <br />
you can select one of them and click the links to get more information about it.<br />
==HCL==<br />
This is Hardware Compatible List.<br />
[[Hardware Compatible List]]<br />
<br />
==Hat Stack==<br />
* [[ DockerPi RISCV ProtoType Board SKU: EP-0117 ]]<br />
* [[ DockerPi-H Station Board SKU: EP-0116 ]]<br />
* [[ DockerPi NightLight SKU: EP-0098 ]]<br />
* [[ DockerPi 4 Channel Relay SKU: EP-0099 ]]<br />
* [[ DockerPi PowerBoard SKU: EP-0104 ]]<br />
* [[ DockerPi Sensor Hub Development Board SKU: EP-0106 ]]<br />
* [[ DockerPi Motor Board(A) SKU: EP-0108 ]]<br />
* [[ DockerPi DIY Programmable intelligent toycar SKU: EP-0109]]<br />
* [[ IoT Node(A) SKU: EP-0105 ]]<br />
<br />
==Development Boards==<br />
==AI Learning==<br />
* [[ NVIDIA® Jetson Nano™ Developer Kit SKU: EZ-0075 ]]<br />
* [[ AC8265 Wireless NIC 2.4G/5G WiFi Bluetooth 4.2 for Jetson Nano SKU: L-0031 ]]<br />
<br />
==IoT Modules==<br />
* [[ ESP32 WROVER KIT SKU: EP-0090 ]]<br />
* [[ ESP32 WROVER SKU: EZ-0061 ]]<br />
* [[ GeeekNET ESP32 Development Board SKU: EZ-0062 ]]<br />
* [[ GeeekNET ESP32-WROVER Development Board SKU: EZ-0063 ]]<br />
----<br />
==Tinker Board==<br />
* [[ ASUS Tinker Board SKU: EZ-0066 ]]<br />
* [[ ASUS Tinker Board Model S SKU: EZ-0065 ]]<br />
<br />
----<br />
<br />
==Raspberry Pi==<br />
* [[ Raspberry Pi 4 Model B 2GB Version SKU: ER-0018 ]]<br />
* [[ Raspberry Pi 3 Model B SKU: ER-0007 ]]<br />
* [[ Raspberry Pi zero w (with enclosure)Kit SKU: K-0231 ]]<br />
* [[ Raspberry Pi zero (with enclosure) Kit SKU:K-0230 ]]<br />
----<br />
<br />
==Banana Pi==<br />
* [[ Banana Pi R64 SKU: EB-0020 ]]<br />
* [[ Banana Pi M4 SKU: EP-0019 ]]<br />
* [[ Banana Pi M64 SKU: EB-0012 ]]<br />
* [[ Banana Pi M2 ULTRA SKU: EB-0013 ]]<br />
<br />
==Gaming Assesories==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ USB Game Pad for N64 SKU: D-0023 ]]<br />
* [[ NT68676 Arcade screen driver board SKU: Z-0261 ]]<br />
* [[ USB Microphone SKU: Z-0179 ]]<br />
* [[ GuliKit Route+ Bluetooth Transmitter For Nintendo SWITCH SKU: Z-0279 ]]<br />
* [[ 8579 Switch Bluetooth Programming Handle (Black) SKU: Z-0252 ]]<br />
* [[ 8579 Switch Bluetooth Programming Handle (Blue) SKU: Z-0253 ]]<br />
* [[ 8580 Switch Bluetooth Handle (Gray) SKU: Z-0254 ]]<br />
* [[ 8951 PS4 Private mode Bluetooth controller SKU: Z-0255 ]]<br />
* [[ 8577 Switch Split Gamepad SKU: Z-0257 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ GPI Case SKU: Z-0260 ]]<br />
</td><br />
</tr></table><br />
<br />
==Electronic Accessories==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ GeeekPi 40Pin Header Kit Box SKU: T-0020 ]]<br />
</td><br />
</tr></table><br />
<br />
==Extension Modules==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ UPS Plus SKU: EP-0136 ]]<br />
* [[ Black prototype shield expansion board for Arduino SKU: EP-0131 ]]<br />
* [[ 24/20-pin ATX DC Power Supply Breakout Board SKU: EP-0130 ]]<br />
* [[ PCM5122 HIFI Audio DAC Expansion Board For RPi SKU: D-0020 ]]<br />
* [[ Camera Module For RPi Zero/w SKU: ER-0014 ]]<br />
* [[ TF-Luna Laser LiDAR module SKU: D-0018 ]]<br />
* [[ nRF52840 M.2 Developer Kit SKU: G-0002 ]]<br />
* [[ GPIO Screw Terminal Hat SKU: EP-0129 ]]<br />
* [[ RPi 4G 3G Hat SKU: EP-0128 ]]<br />
* [[ RPi Isolated PoE Hat SKU: EP-0127 ]]<br />
* [[ Easy Multiplexing Board SKU: EP-0123 ]]<br />
* [[ GeeekPi 1/2 Breadboard SKU: EP-0124 ]]<br />
* [[ GeeekPi 1/4 Breadboard SKU: EP-0125 ]]<br />
* [[ GeeekPi Fullsize Breadboard SKU: EP-0126 ]]<br />
* [[ RPi Prototype Hat Breadboard SKU: K-0335 ]]<br />
* [[ Jetson Nano 800M IMX219 160 Degree Wide angle Camera SKU:ER-0022 ]]<br />
* [[ 8 Bit Level conversion module SKU: D-0010 ]]<br />
* [[ MAX7219 32x8 LED Matrix SKU: D-0012 ]]<br />
* [[ HC-SR04 Ultrasonic Module SKU: D-0013 ]]<br />
* [[ 3D printer Endstop mechanical limit switch RAMPS SKU: D-0015 ]]<br />
* [[ MAX7219 8x8 LED Matrix SKU: D-0016 ]]<br />
* [[ MAX7219 DIP Chip 8x8 LED Matrix SKU: D-0017 ]]<br />
* [[ Dual Fan Hat for RPi SKU: EP-0120 ]]<br />
* [[ GPIO Edge Extension SKU: EP-0121 ]]<br />
* [[ UPS (With RTC & Coulometer) For Raspberry Pi SKU: EP-0118 ]]<br />
* [[ Photoelectric limit switch for 3D Printer SKU: D-0008 ]]<br />
* [[ MAX7219 7-Segment LED matrix SKU: D-0009 ]]<br />
* [[ Stepper Motor SKU: D-0011 ]]<br />
* [[ PIR Sensor SKU: D-0005 ]]<br />
* [[ PCF8574T LCD Driver Board SKU: D-0006 ]]<br />
* [[ 4Bit-7Seg Digital Display Module SKU: D-0007 ]]<br />
* [[ 48Vto12V PoE splitter module SKU: P-0010 ]]<br />
* [[ 48Vto12V PoE splitter module with Gigabit NIC SKU: P-0011 ]]<br />
* [[ TMC2209 3D Printer Driver Board Pack SKU: D-0003 ]]<br />
* [[ Vibration Sensor Module SKU: EZ-0089 ]]<br />
* [[ Pitaya Go IoT SKU: Z-0269 ]]<br />
* [[ Power-Over-Ethernet (PoE) HAT for RPi 4B/3B+ SKU: EP-0115 ]]<br />
<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ 8MM Camera module for Raspberr Pi SKU: ER-0021 ]]<br />
* [[ Gigabit USB-C PoE Splitter SKU:P-0005]]<br />
* [[ Gigabit USB-C PoE Splitter 48V to 5V for RPi 4B SKU:P-0006]]<br />
* [[ Pitaya go SKU: Z-0269 ]]<br />
* [[TFmini PLus Lidar Module（Distance measurement） SKU:Z-0231 ]]<br />
* [[ Raspberry Pi Zero/Zero W Camera Ribben Cable Wire(Gold finger) SKU: Z-0209 ]]<br />
* [[ Raspberry Pi night vision camera adjustable-focus module ER-0016 ]]<br />
* [[1602 Serial LCD Module Display SKU:Z-0234 ]]<br />
* [[2004 Serial LCD Module Display SKU:Z-0235 ]]<br />
* [[USB Isolator SKU:EP-0101 ]]<br />
* [[USB dongle for Raspberry Pi Zero/Zero W SKU:EP-0097 ]] <br />
* [[MicroBit Basic Extension Board Horizontal Version SKU: EP-0095 ]]<br />
* [[MicroBit Basic Extension Board Vertical Version SKU: EP-0096 ]]<br />
* [[TFmini Lidar Module（Distance measurement） SKU:EZ-0068 ]]<br />
* [[Raspberry Pi GPIO Breakout Board Big Black (T-Type) SKU: EP-0094 ]]<br />
* [[Raspberry Pi GPIO Breakout Board V1.1(T-Type) SKU: K-0291 ]]<br />
* [[GeeekPi 1/2 Sized Breadboard SKU: EP-0091 ]]<br />
* [[GeeekPi 1/4 Sized Breadboard SKU: EP-0092 ]]<br />
* [[GeeekPi Full Sized Breadboard SKU: EP-0093 ]]<br />
* [[Pi Zero Enc28j60 Network Adapter Module SKU: EP-0088 ]]<br />
* [[UPS for Raspberry Pi 4B/3B+/3B SKU: EP-0114]]<br />
* [[UPS for Raspberry Pi 3B/3B+ SKU: EP-0100]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[USB Joystick controller Board SKU: EP-0080 ]]<br />
* [[Raspberry Pi LM75B temperature Sensor v1.0 SKU:EP-0031]]<br />
* [[Raspberry Pi Super Capacitor RTC(English)|Raspberry Pi Super Capacitor RTC]]<br />
* [[DS1307 RTC Module with BAT for Raspberry Pi SKU: EP-0059]]<br />
* [[Raspberry Pi Expansion Board(English)|Raspberry Pi Expansion Board]]<br />
* [[RPI-B+-GPIO-Triple(English)| RPI-B+-GPIO-Triple]]<br />
* [[Raspberry Pi Heatsink(English) | Raspberry Pi Heatsink]]<br />
* [[Raspberry Pi ADC-DAC Module(English) | Raspberry Pi ADC-DAC Module]]<br />
* [[USB Gamepad SKU: Z-0177 ]]<br />
* [[RPI B+ GPIO Reference Board SKU:EP-0021 ]]<br />
* [[RPI B+ Rectangle Extend Board SKU:EP-0020 ]]<br />
* [[RaspberryPi Downgrade(English)| RaspberryPi Downgrade]]<br />
* [[RaspberryPi B+ GPIO Reference Board(English)| RaspberryPi B+ GPIO Reference Board]]<br />
* [[RaspberryPi RS232 UART Board(English)| RaspberryPi RS232 UART Board]]<br />
* [[GPS Module SKU:EZ-0024]]<br />
* [[USB-Port-GPS Module SKU:EZ-0048]]<br />
* [[VGA666 Module For RPi SKU:EP-0073]]<br />
</td></tr></table><br />
<br />
==Case & Enclosure & Heat sink==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ Aluminum Alloy CNC Heat Sink without Fan for Raspberry Pi CM4 Module SKU: ZP-0111 ]]<br />
* [[ Aluminum Alloy CNC Heat Sink with Fan for Raspberry Pi CM4 Module SKU: ZP-0112 ]]<br />
* [[ Aluminum alloy CNC without fan Armor Case for Raspberry Pi 4B SKU: C-0027 ]]<br />
* [[ Armor lite heatsink with pwm fan for Raspberry Pi 4B SKU: ZP-0110 ]]<br />
* [[ Argon One Case V2 SKU: C-0023 ]]<br />
* [[ Poly+ Black Case for RPi 4B SKU: C-0025 ]]<br />
* [[ Low-profile ICE tower cooler (Type B) for RPi SKU: EP-0132 ]]<br />
* [[ Plastic Case Kit for RPi ZeroW/Zero SKU: K-0567 ]]<br />
* [[ Argon ONE M.2 Case SKU: C-0022 ]]<br />
* [[ NANOSOUND 1 SKU: C-0020]]<br />
* [[ Acrylic Case for NT68676 Controller Board SKU: ZP-0105 ]]<br />
* [[ Nes3Pi SKU: ZP-0103 ]]<br />
* [[ NesPi 4 Case For RPi 4B SKU: C-0015 ]]<br />
* [[ Rack Tower Ultimate (12Layer) SKU: ZP-0108 ]]<br />
* [[ Rack Tower Pro SKU: ZP-0089 ]]<br />
* [[ Jetson Nano Fan kit SKU: F-0003 ]]<br />
* [[ Acrylic Set-top box kit for RPi 4B SKU: ZP-0102 ]]<br />
* [[ Acrylic case for Jetson Nano SKU: ZP-0101 ]]<br />
* [[ Transparent Layer acrylic bracket shell SKU: ZP-0040 ]]<br />
* [[ Brown layer acrylic bracket shell SKU: ZP-0039 ]]<br />
* [[ Black Low-Profile ICE Cooling Fan For RPi SKU: EP-0122 ]]<br />
* [[ Jetson Nano Iron Case(B01Version) SKU: ZP-0100 ]]<br />
* [[ Icon Case For RPi 4B SKU: ZP-0099]]<br />
* [[ Power Button For RPi SKU: EP-0077]]<br />
* [[ Pi Supply & USB HUB SKU: EP-0078]]<br />
* [[ Pi Supply & USB HUB Without Battery SKU: EP-0079]]<br />
* [[ RPI 5MP CSI Camera SKU: ER-0011]]<br />
* [[ ESP32 Module SKU: EZ-0059 ]]<br />
* [[ Brand new 2.4G wireless mini keyboard with mouse touchpad SKU: Z-0153 ]]<br />
* [[ RPI-ADS1115-ADC-Module SKU:EP-0076]]<br />
* [[ Acrylic Raspberry Pi set-top box kit SKU: ZP-0098 ]]<br />
* [[ 6-Layer Acrylic Cluster framework For Raspberry Pi SKU: ZP-0092 ]]<br />
* [[ Acrylic holder for RPi 4B camera SKU: ZP-0093 ]]<br />
* [[ Argon ONE Aluminum case with Fan for RPi 4B SKU: C-0008 ]]<br />
* [[ NEO Case SKU: C-0006 ]]<br />
* [[ Metal Case for RPi 4B SKU: C-0003 ]]<br />
* [[ Aluminum Case for RPi 4B with 3510 fan SKU:ZP-0090 ]]<br />
* [[ Aluminum Case for RPi 4B with 2510 fan SKU:ZP-0091 ]]<br />
* [[ ABS Case for RPi 4B SKU: C-0005 ]]<br />
* [[ Metal Case for RPi 4B SKU: C-0004 ]]<br />
* [[ Rack Tower SKU: ZP-0088 ]]<br />
* [[ Metal Case For Low-Profile ICE Tower Cooler SKU: ZP-0087 ]] <br />
* [[ Plastic Case for RPi 4B SKU: C-0002 ]]<br />
* [[ ABS Case For RPi 4B SKU: C-0001 ]]<br />
* [[ Low Profile Ice Tower Cooler SKU: EP-0112 ]]<br />
* [[ Nes4Pi SKU: ZP-0086 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ ABS and Acrylic case with 4010 fan for RPi 4B SKU: ZP-0079 ]]<br />
* [[ 9-Layer Acrylic case (Black & Bigfan) for RPi 4B SKU: ZP-0078 ]]<br />
* [[ 9-Layer Acrylic case (Black) for RPi 4B SKU: ZP-0068 ]]<br />
* [[ Aluminum Case with Suspension Fan for RPi 4B SKU: Z-0278 ]]<br />
* [[ 9-Layer Acrylic case for RPi 4B SKU: ZP-0085 ]]<br />
* [[ ICE Tower Cooling Fan For Jetson Nano SKU: EP-0113 ]]<br />
* [[ ICE Tower Cooling Fan Black SKU: EP-0111 ]]<br />
* [[ E Type ABS Case for RPi 4B SKU: ZP-0081 ]]<br />
* [[ L Type ABS Case for RPi 4B SKU: ZP-0082 ]]<br />
* [[ Y Type Aluminum Case for RPi 4B SKU: ZP-0083 ]]<br />
* [[ ABS Electrical Box for RPi 4B SKU: Z-0272 ]]<br />
* [[ ABS Electrical Box for RPi 3B/3B+ SKU: C-0007 ]]<br />
* [[ ABS Buckle Case for RPi 4B SKU: Z-0273 ]]<br />
* [[ 5-layer acrylic case for RPi 4B SKU: ZP-0080 ]]<br />
* [[ Armor Case For RPi 4B with Dual Fan SKU: ZP-0077 ]]<br />
* [[ Armor Case For RPi 4B/3B/3B+ without Fan SKU: ZP-0074 ]]<br />
* [[ New ABS H-Type Case for Raspberry Pi 4B SKU: ZP-0075 ]]<br />
* [[ ABS experiment holder platform SKU: ZP-0073 ]]<br />
* [[ 9 Layers Acrylic Case with 4010 Fan SKU: ZP-0076 ]]<br />
* [[ 9 Layers Acrylic Case with Fan SKU: ZP-0067 ]]<br />
* [[ Single layer Acrylic Case with transparent fan SKU: ZP-0066 ]]<br />
* [[ Brown single layer Acrylic Case with fan SKU: ZP-0065 ]]<br />
* [[ Square radiator for Raspberry Pi 4B SKU: ZP-0038 ]]<br />
* [[ Iron Case for Jetson Nano SKU: ZP-0072 ]]<br />
* [[ Aluminum Heat Sink Pack for Raspberry Pi 4B SKU: Z-0266 ]]<br />
* [[ Metal Case for RPi 4B with 4010 Fan SKU: ZP-0070 ]]<br />
* [[ Metal Case for RPi 4B (Silver & Black) SKU: ZP-0071 ]]<br />
* [[ Metal Case for RPi 4B (Silver & Black) SKU: Z-0264 ]]<br />
* [[ ICE-Tower CPU Cooling Fan for Raspberry Pi SKU: EP-0107 ]]<br />
* [[ Armor Case For RPi 3B+ without Fan SKU: ZP-0051 ]]<br />
* [[Armor Case for Raspberry Pi 3A+ SKU: Z-0237 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Acrylic Shell With Fan Guard For RPi SKU: ZP-0025 ]]<br />
* [[Acrylic Shell With Fan Guard For RPi (Brown Color) SKU: ZP-0069 ]]<br />
* [[3510 Version Extreme Cooling Fan Kit For Raspberry Pi 4B/3B/3B+ SKU: ZP-0042]]<br />
* [[New version Copper Heat Sink SKU: Z-0185]]<br />
* [[Ultimate Cooling Fan Kit For Raspberry Pi 4B/3B+/3B/2B/B+ SKU: ZP-0037]]<br />
* [[ABS case with fan and heat sink for Raspberry Pi 3B+/3B/2B/B+(Black/White) SKU: Z-0183]] <br />
* [[Raspberry Pi 3B white acrylic case SKU: Z-0127]]<br />
* [[Raspberry Pi 3 Enclosure with heat sinks SKU: K-0172]]<br />
* [[ USB HUB Power Supply for Raspberry Pi Double Layer Acrylic Rack SKU: K-0178 ]]<br />
* [[ Black ABS enclosure with screwdriver for Raspberry Pi SKU: Z-0157 ]]<br />
* [[4-layer-Transparent-Acrylic-Case-Clear-Shell-Enclosure-for-Raspberry-Pi-3-Model-B/2B/B+ SKU: ZP-0024]]<br />
* [[Micro-HDMI-to-Standard-HDMI-Male-Cable-4K-Pi4B SKU:L-0030]]<br />
* [[ Ultimate Cooling Fan Kit for Raspberry Pi 3/2/B+ SKU: ZP-0029 ]]<br />
* [[RPi ABS Case SKU: ZP-0049 ]]<br />
* [[Armor Case For RPi 3B SKU: Z-0193]]<br />
* [[Armor Case For RPi 3B+ SKU: Z-0208 ]]<br />
* [[10 Layers Acrylic Case for Raspberry Pi 3B+/3B/2B/B+ SKU: Z-0190]]<br />
* [[Raspberry Pi 3 Aluminum alloy Case SKU: Z-0184]]<br />
</td><br />
</tr></table><br />
<br />
==Cooling Accessories==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<pre> EOL stands for "End of Life", means this product will not produce any more</pre><br />
* [[ 5V Mini Cooling Fan for Raspberry Pi SKU: F-0010 ]]<br />
* [[ MINIWARE MHP30 Mini Hot Plate Preheater SKU: D-0022 ]]<br />
* [[ 4010 24V Blue Backlight Fan SKU: F-0008 ]]<br />
* [[ 5V DVR Mainboard Fan SKU: F-0007 ]]<br />
* [[ 4010 Blower SKU: F-0005 ]]<br />
* [[ 5015 Blower SKU: F-0006 ]]<br />
* [[DC 12V Brushless Blue light Fan SKU: F-0001 ]]<br />
* [[DC 12V Brushless RGB light Fan SKU: F-0002 ]]<br />
</td></tr></table><br />
<br />
==Electronic Engineer Tools==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ DT71 Mini digital tweezers SKU: T-0022 ]]<br />
* [[ Desoldering Iron Kit SKU:T-0021 ]]<br />
* [[ TS80P More-US SKU:T-0019 ]]<br />
* [[ TS80P kit SKU:T-0015 ]]<br />
* [[ TS100 kit SKU:T-0016 ]]<br />
* [[ Tin Lead Rosin Core Solder Wire for Electrical Soldering (1.0mm/0.04Inch) SKU: T-0017 ]]<br />
* [[ Tin Lead Rosin Core Solder Wire for Electrical Soldering (0.8mm/0.03Inch) SKU: T-0018 ]]<br />
* [[ DS213 mini oscilloscope SKU: Z-0241 ]]<br />
</td></tr></table><br />
<br />
==Displays==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<pre> EOL stands for "End of Life", means this product will not produce any more</pre><br />
* [[ 2.13 inch E-paper (BRW) SKU: EP-0133 ]]<br />
* [[0.91 Inch OLED Display SKU: EP-0119 ]]<br />
* [[PiOLED (0.91 Inch OLED Module) SKU: S-0007 ]]<br />
* [[0.91 Inch OLED Module SKU: S-0006]]<br />
* [[0.96 Inch OLED Module SKU: S-0005]]<br />
* [[0.91 Inch OLED Module SKU: EP-0060]]<font color=red>EOL</font><br />
* [[0.96 Inch OLED Module SKU:EP-0049]] <font color=red>EOL</font><br />
* [[52Pi-BPi LCD 1602 Module SKU:EP-0045]]<br />
* [[RGB LCD1602 SKU:EP-0058]]<br />
* [[RPI-RGB-LED-Matrix SKU:EP-0075]]<br />
* [[Raspberry Pi 2.2 Inch GPIO display(without touch screen) SKU:EP-0062]]<br />
* [[Raspberry Pi 2.4 Inch GPIO touch screen SKU:EP-0063]]<br />
* [[TFT28 Display + Touch Panel + NoPCB SKU:EP-0066 ]]<br />
* [[TFT28 Display + Touch Panel + PCB SKU:EP-0065 ]]<br />
* [[5-Inch-800x480-HDMI-TFT-LCD-Touch-Screen SKU:Z-0053]]<br />
* [[5-Inch-800x480-HDMI-GPIO-Touch-Screen SKU:EP-0072]]<br />
* [[5-Inch-800x480-Capacitive-Touch-Screen SKU: EP-0081 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ 7 inch 1024x600 Screen and driver board with Amplifier and Two speakers Kit SKU: EP-0089]]<br />
* [[7-Inch-1024x600 Capacitive Touch Screen (Extend Two USB HOST Port) with 720P Camera SKU: EP-0087 ]]<br />
* [[7-Inch-1024x600 Capacitive Touch Screen (Extend Two USB HOST Port) SKU: EP-0085 ]]<br />
* [[7-Inch-1024x600 Capacitive Touch Screen DIY Kit SKU: EP-0084]]<br />
* [[7-Inch-1024x600 Capacitive Touch Panel DIY Kit SKU: EP-0082]]<br />
* [[7-Inch-1024x600 Display Kit (with Touch Screen) SKU:Z-0017]]<br />
* [[7-Inch-1024x600 Display Kit (without Touch Screen) SKU:Z-0051]]<br />
* [[7-Inch-1024x600 Monitor SKU:K-0106 ]]<br />
* [[7-Inch-800x480 Display Kit(without Touch Screen) SKU:Z-0111]]<br />
* [[7-Inch-1280x800 Display Kit(without Touch Screen) SKU:Z-0112]]<br />
* [[7-Inch-800x480 Monitor SKU:K-0101]]<br />
* [[7-Inch-1280*800 Monitor SKU:K-0102]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[15.6 Inch 1920x1080 FHD Display SKU: S-0003 ]]<br />
* [[10.1 Inch 1280x800 Display Kit(without Touch Screen) SKU: S-0001 ]]<br />
* [[10.1-Inch-1024x600 Display Kit (without Touch Screen) SKU:Z-0113]]<br />
* [[10.1-Inch-1366x768 Display Kit(without Touch Screen) SKU:Z-0114]]<br />
* [[ 10.1-Inch-1280x800 Display Kit(Without Touch Screen) SKU:Z-0143]]<br />
* [[10.1-Inch-1366x768 Monitor SKU:K-0103]]<br />
* [[Super Luxury 10.1 LCD Television SKU: K-0104]]<br />
</td></tr></table><br />
<br />
==Power Supply==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ Milestone wireless charger SKU: P-0017 ]]<br />
* [[5V-3A EU-Standard with switch SKU:P-0007]] <br />
* [[5V-3A US-Standard with switch SKU:P-0008]] <br />
* [[5V-3A UK-Standard with switch SKU:P-0009]] <br />
* [[5V-3A UK-Standard SKU:P-0004]] <font color=red>EOL</font><br />
* [[5V-3A EU-Standard SKU:P-0003]] <font color=red>EOL</font><br />
* [[5V-3A US-Standard SKU:P-0002]] <font color=red>EOL</font><br />
* [[5V-4A Travel Adapter SKU:P-0001]]<br />
* [[5V-2.5A-AU-Standard SKU:Z-0132]]<br />
* [[5V-2.5A-UK-Standard SKU:Z-0133]]<br />
* [[5V-2.5A-US-Standard SKU:Z-0121]]<br />
* [[5V-2.5A-EU-Standard SKU:Z-0097]]<br />
* [[5V-2.5A-EU/US/UK/AU-Plug SKU:Z-0136]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[US-Standard-With-Power-Switch-5V-2.5A SKU:Z-0147]]<br />
* [[EU-Standard-With-Power-Switch-5V-2.5A SKU:Z-0148]]<br />
* [[AU-Standard-With-Power-Switch-5V-2.5A SKU:Z-0149]]<br />
* [[UK-Standard-With-Power-Switch-5V-2.5A SKU:Z-0150]]<br />
* [[Banana Pi US-standard Power Supply SKU: Z-0154]]<br />
* [[Banana Pi EU-standard Power Supply SKU: Z-0155]]<br />
* [[MicroUSB Cable with LCD Voltage/Current Display SKU: L-0026 ]]<br />
* [[MicroUSB Cable with LCD Voltage/Current Display(Support IPhone) SKU: L-0027 ]]<br />
</td></tr></table><br />
<br />
==Raspberry Pi Kits==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ Raspberry Pi Pico Starter Kit SKU: K-0581 ]]<br />
* [[ Metal Alloy Shell with Silver/Black Low-Profile ICE tower Cooler for RPi 4B SKU: K-0522 ]]<br />
* [[ 220PCS Standoffs M2.5 Brass Spacer Kit for Raspberry Pi SKU: T-0008 ]]<br />
* [[RPi 4B Starter Kit SKU: K-0512 ]]<br />
* [[ABS Holder Kit For RPi & Arduino SKU: K-0502 ]]<br />
* [[ ABS Case for RPi 4B with 3.5 Inch Resistive Touch Screen SKU: K-0403 ]]<br />
* [[Arcade Game Machine DIY Kits with Joysticks(Double Players) SKU: K-0167 ]]<br />
* [[Arcade Game Machine DIY Kits without Joysticks (Single Player) SKU: K-0168 ]]<br />
* [[Arcade Game Machine DIY Kits without Joysticks (Double Players) SKU: K-0169 ]]<br />
* [[7 inch 1024x600 Capacitive Touch Screen(Extend Two USB Hosts) with 720P Camera and Acrylic Case Kit SKU: K-0259 ]]<br />
* [[5 inch Capacitive touch screen & Acrylic Case Kit SKU: K-0238 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Retro Game Kit (Single Player) SKU: K-0185]]<br />
* [[Retro Game Kit (Double Players) SKU: K-0186 ]]<br />
* [[Starter Kit SKU: Z-0142]]<br />
* [[Raspberry Pi Complete kit SKU: K-0111]]<br />
* [[Raspberry Pi 3B Overlays Application Kit SKU: Z-0144]]<br />
* [[Raspberry Pi Retro Gamepads Kit with 10.1 inch Monitor SKU: K-0171]]<br />
* [[Raspberry Pi RetroPie Game Kit (with 5 inch GPIO TouchScreen & GamePad x2 ) SKU: K-0174]]<br />
* [[Raspberry Pi RetroPie Game Kit with 2.4GHz wireless GamePad x2]]<br />
* [[Raspberry Pi Acrylic DIY Retro Game Arcade Kit SKU:K-0180]]<br />
</td></tr></table><br />
<br />
==Official Support Products==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Raspberry Pi official 7-Inch-Touch-Screen SKU:Z-0104]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Banana Pi official 7-Inch-Capacitance-Screen SKU:Z-0088]]<br />
</td></tr></table><br />
==X-Series Expansion Board==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<b><font color=red>New Products 2020.4.21 updated</font></b><br><br />
* [[ X872 SKU: EZ-0094 ]]<br />
* [[ X728 SKU: EZ-0095 ]]<br />
* [[ X835 SKU: EZ-0090 ]]<br />
* [[ X856 SKU: EZ-0087 ]]<br />
* [[ X828 SKU: EZ-0088 ]]<br />
* [[ X725 SKU: EZ-0086 ]]<br />
* [[ X855 SKU: EZ-0083 ]]<br />
* [[ X825 SKU: EZ-0082 ]]<br />
* [[ X822 SKU: EZ-0076 ]]<br />
* [[ X852 SKU: EZ-0077 ]]<br />
* [[ X860 SKU: EZ-0078 ]]<br />
* [[ X870 SKU: EZ-0079 ]]<br />
* [[ X735 SKU: EZ-0080 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<b><font color=Green>Old Products 2018.6.6 updated</font></b><br><br />
* [[ X720 SKU: EZ-0072]]<br />
* [[ X730 SKU: EZ-0073]]<br />
* [[ X830 SKU: EZ-0064]]<br />
* [[ X105 SKU: EZ-0008]]<br />
* [[ X200 SKU: EZ-0002]]<br />
* [[ X300 SKU: EZ-0003]]<br />
* [[ X205 SKU: EZ-0046]]<br />
* [[ X400 SKU: EZ-0044]]<br />
* [[ X600 SKU:EZ-0045]]<br />
* [[ X3000 SKU:EZ-0051]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ X6000P-7.1CH DIY Kits SKU:EZ-0052]]<br />
* [[ X5000P Raspberry Pi HiFi Sound Card SKU:EZ-0053]]<br />
* [[ X4000P SKU:EZ-0054]]<br />
* [[ X4000K DIY Kits SKU:EZ-0055]]<br />
* [[ X6000K-8.0CH DIY Kits SKU:EZ-0056]]<br />
* [[ X5000K DIY Kits SKU:EZ-0057]]<br />
* [[ X1000K DIY Kits SKU:EZ-0058]]<br />
</td></tr></table><br />
===X series Acrylic Case===<br />
* [[ Acrylic Case for X725 SKU: ZP-0096 ]]<br />
* [[ Acrylic Case for X825 SKU: ZP-0097 ]]<br />
<br />
==Operation System Card==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[OctoPrint]]<br />
* [[Noobs]]<br />
* [[Raspbian]]<br />
* [[DietPi]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Batocera]]<br />
* [[RetroPie]]<br />
* [[Ubuntu Mate 16.04]]<br />
* [[OSMC]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[5-inch-GPIO-touch-screen-Based-on-Raspbian]]<br />
* [[Windows 10 IOT R2 (Red Stone) 16GB]]<br />
</td></tr></table><br />
<br />
==52Pi Expand Modules ( End Of Life )==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[RPI T-Cobbler GPIO Extend Board With Level shifting SKU:EP-0014]]<br />
* [[RPI T-Cobbler GPIO Extend Board SKU:EP-0003]]<br />
* [[RPI 16x2 LCD+Keypad Kit SKU:Z-0019]]<br />
* [[RPI B+ to B GPIO Downgrade Board SKU:EP-0027 ]]<br />
* [[RPI I2C GPIO Extend Board SKU:EP-0013]]<br />
* [[RPI AD/DA Extend Board SKU:EP-0022]]<br />
* [[RPI B GPIO Reference Board SKU:EP-0018]]<br />
* [[RPI GPIO Triple Extend Board SKU:EP-0012]]<br />
* [[RPI GPIO Rectangle Extend Board SKU:EP-0011]]<br />
* [[RPI I2C Logic Level Converter SKU:EP-0026]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[RPI Infinity cascade IO expand Module SKU:EP-0028]]<br />
* [[RPI Arduino Board SKU:EP-0023]]<br />
* [[RPI RTC Module SKU:EP-0016]]<br />
* [[RPI B TF TO SD SKU:EP-0032]]<br />
* [[RPI UART Extend Board SKU:EP-0017]]<br />
* [[RPI B+ Prototyping Pi Plate Board SKU:EP-0042]]<br />
* [[RPI B+ GPIO Triple Extend Board SKU:EP-0029]]<br />
* [[RPI B Prototyping Pi Plate Board SKU:EP-0004]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[RPI HAT Breakout Mini Kit SKU:EP-0056]]<br />
* [[RPI HAT Prototype Module SKU:EP-0057]]<br />
* [[RPI T Type Extension Board SKU:EP-0046]] <br />
</td></tr></table><br />
<br />
===Documentation===<br />
----<br />
<pre>Some simple guides to setting up the software on your Raspberry Pi.<br />
Beginners should start with NOOBS, which gives the user a choice of operating system from the standard distributions.<br />
The recommended distribution for normal use is Raspbian. <br />
Alternatives are available, such as LibreELEC (Kodi media centre) or Arch Linux.<br />
</pre><br />
* Installing operation system on your Raspberry Pi <br />
** [[NOOBS]]<br />
** [[Installing images]]<br />
** [[SD Cards]]</div>TaterLihttps://wiki.52pi.com/index.php?title=Jetson_Nano_Metal_Case(B01Version)_SKU:_ZP-0100&diff=10078Jetson Nano Metal Case(B01Version) SKU: ZP-01002021-04-14T03:04:12Z<p>TaterLi: TaterLi moved page Jetson Nano Metal Case(B01Version) SKU: ZP-0100 to Jetson Nano Iron Case(B01Version) SKU: ZP-0100: correct info</p>
<hr />
<div>#REDIRECT [[Jetson Nano Iron Case(B01Version) SKU: ZP-0100]]</div>TaterLihttps://wiki.52pi.com/index.php?title=ZP-0100&diff=10077ZP-01002021-04-14T03:04:12Z<p>TaterLi: TaterLi moved page Jetson Nano Metal Case(B01Version) SKU: ZP-0100 to Jetson Nano Iron Case(B01Version) SKU: ZP-0100: correct info</p>
<hr />
<div>==Jetson Nano Iron Case(B01Version)==<br />
[[File:JesonNano 01.jpg|right|320px]]<br />
<br />
==Description==<br />
<PRE>NOTE: The Jetson Nano mainboard and the antenna, camera are not included in the package</PRE><br />
This is a jetson nano case, which can provide switch button, RESET button, FR mode (Factory Recovery mode) antenna interface mounting hole.<br> <br />
It can be installed after you purchase the antenna, also provides an internal cooling fan and installation screwdriver, it is Made of sheet iron.<br><br />
Tt is very beautiful and strong, which can protect your jetson nano very well, and also provides a fan that supports PWM signal.<br />
<br />
==Features==<br />
* Easy to assemble<br />
* Contains necessary components<br />
* Support key switch<br />
* Support reset button<br />
* Support factory mode button<br />
* Support additional antenna installation<br />
* Provide sheet iron protection<br />
==Gallery==<br />
{|<br />
|[[File:JesonNano 02.jpg|left|320px]]<br />
|[[File:JesonNano 03.jpg|none|320px]]<br />
|[[File:JesonNano 04.jpg|none|320px]]<br />
|}<br />
{|<br />
|[[File:JesonNano 05.jpg|left|320px]]<br />
|[[File:JesonNano 06.jpg|none|320px]]<br />
|[[File:JesonNano 07.jpg|none|320px]]<br />
|}<br />
<br />
==Installation Detials==<br />
[[File:Installation guide1.jpg|left|800px]]<br />
[[File:Installation guide2.jpg|left|800px]]<br />
<br style=clear:both;"><br />
==Package Includes==<br />
* 1 x Jetson Nano iron case<br />
* 1 x side fan<br />
* 1 x PWM speed control fan<br />
* 2 x camera iron bracket<br />
* 4 x long screws<br />
* 4 x nut<br />
* 8 x short screws<br />
* 8 x acrylic gasket<br />
* 2 x jumper cap<br />
* 8 x housing screws<br />
* 1 x tweezers<br />
* 1 x screwdriver<br />
* 1 x Reset button<br />
* 1 x FC mode button<br />
* 1 x power switch<br />
[[File:Jeson-Nano清单.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Keywords==<br />
* jetson nano, Jetson Nano Iron Case(B01Version), Iron case,</div>TaterLihttps://wiki.52pi.com/index.php?title=ZP-0100&diff=10076ZP-01002021-04-14T03:03:59Z<p>TaterLi: </p>
<hr />
<div>==Jetson Nano Iron Case(B01Version)==<br />
[[File:JesonNano 01.jpg|right|320px]]<br />
<br />
==Description==<br />
<PRE>NOTE: The Jetson Nano mainboard and the antenna, camera are not included in the package</PRE><br />
This is a jetson nano case, which can provide switch button, RESET button, FR mode (Factory Recovery mode) antenna interface mounting hole.<br> <br />
It can be installed after you purchase the antenna, also provides an internal cooling fan and installation screwdriver, it is Made of sheet iron.<br><br />
Tt is very beautiful and strong, which can protect your jetson nano very well, and also provides a fan that supports PWM signal.<br />
<br />
==Features==<br />
* Easy to assemble<br />
* Contains necessary components<br />
* Support key switch<br />
* Support reset button<br />
* Support factory mode button<br />
* Support additional antenna installation<br />
* Provide sheet iron protection<br />
==Gallery==<br />
{|<br />
|[[File:JesonNano 02.jpg|left|320px]]<br />
|[[File:JesonNano 03.jpg|none|320px]]<br />
|[[File:JesonNano 04.jpg|none|320px]]<br />
|}<br />
{|<br />
|[[File:JesonNano 05.jpg|left|320px]]<br />
|[[File:JesonNano 06.jpg|none|320px]]<br />
|[[File:JesonNano 07.jpg|none|320px]]<br />
|}<br />
<br />
==Installation Detials==<br />
[[File:Installation guide1.jpg|left|800px]]<br />
[[File:Installation guide2.jpg|left|800px]]<br />
<br style=clear:both;"><br />
==Package Includes==<br />
* 1 x Jetson Nano iron case<br />
* 1 x side fan<br />
* 1 x PWM speed control fan<br />
* 2 x camera iron bracket<br />
* 4 x long screws<br />
* 4 x nut<br />
* 8 x short screws<br />
* 8 x acrylic gasket<br />
* 2 x jumper cap<br />
* 8 x housing screws<br />
* 1 x tweezers<br />
* 1 x screwdriver<br />
* 1 x Reset button<br />
* 1 x FC mode button<br />
* 1 x power switch<br />
[[File:Jeson-Nano清单.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Keywords==<br />
* jetson nano, Jetson Nano Iron Case(B01Version), Iron case,</div>TaterLihttps://wiki.52pi.com/index.php?title=Main_Page&diff=10075Main Page2021-04-14T02:57:56Z<p>TaterLi: /* Case & Enclosure & Heat sink */</p>
<hr />
<div>='''RaspberryPi Modules'''=<br />
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. <br />
you can select one of them and click the links to get more information about it.<br />
==HCL==<br />
This is Hardware Compatible List.<br />
[[Hardware Compatible List]]<br />
<br />
==Hat Stack==<br />
* [[ DockerPi RISCV ProtoType Board SKU: EP-0117 ]]<br />
* [[ DockerPi-H Station Board SKU: EP-0116 ]]<br />
* [[ DockerPi NightLight SKU: EP-0098 ]]<br />
* [[ DockerPi 4 Channel Relay SKU: EP-0099 ]]<br />
* [[ DockerPi PowerBoard SKU: EP-0104 ]]<br />
* [[ DockerPi Sensor Hub Development Board SKU: EP-0106 ]]<br />
* [[ DockerPi Motor Board(A) SKU: EP-0108 ]]<br />
* [[ DockerPi DIY Programmable intelligent toycar SKU: EP-0109]]<br />
* [[ IoT Node(A) SKU: EP-0105 ]]<br />
<br />
==Development Boards==<br />
==AI Learning==<br />
* [[ NVIDIA® Jetson Nano™ Developer Kit SKU: EZ-0075 ]]<br />
* [[ AC8265 Wireless NIC 2.4G/5G WiFi Bluetooth 4.2 for Jetson Nano SKU: L-0031 ]]<br />
<br />
==IoT Modules==<br />
* [[ ESP32 WROVER KIT SKU: EP-0090 ]]<br />
* [[ ESP32 WROVER SKU: EZ-0061 ]]<br />
* [[ GeeekNET ESP32 Development Board SKU: EZ-0062 ]]<br />
* [[ GeeekNET ESP32-WROVER Development Board SKU: EZ-0063 ]]<br />
----<br />
==Tinker Board==<br />
* [[ ASUS Tinker Board SKU: EZ-0066 ]]<br />
* [[ ASUS Tinker Board Model S SKU: EZ-0065 ]]<br />
<br />
----<br />
<br />
==Raspberry Pi==<br />
* [[ Raspberry Pi 4 Model B 2GB Version SKU: ER-0018 ]]<br />
* [[ Raspberry Pi 3 Model B SKU: ER-0007 ]]<br />
* [[ Raspberry Pi zero w (with enclosure)Kit SKU: K-0231 ]]<br />
* [[ Raspberry Pi zero (with enclosure) Kit SKU:K-0230 ]]<br />
----<br />
<br />
==Banana Pi==<br />
* [[ Banana Pi R64 SKU: EB-0020 ]]<br />
* [[ Banana Pi M4 SKU: EP-0019 ]]<br />
* [[ Banana Pi M64 SKU: EB-0012 ]]<br />
* [[ Banana Pi M2 ULTRA SKU: EB-0013 ]]<br />
<br />
==Gaming Assesories==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ USB Game Pad for N64 SKU: D-0023 ]]<br />
* [[ NT68676 Arcade screen driver board SKU: Z-0261 ]]<br />
* [[ USB Microphone SKU: Z-0179 ]]<br />
* [[ GuliKit Route+ Bluetooth Transmitter For Nintendo SWITCH SKU: Z-0279 ]]<br />
* [[ 8579 Switch Bluetooth Programming Handle (Black) SKU: Z-0252 ]]<br />
* [[ 8579 Switch Bluetooth Programming Handle (Blue) SKU: Z-0253 ]]<br />
* [[ 8580 Switch Bluetooth Handle (Gray) SKU: Z-0254 ]]<br />
* [[ 8951 PS4 Private mode Bluetooth controller SKU: Z-0255 ]]<br />
* [[ 8577 Switch Split Gamepad SKU: Z-0257 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ GPI Case SKU: Z-0260 ]]<br />
</td><br />
</tr></table><br />
<br />
==Electronic Accessories==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ GeeekPi 40Pin Header Kit Box SKU: T-0020 ]]<br />
</td><br />
</tr></table><br />
<br />
==Extension Modules==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ UPS Plus SKU: EP-0136 ]]<br />
* [[ Black prototype shield expansion board for Arduino SKU: EP-0131 ]]<br />
* [[ 24/20-pin ATX DC Power Supply Breakout Board SKU: EP-0130 ]]<br />
* [[ PCM5122 HIFI Audio DAC Expansion Board For RPi SKU: D-0020 ]]<br />
* [[ Camera Module For RPi Zero/w SKU: ER-0014 ]]<br />
* [[ TF-Luna Laser LiDAR module SKU: D-0018 ]]<br />
* [[ nRF52840 M.2 Developer Kit SKU: G-0002 ]]<br />
* [[ GPIO Screw Terminal Hat SKU: EP-0129 ]]<br />
* [[ RPi 4G 3G Hat SKU: EP-0128 ]]<br />
* [[ RPi Isolated PoE Hat SKU: EP-0127 ]]<br />
* [[ Easy Multiplexing Board SKU: EP-0123 ]]<br />
* [[ GeeekPi 1/2 Breadboard SKU: EP-0124 ]]<br />
* [[ GeeekPi 1/4 Breadboard SKU: EP-0125 ]]<br />
* [[ GeeekPi Fullsize Breadboard SKU: EP-0126 ]]<br />
* [[ RPi Prototype Hat Breadboard SKU: K-0335 ]]<br />
* [[ Jetson Nano 800M IMX219 160 Degree Wide angle Camera SKU:ER-0022 ]]<br />
* [[ 8 Bit Level conversion module SKU: D-0010 ]]<br />
* [[ MAX7219 32x8 LED Matrix SKU: D-0012 ]]<br />
* [[ HC-SR04 Ultrasonic Module SKU: D-0013 ]]<br />
* [[ 3D printer Endstop mechanical limit switch RAMPS SKU: D-0015 ]]<br />
* [[ MAX7219 8x8 LED Matrix SKU: D-0016 ]]<br />
* [[ MAX7219 DIP Chip 8x8 LED Matrix SKU: D-0017 ]]<br />
* [[ Dual Fan Hat for RPi SKU: EP-0120 ]]<br />
* [[ GPIO Edge Extension SKU: EP-0121 ]]<br />
* [[ UPS (With RTC & Coulometer) For Raspberry Pi SKU: EP-0118 ]]<br />
* [[ Photoelectric limit switch for 3D Printer SKU: D-0008 ]]<br />
* [[ MAX7219 7-Segment LED matrix SKU: D-0009 ]]<br />
* [[ Stepper Motor SKU: D-0011 ]]<br />
* [[ PIR Sensor SKU: D-0005 ]]<br />
* [[ PCF8574T LCD Driver Board SKU: D-0006 ]]<br />
* [[ 4Bit-7Seg Digital Display Module SKU: D-0007 ]]<br />
* [[ 48Vto12V PoE splitter module SKU: P-0010 ]]<br />
* [[ 48Vto12V PoE splitter module with Gigabit NIC SKU: P-0011 ]]<br />
* [[ TMC2209 3D Printer Driver Board Pack SKU: D-0003 ]]<br />
* [[ Vibration Sensor Module SKU: EZ-0089 ]]<br />
* [[ Pitaya Go IoT SKU: Z-0269 ]]<br />
* [[ Power-Over-Ethernet (PoE) HAT for RPi 4B/3B+ SKU: EP-0115 ]]<br />
<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ 8MM Camera module for Raspberr Pi SKU: ER-0021 ]]<br />
* [[ Gigabit USB-C PoE Splitter SKU:P-0005]]<br />
* [[ Gigabit USB-C PoE Splitter 48V to 5V for RPi 4B SKU:P-0006]]<br />
* [[ Pitaya go SKU: Z-0269 ]]<br />
* [[TFmini PLus Lidar Module（Distance measurement） SKU:Z-0231 ]]<br />
* [[ Raspberry Pi Zero/Zero W Camera Ribben Cable Wire(Gold finger) SKU: Z-0209 ]]<br />
* [[ Raspberry Pi night vision camera adjustable-focus module ER-0016 ]]<br />
* [[1602 Serial LCD Module Display SKU:Z-0234 ]]<br />
* [[2004 Serial LCD Module Display SKU:Z-0235 ]]<br />
* [[USB Isolator SKU:EP-0101 ]]<br />
* [[USB dongle for Raspberry Pi Zero/Zero W SKU:EP-0097 ]] <br />
* [[MicroBit Basic Extension Board Horizontal Version SKU: EP-0095 ]]<br />
* [[MicroBit Basic Extension Board Vertical Version SKU: EP-0096 ]]<br />
* [[TFmini Lidar Module（Distance measurement） SKU:EZ-0068 ]]<br />
* [[Raspberry Pi GPIO Breakout Board Big Black (T-Type) SKU: EP-0094 ]]<br />
* [[Raspberry Pi GPIO Breakout Board V1.1(T-Type) SKU: K-0291 ]]<br />
* [[GeeekPi 1/2 Sized Breadboard SKU: EP-0091 ]]<br />
* [[GeeekPi 1/4 Sized Breadboard SKU: EP-0092 ]]<br />
* [[GeeekPi Full Sized Breadboard SKU: EP-0093 ]]<br />
* [[Pi Zero Enc28j60 Network Adapter Module SKU: EP-0088 ]]<br />
* [[UPS for Raspberry Pi 4B/3B+/3B SKU: EP-0114]]<br />
* [[UPS for Raspberry Pi 3B/3B+ SKU: EP-0100]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[USB Joystick controller Board SKU: EP-0080 ]]<br />
* [[Raspberry Pi LM75B temperature Sensor v1.0 SKU:EP-0031]]<br />
* [[Raspberry Pi Super Capacitor RTC(English)|Raspberry Pi Super Capacitor RTC]]<br />
* [[DS1307 RTC Module with BAT for Raspberry Pi SKU: EP-0059]]<br />
* [[Raspberry Pi Expansion Board(English)|Raspberry Pi Expansion Board]]<br />
* [[RPI-B+-GPIO-Triple(English)| RPI-B+-GPIO-Triple]]<br />
* [[Raspberry Pi Heatsink(English) | Raspberry Pi Heatsink]]<br />
* [[Raspberry Pi ADC-DAC Module(English) | Raspberry Pi ADC-DAC Module]]<br />
* [[USB Gamepad SKU: Z-0177 ]]<br />
* [[RPI B+ GPIO Reference Board SKU:EP-0021 ]]<br />
* [[RPI B+ Rectangle Extend Board SKU:EP-0020 ]]<br />
* [[RaspberryPi Downgrade(English)| RaspberryPi Downgrade]]<br />
* [[RaspberryPi B+ GPIO Reference Board(English)| RaspberryPi B+ GPIO Reference Board]]<br />
* [[RaspberryPi RS232 UART Board(English)| RaspberryPi RS232 UART Board]]<br />
* [[GPS Module SKU:EZ-0024]]<br />
* [[USB-Port-GPS Module SKU:EZ-0048]]<br />
* [[VGA666 Module For RPi SKU:EP-0073]]<br />
</td></tr></table><br />
<br />
==Case & Enclosure & Heat sink==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ Aluminum Alloy CNC Heat Sink without Fan for Raspberry Pi CM4 Module SKU: ZP-0111 ]]<br />
* [[ Aluminum Alloy CNC Heat Sink with Fan for Raspberry Pi CM4 Module SKU: ZP-0112 ]]<br />
* [[ Aluminum alloy CNC without fan Armor Case for Raspberry Pi 4B SKU: C-0027 ]]<br />
* [[ Armor lite heatsink with pwm fan for Raspberry Pi 4B SKU: ZP-0110 ]]<br />
* [[ Argon One Case V2 SKU: C-0023 ]]<br />
* [[ Poly+ Black Case for RPi 4B SKU: C-0025 ]]<br />
* [[ Low-profile ICE tower cooler (Type B) for RPi SKU: EP-0132 ]]<br />
* [[ Plastic Case Kit for RPi ZeroW/Zero SKU: K-0567 ]]<br />
* [[ Argon ONE M.2 Case SKU: C-0022 ]]<br />
* [[ NANOSOUND 1 SKU: C-0020]]<br />
* [[ Acrylic Case for NT68676 Controller Board SKU: ZP-0105 ]]<br />
* [[ Nes3Pi SKU: ZP-0103 ]]<br />
* [[ NesPi 4 Case For RPi 4B SKU: C-0015 ]]<br />
* [[ Rack Tower Ultimate (12Layer) SKU: ZP-0108 ]]<br />
* [[ Rack Tower Pro SKU: ZP-0089 ]]<br />
* [[ Jetson Nano Fan kit SKU: F-0003 ]]<br />
* [[ Acrylic Set-top box kit for RPi 4B SKU: ZP-0102 ]]<br />
* [[ Acrylic case for Jetson Nano SKU: ZP-0101 ]]<br />
* [[ Transparent Layer acrylic bracket shell SKU: ZP-0040 ]]<br />
* [[ Brown layer acrylic bracket shell SKU: ZP-0039 ]]<br />
* [[ Black Low-Profile ICE Cooling Fan For RPi SKU: EP-0122 ]]<br />
* [[ Jetson Nano Metal Case(B01Version) SKU: ZP-0100 ]]<br />
* [[ Icon Case For RPi 4B SKU: ZP-0099]]<br />
* [[ Power Button For RPi SKU: EP-0077]]<br />
* [[ Pi Supply & USB HUB SKU: EP-0078]]<br />
* [[ Pi Supply & USB HUB Without Battery SKU: EP-0079]]<br />
* [[ RPI 5MP CSI Camera SKU: ER-0011]]<br />
* [[ ESP32 Module SKU: EZ-0059 ]]<br />
* [[ Brand new 2.4G wireless mini keyboard with mouse touchpad SKU: Z-0153 ]]<br />
* [[ RPI-ADS1115-ADC-Module SKU:EP-0076]]<br />
* [[ Acrylic Raspberry Pi set-top box kit SKU: ZP-0098 ]]<br />
* [[ 6-Layer Acrylic Cluster framework For Raspberry Pi SKU: ZP-0092 ]]<br />
* [[ Acrylic holder for RPi 4B camera SKU: ZP-0093 ]]<br />
* [[ Argon ONE Aluminum case with Fan for RPi 4B SKU: C-0008 ]]<br />
* [[ NEO Case SKU: C-0006 ]]<br />
* [[ Metal Case for RPi 4B SKU: C-0003 ]]<br />
* [[ Aluminum Case for RPi 4B with 3510 fan SKU:ZP-0090 ]]<br />
* [[ Aluminum Case for RPi 4B with 2510 fan SKU:ZP-0091 ]]<br />
* [[ ABS Case for RPi 4B SKU: C-0005 ]]<br />
* [[ Metal Case for RPi 4B SKU: C-0004 ]]<br />
* [[ Rack Tower SKU: ZP-0088 ]]<br />
* [[ Metal Case For Low-Profile ICE Tower Cooler SKU: ZP-0087 ]] <br />
* [[ Plastic Case for RPi 4B SKU: C-0002 ]]<br />
* [[ ABS Case For RPi 4B SKU: C-0001 ]]<br />
* [[ Low Profile Ice Tower Cooler SKU: EP-0112 ]]<br />
* [[ Nes4Pi SKU: ZP-0086 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ ABS and Acrylic case with 4010 fan for RPi 4B SKU: ZP-0079 ]]<br />
* [[ 9-Layer Acrylic case (Black & Bigfan) for RPi 4B SKU: ZP-0078 ]]<br />
* [[ 9-Layer Acrylic case (Black) for RPi 4B SKU: ZP-0068 ]]<br />
* [[ Aluminum Case with Suspension Fan for RPi 4B SKU: Z-0278 ]]<br />
* [[ 9-Layer Acrylic case for RPi 4B SKU: ZP-0085 ]]<br />
* [[ ICE Tower Cooling Fan For Jetson Nano SKU: EP-0113 ]]<br />
* [[ ICE Tower Cooling Fan Black SKU: EP-0111 ]]<br />
* [[ E Type ABS Case for RPi 4B SKU: ZP-0081 ]]<br />
* [[ L Type ABS Case for RPi 4B SKU: ZP-0082 ]]<br />
* [[ Y Type Aluminum Case for RPi 4B SKU: ZP-0083 ]]<br />
* [[ ABS Electrical Box for RPi 4B SKU: Z-0272 ]]<br />
* [[ ABS Electrical Box for RPi 3B/3B+ SKU: C-0007 ]]<br />
* [[ ABS Buckle Case for RPi 4B SKU: Z-0273 ]]<br />
* [[ 5-layer acrylic case for RPi 4B SKU: ZP-0080 ]]<br />
* [[ Armor Case For RPi 4B with Dual Fan SKU: ZP-0077 ]]<br />
* [[ Armor Case For RPi 4B/3B/3B+ without Fan SKU: ZP-0074 ]]<br />
* [[ New ABS H-Type Case for Raspberry Pi 4B SKU: ZP-0075 ]]<br />
* [[ ABS experiment holder platform SKU: ZP-0073 ]]<br />
* [[ 9 Layers Acrylic Case with 4010 Fan SKU: ZP-0076 ]]<br />
* [[ 9 Layers Acrylic Case with Fan SKU: ZP-0067 ]]<br />
* [[ Single layer Acrylic Case with transparent fan SKU: ZP-0066 ]]<br />
* [[ Brown single layer Acrylic Case with fan SKU: ZP-0065 ]]<br />
* [[ Square radiator for Raspberry Pi 4B SKU: ZP-0038 ]]<br />
* [[ Iron Case for Jetson Nano SKU: ZP-0072 ]]<br />
* [[ Aluminum Heat Sink Pack for Raspberry Pi 4B SKU: Z-0266 ]]<br />
* [[ Metal Case for RPi 4B with 4010 Fan SKU: ZP-0070 ]]<br />
* [[ Metal Case for RPi 4B (Silver & Black) SKU: ZP-0071 ]]<br />
* [[ Metal Case for RPi 4B (Silver & Black) SKU: Z-0264 ]]<br />
* [[ ICE-Tower CPU Cooling Fan for Raspberry Pi SKU: EP-0107 ]]<br />
* [[ Armor Case For RPi 3B+ without Fan SKU: ZP-0051 ]]<br />
* [[Armor Case for Raspberry Pi 3A+ SKU: Z-0237 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Acrylic Shell With Fan Guard For RPi SKU: ZP-0025 ]]<br />
* [[Acrylic Shell With Fan Guard For RPi (Brown Color) SKU: ZP-0069 ]]<br />
* [[3510 Version Extreme Cooling Fan Kit For Raspberry Pi 4B/3B/3B+ SKU: ZP-0042]]<br />
* [[New version Copper Heat Sink SKU: Z-0185]]<br />
* [[Ultimate Cooling Fan Kit For Raspberry Pi 4B/3B+/3B/2B/B+ SKU: ZP-0037]]<br />
* [[ABS case with fan and heat sink for Raspberry Pi 3B+/3B/2B/B+(Black/White) SKU: Z-0183]] <br />
* [[Raspberry Pi 3B white acrylic case SKU: Z-0127]]<br />
* [[Raspberry Pi 3 Enclosure with heat sinks SKU: K-0172]]<br />
* [[ USB HUB Power Supply for Raspberry Pi Double Layer Acrylic Rack SKU: K-0178 ]]<br />
* [[ Black ABS enclosure with screwdriver for Raspberry Pi SKU: Z-0157 ]]<br />
* [[4-layer-Transparent-Acrylic-Case-Clear-Shell-Enclosure-for-Raspberry-Pi-3-Model-B/2B/B+ SKU: ZP-0024]]<br />
* [[Micro-HDMI-to-Standard-HDMI-Male-Cable-4K-Pi4B SKU:L-0030]]<br />
* [[ Ultimate Cooling Fan Kit for Raspberry Pi 3/2/B+ SKU: ZP-0029 ]]<br />
* [[RPi ABS Case SKU: ZP-0049 ]]<br />
* [[Armor Case For RPi 3B SKU: Z-0193]]<br />
* [[Armor Case For RPi 3B+ SKU: Z-0208 ]]<br />
* [[10 Layers Acrylic Case for Raspberry Pi 3B+/3B/2B/B+ SKU: Z-0190]]<br />
* [[Raspberry Pi 3 Aluminum alloy Case SKU: Z-0184]]<br />
</td><br />
</tr></table><br />
<br />
==Cooling Accessories==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<pre> EOL stands for "End of Life", means this product will not produce any more</pre><br />
* [[ 5V Mini Cooling Fan for Raspberry Pi SKU: F-0010 ]]<br />
* [[ MINIWARE MHP30 Mini Hot Plate Preheater SKU: D-0022 ]]<br />
* [[ 4010 24V Blue Backlight Fan SKU: F-0008 ]]<br />
* [[ 5V DVR Mainboard Fan SKU: F-0007 ]]<br />
* [[ 4010 Blower SKU: F-0005 ]]<br />
* [[ 5015 Blower SKU: F-0006 ]]<br />
* [[DC 12V Brushless Blue light Fan SKU: F-0001 ]]<br />
* [[DC 12V Brushless RGB light Fan SKU: F-0002 ]]<br />
</td></tr></table><br />
<br />
==Electronic Engineer Tools==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ DT71 Mini digital tweezers SKU: T-0022 ]]<br />
* [[ Desoldering Iron Kit SKU:T-0021 ]]<br />
* [[ TS80P More-US SKU:T-0019 ]]<br />
* [[ TS80P kit SKU:T-0015 ]]<br />
* [[ TS100 kit SKU:T-0016 ]]<br />
* [[ Tin Lead Rosin Core Solder Wire for Electrical Soldering (1.0mm/0.04Inch) SKU: T-0017 ]]<br />
* [[ Tin Lead Rosin Core Solder Wire for Electrical Soldering (0.8mm/0.03Inch) SKU: T-0018 ]]<br />
* [[ DS213 mini oscilloscope SKU: Z-0241 ]]<br />
</td></tr></table><br />
<br />
==Displays==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<pre> EOL stands for "End of Life", means this product will not produce any more</pre><br />
* [[ 2.13 inch E-paper (BRW) SKU: EP-0133 ]]<br />
* [[0.91 Inch OLED Display SKU: EP-0119 ]]<br />
* [[PiOLED (0.91 Inch OLED Module) SKU: S-0007 ]]<br />
* [[0.91 Inch OLED Module SKU: S-0006]]<br />
* [[0.96 Inch OLED Module SKU: S-0005]]<br />
* [[0.91 Inch OLED Module SKU: EP-0060]]<font color=red>EOL</font><br />
* [[0.96 Inch OLED Module SKU:EP-0049]] <font color=red>EOL</font><br />
* [[52Pi-BPi LCD 1602 Module SKU:EP-0045]]<br />
* [[RGB LCD1602 SKU:EP-0058]]<br />
* [[RPI-RGB-LED-Matrix SKU:EP-0075]]<br />
* [[Raspberry Pi 2.2 Inch GPIO display(without touch screen) SKU:EP-0062]]<br />
* [[Raspberry Pi 2.4 Inch GPIO touch screen SKU:EP-0063]]<br />
* [[TFT28 Display + Touch Panel + NoPCB SKU:EP-0066 ]]<br />
* [[TFT28 Display + Touch Panel + PCB SKU:EP-0065 ]]<br />
* [[5-Inch-800x480-HDMI-TFT-LCD-Touch-Screen SKU:Z-0053]]<br />
* [[5-Inch-800x480-HDMI-GPIO-Touch-Screen SKU:EP-0072]]<br />
* [[5-Inch-800x480-Capacitive-Touch-Screen SKU: EP-0081 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ 7 inch 1024x600 Screen and driver board with Amplifier and Two speakers Kit SKU: EP-0089]]<br />
* [[7-Inch-1024x600 Capacitive Touch Screen (Extend Two USB HOST Port) with 720P Camera SKU: EP-0087 ]]<br />
* [[7-Inch-1024x600 Capacitive Touch Screen (Extend Two USB HOST Port) SKU: EP-0085 ]]<br />
* [[7-Inch-1024x600 Capacitive Touch Screen DIY Kit SKU: EP-0084]]<br />
* [[7-Inch-1024x600 Capacitive Touch Panel DIY Kit SKU: EP-0082]]<br />
* [[7-Inch-1024x600 Display Kit (with Touch Screen) SKU:Z-0017]]<br />
* [[7-Inch-1024x600 Display Kit (without Touch Screen) SKU:Z-0051]]<br />
* [[7-Inch-1024x600 Monitor SKU:K-0106 ]]<br />
* [[7-Inch-800x480 Display Kit(without Touch Screen) SKU:Z-0111]]<br />
* [[7-Inch-1280x800 Display Kit(without Touch Screen) SKU:Z-0112]]<br />
* [[7-Inch-800x480 Monitor SKU:K-0101]]<br />
* [[7-Inch-1280*800 Monitor SKU:K-0102]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[15.6 Inch 1920x1080 FHD Display SKU: S-0003 ]]<br />
* [[10.1 Inch 1280x800 Display Kit(without Touch Screen) SKU: S-0001 ]]<br />
* [[10.1-Inch-1024x600 Display Kit (without Touch Screen) SKU:Z-0113]]<br />
* [[10.1-Inch-1366x768 Display Kit(without Touch Screen) SKU:Z-0114]]<br />
* [[ 10.1-Inch-1280x800 Display Kit(Without Touch Screen) SKU:Z-0143]]<br />
* [[10.1-Inch-1366x768 Monitor SKU:K-0103]]<br />
* [[Super Luxury 10.1 LCD Television SKU: K-0104]]<br />
</td></tr></table><br />
<br />
==Power Supply==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ Milestone wireless charger SKU: P-0017 ]]<br />
* [[5V-3A EU-Standard with switch SKU:P-0007]] <br />
* [[5V-3A US-Standard with switch SKU:P-0008]] <br />
* [[5V-3A UK-Standard with switch SKU:P-0009]] <br />
* [[5V-3A UK-Standard SKU:P-0004]] <font color=red>EOL</font><br />
* [[5V-3A EU-Standard SKU:P-0003]] <font color=red>EOL</font><br />
* [[5V-3A US-Standard SKU:P-0002]] <font color=red>EOL</font><br />
* [[5V-4A Travel Adapter SKU:P-0001]]<br />
* [[5V-2.5A-AU-Standard SKU:Z-0132]]<br />
* [[5V-2.5A-UK-Standard SKU:Z-0133]]<br />
* [[5V-2.5A-US-Standard SKU:Z-0121]]<br />
* [[5V-2.5A-EU-Standard SKU:Z-0097]]<br />
* [[5V-2.5A-EU/US/UK/AU-Plug SKU:Z-0136]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[US-Standard-With-Power-Switch-5V-2.5A SKU:Z-0147]]<br />
* [[EU-Standard-With-Power-Switch-5V-2.5A SKU:Z-0148]]<br />
* [[AU-Standard-With-Power-Switch-5V-2.5A SKU:Z-0149]]<br />
* [[UK-Standard-With-Power-Switch-5V-2.5A SKU:Z-0150]]<br />
* [[Banana Pi US-standard Power Supply SKU: Z-0154]]<br />
* [[Banana Pi EU-standard Power Supply SKU: Z-0155]]<br />
* [[MicroUSB Cable with LCD Voltage/Current Display SKU: L-0026 ]]<br />
* [[MicroUSB Cable with LCD Voltage/Current Display(Support IPhone) SKU: L-0027 ]]<br />
</td></tr></table><br />
<br />
==Raspberry Pi Kits==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ Raspberry Pi Pico Starter Kit SKU: K-0581 ]]<br />
* [[ Metal Alloy Shell with Silver/Black Low-Profile ICE tower Cooler for RPi 4B SKU: K-0522 ]]<br />
* [[ 220PCS Standoffs M2.5 Brass Spacer Kit for Raspberry Pi SKU: T-0008 ]]<br />
* [[RPi 4B Starter Kit SKU: K-0512 ]]<br />
* [[ABS Holder Kit For RPi & Arduino SKU: K-0502 ]]<br />
* [[ ABS Case for RPi 4B with 3.5 Inch Resistive Touch Screen SKU: K-0403 ]]<br />
* [[Arcade Game Machine DIY Kits with Joysticks(Double Players) SKU: K-0167 ]]<br />
* [[Arcade Game Machine DIY Kits without Joysticks (Single Player) SKU: K-0168 ]]<br />
* [[Arcade Game Machine DIY Kits without Joysticks (Double Players) SKU: K-0169 ]]<br />
* [[7 inch 1024x600 Capacitive Touch Screen(Extend Two USB Hosts) with 720P Camera and Acrylic Case Kit SKU: K-0259 ]]<br />
* [[5 inch Capacitive touch screen & Acrylic Case Kit SKU: K-0238 ]]<br />
<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Retro Game Kit (Single Player) SKU: K-0185]]<br />
* [[Retro Game Kit (Double Players) SKU: K-0186 ]]<br />
* [[Starter Kit SKU: Z-0142]]<br />
* [[Raspberry Pi Complete kit SKU: K-0111]]<br />
* [[Raspberry Pi 3B Overlays Application Kit SKU: Z-0144]]<br />
* [[Raspberry Pi Retro Gamepads Kit with 10.1 inch Monitor SKU: K-0171]]<br />
* [[Raspberry Pi RetroPie Game Kit (with 5 inch GPIO TouchScreen & GamePad x2 ) SKU: K-0174]]<br />
* [[Raspberry Pi RetroPie Game Kit with 2.4GHz wireless GamePad x2]]<br />
* [[Raspberry Pi Acrylic DIY Retro Game Arcade Kit SKU:K-0180]]<br />
</td></tr></table><br />
<br />
==Official Support Products==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Raspberry Pi official 7-Inch-Touch-Screen SKU:Z-0104]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Banana Pi official 7-Inch-Capacitance-Screen SKU:Z-0088]]<br />
</td></tr></table><br />
==X-Series Expansion Board==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<b><font color=red>New Products 2020.4.21 updated</font></b><br><br />
* [[ X872 SKU: EZ-0094 ]]<br />
* [[ X728 SKU: EZ-0095 ]]<br />
* [[ X835 SKU: EZ-0090 ]]<br />
* [[ X856 SKU: EZ-0087 ]]<br />
* [[ X828 SKU: EZ-0088 ]]<br />
* [[ X725 SKU: EZ-0086 ]]<br />
* [[ X855 SKU: EZ-0083 ]]<br />
* [[ X825 SKU: EZ-0082 ]]<br />
* [[ X822 SKU: EZ-0076 ]]<br />
* [[ X852 SKU: EZ-0077 ]]<br />
* [[ X860 SKU: EZ-0078 ]]<br />
* [[ X870 SKU: EZ-0079 ]]<br />
* [[ X735 SKU: EZ-0080 ]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
<b><font color=Green>Old Products 2018.6.6 updated</font></b><br><br />
* [[ X720 SKU: EZ-0072]]<br />
* [[ X730 SKU: EZ-0073]]<br />
* [[ X830 SKU: EZ-0064]]<br />
* [[ X105 SKU: EZ-0008]]<br />
* [[ X200 SKU: EZ-0002]]<br />
* [[ X300 SKU: EZ-0003]]<br />
* [[ X205 SKU: EZ-0046]]<br />
* [[ X400 SKU: EZ-0044]]<br />
* [[ X600 SKU:EZ-0045]]<br />
* [[ X3000 SKU:EZ-0051]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[ X6000P-7.1CH DIY Kits SKU:EZ-0052]]<br />
* [[ X5000P Raspberry Pi HiFi Sound Card SKU:EZ-0053]]<br />
* [[ X4000P SKU:EZ-0054]]<br />
* [[ X4000K DIY Kits SKU:EZ-0055]]<br />
* [[ X6000K-8.0CH DIY Kits SKU:EZ-0056]]<br />
* [[ X5000K DIY Kits SKU:EZ-0057]]<br />
* [[ X1000K DIY Kits SKU:EZ-0058]]<br />
</td></tr></table><br />
===X series Acrylic Case===<br />
* [[ Acrylic Case for X725 SKU: ZP-0096 ]]<br />
* [[ Acrylic Case for X825 SKU: ZP-0097 ]]<br />
<br />
==Operation System Card==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[OctoPrint]]<br />
* [[Noobs]]<br />
* [[Raspbian]]<br />
* [[DietPi]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[Batocera]]<br />
* [[RetroPie]]<br />
* [[Ubuntu Mate 16.04]]<br />
* [[OSMC]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[5-inch-GPIO-touch-screen-Based-on-Raspbian]]<br />
* [[Windows 10 IOT R2 (Red Stone) 16GB]]<br />
</td></tr></table><br />
<br />
==52Pi Expand Modules ( End Of Life )==<br />
<table border="0" cellpadding="10" style="width: 100%;"><br />
<tr><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[RPI T-Cobbler GPIO Extend Board With Level shifting SKU:EP-0014]]<br />
* [[RPI T-Cobbler GPIO Extend Board SKU:EP-0003]]<br />
* [[RPI 16x2 LCD+Keypad Kit SKU:Z-0019]]<br />
* [[RPI B+ to B GPIO Downgrade Board SKU:EP-0027 ]]<br />
* [[RPI I2C GPIO Extend Board SKU:EP-0013]]<br />
* [[RPI AD/DA Extend Board SKU:EP-0022]]<br />
* [[RPI B GPIO Reference Board SKU:EP-0018]]<br />
* [[RPI GPIO Triple Extend Board SKU:EP-0012]]<br />
* [[RPI GPIO Rectangle Extend Board SKU:EP-0011]]<br />
* [[RPI I2C Logic Level Converter SKU:EP-0026]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[RPI Infinity cascade IO expand Module SKU:EP-0028]]<br />
* [[RPI Arduino Board SKU:EP-0023]]<br />
* [[RPI RTC Module SKU:EP-0016]]<br />
* [[RPI B TF TO SD SKU:EP-0032]]<br />
* [[RPI UART Extend Board SKU:EP-0017]]<br />
* [[RPI B+ Prototyping Pi Plate Board SKU:EP-0042]]<br />
* [[RPI B+ GPIO Triple Extend Board SKU:EP-0029]]<br />
* [[RPI B Prototyping Pi Plate Board SKU:EP-0004]]<br />
</td><br />
<td style="text-align: left; vertical-align: top; width: 32%;"><br />
* [[RPI HAT Breakout Mini Kit SKU:EP-0056]]<br />
* [[RPI HAT Prototype Module SKU:EP-0057]]<br />
* [[RPI T Type Extension Board SKU:EP-0046]] <br />
</td></tr></table><br />
<br />
===Documentation===<br />
----<br />
<pre>Some simple guides to setting up the software on your Raspberry Pi.<br />
Beginners should start with NOOBS, which gives the user a choice of operating system from the standard distributions.<br />
The recommended distribution for normal use is Raspbian. <br />
Alternatives are available, such as LibreELEC (Kodi media centre) or Arch Linux.<br />
</pre><br />
* Installing operation system on your Raspberry Pi <br />
** [[NOOBS]]<br />
** [[Installing images]]<br />
** [[SD Cards]]</div>TaterLihttps://wiki.52pi.com/index.php?title=Aluminum_Case_for_Jetson_Nano_SKU:_ZP-0072&diff=10074Aluminum Case for Jetson Nano SKU: ZP-00722021-04-14T02:56:47Z<p>TaterLi: TaterLi moved page Aluminum Case for Jetson Nano SKU: ZP-0072 to Iron Case for Jetson Nano SKU: ZP-0072: correct info</p>
<hr />
<div>#REDIRECT [[Iron Case for Jetson Nano SKU: ZP-0072]]</div>TaterLihttps://wiki.52pi.com/index.php?title=ZP-0072&diff=10073ZP-00722021-04-14T02:56:47Z<p>TaterLi: TaterLi moved page Aluminum Case for Jetson Nano SKU: ZP-0072 to Iron Case for Jetson Nano SKU: ZP-0072: correct info</p>
<hr />
<div>==Iron Case for Jetson Nano==<br />
[[File:Jetsoncase01.jpg|right|300px]]<br />
<br />
==Description==<br />
This is an all-metal functional enclosure specifically tailored for Jetson Nano.<br><br />
Its honeycomb vents reduce the heat generated by your device while it’s performing neural network training or running machine vision programs. <br><br />
And the internal super quiet fan will be good auxiliary heat dissipation, beautiful workmanship of the outer casing, perfect interface opening for each connector.<br><br />
In addition, in order to consider the equipment that Jetson Nano may use, such as the camera, it specially provide the camera holder for Jetson Nano.<br><br />
The metal bracket makes your visual neural network learning device more convenient to use. <br><br />
At the same time, it provides two perfect wireless network expansion antenna interfaces for the Jetson Nano on the outer casing, so that you can avoid Metal shielding interference when it accessing network via extend network interface card, such as intel network card.<br><br />
A switch button with backlight is provided on the front of the panel. <br><br />
In order to prevent mistakenly touching, a reset button is provided on the back of the panel. <br><br />
Four anti-skid rubber pads are added to the bottom of the case to prevent skid.<br />
<br />
==Features==<br />
* Easy to assemble<br />
* Camera holder<br />
* Extended Antenna Base for the network interface card<br />
* Honeycomb vents style<br />
* Super quiet fan<br />
* Good quality <br />
* Anti-skid rubber pads<br />
<br />
==Gallery==<br />
{|<br />
|[[File:Jetsoncase01.jpg|left|320px]]<br />
|[[File:Jetsoncase02.jpg|none|320px]]<br />
|[[File:Jetsoncase03.jpg|none|320px]]<br />
|}<br />
{|<br />
|[[File:Jetsoncase04.jpg|left|320px]]<br />
|[[File:Jetsoncase05.jpg|none|320px]]<br />
|[[File:Jetsoncase01.jpg|none|320px]]<br />
|}<br />
<br />
==How to assemble==<br />
* 1.Fix the 4020 fan with long screws to Jetson Nano on the top of heat sink, and connect the cable to Jetson Nano’s FAN J15.Fixed the Reset button and power on/off button on the case, and then fix Jetson Nano to the case.<br />
* 2.Add Jumper caps on J40 Pin7 and Pin8 to disable auto power-on and connect Reset button to Pin 5 and 6, connect power-on button to Pin 1 and 2 as following picture:<br />
J40 Button Header<br />
[[File:Jetsonnano J40Button pin definitions.png|left|800px]]<br />
<br style="clear:both;"><br />
[[File:ZP-0072-Jeson-Nano 8.jpg|left | 800px]]<br />
<br style="clear:both;"><br />
* 3.Connect the pre-installed fan to Jetson Nano’s GPIO, red wire connects to 5V, black wire connects to GND.<br />
[[File:ZP-0072-Jeson-Nano 7.jpg|left | 800px]]<br />
<br style="clear:both;"><br />
* 4.(Optional) Fixed the camera with M2.0*5 screws and put the acrylic washer between camera and the mounting brackets.<br />
[[File:ZP-0072-Jeson-Nano 10.jpg |left | 800px]]<br />
<br style="clear:both;"><br />
* 5.(Optional) Fixed the antenna to case and connect to the network interface card (NIC).<br />
** Step 1. Remove the two screws on Jetson Nano, detach the Jetson Nano and remove the screw in the middle of the board.\<br />
** Step 2. Connect the extension antenna cable to wireless interface card on IPEX connector, tighten the nut and washer to iron case to each SMA connector, and then put the wireless interface card into the M.2 socket, screw it tightly.<br />
** Step 3. Insert the Jetson Nano into the socket and make sure the clamps lock it in and then screw it again.<br />
** Step 4. Connect the antennas to the extension antenna cable.<br />
{|<br />
|[[File:WifiA1.jpg|left|320px]]<br />
|[[File:WifiA2.jpg|none|320px]]<br />
|[[File:WifiA3.jpg|none|320px]]<br />
|}<br />
{|<br />
|[[File:Wifia10.jpg|left|500px]]<br />
|[[File:Wifia11.jpg|none|500px]]<br />
|}<br />
<br />
==Package Include==<br />
[[ File:ZP-0072-Jeson-Nano铝合金外壳4.jpg|left | 500px]]<br />
<br style="clear:both;"><br />
<br />
==Keywords==<br />
* jetson nano case, case for jetson nano, iron case, quiet fan, fan, heatsink, honycomb vent, jetson nano<br />
<br />
==FAQ==</div>TaterLihttps://wiki.52pi.com/index.php?title=ZP-0072&diff=10072ZP-00722021-04-14T02:55:56Z<p>TaterLi: </p>
<hr />
<div>==Iron Case for Jetson Nano==<br />
[[File:Jetsoncase01.jpg|right|300px]]<br />
<br />
==Description==<br />
This is an all-metal functional enclosure specifically tailored for Jetson Nano.<br><br />
Its honeycomb vents reduce the heat generated by your device while it’s performing neural network training or running machine vision programs. <br><br />
And the internal super quiet fan will be good auxiliary heat dissipation, beautiful workmanship of the outer casing, perfect interface opening for each connector.<br><br />
In addition, in order to consider the equipment that Jetson Nano may use, such as the camera, it specially provide the camera holder for Jetson Nano.<br><br />
The metal bracket makes your visual neural network learning device more convenient to use. <br><br />
At the same time, it provides two perfect wireless network expansion antenna interfaces for the Jetson Nano on the outer casing, so that you can avoid Metal shielding interference when it accessing network via extend network interface card, such as intel network card.<br><br />
A switch button with backlight is provided on the front of the panel. <br><br />
In order to prevent mistakenly touching, a reset button is provided on the back of the panel. <br><br />
Four anti-skid rubber pads are added to the bottom of the case to prevent skid.<br />
<br />
==Features==<br />
* Easy to assemble<br />
* Camera holder<br />
* Extended Antenna Base for the network interface card<br />
* Honeycomb vents style<br />
* Super quiet fan<br />
* Good quality <br />
* Anti-skid rubber pads<br />
<br />
==Gallery==<br />
{|<br />
|[[File:Jetsoncase01.jpg|left|320px]]<br />
|[[File:Jetsoncase02.jpg|none|320px]]<br />
|[[File:Jetsoncase03.jpg|none|320px]]<br />
|}<br />
{|<br />
|[[File:Jetsoncase04.jpg|left|320px]]<br />
|[[File:Jetsoncase05.jpg|none|320px]]<br />
|[[File:Jetsoncase01.jpg|none|320px]]<br />
|}<br />
<br />
==How to assemble==<br />
* 1.Fix the 4020 fan with long screws to Jetson Nano on the top of heat sink, and connect the cable to Jetson Nano’s FAN J15.Fixed the Reset button and power on/off button on the case, and then fix Jetson Nano to the case.<br />
* 2.Add Jumper caps on J40 Pin7 and Pin8 to disable auto power-on and connect Reset button to Pin 5 and 6, connect power-on button to Pin 1 and 2 as following picture:<br />
J40 Button Header<br />
[[File:Jetsonnano J40Button pin definitions.png|left|800px]]<br />
<br style="clear:both;"><br />
[[File:ZP-0072-Jeson-Nano 8.jpg|left | 800px]]<br />
<br style="clear:both;"><br />
* 3.Connect the pre-installed fan to Jetson Nano’s GPIO, red wire connects to 5V, black wire connects to GND.<br />
[[File:ZP-0072-Jeson-Nano 7.jpg|left | 800px]]<br />
<br style="clear:both;"><br />
* 4.(Optional) Fixed the camera with M2.0*5 screws and put the acrylic washer between camera and the mounting brackets.<br />
[[File:ZP-0072-Jeson-Nano 10.jpg |left | 800px]]<br />
<br style="clear:both;"><br />
* 5.(Optional) Fixed the antenna to case and connect to the network interface card (NIC).<br />
** Step 1. Remove the two screws on Jetson Nano, detach the Jetson Nano and remove the screw in the middle of the board.\<br />
** Step 2. Connect the extension antenna cable to wireless interface card on IPEX connector, tighten the nut and washer to iron case to each SMA connector, and then put the wireless interface card into the M.2 socket, screw it tightly.<br />
** Step 3. Insert the Jetson Nano into the socket and make sure the clamps lock it in and then screw it again.<br />
** Step 4. Connect the antennas to the extension antenna cable.<br />
{|<br />
|[[File:WifiA1.jpg|left|320px]]<br />
|[[File:WifiA2.jpg|none|320px]]<br />
|[[File:WifiA3.jpg|none|320px]]<br />
|}<br />
{|<br />
|[[File:Wifia10.jpg|left|500px]]<br />
|[[File:Wifia11.jpg|none|500px]]<br />
|}<br />
<br />
==Package Include==<br />
[[ File:ZP-0072-Jeson-Nano铝合金外壳4.jpg|left | 500px]]<br />
<br style="clear:both;"><br />
<br />
==Keywords==<br />
* jetson nano case, case for jetson nano, iron case, quiet fan, fan, heatsink, honycomb vent, jetson nano<br />
<br />
==FAQ==</div>TaterLihttps://wiki.52pi.com/index.php?title=RTC_EoF-001&diff=8310RTC EoF-0012020-04-22T03:37:26Z<p>TaterLi: /* DT Overlays Used */</p>
<hr />
<div>=Raspberry Pi RTC Module With Battery=<br />
==Description==<br />
This RTC module use DS3231 as its Real-Time Clock chip which has build-in crystal oscillator. This RTC module communicates with Raspberry Pi through I2C bus.DS3231 is a low power consumer RTC chip and whose back up supply is a 0.2uF Super-Capacitor,which can keep work for a week at least after power down<br />
<br>[[Image:CAP RTC.jpg|center|400px]]<br />
==Compatibility List==<br />
* Compatibility<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Platform !! Super Capacitor RTC !! Notes<br />
|-<br />
|-<br />
|Raspberry Pi 4 Model B || √ ||<br />
|-<br />
|Raspberry Pi 3 Model B Plus|| √ ||<br />
|-<br />
|Raspberry Pi zero || √||<br />
|-<br />
| Raspberry Pi zero W || √||<br />
|-<br />
|Raspberry Pi 3 Model B|| √||<br />
|-<br />
|Raspberry Pi 2 Model B|| √||<br />
|-<br />
|Raspberry Pi Model B+|| √|| <br />
|-<br />
|}<br />
<br />
==Technical Details==<br />
{| width="998" cellspacing="0" cellpadding="0" border="1" <br />
|-<br />
! align="center" scope="col" style="width: 40%" | Type<br />
! align="center" scope="col" | value<br />
<br />
|-<br />
| align="center" scope="row" | Work Voltage<br />
| align="center" | 5V<br />
<br />
|-<br />
| align="center" scope="row" | Weight<br />
| align="center" | 4.35g<br />
|-<br />
|align="center" scope="row" | Maximum Current<br />
| align="center" | 1.5mA<br />
|-<br />
| align="center" scope="row" | VBAT Current<br />
| align="center" | 800nA<br />
|-<br />
| align="center" scope="row" | work temprature<br />
| align="center" | 0～+50℃<br />
|-<br />
| align="center" scope="row" | Crystal Oscilator <br />
| align="center" | Epson 20 ppm <br />
|-<br />
| align="center" scope="row" | scale<br />
| align="center" | 22x26x18.6(mm)<br />
|-<br />
| align="center" scope="row" | Battery<br />
| align="center" | CR1220<br />
|-<br />
| align="center" scope="row" | RTC chip<br />
| align="center" | DS3231 <br />
|-<br />
| align="center" scope="row" | mount hole<br />
| align="center" | 2*5 Stacking Header<br />
|}<br />
<br />
==Overview==<br />
<br />
==Schematic==<br />
[[Image:RTC_CCAP01.png|700px]]<br />
<br />
==LCD module scale==<br />
<br>[[Image:RTC CCAP02.png|700px]]<br />
<br />
==DT Overlays Used==<br />
With DT enabled, this becomes a line in config.txt:<br />
<br />
dtoverlay=i2c-rtc ds3231<br />
<br />
It can adds support for a number of I2C Real Time Clock devices<br />
<br />
==Learn==<br />
*Type in [sudo raspi-config] set up raspberry pi and prepare to enable i2c interface<br />
<br>[[Image:RTC_tech02.png|700px]]<br />
*select Advanced Options <br />
<br>[[Image:RTC_tech03.png|700px]]<br />
*select I2c <br />
<br>[[Image:RTC_tech04.png|700px]]<br />
*select yes enable I2C <br />
<br>[[Image:RTC_tech05.png|700px]]<br />
*type in [sudo vim.tiny /etc/modules] to open file modules<br />
<br>[[Image:RTC_tech06.png|700px]]<br />
*add i2c-dev device like picture below<br />
<br>[[Image:RTC_tech07.png|700px]]<br />
*install i2c-tools ,type in [sudo apt-get install i2c-tools]<br />
<br>[[Image:RTC_tech08.png|700px]]<br />
*type in [sudo reboot] wait the raspberry pi restart ,Then type in [sudo i2cdetect –y 1], if RTC works ,it should be like picture below<br />
<br>[[Image:RTC_tech09.png|700px]]<br />
*Type in [sudo su –] change root user,then Type in [modprobe i2c-dev] to load I2C device<br />
<br>[[Image:RTC_tech10.png|700px]]<br />
*Type in [echo "ds1307 0x68" > /sys/class/i2c-adapter/i2c-1/new_device] add RTC to system <br />
<br>[[Image:RTC_tech11.png|700px]]<br />
*Then you can use “hwclock” command to use this RTC module<br />
If you want to know more about hwclock command you can type in “man hwclock” to get details<br />
A brief description like following:<br />
Command [hwclock –r] to get RTC time<br />
Command [hwclock -w]set the system time to RTC time <br />
Like following<br />
<br>[[Image:RTC_tech12.png|700px]]<br />
<br />
==Attachment==<br />
<div id="tech1"></div><br />
<br>[[media:DS3231.pdf|ds3231 date sheet]]</div>TaterLihttps://wiki.52pi.com/index.php?title=RTC_EoF-001&diff=8309RTC EoF-0012020-04-22T03:36:34Z<p>TaterLi: /* Learn */</p>
<hr />
<div>=Raspberry Pi RTC Module With Battery=<br />
==Description==<br />
This RTC module use DS3231 as its Real-Time Clock chip which has build-in crystal oscillator. This RTC module communicates with Raspberry Pi through I2C bus.DS3231 is a low power consumer RTC chip and whose back up supply is a 0.2uF Super-Capacitor,which can keep work for a week at least after power down<br />
<br>[[Image:CAP RTC.jpg|center|400px]]<br />
==Compatibility List==<br />
* Compatibility<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Platform !! Super Capacitor RTC !! Notes<br />
|-<br />
|-<br />
|Raspberry Pi 4 Model B || √ ||<br />
|-<br />
|Raspberry Pi 3 Model B Plus|| √ ||<br />
|-<br />
|Raspberry Pi zero || √||<br />
|-<br />
| Raspberry Pi zero W || √||<br />
|-<br />
|Raspberry Pi 3 Model B|| √||<br />
|-<br />
|Raspberry Pi 2 Model B|| √||<br />
|-<br />
|Raspberry Pi Model B+|| √|| <br />
|-<br />
|}<br />
<br />
==Technical Details==<br />
{| width="998" cellspacing="0" cellpadding="0" border="1" <br />
|-<br />
! align="center" scope="col" style="width: 40%" | Type<br />
! align="center" scope="col" | value<br />
<br />
|-<br />
| align="center" scope="row" | Work Voltage<br />
| align="center" | 5V<br />
<br />
|-<br />
| align="center" scope="row" | Weight<br />
| align="center" | 4.35g<br />
|-<br />
|align="center" scope="row" | Maximum Current<br />
| align="center" | 1.5mA<br />
|-<br />
| align="center" scope="row" | VBAT Current<br />
| align="center" | 800nA<br />
|-<br />
| align="center" scope="row" | work temprature<br />
| align="center" | 0～+50℃<br />
|-<br />
| align="center" scope="row" | Crystal Oscilator <br />
| align="center" | Epson 20 ppm <br />
|-<br />
| align="center" scope="row" | scale<br />
| align="center" | 22x26x18.6(mm)<br />
|-<br />
| align="center" scope="row" | Battery<br />
| align="center" | CR1220<br />
|-<br />
| align="center" scope="row" | RTC chip<br />
| align="center" | DS3231 <br />
|-<br />
| align="center" scope="row" | mount hole<br />
| align="center" | 2*5 Stacking Header<br />
|}<br />
<br />
==Overview==<br />
<br />
==Schematic==<br />
[[Image:RTC_CCAP01.png|700px]]<br />
<br />
==LCD module scale==<br />
<br>[[Image:RTC CCAP02.png|700px]]<br />
<br />
==DT Overlays Used==<br />
With DT enabled, this becomes a line in config.txt:<br />
<br />
dtoverlay=i2c-rtc ds3231<br />
==Learn==<br />
*Type in [sudo raspi-config] set up raspberry pi and prepare to enable i2c interface<br />
<br>[[Image:RTC_tech02.png|700px]]<br />
*select Advanced Options <br />
<br>[[Image:RTC_tech03.png|700px]]<br />
*select I2c <br />
<br>[[Image:RTC_tech04.png|700px]]<br />
*select yes enable I2C <br />
<br>[[Image:RTC_tech05.png|700px]]<br />
*type in [sudo vim.tiny /etc/modules] to open file modules<br />
<br>[[Image:RTC_tech06.png|700px]]<br />
*add i2c-dev device like picture below<br />
<br>[[Image:RTC_tech07.png|700px]]<br />
*install i2c-tools ,type in [sudo apt-get install i2c-tools]<br />
<br>[[Image:RTC_tech08.png|700px]]<br />
*type in [sudo reboot] wait the raspberry pi restart ,Then type in [sudo i2cdetect –y 1], if RTC works ,it should be like picture below<br />
<br>[[Image:RTC_tech09.png|700px]]<br />
*Type in [sudo su –] change root user,then Type in [modprobe i2c-dev] to load I2C device<br />
<br>[[Image:RTC_tech10.png|700px]]<br />
*Type in [echo "ds1307 0x68" > /sys/class/i2c-adapter/i2c-1/new_device] add RTC to system <br />
<br>[[Image:RTC_tech11.png|700px]]<br />
*Then you can use “hwclock” command to use this RTC module<br />
If you want to know more about hwclock command you can type in “man hwclock” to get details<br />
A brief description like following:<br />
Command [hwclock –r] to get RTC time<br />
Command [hwclock -w]set the system time to RTC time <br />
Like following<br />
<br>[[Image:RTC_tech12.png|700px]]<br />
<br />
==Attachment==<br />
<div id="tech1"></div><br />
<br>[[media:DS3231.pdf|ds3231 date sheet]]</div>TaterLihttps://wiki.52pi.com/index.php?title=RTC_EoF-001&diff=8308RTC EoF-0012020-04-22T03:35:28Z<p>TaterLi: /* Compatibility List */</p>
<hr />
<div>=Raspberry Pi RTC Module With Battery=<br />
==Description==<br />
This RTC module use DS3231 as its Real-Time Clock chip which has build-in crystal oscillator. This RTC module communicates with Raspberry Pi through I2C bus.DS3231 is a low power consumer RTC chip and whose back up supply is a 0.2uF Super-Capacitor,which can keep work for a week at least after power down<br />
<br>[[Image:CAP RTC.jpg|center|400px]]<br />
==Compatibility List==<br />
* Compatibility<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Platform !! Super Capacitor RTC !! Notes<br />
|-<br />
|-<br />
|Raspberry Pi 4 Model B || √ ||<br />
|-<br />
|Raspberry Pi 3 Model B Plus|| √ ||<br />
|-<br />
|Raspberry Pi zero || √||<br />
|-<br />
| Raspberry Pi zero W || √||<br />
|-<br />
|Raspberry Pi 3 Model B|| √||<br />
|-<br />
|Raspberry Pi 2 Model B|| √||<br />
|-<br />
|Raspberry Pi Model B+|| √|| <br />
|-<br />
|}<br />
<br />
==Technical Details==<br />
{| width="998" cellspacing="0" cellpadding="0" border="1" <br />
|-<br />
! align="center" scope="col" style="width: 40%" | Type<br />
! align="center" scope="col" | value<br />
<br />
|-<br />
| align="center" scope="row" | Work Voltage<br />
| align="center" | 5V<br />
<br />
|-<br />
| align="center" scope="row" | Weight<br />
| align="center" | 4.35g<br />
|-<br />
|align="center" scope="row" | Maximum Current<br />
| align="center" | 1.5mA<br />
|-<br />
| align="center" scope="row" | VBAT Current<br />
| align="center" | 800nA<br />
|-<br />
| align="center" scope="row" | work temprature<br />
| align="center" | 0～+50℃<br />
|-<br />
| align="center" scope="row" | Crystal Oscilator <br />
| align="center" | Epson 20 ppm <br />
|-<br />
| align="center" scope="row" | scale<br />
| align="center" | 22x26x18.6(mm)<br />
|-<br />
| align="center" scope="row" | Battery<br />
| align="center" | CR1220<br />
|-<br />
| align="center" scope="row" | RTC chip<br />
| align="center" | DS3231 <br />
|-<br />
| align="center" scope="row" | mount hole<br />
| align="center" | 2*5 Stacking Header<br />
|}<br />
<br />
==Overview==<br />
<br />
==Schematic==<br />
[[Image:RTC_CCAP01.png|700px]]<br />
<br />
==LCD module scale==<br />
<br>[[Image:RTC CCAP02.png|700px]]<br />
<br />
==Learn==<br />
*Type in [sudo raspi-config] set up raspberry pi and prepare to enable i2c interface<br />
<br>[[Image:RTC_tech02.png|700px]]<br />
*select Advanced Options <br />
<br>[[Image:RTC_tech03.png|700px]]<br />
*select I2c <br />
<br>[[Image:RTC_tech04.png|700px]]<br />
*select yes enable I2C <br />
<br>[[Image:RTC_tech05.png|700px]]<br />
*type in [sudo vim.tiny /etc/modules] to open file modules<br />
<br>[[Image:RTC_tech06.png|700px]]<br />
*add i2c-dev device like picture below<br />
<br>[[Image:RTC_tech07.png|700px]]<br />
*install i2c-tools ,type in [sudo apt-get install i2c-tools]<br />
<br>[[Image:RTC_tech08.png|700px]]<br />
*type in [sudo reboot] wait the raspberry pi restart ,Then type in [sudo i2cdetect –y 1], if RTC works ,it should be like picture below<br />
<br>[[Image:RTC_tech09.png|700px]]<br />
*Type in [sudo su –] change root user,then Type in [modprobe i2c-dev] to load I2C device<br />
<br>[[Image:RTC_tech10.png|700px]]<br />
*Type in [echo "ds1307 0x68" > /sys/class/i2c-adapter/i2c-1/new_device] add RTC to system <br />
<br>[[Image:RTC_tech11.png|700px]]<br />
*Then you can use “hwclock” command to use this RTC module<br />
If you want to know more about hwclock command you can type in “man hwclock” to get details<br />
A brief description like following:<br />
Command [hwclock –r] to get RTC time<br />
Command [hwclock -w]set the system time to RTC time <br />
Like following<br />
<br>[[Image:RTC_tech12.png|700px]]<br />
==Attachment==<br />
<div id="tech1"></div><br />
<br>[[media:DS3231.pdf|ds3231 date sheet]]</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0105&diff=7886EP-01052020-03-16T04:03:57Z<p>TaterLi: /* How to use Lora TX & RX with C(Raspberry Pi) */</p>
<hr />
<div>==IoT Node(A)==<br />
[[File:IoTnodeA1.jpg|right|300px]]<br />
<br />
==Descriptions==<br />
IoT Node(A) is one of Docker Pi series module.<br><br />
IOT Node(A) = GPS/BDS + GSM + Lora.<br><br />
I2C directly controls Lora, sends and receives data, controls the GSM/GPS/BDS module through SC16IS752, the mainboard only needs I2C support.<br><br />
Support Raspberry Pi and other similar products.<br />
<br />
==Features==<br />
* DockerPi Series<br />
* Programmable<br />
* Control directly(without programming)<br />
* Extend the GPIO Pins <br />
* GPS/BDS Support<br />
* GSM Support<br />
* Lora Support<br />
* Can Stack with other Stack board<br />
* Independent of the mainboard hardware (require I2C support)<br />
<br />
==Official Compatibility Test==<br />
Not only support the following development boards, other development boards can be compatible if they have I2C peripherals. (Note: some software changes may be required)<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Platform !!DockerPi IoT Node(A)!! Notes<br />
|-<br />
|Raspberry Pi All Platform|| √ ||Not Include CM Series & EOL Platform<br />
|-<br />
|}<br />
<br />
==Specifications==<br />
===GPRS section===<br />
* 1. Low power consumption, standby sleep current <1mA<br />
* 2. Support GSM/GPRS four frequency bands, including 850, 900, 1800, 1900MHZ;<br />
* 3. GPRS Class 10;<br />
* 4. Support GPRS data service, maximum data rate, download 85.6Kbps, upload 42.8Kbps;<br />
* 5. Support standard GSM07.07, 07.05 AT commands, and access the serial port through I2C interface conversion.<br />
* 6. AT commands support standard AT and TCP/IP command ports<br />
===GPS section===<br />
* 1. Support BDS/GPS joint positioning<br />
* 2. Support A-GPS, A-BDS<br />
* 3. Support standard SIM card<br />
===LORA section===<br />
* 1. Transmission distance:500 Meters (RF parameters: 0x50 @ China City)<br />
* 2. Support FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation methods<br />
* 3. Ultra-high receiver sensitivity as low as -141 dBm<br />
* 4. Support preamble detection<br />
* 5. Packet engine with CRC, up to 256 bytes<br />
* 6. LORA transceiver indicator<br />
* 7. Easy TX/RX by Docker Pi<br />
<br />
==Mechanical Drawings==<br />
[[File:Lora mechanical.png|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==Gallery==<br />
{|<br />
|[[File:IoTnodeA1.jpg|left|320px]]<br />
|[[File:IoTnodeA2.jpg|none|320px]]<br />
|[[File:IoTnodeA3.jpg|none|320px]]<br />
|}<br />
{|<br />
|[[File:IoTnodeA4.jpg|left|320px]]<br />
|[[File:IoTnodeA5.jpg|none|320px]]<br />
|[[File:IoTnodeA6.jpg|none|320px]]<br />
|}<br />
<br />
==Package Include==<br />
* 1 x IoT Node(A) Board <br />
* 1 x Instructions<br />
* 4 x M2.5*12 + 6 Copper stick<br />
* 4 x M2.5*6 Nut<br />
* 4 x M2.5*6 Half-round head screw<br />
* 1 x 433MHz L-Shaped Tape Antenna <br />
* 1 x 2.4GHz PCB Antenna<br />
* 1 x GPS/BDS High Gain GPS Built-in Ceramic Active Antenna<br />
<br />
==On Board Modules Documentations==<br />
* A9G Module Spicification: [[ File:A9g product specification.pdf ]]<br />
* A9G Module AT Command Manual: [[ File:A9G AT COMMAND manual.pdf ]]<br />
* A9G GPRS Instruction Set v1.0 [[ File:A9G gprs series module at instruction set v1.0.pdf ]]<br />
* GPRS C SDK: [[ File:GPRS C SDK-master.zip ]]<br />
<br />
==Technical Details==<br />
===A9G Module===<br />
* A9G module offers two serial port. <br />
* Use I2C <=> UART bridge for communication.<br />
{| class="wikitable"<br />
|-<br />
! Serial Port !! Module name <br />
|-<br />
|/dev/ttySC0 || GSM<br />
|-<br />
|/dev/ttySC1 || GPS/BDS<br />
|}<br />
<br />
===Register Map===<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Register Address!! Function !! Value<br />
|-<br />
| 0x01 || LORA_TX1 || Lora TX Buffer 1 - User Data<br />
|-<br />
| 0x02 || LORA_TX2 || Lora TX Buffer 2 - User Data<br />
|-<br />
| 0x03 || LORA_TX3 || Lora TX Buffer 3 - User Data<br />
|-<br />
| 0x04 || LORA_TX4 || Lora TX Buffer 4 - User Data<br />
|-<br />
| 0x05 || LORA_TX5 || Lora TX Buffer 5 - User Data<br />
|-<br />
| 0x06 || LORA_TX6 || Lora TX Buffer 6 - User Data<br />
|-<br />
| 0x07 || LORA_TX7 || Lora TX Buffer 7 - User Data<br />
|-<br />
| 0x08 || LORA_TX8 || Lora TX Buffer 8 - User Data<br />
|-<br />
| 0x09 || LORA_TX9 || Lora TX Buffer 9 - User Data<br />
|-<br />
| 0x0a || LORA_TX10 || Lora TX Buffer 10 - User Data<br />
|-<br />
| 0x0b || LORA_TX11 || Lora TX Buffer 11 - User Data<br />
|-<br />
| 0x0c || LORA_TX12 || Lora TX Buffer 12 - User Data<br />
|-<br />
| 0x0d || LORA_TX13 || Lora TX Buffer 13 - User Data<br />
|-<br />
| 0x0e || LORA_TX14 || Lora TX Buffer 14 - User Data<br />
|-<br />
| 0x0f || LORA_TX15 || Lora TX Buffer 15 - User Data<br />
|-<br />
| 0x10 || LORA_TX16 || Lora TX Buffer 16 - User Data<br />
|-<br />
| 0x11 || LORA_RX1 || Lora RX Buffer 1 - User Data<br />
|-<br />
| 0x12 || LORA_RX2 || Lora RX Buffer 2 - User Data<br />
|-<br />
| 0x13 || LORA_RX3 || Lora RX Buffer 3 - User Data<br />
|-<br />
| 0x14 || LORA_RX4 || Lora RX Buffer 4 - User Data<br />
|-<br />
| 0x15 || LORA_RX5 || Lora RX Buffer 5 - User Data<br />
|-<br />
| 0x16 || LORA_RX6 || Lora RX Buffer 6 - User Data<br />
|-<br />
| 0x17 || LORA_RX7 || Lora RX Buffer 7 - User Data<br />
|-<br />
| 0x18 || LORA_RX8 || Lora RX Buffer 8 - User Data<br />
|-<br />
| 0x19 || LORA_RX9 || Lora RX Buffer 9 - User Data<br />
|-<br />
| 0x1a || LORA_RX10 || Lora RX Buffer 10 - User Data<br />
|-<br />
| 0x1b || LORA_RX11 || Lora RX Buffer 11 - User Data<br />
|-<br />
| 0x1c || LORA_RX12 || Lora RX Buffer 12 - User Data<br />
|-<br />
| 0x1d || LORA_RX13 || Lora RX Buffer 13 - User Data<br />
|-<br />
| 0x1e || LORA_RX14 || Lora RX Buffer 14 - User Data<br />
|-<br />
| 0x1f || LORA_RX15 || Lora RX Buffer 15 - User Data<br />
|-<br />
| 0x20 || LORA_RX16 || Lora RX Buffer 16 - User Data<br />
|-<br />
|}<br />
<br />
* 0x01 - 0x10 Write Only.<br />
* 0x11 - 0x20 Read Only.<br />
----<br />
{| class="wikitable" style="height: 200px"<br />
|-<br />
! scope="col" width="100" |Register Address <br />
! colspan="8"| 0x22 <br />
|-<br />
| Name || - <br />
! colspan="3" |SpreadingFactor <br />
! colspan="2" |SignalBandwidth <br />
! colspan="2" |ErrorCoding <br />
|-<br />
|Default Value || 0 || 1 || 0 || 1 || 1 || 0 || 1 || 1 <br />
|-<br />
| Description || Reserved <br />
! colspan="3" | Band range 7-12 <br />
! colspan="2" | Spread spectrum bandwidth 6-9 <br />
! colspan="2" | Effective data ratio 1-4<br />
|}<br />
<br />
* It is recommended to keep the default unless you know the meaning of the LORA parameter.<br />
----<br />
{| class="wikitable" style="height: 200px"<br />
|-<br />
! scope="col" width="100" |Register Address <br />
! colspan="8"| 0x23 <br />
|-<br />
|Default Value || 0 || 0 || 0 || 0 || 0 || 0 || 0 || 0 <br />
|-<br />
| Description || L_SET || G_RESET || Reserved || Reserved ||Reserved || Reserved || L_RXNE || L_TX<br />
|}<br />
<br />
* L_SET(Write Only)<br />
# Write 1 to set parameters from 0x22 to LORA Module.<br />
# Write 0 not effect<br />
* G_RESET(Write Only)<br />
# Write 1 to reset A9G Module<br />
# Write 0 not effect<br />
* L_RXNE(Read & Write)<br />
# Write 1 cause error<br />
# Write 0 to clear<br />
# Read 1 means data has been received, please get the data from the register 0x11 - 0x20.<br />
# Read 0 means no data available now.<br />
* L_SET(Write Only)<br />
# Write 1 to send data,please fill in the data in register 0x01 - 0x10 before send.<br />
# Write 0 not effect<br />
<br />
<br />
----<br />
<br />
==How to use==<br />
===How to assemble===<br />
* Mount the Iot Node(A) board to Raspberry Pi<br />
* Hookup GPS antana and Lora antana to IPX port.<br />
E1：GPS-ANTANA-IPX<br />
E3：LoRa-ANTANA-IPX<br />
* Screws the GPRS antana on the SMA port.<br />
{|<br />
|[[File:IoTnodeA8.jpg|left|440px]]<br />
|[[File:IoTnodeA7.jpg|none|440px]]<br />
|}<br />
<br />
===Configuring I2C(Raspberry Pi)===<br />
Run '''sudo raspi-config''' and follow the prompts to install i2c support for the ARM core and linux kernel<br /><br />
Go to '''Interfacing Options'''<br />
[[File:Raspi-config-1.png |none|320px]]<br />
then '''I2C'''<br />
[[File:Raspi-config-2.png |none|320px]]<br />
Enable!<br />
[[File:Raspi-config-3.png |none|320px]]<br />
Done!<br />
[[File:Raspi-config-4.png |none|320px]]<br />
<br />
=== Replace /boot/overlays/sc16is752-i2c.dtbo(Raspberry Pi)===<br />
Replace /boot/overlays/sc16is752-i2c.dtbo file with this file: <br />
'''[[ File:Sc16is752-i2c.zip ]]'''<br />
<br />
[[File:Replace_dtbo_sc16is752.png|none|480px]]<br />
<br />
Modify '''/boot/config.txt''' file and add following parameter:<br />
<br />
<pre> dtoverlay=sc16is752-i2c </pre><br />
<br />
[[File:Add_dt_sc16.png|none|480px]]<br />
<br />
And then save it and reboot Raspberry Pi.<br><br />
* After rebooting, two serial devices will be detected in following location:<br />
<pre> <br />
/dev/ttySC0 <br />
/dev/ttySC1<br />
</pre><br />
<br />
===How to use GPS Module with gpsd(Raspberry Pi)===<br />
A) First, replace the /boot/overlays/sc16is752-i2c.dtbo and make sure I2C is working properly.<br />
# Replace sc16is752-i2c.dtbo [[https://wiki.52pi.com/index.php/IoT_Node(A)_SKU:_EP-0105#Replace_.2Fboot.2Foverlays.2Fsc16is752-i2c.dtbo.28Raspberry_Pi.29]]<br />
# Configuring I2C[[https://wiki.52pi.com/index.php/IoT_Node(A)_SKU:_EP-0105#Configuring_I2C.28Raspberry_Pi.29]]<br />
<br />
B)Install gpsd tools.<br />
<pre><br />
sudo apt install gpsd gpsd-clients<br />
</pre><br />
[[File:Gpsd-install.png|none|480px]]<br />
C)Modify '''/etc/default/gpsd''' file and add following parameters:<br />
<pre><br />
DEVICES="/dev/ttySC1"<br />
GPSD_OPTIONS="-F /var/run/gpsd.sock"<br />
</pre><br />
[[File:Gpsd-config.png|none|480px]]<br />
<br />
D)Enter command '''i2cset -y 1 0x16 0x23 0x40''' to reset the GPRS module.<br />
<br />
E)Python Script For Open GPS:<br />
<pre><br />
import serial<br />
import os<br />
import time<br />
<br />
# Restart gpsd service.<br />
os.system("sudo systemctl restart gpsd.socket")<br />
# Open serial port <br />
ser = serial.Serial('/dev/ttySC0', 115200)<br />
<br />
i = 0<br />
<br />
if ser.isOpen == False:<br />
ser.open()<br />
try:<br />
print("Turn on GPS...")<br />
while True:<br />
ser.write(str.encode("AT+GPS=1\r"))<br />
size = ser.inWaiting() <br />
if size != 0:<br />
ticks = time.time()<br />
response = ser.read(size)<br />
gps = str(response,encoding="utf-8")<br />
if(gps.find("OK") != -1):<br />
os.system("sudo cgps -s") <br />
exit()<br />
else:<br />
i = i + 1<br />
print("Waiting GPS Enable, If the time is too long, Please test outdoors:" + str(i))<br />
ser.flushInput() <br />
time.sleep(1) <br />
except KeyboardInterrupt:<br />
ser.flushInput()<br />
ser.close()<br />
</pre><br />
F)Save it and execute it:<br />
<pre><br />
python3 GPS.py <br />
</pre><br />
[[File:Gps-fix.png|none|500px]]<br />
<br />
===How to use GPS Module with C(Raspberry Pi)===<br />
A)Install gpsd tools.<br />
<pre><br />
sudo apt-get install libgps-dev<br />
</pre><br />
B)Create source code and name it "gps.c"<br />
<pre><br />
#include <gps.h><br />
#include <stdio.h><br />
#include <stdlib.h><br />
#include <unistd.h><br />
#include <math.h><br />
<br />
int main()<br />
{<br />
int rc;<br />
struct timeval tv;<br />
struct gps_data_t gps_data;<br />
if ((rc = gps_open("localhost", "2947", &gps_data)) == -1)<br />
{<br />
printf("code: %d, reason: %s\n", rc, gps_errstr(rc));<br />
return EXIT_FAILURE;<br />
}<br />
<br />
gps_stream(&gps_data, WATCH_ENABLE | WATCH_JSON, NULL);<br />
<br />
while (1)<br />
{<br />
/* wait for 2 seconds to receive data */<br />
if (gps_waiting(&gps_data, 2000000))<br />
{<br />
/* read data */<br />
if ((rc = gps_read(&gps_data)) == -1)<br />
{<br />
printf("error occured reading gps data. code: %d, reason: %s\n", rc, gps_errstr(rc));<br />
}<br />
else<br />
{<br />
/* Display data from the GPS receiver. */<br />
if ((gps_data.status == STATUS_FIX) && (gps_data.fix.mode == MODE_2D || gps_data.fix.mode == MODE_3D) && !isnan(gps_data.fix.latitude) && !isnan(gps_data.fix.longitude))<br />
{<br />
/* gettimeofday(&tv, NULL); EDIT: tv.tv_sec isn't actually the timestamp! */<br />
<br />
printf("latitude: %f, longitude: %f, speed: %f, timestamp: %lf\n", gps_data.fix.latitude, gps_data.fix.longitude, gps_data.fix.speed, gps_data.fix.time);<br />
//EDIT: Replaced tv.tv_sec with gps_data.fix.time<br />
}<br />
else<br />
{<br />
printf("no GPS data available\n");<br />
}<br />
}<br />
}<br />
sleep(3);<br />
}<br />
/* When you are done... */<br />
gps_stream(&gps_data, WATCH_DISABLE, NULL);<br />
gps_close(&gps_data);<br />
return EXIT_SUCCESS;<br />
}<br />
</pre><br />
<br />
</pre><br />
Compile!<br />
<br />
<code>gcc gps.c -lm -lgps -o gps</code><br><br />
<br />
Exec It! <br />
<br />
<code>./gps</code><br><br />
<br />
[[File:Gps-c.png|none|500px]]<br />
----<br />
<br />
===How to use GPS Module with Python(Raspberry Pi)===<br />
The following code is recommended to be executed using Python 3 and install the '''gpsd-py3''' library and '''GPS 2D/3D Fix''':<br><br />
<pre><br />
import gpsd<br />
<br />
# Connect to the local gpsd<br />
gpsd.connect()<br />
<br />
# Get gps position<br />
packet = gpsd.get_current()<br />
<br />
# See the inline docs for GpsResponse for the available data<br />
print(packet.position())<br />
</pre><br />
[[File:Gps-py.png|none|300px]]<br />
----<br />
<br />
===How to use GSM Module with PPPd(Raspberry Pi)===<br />
<br />
A) First, replace the /boot/overlays/sc16is752-i2c.dtbo and make sure I2C is working properly.<br />
# Replace sc16is752-i2c.dtbo [[https://wiki.52pi.com/index.php/IoT_Node(A)_SKU:_EP-0105#Replace_.2Fboot.2Foverlays.2Fsc16is752-i2c.dtbo.28Raspberry_Pi.29]]<br />
# Configuring I2C[[https://wiki.52pi.com/index.php/IoT_Node(A)_SKU:_EP-0105#Configuring_I2C.28Raspberry_Pi.29]]<br />
<br />
B)Enter command '''i2cset -y 1 0x16 0x23 0x40''' to reset the GPRS module.<br />
# After running the command, you need to wait a little, about 10 seconds.<br />
# You can also use the following method to reset.[[https://wiki.52pi.com/index.php/IoT_Node(A)_SKU:_EP-0105#How_to_diagnose_my_GSM_Module.28Raspberry_Pi.29]]<br />
<br />
C)Enter command '''sudo apt install ppp''' to install ppp tools.<br />
<br />
[[File:Pppd-tools-apt.png|none|480px]]<br />
<br />
D)Copy '''/etc/ppp/peers/provider''' to '''/etc/ppp/peers/gprs'''<br />
<br />
E)Modify '''/etc/ppp/peers/gprs'''<br />
#Line 10 : Please consult your service provider for the user (Example:cmnet).<br />
#Line 15 : Please consult your service provider for the apn (Example:cmnet).<br />
#Line 18 - Line 24:Recommended setting <br />
<br />
[[File:Gprs-set.png|none|480px]]<br />
<br />
F)Modify '''/etc/chatscripts/gprs''' (Change Line 34 to Line 35,Dialout Number May be '''NOT''' *99#)<br />
<br />
[[File:Gprs ppp.png|none|480px]]<br />
<br />
G)Enter command '''sudo pppd call gprs''' to dial up.<br />
<br />
[[File:Get-ip-ppp.png|none|480px]]<br />
<br />
H)Check your ppp config from your ISP.<br />
<br />
[[File:Ppp-test.png|none|480px]]<br />
<br />
I)Enter command '''ping -I ppp0 8.8.8.8''' test your network (If '''Internet''' available and '''route table''' is correct)<br />
<br />
[[File:Ping-google.png|none]]<br />
<br />
J)Please keep the GSM signal good, otherwise the following will occur.<br />
<br />
[[File:Ppp0-signal-bad.png|none]]<br />
<br />
===How to diagnose my GSM Module(Raspberry Pi)===<br />
The following code is recommended to be executed using Python 3 and install the '''smbus''' library:<br><br />
<pre><br />
import serial<br />
import time<br />
import smbus<br />
import operator<br />
import os<br />
<br />
print("Waiting for initializing...")<br />
<br />
bus = smbus.SMBus(1) <br />
bus.write_byte_data(0x16,0x23,0x40)<br />
<br />
ser = serial.Serial('/dev/ttySC0', 115200)<br />
<br />
if ser.isOpen == False:<br />
ser.open()<br />
try:<br />
print('-'*60)<br />
print("Initializing A9G GPRS module.")<br />
print("GSM connecting...")<br />
time.sleep(3)<br />
i = 0<br />
while True:<br />
ser.write(str.encode("AT+CCID\r"))<br />
size = ser.inWaiting() <br />
if size != 0:<br />
ticks = time.time()<br />
response = ser.read(size)<br />
ccid = str(response,encoding="utf-8")<br />
print(ccid)<br />
else:<br />
i = i + 1<br />
ser.flushInput() <br />
time.sleep(1) <br />
except KeyboardInterrupt:<br />
ser.close()<br />
</pre><br />
<br />
Exec the Test Script,based on the results of the implementation, we can diagnose the GSM module.<br />
<br />
For example, the following return, '''CME ERROR 53''' error tell us Power not good.<br />
<br />
CME Code = GSM Equipment Related errors<br />
<br />
[[File:Cme-53.png|500px|none]]<br />
<br />
Of course, the script also has a reset function. If you can display the '''CCID''' correctly, the reset is complete.<br />
<br />
[[File:A9g-test.png|500px|none]]<br />
Press '''Ctrl-C''' to kill this script.<br />
<br />
===Dialout log reference(Raspberry Pi)===<br />
'''For quick troubleshooting, please refer to other documents for more details.'''<br />
<pre><br />
Script /usr/sbin/chat -s -v -f /etc/chatscripts/gprs -T cmnet finished (pid 1025), status = 0x0<br />
Serial connection established.<br />
using channel 1<br />
Using interface ppp0<br />
Connect: ppp0 <--> /dev/ttyUSB0<br />
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x93623f70> <pcomp> <accomp>]<br />
rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <auth pap> <magic 0xb90fa> <pcomp> <accomp>]<br />
sent [LCP ConfAck id=0x1 <asyncmap 0x0> <auth pap> <magic 0xb90fa> <pcomp> <accomp>]<br />
rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x93623f70> <pcomp> <accomp>]<br />
sent [LCP EchoReq id=0x0 magic=0x93623f70]<br />
sent [PAP AuthReq id=0x1 user="cmnet" password=<hidden>]<br />
rcvd [LCP EchoRep id=0x0 magic=0xb90fa]<br />
rcvd [PAP AuthAck id=0x1 "Login ok"]<br />
Remote message: Login ok<br />
PAP authentication succeeded<br />
sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]<br />
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]<br />
rcvd [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.0.1>]<br />
sent [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.0.1>]<br />
rcvd [LCP ProtRej id=0x2 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]<br />
Protocol-Reject for 'Compression Control Protocol' (0x80fd) received<br />
rcvd [IPCP ConfNak id=0x1 <addr 10.188.229.78> <ms-dns1 211.136.17.107> <ms-dns2 211.136.20.203>]<br />
sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 10.188.229.78> <ms-dns1 211.136.17.107> <ms-dns2 211.136.20.203>]<br />
rcvd [IPCP ConfAck id=0x2 <compress VJ 0f 01> <addr 10.188.229.78> <ms-dns1 211.136.17.107> <ms-dns2 211.136.20.203>]<br />
not replacing default route to eth0 [10.0.1.1]<br />
local IP address 10.188.229.78<br />
remote IP address 192.168.0.1<br />
primary DNS address 211.136.17.107<br />
secondary DNS address 211.136.20.203<br />
Script /etc/ppp/ip-up started (pid 1034)<br />
Script /etc/ppp/ip-up finished (pid 1034), status = 0x0<br />
</pre><br />
<br />
===How to use Lora TX & RX with C(Raspberry Pi)===<br />
<br />
'''It must be transferred between the two IOT Node(A). The content sent by itself cannot be received by itself.'''<br />
<br />
* How to Send:After filling the data into register 0x01 - 0x10, set the '''L_TX''' bit to start sending data.<br />
<pre><br />
#include <stdio.h><br />
#include <wiringPi.h><br />
#include <wiringPiI2C.h><br />
<br />
int main(){<br />
int fd;<br />
<br />
fd = wiringPiI2CSetup(0x16);<br />
<br />
wiringPiI2CWriteReg8(fd,1,0xAA);<br />
wiringPiI2CWriteReg8(fd,2,0x55);<br />
wiringPiI2CWriteReg8(fd,3,0xA5);<br />
wiringPiI2CWriteReg8(fd,4,0x5A);<br />
<br />
wiringPiI2CWriteReg8(fd,0x23,0x01);<br />
}<br />
</pre><br />
</pre><br />
* How to Send Receive:Check '''L_RXNE''' bit,If set,new data arrived,this flag must be manually clear.<br />
<pre><br />
#include <stdio.h><br />
#include <wiringPi.h><br />
#include <wiringPiI2C.h><br />
<br />
int main(){<br />
int fd;<br />
int ret[4];<br />
<br />
fd = wiringPiI2CSetup(0x16);<br />
<br />
if (wiringPiI2CReadReg8(fd, 0x23) & 0x02 )<br />
{<br />
ret[0] = wiringPiI2CReadReg8(fd, 0x11);<br />
ret[1] = wiringPiI2CReadReg8(fd, 0x12);<br />
ret[2] = wiringPiI2CReadReg8(fd, 0x13);<br />
ret[3] = wiringPiI2CReadReg8(fd, 0x14);<br />
<br />
printf("Received data:0x%02X,0x%02X,0x%02X,0x%02X",ret[0],ret[1],ret[2],ret[3])<br />
}else{<br />
printf("No data Received yet~")<br />
}<br />
}<br />
</pre><br />
<br />
===How to use Lora TX & RX with Python(Raspberry Pi)===<br />
The following code is recommended to be executed using Python 3 and install the '''smbus''' library.<br />
<br />
'''It must be transferred between the two IOT Node(A). The content sent by itself cannot be received by itself. Please save it as a py script for execution.'''<br />
<br />
* How to Send:After filling the data into register 0x01 - 0x10, set the '''L_TX''' bit to start sending data.<br />
<pre><br />
import time<br />
import smbus<br />
import os<br />
import sys<br />
<br />
bus = smbus.SMBus(1) <br />
<br />
try:<br />
data_list = [170,85,165,90] <br />
<br />
# write data to register and then the data will be send out. <br />
for index in range(1,len(data_list) + 1):<br />
bus.write_byte_data(0x16,index,data_list[index - 1])<br />
print("LORA send data to %d register %d data" %(index, data_list[index - 1]))<br />
<br />
bus.write_byte_data(0x16,0x23,0x01) <br />
except KeyboardInterrupt:<br />
sys.exit()<br />
</pre><br />
</pre><br />
* How to Send Receive:Check '''L_RXNE''' bit,If set,new data arrived,this flag must be manually clear.<br />
<pre><br />
import time<br />
import smbus<br />
import os<br />
import sys<br />
<br />
bus = smbus.SMBus(1) <br />
recv_data = [] <br />
<br />
try:<br />
if bus.read_byte_data(0x16,0x23) & 0x02 :<br />
# manually clear L_RXNE<br />
bus.write_byte_data(0x16,0x23,0x00) <br />
register_list = [0x11,0x12,0x13,0x14]<br />
<br />
# read out data<br />
for index in range(0x11,len(register_list) + 0x11):<br />
recv_data.append(bus.read_byte_data(0x16, register_list[index - 0x11]))<br />
<br />
print("Received data:")<br />
print(recv_data) <br />
else :<br />
print("No data Received yet~")<br />
except KeyboardInterrupt:<br />
sys.exit()<br />
</pre><br />
<br />
===Special description of I2C bandwidth===<br />
<br />
*The limit of the I2C speed is 400kHz,due to the I2C protocol,so the single device effective bandwidth is lower than 320kbps,multi device effective bandwidth is lower than 160kbps.<br />
*The limit of the I2C <=> UART Bridge speed is 115200bps.<br />
*When GPS and GSM work at the same time, I2C bandwidth is insufficient,because 115.2kbps * 2 = 230.4kbps,so some data will be overflow.<br />
*Reducing the baud rate of GPS and GSM communication can improve the communication bandwidth shortage.<br />
*Stacking other DockerPi modules may take up extra I2C bandwidth.<br />
*At usually, the network data speed is slow, so the GSM bandwidth is not full, so there is no overflow problem.<br />
<br />
==FAQ==<br />
* Q: GPS Status always NO FIX?<br />
A: GPS must be used outdoors,It may take up to 15 minutes for the first use.<br />
<br />
* Q: Unable to open serial port?<br />
A: Check permissions, dialout groups, and whether other software is occupying the serial port.<br />
<br />
* Q: PPP No internet access,How can I do?<br />
A: Consult your ISP service provider.<br />
<br />
* Q: Dose CDMA Support?<br />
A: No.<br />
<br />
* Q: I can't use the BDS system.<br />
A: Available only in China and parts of Asia.<br />
<br />
* Q: The network speed is too slow.<br />
A: 2G network is unable to compare speed with 5G network.<br />
<br />
* Q: Can I use other GPS antennas?<br />
A: Yes, but please be careful not to use antennas that exceed the GPS power limit.<br />
<br />
* Q: My SIM card has no signal, but it works fine on the mobile phone. Why?<br />
A: Make sure your location 2G network is well covered & Make sure your carrier does not ban your 2G network.<br />
<br />
* Q: PPP have internet access,but can't ping any website?<br />
A: Try to run '''route add -net 0.0.0.0 ppp0'''<br />
<br />
* Q: GSM Connect script failed,How to do?<br />
A: Try to run '''i2cset -y 1 0x16 0x23 0x40''' and wait 1 minutes.If Failed,Please check your SIM card.<br />
<br />
* Q: Why I get "timeout sending Config-Requests"?<br />
A: Please check the antenna and 2G signal conditions..<br />
<br />
* Q: Could not determine local IP address,How can I do?<br />
A: The program will try again until it fails. If it fails, please try again later, or contact the ISP to resolve it.<br />
<br />
* Q: Could not determine remote IP address,How can I do?<br />
A: Your ISP limits how your SIM is used.<br />
<br />
* Q: What is China Dialout Number?<br />
A: WCDMA(*99#) CDMA(#777) TD-SCDMA(981#) GPRS/EGDE(99**1#)<br />
<br />
* Q: What is Other Region Dialout Number?<br />
A: Ask your ISP provider.<br />
<br />
* Q: '''pppd call gprs''' can dial successfully but '''ping -I ppp0 8.8.8.8''' fail,How can I do?<br />
A: If there is no problem with the previous script, if you run '''pppd call gprs''' succes, and ifpconfig can view the ppp0 network card. However, if you have enabled Ethernet eth0 before dialing, you can use the ppp0 NIC to ping the specified ip or domain name '''ping -I ppp0 8.8.8.8''' and it will not succeed for two reasons. One is the default gateway in the routing table. It was generated by eth0 before, and one is the default dns server address.After the defaultroute is enabled in the pppd script, pppd will add a default gateway information to the routing table after dialing successfully. However, because there is already a default gateway, the addition fails. The default gateway is still set by the previous eth. Before '''pppd call gprs''' we should first '''route del default''' to delete the default route (preferably write a script to delete the default route - dialing and other operations).<br />
<br />
* Q: Dial stability is relatively poor, Why?<br />
A: Because 2G coverage is getting lower and lower, you can use a more powerful antenna or add the '''lcp-echo-interval''' parameter.<br />
<br />
* Q: Why I get '''UnicodeDecodeError: 'utf8' codec can't decode byte 0xXX''' ?<br />
A: Please refer => [[IoT_Node(A)_SKU:_EP-0105#Replace_.2Fboot.2Foverlays.2Fsc16is752-i2c.dtbo.28Raspberry_Pi.29]]<br />
<br />
==Keywords==<br />
* IoT,Lora,GPS,GPRS,GSM,Node,radio devices,BDS</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0106&diff=7797EP-01062020-02-28T09:00:44Z<p>TaterLi: /* Register Map */</p>
<hr />
<div>==DockerPi Sensor Hub Development Board==<br />
[[File:Sensorhub2.jpg |right|300px]]<br />
<br />
==Description==<br />
The DockerPi SensorHub for obtaining environmental parameters in the Internet of Things.<br><br />
It integrates various environmental sensors: temperature sensors, humidity sensors, air pressure sensors, lighting and thermal infrared sensors. <br><br />
You can use them in smart homes. <br><br />
To obtain various parameters in life, these parameters can be processed to control the home reasonably and intelligently. <br><br />
For example, the temperature of the temperature sensor can be used to control the heating device or the air conditioner. <br><br />
The thermal infrared sensor can detect if someone is in the living room. <br><br />
<br />
==Features==<br />
* DockerPi Series<br />
* Programmable<br />
* Read directly(without programming)<br />
* Extend the GPIO Pins <br />
* Ext. Temperature Detection, Thermistor Detection Temperature Range -30℃~127℃<br />
* OnBoard Temperature DHT11 -20℃~60℃<br />
* P. Temperature Sensor -40℃~80℃. <br />
* Humidity detection, sensor detection range 20% Rh ~ 95% Rh<br />
* Light intensity detection, detection range: 0Lux~1800Lux<br />
* Pressure detection, detection range: 300 Pa ~ 1100 hPa<br />
* Biopsy test (biopsy test with corresponding indicator), maximum detection angle of 100 degrees, maximum distance of 12m<br />
* Can Stack with other Stack board<br />
* Independent of the mainboard hardware (require I2C support)<br />
<br />
==Official Compatibility Test==<br />
Not only support the following development boards, other development boards can be compatible if they have I2C peripherals. (Note: some software changes may be required)<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Platform !!DockerPi Sensor Hub !! Notes<br />
|-<br />
|Raspberry Pi All Platform|| √ ||Not Include CM Series & EOL Platform<br />
|-<br />
|Banana Pi M3 || √ ||Python 3 & Modify DEVICE_BUS to 2<br />
|-<br />
|Orange Pi Zero || √ ||Python 3 & Modify DEVICE_BUS to 0<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x Sensor Hub development board <br />
* 4 x M2.5x12 copper stick<br />
* 8 x M2.5x6 screws and nuts <br />
* 1 x NTC temperature sensor (waterproof)<br />
* 1 x Introductions<br />
[[File:Sensorhub9.jpg|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Gallery==<br />
{|<br />
|[[File:Sensorhub1.jpg |left|320px]]<br />
|[[File:Sensorhub2.jpg |none|320px]]<br />
|[[File:Sensorhub3.jpg |none|320px]]<br />
|}<br />
{|<br />
|[[File:Sensorhub4.jpg |left|320px]]<br />
|[[File:Sensorhub5.jpg |none|320px]]<br />
|[[File:Sensorhub6.jpg |none|320px]]<br />
|}<br />
{|<br />
|[[File:Sensorhub7.jpg |left|320px]]<br />
|[[File:Sensorhub8.jpg |none|320px]]<br />
|[[File:Sensorhub9.jpg |none|320px]]<br />
|}<br />
<br />
==Mechanical Drawings==<br />
[[File:Mechanical sensorhub0.png|left|600px]]<br />
<br style="clear:both;"><br />
<br />
==Register Map==<br />
<br />
'''All registers are Read Only'''.<br />
<br />
'''Device Addr:0x17'''.<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Register Address !! Function !! Value<br />
|-<br />
| 0x01 || TEMP_REG || Ext. Temperature [Unit:degC]<br />
|-<br />
| 0x02 || LIGHT_REG_L || Light Brightness Low 8 Bit [Unit:Lux]<br />
|-<br />
| 0x03 || LIGHT_REG_H || Light Brightness High 8 Bit [Unit:Lux]<br />
|-<br />
| 0x04 || STATUS_REG || Status Function<br />
|-<br />
| 0x05 || ON_BOARD_TEMP_REG || OnBoard Temperature [Unit:degC]<br />
|-<br />
| 0x06 || ON_BOARD_HUMIDITY_REG || OnBoard Humidity [Uinit:%]<br />
|-<br />
| 0x07 || ON_BOARD_SENSOR_ERROR || 0(OK) - 1(Error)<br />
|-<br />
| 0x08 || BMP280_TEMP_REG || P. Temperature [Unit:degC]<br />
|-<br />
| 0x09 || BMP280_PRESSURE_REG_L || P. Pressure Low 8 Bit [Unit:Pa]<br />
|-<br />
| 0x0A || BMP280_PRESSURE_REG_M || P. Pressure Mid 8 Bit [Unit:Pa]<br />
|-<br />
| 0x0B || BMP280_PRESSURE_REG_H || P. Pressure High 8 Bit [Unit:Pa]<br />
|-<br />
| 0x0C || BMP280_STATUS || 0(OK) - 1(Error)<br />
|-<br />
| 0x0D || HUMAN_DETECT || 0(No Active Body) - 1(Active Body)<br />
|}<br />
<br />
{| class="wikitable" style="height: 200px"<br />
|-<br />
! scope="col" width="100" |STATUS_REG<br />
! colspan="8"| 0x04 <br />
|-<br />
|Default Value || 0 || 0 || 0 || 0 || 0 || 0 || 0 || 0 <br />
|-<br />
| Description || Reserved || Reserved || Reserved || Reserved || L_FAIL || L_OVR || T_FAIL || T_OVR<br />
|}<br />
<br />
* T_OVR(Read Only)<br />
# Read 1 means Ext. Temperature Overflow.<br />
# Read 0 means Ext. Temperature works well.<br />
* T_FAIL(Read Only)<br />
# Read 1 means Ext. Temperature Not Found.<br />
# Read 0 means Ext. Temperature works well.<br />
* L_OVR(Read Only)<br />
# Read 1 means Light Brightness Overflow.<br />
# Read 0 means Light Brightness works well.<br />
* T_FAIL(Read Only)<br />
# Read 1 means Light Brightness Not Found.<br />
# Read 0 means Light Brightness works well.<br />
<br />
==Configuring I2C(Raspberry Pi)==<br />
Run sudo raspi-config and follow the prompts to install i2c support for the ARM core and linux kernel<br /><br />
Go to '''Interfacing Options'''<br />
[[File:Raspi-config-1.png |none|320px]]<br />
then '''I2C'''<br />
[[File:Raspi-config-2.png |none|320px]]<br />
Enable!<br />
[[File:Raspi-config-3.png |none|320px]]<br />
Done!<br />
[[File:Raspi-config-4.png |none|320px]]<br />
<br />
==Program in Language C(Raspberry Pi)==<br />
* Create source code and name it "sensor.c"<br />
<pre><br />
#include <stdio.h><br />
#include <stdint.h><br />
#include <wiringPi.h><br />
#include <wiringPiI2C.h><br />
<br />
#define TEMP_REG 0x01<br />
#define LIGHT_REG_L 0x02<br />
#define LIGHT_REG_H 0x03<br />
#define STATUS_REG 0x04<br />
#define ON_BOARD_TEMP_REG 0x05<br />
#define ON_BOARD_HUMIDITY_REG 0x06<br />
#define ON_BOARD_SENSOR_ERROR 0x07<br />
#define BMP280_TEMP_REG 0x08<br />
#define BMP280_PRESSURE_REG_L 0x09<br />
#define BMP280_PRESSURE_REG_M 0x0A<br />
#define BMP280_PRESSURE_REG_H 0x0B<br />
#define BMP280_STATUS 0x0C<br />
#define HUMAN_DETECT 0x0D<br />
<br />
uint8_t aReceiveBuf[0x0D + 1];<br />
<br />
int main(void)<br />
{<br />
<br />
int fd;<br />
int i = 0;<br />
fd = wiringPiI2CSetup(0x17);<br />
<br />
if (fd < 0)<br />
printf("Extend board Can not be initialized, please enable I2C and try again!\n", fd);<br />
<br />
for (i = TEMP_REG; i <= HUMAN_DETECT; i++)<br />
{<br />
aReceiveBuf[i] = wiringPiI2CReadReg8(fd, i);<br />
}<br />
<br />
if (aReceiveBuf[STATUS_REG] & 0x01)<br />
{<br />
printf("Off-chip temperature sensor overrange!\n");<br />
}<br />
else if (aReceiveBuf[STATUS_REG] & 0x02)<br />
{<br />
printf("No external temperature sensor!\n");<br />
}<br />
else<br />
{<br />
printf("Current external Sensor Temperature = %d Celsius\n", (int)aReceiveBuf[TEMP_REG]);<br />
}<br />
<br />
if (aReceiveBuf[STATUS_REG] & 0x04)<br />
{<br />
printf("Onboard brightness sensor overrange!\n");<br />
}<br />
else if (aReceiveBuf[STATUS_REG] & 0x08)<br />
{<br />
printf("Onboard brightness sensor failure!\n");<br />
}<br />
else<br />
{<br />
printf("Current onboard sensor brightness = %d Lux\n", (int)(aReceiveBuf[LIGHT_REG_H] << 8) | (aReceiveBuf[LIGHT_REG_L]));<br />
}<br />
<br />
printf("Current onboard sensor temperature = %d Celsius\n", (int)aReceiveBuf[ON_BOARD_TEMP_REG]);<br />
printf("Current onboard sensor humidity = %d %%\n", (int)aReceiveBuf[ON_BOARD_HUMIDITY_REG]);<br />
if (aReceiveBuf[ON_BOARD_SENSOR_ERROR] != 0)<br />
{<br />
printf("Onboard temperature and humidity sensor data may not be up to date!\n");<br />
}<br />
<br />
if (aReceiveBuf[BMP280_STATUS] == 0)<br />
{<br />
<br />
printf("Current barometer temperature = %d Celsius\n", (int)aReceiveBuf[BMP280_TEMP_REG]);<br />
printf("Current barometer pressure = %d Pascal"\n", (int)aReceiveBuf[BMP280_PRESSURE_REG_L] | (int)aReceiveBuf[BMP280_PRESSURE_REG_M] << 8 | (int)aReceiveBuf[BMP280_PRESSURE_REG_H] << 16);<br />
}<br />
else<br />
{<br />
printf("Onboard barometer works abnormally!\n");<br />
}<br />
<br />
if (aReceiveBuf[HUMAN_DETECT] == 1)<br />
{<br />
printf("Live body detected within 5 seconds!\n");<br />
}<br />
else<br />
{<br />
printf("No humans detecte!\n");<br />
}<br />
<br />
return 0;<br />
}<br />
</pre><br />
Compile!<br />
<br />
<code>gcc sensor.c -lwiringPi -o sensor</code><br><br />
<br />
Exec It! <br />
<br />
<code>./sensor</code><br><br />
==Program in Language Python(Raspberry Pi)==<br />
The following code is recommended to be executed using Python 3 and install the '''smbus''' library:<br><br />
<pre><br />
import smbus<br />
<br />
DEVICE_BUS = 1<br />
DEVICE_ADDR = 0x17<br />
<br />
TEMP_REG = 0x01<br />
LIGHT_REG_L = 0x02<br />
LIGHT_REG_H = 0x03<br />
STATUS_REG = 0x04<br />
ON_BOARD_TEMP_REG = 0x05<br />
ON_BOARD_HUMIDITY_REG = 0x06<br />
ON_BOARD_SENSOR_ERROR = 0x07<br />
BMP280_TEMP_REG = 0x08<br />
BMP280_PRESSURE_REG_L = 0x09<br />
BMP280_PRESSURE_REG_M = 0x0A<br />
BMP280_PRESSURE_REG_H = 0x0B<br />
BMP280_STATUS = 0x0C<br />
HUMAN_DETECT = 0x0D<br />
<br />
bus = smbus.SMBus(DEVICE_BUS)<br />
<br />
aReceiveBuf = []<br />
<br />
aReceiveBuf.append(0x00) # 占位符<br />
<br />
for i in range(TEMP_REG,HUMAN_DETECT + 1):<br />
aReceiveBuf.append(bus.read_byte_data(DEVICE_ADDR, i))<br />
<br />
if aReceiveBuf[STATUS_REG] & 0x01 :<br />
print("Off-chip temperature sensor overrange!")<br />
elif aReceiveBuf[STATUS_REG] & 0x02 :<br />
print("No external temperature sensor!")<br />
else :<br />
print("Current off-chip sensor temperature = %d Celsius" % aReceiveBuf[TEMP_REG])<br />
<br />
<br />
if aReceiveBuf[STATUS_REG] & 0x04 :<br />
print("Onboard brightness sensor overrange!")<br />
elif aReceiveBuf[STATUS_REG] & 0x08 :<br />
print("Onboard brightness sensor failure!")<br />
else :<br />
print("Current onboard sensor brightness = %d Lux" % (aReceiveBuf[LIGHT_REG_H] << 8 | aReceiveBuf[LIGHT_REG_L]))<br />
<br />
print("Current onboard sensor temperature = %d Celsius" % aReceiveBuf[ON_BOARD_TEMP_REG])<br />
print("Current onboard sensor humidity = %d %%" % aReceiveBuf[ON_BOARD_HUMIDITY_REG])<br />
<br />
if aReceiveBuf[ON_BOARD_SENSOR_ERROR] != 0 :<br />
print("Onboard temperature and humidity sensor data may not be up to date!")<br />
<br />
if aReceiveBuf[BMP280_STATUS] == 0 :<br />
print("Current barometer temperature = %d Celsius" % aReceiveBuf[BMP280_TEMP_REG])<br />
print("Current barometer pressure = %d pascal" % (aReceiveBuf[BMP280_PRESSURE_REG_L] | aReceiveBuf[BMP280_PRESSURE_REG_M] << 8 | aReceiveBuf[BMP280_PRESSURE_REG_H] << 16))<br />
else :<br />
print("Onboard barometer works abnormally!")<br />
<br />
if aReceiveBuf[HUMAN_DETECT] == 1 :<br />
print("Live body detected within 5 seconds!")<br />
else:<br />
print("No humans detected!")<br />
<br />
</pre><br />
==Program in Language Java(Raspberry Pi)==<br />
Creat a new file named :SensorHub.java and paste following codes:<br />
<pre><br />
import java.io.IOException;<br />
import java.util.Arrays;<br />
<br />
import com.pi4j.io.i2c.I2CBus;<br />
import com.pi4j.io.i2c.I2CDevice;<br />
import com.pi4j.io.i2c.I2CFactory;<br />
import com.pi4j.io.i2c.I2CFactory.UnsupportedBusNumberException;<br />
import com.pi4j.platform.PlatformAlreadyAssignedException;<br />
import com.pi4j.util.Console;<br />
<br />
public class SensorHub {<br />
<br />
//SensorHub Address<br />
public static final int DOCKERPI_SENSORHUB_BOARD = 0x17;<br />
<br />
//SensorHub's functions<br />
public static final byte TEMP_REG = (byte) 0x01; <br />
public static final byte LIGHT_REG_L = (byte) 0x02;<br />
public static final byte LIGHT_REG_H = (byte) 0x03;<br />
public static final byte STATUS_REG = (byte) 0x04;<br />
public static final byte ON_BOARD_TEMP_REG = (byte) 0x05;<br />
public static final byte ON_BOARD_HUMIDITY_REG = (byte) 0x06;<br />
public static final byte ON_BOARD_SENSOR_ERROR = (byte) 0x07;<br />
public static final byte BMP280_TEMP_REG = (byte) 0x08; <br />
public static final byte BMP280_PRESSURE_REG_L = (byte) 0x09;<br />
public static final byte BMP280_PRESSURE_REG_M = (byte) 0x0A;<br />
public static final byte BMP280_PRESSURE_REG_H = (byte) 0X0B;<br />
public static final byte BMP280_STATUS = (byte) 0x0C;<br />
public static final byte HUMAN_DETECT = (byte) 0x0D;<br />
<br />
public static void main(String[] args)<br />
throws InterruptedException, PlatformAlreadyAssignedException, IOException, UnsupportedBusNumberException {<br />
<br />
final Console console = new Console();<br />
<br />
I2CBus i2c = I2CFactory.getInstance(I2CBus.BUS_1);<br />
I2CDevice device = i2c.getDevice(DOCKERPI_SENSORHUB_BOARD);<br />
<br />
int i = 0;<br />
<br />
if(device.read(DOCKERPI_SENSORHUB_BOARD) < 0)<br />
console.println("External board Can not be initialized, please enable I2C and try again!",device.read(DOCKERPI_SENSORHUB_BOARD));<br />
else<br />
console.println("External board has been initialized");<br />
<br />
if((device.read(STATUS_REG) & 0x01) == 0x01)<br />
console.println("off-chip temperature sensor overrange!");<br />
else if((device.read(STATUS_REG) & 0x02) == 0x02)<br />
console.println("No external temperature sensor!");<br />
<br />
else {<br />
console.println("the temp of air is :" + device.read(TEMP_REG) + "centigrade");<br />
} <br />
<br />
if((device.read(STATUS_REG) & 0x04) == 0x04) {<br />
console.println("Onboard brightness sensor overrange!");<br />
}<br />
else if((device.read(STATUS_REG) & 0x08) == 0x08) {<br />
console.println("Onboard brightness sensor failure!");<br />
}<br />
else {<br />
console.println("Current onboard sensor brightness is :" + (device.read(LIGHT_REG_L) | device.read(LIGHT_REG_H) << 8) + "lux");<br />
}<br />
<br />
if(device.read(ON_BOARD_SENSOR_ERROR) == 1)<br />
console.println("Onboard temperature and humidity sensor data may not be up to date!");<br />
<br />
console.println("the temp of sensor on board is :" + device.read(ON_BOARD_TEMP_REG) + "centigrade");<br />
console.println("the humidity of sensor is :" + device.read(ON_BOARD_HUMIDITY_REG) + "%");<br />
<br />
if(device.read(BMP280_STATUS) == 0) {<br />
console.println("the temp of air pressure sensor is :" + device.read(BMP280_TEMP_REG) + "centigrade"); <br />
console.println("the air pressure is :" + (device.read(BMP280_PRESSURE_REG_L) | device.read(BMP280_PRESSURE_REG_M) << 8 | device.read(BMP280_PRESSURE_REG_H) << 16) + "pa");<br />
}<br />
else<br />
console.println("Onboard barometer works abnormally!");<br />
<br />
if(device.read(HUMAN_DETECT) == 1) {<br />
console.println("Live body detected within 5 seconds!");<br />
}<br />
else {<br />
console.println("No humans detecte!");<br />
}<br />
}<br />
<br />
}<br />
</pre><br />
*Compile it and running :<br />
<pre>javac SensorHub.java -classpath .:classes:/opt/pi4j/lib/'*'</pre><br />
<pre>sudo java -classpath .:classes:/opt/pi4j/lib/'*' SensorHub</pre><br />
<br />
==Keywords==<br />
SensorHub， Docker pi, humidity, temperature, airpressure, NTC, pir sensor, DHT11, DHT12, light sensor.</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0106&diff=7796EP-01062020-02-28T08:59:49Z<p>TaterLi: /* Register Map */</p>
<hr />
<div>==DockerPi Sensor Hub Development Board==<br />
[[File:Sensorhub2.jpg |right|300px]]<br />
<br />
==Description==<br />
The DockerPi SensorHub for obtaining environmental parameters in the Internet of Things.<br><br />
It integrates various environmental sensors: temperature sensors, humidity sensors, air pressure sensors, lighting and thermal infrared sensors. <br><br />
You can use them in smart homes. <br><br />
To obtain various parameters in life, these parameters can be processed to control the home reasonably and intelligently. <br><br />
For example, the temperature of the temperature sensor can be used to control the heating device or the air conditioner. <br><br />
The thermal infrared sensor can detect if someone is in the living room. <br><br />
<br />
==Features==<br />
* DockerPi Series<br />
* Programmable<br />
* Read directly(without programming)<br />
* Extend the GPIO Pins <br />
* Ext. Temperature Detection, Thermistor Detection Temperature Range -30℃~127℃<br />
* OnBoard Temperature DHT11 -20℃~60℃<br />
* P. Temperature Sensor -40℃~80℃. <br />
* Humidity detection, sensor detection range 20% Rh ~ 95% Rh<br />
* Light intensity detection, detection range: 0Lux~1800Lux<br />
* Pressure detection, detection range: 300 Pa ~ 1100 hPa<br />
* Biopsy test (biopsy test with corresponding indicator), maximum detection angle of 100 degrees, maximum distance of 12m<br />
* Can Stack with other Stack board<br />
* Independent of the mainboard hardware (require I2C support)<br />
<br />
==Official Compatibility Test==<br />
Not only support the following development boards, other development boards can be compatible if they have I2C peripherals. (Note: some software changes may be required)<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Platform !!DockerPi Sensor Hub !! Notes<br />
|-<br />
|Raspberry Pi All Platform|| √ ||Not Include CM Series & EOL Platform<br />
|-<br />
|Banana Pi M3 || √ ||Python 3 & Modify DEVICE_BUS to 2<br />
|-<br />
|Orange Pi Zero || √ ||Python 3 & Modify DEVICE_BUS to 0<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x Sensor Hub development board <br />
* 4 x M2.5x12 copper stick<br />
* 8 x M2.5x6 screws and nuts <br />
* 1 x NTC temperature sensor (waterproof)<br />
* 1 x Introductions<br />
[[File:Sensorhub9.jpg|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Gallery==<br />
{|<br />
|[[File:Sensorhub1.jpg |left|320px]]<br />
|[[File:Sensorhub2.jpg |none|320px]]<br />
|[[File:Sensorhub3.jpg |none|320px]]<br />
|}<br />
{|<br />
|[[File:Sensorhub4.jpg |left|320px]]<br />
|[[File:Sensorhub5.jpg |none|320px]]<br />
|[[File:Sensorhub6.jpg |none|320px]]<br />
|}<br />
{|<br />
|[[File:Sensorhub7.jpg |left|320px]]<br />
|[[File:Sensorhub8.jpg |none|320px]]<br />
|[[File:Sensorhub9.jpg |none|320px]]<br />
|}<br />
<br />
==Mechanical Drawings==<br />
[[File:Mechanical sensorhub0.png|left|600px]]<br />
<br style="clear:both;"><br />
<br />
==Register Map==<br />
<br />
'''All registers are Read Only'''.<br />
'''Device Addr:0x17'''.<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Register Address !! Function !! Value<br />
|-<br />
| 0x01 || TEMP_REG || Ext. Temperature [Unit:degC]<br />
|-<br />
| 0x02 || LIGHT_REG_L || Light Brightness Low 8 Bit [Unit:Lux]<br />
|-<br />
| 0x03 || LIGHT_REG_H || Light Brightness High 8 Bit [Unit:Lux]<br />
|-<br />
| 0x04 || STATUS_REG || Status Function<br />
|-<br />
| 0x05 || ON_BOARD_TEMP_REG || OnBoard Temperature [Unit:degC]<br />
|-<br />
| 0x06 || ON_BOARD_HUMIDITY_REG || OnBoard Humidity [Uinit:%]<br />
|-<br />
| 0x07 || ON_BOARD_SENSOR_ERROR || 0(OK) - 1(Error)<br />
|-<br />
| 0x08 || BMP280_TEMP_REG || P. Temperature [Unit:degC]<br />
|-<br />
| 0x09 || BMP280_PRESSURE_REG_L || P. Pressure Low 8 Bit [Unit:Pa]<br />
|-<br />
| 0x0A || BMP280_PRESSURE_REG_M || P. Pressure Mid 8 Bit [Unit:Pa]<br />
|-<br />
| 0x0B || BMP280_PRESSURE_REG_H || P. Pressure High 8 Bit [Unit:Pa]<br />
|-<br />
| 0x0C || BMP280_STATUS || 0(OK) - 1(Error)<br />
|-<br />
| 0x0D || HUMAN_DETECT || 0(No Active Body) - 1(Active Body)<br />
|}<br />
<br />
{| class="wikitable" style="height: 200px"<br />
|-<br />
! scope="col" width="100" |STATUS_REG<br />
! colspan="8"| 0x04 <br />
|-<br />
|Default Value || 0 || 0 || 0 || 0 || 0 || 0 || 0 || 0 <br />
|-<br />
| Description || Reserved || Reserved || Reserved || Reserved || L_FAIL || L_OVR || T_FAIL || T_OVR<br />
|}<br />
<br />
* T_OVR(Read Only)<br />
# Read 1 means Ext. Temperature Overflow.<br />
# Read 0 means Ext. Temperature works well.<br />
* T_FAIL(Read Only)<br />
# Read 1 means Ext. Temperature Not Found.<br />
# Read 0 means Ext. Temperature works well.<br />
* L_OVR(Read Only)<br />
# Read 1 means Light Brightness Overflow.<br />
# Read 0 means Light Brightness works well.<br />
* T_FAIL(Read Only)<br />
# Read 1 means Light Brightness Not Found.<br />
# Read 0 means Light Brightness works well.<br />
<br />
==Configuring I2C(Raspberry Pi)==<br />
Run sudo raspi-config and follow the prompts to install i2c support for the ARM core and linux kernel<br /><br />
Go to '''Interfacing Options'''<br />
[[File:Raspi-config-1.png |none|320px]]<br />
then '''I2C'''<br />
[[File:Raspi-config-2.png |none|320px]]<br />
Enable!<br />
[[File:Raspi-config-3.png |none|320px]]<br />
Done!<br />
[[File:Raspi-config-4.png |none|320px]]<br />
<br />
==Program in Language C(Raspberry Pi)==<br />
* Create source code and name it "sensor.c"<br />
<pre><br />
#include <stdio.h><br />
#include <stdint.h><br />
#include <wiringPi.h><br />
#include <wiringPiI2C.h><br />
<br />
#define TEMP_REG 0x01<br />
#define LIGHT_REG_L 0x02<br />
#define LIGHT_REG_H 0x03<br />
#define STATUS_REG 0x04<br />
#define ON_BOARD_TEMP_REG 0x05<br />
#define ON_BOARD_HUMIDITY_REG 0x06<br />
#define ON_BOARD_SENSOR_ERROR 0x07<br />
#define BMP280_TEMP_REG 0x08<br />
#define BMP280_PRESSURE_REG_L 0x09<br />
#define BMP280_PRESSURE_REG_M 0x0A<br />
#define BMP280_PRESSURE_REG_H 0x0B<br />
#define BMP280_STATUS 0x0C<br />
#define HUMAN_DETECT 0x0D<br />
<br />
uint8_t aReceiveBuf[0x0D + 1];<br />
<br />
int main(void)<br />
{<br />
<br />
int fd;<br />
int i = 0;<br />
fd = wiringPiI2CSetup(0x17);<br />
<br />
if (fd < 0)<br />
printf("Extend board Can not be initialized, please enable I2C and try again!\n", fd);<br />
<br />
for (i = TEMP_REG; i <= HUMAN_DETECT; i++)<br />
{<br />
aReceiveBuf[i] = wiringPiI2CReadReg8(fd, i);<br />
}<br />
<br />
if (aReceiveBuf[STATUS_REG] & 0x01)<br />
{<br />
printf("Off-chip temperature sensor overrange!\n");<br />
}<br />
else if (aReceiveBuf[STATUS_REG] & 0x02)<br />
{<br />
printf("No external temperature sensor!\n");<br />
}<br />
else<br />
{<br />
printf("Current external Sensor Temperature = %d Celsius\n", (int)aReceiveBuf[TEMP_REG]);<br />
}<br />
<br />
if (aReceiveBuf[STATUS_REG] & 0x04)<br />
{<br />
printf("Onboard brightness sensor overrange!\n");<br />
}<br />
else if (aReceiveBuf[STATUS_REG] & 0x08)<br />
{<br />
printf("Onboard brightness sensor failure!\n");<br />
}<br />
else<br />
{<br />
printf("Current onboard sensor brightness = %d Lux\n", (int)(aReceiveBuf[LIGHT_REG_H] << 8) | (aReceiveBuf[LIGHT_REG_L]));<br />
}<br />
<br />
printf("Current onboard sensor temperature = %d Celsius\n", (int)aReceiveBuf[ON_BOARD_TEMP_REG]);<br />
printf("Current onboard sensor humidity = %d %%\n", (int)aReceiveBuf[ON_BOARD_HUMIDITY_REG]);<br />
if (aReceiveBuf[ON_BOARD_SENSOR_ERROR] != 0)<br />
{<br />
printf("Onboard temperature and humidity sensor data may not be up to date!\n");<br />
}<br />
<br />
if (aReceiveBuf[BMP280_STATUS] == 0)<br />
{<br />
<br />
printf("Current barometer temperature = %d Celsius\n", (int)aReceiveBuf[BMP280_TEMP_REG]);<br />
printf("Current barometer pressure = %d Pascal"\n", (int)aReceiveBuf[BMP280_PRESSURE_REG_L] | (int)aReceiveBuf[BMP280_PRESSURE_REG_M] << 8 | (int)aReceiveBuf[BMP280_PRESSURE_REG_H] << 16);<br />
}<br />
else<br />
{<br />
printf("Onboard barometer works abnormally!\n");<br />
}<br />
<br />
if (aReceiveBuf[HUMAN_DETECT] == 1)<br />
{<br />
printf("Live body detected within 5 seconds!\n");<br />
}<br />
else<br />
{<br />
printf("No humans detecte!\n");<br />
}<br />
<br />
return 0;<br />
}<br />
</pre><br />
Compile!<br />
<br />
<code>gcc sensor.c -lwiringPi -o sensor</code><br><br />
<br />
Exec It! <br />
<br />
<code>./sensor</code><br><br />
==Program in Language Python(Raspberry Pi)==<br />
The following code is recommended to be executed using Python 3 and install the '''smbus''' library:<br><br />
<pre><br />
import smbus<br />
<br />
DEVICE_BUS = 1<br />
DEVICE_ADDR = 0x17<br />
<br />
TEMP_REG = 0x01<br />
LIGHT_REG_L = 0x02<br />
LIGHT_REG_H = 0x03<br />
STATUS_REG = 0x04<br />
ON_BOARD_TEMP_REG = 0x05<br />
ON_BOARD_HUMIDITY_REG = 0x06<br />
ON_BOARD_SENSOR_ERROR = 0x07<br />
BMP280_TEMP_REG = 0x08<br />
BMP280_PRESSURE_REG_L = 0x09<br />
BMP280_PRESSURE_REG_M = 0x0A<br />
BMP280_PRESSURE_REG_H = 0x0B<br />
BMP280_STATUS = 0x0C<br />
HUMAN_DETECT = 0x0D<br />
<br />
bus = smbus.SMBus(DEVICE_BUS)<br />
<br />
aReceiveBuf = []<br />
<br />
aReceiveBuf.append(0x00) # 占位符<br />
<br />
for i in range(TEMP_REG,HUMAN_DETECT + 1):<br />
aReceiveBuf.append(bus.read_byte_data(DEVICE_ADDR, i))<br />
<br />
if aReceiveBuf[STATUS_REG] & 0x01 :<br />
print("Off-chip temperature sensor overrange!")<br />
elif aReceiveBuf[STATUS_REG] & 0x02 :<br />
print("No external temperature sensor!")<br />
else :<br />
print("Current off-chip sensor temperature = %d Celsius" % aReceiveBuf[TEMP_REG])<br />
<br />
<br />
if aReceiveBuf[STATUS_REG] & 0x04 :<br />
print("Onboard brightness sensor overrange!")<br />
elif aReceiveBuf[STATUS_REG] & 0x08 :<br />
print("Onboard brightness sensor failure!")<br />
else :<br />
print("Current onboard sensor brightness = %d Lux" % (aReceiveBuf[LIGHT_REG_H] << 8 | aReceiveBuf[LIGHT_REG_L]))<br />
<br />
print("Current onboard sensor temperature = %d Celsius" % aReceiveBuf[ON_BOARD_TEMP_REG])<br />
print("Current onboard sensor humidity = %d %%" % aReceiveBuf[ON_BOARD_HUMIDITY_REG])<br />
<br />
if aReceiveBuf[ON_BOARD_SENSOR_ERROR] != 0 :<br />
print("Onboard temperature and humidity sensor data may not be up to date!")<br />
<br />
if aReceiveBuf[BMP280_STATUS] == 0 :<br />
print("Current barometer temperature = %d Celsius" % aReceiveBuf[BMP280_TEMP_REG])<br />
print("Current barometer pressure = %d pascal" % (aReceiveBuf[BMP280_PRESSURE_REG_L] | aReceiveBuf[BMP280_PRESSURE_REG_M] << 8 | aReceiveBuf[BMP280_PRESSURE_REG_H] << 16))<br />
else :<br />
print("Onboard barometer works abnormally!")<br />
<br />
if aReceiveBuf[HUMAN_DETECT] == 1 :<br />
print("Live body detected within 5 seconds!")<br />
else:<br />
print("No humans detected!")<br />
<br />
</pre><br />
==Program in Language Java(Raspberry Pi)==<br />
Creat a new file named :SensorHub.java and paste following codes:<br />
<pre><br />
import java.io.IOException;<br />
import java.util.Arrays;<br />
<br />
import com.pi4j.io.i2c.I2CBus;<br />
import com.pi4j.io.i2c.I2CDevice;<br />
import com.pi4j.io.i2c.I2CFactory;<br />
import com.pi4j.io.i2c.I2CFactory.UnsupportedBusNumberException;<br />
import com.pi4j.platform.PlatformAlreadyAssignedException;<br />
import com.pi4j.util.Console;<br />
<br />
public class SensorHub {<br />
<br />
//SensorHub Address<br />
public static final int DOCKERPI_SENSORHUB_BOARD = 0x17;<br />
<br />
//SensorHub's functions<br />
public static final byte TEMP_REG = (byte) 0x01; <br />
public static final byte LIGHT_REG_L = (byte) 0x02;<br />
public static final byte LIGHT_REG_H = (byte) 0x03;<br />
public static final byte STATUS_REG = (byte) 0x04;<br />
public static final byte ON_BOARD_TEMP_REG = (byte) 0x05;<br />
public static final byte ON_BOARD_HUMIDITY_REG = (byte) 0x06;<br />
public static final byte ON_BOARD_SENSOR_ERROR = (byte) 0x07;<br />
public static final byte BMP280_TEMP_REG = (byte) 0x08; <br />
public static final byte BMP280_PRESSURE_REG_L = (byte) 0x09;<br />
public static final byte BMP280_PRESSURE_REG_M = (byte) 0x0A;<br />
public static final byte BMP280_PRESSURE_REG_H = (byte) 0X0B;<br />
public static final byte BMP280_STATUS = (byte) 0x0C;<br />
public static final byte HUMAN_DETECT = (byte) 0x0D;<br />
<br />
public static void main(String[] args)<br />
throws InterruptedException, PlatformAlreadyAssignedException, IOException, UnsupportedBusNumberException {<br />
<br />
final Console console = new Console();<br />
<br />
I2CBus i2c = I2CFactory.getInstance(I2CBus.BUS_1);<br />
I2CDevice device = i2c.getDevice(DOCKERPI_SENSORHUB_BOARD);<br />
<br />
int i = 0;<br />
<br />
if(device.read(DOCKERPI_SENSORHUB_BOARD) < 0)<br />
console.println("External board Can not be initialized, please enable I2C and try again!",device.read(DOCKERPI_SENSORHUB_BOARD));<br />
else<br />
console.println("External board has been initialized");<br />
<br />
if((device.read(STATUS_REG) & 0x01) == 0x01)<br />
console.println("off-chip temperature sensor overrange!");<br />
else if((device.read(STATUS_REG) & 0x02) == 0x02)<br />
console.println("No external temperature sensor!");<br />
<br />
else {<br />
console.println("the temp of air is :" + device.read(TEMP_REG) + "centigrade");<br />
} <br />
<br />
if((device.read(STATUS_REG) & 0x04) == 0x04) {<br />
console.println("Onboard brightness sensor overrange!");<br />
}<br />
else if((device.read(STATUS_REG) & 0x08) == 0x08) {<br />
console.println("Onboard brightness sensor failure!");<br />
}<br />
else {<br />
console.println("Current onboard sensor brightness is :" + (device.read(LIGHT_REG_L) | device.read(LIGHT_REG_H) << 8) + "lux");<br />
}<br />
<br />
if(device.read(ON_BOARD_SENSOR_ERROR) == 1)<br />
console.println("Onboard temperature and humidity sensor data may not be up to date!");<br />
<br />
console.println("the temp of sensor on board is :" + device.read(ON_BOARD_TEMP_REG) + "centigrade");<br />
console.println("the humidity of sensor is :" + device.read(ON_BOARD_HUMIDITY_REG) + "%");<br />
<br />
if(device.read(BMP280_STATUS) == 0) {<br />
console.println("the temp of air pressure sensor is :" + device.read(BMP280_TEMP_REG) + "centigrade"); <br />
console.println("the air pressure is :" + (device.read(BMP280_PRESSURE_REG_L) | device.read(BMP280_PRESSURE_REG_M) << 8 | device.read(BMP280_PRESSURE_REG_H) << 16) + "pa");<br />
}<br />
else<br />
console.println("Onboard barometer works abnormally!");<br />
<br />
if(device.read(HUMAN_DETECT) == 1) {<br />
console.println("Live body detected within 5 seconds!");<br />
}<br />
else {<br />
console.println("No humans detecte!");<br />
}<br />
}<br />
<br />
}<br />
</pre><br />
*Compile it and running :<br />
<pre>javac SensorHub.java -classpath .:classes:/opt/pi4j/lib/'*'</pre><br />
<pre>sudo java -classpath .:classes:/opt/pi4j/lib/'*' SensorHub</pre><br />
<br />
==Keywords==<br />
SensorHub， Docker pi, humidity, temperature, airpressure, NTC, pir sensor, DHT11, DHT12, light sensor.</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0065&diff=7652EP-00652020-02-02T04:07:47Z<p>TaterLi: /* Features */</p>
<hr />
<div>==TFT28 Display + Touch Panel + PCB==<br />
==Description==<br />
[[File:Tft28.jpg|left|300px]]<br />
<br style="clear:both;"><br />
KL-TFT028B-PCB is 240x320 dots 2.8" color tft lcd module display with ILI9341 controller and 4-wire resistive touch panel,superior display quality,super wide viewing angle and easily controlled by MCU such as 8051, PIC, AVR, ARDUINO, and ARM .<br><br />
It can be used in any embedded systems,industrial device,security and hand-held equipment which requires display in high quality and colorful image.It supports 8080 8-bit,9-bit,16-bit,18-bit parallel,3-wire,4-wire serial spi interface. FPC with zif connector is easily to assemble or remove.<br><br />
----<br />
<br />
==Features==<br />
*1.Brand New Screen with the production date on the back<br />
*2.IL19341 driver chip is suitable for mutiple circuit design requirments<br />
*3.320X240 resolution, 16-bit color (65,000 colors) <br />
*4.Highly sensitive resistive touch screen<br />
*5.LED backlight with low power consumption and high brightness<br />
*6.Multiple modes are switched by resistance<br />
*7.Screen development manual is available to help with circuit development<br />
----<br />
<br />
==Gallery==<br />
{|<br />
|[[File:Tft28b1.jpg|left|300px]]<br />
|[[File:Tft28b2.jpg|none|300px]]<br />
|[[File:Tft28b3.jpg|none|300px]]<br />
|}<br />
----<br />
{|<br />
|[[File:Tft28b4.jpg|left|300px]]<br />
|[[File:Tft28b5.jpg|none|300px]]<br />
|[[File:Tft28b6.jpg|none|300px]]<br />
|}<br />
----<br />
==Attributions==<br />
{| class="wikitable"<br />
!Parameters !! Values<br />
|-<br />
|Gross Weight (kg) || 0.0200kg<br />
|-<br />
|Manufacturer || Cool-Lite<br />
|-<br />
|Series Number|| KL-TFT028B<br />
|-<br />
|Part Number(Order Number)|| KL-TFT028B<br />
|-<br />
|Connection|| FPC-Connector<br />
|-<br />
|Display Format|| 240x320 Dots 262K<br />
|-<br />
|Sunlight Readable|| No<br />
|-<br />
|Touch Panel Optional|| Yes<br />
|-<br />
|Outline Dimension || 50.2(W)x69.3(H)x4.0(T)mm<br />
|-<br />
|Visual Area|| 44.80x59.20mm<br />
|-<br />
|Active Area|| 43.20(W)x57.60(H)mm<br />
|-<br />
|Character Size|| User Define<br />
|-<br />
|Diagonal Size || 2.8“<br />
|-<br />
|Dot (Pixel) Size|| 0.18x0.18mm<br />
|-<br />
|Dot Pitch|| No<br />
|-<br />
|IC Package|| COG<br />
|-<br />
|IC or Equivalent|| ILI9341V<br />
|-<br />
|Interface|| 8080 8-bit Parallel , 8080 9-bit Parallel , 8080 16-bit Parallel , 8080 18-bit Parallel , 3-Wire SPI , 4-Wire SPI , 16-Bit RGB ,18-Bit RGB<br />
|-<br />
|Display Type|| TFT-LCD Color<br />
|-<br />
|Response Time(Typ) || Less than 5ms with Parallel / Less than 200ms with SPI<br />
|-<br />
|Contrast Ratio(Typ)|| 500:1<br />
|-<br />
|Colors|| 65K/262K<br />
|-<br />
|Viewing Direction|| 12:00<br />
|-<br />
|Viewing Angle Range|| Left:70.0 , Right:70.0 , Up:70.0 , Down:60.0 degree<br />
|-<br />
|Appearance|| RGB on Black<br />
|-<br />
|Brightness(Typ)|| 240cd/m2<br />
|-<br />
|Backlight Color|| White Color<br />
|-<br />
|Backlight Current (Typ)|| No<br />
|-<br />
|Power Supply(Typ/Absolute)|| 2.8V/3.3V<br />
|-<br />
|Supply Current for LCM(Max)|| 24 mA<br />
|-<br />
|Operating Temperature|| -20℃~70℃<br />
|-<br />
|Storage Temperature|| -30℃~80℃<br />
|}<br />
----<br />
==Documentation==<br />
* ILI9341 Datasheet Download：[[File:ILI9341Datasheet.pdf]]<br />
* Demo Code Refference: [ https://github.com/adafruit/Adafruit_ILI9341 ]<br />
----<br />
==Package Includes==<br />
* 1 x TFT28 Display with Touch screen<br />
* 1 x PCB Driver Board <br />
* 3 x 17 Pin header<br />
==Keywords==<br />
* TFT2.8 inch touch screen, touch screen, TFT 2.8 inch, Raspberry Pi 4B, ILI9341,</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7612EP-01162020-01-09T09:54:21Z<p>TaterLi: </p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 3 2.jpg|right|300px]]<br />
[[File:OPENSOURCE.jpg|thumb|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product Function:<br />
{|<br />
|[[File:DOCKERPI 9.jpg|left|320px]]<br />
|}<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Busy(ON)/ Transmission(Blink) / Idle(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7611EP-01162020-01-09T09:53:52Z<p>TaterLi: </p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:OPENSOURCE.jpg|thumb|left]]<br />
[[File:DOCKERPI 3 2.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product Function:<br />
{|<br />
|[[File:DOCKERPI 9.jpg|left|320px]]<br />
|}<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Busy(ON)/ Transmission(Blink) / Idle(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7610EP-01162020-01-09T09:53:34Z<p>TaterLi: /* Open Source Description */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 3 2.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
[[File:OPENSOURCE.jpg|left]]<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product Function:<br />
{|<br />
|[[File:DOCKERPI 9.jpg|left|320px]]<br />
|}<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Busy(ON)/ Transmission(Blink) / Idle(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=File:OPENSOURCE.jpg&diff=7609File:OPENSOURCE.jpg2020-01-09T09:53:18Z<p>TaterLi: </p>
<hr />
<div></div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7608EP-01162020-01-09T09:52:03Z<p>TaterLi: /* Gallery */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 3 2.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product Function:<br />
{|<br />
|[[File:DOCKERPI 9.jpg|left|320px]]<br />
|}<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Busy(ON)/ Transmission(Blink) / Idle(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7607EP-01162020-01-09T09:50:41Z<p>TaterLi: /* Gallery */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 3 2.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product Function<br />
{|<br />
|[[File:DOCKERPI 9.jpg|left|320px]]<br />
|}<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Busy(ON)/ Transmission(Blink) / Idle(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7606EP-01162020-01-09T09:49:20Z<p>TaterLi: </p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 3 2.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
* Product Function<br />
{|<br />
|[[File:DOCKERPI 9.jpg|left|320px]]<br />
|}<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Busy(ON)/ Transmission(Blink) / Idle(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7605EP-01162020-01-09T09:48:43Z<p>TaterLi: /* Gallery */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 3 2.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
* Product Function<br />
{|<br />
|[[File:DOCKERPI 9.jpg|left|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Busy(ON)/ Transmission(Blink) / Idle(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=File:DOCKERPI_9.jpg&diff=7604File:DOCKERPI 9.jpg2020-01-09T09:48:30Z<p>TaterLi: </p>
<hr />
<div></div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7603EP-01162020-01-09T09:44:23Z<p>TaterLi: /* DockerPi-H Board */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 3 2.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Busy(ON)/ Transmission(Blink) / Idle(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=File:DOCKERPI_3_2.jpg&diff=7602File:DOCKERPI 3 2.jpg2020-01-09T09:43:07Z<p>TaterLi: TaterLi uploaded a new version of File:DOCKERPI 3 2.jpg</p>
<hr />
<div></div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7601EP-01162020-01-09T07:24:37Z<p>TaterLi: /* LED Status */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Busy(ON)/ Transmission(Blink) / Idle(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7600EP-01162020-01-09T07:24:18Z<p>TaterLi: /* LED Status */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:Transmission(Blink) IDLE(OFF)<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7599EP-01162020-01-09T07:23:06Z<p>TaterLi: /* LED Status */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
LED2:DATA,Lights up when data is being transmitted.<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7598EP-01162020-01-09T07:22:59Z<p>TaterLi: /* LED Status */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
<br />
<br />
LED2:DATA,Lights up when data is being transmitted.<br />
<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7597EP-01162020-01-09T07:22:48Z<p>TaterLi: /* Bluetooth Interface */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====LED Status====<br />
LED1:Link(ON) / Broadcast(Blink) / Fault(OFF)<br />
LED2:DATA,Lights up when data is being transmitted.<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7596EP-01162020-01-08T08:36:04Z<p>TaterLi: /* Supported platforms */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : sscom.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7595EP-01162020-01-08T08:35:04Z<p>TaterLi: /* Open Source Description */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
Android and IOS app source code provided by NordicSemiconductor.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : putty.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7594EP-01162020-01-08T08:33:28Z<p>TaterLi: /* UART Interface */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : putty.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:'''115200 8N1'''<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7593EP-01162020-01-08T08:33:21Z<p>TaterLi: /* UART Interface */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : putty.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
<br />
Mode:115200 8N1<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7592EP-01162020-01-08T08:32:04Z<p>TaterLi: /* UART Interface */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : putty.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 00 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLihttps://wiki.52pi.com/index.php?title=EP-0116&diff=7591EP-01162020-01-08T08:31:34Z<p>TaterLi: /* Bluetooth Interface */</p>
<hr />
<div>==DockerPi-H Board ==<br />
[[File:DOCKERPI 1.jpg|right|300px]]<br />
<br />
==Open Source Description==<br />
Anyone may use the content of the white paper for non-commercial or educational purposes without permission without the permission of the source and copyright notice, but it may not be used for profit or commercial purposes without permission.<br />
<br />
Custom product LOGO is '''NOT''' allowed without copyright notice,Open source does not mean arbitrary use of trademarks!<br />
<br />
Welcome to submit links to your project(or tips),after our review, we will link your project in GitHub Page.<br />
<br />
==Product Description==<br />
DockerPi-H is one of the DockerPi series expansion boards, which can convert I2C communication of other products in the DockerPi series to UART (TTL) / HID / BLE.<br> <br />
BLE is usually used for the Internet of Things, TTL is usually used for industrial control, HID can communicate without driver.<br><br />
This product design for low power consumption, and can be maintained by only a few mA.<br> <br />
DockerPi-H allows you to operate DockerPi series expansion boards without Raspberry Pi (or similar SBC).<br><br />
It can connect your personal computer to DockerPi expansion boards and also allows you to wirelessly control DockerPi expansion boards.<br><br />
<br />
==Features==<br />
* Open source project (not for commercial distribution)<br />
* DockerPi series products<br />
* Programmable, can work with mobile phones, personal computers, industrial computers, ITX.<br />
* Support BLE, HID, UART-TTL to transmit data<br />
* Support BLE, UART-TTL data in ASCII mode<br />
* Support UART-TTL, HID data in HEX mode<br />
* HID does not require driver support<br />
* It is recommended to install at the bottom of all modules<br />
* Low power design<br />
* BLE module provides FCC / CE certification<br />
<br />
==Supported platforms==<br />
* 1. Tested Mobile devices : IPhone 6s Plus, HUAWEI SCM-AL09<br />
* 2. Tested Platform : putty.exe(Windows Environment), minicom(Linux Environment), pyserial module(via USB-to-TTL cable)<br />
* 3. Supoort Interface : Bluetooth LE Only / USB HID / TTL UART<br />
<br />
==Sources Repository==<br />
* [https://github.com/geeekpi/station DockerPi-H Open Sources Page]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Windows.exe CP2112 Software package for Windows]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Linux.bin CP2112 Softare package for Linux]<br />
* [https://www.silabs.com/documents/public/software/CP2112_Mac.zip CP2112 Software package for MAC]<br />
* [https://github.com/NordicSemiconductor NordicSemiconductor Open Sources Page]<br />
<br />
==Gallery==<br />
* Product View:<br />
{|<br />
|[[File:DOCKERPI 3.jpg|left|320px]]<br />
|[[File:DOCKERPI 2.jpg|none|320px]]<br />
|[[File:DOCKERPI 3 2.jpg|none|320px]]<br />
|}<br />
* Application View:<br />
{|<br />
|[[File:DOCKERPI 4.jpg|left|320px]]<br />
|[[File:DOCKERPI 5.jpg|none|320px]]<br />
|[[File:DOCKERPI 7.jpg|none|320px]]<br />
|}<br />
<br />
==Package Includes==<br />
* 1 x 3-Pin Header <br />
* 4 x M2.5 nut<br />
* 8 x M2.5 Copper stick<br />
* 1 x Acrylic panel<br />
* 1 x USB Micro data cable<br />
<br />
==How to Use==<br />
===HID Interface===<br />
The HID interface is implemented using CP2112, please refer to for more information. [ '''[https://www.silabs.com/interface/usb-bridges/classic/device.cp2112 CP2112 Classic USB to HID Bridge]''' ]<br />
====API Reference====<br />
[[File:An496-hid-usb-to-smbus-api-specification.pdf]]<br />
====Quick Reference====<br />
''HidSmbus_WriteRequest''<br />
<br />
This function writes the specified number of bytes from the supplied buffer to the specified slave device and returns immediately after sending the request to the CP2112.<br />
<br />
''HidSmbus_AddressReadRequest''<br />
<br />
This function intiates a read transfer to the specified slave device address and specifies the address to read from on the device.<br />
<br />
''HidSmbus_ForceReadResponse''<br />
<br />
This function causes the device to send a read response to the host after a read transfer has been issued.<br />
<br />
''HidSmbus_GetReadResponse''<br />
<br />
This function returns the read response to a read request. Read and write timeouts as well as transfer retries can be set using HidSmbus_SetSmbusConfig() as described in HidSmbus_SetSmbusConfig.<br />
<br />
====Test Conditions====<br />
DockerPi SensorHub and DockerPi Relay need to be installed on the top of DockerPi-H.<br />
====Example Code(C#)====<br />
<pre><br />
using System;<br />
using System.Collections.Generic;<br />
using System.ComponentModel;<br />
using System.Data;<br />
using System.Drawing;<br />
using System.Linq;<br />
using System.Text;<br />
using System.Threading;<br />
using System.Threading.Tasks;<br />
using System.Windows.Forms;<br />
using SLAB_HID_TO_SMBUS;<br />
<br />
namespace WindowsFormsApp1<br />
{<br />
public partial class Form1 : Form<br />
{<br />
const ushort vid = 4292; //10C4<br />
const ushort pid = 60048; //EA90<br />
IntPtr connectedDevice;<br />
<br />
const byte RelaySlaveAddress = 0x20;<br />
const byte SensorSlaveAddress = 0x2E;<br />
<br />
ushort RelayStauts = 0;<br />
<br />
<br />
public Form1()<br />
{<br />
InitializeComponent();<br />
uint numDevices = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetNumDevices(ref numDevices, vid, pid);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_Open(ref connectedDevice, 0, vid, pid);<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void RelayButton_Click(object sender, EventArgs e)<br />
{<br />
timer_get_temp.Enabled = false;<br />
<br />
if (RelayStauts == 0)<br />
{<br />
RelayStauts = 1;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0xFF }, 2);<br />
<br />
}<br />
else<br />
{<br />
RelayStauts = 0;<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_WriteRequest(connectedDevice, RelaySlaveAddress, new byte[] { 0x01, 0x00 }, 2);<br />
}<br />
<br />
timer_get_temp.Enabled = true;<br />
}<br />
<br />
private void Timer_get_temp_Tick(object sender, EventArgs e)<br />
{<br />
<br />
byte bytesRead = 0;<br />
byte status = 0;<br />
byte[] readbuff = new byte[61];<br />
<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_AddressReadRequest(connectedDevice, SensorSlaveAddress, 1, 1, new byte[] { 0x01 });<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_ForceReadResponse(connectedDevice, 1);<br />
SLAB_HID_TO_SMBUS.CP2112_DLL.HidSmbus_GetReadResponse(connectedDevice, ref status, readbuff, 61, ref bytesRead);<br />
<br />
if(bytesRead == 1)<br />
{<br />
progressBar.Value = readbuff[0];<br />
}<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
===UART Interface===<br />
Serial interface supports ASCII mode or HEX mode transmission,3V3 TTL as voltage reference.<br />
<br />
You can solder headers or use a jumper wire to connect to your device.<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS || 0A/0D<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA!!END<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || * || 1<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA || 0A/0D<br />
<br />
|-<br />
|}<br />
<br />
====How to Communicate====<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br />
The execution code is: AA011501FF The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
<br />
HEX Mode:<br />
<br />
After sending each instruction, you need to send the '''0A''' or '''0D''' end this transaction.<br />
<br />
[[File:SendByHeX.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
ASCII Mode:<br />
<br />
In ASCII mode, you must check '''AddCrLf'''.<br />
<br />
[[File:SendByASCII.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Read back<br />
The execution code is: AA001501 The meaning of the code is: AA - starting code, DIR parameter 01 means read, 15 means I2C address 0x15, 01 means first LED register.<br />
<br />
If you use HEX mode, you can return the result in HEX mode,If you use ASCII mode, you can return the result in ASCII mode,write operation returns nothing.<br />
<br />
[[File:SendReturn.png|left]]<br />
<br />
<br style="clear:both;"><br />
<br />
===Bluetooth Interface===<br />
Bluetooth interface only provides '''LE only''' protocol support<br />
====Interface Protocol====<br />
Read Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS<br />
|-<br />
|Length|| 1 || 1 || 1 || 1<br />
|-<br />
|Comment|| AA || 00 => i2c-get || I2C_ADDR_RANGE || DATA-ADDRESS<br />
|-<br />
|}<br />
<br />
Write Function:<br />
<br />
{| class="wikitable" style="text-align: center;" <br />
|-<br />
!Function!!Preamble!!Direction!!CHIP-ADDRESS!!DATA-ADDRESS!!DATA<br />
|-<br />
|Length|| 1 || 1 || 1 || 1 || *<br />
|-<br />
|Comment|| AA || 01 => i2c-set || I2C_ADDR_RANGE || DATA-ADDRESS || DATA<br />
<br />
|-<br />
|}<br />
<br />
====Download SDK====<br />
* For IOS user<br />
** nRF Toolbox Download Link: [ https://apps.apple.com/cn/app/nrf-toolbox/id820906058 ]<br />
* For Android user<br />
** nRF Toolbox Download Link: [ https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox ]<br />
* For Sources code user<br />
** Android: [ https://github.com/NordicSemiconductor/Android-nRF-Toolbox ]<br />
** IOS: [ https://github.com/NordicSemiconductor/IOS-nRF-Toolbox ]<br />
====Development Method====<br />
* 1. Download SDK from the links mentioned before and install it to IOS device or Android device.<br />
* 2. Open the nRF Toolbox app<br />
[[File:TIM图片20200108112710.png|left|320px]]<br />
<br style="clear:both;"><br />
* 3. Select "UART" icon and press "Edit" <br />
[[File:TIM图片20200108112702.png|left|320px]]<br />
[[File:TIM图片20200108112706.png|none|320px]]<br />
<br style="clear:both;"><br />
* 4. Select one icon and input the execution code and press OK, and then press the icon will send the code to DockerPi Nightlight board.<br />
** For example: Turn on NightLight board's first LED.<br />
NightLight board's control bus is 1, I2C address is 0x15, and first LED register is 0x01, Turn on it by sending 0xFF<br><br />
The execution code is: AA011501FF <br />
The meaning of the code is: AA - starting code, DIR parameter 01 means write, 15 means I2C address 0x15, 01 means first LED register, FF eq 0xFF means Turn it on.<br />
[[File:TIM图片20200108112658.png|left|320px]]<br />
[[File:TIM图片20200108112654.png|none|320px]]<br />
<br style="clear:both;"><br />
* 5. Press "Connect" to scan the DockerPi-H, and select it.<br />
[[File:TIM图片20200108112645.png|left|320px]]<br />
[[File:TIM图片20200108112637.png|none|320px]]<br />
<br style="clear:both;"><br />
* 6.If the connection is successful, the blue LED will stop blinking and stay on.and you can see log by pressing "show log" link.<br />
[[File:TIM图片20200108112625.png|left|320px]]<br />
<br style="clear:both;"><br />
<br />
==Product Includes==<br />
* 1 x DockerPi-H BlueTooth Board <br />
* 1 x Acrylic Plate<br />
* 1 x 3-Pin Pin Header<br />
* 4 x M2.5 Nut<br />
* 4 x M2.5 Screw<br />
* 4 x M2.5x6 Copper Stick<br />
[[File:DOCKERPI 8.jpg|left|500px]]<br />
<br style="clear:both;"><br />
<br />
==FAQ==<br />
* Q: Should I connect DockerPi-H to my Raspberry Pi to make it work? <br />
A: No, the DockerPi-H is seperated from Raspberry Pi, all you need to do is connect other DockerPi product such as Nightlight board or 4 channel relay board to it and control it via bluetooth.<br />
* Q: Can I just using DockerPi-H to build my own project without other DockerPi product? <br />
A: No, DockerPi-H is built for DockerPi series product so that you should have another DockerPi series product at least.<br />
* Q: A write I2C operation has been performed but nothing return? <br />
A: Only read operations can return.<br />
* Q: Whether the UART interface can be directly connected to the RS232 connection terminal?<br />
A: The voltages are not compatible and you need to level shift.<br />
<br />
==Keywords==<br />
* GeeekPi, dockerPi, dockerPi-H, bluetooth, BLE</div>TaterLi