diff --git a/config/en/mkdocs.yml b/config/en/mkdocs.yml
index db196421..69d1c172 100644
--- a/config/en/mkdocs.yml
+++ b/config/en/mkdocs.yml
@@ -73,35 +73,35 @@ nav:
         - "BliKVM v3 HAT guide": BLIKVM-HAT-guide.md
         - "BliKVM v2 PCIe guide": BLIKVM-PCIE-guide.md
         - "BliKVM v1 CM4 guide": BLIKVM-CM4-guide.md
-        - "First steps": first_steps.md
+        - "First Steps": first_steps.md
         - "FAQ": faq.md
     - "Network":
-        - "Port forwarding": port-forwarding.md
+        - "Port Forwarding": port-forwarding.md
         - "Tailscale VPN": tailscale.md
         - "Set Static IP ": static_ip.md
         - "Wifi Config": wifi.md
     - "Function":
         - "Upgrade": update.md
-        - "keyboard": hid.md
+        - "Keyboard": hid.md
         - "RTC clock": rtc.md
-        - "Flasing OS": flashing_os.md
-        - "OLED display": OLED-display.md
+        - "Flashing OS": flashing_os.md
+        - "OLED Display": OLED-display.md
         - "Expand Filesystem": Expand_Filesystem.md
         - "Serial-over-USB": serial_over_usb.md 
-        - "USB flash Drive": msd.md
+        - "MSD": msd.md
         - "HDMI EDID": edid.md
     - "Installation instructions":
         - "v3 HAT illustrated instructions": BLIHAT-Installation.md
         - "v2 PCIe illustrated instructions": BLIKVM-PCIe-installation.md
     - "Accessories":
-        - "ATX guide": atx-guide.md
+        - "ATX Guide": atx-guide.md
         - "HDMI to CSI & Audio": hdmi-csi-i2s.md
-        - "USB splitter": usb-splitter-guide.md
-        - "Multiport KVM over IP": switch-guide.md
-    - "development":
-        - "make image": make-image.md
-        - "config for PiKVM OS": modify_pikvm_image.md
-        - "v4 dev guide": Dev-BliKVM-v4-Allwinner.md
+        - "USB Splitter": usb-splitter-guide.md
+        - "Multiport KVM-over-IP": switch-guide.md
+    - "Development":
+        - "Make Image": make-image.md
+        - "Config for PiKVM OS": modify_pikvm_image.md
+        - "v4 Allwinner Dev Guide": Dev-BliKVM-v4-Allwinner.md
 plugins:
   - glightbox
   - git-revision-date-localized:
diff --git a/generated/en/404.html b/generated/en/404.html
index a0c0d028..83d9244e 100644
--- a/generated/en/404.html
+++ b/generated/en/404.html
@@ -398,7 +398,7 @@
   
     <li class="md-nav__item">
       <a href="/first_steps/" class="md-nav__link">
-        First steps
+        First Steps
       </a>
     </li>
   
@@ -472,7 +472,7 @@
   
     <li class="md-nav__item">
       <a href="/port-forwarding/" class="md-nav__link">
-        Port forwarding
+        Port Forwarding
       </a>
     </li>
   
@@ -598,7 +598,7 @@
   
     <li class="md-nav__item">
       <a href="/hid/" class="md-nav__link">
-        keyboard
+        Keyboard
       </a>
     </li>
   
@@ -626,7 +626,7 @@
   
     <li class="md-nav__item">
       <a href="/flashing_os/" class="md-nav__link">
-        Flasing OS
+        Flashing OS
       </a>
     </li>
   
@@ -640,7 +640,7 @@
   
     <li class="md-nav__item">
       <a href="/OLED-display/" class="md-nav__link">
-        OLED display
+        OLED Display
       </a>
     </li>
   
@@ -682,7 +682,7 @@
   
     <li class="md-nav__item">
       <a href="/msd/" class="md-nav__link">
-        USB flash Drive
+        MSD
       </a>
     </li>
   
@@ -826,7 +826,7 @@
   
     <li class="md-nav__item">
       <a href="/atx-guide/" class="md-nav__link">
-        ATX guide
+        ATX Guide
       </a>
     </li>
   
@@ -854,7 +854,7 @@
   
     <li class="md-nav__item">
       <a href="/usb-splitter-guide/" class="md-nav__link">
-        USB splitter
+        USB Splitter
       </a>
     </li>
   
@@ -868,7 +868,7 @@
   
     <li class="md-nav__item">
       <a href="/switch-guide/" class="md-nav__link">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
     </li>
   
@@ -908,14 +908,14 @@
       
       
         <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
         </label>
       
-      <nav class="md-nav" aria-label="development" data-md-level="1">
+      <nav class="md-nav" aria-label="Development" data-md-level="1">
         <label class="md-nav__title" for="__nav_6">
           <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
         <ul class="md-nav__list" data-md-scrollfix>
           
@@ -926,7 +926,7 @@
   
     <li class="md-nav__item">
       <a href="/make-image/" class="md-nav__link">
-        make image
+        Make Image
       </a>
     </li>
   
@@ -940,7 +940,7 @@
   
     <li class="md-nav__item">
       <a href="/modify_pikvm_image/" class="md-nav__link">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
     </li>
   
@@ -954,7 +954,7 @@
   
     <li class="md-nav__item">
       <a href="/Dev-BliKVM-v4-Allwinner/" class="md-nav__link">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
     </li>
   
diff --git a/generated/en/BLIHAT-Installation/index.html b/generated/en/BLIHAT-Installation/index.html
index 493a4bc0..39a9334b 100644
--- a/generated/en/BLIHAT-Installation/index.html
+++ b/generated/en/BLIHAT-Installation/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -369,7 +369,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -379,12 +379,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -393,28 +393,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/BLIKVM-CM4-guide/index.html b/generated/en/BLIKVM-CM4-guide/index.html
index 3071be61..e34c2f5b 100644
--- a/generated/en/BLIKVM-CM4-guide/index.html
+++ b/generated/en/BLIKVM-CM4-guide/index.html
@@ -244,7 +244,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -269,7 +269,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -309,7 +309,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -319,12 +319,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -339,7 +339,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -389,7 +389,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -399,12 +399,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -413,28 +413,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -638,13 +638,13 @@ <h2 id="support-1080p60hz-hdmi-input"><strong> Support 1080p60hz HDMI input </st
             </div>
 </div>
 </a>
-<a aria-label="Next: First steps" class="md-footer__link md-footer__link--next" href="../first_steps/" rel="next">
+<a aria-label="Next: First Steps" class="md-footer__link md-footer__link--next" href="../first_steps/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              First steps
+              First Steps
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/BLIKVM-HAT-guide/index.html b/generated/en/BLIKVM-HAT-guide/index.html
index 027bc549..f3ca1865 100644
--- a/generated/en/BLIKVM-HAT-guide/index.html
+++ b/generated/en/BLIKVM-HAT-guide/index.html
@@ -282,7 +282,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -307,7 +307,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -347,7 +347,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -357,12 +357,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -377,7 +377,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -427,7 +427,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -437,12 +437,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -451,28 +451,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/BLIKVM-PCIE-guide/index.html b/generated/en/BLIKVM-PCIE-guide/index.html
index 3724ae81..b4fa9479 100644
--- a/generated/en/BLIKVM-PCIE-guide/index.html
+++ b/generated/en/BLIKVM-PCIE-guide/index.html
@@ -273,7 +273,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -298,7 +298,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -338,7 +338,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -348,12 +348,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -368,7 +368,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -418,7 +418,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -428,12 +428,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -442,28 +442,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/BLIKVM-PCIe-installation/index.html b/generated/en/BLIKVM-PCIe-installation/index.html
index 540d6232..4ed1d4b4 100644
--- a/generated/en/BLIKVM-PCIe-installation/index.html
+++ b/generated/en/BLIKVM-PCIe-installation/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -419,7 +419,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -429,12 +429,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -443,28 +443,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -690,13 +690,13 @@ <h2 id="appendix-3install-wifi-antenna"><strong>Appendix 3.Install wifi antenna<
             </div>
 </div>
 </a>
-<a aria-label="Next: ATX guide" class="md-footer__link md-footer__link--next" href="../atx-guide/" rel="next">
+<a aria-label="Next: ATX Guide" class="md-footer__link md-footer__link--next" href="../atx-guide/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              ATX guide
+              ATX Guide
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/BliKVM-v4-guide/index.html b/generated/en/BliKVM-v4-guide/index.html
index aa392037..496cc828 100644
--- a/generated/en/BliKVM-v4-guide/index.html
+++ b/generated/en/BliKVM-v4-guide/index.html
@@ -244,7 +244,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -269,7 +269,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -309,7 +309,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -319,12 +319,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -339,7 +339,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -389,7 +389,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -399,12 +399,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -413,28 +413,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -586,7 +586,7 @@ <h2 id="dev">Dev</h2>
 <small>
     
       Last update:
-      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">July 17, 2023</span>
+      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">August 13, 2023</span>
 <br/>
         Created:
         <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">July 13, 2023</span>
diff --git a/generated/en/Datasheet-BliKVM-v4/index.html b/generated/en/Datasheet-BliKVM-v4/index.html
index 345c3654..7ea46bb0 100644
--- a/generated/en/Datasheet-BliKVM-v4/index.html
+++ b/generated/en/Datasheet-BliKVM-v4/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -346,7 +346,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -356,12 +356,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -370,28 +370,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/Dev-BliKVM-v4-Allwinner/index.html b/generated/en/Dev-BliKVM-v4-Allwinner/index.html
index d04b5eca..44f6e701 100644
--- a/generated/en/Dev-BliKVM-v4-Allwinner/index.html
+++ b/generated/en/Dev-BliKVM-v4-Allwinner/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>v4 dev guide - BliKVM Handbook</title>
+<title>v4 Allwinner Dev Guide - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              v4 dev guide
+              v4 Allwinner Dev Guide
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -346,7 +346,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -356,12 +356,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -370,33 +370,33 @@
 <li class="md-nav__item md-nav__item--active md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <label class="md-nav__link md-nav__link--active" for="__toc">
-          v4 dev guide
+          v4 Allwinner Dev Guide
           <span class="md-nav__icon md-icon"></span>
 </label>
 <a class="md-nav__link md-nav__link--active" href="./">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 <nav aria-label="Table of contents" class="md-nav md-nav--secondary">
 <label class="md-nav__title" for="__toc">
@@ -690,7 +690,7 @@ <h3 id="lcd-display">LCD Display</h3>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: config for PiKVM OS" class="md-footer__link md-footer__link--prev" href="../modify_pikvm_image/" rel="prev">
+<a aria-label="Previous: Config for PiKVM OS" class="md-footer__link md-footer__link--prev" href="../modify_pikvm_image/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -699,7 +699,7 @@ <h3 id="lcd-display">LCD Display</h3>
 <span class="md-footer__direction">
                 Previous
               </span>
-              config for PiKVM OS
+              Config for PiKVM OS
             </div>
 </div>
 </a>
diff --git a/generated/en/Expand_Filesystem/index.html b/generated/en/Expand_Filesystem/index.html
index 7e9b8b78..514a358a 100644
--- a/generated/en/Expand_Filesystem/index.html
+++ b/generated/en/Expand_Filesystem/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
@@ -324,7 +324,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -374,7 +374,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -384,12 +384,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -398,28 +398,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -559,7 +559,7 @@ <h2 id="method-3-use-script">Method 3: Use script</h2>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: OLED display" class="md-footer__link md-footer__link--prev" href="../OLED-display/" rel="prev">
+<a aria-label="Previous: OLED Display" class="md-footer__link md-footer__link--prev" href="../OLED-display/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -568,7 +568,7 @@ <h2 id="method-3-use-script">Method 3: Use script</h2>
 <span class="md-footer__direction">
                 Previous
               </span>
-              OLED display
+              OLED Display
             </div>
 </div>
 </a>
diff --git a/generated/en/OLED-display/index.html b/generated/en/OLED-display/index.html
index 6dcbae76..6bb2d77b 100644
--- a/generated/en/OLED-display/index.html
+++ b/generated/en/OLED-display/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>OLED display - BliKVM Handbook</title>
+<title>OLED Display - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              OLED display
+              OLED Display
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,13 +276,13 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <a class="md-nav__link md-nav__link--active" href="./">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -297,7 +297,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -347,7 +347,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -357,12 +357,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -371,28 +371,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -482,7 +482,7 @@ <h1 id="oled-display">OLED display</h1>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: Flasing OS" class="md-footer__link md-footer__link--prev" href="../flashing_os/" rel="prev">
+<a aria-label="Previous: Flashing OS" class="md-footer__link md-footer__link--prev" href="../flashing_os/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -491,7 +491,7 @@ <h1 id="oled-display">OLED display</h1>
 <span class="md-footer__direction">
                 Previous
               </span>
-              Flasing OS
+              Flashing OS
             </div>
 </div>
 </a>
diff --git a/generated/en/atx-guide/index.html b/generated/en/atx-guide/index.html
index 16143210..32f5830c 100644
--- a/generated/en/atx-guide/index.html
+++ b/generated/en/atx-guide/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>ATX guide - BliKVM Handbook</title>
+<title>ATX Guide - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              ATX guide
+              ATX Guide
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -347,11 +347,11 @@
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <label class="md-nav__link md-nav__link--active" for="__toc">
-          ATX guide
+          ATX Guide
           <span class="md-nav__icon md-icon"></span>
 </label>
 <a class="md-nav__link md-nav__link--active" href="./">
-        ATX guide
+        ATX Guide
       </a>
 <nav aria-label="Table of contents" class="md-nav md-nav--secondary">
 <label class="md-nav__title" for="__toc">
@@ -399,12 +399,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -413,28 +413,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/atx/index.html b/generated/en/atx/index.html
index 6b4f1ea9..3fe6a5f7 100644
--- a/generated/en/atx/index.html
+++ b/generated/en/atx/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -346,7 +346,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -356,12 +356,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -370,28 +370,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/edid/index.html b/generated/en/edid/index.html
index c8b41bbe..c6c41f92 100644
--- a/generated/en/edid/index.html
+++ b/generated/en/edid/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
@@ -379,7 +379,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -389,12 +389,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -403,28 +403,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -575,7 +575,7 @@ <h2 id="custom-edid">Custom EDID</h2>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: USB flash Drive" class="md-footer__link md-footer__link--prev" href="../msd/" rel="prev">
+<a aria-label="Previous: MSD" class="md-footer__link md-footer__link--prev" href="../msd/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -584,7 +584,7 @@ <h2 id="custom-edid">Custom EDID</h2>
 <span class="md-footer__direction">
                 Previous
               </span>
-              USB flash Drive
+              MSD
             </div>
 </div>
 </a>
diff --git a/generated/en/faq/index.html b/generated/en/faq/index.html
index 5377daab..e2ea38fb 100644
--- a/generated/en/faq/index.html
+++ b/generated/en/faq/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
@@ -274,7 +274,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -314,7 +314,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -324,12 +324,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -344,7 +344,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -394,7 +394,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -404,12 +404,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -418,28 +418,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -692,7 +692,7 @@ <h2 id="raspberry-problem">Raspberry problem</h2>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: First steps" class="md-footer__link md-footer__link--prev" href="../first_steps/" rel="prev">
+<a aria-label="Previous: First Steps" class="md-footer__link md-footer__link--prev" href="../first_steps/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -701,17 +701,17 @@ <h2 id="raspberry-problem">Raspberry problem</h2>
 <span class="md-footer__direction">
                 Previous
               </span>
-              First steps
+              First Steps
             </div>
 </div>
 </a>
-<a aria-label="Next: Port forwarding" class="md-footer__link md-footer__link--next" href="../port-forwarding/" rel="next">
+<a aria-label="Next: Port Forwarding" class="md-footer__link md-footer__link--next" href="../port-forwarding/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              Port forwarding
+              Port Forwarding
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/first_steps/index.html b/generated/en/first_steps/index.html
index c2a36c20..67b05cd4 100644
--- a/generated/en/first_steps/index.html
+++ b/generated/en/first_steps/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>First steps - BliKVM Handbook</title>
+<title>First Steps - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              First steps
+              First Steps
             
           </span>
 </div>
@@ -202,11 +202,11 @@
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <label class="md-nav__link md-nav__link--active" for="__toc">
-          First steps
+          First Steps
           <span class="md-nav__icon md-icon"></span>
 </label>
 <a class="md-nav__link md-nav__link--active" href="./">
-        First steps
+        First Steps
       </a>
 <nav aria-label="Table of contents" class="md-nav md-nav--secondary">
 <label class="md-nav__title" for="__toc">
@@ -264,7 +264,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -304,7 +304,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -314,12 +314,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -334,7 +334,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -384,7 +384,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -394,12 +394,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -408,28 +408,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/flashing_os/index.html b/generated/en/flashing_os/index.html
index ebdfff46..3d09f62d 100644
--- a/generated/en/flashing_os/index.html
+++ b/generated/en/flashing_os/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>Flasing OS - BliKVM Handbook</title>
+<title>Flashing OS - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              Flasing OS
+              Flashing OS
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -277,11 +277,11 @@
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <label class="md-nav__link md-nav__link--active" for="__toc">
-          Flasing OS
+          Flashing OS
           <span class="md-nav__icon md-icon"></span>
 </label>
 <a class="md-nav__link md-nav__link--active" href="./">
-        Flasing OS
+        Flashing OS
       </a>
 <nav aria-label="Table of contents" class="md-nav md-nav--secondary">
 <label class="md-nav__title" for="__toc">
@@ -337,7 +337,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -352,7 +352,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -402,7 +402,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -412,12 +412,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -426,28 +426,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -637,7 +637,7 @@ <h3 id="using-rpi-imager-linux-macos-and-windows">Using RPi Imager (Linux, MacOS
 <small>
     
       Last update:
-      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">July 15, 2023</span>
+      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">August 13, 2023</span>
 <br/>
         Created:
         <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">June 4, 2022</span>
@@ -666,13 +666,13 @@ <h3 id="using-rpi-imager-linux-macos-and-windows">Using RPi Imager (Linux, MacOS
             </div>
 </div>
 </a>
-<a aria-label="Next: OLED display" class="md-footer__link md-footer__link--next" href="../OLED-display/" rel="next">
+<a aria-label="Next: OLED Display" class="md-footer__link md-footer__link--next" href="../OLED-display/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              OLED display
+              OLED Display
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/hdmi-csi-i2s/index.html b/generated/en/hdmi-csi-i2s/index.html
index 149b88b8..1cf013ad 100644
--- a/generated/en/hdmi-csi-i2s/index.html
+++ b/generated/en/hdmi-csi-i2s/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -346,7 +346,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
@@ -423,12 +423,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -437,28 +437,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -888,7 +888,7 @@ <h2 id="purchase-link"><strong>Purchase link</strong></h2>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: ATX guide" class="md-footer__link md-footer__link--prev" href="../atx-guide/" rel="prev">
+<a aria-label="Previous: ATX Guide" class="md-footer__link md-footer__link--prev" href="../atx-guide/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -897,17 +897,17 @@ <h2 id="purchase-link"><strong>Purchase link</strong></h2>
 <span class="md-footer__direction">
                 Previous
               </span>
-              ATX guide
+              ATX Guide
             </div>
 </div>
 </a>
-<a aria-label="Next: USB splitter" class="md-footer__link md-footer__link--next" href="../usb-splitter-guide/" rel="next">
+<a aria-label="Next: USB Splitter" class="md-footer__link md-footer__link--next" href="../usb-splitter-guide/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              USB splitter
+              USB Splitter
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/hid/index.html b/generated/en/hid/index.html
index d49cef39..3403bb58 100644
--- a/generated/en/hid/index.html
+++ b/generated/en/hid/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>keyboard - BliKVM Handbook</title>
+<title>Keyboard - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              keyboard
+              Keyboard
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -267,7 +267,7 @@
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <a class="md-nav__link md-nav__link--active" href="./">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -277,12 +277,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -297,7 +297,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -347,7 +347,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -357,12 +357,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -371,28 +371,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/index.html b/generated/en/index.html
index f133777d..2a1cbd62 100644
--- a/generated/en/index.html
+++ b/generated/en/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -346,7 +346,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -356,12 +356,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -370,28 +370,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/make-image/index.html b/generated/en/make-image/index.html
index 07b0a0cc..524abcd8 100644
--- a/generated/en/make-image/index.html
+++ b/generated/en/make-image/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>make image - BliKVM Handbook</title>
+<title>Make Image - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              make image
+              Make Image
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -346,7 +346,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -356,12 +356,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -370,29 +370,29 @@
 <li class="md-nav__item md-nav__item--active md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <a class="md-nav__link md-nav__link--active" href="./">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -458,7 +458,7 @@ <h1 id="make-your-own-image">Make your own image</h1>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: Multiport KVM over IP" class="md-footer__link md-footer__link--prev" href="../switch-guide/" rel="prev">
+<a aria-label="Previous: Multiport KVM-over-IP" class="md-footer__link md-footer__link--prev" href="../switch-guide/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -467,17 +467,17 @@ <h1 id="make-your-own-image">Make your own image</h1>
 <span class="md-footer__direction">
                 Previous
               </span>
-              Multiport KVM over IP
+              Multiport KVM-over-IP
             </div>
 </div>
 </a>
-<a aria-label="Next: config for PiKVM OS" class="md-footer__link md-footer__link--next" href="../modify_pikvm_image/" rel="next">
+<a aria-label="Next: Config for PiKVM OS" class="md-footer__link md-footer__link--next" href="../modify_pikvm_image/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              config for PiKVM OS
+              Config for PiKVM OS
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/modify_pikvm_image/index.html b/generated/en/modify_pikvm_image/index.html
index d2765316..9e1cb829 100644
--- a/generated/en/modify_pikvm_image/index.html
+++ b/generated/en/modify_pikvm_image/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>config for PiKVM OS - BliKVM Handbook</title>
+<title>Config for PiKVM OS - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              config for PiKVM OS
+              Config for PiKVM OS
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -346,7 +346,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -356,12 +356,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -370,28 +370,28 @@
 <li class="md-nav__item md-nav__item--active md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <label class="md-nav__link md-nav__link--active" for="__toc">
-          config for PiKVM OS
+          Config for PiKVM OS
           <span class="md-nav__icon md-icon"></span>
 </label>
 <a class="md-nav__link md-nav__link--active" href="./">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 <nav aria-label="Table of contents" class="md-nav md-nav--secondary">
 <label class="md-nav__title" for="__toc">
@@ -414,7 +414,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -518,7 +518,7 @@ <h2 id="check-edid-file-for-1080p60hz-input"><strong>Check EDID file for 1080P60
 <small>
     
       Last update:
-      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">March 8, 2023</span>
+      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">August 13, 2023</span>
 <br/>
         Created:
         <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">March 8, 2023</span>
@@ -534,7 +534,7 @@ <h2 id="check-edid-file-for-1080p60hz-input"><strong>Check EDID file for 1080P60
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: make image" class="md-footer__link md-footer__link--prev" href="../make-image/" rel="prev">
+<a aria-label="Previous: Make Image" class="md-footer__link md-footer__link--prev" href="../make-image/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -543,17 +543,17 @@ <h2 id="check-edid-file-for-1080p60hz-input"><strong>Check EDID file for 1080P60
 <span class="md-footer__direction">
                 Previous
               </span>
-              make image
+              Make Image
             </div>
 </div>
 </a>
-<a aria-label="Next: v4 dev guide" class="md-footer__link md-footer__link--next" href="../Dev-BliKVM-v4-Allwinner/" rel="next">
+<a aria-label="Next: v4 Allwinner Dev Guide" class="md-footer__link md-footer__link--next" href="../Dev-BliKVM-v4-Allwinner/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              v4 dev guide
+              v4 Allwinner Dev Guide
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/msd/index.html b/generated/en/msd/index.html
index 07268427..3d4f8ac7 100644
--- a/generated/en/msd/index.html
+++ b/generated/en/msd/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>USB flash Drive - BliKVM Handbook</title>
+<title>MSD - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              USB flash Drive
+              MSD
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -297,11 +297,11 @@
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <label class="md-nav__link md-nav__link--active" for="__toc">
-          USB flash Drive
+          MSD
           <span class="md-nav__icon md-icon"></span>
 </label>
 <a class="md-nav__link md-nav__link--active" href="./">
-        USB flash Drive
+        MSD
       </a>
 <nav aria-label="Table of contents" class="md-nav md-nav--secondary">
 <label class="md-nav__title" for="__toc">
@@ -369,7 +369,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -379,12 +379,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -393,28 +393,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/port-forwarding/index.html b/generated/en/port-forwarding/index.html
index 1a9221d8..4669bdee 100644
--- a/generated/en/port-forwarding/index.html
+++ b/generated/en/port-forwarding/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>Port forwarding - BliKVM Handbook</title>
+<title>Port Forwarding - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              Port forwarding
+              Port Forwarding
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -227,7 +227,7 @@
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <a class="md-nav__link md-nav__link--active" href="./">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -267,7 +267,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -277,12 +277,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -297,7 +297,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -347,7 +347,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -357,12 +357,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -371,28 +371,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/rtc/index.html b/generated/en/rtc/index.html
index b6deb06a..52f2097e 100644
--- a/generated/en/rtc/index.html
+++ b/generated/en/rtc/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
@@ -299,12 +299,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -319,7 +319,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -369,7 +369,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -379,12 +379,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -393,28 +393,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -539,7 +539,7 @@ <h2 id="blikvm-v4-pcf8563"><strong>BliKVM V4 - pcf8563</strong></h2>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: keyboard" class="md-footer__link md-footer__link--prev" href="../hid/" rel="prev">
+<a aria-label="Previous: Keyboard" class="md-footer__link md-footer__link--prev" href="../hid/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -548,17 +548,17 @@ <h2 id="blikvm-v4-pcf8563"><strong>BliKVM V4 - pcf8563</strong></h2>
 <span class="md-footer__direction">
                 Previous
               </span>
-              keyboard
+              Keyboard
             </div>
 </div>
 </a>
-<a aria-label="Next: Flasing OS" class="md-footer__link md-footer__link--next" href="../flashing_os/" rel="next">
+<a aria-label="Next: Flashing OS" class="md-footer__link md-footer__link--next" href="../flashing_os/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              Flasing OS
+              Flashing OS
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/search/search_index.json b/generated/en/search/search_index.json
index 370ff2d3..e1a27a61 100644
--- a/generated/en/search/search_index.json
+++ b/generated/en/search/search_index.json
@@ -1 +1 @@
-{"config":{"indexing":"full","lang":["en","ja","ru"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"BLIKVM Overview BLIKVM is an open-source KVM, it has three versions: CM4 Board, Raspberry HAT, PCIE Board. This device helps to manage servers or workstations remotely, regardless of the health of the operating system or whether one is installed. You can fix any problem, configure the BIOS, and even reinstall the OS using the virtual CD-ROM or Flash Drive. Here you will find comprehensive information about all aspects of the operation of BLIKVM. Join our BLIKVM Discord Community for Support, FAQ & News! FEATURE BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 H616 SOC Raspberry CM4 Raspberry CM4 Raspberry 4B Allwinner H616 Supported resolutions 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI Capture TC358743 TC358743 TC358743 MS2131 HDMI Loop Through No No No Yes POE No Yes Yes Yes DC-IN No No No Yes USB-C Power Yes Yes Yes Yes USB Power/Data Splitter Yes Yes(external) Yes Yes Serial Console No Yes Yes Yes ATX controls Yes Yes Yes Yes BIOS controls Yes Yes Yes Yes Open source system Yes Yes Yes Yes Reinstall the controlled computer system Yes Yes Yes Yes FAN Yes(Not support PWM controls) Yes Yes Optional(default with heat sink) Display Module OLED 128x64 white OLED 128x32 white OLED 128x64 white LCD 240x240 color Real Time Clock Yes(DS1307) Yes(PCF8563) Yes(PCF8563) Yes(PCF8563) Case Metallic Black No Metallic Black White Blue Orange(1U rack compatible) Metallic Black(1U rack compatible) Buzzer No No No Yes Custom button No No No Yes Software update Yes Yes Yes Yes 32GB SD Card Yes (OS included) Yes (OS included) Yes (OS included) Yes (OS included) HDMI backpower mitigation No Yes Yes Yes Professional technical support Yes Yes Yes Yes Features Video capture (1080P 60Hz) Keyboard forwarding Mouse forwarding ATX Fan Control Fullscreen mode Paste text from clipboard VPN support Mass Storage Drive (emulate a CD-ROM or Flash Drive) Multiport KVM over IP OLED to display system info, like temp, uptime, IP Password authentication Support multiple languages Wake-on-LAN Guide 1.BLIKVM v1 CM4 version 2.BLIKVM v2 PCIE version 3.BLIKVM v3 HAT version 4.BliKVM v4 Allwinner version","title":"BLIKVM Overview"},{"location":"#blikvm-overview","text":"BLIKVM is an open-source KVM, it has three versions: CM4 Board, Raspberry HAT, PCIE Board. This device helps to manage servers or workstations remotely, regardless of the health of the operating system or whether one is installed. You can fix any problem, configure the BIOS, and even reinstall the OS using the virtual CD-ROM or Flash Drive. Here you will find comprehensive information about all aspects of the operation of BLIKVM. Join our BLIKVM Discord Community for Support, FAQ & News! FEATURE BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 H616 SOC Raspberry CM4 Raspberry CM4 Raspberry 4B Allwinner H616 Supported resolutions 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI Capture TC358743 TC358743 TC358743 MS2131 HDMI Loop Through No No No Yes POE No Yes Yes Yes DC-IN No No No Yes USB-C Power Yes Yes Yes Yes USB Power/Data Splitter Yes Yes(external) Yes Yes Serial Console No Yes Yes Yes ATX controls Yes Yes Yes Yes BIOS controls Yes Yes Yes Yes Open source system Yes Yes Yes Yes Reinstall the controlled computer system Yes Yes Yes Yes FAN Yes(Not support PWM controls) Yes Yes Optional(default with heat sink) Display Module OLED 128x64 white OLED 128x32 white OLED 128x64 white LCD 240x240 color Real Time Clock Yes(DS1307) Yes(PCF8563) Yes(PCF8563) Yes(PCF8563) Case Metallic Black No Metallic Black White Blue Orange(1U rack compatible) Metallic Black(1U rack compatible) Buzzer No No No Yes Custom button No No No Yes Software update Yes Yes Yes Yes 32GB SD Card Yes (OS included) Yes (OS included) Yes (OS included) Yes (OS included) HDMI backpower mitigation No Yes Yes Yes Professional technical support Yes Yes Yes Yes","title":"BLIKVM Overview"},{"location":"#features","text":"Video capture (1080P 60Hz) Keyboard forwarding Mouse forwarding ATX Fan Control Fullscreen mode Paste text from clipboard VPN support Mass Storage Drive (emulate a CD-ROM or Flash Drive) Multiport KVM over IP OLED to display system info, like temp, uptime, IP Password authentication Support multiple languages Wake-on-LAN","title":"Features"},{"location":"#guide","text":"1.BLIKVM v1 CM4 version 2.BLIKVM v2 PCIE version 3.BLIKVM v3 HAT version 4.BliKVM v4 Allwinner version","title":"Guide"},{"location":"BLIHAT-Installation/","text":"BLIHAT Installation Guide 1.Unpack and take out the devices Open the protective bag 2.Install the main device Flip to back Open the case Flip to back, unscrew the two screws on the back Open the protective bag and take out the parts Install Micro SD card Install the FFC cable Install the HAT on Raspberry Pi 4 Install four Hex Spacers Install the C790 module, use the long screws you just removed Install the audio cable Stick a heat conductive sheet on the back of the Raspberry Pi 4 , tear off the protective film of the sheet Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"v3 HAT illustrated instructions"},{"location":"BLIHAT-Installation/#blihat-installation-guide","text":"","title":"BLIHAT Installation Guide"},{"location":"BLIHAT-Installation/#1unpack-and-take-out-the-devices","text":"Open the protective bag","title":"1.Unpack and take out the devices"},{"location":"BLIHAT-Installation/#2install-the-main-device","text":"Flip to back Open the case Flip to back, unscrew the two screws on the back Open the protective bag and take out the parts Install Micro SD card Install the FFC cable Install the HAT on Raspberry Pi 4 Install four Hex Spacers Install the C790 module, use the long screws you just removed Install the audio cable Stick a heat conductive sheet on the back of the Raspberry Pi 4 , tear off the protective film of the sheet Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"2.Install the main device"},{"location":"BLIKVM-CM4-guide/","text":"BLIKVM-CM4 version guide BLIKVM-CM4-V2.2 Video Installation requirements If you have an assembly kit, you will need the following things Raspberry CM4 with 1Gb RAM or more. USB-C to USB-A cable. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit (5.1V 3A USB-C, recommended by the Raspberry Pi). Power supply You must use USB-C to USB-A cable. Use USB-C to USB-C cable can't work, This is an incompatibility in the hardware design and will be fixed in a later version. Basic setup 1. Flash the memory card or eMMC 2.Build BLIKVM according to the video instruction or review the instructions: Video Guide: Metal case step by step Geerling: Engineering Test video Ortimo: BLIKVM with Raspberry PI CM4 16GB EMMC setup 3. Connect BLIKVM to the computer according to the diagram below: HDMI IN and otg port must be connected to the computer. ATX too, but it\u2019s optional, read below. There should be no USB hub between BLIKVM and the computer, as some UEFI/BIOS cannot detect them at the boot stage. BLIKVM supports 1080p60Hz or lower about HDMI source. Connect Ethernet to the network and PWR IN to the BLIKVM power supply. ATX connection To manage the power of your computer, you will connect CN-ATX port to the computer.The user can use the ATX cable provided with the product to connect the product and the motherboard ATX switch of the controlled computer. The length of the ATX cable is 60CM, you can also use the double female Dupont cables. Hardware Features 1\u3001HDMI IN port with I2S 2\u3001ATX controller interface (power on/off, reboot control, PWR and HDD ACT LEDs) 3\u3001USB3.0 port x 2 4\u3001USB-C OTG 5\u3001Real Time Clock (RTC) 6\u3001Gigabit Ethernet 7\u3001Activity LED 8\u3001Micro SD Card socket 9\u3001Power LED 10\u3001I2C display connector 11\u3001nRPI_BOOT Jumper 12\u3001USB-C power input 13\u3001FAN connector 5V 14\u3001CSI-2 date lanes switch 15\u3001CM4 Module Connectors Size 12cm x 7cm x 3.5cm Support 1080p60hz HDMI input First in V2.2 version, there is CSI channel switch. This switch is switch 2 csi channels or 4 csi channels. In other versions, the switch is obsolete. Newer keeps the factory state, ignore this switch. Only flip the switch when the device is powered off, otherwise it may cause permanent damage! The four small switches should be up or down at the same time. The video encoding function of the Raspberry Pi is implemented by the HDMI-to-CSI bridge chip Toshiba TC358743, which supports up to 4 CSI-2 data lanes. The camera interface of Raspberry Pi 4B only supports 2 CSI-2 date lanes(up to 1080P50Hz), Raspberry Pi CM4 can support 4 CSI-2 date lanes(up to 1080P60Hz). Currently, PiKVM only uses two CSI-2 channels. 1\u3001 find edid file: rw vim /etc/kvmd/tc358743-edid.hex write the following 1080p 60Hz EDID into the file tc358743-edid.hex. 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C 2\u3001add csi 4 lanes Edit /boot/config.txt, modify \"dtoverlay=tc358743\" to \"dtoverlay=tc358743,4lane=1\" vim /boot/config.txt ro Now, reboot blikvm, and you can test 1080p 60hz input.","title":"BliKVM v1 CM4 guide"},{"location":"BLIKVM-CM4-guide/#blikvm-cm4-version-guide","text":"BLIKVM-CM4-V2.2 Video","title":"BLIKVM-CM4 version guide"},{"location":"BLIKVM-CM4-guide/#installation-requirements","text":"If you have an assembly kit, you will need the following things Raspberry CM4 with 1Gb RAM or more. USB-C to USB-A cable. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit (5.1V 3A USB-C, recommended by the Raspberry Pi). Power supply You must use USB-C to USB-A cable. Use USB-C to USB-C cable can't work, This is an incompatibility in the hardware design and will be fixed in a later version.","title":"Installation requirements"},{"location":"BLIKVM-CM4-guide/#basic-setup","text":"1. Flash the memory card or eMMC 2.Build BLIKVM according to the video instruction or review the instructions: Video Guide: Metal case step by step Geerling: Engineering Test video Ortimo: BLIKVM with Raspberry PI CM4 16GB EMMC setup 3. Connect BLIKVM to the computer according to the diagram below: HDMI IN and otg port must be connected to the computer. ATX too, but it\u2019s optional, read below. There should be no USB hub between BLIKVM and the computer, as some UEFI/BIOS cannot detect them at the boot stage. BLIKVM supports 1080p60Hz or lower about HDMI source. Connect Ethernet to the network and PWR IN to the BLIKVM power supply.","title":"Basic setup"},{"location":"BLIKVM-CM4-guide/#atx-connection","text":"To manage the power of your computer, you will connect CN-ATX port to the computer.The user can use the ATX cable provided with the product to connect the product and the motherboard ATX switch of the controlled computer. The length of the ATX cable is 60CM, you can also use the double female Dupont cables.","title":"ATX connection"},{"location":"BLIKVM-CM4-guide/#hardware-features","text":"1\u3001HDMI IN port with I2S 2\u3001ATX controller interface (power on/off, reboot control, PWR and HDD ACT LEDs) 3\u3001USB3.0 port x 2 4\u3001USB-C OTG 5\u3001Real Time Clock (RTC) 6\u3001Gigabit Ethernet 7\u3001Activity LED 8\u3001Micro SD Card socket 9\u3001Power LED 10\u3001I2C display connector 11\u3001nRPI_BOOT Jumper 12\u3001USB-C power input 13\u3001FAN connector 5V 14\u3001CSI-2 date lanes switch 15\u3001CM4 Module Connectors","title":"Hardware Features"},{"location":"BLIKVM-CM4-guide/#size","text":"12cm x 7cm x 3.5cm","title":"Size"},{"location":"BLIKVM-CM4-guide/#support-1080p60hz-hdmi-input","text":"First in V2.2 version, there is CSI channel switch. This switch is switch 2 csi channels or 4 csi channels. In other versions, the switch is obsolete. Newer keeps the factory state, ignore this switch. Only flip the switch when the device is powered off, otherwise it may cause permanent damage! The four small switches should be up or down at the same time. The video encoding function of the Raspberry Pi is implemented by the HDMI-to-CSI bridge chip Toshiba TC358743, which supports up to 4 CSI-2 data lanes. The camera interface of Raspberry Pi 4B only supports 2 CSI-2 date lanes(up to 1080P50Hz), Raspberry Pi CM4 can support 4 CSI-2 date lanes(up to 1080P60Hz). Currently, PiKVM only uses two CSI-2 channels. 1\u3001 find edid file: rw vim /etc/kvmd/tc358743-edid.hex write the following 1080p 60Hz EDID into the file tc358743-edid.hex. 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C 2\u3001add csi 4 lanes Edit /boot/config.txt, modify \"dtoverlay=tc358743\" to \"dtoverlay=tc358743,4lane=1\" vim /boot/config.txt ro Now, reboot blikvm, and you can test 1080p 60hz input.","title":"Support 1080p60hz HDMI input"},{"location":"BLIKVM-HAT-guide/","text":"BLIKVM HAT version guide Introduction BLIKVM hat Video The Raspberry Pi IPKVM HAT is an add-on board for Raspberry Pi 4, made especially for KVM Over IP. BLIKVM-RPI4 is a Raspberry Pi 4 PoE KVM HAT. This product\u2019s key features include video capture, ATX adapter,PoE, OLED and RTC. The product has a customized metal case to dissipate heat and provide protection for the HAT. The product can be easily installed on a standard 1U rack. The product is currently perfectly compatible with blikvm image and pikvm image. Installation requirements If you have an assembly kit, you will need the following things Raspberry Pi 4B with 1Gb RAM or more. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit & cable(5.1V 3A USB-C, recommended by the Raspberry Pi). Basic setup 1. Flash the memory card or eMMC 2.Build BLIKVM according to the video instruction or review the illustrated instructions : Video Guide: Metal case step by step 3. Install the ATX adapter board The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. Choose one as needed Use Dupont cables to connect ATX adapter board to motherboard and chassis panel. There are clear pin definitions on the board for easy wiring. Mount the ATX adapter board to the case shell Use a RJ45 network cable to connect the board to the CN-ATX interface of the HAT 4. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the HAT with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 5. Install the USB cable Connect the RPI4 port to the Raspberry Pi 4 Connect the USB port to the controlled computer When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. 6. Test Powered by PoE, the HAT is connected to the router via the network cable The screen displays the current status of the device, including the machine's IP address Access the IP address of the HAT in the browser. Enjoy! Specification HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@50fps. Fixed HDMI back power issue. CN-ATX The CN-ATX interface is connected to the ATX adapter board (an accessory for the HAT)through a network cable, which can turn on, off, and restart the controlled computer. Display A white OLED display with a resolution of 128x32, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. PoE Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A Plug in the PoE jumper cap to enable PoE power supply FAN The IPKVM HAT is fitted with a small fan that is controlled by your Raspberry Pi via GPIO12. Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi via I2C. The coin cell battery is installed under the HDMI IN module. Accessories ATX adapter board This board is connected to the switch port on the motherboard of the controlled computer with DuPont cables. The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. USB/PWR splitter Connect the RPI4 port to your Raspberry Pi 4. Connect the USB port to the controlled computer. When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. Metal case The metal case protects the HAT and improve heat dissipation. There are clear port markings on the case. The case can be easily installed on a standard 1U rack. List Product List Raspberry Pi IPKVM HAT 1 ATX adapter board 1 USB/PWR splitter 1 HDMI pass-through EDID emulator 1 Metal case 1 32G TF card 1 USB Type-C to USB Type-C Cable 30cm 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 List of items prepared by the user Raspberry Pi 4 1 RJ45 network cable 2 USB Type-A to USB Type-C Cable 2 HDMI cable 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"BliKVM v3 HAT guide"},{"location":"BLIKVM-HAT-guide/#blikvm-hat-version-guide","text":"","title":"BLIKVM HAT version guide"},{"location":"BLIKVM-HAT-guide/#introduction","text":"BLIKVM hat Video The Raspberry Pi IPKVM HAT is an add-on board for Raspberry Pi 4, made especially for KVM Over IP. BLIKVM-RPI4 is a Raspberry Pi 4 PoE KVM HAT. This product\u2019s key features include video capture, ATX adapter,PoE, OLED and RTC. The product has a customized metal case to dissipate heat and provide protection for the HAT. The product can be easily installed on a standard 1U rack. The product is currently perfectly compatible with blikvm image and pikvm image.","title":"Introduction"},{"location":"BLIKVM-HAT-guide/#installation-requirements","text":"If you have an assembly kit, you will need the following things Raspberry Pi 4B with 1Gb RAM or more. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit & cable(5.1V 3A USB-C, recommended by the Raspberry Pi).","title":"Installation requirements"},{"location":"BLIKVM-HAT-guide/#basic-setup","text":"1. Flash the memory card or eMMC 2.Build BLIKVM according to the video instruction or review the illustrated instructions : Video Guide: Metal case step by step 3. Install the ATX adapter board The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. Choose one as needed Use Dupont cables to connect ATX adapter board to motherboard and chassis panel. There are clear pin definitions on the board for easy wiring. Mount the ATX adapter board to the case shell Use a RJ45 network cable to connect the board to the CN-ATX interface of the HAT 4. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the HAT with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 5. Install the USB cable Connect the RPI4 port to the Raspberry Pi 4 Connect the USB port to the controlled computer When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. 6. Test Powered by PoE, the HAT is connected to the router via the network cable The screen displays the current status of the device, including the machine's IP address Access the IP address of the HAT in the browser. Enjoy!","title":"Basic setup"},{"location":"BLIKVM-HAT-guide/#specification","text":"HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@50fps. Fixed HDMI back power issue. CN-ATX The CN-ATX interface is connected to the ATX adapter board (an accessory for the HAT)through a network cable, which can turn on, off, and restart the controlled computer. Display A white OLED display with a resolution of 128x32, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. PoE Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A Plug in the PoE jumper cap to enable PoE power supply FAN The IPKVM HAT is fitted with a small fan that is controlled by your Raspberry Pi via GPIO12. Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi via I2C. The coin cell battery is installed under the HDMI IN module.","title":"Specification"},{"location":"BLIKVM-HAT-guide/#accessories","text":"","title":"Accessories"},{"location":"BLIKVM-HAT-guide/#atx-adapter-board","text":"This board is connected to the switch port on the motherboard of the controlled computer with DuPont cables. The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket.","title":"ATX adapter board"},{"location":"BLIKVM-HAT-guide/#usbpwr-splitter","text":"Connect the RPI4 port to your Raspberry Pi 4. Connect the USB port to the controlled computer. When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply.","title":"USB/PWR splitter"},{"location":"BLIKVM-HAT-guide/#hdmi-pass-through-edid-emulator","text":"If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer.","title":"HDMI pass-through EDID emulator"},{"location":"BLIKVM-HAT-guide/#metal-case","text":"The metal case protects the HAT and improve heat dissipation. There are clear port markings on the case. The case can be easily installed on a standard 1U rack.","title":"Metal case"},{"location":"BLIKVM-HAT-guide/#list","text":"","title":"List"},{"location":"BLIKVM-HAT-guide/#product-list","text":"Raspberry Pi IPKVM HAT 1 ATX adapter board 1 USB/PWR splitter 1 HDMI pass-through EDID emulator 1 Metal case 1 32G TF card 1 USB Type-C to USB Type-C Cable 30cm 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Phillips screwdriver 1 Cross Wrench Sleeve 1","title":"Product List"},{"location":"BLIKVM-HAT-guide/#list-of-items-prepared-by-the-user","text":"Raspberry Pi 4 1 RJ45 network cable 2 USB Type-A to USB Type-C Cable 2 HDMI cable 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"List of items prepared by the user"},{"location":"BLIKVM-PCIE-guide/","text":"BLIKVM PCIe Introduction BLIKVM PCIe is a PCIe add-in card based on Raspberry Pi CM4 for KVM Over IP. This product\u2019s key features include video capture, ATX controller, PoE, OLED , UART and RTC. The card has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. The product is currently perfectly compatible with blikvm image and pikvm image. Installation requirements You will need the following things Raspberry Pi CM4(if you order PCIe card only). PoE-sourcing equipment or 5V/3A USB adapter. CR1220 coin cell battery. Basic setup 1. If you have an assembly kit, Flash the memory card or eMMC 2.Build BLIKVM according to the illustrated instructions : Geerling: Engineering Test video Craft Computing: Never Pay For IPMI Again - BliKVM Review Specification hardware feature list HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@60fps. Fixed HDMI back power issue. USB-PC The BLIKVM PCIe card provides two USB interfaces, one is PC-IN (type c interface) and the other is USB-PC2 (pin interface). The purpose of these two interfaces is to connect to the USB of the controlled computer, used to control the mouse and keyboard. At the same time, only one interface can be used. The purpose of designing two interfaces is to directly use USB PC2 when the user's PC host has a row pin USB interface, which will make the wiring more concise. POWER-IN When using PoE power supply, there is no need to connect the PWR-IN port. When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. ETHERNET-PoE Gigabit Ethernet port Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A ATX-Connecter Connect to power control interface on the motherboard of the controlled computer with DuPont cables. It can turn on, off, and restart the controlled computer. The pin is defined on the printing of the PCIe board, BTN means button. According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the PCIe board. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and PCIe. See the following figure for the connection relationship\uff1a OLED Display A white OLED display with a resolution of 128x64, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. FAN The Card HAT is fitted with a small fan that is controlled by your Raspberry Pi CM4 via GPIO12. BOOT Fit jumper to disable eMMC Boot Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi CM4 via I2C. The CR1220 battery is installed under the HDMI IN module. UART Connect the serial port to debug your Raspberry Pi CM4. The uart of Raspberry Pi CM4. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. Connect serial cable wires to G T R connectors on the PCIe board. NOTE: black wire = Ground, whiTe = Tx, and gReen = Rx; For specific methods, please refer to this document . Accessories HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. VGA-HDMI module When your device does not have an HDMI output interface, you can use a VGA to HDMI module. USB to TTL module Connect your computer usb interface with the serial port of BLIKVM to debug your Raspberry Pi CM4. Fan Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card. Dimensions Test Video BLIKVM hardware PCIe version is tested wonderful based on pikvm software. Notes To prevent the CM4 module from contacting the SD card holder, do not remove the insulating tape List Product List BLIKVM PCIe card version 1 BLIKVM PCIe add-in card 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 BLIKVM PCIe plug-n-play version 1 BLIKVM PCIe add-in card 1 CM4 102000 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 List of items prepared by the user Raspberry Pi CM4(if you order PCIe card only) 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"BliKVM v2 PCIe guide"},{"location":"BLIKVM-PCIE-guide/#blikvm-pcie","text":"","title":"BLIKVM PCIe"},{"location":"BLIKVM-PCIE-guide/#introduction","text":"BLIKVM PCIe is a PCIe add-in card based on Raspberry Pi CM4 for KVM Over IP. This product\u2019s key features include video capture, ATX controller, PoE, OLED , UART and RTC. The card has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. The product is currently perfectly compatible with blikvm image and pikvm image.","title":"Introduction"},{"location":"BLIKVM-PCIE-guide/#installation-requirements","text":"You will need the following things Raspberry Pi CM4(if you order PCIe card only). PoE-sourcing equipment or 5V/3A USB adapter. CR1220 coin cell battery.","title":"Installation requirements"},{"location":"BLIKVM-PCIE-guide/#basic-setup","text":"1. If you have an assembly kit, Flash the memory card or eMMC 2.Build BLIKVM according to the illustrated instructions : Geerling: Engineering Test video Craft Computing: Never Pay For IPMI Again - BliKVM Review","title":"Basic setup"},{"location":"BLIKVM-PCIE-guide/#specification","text":"hardware feature list HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@60fps. Fixed HDMI back power issue. USB-PC The BLIKVM PCIe card provides two USB interfaces, one is PC-IN (type c interface) and the other is USB-PC2 (pin interface). The purpose of these two interfaces is to connect to the USB of the controlled computer, used to control the mouse and keyboard. At the same time, only one interface can be used. The purpose of designing two interfaces is to directly use USB PC2 when the user's PC host has a row pin USB interface, which will make the wiring more concise. POWER-IN When using PoE power supply, there is no need to connect the PWR-IN port. When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. ETHERNET-PoE Gigabit Ethernet port Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A ATX-Connecter Connect to power control interface on the motherboard of the controlled computer with DuPont cables. It can turn on, off, and restart the controlled computer. The pin is defined on the printing of the PCIe board, BTN means button. According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the PCIe board. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and PCIe. See the following figure for the connection relationship\uff1a OLED Display A white OLED display with a resolution of 128x64, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. FAN The Card HAT is fitted with a small fan that is controlled by your Raspberry Pi CM4 via GPIO12. BOOT Fit jumper to disable eMMC Boot Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi CM4 via I2C. The CR1220 battery is installed under the HDMI IN module. UART Connect the serial port to debug your Raspberry Pi CM4. The uart of Raspberry Pi CM4. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. Connect serial cable wires to G T R connectors on the PCIe board. NOTE: black wire = Ground, whiTe = Tx, and gReen = Rx; For specific methods, please refer to this document .","title":"Specification"},{"location":"BLIKVM-PCIE-guide/#accessories","text":"HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. VGA-HDMI module When your device does not have an HDMI output interface, you can use a VGA to HDMI module. USB to TTL module Connect your computer usb interface with the serial port of BLIKVM to debug your Raspberry Pi CM4. Fan Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card.","title":"Accessories"},{"location":"BLIKVM-PCIE-guide/#dimensions","text":"","title":"Dimensions"},{"location":"BLIKVM-PCIE-guide/#test-video","text":"BLIKVM hardware PCIe version is tested wonderful based on pikvm software.","title":"Test Video"},{"location":"BLIKVM-PCIE-guide/#notes","text":"To prevent the CM4 module from contacting the SD card holder, do not remove the insulating tape","title":"Notes"},{"location":"BLIKVM-PCIE-guide/#list","text":"","title":"List"},{"location":"BLIKVM-PCIE-guide/#product-list","text":"BLIKVM PCIe card version 1 BLIKVM PCIe add-in card 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 BLIKVM PCIe plug-n-play version 1 BLIKVM PCIe add-in card 1 CM4 102000 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1","title":"Product List"},{"location":"BLIKVM-PCIE-guide/#list-of-items-prepared-by-the-user","text":"Raspberry Pi CM4(if you order PCIe card only) 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"List of items prepared by the user"},{"location":"BLIKVM-PCIe-installation/","text":"BLIKVM PCIe CM4 Installation Guide 1.Unpack and take out the devices Product List 2.Install the main device Install CM4 and 4 Hex spacers (This article takes CM4 lite as an example, using the image in the Micro SD card, CM4 eMMC user need to burn the image by yourself.)Stick a heat conductive sheet on the top of CM4 , tear off the protective film of the sheet. Install metal heatsink The main device installation is complete. 3.Connect USB and ATX The motherboard used in this article is Asus H520M-E, the interface definition of different motherboards may be different, please refer to your motherboard manual. 4.Connect OLED The OLED you received does not have a bracket installed. Please refer to the picture for installation. In addition, OLED support is made of acrylic material, which needs to be used after removing the protective film on the surface. The above is the installation steps, and the effect of not tearing the film is as follows. In actual use, please remove the protective film. 5.Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the product with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 6.Connect the network cable Gigabit Ethernet port standard: IEEE 802.3af PoE input voltage:37v-57v. When using PoE power supply, there is no need to connect the PWR-IN port. 7.Connect PWR-IN When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. 8.Test OLED screen showing device IP and other information. Access the IP address in browser. After passing the test, install the product into the computer case. 9.Install the product into the computer case Disconnect power and wiring, install the product on the motherboard, and reconnect the cables after installation is complete. The color of ATX cable received in different batches may be different. Please directly refer to the pin definition for connection Enjoy! Appendix 1.Install a low profile PCIe I/O bracket Note Appendix 2.Install the cooling fan Usually the metal heatsink is sufficient, the cooling fan is not necessary. The cooling fan is controlled by CM4 via GPIO12. Appendix 3.Install wifi antenna Note","title":"v2 PCIe illustrated instructions"},{"location":"BLIKVM-PCIe-installation/#blikvm-pcie-cm4-installation-guide","text":"","title":"BLIKVM PCIe CM4 Installation Guide"},{"location":"BLIKVM-PCIe-installation/#1unpack-and-take-out-the-devices","text":"Product List","title":"1.Unpack and take out the devices"},{"location":"BLIKVM-PCIe-installation/#2install-the-main-device","text":"Install CM4 and 4 Hex spacers (This article takes CM4 lite as an example, using the image in the Micro SD card, CM4 eMMC user need to burn the image by yourself.)Stick a heat conductive sheet on the top of CM4 , tear off the protective film of the sheet. Install metal heatsink The main device installation is complete.","title":"2.Install the main device"},{"location":"BLIKVM-PCIe-installation/#3connect-usb-and-atx","text":"The motherboard used in this article is Asus H520M-E, the interface definition of different motherboards may be different, please refer to your motherboard manual.","title":"3.Connect USB and ATX"},{"location":"BLIKVM-PCIe-installation/#4connect-oled","text":"The OLED you received does not have a bracket installed. Please refer to the picture for installation. In addition, OLED support is made of acrylic material, which needs to be used after removing the protective film on the surface. The above is the installation steps, and the effect of not tearing the film is as follows. In actual use, please remove the protective film.","title":"4.Connect OLED"},{"location":"BLIKVM-PCIe-installation/#5connect-the-hdmi-cable","text":"Connect the HDMI output port of the computer directly to the HDMI IN port of the product with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer.","title":"5.Connect the HDMI cable"},{"location":"BLIKVM-PCIe-installation/#6connect-the-network-cable","text":"Gigabit Ethernet port standard: IEEE 802.3af PoE input voltage:37v-57v. When using PoE power supply, there is no need to connect the PWR-IN port.","title":"6.Connect the network cable"},{"location":"BLIKVM-PCIe-installation/#7connect-pwr-in","text":"When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply.","title":"7.Connect PWR-IN"},{"location":"BLIKVM-PCIe-installation/#8test","text":"OLED screen showing device IP and other information. Access the IP address in browser. After passing the test, install the product into the computer case.","title":"8.Test"},{"location":"BLIKVM-PCIe-installation/#9install-the-product-into-the-computer-case","text":"Disconnect power and wiring, install the product on the motherboard, and reconnect the cables after installation is complete. The color of ATX cable received in different batches may be different. Please directly refer to the pin definition for connection Enjoy!","title":"9.Install the product into the computer case"},{"location":"BLIKVM-PCIe-installation/#appendix-1install-a-low-profile-pcie-io-bracket","text":"Note","title":"Appendix 1.Install a low profile PCIe  I/O bracket"},{"location":"BLIKVM-PCIe-installation/#appendix-2install-the-cooling-fan","text":"Usually the metal heatsink is sufficient, the cooling fan is not necessary. The cooling fan is controlled by CM4 via GPIO12.","title":"Appendix 2.Install the cooling fan"},{"location":"BLIKVM-PCIe-installation/#appendix-3install-wifi-antenna","text":"Note","title":"Appendix 3.Install wifi antenna"},{"location":"BliKVM-v4-guide/","text":"BliKVM v4 Allwinner BliKVM v4 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM V4 Datasheet Features Video capture (HDMI, support 4K@30Hz input) Keyboard forwarding Mouse forwarding HDMI video loop through ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE & DC Support WiFi Serial console port 1.33 inch color display Real Time Clock (RTC) Installation Requirements In addition to the v4 kit, you will need the following equipment: Power adapter (5V 3A, USB-A port, or 12V 2A DC port). If you plan to use PoE (Power over Ethernet) or if the USB ports on your controlled computers provide sufficient power, a separate power adapter is not required. HDMI cables (at least one). If you also need to use the HDMI loop-out interface, you will need two cables. Ethernet cable(s) (provide based on your requirements). One cable is required for using the ATX power switch function, and one cable is required for using the Ethernet connection. USB-C to USB-A cable (for mouse and keyboard data transmission). info \"Video Guide: Unpacking and connecting case step by step\" Installation Steps 1. Open the v4 kit package and connect the BliKVM to the controlled computer according to the connection diagram shown below: ATX Connection Please refer to the ATX Connection Guide . 2. Once all the cables are connected, power on the BliKVM. Wait until the display shows the interface, indicating that the device has started up successfully. 3. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. 4. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 5. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience! Video Mode v4 supports a maximum video input of 4K30Hz, and the default transmission resolution is 1920x1080. Product List BLIKVM v4 1 WiFi Antenna 1 ATX adapter board 1 ATX Dupont Cables 8pin Male to Male 60cm 1 ATX Dupont Cables 8pin Male to Female 60cm 1 1U Rack Mounting Ears 2 M2.5x5 Screws 8 Silicone Bumper Pellets 1 Dev If you want to develop or port software on v4 hardware yourself, you can refer to this hardware resource description .","title":"BliKVM v4 Allwinner guide"},{"location":"BliKVM-v4-guide/#blikvm-v4-allwinner","text":"BliKVM v4 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM V4 Datasheet","title":"BliKVM v4 Allwinner"},{"location":"BliKVM-v4-guide/#features","text":"Video capture (HDMI, support 4K@30Hz input) Keyboard forwarding Mouse forwarding HDMI video loop through ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE & DC Support WiFi Serial console port 1.33 inch color display Real Time Clock (RTC)","title":"Features"},{"location":"BliKVM-v4-guide/#installation-requirements","text":"In addition to the v4 kit, you will need the following equipment: Power adapter (5V 3A, USB-A port, or 12V 2A DC port). If you plan to use PoE (Power over Ethernet) or if the USB ports on your controlled computers provide sufficient power, a separate power adapter is not required. HDMI cables (at least one). If you also need to use the HDMI loop-out interface, you will need two cables. Ethernet cable(s) (provide based on your requirements). One cable is required for using the ATX power switch function, and one cable is required for using the Ethernet connection. USB-C to USB-A cable (for mouse and keyboard data transmission). info \"Video Guide: Unpacking and connecting case step by step\"","title":"Installation Requirements"},{"location":"BliKVM-v4-guide/#installation-steps","text":"1. Open the v4 kit package and connect the BliKVM to the controlled computer according to the connection diagram shown below: ATX Connection Please refer to the ATX Connection Guide . 2. Once all the cables are connected, power on the BliKVM. Wait until the display shows the interface, indicating that the device has started up successfully. 3. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. 4. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 5. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience!","title":"Installation Steps"},{"location":"BliKVM-v4-guide/#video-mode","text":"v4 supports a maximum video input of 4K30Hz, and the default transmission resolution is 1920x1080.","title":"Video Mode"},{"location":"BliKVM-v4-guide/#product-list","text":"BLIKVM v4 1 WiFi Antenna 1 ATX adapter board 1 ATX Dupont Cables 8pin Male to Male 60cm 1 ATX Dupont Cables 8pin Male to Female 60cm 1 1U Rack Mounting Ears 2 M2.5x5 Screws 8 Silicone Bumper Pellets 1","title":"Product List"},{"location":"BliKVM-v4-guide/#dev","text":"If you want to develop or port software on v4 hardware yourself, you can refer to this hardware resource description .","title":"Dev"},{"location":"Datasheet-BliKVM-v4/","text":"BliKVM v4 Allwinner (H616 SOC) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! Connectivity diagram 1 USB 2.0 port 10 Antenna interface 2 Power Input 5V 3A & UART 11 RJ45 100M Ethernet port & PoE 3 RJ45 ATX control port 12 Display 1.33 inch LCD 4 HDMI video loop through port 13 Power LED (red) 5 USB-PC port 14 User defined button SW1 6 Power Input 12V 2A 5.5*2.1mm 15 ACT LED (green) 7 HDMI video input port 16 Display ON/OFF button 8 HDMI input status LED (green) 17 Micro SD card slot 9 HDMI output status LED (yellow) Specifications Parameter name Characteristics Power 5V 3A 5V port, USB-PC port 12V 2A 12V port PoE Power over Ethernet (IEEE802.3af compliant) 48V DC Connectivity/Interfaces HDMI-IN HDMI video input port HDMI-OUT HDMI video loop through port USB-PC Keyboard, mouse, mass storage, and other external device emulation) ATX Turn on/off or restart the controlled computer WiFi & Bluetooth IEEE802.11 b/g/n + BLE4.2 Micro SD card slot Persistent storage for OS and your data 5V port 5V 3A power or serial console management port Displays and indicators LED indicators Power LED, ACT LED, HDMI input status LED (green)\uff0c HDMI output status LED (yellow) LCD display LCD 240x240 1.33 inch User defined button SW1 Buzzer Find me Video Supported resolutions Up to 4k@30Hz Video compression methods MJPEG Core Chip ALLWINNER H616 RAM 1GB Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 100 (L) x 134 (W) x 44.4 (H) mm Weight 0.45 kg Dimensions Schematic Diagram","title":"BliKVM v4 Allwinner (H616 SOC)"},{"location":"Datasheet-BliKVM-v4/#blikvm-v4-allwinner-h616-soc","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"BliKVM v4 Allwinner (H616 SOC)"},{"location":"Datasheet-BliKVM-v4/#connectivity-diagram","text":"1 USB 2.0 port 10 Antenna interface 2 Power Input 5V 3A & UART 11 RJ45 100M Ethernet port & PoE 3 RJ45 ATX control port 12 Display 1.33 inch LCD 4 HDMI video loop through port 13 Power LED (red) 5 USB-PC port 14 User defined button SW1 6 Power Input 12V 2A 5.5*2.1mm 15 ACT LED (green) 7 HDMI video input port 16 Display ON/OFF button 8 HDMI input status LED (green) 17 Micro SD card slot 9 HDMI output status LED (yellow)","title":"Connectivity diagram"},{"location":"Datasheet-BliKVM-v4/#specifications","text":"Parameter name Characteristics Power 5V 3A 5V port, USB-PC port 12V 2A 12V port PoE Power over Ethernet (IEEE802.3af compliant) 48V DC Connectivity/Interfaces HDMI-IN HDMI video input port HDMI-OUT HDMI video loop through port USB-PC Keyboard, mouse, mass storage, and other external device emulation) ATX Turn on/off or restart the controlled computer WiFi & Bluetooth IEEE802.11 b/g/n + BLE4.2 Micro SD card slot Persistent storage for OS and your data 5V port 5V 3A power or serial console management port Displays and indicators LED indicators Power LED, ACT LED, HDMI input status LED (green)\uff0c HDMI output status LED (yellow) LCD display LCD 240x240 1.33 inch User defined button SW1 Buzzer Find me Video Supported resolutions Up to 4k@30Hz Video compression methods MJPEG Core Chip ALLWINNER H616 RAM 1GB Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 100 (L) x 134 (W) x 44.4 (H) mm Weight 0.45 kg","title":"Specifications"},{"location":"Datasheet-BliKVM-v4/#dimensions-schematic-diagram","text":"","title":"Dimensions Schematic Diagram"},{"location":"Dev-BliKVM-v4-Allwinner/","text":"Dev BliKVM v4 Allwinner (H616 SOC) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! System Block Diagram Functional Module Panel Function Pin Description Button SW1 GPIOI1(257) Press for high level Button SW1 GPIOI2(258) Press for high level LED ACT GPIOI5(261) Low level enable LED LED PWR 3V3 PWR LED is always on after power on ATX Function Pin Description LED-PWR GPIOH10(234) Light on for high level LED-HDD GPIOH9(233) Light on for high level SW-PWR GPIOH4(228) High level enable SW-RST GPIOI16(272) High level enable BUZZER Function Pin Description Buzzer GPIOI15(271) High level enable FAN Function Pin Description Fan GPIOI13(269) High level enable LCD Display 1.33-inch LCD display module, driver chip ST7789, resolution 240x240. Function Pin Description LCD_EN GPIOI4(260) Backlight high level enable LCD_RST GPIOI6(262) Reset Low level enable LCD_DC GPIOI3(259) Data/command control pin SPI1_CS GPIOH5 SPI1_CLK GPIOH6 SPI1_MOSI GPIOH7 GND GND 3V3 3V3","title":"v4 dev guide"},{"location":"Dev-BliKVM-v4-Allwinner/#dev-blikvm-v4-allwinner-h616-soc","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"Dev BliKVM v4 Allwinner (H616 SOC)"},{"location":"Dev-BliKVM-v4-Allwinner/#system-block-diagram","text":"","title":"System Block Diagram"},{"location":"Dev-BliKVM-v4-Allwinner/#functional-module","text":"","title":"Functional Module"},{"location":"Dev-BliKVM-v4-Allwinner/#panel","text":"Function Pin Description Button SW1 GPIOI1(257) Press for high level Button SW1 GPIOI2(258) Press for high level LED ACT GPIOI5(261) Low level enable LED LED PWR 3V3 PWR LED is always on after power on","title":"Panel"},{"location":"Dev-BliKVM-v4-Allwinner/#atx","text":"Function Pin Description LED-PWR GPIOH10(234) Light on for high level LED-HDD GPIOH9(233) Light on for high level SW-PWR GPIOH4(228) High level enable SW-RST GPIOI16(272) High level enable","title":"ATX"},{"location":"Dev-BliKVM-v4-Allwinner/#buzzer","text":"Function Pin Description Buzzer GPIOI15(271) High level enable","title":"BUZZER"},{"location":"Dev-BliKVM-v4-Allwinner/#fan","text":"Function Pin Description Fan GPIOI13(269) High level enable","title":"FAN"},{"location":"Dev-BliKVM-v4-Allwinner/#lcd-display","text":"1.33-inch LCD display module, driver chip ST7789, resolution 240x240. Function Pin Description LCD_EN GPIOI4(260) Backlight high level enable LCD_RST GPIOI6(262) Reset Low level enable LCD_DC GPIOI3(259) Data/command control pin SPI1_CS GPIOH5 SPI1_CLK GPIOH6 SPI1_MOSI GPIOH7 GND GND 3V3 3V3","title":"LCD Display"},{"location":"Expand_Filesystem/","text":"Expand Filesystem If you find that the free space of the raspberry pi SD card or eMMC is smaller than the capacity of the actual SD card or eMMC, you need to do the following to expand the raspberry pi. If you find that the system does not have the raspi config tool, you can use Method 2 (use the GParted partition tool). Method 1: Use raspi-config tool If you are using a mirror after June 2023 and have added a third read-write partition, this method is no longer applicable. Please refer to method 2 and method 3. 1. open raspi-config. sudo raspi-config 2. choose Advancd Options\uff1a 3. choose Expand Filesystem\uff1a 4. Ok: 5. Execute the command resize2fs /dev/mmcblk0p2 in the terminal to see that the SD card has been successfully expanded. Method 2: Use GParted tool 1. Connect the SD card or EMMc that has burned the image to the computer through USB. Take the GParted partition tool under Linux as an example. Other platforms also have similar partition tools. Open GParted software and select SD card: 2. By observing the partition of the SD card in the above figure, we can find that 2.01GB and 21.87GB of space are unused before and after the sdb3 partition, which is the space we want to expand. Select the sdb3 partition and click Resize. 3. You can drag the white partition of sdb3 to the leftmost and rightmost, or fill in 25958 with \"Previous Free Space\" as \"0\" and \"New Size\" as \"Maximum Size\", and then click Resize in the lower right corner. Then click OK to see that all unused space of sd has been used. 4. Insert the SD card into the device and start it. Method 3: Use script If you are using a BliKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand. sh on any path, and write the following content to expand.sh #!/bin/bash set -x resize_mmcblk0p3() { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100% resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" If you are using a PiKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand. sh on any path, and write the following content to expand.sh #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab; then part=$(grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}') # shellcheck disable=SC2206 splitted=(${part//=/ }) if [ \"${splitted[0]}\" == LABEL ]; then label=${splitted[1]} part=$(blkid -c /dev/null -L \"$label\") else label=PIMSD fi unset splitted disk=/dev/$(lsblk -no pkname \"$part\") npart=$(cat \"/sys/class/block/${part//\\/dev\\//}/partition\") umount \"$part\" parted \"$disk\" -a optimal -s resizepart \"$npart\" 100% yes | mkfs.ext4 -L \"$label\" -F -m 0 \"$part\" mount \"$part\" unset disk part npart label fi 2. Execute 'bash expand. sh' on the terminal and wait for the execution to complete.","title":"Expand Filesystem"},{"location":"Expand_Filesystem/#expand-filesystem","text":"If you find that the free space of the raspberry pi SD card or eMMC is smaller than the capacity of the actual SD card or eMMC, you need to do the following to expand the raspberry pi. If you find that the system does not have the raspi config tool, you can use Method 2 (use the GParted partition tool).","title":"Expand Filesystem"},{"location":"Expand_Filesystem/#method-1-use-raspi-config-tool","text":"If you are using a mirror after June 2023 and have added a third read-write partition, this method is no longer applicable. Please refer to method 2 and method 3. 1. open raspi-config. sudo raspi-config 2. choose Advancd Options\uff1a 3. choose Expand Filesystem\uff1a 4. Ok: 5. Execute the command resize2fs /dev/mmcblk0p2 in the terminal to see that the SD card has been successfully expanded.","title":"Method 1: Use raspi-config tool"},{"location":"Expand_Filesystem/#method-2-use-gparted-tool","text":"1. Connect the SD card or EMMc that has burned the image to the computer through USB. Take the GParted partition tool under Linux as an example. Other platforms also have similar partition tools. Open GParted software and select SD card: 2. By observing the partition of the SD card in the above figure, we can find that 2.01GB and 21.87GB of space are unused before and after the sdb3 partition, which is the space we want to expand. Select the sdb3 partition and click Resize. 3. You can drag the white partition of sdb3 to the leftmost and rightmost, or fill in 25958 with \"Previous Free Space\" as \"0\" and \"New Size\" as \"Maximum Size\", and then click Resize in the lower right corner. Then click OK to see that all unused space of sd has been used. 4. Insert the SD card into the device and start it.","title":"Method 2: Use GParted tool"},{"location":"Expand_Filesystem/#method-3-use-script","text":"If you are using a BliKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand. sh on any path, and write the following content to expand.sh #!/bin/bash set -x resize_mmcblk0p3() { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100% resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" If you are using a PiKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand. sh on any path, and write the following content to expand.sh #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab; then part=$(grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}') # shellcheck disable=SC2206 splitted=(${part//=/ }) if [ \"${splitted[0]}\" == LABEL ]; then label=${splitted[1]} part=$(blkid -c /dev/null -L \"$label\") else label=PIMSD fi unset splitted disk=/dev/$(lsblk -no pkname \"$part\") npart=$(cat \"/sys/class/block/${part//\\/dev\\//}/partition\") umount \"$part\" parted \"$disk\" -a optimal -s resizepart \"$npart\" 100% yes | mkfs.ext4 -L \"$label\" -F -m 0 \"$part\" mount \"$part\" unset disk part npart label fi 2. Execute 'bash expand. sh' on the terminal and wait for the execution to complete.","title":"Method 3: Use script"},{"location":"OLED-display/","text":"OLED display Follow the method below to enable OLED. If you use PiKVM official image, log in to PiKVM and run these commands: # rw # systemctl enable --now kvmd-oled //Enable OLED # ro If the oled still can't work, you need to check whether there has \"dtparam=i2c_arm=on\" in \"/boot/config.txt\" file, and whether there has \"i2c-dev\" in \"/etc/modules-load.d/i2c.conf\" file. If not, please create and add them. If it still does not work after the above configuration, please burn the image provided by blikvm for testing to check whether the OLED hardware is damaged. BLIKVM CM4 version OLED display The product comes standard with a monochrome OLED display with a resolution of 128x64, and the chip is SSD1306. The user connects the display to the product with the wiring of the display. The module is connected to CM4 through the I^2^C interface. The wiring definition is shown in the following table. This is a library for the monochrome OLEDs based on SSD1306 drivers. Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C)","title":"OLED display"},{"location":"OLED-display/#oled-display","text":"Follow the method below to enable OLED. If you use PiKVM official image, log in to PiKVM and run these commands: # rw # systemctl enable --now kvmd-oled //Enable OLED # ro If the oled still can't work, you need to check whether there has \"dtparam=i2c_arm=on\" in \"/boot/config.txt\" file, and whether there has \"i2c-dev\" in \"/etc/modules-load.d/i2c.conf\" file. If not, please create and add them. If it still does not work after the above configuration, please burn the image provided by blikvm for testing to check whether the OLED hardware is damaged. BLIKVM CM4 version OLED display The product comes standard with a monochrome OLED display with a resolution of 128x64, and the chip is SSD1306. The user connects the display to the product with the wiring of the display. The module is connected to CM4 through the I^2^C interface. The wiring definition is shown in the following table. This is a library for the monochrome OLEDs based on SSD1306 drivers. Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C)","title":"OLED display"},{"location":"atx-guide/","text":"ATXA guide 1. Introduction ATXA is an ATX adapter borad to manage the power of your computer. The product includes two modules A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable.Join to the Discord Community Chat for news, questions and support! ATXA_A ATXA_B 2. A-board A-board is connected to the Raspberry Pi. The following table is a typical connection method in PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed 3. B-board The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B Instructions for connecting to the computer motherboard According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the ATXA-B motherboard. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and ATXA-B. See the following figure for the connection relationship\uff1a 4.Mechanical Diagram 5.Test video youtube\uff1a ATX 6.More link Purchase\uff1a ATX","title":"ATX guide"},{"location":"atx-guide/#atxa-guide","text":"","title":"ATXA guide"},{"location":"atx-guide/#1-introduction","text":"ATXA is an ATX adapter borad to manage the power of your computer. The product includes two modules A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable.Join to the Discord Community Chat for news, questions and support! ATXA_A ATXA_B","title":"1. Introduction"},{"location":"atx-guide/#2-a-board","text":"A-board is connected to the Raspberry Pi. The following table is a typical connection method in PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed","title":"2. A-board"},{"location":"atx-guide/#3-b-board","text":"The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B Instructions for connecting to the computer motherboard According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the ATXA-B motherboard. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and ATXA-B. See the following figure for the connection relationship\uff1a","title":"3. B-board"},{"location":"atx-guide/#4mechanical-diagram","text":"","title":"4.Mechanical Diagram"},{"location":"atx-guide/#5test-video","text":"youtube\uff1a ATX","title":"5.Test video"},{"location":"atx-guide/#6more-link","text":"Purchase\uff1a ATX","title":"6.More link"},{"location":"atx/","text":"ATX Control Board To manage the power of your computer, you need to install an ATX control board inside the chassis and connect it to the motherboard (to enable KVM control of power on/off via the ATX switch). There is a female-to-female cable that connects from the motherboard to the ATX control board and a male-to-female cable that connects from the ATX control board to the front panel (to keep the power on/off button on the chassis functional). The interface on the ATX control board has two ports (TO CASE, TO MB), and both ports have the same functionality, so they can be used interchangeably. ATX compatibility Laptops are not compatible with ATX as they lack the required ATX pins. This method is only applicable to PC servers and desktops. Detailed Instructions 1. Connect the two cables to the ATX control board. To secure the ATX control board inside the chassis, you can choose to mount it on a bracket attached to a PCIe slot. Example 2. Locate the motherboard pins responsible for connecting the front panel buttons and LEDs and disconnect them. Usually, the cables and connectors on the motherboard are labeled. If you're unsure, you can refer to your motherboard's documentation. Example 3. Connect the DuPont male connector from the front panel to the DuPont female connector on the ATX cable, following the pin definitions and paying attention to the labels and polarity (+ or -). Example 4. Using the same method, connect the female pins from the ATX board to the corresponding connector on the motherboard. Refer to your motherboard's documentation to determine which pins on the motherboard connect to which pins on the ATX control board. Sometimes, this information is printed on the motherboard. Example 5. Install the ATX board into a PCI slot on the chassis and secure it with screws or use alternative mounting methods according to your preference. Example 6. Arrange the cables neatly and secure them as needed. Make sure the cables do not come into contact with any fans inside the chassis. Use an Ethernet cable to connect the ATX board to the ATX interface of the BliKVM. With this, the hardware connection of the ATX control board is complete.","title":"ATX Control Board"},{"location":"atx/#atx-control-board","text":"To manage the power of your computer, you need to install an ATX control board inside the chassis and connect it to the motherboard (to enable KVM control of power on/off via the ATX switch). There is a female-to-female cable that connects from the motherboard to the ATX control board and a male-to-female cable that connects from the ATX control board to the front panel (to keep the power on/off button on the chassis functional). The interface on the ATX control board has two ports (TO CASE, TO MB), and both ports have the same functionality, so they can be used interchangeably. ATX compatibility Laptops are not compatible with ATX as they lack the required ATX pins. This method is only applicable to PC servers and desktops.","title":"ATX Control Board"},{"location":"atx/#detailed-instructions","text":"1. Connect the two cables to the ATX control board. To secure the ATX control board inside the chassis, you can choose to mount it on a bracket attached to a PCIe slot. Example 2. Locate the motherboard pins responsible for connecting the front panel buttons and LEDs and disconnect them. Usually, the cables and connectors on the motherboard are labeled. If you're unsure, you can refer to your motherboard's documentation. Example 3. Connect the DuPont male connector from the front panel to the DuPont female connector on the ATX cable, following the pin definitions and paying attention to the labels and polarity (+ or -). Example 4. Using the same method, connect the female pins from the ATX board to the corresponding connector on the motherboard. Refer to your motherboard's documentation to determine which pins on the motherboard connect to which pins on the ATX control board. Sometimes, this information is printed on the motherboard. Example 5. Install the ATX board into a PCI slot on the chassis and secure it with screws or use alternative mounting methods according to your preference. Example 6. Arrange the cables neatly and secure them as needed. Make sure the cables do not come into contact with any fans inside the chassis. Use an Ethernet cable to connect the ATX board to the ATX interface of the BliKVM. With this, the hardware connection of the ATX control board is complete.","title":"Detailed Instructions"},{"location":"edid/","text":"EDID The EDID file in BliKVM serves the purpose of informing the controlled computer about the expected HDMI output resolution. For example, if the EDID is set to 1080P60Hz, and the controlled computer supports this resolution, it will output at 1080P60Hz. Additionally, EDID can be used to disable audio, modify the display model, name, manufacturer, and other information. In most cases, you don't need to change it, but sometimes, especially with strange UEFI/BIOS behavior, it may be necessary. Note BliKVM v1, v2, and v3 use the CSI video capture scheme, which supports EDID settings. However, BliKVM v4 uses the USB video capture scheme, which does not support EDID settings. For v3 HAT, there is a limitation of two CSI channels on the Raspberry Pi 4B, which means it can only capture video input with a maximum resolution of 1080P50Hz. Therefore, if you set 1080P60Hz EDID for v3, it will not be able to capture the image. If you are using PiKVM OS, you can refer to this link for modification instructions. If you are using BliKVM OS, the EDID file is located at /usr/bin/blikvm/edid.txt . Open this file, and replace the EDID contents with the desired resolution's EDID. EDID Examples for 1080P60Hz The following EDID is suitable for v1 and v2 hardware. 1920x1080 60Hz, with audio 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C EDID Examples for 1080P50Hz The following EDID is suitable for v1, v2, and v3 hardware, especially when you want v3 HAT to capture 1080P resolution. 1920x1080 50Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028 EDID Examples for 720P60Hz The following EDID is suitable for v1, v2, and v3 hardware. 1280x720 60Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 Custom EDID To customize the EDID, it is best to use third-party utilities, such as the recommended advanced AW EDID Editor (works well in Windows and can be used in wine) or wxEDID . Both editors work with the binary EDID format. Using these tools, you can modify the EDID information like editing a file, similar to changing the information on an identity card. By editing the EDID, you can adjust the parameters and characteristics of the display to suit different usage requirements, and thus achieve better display performance.","title":"HDMI EDID"},{"location":"edid/#edid","text":"The EDID file in BliKVM serves the purpose of informing the controlled computer about the expected HDMI output resolution. For example, if the EDID is set to 1080P60Hz, and the controlled computer supports this resolution, it will output at 1080P60Hz. Additionally, EDID can be used to disable audio, modify the display model, name, manufacturer, and other information. In most cases, you don't need to change it, but sometimes, especially with strange UEFI/BIOS behavior, it may be necessary. Note BliKVM v1, v2, and v3 use the CSI video capture scheme, which supports EDID settings. However, BliKVM v4 uses the USB video capture scheme, which does not support EDID settings. For v3 HAT, there is a limitation of two CSI channels on the Raspberry Pi 4B, which means it can only capture video input with a maximum resolution of 1080P50Hz. Therefore, if you set 1080P60Hz EDID for v3, it will not be able to capture the image. If you are using PiKVM OS, you can refer to this link for modification instructions. If you are using BliKVM OS, the EDID file is located at /usr/bin/blikvm/edid.txt . Open this file, and replace the EDID contents with the desired resolution's EDID.","title":"EDID"},{"location":"edid/#edid-examples-for-1080p60hz","text":"The following EDID is suitable for v1 and v2 hardware. 1920x1080 60Hz, with audio 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C","title":"EDID Examples for 1080P60Hz"},{"location":"edid/#edid-examples-for-1080p50hz","text":"The following EDID is suitable for v1, v2, and v3 hardware, especially when you want v3 HAT to capture 1080P resolution. 1920x1080 50Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028","title":"EDID Examples for 1080P50Hz"},{"location":"edid/#edid-examples-for-720p60hz","text":"The following EDID is suitable for v1, v2, and v3 hardware. 1280x720 60Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000","title":"EDID Examples for 720P60Hz"},{"location":"edid/#custom-edid","text":"To customize the EDID, it is best to use third-party utilities, such as the recommended advanced AW EDID Editor (works well in Windows and can be used in wine) or wxEDID . Both editors work with the binary EDID format. Using these tools, you can modify the EDID information like editing a file, similar to changing the information on an identity card. By editing the EDID, you can adjust the parameters and characteristics of the display to suit different usage requirements, and thus achieve better display performance.","title":"Custom EDID"},{"location":"faq/","text":"FAQ & Troubleshooting As a first step, we recommend carefully reading our documentation. Most steps to successfully set up your BLIKVM are already described there. If you run into any issues you can check this page which will list common errors. If that still doesn't help you you're welcome to raise an issue ticket or join our Discord for further help. Common questions Can I connect multiple servers to a single BLIKVM? Yes, but it requires additional work to set up. See this page . How can I get the access to PiKVM in my local network over Internet? If your router has an external IP address, you can use port forwarding to forward port 80 (Web), port 8008 (mjpeg), and port 8188 (webrtc) In all other cases, you can use the excellent free VPN service Tailscale. Which BLiKVM hardware version should I choose, such as BLiKVM V1 CM4, BLiKVM V2 PCIe, and BLiKVM V3 Hat? First, please refer to this page for a comparison of the main parameters of each version. V1 and V3 are external solutions, while V2 is an internal chassis solution. If you have a chassis and there is space inside, choosing the V2 PCIe version would be a better option. So how do you choose between the external solutions V1 and V3? V1 is based on the CM4 platform, with higher integration and ready-to-use versions available. V3 is based on the Raspberry Pi 4B platform, with all IO ports exposed and greater expandability. Another key difference is that V1 supports up to 1080P60Hz input, while V3 supports up to 1080P50Hz input. Of course, you also need to consider whether you already have a CM4 or 4B, as purchasing the corresponding baseboard would offer better cost-effectiveness. Can I use BLIKVM for gaming? No, because: For HDMI-CSI bridge, bus bandwidth is not enough to transmit more than 1080p60. For HDMI-USB dongle, high latency and low video quality. General hardware video capture differs from software streaming and introduces additional latency. Can BLIKVM do 4K video? For HDMI-CSI bridge, no. There is not enough bandwidth in the CSI bus for that much data. 1080p60 will max out the bandwidth. For the USB capture devices: technically yes, they will downsample to something smaller to meet the USB 2.0 bandwidth limitations, so the source may be 4k, but the stream will not. The 4K real-time video will not fit through the network anyway. Where does the cursor/video latency come from? Here is the chain of transferring an image to your browser or VNC client. Capture device -> Compression -> Network -> Decompression -> Rendering 100-200ms is very, very fast for this. But we are working to speed things up even more. Does BLIKVM support sound? BliKVM v1 CM4, v2 PCIe, v3 HAT version supported\uff0c v4 Allwinner not support now. Can I power the Pi via PoE? Yes! Hat and PCIe version supported. First steps What is the default password? How do I change it? If you use PiKVM, there are two types of accounts: OS and PiKVM (web interface) accounts. The system account root can be used for SSH/UART access and has the password root . The web interface account is called admin and has the password admin . The PiKVM account cannot be used for SSH access and vice versa. To change passwords, use the following commands (under root): su - # If you're in the webterm rw # Switch filesystem to read-write mode passwd root # Change OS root password kvmd-htpasswd set admin # Change web ui admin password ro # Back to read-only How do I add another user? If you use PiKVM software, as stated above you need to make 2 accounts, 1 for the shell, the other for the PiKVM Web UI. If you require additional users for PiKVM UI, you can use the following: # rw # su - # kvmd-htpasswd set <user> # Adds a new user # kvmd-htpasswd set <user> # Sets the password as long as the user exists # kvmd-htpasswd del <user> # Removes/deletes a user To add a shell/terminal account: # rw # su - # adduser <user> # passwd <user> Keep in mind that the more users that are added, the stream if accessed, fps will drop. Video problems BLIKVM does not show the video from the computer at all Double-check that the video capture device is connected correctly. For the CSI bridge, this should be exactly the camera port. Some laptops do not output any signal until you switch the output (usually via the FN + and an F5 key on the keyboard). Your computer may have turned on sleep mode for the monitor. Move the mouse to turn it off. For windows you might need to check for the active signal resolution. To change the active signal resolution you have to go to Settings>System>Display>Advanced display settings>Display adapter properties then, click \"List All Models\" and choose the one you want. Keep trying different Hz settings. The video works in the booted OS, but not in the BIOS/UEFI This problem appears on Intel NUC, GA-H77-DS3H, and some other devices when using a CSI bridge. All you need to do is change the EDID data. This is the information about supported resolutions that the CSI bridge reports to your computer. Glitchy or wrong BIOS/UEFI resolution On some motherboards, the BIOS may be displayed at a lower resolution, or with some rendering issues/glitches, specially on newer ASUS ones. Like this: This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. If you can't or don't want to enable the CSM, you can try connecting a DisplayPort (DP) monitor, or a dummy plug . If you remove the DP cable/adapter the bug will reappear. If none of this works, try connecting the DP cable first, boot into the BIOS, disable the CSM and shutdown (do not restart) your PC. Then, boot into the BIOS and enable the CSM before shutting down your PC. Then connect the HDMI and turn your PC on again. There is no video in GRUB2, but there is before and after Sometimes this can be caused by the specifics of the BIOS/UEFI and how GRUB2 works with video. This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. The video mode will be located in the same section. Switch the Video mode from UEFI to Legacy . No image from computer with Linux + Awesome WM Sometimes Awesome WM on Linux can't recognize a video output change on a cable. That is, if the cable was first inserted into the monitor, and then you reconnected it to BLIKVM - it may happen that you will not see the image. It seems that the problem is Awesome WM, since for example with KDE, it is not reproducable. If you turn on your workstation with BLIKVM already connected, everything will work fine. USB problems (keyboard, mouse, mass storage, etc) What speed is the USB OTG port? Per the official RPI documentation, this is a limitation of the SoC. The OTG port is only USB2.0, so is limited to 455 Mbit/s. Why can't some keyboard shortcuts of physical keyboards be captured while virtual keyboards can? For example, the F11 key on a Mac computer cannot be captured. This is because some shortcuts are already in use by the system, such as in macOS, where F11 is assigned to the \"Show Desktop\" function by default. When you press F11 in a web interface, the KeyboardEvent is first captured by the system, and if a callback is registered in the system, the event will not be passed to the application. To solve this issue, you can disable the system's assigned shortcut or use a virtual keyboard. Hardware problems (Wi-Fi, ATX, etc) If you use PiKVM software, the web UI show FAN error! Because the fan model used by BLIKVM hardware is different from that of PIKVM hardware, viewing the fan status through the web interface may fail in the latest system of pikvm. However, this will not affect the normal operation of BLIKVM fan. Therefore, when using the PIKVM image, as long as you ensure that the install script displays OK, it means that the update of the kvmd fan program is successful. The threshold temperature set by the default program is 60 degrees Celsius. When the CPU temperature is detected to exceed 60 degrees Celsius, the fan will start rotating at 85% speed. If you want to modify the threshold temperature and speed, you can modify the kvmd-fan.py script, and then re-execute install.sh. I can't connect to Wi-Fi at all! If your device is unable to connect to the Wi-Fi network that you have set up, check the 2.4 GHz Wi-Fi channel used by your Wi-Fi access point. If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. BLIKVM complains about low power warnings Are you using a \"proper\" power supply? Not one you hacked together? Some USB power bricks advertise 5V 2.1A or higher, but can't deliver consistent 5V. Best to use Raspberry Pi Foundation recommended power supplies. It should be 5.1v and 3A DC output. When I use the PoE, do I still need to use the power OTG splitter to prevent back power on the machine usb? Only HAT version you need to use power OTG splitter to prevent back power. Generally, most hosts computer are protected back power, you do not need to usr power OTG splitter in this case. BLIKVM-CM4-V2.2 and BLIKVM-PCIe version don't need. In some board like BLIKVM-PCIe or BLIKVM-CM4-V2.2 has boot pin, how do I connect? If you short them, CM4 will not start normally, but will enter the burning image mode. If your hardware version of boot has only two pins, use the jumper cap to connect the two pins as a short circuit. If you do not use the jumper cap or plug it into one pin, CM4 will start normally. If you use three boot pins of the hardware version, use the jumper cap to connect GND and another non-GND pin to indicate short circuit, and plug the jumper cap on the two GND pins or do not use it, CM4 will start normally. Web problems What ports does BliKVM OS occupy, and how should it be forwarded when using a public server? The web interface uses the HTTP protocol and occupies port 80. If you are using hardware versions V1, V2, or V3 with web-rtc transmission, the port is 8188. If you are using hardware version V4 with MJPEG transmission, the port is 8008. Please note that the ports cannot be modified; only port forwarding can be configured. Raspberry problem Can I use both the CM4 version with EMMC and the SD card at the same time? No, you can't, When designing the CM4 hardware, several pins of the SD card are only valid in the lite version. You can find instructions on the official website of Raspberry Pi.","title":"FAQ"},{"location":"faq/#faq-troubleshooting","text":"As a first step, we recommend carefully reading our documentation. Most steps to successfully set up your BLIKVM are already described there. If you run into any issues you can check this page which will list common errors. If that still doesn't help you you're welcome to raise an issue ticket or join our Discord for further help.","title":"FAQ &amp; Troubleshooting"},{"location":"faq/#common-questions","text":"Can I connect multiple servers to a single BLIKVM? Yes, but it requires additional work to set up. See this page . How can I get the access to PiKVM in my local network over Internet? If your router has an external IP address, you can use port forwarding to forward port 80 (Web), port 8008 (mjpeg), and port 8188 (webrtc) In all other cases, you can use the excellent free VPN service Tailscale. Which BLiKVM hardware version should I choose, such as BLiKVM V1 CM4, BLiKVM V2 PCIe, and BLiKVM V3 Hat? First, please refer to this page for a comparison of the main parameters of each version. V1 and V3 are external solutions, while V2 is an internal chassis solution. If you have a chassis and there is space inside, choosing the V2 PCIe version would be a better option. So how do you choose between the external solutions V1 and V3? V1 is based on the CM4 platform, with higher integration and ready-to-use versions available. V3 is based on the Raspberry Pi 4B platform, with all IO ports exposed and greater expandability. Another key difference is that V1 supports up to 1080P60Hz input, while V3 supports up to 1080P50Hz input. Of course, you also need to consider whether you already have a CM4 or 4B, as purchasing the corresponding baseboard would offer better cost-effectiveness. Can I use BLIKVM for gaming? No, because: For HDMI-CSI bridge, bus bandwidth is not enough to transmit more than 1080p60. For HDMI-USB dongle, high latency and low video quality. General hardware video capture differs from software streaming and introduces additional latency. Can BLIKVM do 4K video? For HDMI-CSI bridge, no. There is not enough bandwidth in the CSI bus for that much data. 1080p60 will max out the bandwidth. For the USB capture devices: technically yes, they will downsample to something smaller to meet the USB 2.0 bandwidth limitations, so the source may be 4k, but the stream will not. The 4K real-time video will not fit through the network anyway. Where does the cursor/video latency come from? Here is the chain of transferring an image to your browser or VNC client. Capture device -> Compression -> Network -> Decompression -> Rendering 100-200ms is very, very fast for this. But we are working to speed things up even more. Does BLIKVM support sound? BliKVM v1 CM4, v2 PCIe, v3 HAT version supported\uff0c v4 Allwinner not support now. Can I power the Pi via PoE? Yes! Hat and PCIe version supported.","title":"Common questions"},{"location":"faq/#first-steps","text":"What is the default password? How do I change it? If you use PiKVM, there are two types of accounts: OS and PiKVM (web interface) accounts. The system account root can be used for SSH/UART access and has the password root . The web interface account is called admin and has the password admin . The PiKVM account cannot be used for SSH access and vice versa. To change passwords, use the following commands (under root): su - # If you're in the webterm rw # Switch filesystem to read-write mode passwd root # Change OS root password kvmd-htpasswd set admin # Change web ui admin password ro # Back to read-only How do I add another user? If you use PiKVM software, as stated above you need to make 2 accounts, 1 for the shell, the other for the PiKVM Web UI. If you require additional users for PiKVM UI, you can use the following: # rw # su - # kvmd-htpasswd set <user> # Adds a new user # kvmd-htpasswd set <user> # Sets the password as long as the user exists # kvmd-htpasswd del <user> # Removes/deletes a user To add a shell/terminal account: # rw # su - # adduser <user> # passwd <user> Keep in mind that the more users that are added, the stream if accessed, fps will drop.","title":"First steps"},{"location":"faq/#video-problems","text":"BLIKVM does not show the video from the computer at all Double-check that the video capture device is connected correctly. For the CSI bridge, this should be exactly the camera port. Some laptops do not output any signal until you switch the output (usually via the FN + and an F5 key on the keyboard). Your computer may have turned on sleep mode for the monitor. Move the mouse to turn it off. For windows you might need to check for the active signal resolution. To change the active signal resolution you have to go to Settings>System>Display>Advanced display settings>Display adapter properties then, click \"List All Models\" and choose the one you want. Keep trying different Hz settings. The video works in the booted OS, but not in the BIOS/UEFI This problem appears on Intel NUC, GA-H77-DS3H, and some other devices when using a CSI bridge. All you need to do is change the EDID data. This is the information about supported resolutions that the CSI bridge reports to your computer. Glitchy or wrong BIOS/UEFI resolution On some motherboards, the BIOS may be displayed at a lower resolution, or with some rendering issues/glitches, specially on newer ASUS ones. Like this: This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. If you can't or don't want to enable the CSM, you can try connecting a DisplayPort (DP) monitor, or a dummy plug . If you remove the DP cable/adapter the bug will reappear. If none of this works, try connecting the DP cable first, boot into the BIOS, disable the CSM and shutdown (do not restart) your PC. Then, boot into the BIOS and enable the CSM before shutting down your PC. Then connect the HDMI and turn your PC on again. There is no video in GRUB2, but there is before and after Sometimes this can be caused by the specifics of the BIOS/UEFI and how GRUB2 works with video. This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. The video mode will be located in the same section. Switch the Video mode from UEFI to Legacy . No image from computer with Linux + Awesome WM Sometimes Awesome WM on Linux can't recognize a video output change on a cable. That is, if the cable was first inserted into the monitor, and then you reconnected it to BLIKVM - it may happen that you will not see the image. It seems that the problem is Awesome WM, since for example with KDE, it is not reproducable. If you turn on your workstation with BLIKVM already connected, everything will work fine.","title":"Video problems"},{"location":"faq/#usb-problems-keyboard-mouse-mass-storage-etc","text":"What speed is the USB OTG port? Per the official RPI documentation, this is a limitation of the SoC. The OTG port is only USB2.0, so is limited to 455 Mbit/s. Why can't some keyboard shortcuts of physical keyboards be captured while virtual keyboards can? For example, the F11 key on a Mac computer cannot be captured. This is because some shortcuts are already in use by the system, such as in macOS, where F11 is assigned to the \"Show Desktop\" function by default. When you press F11 in a web interface, the KeyboardEvent is first captured by the system, and if a callback is registered in the system, the event will not be passed to the application. To solve this issue, you can disable the system's assigned shortcut or use a virtual keyboard.","title":"USB problems (keyboard, mouse, mass storage, etc)"},{"location":"faq/#hardware-problems-wi-fi-atx-etc","text":"If you use PiKVM software, the web UI show FAN error! Because the fan model used by BLIKVM hardware is different from that of PIKVM hardware, viewing the fan status through the web interface may fail in the latest system of pikvm. However, this will not affect the normal operation of BLIKVM fan. Therefore, when using the PIKVM image, as long as you ensure that the install script displays OK, it means that the update of the kvmd fan program is successful. The threshold temperature set by the default program is 60 degrees Celsius. When the CPU temperature is detected to exceed 60 degrees Celsius, the fan will start rotating at 85% speed. If you want to modify the threshold temperature and speed, you can modify the kvmd-fan.py script, and then re-execute install.sh. I can't connect to Wi-Fi at all! If your device is unable to connect to the Wi-Fi network that you have set up, check the 2.4 GHz Wi-Fi channel used by your Wi-Fi access point. If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. BLIKVM complains about low power warnings Are you using a \"proper\" power supply? Not one you hacked together? Some USB power bricks advertise 5V 2.1A or higher, but can't deliver consistent 5V. Best to use Raspberry Pi Foundation recommended power supplies. It should be 5.1v and 3A DC output. When I use the PoE, do I still need to use the power OTG splitter to prevent back power on the machine usb? Only HAT version you need to use power OTG splitter to prevent back power. Generally, most hosts computer are protected back power, you do not need to usr power OTG splitter in this case. BLIKVM-CM4-V2.2 and BLIKVM-PCIe version don't need. In some board like BLIKVM-PCIe or BLIKVM-CM4-V2.2 has boot pin, how do I connect? If you short them, CM4 will not start normally, but will enter the burning image mode. If your hardware version of boot has only two pins, use the jumper cap to connect the two pins as a short circuit. If you do not use the jumper cap or plug it into one pin, CM4 will start normally. If you use three boot pins of the hardware version, use the jumper cap to connect GND and another non-GND pin to indicate short circuit, and plug the jumper cap on the two GND pins or do not use it, CM4 will start normally.","title":"Hardware problems (Wi-Fi, ATX, etc)"},{"location":"faq/#web-problems","text":"What ports does BliKVM OS occupy, and how should it be forwarded when using a public server? The web interface uses the HTTP protocol and occupies port 80. If you are using hardware versions V1, V2, or V3 with web-rtc transmission, the port is 8188. If you are using hardware version V4 with MJPEG transmission, the port is 8008. Please note that the ports cannot be modified; only port forwarding can be configured.","title":"Web problems"},{"location":"faq/#raspberry-problem","text":"Can I use both the CM4 version with EMMC and the SD card at the same time? No, you can't, When designing the CM4 hardware, several pins of the SD card are only valid in the lite version. You can find instructions on the official website of Raspberry Pi.","title":"Raspberry problem"},{"location":"first_steps/","text":"First steps First power on Power up the device. Do not turn off the device until it's fully booted for the first time After turning on the power, BLIKVM OS will perform the necessary operations on the memory card. Getting access to BLIKVM By default, BliKVM receives a dynamic IP address via DHCP. The IP address will be displayed on the BliKVM monitor. If you are using DIY hardware without a monitor, use the following tips: Finding BliKVM in the network You can determine the IP address of BliKVM using the following methods: Common Method: Access the web interface of your router and look for the allocated IP address list. The specific method depends on the router model. Linux Only: Use the command arp-scan --localnet . Linux, macOS, Windows: Download and run Angry IP Scanner . Windows PowerShell: Use the command arp -a . In the example below, let's assume your BliKVM has obtained the address 192.168.0.100 , and you have successfully found that address using the instructions above. Accessing BliKVM Web Interface In most networks, you can access BliKVM in any browser using the following URL: http://192.168.0.100/ . Google Chrome (Chromium), Firefox, and Safari work best with no extensions enabled. If one works and the other does not, it may be an issue with the browser or extensions. It is recommended to use a private browsing window or incognito mode. Internet Explorer and early versions of Microsoft Edge (non-Chromium version) are not supported. The default username is admin , and the password is also admin . Once logged in, you will have access to the main menu with essential functions. You can change system settings and passwords using the web interface's account management feature. Note about accessing BliKVM web via http, not https Accessing BliKVM via SSH SSH is the most common method for remote access in the Linux world. You can access BliKVM via SSH. This method is used for managing the device: Linux, macOS: Open any terminal application and run: ssh blikvm@192.168.0.100 . Windows: Use PuTTY for the operation. The default blikvm user password is blikvm . You can use sudo -i to obtain root privileges. Optional: Updating BliKVM Software This section is not mandatory and should only be performed if you are next to the BliKVM for recovery purposes. Refer to the Software Update Guide for instructions. Note on BliKVM OS Terminal Usage Some configuration changes must be made under the root user (i.e., administrator). Obtaining Root Privileges If you are logged in via SSH, use sudo -i to obtain root privileges. BliKVM storage cards in versions v1, v2, and v3 are mounted in read-only mode. This protects the file system from being corrupted in the event of a sudden power outage. To edit any files and make changes, you need to remount the file system in read-write mode. You can determine the current mode by checking if ro or rw is displayed in the terminal. Enabling Write Mode To enable write mode, run the command rw . To disable write mode, run the command ro . If you receive a \"Device is busy\" message, execute the reboot command. What's next? Set up internet access using Port Forwarding or Tailscale VPN . Explore BLIKVM features using the table of contents on the left. Join our Discord to contact the community and developers. Check out the GitHub - BLIKVM is a Open Source project! FAQ and Troubleshooting If you have any questions or run into problems, take a look at the FAQ . Seriously, it's really useful! We've probably already found a solution for it :) For any other help and support, you can contact us via the Discord chat .","title":"First steps"},{"location":"first_steps/#first-steps","text":"","title":"First steps"},{"location":"first_steps/#first-power-on","text":"Power up the device. Do not turn off the device until it's fully booted for the first time After turning on the power, BLIKVM OS will perform the necessary operations on the memory card.","title":"First power on"},{"location":"first_steps/#getting-access-to-blikvm","text":"By default, BliKVM receives a dynamic IP address via DHCP. The IP address will be displayed on the BliKVM monitor. If you are using DIY hardware without a monitor, use the following tips: Finding BliKVM in the network You can determine the IP address of BliKVM using the following methods: Common Method: Access the web interface of your router and look for the allocated IP address list. The specific method depends on the router model. Linux Only: Use the command arp-scan --localnet . Linux, macOS, Windows: Download and run Angry IP Scanner . Windows PowerShell: Use the command arp -a . In the example below, let's assume your BliKVM has obtained the address 192.168.0.100 , and you have successfully found that address using the instructions above. Accessing BliKVM Web Interface In most networks, you can access BliKVM in any browser using the following URL: http://192.168.0.100/ . Google Chrome (Chromium), Firefox, and Safari work best with no extensions enabled. If one works and the other does not, it may be an issue with the browser or extensions. It is recommended to use a private browsing window or incognito mode. Internet Explorer and early versions of Microsoft Edge (non-Chromium version) are not supported. The default username is admin , and the password is also admin . Once logged in, you will have access to the main menu with essential functions. You can change system settings and passwords using the web interface's account management feature. Note about accessing BliKVM web via http, not https Accessing BliKVM via SSH SSH is the most common method for remote access in the Linux world. You can access BliKVM via SSH. This method is used for managing the device: Linux, macOS: Open any terminal application and run: ssh blikvm@192.168.0.100 . Windows: Use PuTTY for the operation. The default blikvm user password is blikvm . You can use sudo -i to obtain root privileges. Optional: Updating BliKVM Software This section is not mandatory and should only be performed if you are next to the BliKVM for recovery purposes. Refer to the Software Update Guide for instructions.","title":"Getting access to BLIKVM"},{"location":"first_steps/#note-on-blikvm-os-terminal-usage","text":"Some configuration changes must be made under the root user (i.e., administrator). Obtaining Root Privileges If you are logged in via SSH, use sudo -i to obtain root privileges. BliKVM storage cards in versions v1, v2, and v3 are mounted in read-only mode. This protects the file system from being corrupted in the event of a sudden power outage. To edit any files and make changes, you need to remount the file system in read-write mode. You can determine the current mode by checking if ro or rw is displayed in the terminal. Enabling Write Mode To enable write mode, run the command rw . To disable write mode, run the command ro . If you receive a \"Device is busy\" message, execute the reboot command.","title":"Note on BliKVM OS Terminal Usage"},{"location":"first_steps/#whats-next","text":"Set up internet access using Port Forwarding or Tailscale VPN . Explore BLIKVM features using the table of contents on the left. Join our Discord to contact the community and developers. Check out the GitHub - BLIKVM is a Open Source project!","title":"What's next?"},{"location":"first_steps/#faq-and-troubleshooting","text":"If you have any questions or run into problems, take a look at the FAQ . Seriously, it's really useful! We've probably already found a solution for it :) For any other help and support, you can contact us via the Discord chat .","title":"FAQ and Troubleshooting"},{"location":"flashing_os/","text":"Flasing the OS image Micro-SD Card Requirements Minimum 16 Gb Class 10 is strongly recommended Why are there two versions of software, BLIKVM and PiKVM? What is the difference between the two versions? Which one should I choose? Can I use the official image of PiKVM? At the beginning of the BLIKVM project, the hardware was developed, and the software directly used PiKVM. With the continuous progress of the project, BLIKVM has developed its own software version of new architecture, which also lays the foundation for deeper cooperation with its own hardware; The core functions of BLIKVM and PiKVM are the same for users. Some subdivision functions are not the same. For example, BLIKVM supports multiple languages; Select according to your own use experience; You can use the PiKVM official image, but you need to make some adaptations according to the different hardware, mainly involving screens, fans, etc. Since the PiKVM official image is always updated, the specific adaptations need to be seen according to the specific situation you encounter at that time; Download the image BLIKVM software You can find BliKVM v1 CM4, v2 PCIe, v3 HAT, v4 Allwinner BLIKVM software image, v1 v2 v3 use a same image. BLIKVM image The web UI style is as follows: Base on PiKVM software Raspberry 4B and CM4 board use different PiKVM software image. After entering the link, you can see the image named with each hardware version (HAT CM4 PCIe) PiKVM image Flash the image Tip Ignore request to format your sd card, this step is not nessessary. Choose the most suitable method for you. How to flash the eMMC on a Raspberry Pi Compute Module 4 Board Link First, use the jumper cap to short the boot pin. If you use BLIKVM CM4 version Then connect the data cable to the USB OTG interface. Power on blikvm and observe the act light, the green light is always on. If you use BLIKVM PCIe version Then connect the data cable to the USB-PC interface. Power on blikvm and observe the ACT and PWR LED isn't light. After initialize EMMC through the usbboot/rpiboot, the ACT and PWR LED light is always on. EMMC knowledge If you use raspberry pi computing modules such as CM3 or CM4 EMMC\uff0cyou can initialize EMMC through the usbboot. Note that the EMMC version cannot directly use the SD card to start the image. From this video you can learn how to flash image quickly. How to flash the eMMC on a Raspberry Pi Compute Module 4 video Taking Ubuntu system as an example: Linux usbboot If you use an Micro-SD Card, you don't need to care about that. # sudo apt-get install libusb-1.0-0-dev # git clone --depth=1 https://github.com/raspberrypi/usbboot # cd usbboot # make # sudo ./rpiboot If the content shown in the figure below appears, it indicates that EMMC initialization is successful. Using RPi Imager (Linux, MacOS and Windows) Download and install the latest version of RPi Imager . Run RPi Imager: Press CHOOSE OS and select Use custom image at bottom of the list: After clicking on this item, select the image file ( .img.xz ), then click CHOOSE STORAGE : Insert the memory card into the card reader. Choose the card reader from this list. Be careful and choose the right device: After choosing the memory card, press the WRITE button. Confirm the operation when you are asked about it: Wait for the process to finish. Get yourself a coffee or do some stretching :) Tip The process may hang at 99% for a long time, this is okay, just wait for it to complete 8.Remove the memory card after successful completion: Tip If an error occurs during flashing or booting PiKVM, repeat the process.","title":"Flasing OS"},{"location":"flashing_os/#flasing-the-os-image","text":"Micro-SD Card Requirements Minimum 16 Gb Class 10 is strongly recommended Why are there two versions of software, BLIKVM and PiKVM? What is the difference between the two versions? Which one should I choose? Can I use the official image of PiKVM? At the beginning of the BLIKVM project, the hardware was developed, and the software directly used PiKVM. With the continuous progress of the project, BLIKVM has developed its own software version of new architecture, which also lays the foundation for deeper cooperation with its own hardware; The core functions of BLIKVM and PiKVM are the same for users. Some subdivision functions are not the same. For example, BLIKVM supports multiple languages; Select according to your own use experience; You can use the PiKVM official image, but you need to make some adaptations according to the different hardware, mainly involving screens, fans, etc. Since the PiKVM official image is always updated, the specific adaptations need to be seen according to the specific situation you encounter at that time;","title":"Flasing the OS image"},{"location":"flashing_os/#download-the-image","text":"","title":"Download the image"},{"location":"flashing_os/#blikvm-software","text":"You can find BliKVM v1 CM4, v2 PCIe, v3 HAT, v4 Allwinner BLIKVM software image, v1 v2 v3 use a same image. BLIKVM image The web UI style is as follows:","title":"BLIKVM software"},{"location":"flashing_os/#base-on-pikvm-software","text":"Raspberry 4B and CM4 board use different PiKVM software image. After entering the link, you can see the image named with each hardware version (HAT CM4 PCIe) PiKVM image","title":"Base on PiKVM software"},{"location":"flashing_os/#flash-the-image","text":"Tip Ignore request to format your sd card, this step is not nessessary. Choose the most suitable method for you. How to flash the eMMC on a Raspberry Pi Compute Module 4","title":"Flash the image"},{"location":"flashing_os/#board-link","text":"First, use the jumper cap to short the boot pin. If you use BLIKVM CM4 version Then connect the data cable to the USB OTG interface. Power on blikvm and observe the act light, the green light is always on. If you use BLIKVM PCIe version Then connect the data cable to the USB-PC interface. Power on blikvm and observe the ACT and PWR LED isn't light. After initialize EMMC through the usbboot/rpiboot, the ACT and PWR LED light is always on. EMMC knowledge If you use raspberry pi computing modules such as CM3 or CM4 EMMC\uff0cyou can initialize EMMC through the usbboot. Note that the EMMC version cannot directly use the SD card to start the image. From this video you can learn how to flash image quickly. How to flash the eMMC on a Raspberry Pi Compute Module 4 video Taking Ubuntu system as an example:","title":"Board Link"},{"location":"flashing_os/#linux-usbboot","text":"If you use an Micro-SD Card, you don't need to care about that. # sudo apt-get install libusb-1.0-0-dev # git clone --depth=1 https://github.com/raspberrypi/usbboot # cd usbboot # make # sudo ./rpiboot If the content shown in the figure below appears, it indicates that EMMC initialization is successful.","title":"Linux usbboot"},{"location":"flashing_os/#using-rpi-imager-linux-macos-and-windows","text":"Download and install the latest version of RPi Imager . Run RPi Imager: Press CHOOSE OS and select Use custom image at bottom of the list: After clicking on this item, select the image file ( .img.xz ), then click CHOOSE STORAGE : Insert the memory card into the card reader. Choose the card reader from this list. Be careful and choose the right device: After choosing the memory card, press the WRITE button. Confirm the operation when you are asked about it: Wait for the process to finish. Get yourself a coffee or do some stretching :) Tip The process may hang at 99% for a long time, this is okay, just wait for it to complete 8.Remove the memory card after successful completion: Tip If an error occurs during flashing or booting PiKVM, repeat the process.","title":"Using RPi Imager (Linux, MacOS and Windows)"},{"location":"hdmi-csi-i2s/","text":"HDMI to CSI&I2S bridge guide Convert HDMI signal acquisition into CSI signal and I2S audio signal. Introduction This module takes the incoming HDMI signal and converts it into a separate CSI signal and I2S audio signal. HDMI input supports up to 1080P60Hz. It works well on raspberry pi, there are three versions of this module in history(C779\u3001C780\u3001C790). C790 is the latest version. C790 has mitigate HDMI backpowering,also has two csi channels and four csi channels at the same time. Features C790 hardware parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 4 CSI-2 channels & clock The CSI-2 interface, with 15 pin FPC seat, spacing 1.0 mm, is located on the front of the C790 module. The CSI-2 interface, with 22 pin FPC seat, spacing 0.5 mm, is located on the back of the C790 module. Size: 30 x 45 mm Install:4 x M2.5 Power supply:3.3V Weight: 10g Pi 4B only support 1080P50Hz, limited by the number of CSI-2 channels. CM4 support 1080P60HZ, So if you must use 1080P60Hz input, please use CM4 and C790 together. interface C790 has two csi output interface. In fornt of C790, the CSI-2 interface is 15 pin FPC seat, spacing 1.0 mm. In back of C790, the CSI-2 interface is 22 pin FPC seat, spacing 0.5 mm. size Install C790 on raspberry pi for reference C780 C780A hardware parameters HDMI input: supports up to 1080P50Hz on raspberry pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install:6 x M2.5 Power supply:3.3V Weight: 10g C780B hardware parameters HDMI input: supports up to 1080P60Hz on raspberry pi HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 4 CSI-2 channels & clock CSI-2 interface: 22 pin FPC seat, spacing 0.5 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install:6 x M2.5 Power supply:3.3V Weight: 10g interface The wiring of audio part is shown in Figure. size The size of C780 is shown in Figure. There are 6 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. As shown in Figure, the user can directly fix the module on the raspberry pi zero.C780 is designed to be broken, and the hole spacing before breaking can be perfectly installed with most series of raspberry pi. C779 hardware parameters HDMI input: supports up to 1080P50Hz on raspberry pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 35 x 50 mm Install:4 x M2.5 Power supply:3.3V Weight: 10g size The size of C779 is shown in Figure. There are 4 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. CSI Interface Definitions The CSI (Camera Serial Interface) interfaces C779 and C780A have 15 pins each, while the C780B interface has 22 pins. The C790 interface is unique as it supports both 15 and 22 PIN configurations. Software demo The use guide of C790/C780/C779 depends on the official Raspberry Pi OS version you are using. Different versions have different usage methods. If you have some questions, Join our BLIKVM Discord Community for Support, FAQ & News! To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If \u201cuname -a\u201d reports anything less, then fix this before proceeding. pi@raspberrypi:~ $ uname -a Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. Update & upgrade the raspberry pi system (It will take a long time depend on the different country) sudo apt-get update sudo apt-get upgrade 2. Enable camera module (the camera is enabled by default in Raspberry pi Bullseys OS) sudo raspi-config sudo reboot Navigate to \u2018Interfacing Options\u2019 and hit Enter. Now select the \u2018Camera\u2019 option, and hit the Enter key to enable it. Select \u201cFinish\u201d and select to reboot your Raspberry Pi. reboot is important!! 3. Edit /boot/config.txt (that will need sudo) sudo nano /boot/config.txt Add the line: dtoverlay=tc358743 Add the line if your shield support audio like C780 or C790. dtoverlay=tc358743-audio please append the If (and only if) you have a device such as the C780 or C790 that supports the 22pin connector with all 4 lanes wired out, and are using a Compute Module with the CAM1 connector that also has all 4 lanes wired up, you can use: dtoverlay=tc358743,4lane=1 !!! note \"4. Check the amount of memory assigned to the CMA heap with \u201cdmesg | grep cma\u201d. The first line should be along the lines of\" pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 If it reports less than 96MB assigned to CMA, then edit /boot/cmdline.txt and add to the start of the line. Do NOT add any carriage returns. cma=96M !!! note \"5. Reboot. If all is well you should get a /dev/video0 device, and \u201cv4l2-ctl \u2013list-devices\u201d will tell you that it is provided by Unicam. After connecting all the cables, power on the Raspberry Pi, the C790 indicator light is normally green, and after opening the Raspberry Pi terminal, enter the following command:\" pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 !!! note \"6. This driver puts all the control in the hands of the user, or the user\u2019s application. By default there is no EDID loaded into the chip to allow it to tell the HDMI source what resolutions are supported. There are EDID editors around. If you create a file edid.txt, then you can push this to the device using\" The comment of edid.txt file: 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt #copy the above commend in edid.txt, save&exit; pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan 7. The driver does NOT automatically switch to the resolution detected. Use the command: pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: You MUST set the timings via \u201cv4l2-ctl \u2013set-dv-bt-timings\u201d. You can pass in an index to the detected mode, or use: v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. 8. The chip supports two formats \u2013 BGR3 (the default) and UYVY. BGR3 is 24bpp, and UYVY is YUV4:2:2 16bpp. Over the normal 2 CSI-2 lanes the data rate is such that BGR3 can run at a maximum of 1080p30, whilst UYVY will go up to 1080p50. Use the following command to select UYVY, however your application may override that. v4l2-ctl -v pixelformat=UYVY 9. Check that the audio drivers / card is available to ALSA. pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1 means that the card number for the TC358743XBG is \u201c1\u201d and it might be different. 10. Install GStreamer tool. sudo apt install gstreamer1.0-tools Check gstreamer tool version: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note: Different versions have different command line parameters, which is very annoying. 11. Use gstreamer to record video and audio #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. foo.mkv is the output file. If your gstreamer is version 1.8 or above, you can try the following test command. In addition, alsasrc device=hw:1 represents the sound card of TC358743, you can use \u201carecord -l\u201d to query. #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: We recommend that you modify the above framerate parameter to the actual frame rate of your HDMI signal, the actual frame rate value is from the result of \u2018v4l2-ctl \u2013query-dv-timings\u2019 command. For the above HDMI device, because the frame rate is 60, so we modify the framerate parameter to 60 like the followint command. Record the video only: gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Record the video and audio: (if your shield supports audio also) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Packing List C790 Test video C780A test:https://www.youtube.com/watch?v=ecqyINoiHNQ C780B test:https://www.youtube.com/watch?v=nc-hwPT2Uak&t=15s Purchase link Purchase\uff1a C790 & C780 Purchase\uff1a C779","title":"HDMI to CSI & Audio"},{"location":"hdmi-csi-i2s/#hdmi-to-csii2s-bridge-guide","text":"Convert HDMI signal acquisition into CSI signal and I2S audio signal.","title":"HDMI to CSI&amp;I2S bridge guide"},{"location":"hdmi-csi-i2s/#introduction","text":"This module takes the incoming HDMI signal and converts it into a separate CSI signal and I2S audio signal. HDMI input supports up to 1080P60Hz. It works well on raspberry pi, there are three versions of this module in history(C779\u3001C780\u3001C790). C790 is the latest version. C790 has mitigate HDMI backpowering,also has two csi channels and four csi channels at the same time.","title":"Introduction"},{"location":"hdmi-csi-i2s/#features","text":"","title":"Features"},{"location":"hdmi-csi-i2s/#c790","text":"hardware parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 4 CSI-2 channels & clock The CSI-2 interface, with 15 pin FPC seat, spacing 1.0 mm, is located on the front of the C790 module. The CSI-2 interface, with 22 pin FPC seat, spacing 0.5 mm, is located on the back of the C790 module. Size: 30 x 45 mm Install:4 x M2.5 Power supply:3.3V Weight: 10g Pi 4B only support 1080P50Hz, limited by the number of CSI-2 channels. CM4 support 1080P60HZ, So if you must use 1080P60Hz input, please use CM4 and C790 together. interface C790 has two csi output interface. In fornt of C790, the CSI-2 interface is 15 pin FPC seat, spacing 1.0 mm. In back of C790, the CSI-2 interface is 22 pin FPC seat, spacing 0.5 mm. size Install C790 on raspberry pi for reference","title":"C790"},{"location":"hdmi-csi-i2s/#c780","text":"C780A hardware parameters HDMI input: supports up to 1080P50Hz on raspberry pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install:6 x M2.5 Power supply:3.3V Weight: 10g C780B hardware parameters HDMI input: supports up to 1080P60Hz on raspberry pi HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 4 CSI-2 channels & clock CSI-2 interface: 22 pin FPC seat, spacing 0.5 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install:6 x M2.5 Power supply:3.3V Weight: 10g interface The wiring of audio part is shown in Figure. size The size of C780 is shown in Figure. There are 6 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. As shown in Figure, the user can directly fix the module on the raspberry pi zero.C780 is designed to be broken, and the hole spacing before breaking can be perfectly installed with most series of raspberry pi.","title":"C780"},{"location":"hdmi-csi-i2s/#c779","text":"hardware parameters HDMI input: supports up to 1080P50Hz on raspberry pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 35 x 50 mm Install:4 x M2.5 Power supply:3.3V Weight: 10g size The size of C779 is shown in Figure. There are 4 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws.","title":"C779"},{"location":"hdmi-csi-i2s/#csi-interface-definitions","text":"The CSI (Camera Serial Interface) interfaces C779 and C780A have 15 pins each, while the C780B interface has 22 pins. The C790 interface is unique as it supports both 15 and 22 PIN configurations.","title":"CSI Interface Definitions"},{"location":"hdmi-csi-i2s/#software-demo","text":"The use guide of C790/C780/C779 depends on the official Raspberry Pi OS version you are using. Different versions have different usage methods. If you have some questions, Join our BLIKVM Discord Community for Support, FAQ & News! To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If \u201cuname -a\u201d reports anything less, then fix this before proceeding. pi@raspberrypi:~ $ uname -a Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. Update & upgrade the raspberry pi system (It will take a long time depend on the different country) sudo apt-get update sudo apt-get upgrade 2. Enable camera module (the camera is enabled by default in Raspberry pi Bullseys OS) sudo raspi-config sudo reboot Navigate to \u2018Interfacing Options\u2019 and hit Enter. Now select the \u2018Camera\u2019 option, and hit the Enter key to enable it. Select \u201cFinish\u201d and select to reboot your Raspberry Pi. reboot is important!! 3. Edit /boot/config.txt (that will need sudo) sudo nano /boot/config.txt Add the line: dtoverlay=tc358743 Add the line if your shield support audio like C780 or C790. dtoverlay=tc358743-audio please append the If (and only if) you have a device such as the C780 or C790 that supports the 22pin connector with all 4 lanes wired out, and are using a Compute Module with the CAM1 connector that also has all 4 lanes wired up, you can use: dtoverlay=tc358743,4lane=1 !!! note \"4. Check the amount of memory assigned to the CMA heap with \u201cdmesg | grep cma\u201d. The first line should be along the lines of\" pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 If it reports less than 96MB assigned to CMA, then edit /boot/cmdline.txt and add to the start of the line. Do NOT add any carriage returns. cma=96M !!! note \"5. Reboot. If all is well you should get a /dev/video0 device, and \u201cv4l2-ctl \u2013list-devices\u201d will tell you that it is provided by Unicam. After connecting all the cables, power on the Raspberry Pi, the C790 indicator light is normally green, and after opening the Raspberry Pi terminal, enter the following command:\" pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 !!! note \"6. This driver puts all the control in the hands of the user, or the user\u2019s application. By default there is no EDID loaded into the chip to allow it to tell the HDMI source what resolutions are supported. There are EDID editors around. If you create a file edid.txt, then you can push this to the device using\" The comment of edid.txt file: 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt #copy the above commend in edid.txt, save&exit; pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan 7. The driver does NOT automatically switch to the resolution detected. Use the command: pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: You MUST set the timings via \u201cv4l2-ctl \u2013set-dv-bt-timings\u201d. You can pass in an index to the detected mode, or use: v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. 8. The chip supports two formats \u2013 BGR3 (the default) and UYVY. BGR3 is 24bpp, and UYVY is YUV4:2:2 16bpp. Over the normal 2 CSI-2 lanes the data rate is such that BGR3 can run at a maximum of 1080p30, whilst UYVY will go up to 1080p50. Use the following command to select UYVY, however your application may override that. v4l2-ctl -v pixelformat=UYVY 9. Check that the audio drivers / card is available to ALSA. pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1 means that the card number for the TC358743XBG is \u201c1\u201d and it might be different. 10. Install GStreamer tool. sudo apt install gstreamer1.0-tools Check gstreamer tool version: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note: Different versions have different command line parameters, which is very annoying. 11. Use gstreamer to record video and audio #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. foo.mkv is the output file. If your gstreamer is version 1.8 or above, you can try the following test command. In addition, alsasrc device=hw:1 represents the sound card of TC358743, you can use \u201carecord -l\u201d to query. #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: We recommend that you modify the above framerate parameter to the actual frame rate of your HDMI signal, the actual frame rate value is from the result of \u2018v4l2-ctl \u2013query-dv-timings\u2019 command. For the above HDMI device, because the frame rate is 60, so we modify the framerate parameter to 60 like the followint command. Record the video only: gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Record the video and audio: (if your shield supports audio also) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9)","title":"Software demo"},{"location":"hdmi-csi-i2s/#packing-list","text":"C790","title":"Packing List"},{"location":"hdmi-csi-i2s/#test-video","text":"C780A test:https://www.youtube.com/watch?v=ecqyINoiHNQ C780B test:https://www.youtube.com/watch?v=nc-hwPT2Uak&t=15s","title":"Test video"},{"location":"hdmi-csi-i2s/#purchase-link","text":"Purchase\uff1a C790 & C780 Purchase\uff1a C779","title":"Purchase link"},{"location":"hid/","text":"Virtual Keyboard The virtual keyboard supports the use of combination keys. To do this, click and hold the corresponding virtual key with the mouse, drag it outside the virtual keyboard, and then release it to complete the operation of the combination key. For example, using the ctrl+alt+del combination key has the following effect: Currently, when pressing cmd+other keys simultaneously on a Mac computer, the other keys will not be released when cmd is released. This bug has not been fixed yet. Users can solve this problem by clicking on the incorrectly released key on the virtual keyboard first.","title":"keyboard"},{"location":"hid/#virtual-keyboard","text":"The virtual keyboard supports the use of combination keys. To do this, click and hold the corresponding virtual key with the mouse, drag it outside the virtual keyboard, and then release it to complete the operation of the combination key. For example, using the ctrl+alt+del combination key has the following effect: Currently, when pressing cmd+other keys simultaneously on a Mac computer, the other keys will not be released when cmd is released. This bug has not been fixed yet. Users can solve this problem by clicking on the incorrectly released key on the virtual keyboard first.","title":"Virtual Keyboard"},{"location":"make-image/","text":"Make your own image When you have made modifications to an image and want to create your own image, you can follow the steps below on Linux to create a minimal image. Firstly, use the gparted software to open the SD card of the image you want to create. Use gparted to partition the unused space and set it as unallocated. This ensures that this portion of empty space without any valid content is not included in the image creation. Next, use the fdisk command to view the size of the available space, as shown in the following image, which is 10151935. Then, use the dd command to write to an empty img file. Set the count value to be greater than the size of the volume end obtained from fdisk by at least 1. touch blikvm-armbian-v4-20230623.img sudo dd if=/dev/sdb of=./blikvm-armbian-v4-20230623.img bs=512 count=10151936 Wait for the dd command to finish executing.","title":"make image"},{"location":"make-image/#make-your-own-image","text":"When you have made modifications to an image and want to create your own image, you can follow the steps below on Linux to create a minimal image. Firstly, use the gparted software to open the SD card of the image you want to create. Use gparted to partition the unused space and set it as unallocated. This ensures that this portion of empty space without any valid content is not included in the image creation. Next, use the fdisk command to view the size of the available space, as shown in the following image, which is 10151935. Then, use the dd command to write to an empty img file. Set the count value to be greater than the size of the volume end obtained from fdisk by at least 1. touch blikvm-armbian-v4-20230623.img sudo dd if=/dev/sdb of=./blikvm-armbian-v4-20230623.img bs=512 count=10151936 Wait for the dd command to finish executing.","title":"Make your own image"},{"location":"modify_pikvm_image/","text":"Modifying PiKVM image to work with BliKVM hardware Because the blikvm hardware implementation scheme and PiKVM hardware implementation scheme are not exactly the same, you need to modify some errors through the following configuration for the official image of PiKVM. Of course, you can use the configured image . Fan config Since BliKVM's fan hardware is different to PiKVM's, you need to replace the control fan script first. The following default starting fan temperature is 40 degrees Celsius su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro Edit the /etc/kvmd/override.yaml file and add the following content to remove the web UI error warning about fans. kvmd: info: fan: unix: '' Check EDID file for 1080P60Hz input The function of the EDID file is to set the controlled computer to input according to the expected resolution. Since the image EDID file of PiKVM in different periods does not necessarily meet 1080P60Hz, when you use the CM4 version of hardware, it is found that the default output of the controlled computer is not 1080P60Hz, you can modify /etc/kvmd/tc358743-edid.hex to the following contents 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 make sure /boot/config.txt has the 4lane=1 entry in it for 1080p60hz support # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio If you use webrtc can't get audio, try to edit /etc/kvmd/janus/janus.plugin.ustreamer.jcfg to add audio support. audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" }","title":"config for PiKVM OS"},{"location":"modify_pikvm_image/#modifying-pikvm-image-to-work-with-blikvm-hardware","text":"Because the blikvm hardware implementation scheme and PiKVM hardware implementation scheme are not exactly the same, you need to modify some errors through the following configuration for the official image of PiKVM. Of course, you can use the configured image .","title":"Modifying PiKVM image to work with BliKVM hardware"},{"location":"modify_pikvm_image/#fan-config","text":"Since BliKVM's fan hardware is different to PiKVM's, you need to replace the control fan script first. The following default starting fan temperature is 40 degrees Celsius su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro Edit the /etc/kvmd/override.yaml file and add the following content to remove the web UI error warning about fans. kvmd: info: fan: unix: ''","title":"Fan config"},{"location":"modify_pikvm_image/#check-edid-file-for-1080p60hz-input","text":"The function of the EDID file is to set the controlled computer to input according to the expected resolution. Since the image EDID file of PiKVM in different periods does not necessarily meet 1080P60Hz, when you use the CM4 version of hardware, it is found that the default output of the controlled computer is not 1080P60Hz, you can modify /etc/kvmd/tc358743-edid.hex to the following contents 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 make sure /boot/config.txt has the 4lane=1 entry in it for 1080p60hz support # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio If you use webrtc can't get audio, try to edit /etc/kvmd/janus/janus.plugin.ustreamer.jcfg to add audio support. audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" }","title":"Check EDID file for 1080P60Hz input"},{"location":"msd/","text":"Mass Storage Drive Reinstall the system Video BliKVM's USB device simulation feature allows you to remotely mount images on the virtual machine's mass storage drive, making it easy to install or reinstall operating systems and other software. This can be a useful feature for system administrators who need to manage multiple virtual machines remotely. By mounting an image on the mass storage drive, you can quickly and easily set up or configure a new virtual machine without having to physically connect a USB drive or other external storage device. Note: the size of the MSD is limited by the size of your sd card or eMMC module. Web UI Currently, except for uploading images that are not yet supported, all other tasks can be completed through the web UI Upload images manually (without Web UI) Confirm that the following four paths exist. If you are using the official latest image of blikvm, and it is fully configured, there is no need to check. /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy SSH logs in to blikvm, executes the rw command, and changes the system permission to writable. rw In your PC ,use scp cmd send iso file to kvm board. scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ excute msd cmd.wait until excute end. If you don't use option paramter\uff1a The default size of the USB flash disk is 5GB. The default filename is scan /mnt/msd/user dir. The default msd name is ventoy. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make If your iso is large than 5GB.You can specify the optional parameter - s xxx, xxx is the Size. If you need specify iso ,you can use -f xxx.iso. If you want to specify the msd name, you can use -n xxx. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso Tips: cp progress slowly, Please be patient. If you want to excute other cmd, you can use other option. c option contains : make/conn/disconn/clean connect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn disconnect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn clean msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean throuht web restart PC, enter BIOS, modify boot priority,set blikvm USB first. according to step, select operate system , format partition and install system.","title":"USB flash Drive"},{"location":"msd/#mass-storage-drive","text":"Reinstall the system Video BliKVM's USB device simulation feature allows you to remotely mount images on the virtual machine's mass storage drive, making it easy to install or reinstall operating systems and other software. This can be a useful feature for system administrators who need to manage multiple virtual machines remotely. By mounting an image on the mass storage drive, you can quickly and easily set up or configure a new virtual machine without having to physically connect a USB drive or other external storage device. Note: the size of the MSD is limited by the size of your sd card or eMMC module.","title":"Mass Storage Drive"},{"location":"msd/#web-ui","text":"Currently, except for uploading images that are not yet supported, all other tasks can be completed through the web UI","title":"Web UI"},{"location":"msd/#upload-images-manually-without-web-ui","text":"Confirm that the following four paths exist. If you are using the official latest image of blikvm, and it is fully configured, there is no need to check. /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy SSH logs in to blikvm, executes the rw command, and changes the system permission to writable. rw In your PC ,use scp cmd send iso file to kvm board. scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ excute msd cmd.wait until excute end. If you don't use option paramter\uff1a The default size of the USB flash disk is 5GB. The default filename is scan /mnt/msd/user dir. The default msd name is ventoy. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make If your iso is large than 5GB.You can specify the optional parameter - s xxx, xxx is the Size. If you need specify iso ,you can use -f xxx.iso. If you want to specify the msd name, you can use -n xxx. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso Tips: cp progress slowly, Please be patient. If you want to excute other cmd, you can use other option. c option contains : make/conn/disconn/clean connect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn disconnect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn clean msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean throuht web restart PC, enter BIOS, modify boot priority,set blikvm USB first. according to step, select operate system , format partition and install system.","title":"Upload images manually (without Web UI)"},{"location":"port-forwarding/","text":"Port forwarding If your ISP provides an external IP address for the router, you can configure Port forwarding to access BliKVM: The web interface uses the HTTP protocol and occupies port 80; If your hardware is v1 v2 v3 and you are using web rtc transmission, the port is 8188; If your hardware is v4 and you are using mjepg transmission, the port is 8008; Note that the port does not support modification and can only be configured for forwarding; If you do not have an external IP address, we suggest trying to use Tailscale VPN \u3002","title":"Port forwarding"},{"location":"port-forwarding/#port-forwarding","text":"If your ISP provides an external IP address for the router, you can configure Port forwarding to access BliKVM: The web interface uses the HTTP protocol and occupies port 80; If your hardware is v1 v2 v3 and you are using web rtc transmission, the port is 8188; If your hardware is v4 and you are using mjepg transmission, the port is 8008; Note that the port does not support modification and can only be configured for forwarding; If you do not have an external IP address, we suggest trying to use Tailscale VPN \u3002","title":"Port forwarding"},{"location":"rtc/","text":"RTC Clock The purpose of an RTC (Real-Time Clock) is to provide real-time information about the current date and time for a device or system. It is an independent clock chip or module that has its own power source, allowing it to maintain accurate time even when the device is powered off or experiences a power outage. Due to shipping restrictions on international deliveries, the RTC hardware is shipped without a battery, and users need to purchase a CR1220 button cell battery themselves. The specific RTC clock model used in different versions of BliKVM may vary, and the usage methods may differ slightly. BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563 1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc0 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30 BliKVM V4 - pcf8563 1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc1 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"RTC clock"},{"location":"rtc/#rtc-clock","text":"The purpose of an RTC (Real-Time Clock) is to provide real-time information about the current date and time for a device or system. It is an independent clock chip or module that has its own power source, allowing it to maintain accurate time even when the device is powered off or experiences a power outage. Due to shipping restrictions on international deliveries, the RTC hardware is shipped without a battery, and users need to purchase a CR1220 button cell battery themselves. The specific RTC clock model used in different versions of BliKVM may vary, and the usage methods may differ slightly.","title":"RTC Clock"},{"location":"rtc/#blikvm-v2-pcie-and-blikvm-v3-hat-pcf8563","text":"1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc0 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563"},{"location":"rtc/#blikvm-v4-pcf8563","text":"1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc1 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V4 - pcf8563"},{"location":"serial_over_usb/","text":"Serial-over-USB connection The BliKVM device can be accessed through the serial port terminal. 1.For hardware connection, you should use the USB to ttl module to connect the USB of the computer to the uart of BliKVM. If you are using the Hat version, please connect the serial ports GPIO14 and GPIO15. If you are using the PCIe version, connect the GTR pin marked by the PCB 2.Install terminal login tools on the computer. For example, you can install putty tools on Windows 3. Use the putty instruction. Enter the correct COM port. The default baud rate is 115200. Select serial as the connection method, and then click Open\uff08Use PiKVM firmware as an example\uff09 If your computer cannot correctly recognize the USB to TTL module, please follow the steps below to install the driver for your computer Connect the usb-a connector to your admin host (in this example, it's on a windows host). As a result, device manager will show a new USB Serial device in Other devices. Download and extract/run drivers. In this example, I downloaded and extracted the ZIP file. https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all Update driver for the new USB Serial device, point it to where you extracted the files, and click Next then Close. If done right, the new USB serial device should now show up under Ports as USB-SERIAL CH340 (COMX).","title":"Serial-over-USB"},{"location":"serial_over_usb/#serial-over-usb-connection","text":"The BliKVM device can be accessed through the serial port terminal. 1.For hardware connection, you should use the USB to ttl module to connect the USB of the computer to the uart of BliKVM. If you are using the Hat version, please connect the serial ports GPIO14 and GPIO15. If you are using the PCIe version, connect the GTR pin marked by the PCB 2.Install terminal login tools on the computer. For example, you can install putty tools on Windows 3. Use the putty instruction. Enter the correct COM port. The default baud rate is 115200. Select serial as the connection method, and then click Open\uff08Use PiKVM firmware as an example\uff09 If your computer cannot correctly recognize the USB to TTL module, please follow the steps below to install the driver for your computer Connect the usb-a connector to your admin host (in this example, it's on a windows host). As a result, device manager will show a new USB Serial device in Other devices. Download and extract/run drivers. In this example, I downloaded and extracted the ZIP file. https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all Update driver for the new USB Serial device, point it to where you extracted the files, and click Next then Close. If done right, the new USB serial device should now show up under Ports as USB-SERIAL CH340 (COMX).","title":"Serial-over-USB connection"},{"location":"static_ip/","text":"Set static IP To configure a static IP address on a BliKVM image, you can follow these steps: SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/dhcpcd.conf Within the file, locate the section that starts with \"# Example static IP configuration\". Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: interface eth0 static ip_address=192.168.1.100/24 static routers=192.168.1.1 static domain_name_servers=192.168.1.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet.","title":"Set Static IP "},{"location":"static_ip/#set-static-ip","text":"To configure a static IP address on a BliKVM image, you can follow these steps: SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/dhcpcd.conf Within the file, locate the section that starts with \"# Example static IP configuration\". Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: interface eth0 static ip_address=192.168.1.100/24 static routers=192.168.1.1 static domain_name_servers=192.168.1.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet.","title":"Set static IP"},{"location":"switch-guide/","text":"HDMI Switch Mannul BliKVM-Switch-V1.0 uses and tests video, supporting BliKVM and PiKVM Introduction BliKVM-Switch-V1.0 is a four channel HDMI+USB switch, which supports panel button, desktop controller, KVM remote to switch between computers. Maximum support of the switch itself 4K@60HZ Plug and play, drive free. BliKVM-Switch-V1.0 uses the same hardware solution as XH-HK4401, AG7210 HDMI switching chip supports up to 4K@60Hz, CH444G USB switching chip supports USB2.0. The difference is that BliKVM-Switch-V1.0 is equipped with KVM USB cable, which can realize KVM port selection. BliKVM-Switch-V1.0 is compatible with BliKVM and PiKVM. points for attention The switch can be powered directly from the USB input to the computer, that is, the switch can work normally without power supply. If the USB power supply of the controlled computer cannot make the switch work, the switch can be powered independently. The switch package only provides a USB power cable, but does not provide a power adapter. The customer needs to configure a power adapter (5V). Desktop controller can control HDMI switch with USB cable. For customers who do not use KVM, this is another way of switching for easy cable management. HDMI input support up to 4096x2160/60Hz resolution 4K 60Hz input, the power is about 200 mW. Interface diagram Front and back interface diagram, the control interface in the right figure is the remote control interface. Schematic Diagram of Side Interface. Equipment connection diagram. Software configuration If you are using BliKVM software and have powered on the switch and connected the cables before starting BliKVM, no additional configuration is needed. BliKVM will automatically detect the switch when it starts. If automatic detection fails, you can manually specify the switch device. First, confirm the device descriptor name of the switch by using the terminal, such as /dev/ttyUSB0 . Then, edit the switch_handle field in /usr/bin/blikvm/package.json and assign /dev/ttyUSB0 to it. Afterward, restart BliKVM. Click MORE in the lower left corner, find the BliKVM switch column, and then switch. Note that the flashing blue dot of the corresponding channel indicates that the switch insertion is recognized and is in the current channel. If there is no blue dot, the switch insertion is not recognized\u3002 If you use PiKVM software, please configure it according to the following instructions. Log in to PiKVM through SSH. The user name and password are root; Uses the rw command on the terminal to change the system to a read-write system; Edit /etc/kvmd/override. yaml this file to make it contain the following contents. That is, add after the original content. kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] Use the ro command on the terminal to reset the system to a read-only system; Use 'systemctl restart kvmd' on the terminal to restart the service; Enter the PiKVM web interface and click the GPIO menu. You should see 4 inputs, one of which has a green circle to indicate that it is currently selected. Click Other Inputs to change the selected host. Control protocol If you want to use the blicube switch on other platforms, please refer to the following protocol The communication baud rate is 19200 The message sent to switch by switching to channel 1 is SW1\\r\\nG01gA The message sent to switch by switching to channel 2 is SW2\\r\\nG02gA The message sent to switch by switching to channel 3 is SW3\\r\\nG03gA The message sent to switch by switching to channel 4 is SW4\\r\\nG04gA The message returned by the switch for the current channel is: G01gA , G02gA , G03gA , G04gA Packing list product quantity note HDMI KVM Switch(4-channel) 1 110mm * 60mm * 33mm Desktop controller 1 USB cable of Desktop controller 4 length: 1.2m HDMI(Standard) cable 5 length: 1.5m USB power cable 1 length: 0.8m USB cable of KVM 1 length: 1.5m USB cable of Desktop controller 1 length: 1m","title":"Multiport KVM over IP"},{"location":"switch-guide/#hdmi-switch-mannul","text":"BliKVM-Switch-V1.0 uses and tests video, supporting BliKVM and PiKVM","title":"HDMI Switch Mannul"},{"location":"switch-guide/#introduction","text":"BliKVM-Switch-V1.0 is a four channel HDMI+USB switch, which supports panel button, desktop controller, KVM remote to switch between computers. Maximum support of the switch itself 4K@60HZ Plug and play, drive free. BliKVM-Switch-V1.0 uses the same hardware solution as XH-HK4401, AG7210 HDMI switching chip supports up to 4K@60Hz, CH444G USB switching chip supports USB2.0. The difference is that BliKVM-Switch-V1.0 is equipped with KVM USB cable, which can realize KVM port selection. BliKVM-Switch-V1.0 is compatible with BliKVM and PiKVM. points for attention The switch can be powered directly from the USB input to the computer, that is, the switch can work normally without power supply. If the USB power supply of the controlled computer cannot make the switch work, the switch can be powered independently. The switch package only provides a USB power cable, but does not provide a power adapter. The customer needs to configure a power adapter (5V). Desktop controller can control HDMI switch with USB cable. For customers who do not use KVM, this is another way of switching for easy cable management. HDMI input support up to 4096x2160/60Hz resolution 4K 60Hz input, the power is about 200 mW.","title":"Introduction"},{"location":"switch-guide/#interface-diagram","text":"Front and back interface diagram, the control interface in the right figure is the remote control interface. Schematic Diagram of Side Interface. Equipment connection diagram.","title":"Interface diagram"},{"location":"switch-guide/#software-configuration","text":"If you are using BliKVM software and have powered on the switch and connected the cables before starting BliKVM, no additional configuration is needed. BliKVM will automatically detect the switch when it starts. If automatic detection fails, you can manually specify the switch device. First, confirm the device descriptor name of the switch by using the terminal, such as /dev/ttyUSB0 . Then, edit the switch_handle field in /usr/bin/blikvm/package.json and assign /dev/ttyUSB0 to it. Afterward, restart BliKVM. Click MORE in the lower left corner, find the BliKVM switch column, and then switch. Note that the flashing blue dot of the corresponding channel indicates that the switch insertion is recognized and is in the current channel. If there is no blue dot, the switch insertion is not recognized\u3002 If you use PiKVM software, please configure it according to the following instructions. Log in to PiKVM through SSH. The user name and password are root; Uses the rw command on the terminal to change the system to a read-write system; Edit /etc/kvmd/override. yaml this file to make it contain the following contents. That is, add after the original content. kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] Use the ro command on the terminal to reset the system to a read-only system; Use 'systemctl restart kvmd' on the terminal to restart the service; Enter the PiKVM web interface and click the GPIO menu. You should see 4 inputs, one of which has a green circle to indicate that it is currently selected. Click Other Inputs to change the selected host.","title":"Software configuration"},{"location":"switch-guide/#control-protocol","text":"If you want to use the blicube switch on other platforms, please refer to the following protocol The communication baud rate is 19200 The message sent to switch by switching to channel 1 is SW1\\r\\nG01gA The message sent to switch by switching to channel 2 is SW2\\r\\nG02gA The message sent to switch by switching to channel 3 is SW3\\r\\nG03gA The message sent to switch by switching to channel 4 is SW4\\r\\nG04gA The message returned by the switch for the current channel is: G01gA , G02gA , G03gA , G04gA","title":"Control protocol"},{"location":"switch-guide/#packing-list","text":"product quantity note HDMI KVM Switch(4-channel) 1 110mm * 60mm * 33mm Desktop controller 1 USB cable of Desktop controller 4 length: 1.2m HDMI(Standard) cable 5 length: 1.5m USB power cable 1 length: 0.8m USB cable of KVM 1 length: 1.5m USB cable of Desktop controller 1 length: 1m","title":"Packing list"},{"location":"tailscale/","text":"Tailscale VPN Tailscale can be used to access your BliKVM from the public internet. It is a convenient and free networking tool for setting up a small VPN network. This document provides an example for accessing your BliKVM over the internet, but you can also use Zerotier or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the Tailscale documentation. BliKVM\u5b89\u88c5Tailscale First, make sure that your system has read-write access. If it's a read-only system, use the rw command to make it writable. Then, proceed with the Tailscale installation by running the following command: curl -fsSL https://tailscale.com/install.sh | sh Note that in some regions, such as China, downloading Tailscale directly might be problematic due to network restrictions. Please configure your network accordingly. Adding BliKVM to your Tailscale Network Register an account on the Tailscale website and generate your own keys in the settings. On the BliKVM terminal, use the following command to add BliKVM to your Tailscale network: sudo tailscale up --authkey=your-auth-key --accept-routes If everything goes well, you can run ip addr show tailscale0 on the BliKVM terminal to view the IP address assigned by Tailscale for the virtual network. Here's an example output: 3: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100.126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever The IP address, such as 100.126.223.28, can be used to access the BliKVM web interface from your host machine. \u4e3b\u673a\u5b89\u88c5Tailscale Download and install Tailscale from the Tailscale website on your controlling host machine. Log in with your Tailscale account, and then you can check the Tailscale admin page to verify if both your machines are online. Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://<tailscale_kvm_ip>","title":"Tailscale VPN"},{"location":"tailscale/#tailscale-vpn","text":"Tailscale can be used to access your BliKVM from the public internet. It is a convenient and free networking tool for setting up a small VPN network. This document provides an example for accessing your BliKVM over the internet, but you can also use Zerotier or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the Tailscale documentation.","title":"Tailscale VPN"},{"location":"tailscale/#blikvmtailscale","text":"First, make sure that your system has read-write access. If it's a read-only system, use the rw command to make it writable. Then, proceed with the Tailscale installation by running the following command: curl -fsSL https://tailscale.com/install.sh | sh Note that in some regions, such as China, downloading Tailscale directly might be problematic due to network restrictions. Please configure your network accordingly.","title":"BliKVM\u5b89\u88c5Tailscale"},{"location":"tailscale/#adding-blikvm-to-your-tailscale-network","text":"Register an account on the Tailscale website and generate your own keys in the settings. On the BliKVM terminal, use the following command to add BliKVM to your Tailscale network: sudo tailscale up --authkey=your-auth-key --accept-routes If everything goes well, you can run ip addr show tailscale0 on the BliKVM terminal to view the IP address assigned by Tailscale for the virtual network. Here's an example output: 3: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100.126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever The IP address, such as 100.126.223.28, can be used to access the BliKVM web interface from your host machine.","title":"Adding BliKVM to your Tailscale Network"},{"location":"tailscale/#tailscale","text":"Download and install Tailscale from the Tailscale website on your controlling host machine. Log in with your Tailscale account, and then you can check the Tailscale admin page to verify if both your machines are online. Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://<tailscale_kvm_ip>","title":"\u4e3b\u673a\u5b89\u88c5Tailscale"},{"location":"update/","text":"Software update introduction Introduction The currently available versions of the BLIKVM project are hosted in the release package of the github. The update software function needs to keep the device connected. There are currently two ways to update the software. Method 1: Click the update button through the web interface, and the program will be updated automatically. Restart is required after the update. Method 2: Manually run the script on the KVM terminal to update, and restart after the update. Common causes of upgrade errors The device is not connected to the network; Network access to github is limited; We strongly recommend performing the update while you are in close proximity to the BliKVM hardware you are upgrading. The reason is if anything goes wrong you can intervene. If you are familiar with command-line operations, we recommend manually updating so that you can monitor the command-line status in real time. If the update is abnormal and the web interface cannot exit the update status, use ssh to the terminal can and restart to recover. Manually run the script to update In the terminal rw sudo -i cd /opt/bin/blikvm/ git pull --rebase python3 /opt/bin/blikvm/script/update.py ro Observe the output of the terminal. When you see the message of successful upgrade, the terminal enters reboot, and the reboot takes effect. If you are unable to update successfully due to network issues, you can download the latest release.tar.gz package on another PC with a stable network connection and follow the instructions below for installation. SSH into the device terminal and use tar -zxvf release.tar.gz to extract the release.tar.gz file. rw sudo -i cd /your release path/ python3 install_release.py --releasepath=./ ro You can compare the versions before and after in /usr/bin/blikvm/package.json. If you have upgraded to the specified version, the installation is successful, and you can reboot for the changes to take effect. Web UI update After clicking the More Options button, find the CheckUpdate button and click it. If the available version is found, the pop-up box in the figure below will appear. Click OK to enter the upgrade process. The web interface is temporarily inoperable during the upgrade process. View the current update status by manually refreshing the page. When the message of successful update appears, it means that the update has been successful. Click the restart button, and the new version of software will take effect.","title":"Upgrade"},{"location":"update/#software-update-introduction","text":"","title":"Software update introduction"},{"location":"update/#introduction","text":"The currently available versions of the BLIKVM project are hosted in the release package of the github. The update software function needs to keep the device connected. There are currently two ways to update the software. Method 1: Click the update button through the web interface, and the program will be updated automatically. Restart is required after the update. Method 2: Manually run the script on the KVM terminal to update, and restart after the update. Common causes of upgrade errors The device is not connected to the network; Network access to github is limited; We strongly recommend performing the update while you are in close proximity to the BliKVM hardware you are upgrading. The reason is if anything goes wrong you can intervene. If you are familiar with command-line operations, we recommend manually updating so that you can monitor the command-line status in real time. If the update is abnormal and the web interface cannot exit the update status, use ssh to the terminal can and restart to recover.","title":"Introduction"},{"location":"update/#manually-run-the-script-to-update","text":"In the terminal rw sudo -i cd /opt/bin/blikvm/ git pull --rebase python3 /opt/bin/blikvm/script/update.py ro Observe the output of the terminal. When you see the message of successful upgrade, the terminal enters reboot, and the reboot takes effect. If you are unable to update successfully due to network issues, you can download the latest release.tar.gz package on another PC with a stable network connection and follow the instructions below for installation. SSH into the device terminal and use tar -zxvf release.tar.gz to extract the release.tar.gz file. rw sudo -i cd /your release path/ python3 install_release.py --releasepath=./ ro You can compare the versions before and after in /usr/bin/blikvm/package.json. If you have upgraded to the specified version, the installation is successful, and you can reboot for the changes to take effect.","title":"Manually run the script to update"},{"location":"update/#web-ui-update","text":"After clicking the More Options button, find the CheckUpdate button and click it. If the available version is found, the pop-up box in the figure below will appear. Click OK to enter the upgrade process. The web interface is temporarily inoperable during the upgrade process. View the current update status by manually refreshing the page. When the message of successful update appears, it means that the update has been successful. Click the restart button, and the new version of software will take effect.","title":"Web UI update"},{"location":"usb-splitter-guide/","text":"USB/PWR Splitter guide 1. Introduction The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage. 2.Mechanical Diagram 3.Test video USB splitter Video 4.3D printable case A simple snap fit case for the USB splitter. Download file","title":"USB splitter"},{"location":"usb-splitter-guide/#usbpwr-splitter-guide","text":"","title":"USB/PWR Splitter guide"},{"location":"usb-splitter-guide/#1-introduction","text":"The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage.","title":"1. Introduction"},{"location":"usb-splitter-guide/#2mechanical-diagram","text":"","title":"2.Mechanical Diagram"},{"location":"usb-splitter-guide/#3test-video","text":"USB splitter Video","title":"3.Test video"},{"location":"usb-splitter-guide/#43d-printable-case","text":"A simple snap fit case for the USB splitter. Download file","title":"4.3D printable case"},{"location":"wifi/","text":"Wifi Configure Because BLIKVM has many kinds of hardware and supports different OS, such as BLIKVM OS and PiKVM OS, different OS confifure wifi methods may not be the same. Please confirm the hardware and OS usage before using the method in this document. Please confirm that the hardware you use supports wifi function, for example, the CM400200 version does not have wifi function; If the SOC of KVM hardware is CM4, please confirm whether wifi antenna is connected; PiKVM OS is arch linux; BLIKVM OS raspberry pi series is debian system, and H616 series is armbian system; v1 v2 v3 use raspi-config for wifi configure on raspberry pi debian system Log in to ssh, command: ssh blikvm@ip The system is reloaded as writable. Command: rw Start raspi-config, command: sudo raspi-config Select System Options Select Wireless LAN Select the country where wifi is located, and China will select CN. If it has been set before, this step will skip to 7 Enter the ssid (name) of Wi-Fi Enter the Wi-Fi password. If there is no password, press Enter directly At this time, you will return to the interface in Step 4, press the tab key to select , and press Enter Check whether to connect to wifi. Command: ifconfig wlan0. If you see the ip obtained, you are connected Mount the system as read-only. Command: ro v4 Hardware using Armbian System with armbian-config Log in via SSH using the command: ssh blikvm@ip to access the Armbian system. Enter the following command to launch the armbian-config tool: sudo armbian-config In the armbian-config menu, navigate and select options using the arrow keys and press Enter. Scroll down to the \"Network\" option using the arrow keys and press Enter to enter the submenu. In the \"Network\" submenu, select the \"Wireless\" option and press Enter to enter the Wi-Fi configuration menu. In the Wi-Fi configuration menu, select the \"Connect to Wi-Fi\" option and press Enter to enter the Wi-Fi connection setup. armbian-config will list the available wireless interfaces and already configured networks. Select the wireless interface you want to connect to and press Enter. armbian-config will display the list of available Wi-Fi networks. Use the arrow keys to select the Wi-Fi network you want to connect to and press Enter. If the Wi-Fi network is password-protected, armbian-config will prompt you to enter the Wi-Fi password. Enter the password and press Enter. Wait for a moment while the Armbian system attempts to connect to the specified Wi-Fi network. If the connection is successful, you will see a corresponding message on the screen. Exit the armbian-config tool. Please note that the menu options and configurations mentioned above may vary slightly depending on the specific version of the Armbian system. Make sure to follow the appropriate steps based on your system version and configuration.","title":"Wifi Config"},{"location":"wifi/#wifi-configure","text":"Because BLIKVM has many kinds of hardware and supports different OS, such as BLIKVM OS and PiKVM OS, different OS confifure wifi methods may not be the same. Please confirm the hardware and OS usage before using the method in this document. Please confirm that the hardware you use supports wifi function, for example, the CM400200 version does not have wifi function; If the SOC of KVM hardware is CM4, please confirm whether wifi antenna is connected; PiKVM OS is arch linux; BLIKVM OS raspberry pi series is debian system, and H616 series is armbian system;","title":"Wifi Configure"},{"location":"wifi/#v1-v2-v3-use-raspi-config-for-wifi-configure-on-raspberry-pi-debian-system","text":"Log in to ssh, command: ssh blikvm@ip The system is reloaded as writable. Command: rw Start raspi-config, command: sudo raspi-config Select System Options Select Wireless LAN Select the country where wifi is located, and China will select CN. If it has been set before, this step will skip to 7 Enter the ssid (name) of Wi-Fi Enter the Wi-Fi password. If there is no password, press Enter directly At this time, you will return to the interface in Step 4, press the tab key to select , and press Enter Check whether to connect to wifi. Command: ifconfig wlan0. If you see the ip obtained, you are connected Mount the system as read-only. Command: ro","title":"v1 v2 v3 use raspi-config for wifi configure on raspberry pi debian system"},{"location":"wifi/#v4-hardware-using-armbian-system-with-armbian-config","text":"Log in via SSH using the command: ssh blikvm@ip to access the Armbian system. Enter the following command to launch the armbian-config tool: sudo armbian-config In the armbian-config menu, navigate and select options using the arrow keys and press Enter. Scroll down to the \"Network\" option using the arrow keys and press Enter to enter the submenu. In the \"Network\" submenu, select the \"Wireless\" option and press Enter to enter the Wi-Fi configuration menu. In the Wi-Fi configuration menu, select the \"Connect to Wi-Fi\" option and press Enter to enter the Wi-Fi connection setup. armbian-config will list the available wireless interfaces and already configured networks. Select the wireless interface you want to connect to and press Enter. armbian-config will display the list of available Wi-Fi networks. Use the arrow keys to select the Wi-Fi network you want to connect to and press Enter. If the Wi-Fi network is password-protected, armbian-config will prompt you to enter the Wi-Fi password. Enter the password and press Enter. Wait for a moment while the Armbian system attempts to connect to the specified Wi-Fi network. If the connection is successful, you will see a corresponding message on the screen. Exit the armbian-config tool. Please note that the menu options and configurations mentioned above may vary slightly depending on the specific version of the Armbian system. Make sure to follow the appropriate steps based on your system version and configuration.","title":"v4 Hardware using Armbian System with armbian-config"}]}
\ No newline at end of file
+{"config":{"indexing":"full","lang":["en","ja","ru"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"BLIKVM Overview BLIKVM is an open-source KVM, it has three versions: CM4 Board, Raspberry HAT, PCIE Board. This device helps to manage servers or workstations remotely, regardless of the health of the operating system or whether one is installed. You can fix any problem, configure the BIOS, and even reinstall the OS using the virtual CD-ROM or Flash Drive. Here you will find comprehensive information about all aspects of the operation of BLIKVM. Join our BLIKVM Discord Community for Support, FAQ & News! FEATURE BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 H616 SOC Raspberry CM4 Raspberry CM4 Raspberry 4B Allwinner H616 Supported resolutions 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI Capture TC358743 TC358743 TC358743 MS2131 HDMI Loop Through No No No Yes POE No Yes Yes Yes DC-IN No No No Yes USB-C Power Yes Yes Yes Yes USB Power/Data Splitter Yes Yes(external) Yes Yes Serial Console No Yes Yes Yes ATX controls Yes Yes Yes Yes BIOS controls Yes Yes Yes Yes Open source system Yes Yes Yes Yes Reinstall the controlled computer system Yes Yes Yes Yes FAN Yes(Not support PWM controls) Yes Yes Optional(default with heat sink) Display Module OLED 128x64 white OLED 128x32 white OLED 128x64 white LCD 240x240 color Real Time Clock Yes(DS1307) Yes(PCF8563) Yes(PCF8563) Yes(PCF8563) Case Metallic Black No Metallic Black White Blue Orange(1U rack compatible) Metallic Black(1U rack compatible) Buzzer No No No Yes Custom button No No No Yes Software update Yes Yes Yes Yes 32GB SD Card Yes (OS included) Yes (OS included) Yes (OS included) Yes (OS included) HDMI backpower mitigation No Yes Yes Yes Professional technical support Yes Yes Yes Yes Features Video capture (1080P 60Hz) Keyboard forwarding Mouse forwarding ATX Fan Control Fullscreen mode Paste text from clipboard VPN support Mass Storage Drive (emulate a CD-ROM or Flash Drive) Multiport KVM over IP OLED to display system info, like temp, uptime, IP Password authentication Support multiple languages Wake-on-LAN Guide 1.BLIKVM v1 CM4 version 2.BLIKVM v2 PCIE version 3.BLIKVM v3 HAT version 4.BliKVM v4 Allwinner version","title":"BLIKVM Overview"},{"location":"#blikvm-overview","text":"BLIKVM is an open-source KVM, it has three versions: CM4 Board, Raspberry HAT, PCIE Board. This device helps to manage servers or workstations remotely, regardless of the health of the operating system or whether one is installed. You can fix any problem, configure the BIOS, and even reinstall the OS using the virtual CD-ROM or Flash Drive. Here you will find comprehensive information about all aspects of the operation of BLIKVM. Join our BLIKVM Discord Community for Support, FAQ & News! FEATURE BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 H616 SOC Raspberry CM4 Raspberry CM4 Raspberry 4B Allwinner H616 Supported resolutions 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI Capture TC358743 TC358743 TC358743 MS2131 HDMI Loop Through No No No Yes POE No Yes Yes Yes DC-IN No No No Yes USB-C Power Yes Yes Yes Yes USB Power/Data Splitter Yes Yes(external) Yes Yes Serial Console No Yes Yes Yes ATX controls Yes Yes Yes Yes BIOS controls Yes Yes Yes Yes Open source system Yes Yes Yes Yes Reinstall the controlled computer system Yes Yes Yes Yes FAN Yes(Not support PWM controls) Yes Yes Optional(default with heat sink) Display Module OLED 128x64 white OLED 128x32 white OLED 128x64 white LCD 240x240 color Real Time Clock Yes(DS1307) Yes(PCF8563) Yes(PCF8563) Yes(PCF8563) Case Metallic Black No Metallic Black White Blue Orange(1U rack compatible) Metallic Black(1U rack compatible) Buzzer No No No Yes Custom button No No No Yes Software update Yes Yes Yes Yes 32GB SD Card Yes (OS included) Yes (OS included) Yes (OS included) Yes (OS included) HDMI backpower mitigation No Yes Yes Yes Professional technical support Yes Yes Yes Yes","title":"BLIKVM Overview"},{"location":"#features","text":"Video capture (1080P 60Hz) Keyboard forwarding Mouse forwarding ATX Fan Control Fullscreen mode Paste text from clipboard VPN support Mass Storage Drive (emulate a CD-ROM or Flash Drive) Multiport KVM over IP OLED to display system info, like temp, uptime, IP Password authentication Support multiple languages Wake-on-LAN","title":"Features"},{"location":"#guide","text":"1.BLIKVM v1 CM4 version 2.BLIKVM v2 PCIE version 3.BLIKVM v3 HAT version 4.BliKVM v4 Allwinner version","title":"Guide"},{"location":"BLIHAT-Installation/","text":"BLIHAT Installation Guide 1.Unpack and take out the devices Open the protective bag 2.Install the main device Flip to back Open the case Flip to back, unscrew the two screws on the back Open the protective bag and take out the parts Install Micro SD card Install the FFC cable Install the HAT on Raspberry Pi 4 Install four Hex Spacers Install the C790 module, use the long screws you just removed Install the audio cable Stick a heat conductive sheet on the back of the Raspberry Pi 4 , tear off the protective film of the sheet Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"v3 HAT illustrated instructions"},{"location":"BLIHAT-Installation/#blihat-installation-guide","text":"","title":"BLIHAT Installation Guide"},{"location":"BLIHAT-Installation/#1unpack-and-take-out-the-devices","text":"Open the protective bag","title":"1.Unpack and take out the devices"},{"location":"BLIHAT-Installation/#2install-the-main-device","text":"Flip to back Open the case Flip to back, unscrew the two screws on the back Open the protective bag and take out the parts Install Micro SD card Install the FFC cable Install the HAT on Raspberry Pi 4 Install four Hex Spacers Install the C790 module, use the long screws you just removed Install the audio cable Stick a heat conductive sheet on the back of the Raspberry Pi 4 , tear off the protective film of the sheet Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"2.Install the main device"},{"location":"BLIKVM-CM4-guide/","text":"BLIKVM-CM4 version guide BLIKVM-CM4-V2.2 Video Installation requirements If you have an assembly kit, you will need the following things Raspberry CM4 with 1Gb RAM or more. USB-C to USB-A cable. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit (5.1V 3A USB-C, recommended by the Raspberry Pi). Power supply You must use USB-C to USB-A cable. Use USB-C to USB-C cable can't work, This is an incompatibility in the hardware design and will be fixed in a later version. Basic setup 1. Flash the memory card or eMMC 2.Build BLIKVM according to the video instruction or review the instructions: Video Guide: Metal case step by step Geerling: Engineering Test video Ortimo: BLIKVM with Raspberry PI CM4 16GB EMMC setup 3. Connect BLIKVM to the computer according to the diagram below: HDMI IN and otg port must be connected to the computer. ATX too, but it\u2019s optional, read below. There should be no USB hub between BLIKVM and the computer, as some UEFI/BIOS cannot detect them at the boot stage. BLIKVM supports 1080p60Hz or lower about HDMI source. Connect Ethernet to the network and PWR IN to the BLIKVM power supply. ATX connection To manage the power of your computer, you will connect CN-ATX port to the computer.The user can use the ATX cable provided with the product to connect the product and the motherboard ATX switch of the controlled computer. The length of the ATX cable is 60CM, you can also use the double female Dupont cables. Hardware Features 1\u3001HDMI IN port with I2S 2\u3001ATX controller interface (power on/off, reboot control, PWR and HDD ACT LEDs) 3\u3001USB3.0 port x 2 4\u3001USB-C OTG 5\u3001Real Time Clock (RTC) 6\u3001Gigabit Ethernet 7\u3001Activity LED 8\u3001Micro SD Card socket 9\u3001Power LED 10\u3001I2C display connector 11\u3001nRPI_BOOT Jumper 12\u3001USB-C power input 13\u3001FAN connector 5V 14\u3001CSI-2 date lanes switch 15\u3001CM4 Module Connectors Size 12cm x 7cm x 3.5cm Support 1080p60hz HDMI input First in V2.2 version, there is CSI channel switch. This switch is switch 2 csi channels or 4 csi channels. In other versions, the switch is obsolete. Newer keeps the factory state, ignore this switch. Only flip the switch when the device is powered off, otherwise it may cause permanent damage! The four small switches should be up or down at the same time. The video encoding function of the Raspberry Pi is implemented by the HDMI-to-CSI bridge chip Toshiba TC358743, which supports up to 4 CSI-2 data lanes. The camera interface of Raspberry Pi 4B only supports 2 CSI-2 date lanes(up to 1080P50Hz), Raspberry Pi CM4 can support 4 CSI-2 date lanes(up to 1080P60Hz). Currently, PiKVM only uses two CSI-2 channels. 1\u3001 find edid file: rw vim /etc/kvmd/tc358743-edid.hex write the following 1080p 60Hz EDID into the file tc358743-edid.hex. 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C 2\u3001add csi 4 lanes Edit /boot/config.txt, modify \"dtoverlay=tc358743\" to \"dtoverlay=tc358743,4lane=1\" vim /boot/config.txt ro Now, reboot blikvm, and you can test 1080p 60hz input.","title":"BliKVM v1 CM4 guide"},{"location":"BLIKVM-CM4-guide/#blikvm-cm4-version-guide","text":"BLIKVM-CM4-V2.2 Video","title":"BLIKVM-CM4 version guide"},{"location":"BLIKVM-CM4-guide/#installation-requirements","text":"If you have an assembly kit, you will need the following things Raspberry CM4 with 1Gb RAM or more. USB-C to USB-A cable. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit (5.1V 3A USB-C, recommended by the Raspberry Pi). Power supply You must use USB-C to USB-A cable. Use USB-C to USB-C cable can't work, This is an incompatibility in the hardware design and will be fixed in a later version.","title":"Installation requirements"},{"location":"BLIKVM-CM4-guide/#basic-setup","text":"1. Flash the memory card or eMMC 2.Build BLIKVM according to the video instruction or review the instructions: Video Guide: Metal case step by step Geerling: Engineering Test video Ortimo: BLIKVM with Raspberry PI CM4 16GB EMMC setup 3. Connect BLIKVM to the computer according to the diagram below: HDMI IN and otg port must be connected to the computer. ATX too, but it\u2019s optional, read below. There should be no USB hub between BLIKVM and the computer, as some UEFI/BIOS cannot detect them at the boot stage. BLIKVM supports 1080p60Hz or lower about HDMI source. Connect Ethernet to the network and PWR IN to the BLIKVM power supply.","title":"Basic setup"},{"location":"BLIKVM-CM4-guide/#atx-connection","text":"To manage the power of your computer, you will connect CN-ATX port to the computer.The user can use the ATX cable provided with the product to connect the product and the motherboard ATX switch of the controlled computer. The length of the ATX cable is 60CM, you can also use the double female Dupont cables.","title":"ATX connection"},{"location":"BLIKVM-CM4-guide/#hardware-features","text":"1\u3001HDMI IN port with I2S 2\u3001ATX controller interface (power on/off, reboot control, PWR and HDD ACT LEDs) 3\u3001USB3.0 port x 2 4\u3001USB-C OTG 5\u3001Real Time Clock (RTC) 6\u3001Gigabit Ethernet 7\u3001Activity LED 8\u3001Micro SD Card socket 9\u3001Power LED 10\u3001I2C display connector 11\u3001nRPI_BOOT Jumper 12\u3001USB-C power input 13\u3001FAN connector 5V 14\u3001CSI-2 date lanes switch 15\u3001CM4 Module Connectors","title":"Hardware Features"},{"location":"BLIKVM-CM4-guide/#size","text":"12cm x 7cm x 3.5cm","title":"Size"},{"location":"BLIKVM-CM4-guide/#support-1080p60hz-hdmi-input","text":"First in V2.2 version, there is CSI channel switch. This switch is switch 2 csi channels or 4 csi channels. In other versions, the switch is obsolete. Newer keeps the factory state, ignore this switch. Only flip the switch when the device is powered off, otherwise it may cause permanent damage! The four small switches should be up or down at the same time. The video encoding function of the Raspberry Pi is implemented by the HDMI-to-CSI bridge chip Toshiba TC358743, which supports up to 4 CSI-2 data lanes. The camera interface of Raspberry Pi 4B only supports 2 CSI-2 date lanes(up to 1080P50Hz), Raspberry Pi CM4 can support 4 CSI-2 date lanes(up to 1080P60Hz). Currently, PiKVM only uses two CSI-2 channels. 1\u3001 find edid file: rw vim /etc/kvmd/tc358743-edid.hex write the following 1080p 60Hz EDID into the file tc358743-edid.hex. 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C 2\u3001add csi 4 lanes Edit /boot/config.txt, modify \"dtoverlay=tc358743\" to \"dtoverlay=tc358743,4lane=1\" vim /boot/config.txt ro Now, reboot blikvm, and you can test 1080p 60hz input.","title":"Support 1080p60hz HDMI input"},{"location":"BLIKVM-HAT-guide/","text":"BLIKVM HAT version guide Introduction BLIKVM hat Video The Raspberry Pi IPKVM HAT is an add-on board for Raspberry Pi 4, made especially for KVM Over IP. BLIKVM-RPI4 is a Raspberry Pi 4 PoE KVM HAT. This product\u2019s key features include video capture, ATX adapter,PoE, OLED and RTC. The product has a customized metal case to dissipate heat and provide protection for the HAT. The product can be easily installed on a standard 1U rack. The product is currently perfectly compatible with blikvm image and pikvm image. Installation requirements If you have an assembly kit, you will need the following things Raspberry Pi 4B with 1Gb RAM or more. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit & cable(5.1V 3A USB-C, recommended by the Raspberry Pi). Basic setup 1. Flash the memory card or eMMC 2.Build BLIKVM according to the video instruction or review the illustrated instructions : Video Guide: Metal case step by step 3. Install the ATX adapter board The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. Choose one as needed Use Dupont cables to connect ATX adapter board to motherboard and chassis panel. There are clear pin definitions on the board for easy wiring. Mount the ATX adapter board to the case shell Use a RJ45 network cable to connect the board to the CN-ATX interface of the HAT 4. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the HAT with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 5. Install the USB cable Connect the RPI4 port to the Raspberry Pi 4 Connect the USB port to the controlled computer When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. 6. Test Powered by PoE, the HAT is connected to the router via the network cable The screen displays the current status of the device, including the machine's IP address Access the IP address of the HAT in the browser. Enjoy! Specification HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@50fps. Fixed HDMI back power issue. CN-ATX The CN-ATX interface is connected to the ATX adapter board (an accessory for the HAT)through a network cable, which can turn on, off, and restart the controlled computer. Display A white OLED display with a resolution of 128x32, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. PoE Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A Plug in the PoE jumper cap to enable PoE power supply FAN The IPKVM HAT is fitted with a small fan that is controlled by your Raspberry Pi via GPIO12. Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi via I2C. The coin cell battery is installed under the HDMI IN module. Accessories ATX adapter board This board is connected to the switch port on the motherboard of the controlled computer with DuPont cables. The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. USB/PWR splitter Connect the RPI4 port to your Raspberry Pi 4. Connect the USB port to the controlled computer. When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. Metal case The metal case protects the HAT and improve heat dissipation. There are clear port markings on the case. The case can be easily installed on a standard 1U rack. List Product List Raspberry Pi IPKVM HAT 1 ATX adapter board 1 USB/PWR splitter 1 HDMI pass-through EDID emulator 1 Metal case 1 32G TF card 1 USB Type-C to USB Type-C Cable 30cm 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 List of items prepared by the user Raspberry Pi 4 1 RJ45 network cable 2 USB Type-A to USB Type-C Cable 2 HDMI cable 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"BliKVM v3 HAT guide"},{"location":"BLIKVM-HAT-guide/#blikvm-hat-version-guide","text":"","title":"BLIKVM HAT version guide"},{"location":"BLIKVM-HAT-guide/#introduction","text":"BLIKVM hat Video The Raspberry Pi IPKVM HAT is an add-on board for Raspberry Pi 4, made especially for KVM Over IP. BLIKVM-RPI4 is a Raspberry Pi 4 PoE KVM HAT. This product\u2019s key features include video capture, ATX adapter,PoE, OLED and RTC. The product has a customized metal case to dissipate heat and provide protection for the HAT. The product can be easily installed on a standard 1U rack. The product is currently perfectly compatible with blikvm image and pikvm image.","title":"Introduction"},{"location":"BLIKVM-HAT-guide/#installation-requirements","text":"If you have an assembly kit, you will need the following things Raspberry Pi 4B with 1Gb RAM or more. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit & cable(5.1V 3A USB-C, recommended by the Raspberry Pi).","title":"Installation requirements"},{"location":"BLIKVM-HAT-guide/#basic-setup","text":"1. Flash the memory card or eMMC 2.Build BLIKVM according to the video instruction or review the illustrated instructions : Video Guide: Metal case step by step 3. Install the ATX adapter board The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. Choose one as needed Use Dupont cables to connect ATX adapter board to motherboard and chassis panel. There are clear pin definitions on the board for easy wiring. Mount the ATX adapter board to the case shell Use a RJ45 network cable to connect the board to the CN-ATX interface of the HAT 4. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the HAT with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 5. Install the USB cable Connect the RPI4 port to the Raspberry Pi 4 Connect the USB port to the controlled computer When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. 6. Test Powered by PoE, the HAT is connected to the router via the network cable The screen displays the current status of the device, including the machine's IP address Access the IP address of the HAT in the browser. Enjoy!","title":"Basic setup"},{"location":"BLIKVM-HAT-guide/#specification","text":"HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@50fps. Fixed HDMI back power issue. CN-ATX The CN-ATX interface is connected to the ATX adapter board (an accessory for the HAT)through a network cable, which can turn on, off, and restart the controlled computer. Display A white OLED display with a resolution of 128x32, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. PoE Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A Plug in the PoE jumper cap to enable PoE power supply FAN The IPKVM HAT is fitted with a small fan that is controlled by your Raspberry Pi via GPIO12. Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi via I2C. The coin cell battery is installed under the HDMI IN module.","title":"Specification"},{"location":"BLIKVM-HAT-guide/#accessories","text":"","title":"Accessories"},{"location":"BLIKVM-HAT-guide/#atx-adapter-board","text":"This board is connected to the switch port on the motherboard of the controlled computer with DuPont cables. The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket.","title":"ATX adapter board"},{"location":"BLIKVM-HAT-guide/#usbpwr-splitter","text":"Connect the RPI4 port to your Raspberry Pi 4. Connect the USB port to the controlled computer. When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply.","title":"USB/PWR splitter"},{"location":"BLIKVM-HAT-guide/#hdmi-pass-through-edid-emulator","text":"If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer.","title":"HDMI pass-through EDID emulator"},{"location":"BLIKVM-HAT-guide/#metal-case","text":"The metal case protects the HAT and improve heat dissipation. There are clear port markings on the case. The case can be easily installed on a standard 1U rack.","title":"Metal case"},{"location":"BLIKVM-HAT-guide/#list","text":"","title":"List"},{"location":"BLIKVM-HAT-guide/#product-list","text":"Raspberry Pi IPKVM HAT 1 ATX adapter board 1 USB/PWR splitter 1 HDMI pass-through EDID emulator 1 Metal case 1 32G TF card 1 USB Type-C to USB Type-C Cable 30cm 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Phillips screwdriver 1 Cross Wrench Sleeve 1","title":"Product List"},{"location":"BLIKVM-HAT-guide/#list-of-items-prepared-by-the-user","text":"Raspberry Pi 4 1 RJ45 network cable 2 USB Type-A to USB Type-C Cable 2 HDMI cable 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"List of items prepared by the user"},{"location":"BLIKVM-PCIE-guide/","text":"BLIKVM PCIe Introduction BLIKVM PCIe is a PCIe add-in card based on Raspberry Pi CM4 for KVM Over IP. This product\u2019s key features include video capture, ATX controller, PoE, OLED , UART and RTC. The card has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. The product is currently perfectly compatible with blikvm image and pikvm image. Installation requirements You will need the following things Raspberry Pi CM4(if you order PCIe card only). PoE-sourcing equipment or 5V/3A USB adapter. CR1220 coin cell battery. Basic setup 1. If you have an assembly kit, Flash the memory card or eMMC 2.Build BLIKVM according to the illustrated instructions : Geerling: Engineering Test video Craft Computing: Never Pay For IPMI Again - BliKVM Review Specification hardware feature list HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@60fps. Fixed HDMI back power issue. USB-PC The BLIKVM PCIe card provides two USB interfaces, one is PC-IN (type c interface) and the other is USB-PC2 (pin interface). The purpose of these two interfaces is to connect to the USB of the controlled computer, used to control the mouse and keyboard. At the same time, only one interface can be used. The purpose of designing two interfaces is to directly use USB PC2 when the user's PC host has a row pin USB interface, which will make the wiring more concise. POWER-IN When using PoE power supply, there is no need to connect the PWR-IN port. When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. ETHERNET-PoE Gigabit Ethernet port Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A ATX-Connecter Connect to power control interface on the motherboard of the controlled computer with DuPont cables. It can turn on, off, and restart the controlled computer. The pin is defined on the printing of the PCIe board, BTN means button. According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the PCIe board. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and PCIe. See the following figure for the connection relationship\uff1a OLED Display A white OLED display with a resolution of 128x64, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. FAN The Card HAT is fitted with a small fan that is controlled by your Raspberry Pi CM4 via GPIO12. BOOT Fit jumper to disable eMMC Boot Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi CM4 via I2C. The CR1220 battery is installed under the HDMI IN module. UART Connect the serial port to debug your Raspberry Pi CM4. The uart of Raspberry Pi CM4. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. Connect serial cable wires to G T R connectors on the PCIe board. NOTE: black wire = Ground, whiTe = Tx, and gReen = Rx; For specific methods, please refer to this document . Accessories HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. VGA-HDMI module When your device does not have an HDMI output interface, you can use a VGA to HDMI module. USB to TTL module Connect your computer usb interface with the serial port of BLIKVM to debug your Raspberry Pi CM4. Fan Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card. Dimensions Test Video BLIKVM hardware PCIe version is tested wonderful based on pikvm software. Notes To prevent the CM4 module from contacting the SD card holder, do not remove the insulating tape List Product List BLIKVM PCIe card version 1 BLIKVM PCIe add-in card 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 BLIKVM PCIe plug-n-play version 1 BLIKVM PCIe add-in card 1 CM4 102000 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 List of items prepared by the user Raspberry Pi CM4(if you order PCIe card only) 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"BliKVM v2 PCIe guide"},{"location":"BLIKVM-PCIE-guide/#blikvm-pcie","text":"","title":"BLIKVM PCIe"},{"location":"BLIKVM-PCIE-guide/#introduction","text":"BLIKVM PCIe is a PCIe add-in card based on Raspberry Pi CM4 for KVM Over IP. This product\u2019s key features include video capture, ATX controller, PoE, OLED , UART and RTC. The card has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. The product is currently perfectly compatible with blikvm image and pikvm image.","title":"Introduction"},{"location":"BLIKVM-PCIE-guide/#installation-requirements","text":"You will need the following things Raspberry Pi CM4(if you order PCIe card only). PoE-sourcing equipment or 5V/3A USB adapter. CR1220 coin cell battery.","title":"Installation requirements"},{"location":"BLIKVM-PCIE-guide/#basic-setup","text":"1. If you have an assembly kit, Flash the memory card or eMMC 2.Build BLIKVM according to the illustrated instructions : Geerling: Engineering Test video Craft Computing: Never Pay For IPMI Again - BliKVM Review","title":"Basic setup"},{"location":"BLIKVM-PCIE-guide/#specification","text":"hardware feature list HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@60fps. Fixed HDMI back power issue. USB-PC The BLIKVM PCIe card provides two USB interfaces, one is PC-IN (type c interface) and the other is USB-PC2 (pin interface). The purpose of these two interfaces is to connect to the USB of the controlled computer, used to control the mouse and keyboard. At the same time, only one interface can be used. The purpose of designing two interfaces is to directly use USB PC2 when the user's PC host has a row pin USB interface, which will make the wiring more concise. POWER-IN When using PoE power supply, there is no need to connect the PWR-IN port. When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. ETHERNET-PoE Gigabit Ethernet port Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A ATX-Connecter Connect to power control interface on the motherboard of the controlled computer with DuPont cables. It can turn on, off, and restart the controlled computer. The pin is defined on the printing of the PCIe board, BTN means button. According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the PCIe board. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and PCIe. See the following figure for the connection relationship\uff1a OLED Display A white OLED display with a resolution of 128x64, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. FAN The Card HAT is fitted with a small fan that is controlled by your Raspberry Pi CM4 via GPIO12. BOOT Fit jumper to disable eMMC Boot Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi CM4 via I2C. The CR1220 battery is installed under the HDMI IN module. UART Connect the serial port to debug your Raspberry Pi CM4. The uart of Raspberry Pi CM4. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. Connect serial cable wires to G T R connectors on the PCIe board. NOTE: black wire = Ground, whiTe = Tx, and gReen = Rx; For specific methods, please refer to this document .","title":"Specification"},{"location":"BLIKVM-PCIE-guide/#accessories","text":"HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. VGA-HDMI module When your device does not have an HDMI output interface, you can use a VGA to HDMI module. USB to TTL module Connect your computer usb interface with the serial port of BLIKVM to debug your Raspberry Pi CM4. Fan Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card.","title":"Accessories"},{"location":"BLIKVM-PCIE-guide/#dimensions","text":"","title":"Dimensions"},{"location":"BLIKVM-PCIE-guide/#test-video","text":"BLIKVM hardware PCIe version is tested wonderful based on pikvm software.","title":"Test Video"},{"location":"BLIKVM-PCIE-guide/#notes","text":"To prevent the CM4 module from contacting the SD card holder, do not remove the insulating tape","title":"Notes"},{"location":"BLIKVM-PCIE-guide/#list","text":"","title":"List"},{"location":"BLIKVM-PCIE-guide/#product-list","text":"BLIKVM PCIe card version 1 BLIKVM PCIe add-in card 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 BLIKVM PCIe plug-n-play version 1 BLIKVM PCIe add-in card 1 CM4 102000 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1","title":"Product List"},{"location":"BLIKVM-PCIE-guide/#list-of-items-prepared-by-the-user","text":"Raspberry Pi CM4(if you order PCIe card only) 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"List of items prepared by the user"},{"location":"BLIKVM-PCIe-installation/","text":"BLIKVM PCIe CM4 Installation Guide 1.Unpack and take out the devices Product List 2.Install the main device Install CM4 and 4 Hex spacers (This article takes CM4 lite as an example, using the image in the Micro SD card, CM4 eMMC user need to burn the image by yourself.)Stick a heat conductive sheet on the top of CM4 , tear off the protective film of the sheet. Install metal heatsink The main device installation is complete. 3.Connect USB and ATX The motherboard used in this article is Asus H520M-E, the interface definition of different motherboards may be different, please refer to your motherboard manual. 4.Connect OLED The OLED you received does not have a bracket installed. Please refer to the picture for installation. In addition, OLED support is made of acrylic material, which needs to be used after removing the protective film on the surface. The above is the installation steps, and the effect of not tearing the film is as follows. In actual use, please remove the protective film. 5.Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the product with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 6.Connect the network cable Gigabit Ethernet port standard: IEEE 802.3af PoE input voltage:37v-57v. When using PoE power supply, there is no need to connect the PWR-IN port. 7.Connect PWR-IN When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. 8.Test OLED screen showing device IP and other information. Access the IP address in browser. After passing the test, install the product into the computer case. 9.Install the product into the computer case Disconnect power and wiring, install the product on the motherboard, and reconnect the cables after installation is complete. The color of ATX cable received in different batches may be different. Please directly refer to the pin definition for connection Enjoy! Appendix 1.Install a low profile PCIe I/O bracket Note Appendix 2.Install the cooling fan Usually the metal heatsink is sufficient, the cooling fan is not necessary. The cooling fan is controlled by CM4 via GPIO12. Appendix 3.Install wifi antenna Note","title":"v2 PCIe illustrated instructions"},{"location":"BLIKVM-PCIe-installation/#blikvm-pcie-cm4-installation-guide","text":"","title":"BLIKVM PCIe CM4 Installation Guide"},{"location":"BLIKVM-PCIe-installation/#1unpack-and-take-out-the-devices","text":"Product List","title":"1.Unpack and take out the devices"},{"location":"BLIKVM-PCIe-installation/#2install-the-main-device","text":"Install CM4 and 4 Hex spacers (This article takes CM4 lite as an example, using the image in the Micro SD card, CM4 eMMC user need to burn the image by yourself.)Stick a heat conductive sheet on the top of CM4 , tear off the protective film of the sheet. Install metal heatsink The main device installation is complete.","title":"2.Install the main device"},{"location":"BLIKVM-PCIe-installation/#3connect-usb-and-atx","text":"The motherboard used in this article is Asus H520M-E, the interface definition of different motherboards may be different, please refer to your motherboard manual.","title":"3.Connect USB and ATX"},{"location":"BLIKVM-PCIe-installation/#4connect-oled","text":"The OLED you received does not have a bracket installed. Please refer to the picture for installation. In addition, OLED support is made of acrylic material, which needs to be used after removing the protective film on the surface. The above is the installation steps, and the effect of not tearing the film is as follows. In actual use, please remove the protective film.","title":"4.Connect OLED"},{"location":"BLIKVM-PCIe-installation/#5connect-the-hdmi-cable","text":"Connect the HDMI output port of the computer directly to the HDMI IN port of the product with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer.","title":"5.Connect the HDMI cable"},{"location":"BLIKVM-PCIe-installation/#6connect-the-network-cable","text":"Gigabit Ethernet port standard: IEEE 802.3af PoE input voltage:37v-57v. When using PoE power supply, there is no need to connect the PWR-IN port.","title":"6.Connect the network cable"},{"location":"BLIKVM-PCIe-installation/#7connect-pwr-in","text":"When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply.","title":"7.Connect PWR-IN"},{"location":"BLIKVM-PCIe-installation/#8test","text":"OLED screen showing device IP and other information. Access the IP address in browser. After passing the test, install the product into the computer case.","title":"8.Test"},{"location":"BLIKVM-PCIe-installation/#9install-the-product-into-the-computer-case","text":"Disconnect power and wiring, install the product on the motherboard, and reconnect the cables after installation is complete. The color of ATX cable received in different batches may be different. Please directly refer to the pin definition for connection Enjoy!","title":"9.Install the product into the computer case"},{"location":"BLIKVM-PCIe-installation/#appendix-1install-a-low-profile-pcie-io-bracket","text":"Note","title":"Appendix 1.Install a low profile PCIe  I/O bracket"},{"location":"BLIKVM-PCIe-installation/#appendix-2install-the-cooling-fan","text":"Usually the metal heatsink is sufficient, the cooling fan is not necessary. The cooling fan is controlled by CM4 via GPIO12.","title":"Appendix 2.Install the cooling fan"},{"location":"BLIKVM-PCIe-installation/#appendix-3install-wifi-antenna","text":"Note","title":"Appendix 3.Install wifi antenna"},{"location":"BliKVM-v4-guide/","text":"BliKVM v4 Allwinner BliKVM v4 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM V4 Datasheet Features Video capture (HDMI, support 4K@30Hz input) Keyboard forwarding Mouse forwarding HDMI video loop through ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE & DC Support WiFi Serial console port 1.33 inch color display Real Time Clock (RTC) Installation Requirements In addition to the v4 kit, you will need the following equipment: Power adapter (5V 3A, USB-A port, or 12V 2A DC port). If you plan to use PoE (Power over Ethernet) or if the USB ports on your controlled computers provide sufficient power, a separate power adapter is not required. HDMI cables (at least one). If you also need to use the HDMI loop-out interface, you will need two cables. Ethernet cable(s) (provide based on your requirements). One cable is required for using the ATX power switch function, and one cable is required for using the Ethernet connection. USB-C to USB-A cable (for mouse and keyboard data transmission). info \"Video Guide: Unpacking and connecting case step by step\" Installation Steps 1. Open the v4 kit package and connect the BliKVM to the controlled computer according to the connection diagram shown below: ATX Connection Please refer to the ATX Connection Guide . 2. Once all the cables are connected, power on the BliKVM. Wait until the display shows the interface, indicating that the device has started up successfully. 3. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. 4. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 5. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience! Video Mode v4 supports a maximum video input of 4K30Hz, and the default transmission resolution is 1920x1080. Product List BLIKVM v4 1 WiFi Antenna 1 ATX adapter board 1 ATX Dupont Cables 8pin Male to Male 60cm 1 ATX Dupont Cables 8pin Male to Female 60cm 1 1U Rack Mounting Ears 2 M2.5x5 Screws 8 Silicone Bumper Pellets 1 Dev If you want to develop or port software on v4 hardware yourself, you can refer to this hardware resource description .","title":"BliKVM v4 Allwinner guide"},{"location":"BliKVM-v4-guide/#blikvm-v4-allwinner","text":"BliKVM v4 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM V4 Datasheet","title":"BliKVM v4 Allwinner"},{"location":"BliKVM-v4-guide/#features","text":"Video capture (HDMI, support 4K@30Hz input) Keyboard forwarding Mouse forwarding HDMI video loop through ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE & DC Support WiFi Serial console port 1.33 inch color display Real Time Clock (RTC)","title":"Features"},{"location":"BliKVM-v4-guide/#installation-requirements","text":"In addition to the v4 kit, you will need the following equipment: Power adapter (5V 3A, USB-A port, or 12V 2A DC port). If you plan to use PoE (Power over Ethernet) or if the USB ports on your controlled computers provide sufficient power, a separate power adapter is not required. HDMI cables (at least one). If you also need to use the HDMI loop-out interface, you will need two cables. Ethernet cable(s) (provide based on your requirements). One cable is required for using the ATX power switch function, and one cable is required for using the Ethernet connection. USB-C to USB-A cable (for mouse and keyboard data transmission). info \"Video Guide: Unpacking and connecting case step by step\"","title":"Installation Requirements"},{"location":"BliKVM-v4-guide/#installation-steps","text":"1. Open the v4 kit package and connect the BliKVM to the controlled computer according to the connection diagram shown below: ATX Connection Please refer to the ATX Connection Guide . 2. Once all the cables are connected, power on the BliKVM. Wait until the display shows the interface, indicating that the device has started up successfully. 3. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. 4. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 5. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience!","title":"Installation Steps"},{"location":"BliKVM-v4-guide/#video-mode","text":"v4 supports a maximum video input of 4K30Hz, and the default transmission resolution is 1920x1080.","title":"Video Mode"},{"location":"BliKVM-v4-guide/#product-list","text":"BLIKVM v4 1 WiFi Antenna 1 ATX adapter board 1 ATX Dupont Cables 8pin Male to Male 60cm 1 ATX Dupont Cables 8pin Male to Female 60cm 1 1U Rack Mounting Ears 2 M2.5x5 Screws 8 Silicone Bumper Pellets 1","title":"Product List"},{"location":"BliKVM-v4-guide/#dev","text":"If you want to develop or port software on v4 hardware yourself, you can refer to this hardware resource description .","title":"Dev"},{"location":"Datasheet-BliKVM-v4/","text":"BliKVM v4 Allwinner (H616 SOC) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! Connectivity diagram 1 USB 2.0 port 10 Antenna interface 2 Power Input 5V 3A & UART 11 RJ45 100M Ethernet port & PoE 3 RJ45 ATX control port 12 Display 1.33 inch LCD 4 HDMI video loop through port 13 Power LED (red) 5 USB-PC port 14 User defined button SW1 6 Power Input 12V 2A 5.5*2.1mm 15 ACT LED (green) 7 HDMI video input port 16 Display ON/OFF button 8 HDMI input status LED (green) 17 Micro SD card slot 9 HDMI output status LED (yellow) Specifications Parameter name Characteristics Power 5V 3A 5V port, USB-PC port 12V 2A 12V port PoE Power over Ethernet (IEEE802.3af compliant) 48V DC Connectivity/Interfaces HDMI-IN HDMI video input port HDMI-OUT HDMI video loop through port USB-PC Keyboard, mouse, mass storage, and other external device emulation) ATX Turn on/off or restart the controlled computer WiFi & Bluetooth IEEE802.11 b/g/n + BLE4.2 Micro SD card slot Persistent storage for OS and your data 5V port 5V 3A power or serial console management port Displays and indicators LED indicators Power LED, ACT LED, HDMI input status LED (green)\uff0c HDMI output status LED (yellow) LCD display LCD 240x240 1.33 inch User defined button SW1 Buzzer Find me Video Supported resolutions Up to 4k@30Hz Video compression methods MJPEG Core Chip ALLWINNER H616 RAM 1GB Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 100 (L) x 134 (W) x 44.4 (H) mm Weight 0.45 kg Dimensions Schematic Diagram","title":"BliKVM v4 Allwinner (H616 SOC)"},{"location":"Datasheet-BliKVM-v4/#blikvm-v4-allwinner-h616-soc","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"BliKVM v4 Allwinner (H616 SOC)"},{"location":"Datasheet-BliKVM-v4/#connectivity-diagram","text":"1 USB 2.0 port 10 Antenna interface 2 Power Input 5V 3A & UART 11 RJ45 100M Ethernet port & PoE 3 RJ45 ATX control port 12 Display 1.33 inch LCD 4 HDMI video loop through port 13 Power LED (red) 5 USB-PC port 14 User defined button SW1 6 Power Input 12V 2A 5.5*2.1mm 15 ACT LED (green) 7 HDMI video input port 16 Display ON/OFF button 8 HDMI input status LED (green) 17 Micro SD card slot 9 HDMI output status LED (yellow)","title":"Connectivity diagram"},{"location":"Datasheet-BliKVM-v4/#specifications","text":"Parameter name Characteristics Power 5V 3A 5V port, USB-PC port 12V 2A 12V port PoE Power over Ethernet (IEEE802.3af compliant) 48V DC Connectivity/Interfaces HDMI-IN HDMI video input port HDMI-OUT HDMI video loop through port USB-PC Keyboard, mouse, mass storage, and other external device emulation) ATX Turn on/off or restart the controlled computer WiFi & Bluetooth IEEE802.11 b/g/n + BLE4.2 Micro SD card slot Persistent storage for OS and your data 5V port 5V 3A power or serial console management port Displays and indicators LED indicators Power LED, ACT LED, HDMI input status LED (green)\uff0c HDMI output status LED (yellow) LCD display LCD 240x240 1.33 inch User defined button SW1 Buzzer Find me Video Supported resolutions Up to 4k@30Hz Video compression methods MJPEG Core Chip ALLWINNER H616 RAM 1GB Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 100 (L) x 134 (W) x 44.4 (H) mm Weight 0.45 kg","title":"Specifications"},{"location":"Datasheet-BliKVM-v4/#dimensions-schematic-diagram","text":"","title":"Dimensions Schematic Diagram"},{"location":"Dev-BliKVM-v4-Allwinner/","text":"Dev BliKVM v4 Allwinner (H616 SOC) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! System Block Diagram Functional Module Panel Function Pin Description Button SW1 GPIOI1(257) Press for high level Button SW1 GPIOI2(258) Press for high level LED ACT GPIOI5(261) Low level enable LED LED PWR 3V3 PWR LED is always on after power on ATX Function Pin Description LED-PWR GPIOH10(234) Light on for high level LED-HDD GPIOH9(233) Light on for high level SW-PWR GPIOH4(228) High level enable SW-RST GPIOI16(272) High level enable BUZZER Function Pin Description Buzzer GPIOI15(271) High level enable FAN Function Pin Description Fan GPIOI13(269) High level enable LCD Display 1.33-inch LCD display module, driver chip ST7789, resolution 240x240. Function Pin Description LCD_EN GPIOI4(260) Backlight high level enable LCD_RST GPIOI6(262) Reset Low level enable LCD_DC GPIOI3(259) Data/command control pin SPI1_CS GPIOH5 SPI1_CLK GPIOH6 SPI1_MOSI GPIOH7 GND GND 3V3 3V3","title":"v4 Allwinner Dev Guide"},{"location":"Dev-BliKVM-v4-Allwinner/#dev-blikvm-v4-allwinner-h616-soc","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"Dev BliKVM v4 Allwinner (H616 SOC)"},{"location":"Dev-BliKVM-v4-Allwinner/#system-block-diagram","text":"","title":"System Block Diagram"},{"location":"Dev-BliKVM-v4-Allwinner/#functional-module","text":"","title":"Functional Module"},{"location":"Dev-BliKVM-v4-Allwinner/#panel","text":"Function Pin Description Button SW1 GPIOI1(257) Press for high level Button SW1 GPIOI2(258) Press for high level LED ACT GPIOI5(261) Low level enable LED LED PWR 3V3 PWR LED is always on after power on","title":"Panel"},{"location":"Dev-BliKVM-v4-Allwinner/#atx","text":"Function Pin Description LED-PWR GPIOH10(234) Light on for high level LED-HDD GPIOH9(233) Light on for high level SW-PWR GPIOH4(228) High level enable SW-RST GPIOI16(272) High level enable","title":"ATX"},{"location":"Dev-BliKVM-v4-Allwinner/#buzzer","text":"Function Pin Description Buzzer GPIOI15(271) High level enable","title":"BUZZER"},{"location":"Dev-BliKVM-v4-Allwinner/#fan","text":"Function Pin Description Fan GPIOI13(269) High level enable","title":"FAN"},{"location":"Dev-BliKVM-v4-Allwinner/#lcd-display","text":"1.33-inch LCD display module, driver chip ST7789, resolution 240x240. Function Pin Description LCD_EN GPIOI4(260) Backlight high level enable LCD_RST GPIOI6(262) Reset Low level enable LCD_DC GPIOI3(259) Data/command control pin SPI1_CS GPIOH5 SPI1_CLK GPIOH6 SPI1_MOSI GPIOH7 GND GND 3V3 3V3","title":"LCD Display"},{"location":"Expand_Filesystem/","text":"Expand Filesystem If you find that the free space of the raspberry pi SD card or eMMC is smaller than the capacity of the actual SD card or eMMC, you need to do the following to expand the raspberry pi. If you find that the system does not have the raspi config tool, you can use Method 2 (use the GParted partition tool). Method 1: Use raspi-config tool If you are using a mirror after June 2023 and have added a third read-write partition, this method is no longer applicable. Please refer to method 2 and method 3. 1. open raspi-config. sudo raspi-config 2. choose Advancd Options\uff1a 3. choose Expand Filesystem\uff1a 4. Ok: 5. Execute the command resize2fs /dev/mmcblk0p2 in the terminal to see that the SD card has been successfully expanded. Method 2: Use GParted tool 1. Connect the SD card or EMMc that has burned the image to the computer through USB. Take the GParted partition tool under Linux as an example. Other platforms also have similar partition tools. Open GParted software and select SD card: 2. By observing the partition of the SD card in the above figure, we can find that 2.01GB and 21.87GB of space are unused before and after the sdb3 partition, which is the space we want to expand. Select the sdb3 partition and click Resize. 3. You can drag the white partition of sdb3 to the leftmost and rightmost, or fill in 25958 with \"Previous Free Space\" as \"0\" and \"New Size\" as \"Maximum Size\", and then click Resize in the lower right corner. Then click OK to see that all unused space of sd has been used. 4. Insert the SD card into the device and start it. Method 3: Use script If you are using a BliKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand. sh on any path, and write the following content to expand.sh #!/bin/bash set -x resize_mmcblk0p3() { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100% resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" If you are using a PiKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand. sh on any path, and write the following content to expand.sh #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab; then part=$(grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}') # shellcheck disable=SC2206 splitted=(${part//=/ }) if [ \"${splitted[0]}\" == LABEL ]; then label=${splitted[1]} part=$(blkid -c /dev/null -L \"$label\") else label=PIMSD fi unset splitted disk=/dev/$(lsblk -no pkname \"$part\") npart=$(cat \"/sys/class/block/${part//\\/dev\\//}/partition\") umount \"$part\" parted \"$disk\" -a optimal -s resizepart \"$npart\" 100% yes | mkfs.ext4 -L \"$label\" -F -m 0 \"$part\" mount \"$part\" unset disk part npart label fi 2. Execute 'bash expand. sh' on the terminal and wait for the execution to complete.","title":"Expand Filesystem"},{"location":"Expand_Filesystem/#expand-filesystem","text":"If you find that the free space of the raspberry pi SD card or eMMC is smaller than the capacity of the actual SD card or eMMC, you need to do the following to expand the raspberry pi. If you find that the system does not have the raspi config tool, you can use Method 2 (use the GParted partition tool).","title":"Expand Filesystem"},{"location":"Expand_Filesystem/#method-1-use-raspi-config-tool","text":"If you are using a mirror after June 2023 and have added a third read-write partition, this method is no longer applicable. Please refer to method 2 and method 3. 1. open raspi-config. sudo raspi-config 2. choose Advancd Options\uff1a 3. choose Expand Filesystem\uff1a 4. Ok: 5. Execute the command resize2fs /dev/mmcblk0p2 in the terminal to see that the SD card has been successfully expanded.","title":"Method 1: Use raspi-config tool"},{"location":"Expand_Filesystem/#method-2-use-gparted-tool","text":"1. Connect the SD card or EMMc that has burned the image to the computer through USB. Take the GParted partition tool under Linux as an example. Other platforms also have similar partition tools. Open GParted software and select SD card: 2. By observing the partition of the SD card in the above figure, we can find that 2.01GB and 21.87GB of space are unused before and after the sdb3 partition, which is the space we want to expand. Select the sdb3 partition and click Resize. 3. You can drag the white partition of sdb3 to the leftmost and rightmost, or fill in 25958 with \"Previous Free Space\" as \"0\" and \"New Size\" as \"Maximum Size\", and then click Resize in the lower right corner. Then click OK to see that all unused space of sd has been used. 4. Insert the SD card into the device and start it.","title":"Method 2: Use GParted tool"},{"location":"Expand_Filesystem/#method-3-use-script","text":"If you are using a BliKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand. sh on any path, and write the following content to expand.sh #!/bin/bash set -x resize_mmcblk0p3() { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100% resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" If you are using a PiKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand. sh on any path, and write the following content to expand.sh #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab; then part=$(grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}') # shellcheck disable=SC2206 splitted=(${part//=/ }) if [ \"${splitted[0]}\" == LABEL ]; then label=${splitted[1]} part=$(blkid -c /dev/null -L \"$label\") else label=PIMSD fi unset splitted disk=/dev/$(lsblk -no pkname \"$part\") npart=$(cat \"/sys/class/block/${part//\\/dev\\//}/partition\") umount \"$part\" parted \"$disk\" -a optimal -s resizepart \"$npart\" 100% yes | mkfs.ext4 -L \"$label\" -F -m 0 \"$part\" mount \"$part\" unset disk part npart label fi 2. Execute 'bash expand. sh' on the terminal and wait for the execution to complete.","title":"Method 3: Use script"},{"location":"OLED-display/","text":"OLED display Follow the method below to enable OLED. If you use PiKVM official image, log in to PiKVM and run these commands: # rw # systemctl enable --now kvmd-oled //Enable OLED # ro If the oled still can't work, you need to check whether there has \"dtparam=i2c_arm=on\" in \"/boot/config.txt\" file, and whether there has \"i2c-dev\" in \"/etc/modules-load.d/i2c.conf\" file. If not, please create and add them. If it still does not work after the above configuration, please burn the image provided by blikvm for testing to check whether the OLED hardware is damaged. BLIKVM CM4 version OLED display The product comes standard with a monochrome OLED display with a resolution of 128x64, and the chip is SSD1306. The user connects the display to the product with the wiring of the display. The module is connected to CM4 through the I^2^C interface. The wiring definition is shown in the following table. This is a library for the monochrome OLEDs based on SSD1306 drivers. Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C)","title":"OLED Display"},{"location":"OLED-display/#oled-display","text":"Follow the method below to enable OLED. If you use PiKVM official image, log in to PiKVM and run these commands: # rw # systemctl enable --now kvmd-oled //Enable OLED # ro If the oled still can't work, you need to check whether there has \"dtparam=i2c_arm=on\" in \"/boot/config.txt\" file, and whether there has \"i2c-dev\" in \"/etc/modules-load.d/i2c.conf\" file. If not, please create and add them. If it still does not work after the above configuration, please burn the image provided by blikvm for testing to check whether the OLED hardware is damaged. BLIKVM CM4 version OLED display The product comes standard with a monochrome OLED display with a resolution of 128x64, and the chip is SSD1306. The user connects the display to the product with the wiring of the display. The module is connected to CM4 through the I^2^C interface. The wiring definition is shown in the following table. This is a library for the monochrome OLEDs based on SSD1306 drivers. Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C)","title":"OLED display"},{"location":"atx-guide/","text":"ATXA guide 1. Introduction ATXA is an ATX adapter borad to manage the power of your computer. The product includes two modules A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable.Join to the Discord Community Chat for news, questions and support! ATXA_A ATXA_B 2. A-board A-board is connected to the Raspberry Pi. The following table is a typical connection method in PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed 3. B-board The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B Instructions for connecting to the computer motherboard According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the ATXA-B motherboard. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and ATXA-B. See the following figure for the connection relationship\uff1a 4.Mechanical Diagram 5.Test video youtube\uff1a ATX 6.More link Purchase\uff1a ATX","title":"ATX Guide"},{"location":"atx-guide/#atxa-guide","text":"","title":"ATXA guide"},{"location":"atx-guide/#1-introduction","text":"ATXA is an ATX adapter borad to manage the power of your computer. The product includes two modules A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable.Join to the Discord Community Chat for news, questions and support! ATXA_A ATXA_B","title":"1. Introduction"},{"location":"atx-guide/#2-a-board","text":"A-board is connected to the Raspberry Pi. The following table is a typical connection method in PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed","title":"2. A-board"},{"location":"atx-guide/#3-b-board","text":"The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B Instructions for connecting to the computer motherboard According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the ATXA-B motherboard. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and ATXA-B. See the following figure for the connection relationship\uff1a","title":"3. B-board"},{"location":"atx-guide/#4mechanical-diagram","text":"","title":"4.Mechanical Diagram"},{"location":"atx-guide/#5test-video","text":"youtube\uff1a ATX","title":"5.Test video"},{"location":"atx-guide/#6more-link","text":"Purchase\uff1a ATX","title":"6.More link"},{"location":"atx/","text":"ATX Control Board To manage the power of your computer, you need to install an ATX control board inside the chassis and connect it to the motherboard (to enable KVM control of power on/off via the ATX switch). There is a female-to-female cable that connects from the motherboard to the ATX control board and a male-to-female cable that connects from the ATX control board to the front panel (to keep the power on/off button on the chassis functional). The interface on the ATX control board has two ports (TO CASE, TO MB), and both ports have the same functionality, so they can be used interchangeably. ATX compatibility Laptops are not compatible with ATX as they lack the required ATX pins. This method is only applicable to PC servers and desktops. Detailed Instructions 1. Connect the two cables to the ATX control board. To secure the ATX control board inside the chassis, you can choose to mount it on a bracket attached to a PCIe slot. Example 2. Locate the motherboard pins responsible for connecting the front panel buttons and LEDs and disconnect them. Usually, the cables and connectors on the motherboard are labeled. If you're unsure, you can refer to your motherboard's documentation. Example 3. Connect the DuPont male connector from the front panel to the DuPont female connector on the ATX cable, following the pin definitions and paying attention to the labels and polarity (+ or -). Example 4. Using the same method, connect the female pins from the ATX board to the corresponding connector on the motherboard. Refer to your motherboard's documentation to determine which pins on the motherboard connect to which pins on the ATX control board. Sometimes, this information is printed on the motherboard. Example 5. Install the ATX board into a PCI slot on the chassis and secure it with screws or use alternative mounting methods according to your preference. Example 6. Arrange the cables neatly and secure them as needed. Make sure the cables do not come into contact with any fans inside the chassis. Use an Ethernet cable to connect the ATX board to the ATX interface of the BliKVM. With this, the hardware connection of the ATX control board is complete.","title":"ATX Control Board"},{"location":"atx/#atx-control-board","text":"To manage the power of your computer, you need to install an ATX control board inside the chassis and connect it to the motherboard (to enable KVM control of power on/off via the ATX switch). There is a female-to-female cable that connects from the motherboard to the ATX control board and a male-to-female cable that connects from the ATX control board to the front panel (to keep the power on/off button on the chassis functional). The interface on the ATX control board has two ports (TO CASE, TO MB), and both ports have the same functionality, so they can be used interchangeably. ATX compatibility Laptops are not compatible with ATX as they lack the required ATX pins. This method is only applicable to PC servers and desktops.","title":"ATX Control Board"},{"location":"atx/#detailed-instructions","text":"1. Connect the two cables to the ATX control board. To secure the ATX control board inside the chassis, you can choose to mount it on a bracket attached to a PCIe slot. Example 2. Locate the motherboard pins responsible for connecting the front panel buttons and LEDs and disconnect them. Usually, the cables and connectors on the motherboard are labeled. If you're unsure, you can refer to your motherboard's documentation. Example 3. Connect the DuPont male connector from the front panel to the DuPont female connector on the ATX cable, following the pin definitions and paying attention to the labels and polarity (+ or -). Example 4. Using the same method, connect the female pins from the ATX board to the corresponding connector on the motherboard. Refer to your motherboard's documentation to determine which pins on the motherboard connect to which pins on the ATX control board. Sometimes, this information is printed on the motherboard. Example 5. Install the ATX board into a PCI slot on the chassis and secure it with screws or use alternative mounting methods according to your preference. Example 6. Arrange the cables neatly and secure them as needed. Make sure the cables do not come into contact with any fans inside the chassis. Use an Ethernet cable to connect the ATX board to the ATX interface of the BliKVM. With this, the hardware connection of the ATX control board is complete.","title":"Detailed Instructions"},{"location":"edid/","text":"EDID The EDID file in BliKVM serves the purpose of informing the controlled computer about the expected HDMI output resolution. For example, if the EDID is set to 1080P60Hz, and the controlled computer supports this resolution, it will output at 1080P60Hz. Additionally, EDID can be used to disable audio, modify the display model, name, manufacturer, and other information. In most cases, you don't need to change it, but sometimes, especially with strange UEFI/BIOS behavior, it may be necessary. Note BliKVM v1, v2, and v3 use the CSI video capture scheme, which supports EDID settings. However, BliKVM v4 uses the USB video capture scheme, which does not support EDID settings. For v3 HAT, there is a limitation of two CSI channels on the Raspberry Pi 4B, which means it can only capture video input with a maximum resolution of 1080P50Hz. Therefore, if you set 1080P60Hz EDID for v3, it will not be able to capture the image. If you are using PiKVM OS, you can refer to this link for modification instructions. If you are using BliKVM OS, the EDID file is located at /usr/bin/blikvm/edid.txt . Open this file, and replace the EDID contents with the desired resolution's EDID. EDID Examples for 1080P60Hz The following EDID is suitable for v1 and v2 hardware. 1920x1080 60Hz, with audio 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C EDID Examples for 1080P50Hz The following EDID is suitable for v1, v2, and v3 hardware, especially when you want v3 HAT to capture 1080P resolution. 1920x1080 50Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028 EDID Examples for 720P60Hz The following EDID is suitable for v1, v2, and v3 hardware. 1280x720 60Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 Custom EDID To customize the EDID, it is best to use third-party utilities, such as the recommended advanced AW EDID Editor (works well in Windows and can be used in wine) or wxEDID . Both editors work with the binary EDID format. Using these tools, you can modify the EDID information like editing a file, similar to changing the information on an identity card. By editing the EDID, you can adjust the parameters and characteristics of the display to suit different usage requirements, and thus achieve better display performance.","title":"HDMI EDID"},{"location":"edid/#edid","text":"The EDID file in BliKVM serves the purpose of informing the controlled computer about the expected HDMI output resolution. For example, if the EDID is set to 1080P60Hz, and the controlled computer supports this resolution, it will output at 1080P60Hz. Additionally, EDID can be used to disable audio, modify the display model, name, manufacturer, and other information. In most cases, you don't need to change it, but sometimes, especially with strange UEFI/BIOS behavior, it may be necessary. Note BliKVM v1, v2, and v3 use the CSI video capture scheme, which supports EDID settings. However, BliKVM v4 uses the USB video capture scheme, which does not support EDID settings. For v3 HAT, there is a limitation of two CSI channels on the Raspberry Pi 4B, which means it can only capture video input with a maximum resolution of 1080P50Hz. Therefore, if you set 1080P60Hz EDID for v3, it will not be able to capture the image. If you are using PiKVM OS, you can refer to this link for modification instructions. If you are using BliKVM OS, the EDID file is located at /usr/bin/blikvm/edid.txt . Open this file, and replace the EDID contents with the desired resolution's EDID.","title":"EDID"},{"location":"edid/#edid-examples-for-1080p60hz","text":"The following EDID is suitable for v1 and v2 hardware. 1920x1080 60Hz, with audio 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C","title":"EDID Examples for 1080P60Hz"},{"location":"edid/#edid-examples-for-1080p50hz","text":"The following EDID is suitable for v1, v2, and v3 hardware, especially when you want v3 HAT to capture 1080P resolution. 1920x1080 50Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028","title":"EDID Examples for 1080P50Hz"},{"location":"edid/#edid-examples-for-720p60hz","text":"The following EDID is suitable for v1, v2, and v3 hardware. 1280x720 60Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000","title":"EDID Examples for 720P60Hz"},{"location":"edid/#custom-edid","text":"To customize the EDID, it is best to use third-party utilities, such as the recommended advanced AW EDID Editor (works well in Windows and can be used in wine) or wxEDID . Both editors work with the binary EDID format. Using these tools, you can modify the EDID information like editing a file, similar to changing the information on an identity card. By editing the EDID, you can adjust the parameters and characteristics of the display to suit different usage requirements, and thus achieve better display performance.","title":"Custom EDID"},{"location":"faq/","text":"FAQ & Troubleshooting As a first step, we recommend carefully reading our documentation. Most steps to successfully set up your BLIKVM are already described there. If you run into any issues you can check this page which will list common errors. If that still doesn't help you you're welcome to raise an issue ticket or join our Discord for further help. Common questions Can I connect multiple servers to a single BLIKVM? Yes, but it requires additional work to set up. See this page . How can I get the access to PiKVM in my local network over Internet? If your router has an external IP address, you can use port forwarding to forward port 80 (Web), port 8008 (mjpeg), and port 8188 (webrtc) In all other cases, you can use the excellent free VPN service Tailscale. Which BLiKVM hardware version should I choose, such as BLiKVM V1 CM4, BLiKVM V2 PCIe, and BLiKVM V3 Hat? First, please refer to this page for a comparison of the main parameters of each version. V1 and V3 are external solutions, while V2 is an internal chassis solution. If you have a chassis and there is space inside, choosing the V2 PCIe version would be a better option. So how do you choose between the external solutions V1 and V3? V1 is based on the CM4 platform, with higher integration and ready-to-use versions available. V3 is based on the Raspberry Pi 4B platform, with all IO ports exposed and greater expandability. Another key difference is that V1 supports up to 1080P60Hz input, while V3 supports up to 1080P50Hz input. Of course, you also need to consider whether you already have a CM4 or 4B, as purchasing the corresponding baseboard would offer better cost-effectiveness. Can I use BLIKVM for gaming? No, because: For HDMI-CSI bridge, bus bandwidth is not enough to transmit more than 1080p60. For HDMI-USB dongle, high latency and low video quality. General hardware video capture differs from software streaming and introduces additional latency. Can BLIKVM do 4K video? For HDMI-CSI bridge, no. There is not enough bandwidth in the CSI bus for that much data. 1080p60 will max out the bandwidth. For the USB capture devices: technically yes, they will downsample to something smaller to meet the USB 2.0 bandwidth limitations, so the source may be 4k, but the stream will not. The 4K real-time video will not fit through the network anyway. Where does the cursor/video latency come from? Here is the chain of transferring an image to your browser or VNC client. Capture device -> Compression -> Network -> Decompression -> Rendering 100-200ms is very, very fast for this. But we are working to speed things up even more. Does BLIKVM support sound? BliKVM v1 CM4, v2 PCIe, v3 HAT version supported\uff0c v4 Allwinner not support now. Can I power the Pi via PoE? Yes! Hat and PCIe version supported. First steps What is the default password? How do I change it? If you use PiKVM, there are two types of accounts: OS and PiKVM (web interface) accounts. The system account root can be used for SSH/UART access and has the password root . The web interface account is called admin and has the password admin . The PiKVM account cannot be used for SSH access and vice versa. To change passwords, use the following commands (under root): su - # If you're in the webterm rw # Switch filesystem to read-write mode passwd root # Change OS root password kvmd-htpasswd set admin # Change web ui admin password ro # Back to read-only How do I add another user? If you use PiKVM software, as stated above you need to make 2 accounts, 1 for the shell, the other for the PiKVM Web UI. If you require additional users for PiKVM UI, you can use the following: # rw # su - # kvmd-htpasswd set <user> # Adds a new user # kvmd-htpasswd set <user> # Sets the password as long as the user exists # kvmd-htpasswd del <user> # Removes/deletes a user To add a shell/terminal account: # rw # su - # adduser <user> # passwd <user> Keep in mind that the more users that are added, the stream if accessed, fps will drop. Video problems BLIKVM does not show the video from the computer at all Double-check that the video capture device is connected correctly. For the CSI bridge, this should be exactly the camera port. Some laptops do not output any signal until you switch the output (usually via the FN + and an F5 key on the keyboard). Your computer may have turned on sleep mode for the monitor. Move the mouse to turn it off. For windows you might need to check for the active signal resolution. To change the active signal resolution you have to go to Settings>System>Display>Advanced display settings>Display adapter properties then, click \"List All Models\" and choose the one you want. Keep trying different Hz settings. The video works in the booted OS, but not in the BIOS/UEFI This problem appears on Intel NUC, GA-H77-DS3H, and some other devices when using a CSI bridge. All you need to do is change the EDID data. This is the information about supported resolutions that the CSI bridge reports to your computer. Glitchy or wrong BIOS/UEFI resolution On some motherboards, the BIOS may be displayed at a lower resolution, or with some rendering issues/glitches, specially on newer ASUS ones. Like this: This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. If you can't or don't want to enable the CSM, you can try connecting a DisplayPort (DP) monitor, or a dummy plug . If you remove the DP cable/adapter the bug will reappear. If none of this works, try connecting the DP cable first, boot into the BIOS, disable the CSM and shutdown (do not restart) your PC. Then, boot into the BIOS and enable the CSM before shutting down your PC. Then connect the HDMI and turn your PC on again. There is no video in GRUB2, but there is before and after Sometimes this can be caused by the specifics of the BIOS/UEFI and how GRUB2 works with video. This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. The video mode will be located in the same section. Switch the Video mode from UEFI to Legacy . No image from computer with Linux + Awesome WM Sometimes Awesome WM on Linux can't recognize a video output change on a cable. That is, if the cable was first inserted into the monitor, and then you reconnected it to BLIKVM - it may happen that you will not see the image. It seems that the problem is Awesome WM, since for example with KDE, it is not reproducable. If you turn on your workstation with BLIKVM already connected, everything will work fine. USB problems (keyboard, mouse, mass storage, etc) What speed is the USB OTG port? Per the official RPI documentation, this is a limitation of the SoC. The OTG port is only USB2.0, so is limited to 455 Mbit/s. Why can't some keyboard shortcuts of physical keyboards be captured while virtual keyboards can? For example, the F11 key on a Mac computer cannot be captured. This is because some shortcuts are already in use by the system, such as in macOS, where F11 is assigned to the \"Show Desktop\" function by default. When you press F11 in a web interface, the KeyboardEvent is first captured by the system, and if a callback is registered in the system, the event will not be passed to the application. To solve this issue, you can disable the system's assigned shortcut or use a virtual keyboard. Hardware problems (Wi-Fi, ATX, etc) If you use PiKVM software, the web UI show FAN error! Because the fan model used by BLIKVM hardware is different from that of PIKVM hardware, viewing the fan status through the web interface may fail in the latest system of pikvm. However, this will not affect the normal operation of BLIKVM fan. Therefore, when using the PIKVM image, as long as you ensure that the install script displays OK, it means that the update of the kvmd fan program is successful. The threshold temperature set by the default program is 60 degrees Celsius. When the CPU temperature is detected to exceed 60 degrees Celsius, the fan will start rotating at 85% speed. If you want to modify the threshold temperature and speed, you can modify the kvmd-fan.py script, and then re-execute install.sh. I can't connect to Wi-Fi at all! If your device is unable to connect to the Wi-Fi network that you have set up, check the 2.4 GHz Wi-Fi channel used by your Wi-Fi access point. If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. BLIKVM complains about low power warnings Are you using a \"proper\" power supply? Not one you hacked together? Some USB power bricks advertise 5V 2.1A or higher, but can't deliver consistent 5V. Best to use Raspberry Pi Foundation recommended power supplies. It should be 5.1v and 3A DC output. When I use the PoE, do I still need to use the power OTG splitter to prevent back power on the machine usb? Only HAT version you need to use power OTG splitter to prevent back power. Generally, most hosts computer are protected back power, you do not need to usr power OTG splitter in this case. BLIKVM-CM4-V2.2 and BLIKVM-PCIe version don't need. In some board like BLIKVM-PCIe or BLIKVM-CM4-V2.2 has boot pin, how do I connect? If you short them, CM4 will not start normally, but will enter the burning image mode. If your hardware version of boot has only two pins, use the jumper cap to connect the two pins as a short circuit. If you do not use the jumper cap or plug it into one pin, CM4 will start normally. If you use three boot pins of the hardware version, use the jumper cap to connect GND and another non-GND pin to indicate short circuit, and plug the jumper cap on the two GND pins or do not use it, CM4 will start normally. Web problems What ports does BliKVM OS occupy, and how should it be forwarded when using a public server? The web interface uses the HTTP protocol and occupies port 80. If you are using hardware versions V1, V2, or V3 with web-rtc transmission, the port is 8188. If you are using hardware version V4 with MJPEG transmission, the port is 8008. Please note that the ports cannot be modified; only port forwarding can be configured. Raspberry problem Can I use both the CM4 version with EMMC and the SD card at the same time? No, you can't, When designing the CM4 hardware, several pins of the SD card are only valid in the lite version. You can find instructions on the official website of Raspberry Pi.","title":"FAQ"},{"location":"faq/#faq-troubleshooting","text":"As a first step, we recommend carefully reading our documentation. Most steps to successfully set up your BLIKVM are already described there. If you run into any issues you can check this page which will list common errors. If that still doesn't help you you're welcome to raise an issue ticket or join our Discord for further help.","title":"FAQ &amp; Troubleshooting"},{"location":"faq/#common-questions","text":"Can I connect multiple servers to a single BLIKVM? Yes, but it requires additional work to set up. See this page . How can I get the access to PiKVM in my local network over Internet? If your router has an external IP address, you can use port forwarding to forward port 80 (Web), port 8008 (mjpeg), and port 8188 (webrtc) In all other cases, you can use the excellent free VPN service Tailscale. Which BLiKVM hardware version should I choose, such as BLiKVM V1 CM4, BLiKVM V2 PCIe, and BLiKVM V3 Hat? First, please refer to this page for a comparison of the main parameters of each version. V1 and V3 are external solutions, while V2 is an internal chassis solution. If you have a chassis and there is space inside, choosing the V2 PCIe version would be a better option. So how do you choose between the external solutions V1 and V3? V1 is based on the CM4 platform, with higher integration and ready-to-use versions available. V3 is based on the Raspberry Pi 4B platform, with all IO ports exposed and greater expandability. Another key difference is that V1 supports up to 1080P60Hz input, while V3 supports up to 1080P50Hz input. Of course, you also need to consider whether you already have a CM4 or 4B, as purchasing the corresponding baseboard would offer better cost-effectiveness. Can I use BLIKVM for gaming? No, because: For HDMI-CSI bridge, bus bandwidth is not enough to transmit more than 1080p60. For HDMI-USB dongle, high latency and low video quality. General hardware video capture differs from software streaming and introduces additional latency. Can BLIKVM do 4K video? For HDMI-CSI bridge, no. There is not enough bandwidth in the CSI bus for that much data. 1080p60 will max out the bandwidth. For the USB capture devices: technically yes, they will downsample to something smaller to meet the USB 2.0 bandwidth limitations, so the source may be 4k, but the stream will not. The 4K real-time video will not fit through the network anyway. Where does the cursor/video latency come from? Here is the chain of transferring an image to your browser or VNC client. Capture device -> Compression -> Network -> Decompression -> Rendering 100-200ms is very, very fast for this. But we are working to speed things up even more. Does BLIKVM support sound? BliKVM v1 CM4, v2 PCIe, v3 HAT version supported\uff0c v4 Allwinner not support now. Can I power the Pi via PoE? Yes! Hat and PCIe version supported.","title":"Common questions"},{"location":"faq/#first-steps","text":"What is the default password? How do I change it? If you use PiKVM, there are two types of accounts: OS and PiKVM (web interface) accounts. The system account root can be used for SSH/UART access and has the password root . The web interface account is called admin and has the password admin . The PiKVM account cannot be used for SSH access and vice versa. To change passwords, use the following commands (under root): su - # If you're in the webterm rw # Switch filesystem to read-write mode passwd root # Change OS root password kvmd-htpasswd set admin # Change web ui admin password ro # Back to read-only How do I add another user? If you use PiKVM software, as stated above you need to make 2 accounts, 1 for the shell, the other for the PiKVM Web UI. If you require additional users for PiKVM UI, you can use the following: # rw # su - # kvmd-htpasswd set <user> # Adds a new user # kvmd-htpasswd set <user> # Sets the password as long as the user exists # kvmd-htpasswd del <user> # Removes/deletes a user To add a shell/terminal account: # rw # su - # adduser <user> # passwd <user> Keep in mind that the more users that are added, the stream if accessed, fps will drop.","title":"First steps"},{"location":"faq/#video-problems","text":"BLIKVM does not show the video from the computer at all Double-check that the video capture device is connected correctly. For the CSI bridge, this should be exactly the camera port. Some laptops do not output any signal until you switch the output (usually via the FN + and an F5 key on the keyboard). Your computer may have turned on sleep mode for the monitor. Move the mouse to turn it off. For windows you might need to check for the active signal resolution. To change the active signal resolution you have to go to Settings>System>Display>Advanced display settings>Display adapter properties then, click \"List All Models\" and choose the one you want. Keep trying different Hz settings. The video works in the booted OS, but not in the BIOS/UEFI This problem appears on Intel NUC, GA-H77-DS3H, and some other devices when using a CSI bridge. All you need to do is change the EDID data. This is the information about supported resolutions that the CSI bridge reports to your computer. Glitchy or wrong BIOS/UEFI resolution On some motherboards, the BIOS may be displayed at a lower resolution, or with some rendering issues/glitches, specially on newer ASUS ones. Like this: This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. If you can't or don't want to enable the CSM, you can try connecting a DisplayPort (DP) monitor, or a dummy plug . If you remove the DP cable/adapter the bug will reappear. If none of this works, try connecting the DP cable first, boot into the BIOS, disable the CSM and shutdown (do not restart) your PC. Then, boot into the BIOS and enable the CSM before shutting down your PC. Then connect the HDMI and turn your PC on again. There is no video in GRUB2, but there is before and after Sometimes this can be caused by the specifics of the BIOS/UEFI and how GRUB2 works with video. This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. The video mode will be located in the same section. Switch the Video mode from UEFI to Legacy . No image from computer with Linux + Awesome WM Sometimes Awesome WM on Linux can't recognize a video output change on a cable. That is, if the cable was first inserted into the monitor, and then you reconnected it to BLIKVM - it may happen that you will not see the image. It seems that the problem is Awesome WM, since for example with KDE, it is not reproducable. If you turn on your workstation with BLIKVM already connected, everything will work fine.","title":"Video problems"},{"location":"faq/#usb-problems-keyboard-mouse-mass-storage-etc","text":"What speed is the USB OTG port? Per the official RPI documentation, this is a limitation of the SoC. The OTG port is only USB2.0, so is limited to 455 Mbit/s. Why can't some keyboard shortcuts of physical keyboards be captured while virtual keyboards can? For example, the F11 key on a Mac computer cannot be captured. This is because some shortcuts are already in use by the system, such as in macOS, where F11 is assigned to the \"Show Desktop\" function by default. When you press F11 in a web interface, the KeyboardEvent is first captured by the system, and if a callback is registered in the system, the event will not be passed to the application. To solve this issue, you can disable the system's assigned shortcut or use a virtual keyboard.","title":"USB problems (keyboard, mouse, mass storage, etc)"},{"location":"faq/#hardware-problems-wi-fi-atx-etc","text":"If you use PiKVM software, the web UI show FAN error! Because the fan model used by BLIKVM hardware is different from that of PIKVM hardware, viewing the fan status through the web interface may fail in the latest system of pikvm. However, this will not affect the normal operation of BLIKVM fan. Therefore, when using the PIKVM image, as long as you ensure that the install script displays OK, it means that the update of the kvmd fan program is successful. The threshold temperature set by the default program is 60 degrees Celsius. When the CPU temperature is detected to exceed 60 degrees Celsius, the fan will start rotating at 85% speed. If you want to modify the threshold temperature and speed, you can modify the kvmd-fan.py script, and then re-execute install.sh. I can't connect to Wi-Fi at all! If your device is unable to connect to the Wi-Fi network that you have set up, check the 2.4 GHz Wi-Fi channel used by your Wi-Fi access point. If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. BLIKVM complains about low power warnings Are you using a \"proper\" power supply? Not one you hacked together? Some USB power bricks advertise 5V 2.1A or higher, but can't deliver consistent 5V. Best to use Raspberry Pi Foundation recommended power supplies. It should be 5.1v and 3A DC output. When I use the PoE, do I still need to use the power OTG splitter to prevent back power on the machine usb? Only HAT version you need to use power OTG splitter to prevent back power. Generally, most hosts computer are protected back power, you do not need to usr power OTG splitter in this case. BLIKVM-CM4-V2.2 and BLIKVM-PCIe version don't need. In some board like BLIKVM-PCIe or BLIKVM-CM4-V2.2 has boot pin, how do I connect? If you short them, CM4 will not start normally, but will enter the burning image mode. If your hardware version of boot has only two pins, use the jumper cap to connect the two pins as a short circuit. If you do not use the jumper cap or plug it into one pin, CM4 will start normally. If you use three boot pins of the hardware version, use the jumper cap to connect GND and another non-GND pin to indicate short circuit, and plug the jumper cap on the two GND pins or do not use it, CM4 will start normally.","title":"Hardware problems (Wi-Fi, ATX, etc)"},{"location":"faq/#web-problems","text":"What ports does BliKVM OS occupy, and how should it be forwarded when using a public server? The web interface uses the HTTP protocol and occupies port 80. If you are using hardware versions V1, V2, or V3 with web-rtc transmission, the port is 8188. If you are using hardware version V4 with MJPEG transmission, the port is 8008. Please note that the ports cannot be modified; only port forwarding can be configured.","title":"Web problems"},{"location":"faq/#raspberry-problem","text":"Can I use both the CM4 version with EMMC and the SD card at the same time? No, you can't, When designing the CM4 hardware, several pins of the SD card are only valid in the lite version. You can find instructions on the official website of Raspberry Pi.","title":"Raspberry problem"},{"location":"first_steps/","text":"First steps First power on Power up the device. Do not turn off the device until it's fully booted for the first time After turning on the power, BLIKVM OS will perform the necessary operations on the memory card. Getting access to BLIKVM By default, BliKVM receives a dynamic IP address via DHCP. The IP address will be displayed on the BliKVM monitor. If you are using DIY hardware without a monitor, use the following tips: Finding BliKVM in the network You can determine the IP address of BliKVM using the following methods: Common Method: Access the web interface of your router and look for the allocated IP address list. The specific method depends on the router model. Linux Only: Use the command arp-scan --localnet . Linux, macOS, Windows: Download and run Angry IP Scanner . Windows PowerShell: Use the command arp -a . In the example below, let's assume your BliKVM has obtained the address 192.168.0.100 , and you have successfully found that address using the instructions above. Accessing BliKVM Web Interface In most networks, you can access BliKVM in any browser using the following URL: http://192.168.0.100/ . Google Chrome (Chromium), Firefox, and Safari work best with no extensions enabled. If one works and the other does not, it may be an issue with the browser or extensions. It is recommended to use a private browsing window or incognito mode. Internet Explorer and early versions of Microsoft Edge (non-Chromium version) are not supported. The default username is admin , and the password is also admin . Once logged in, you will have access to the main menu with essential functions. You can change system settings and passwords using the web interface's account management feature. Note about accessing BliKVM web via http, not https Accessing BliKVM via SSH SSH is the most common method for remote access in the Linux world. You can access BliKVM via SSH. This method is used for managing the device: Linux, macOS: Open any terminal application and run: ssh blikvm@192.168.0.100 . Windows: Use PuTTY for the operation. The default blikvm user password is blikvm . You can use sudo -i to obtain root privileges. Optional: Updating BliKVM Software This section is not mandatory and should only be performed if you are next to the BliKVM for recovery purposes. Refer to the Software Update Guide for instructions. Note on BliKVM OS Terminal Usage Some configuration changes must be made under the root user (i.e., administrator). Obtaining Root Privileges If you are logged in via SSH, use sudo -i to obtain root privileges. BliKVM storage cards in versions v1, v2, and v3 are mounted in read-only mode. This protects the file system from being corrupted in the event of a sudden power outage. To edit any files and make changes, you need to remount the file system in read-write mode. You can determine the current mode by checking if ro or rw is displayed in the terminal. Enabling Write Mode To enable write mode, run the command rw . To disable write mode, run the command ro . If you receive a \"Device is busy\" message, execute the reboot command. What's next? Set up internet access using Port Forwarding or Tailscale VPN . Explore BLIKVM features using the table of contents on the left. Join our Discord to contact the community and developers. Check out the GitHub - BLIKVM is a Open Source project! FAQ and Troubleshooting If you have any questions or run into problems, take a look at the FAQ . Seriously, it's really useful! We've probably already found a solution for it :) For any other help and support, you can contact us via the Discord chat .","title":"First Steps"},{"location":"first_steps/#first-steps","text":"","title":"First steps"},{"location":"first_steps/#first-power-on","text":"Power up the device. Do not turn off the device until it's fully booted for the first time After turning on the power, BLIKVM OS will perform the necessary operations on the memory card.","title":"First power on"},{"location":"first_steps/#getting-access-to-blikvm","text":"By default, BliKVM receives a dynamic IP address via DHCP. The IP address will be displayed on the BliKVM monitor. If you are using DIY hardware without a monitor, use the following tips: Finding BliKVM in the network You can determine the IP address of BliKVM using the following methods: Common Method: Access the web interface of your router and look for the allocated IP address list. The specific method depends on the router model. Linux Only: Use the command arp-scan --localnet . Linux, macOS, Windows: Download and run Angry IP Scanner . Windows PowerShell: Use the command arp -a . In the example below, let's assume your BliKVM has obtained the address 192.168.0.100 , and you have successfully found that address using the instructions above. Accessing BliKVM Web Interface In most networks, you can access BliKVM in any browser using the following URL: http://192.168.0.100/ . Google Chrome (Chromium), Firefox, and Safari work best with no extensions enabled. If one works and the other does not, it may be an issue with the browser or extensions. It is recommended to use a private browsing window or incognito mode. Internet Explorer and early versions of Microsoft Edge (non-Chromium version) are not supported. The default username is admin , and the password is also admin . Once logged in, you will have access to the main menu with essential functions. You can change system settings and passwords using the web interface's account management feature. Note about accessing BliKVM web via http, not https Accessing BliKVM via SSH SSH is the most common method for remote access in the Linux world. You can access BliKVM via SSH. This method is used for managing the device: Linux, macOS: Open any terminal application and run: ssh blikvm@192.168.0.100 . Windows: Use PuTTY for the operation. The default blikvm user password is blikvm . You can use sudo -i to obtain root privileges. Optional: Updating BliKVM Software This section is not mandatory and should only be performed if you are next to the BliKVM for recovery purposes. Refer to the Software Update Guide for instructions.","title":"Getting access to BLIKVM"},{"location":"first_steps/#note-on-blikvm-os-terminal-usage","text":"Some configuration changes must be made under the root user (i.e., administrator). Obtaining Root Privileges If you are logged in via SSH, use sudo -i to obtain root privileges. BliKVM storage cards in versions v1, v2, and v3 are mounted in read-only mode. This protects the file system from being corrupted in the event of a sudden power outage. To edit any files and make changes, you need to remount the file system in read-write mode. You can determine the current mode by checking if ro or rw is displayed in the terminal. Enabling Write Mode To enable write mode, run the command rw . To disable write mode, run the command ro . If you receive a \"Device is busy\" message, execute the reboot command.","title":"Note on BliKVM OS Terminal Usage"},{"location":"first_steps/#whats-next","text":"Set up internet access using Port Forwarding or Tailscale VPN . Explore BLIKVM features using the table of contents on the left. Join our Discord to contact the community and developers. Check out the GitHub - BLIKVM is a Open Source project!","title":"What's next?"},{"location":"first_steps/#faq-and-troubleshooting","text":"If you have any questions or run into problems, take a look at the FAQ . Seriously, it's really useful! We've probably already found a solution for it :) For any other help and support, you can contact us via the Discord chat .","title":"FAQ and Troubleshooting"},{"location":"flashing_os/","text":"Flasing the OS image Micro-SD Card Requirements Minimum 16 Gb Class 10 is strongly recommended Why are there two versions of software, BLIKVM and PiKVM? What is the difference between the two versions? Which one should I choose? Can I use the official image of PiKVM? At the beginning of the BLIKVM project, the hardware was developed, and the software directly used PiKVM. With the continuous progress of the project, BLIKVM has developed its own software version of new architecture, which also lays the foundation for deeper cooperation with its own hardware; The core functions of BLIKVM and PiKVM are the same for users. Some subdivision functions are not the same. For example, BLIKVM supports multiple languages; Select according to your own use experience; You can use the PiKVM official image, but you need to make some adaptations according to the different hardware, mainly involving screens, fans, etc. Since the PiKVM official image is always updated, the specific adaptations need to be seen according to the specific situation you encounter at that time; Download the image BLIKVM software You can find BliKVM v1 CM4, v2 PCIe, v3 HAT, v4 Allwinner BLIKVM software image, v1 v2 v3 use a same image. BLIKVM image The web UI style is as follows: Base on PiKVM software Raspberry 4B and CM4 board use different PiKVM software image. After entering the link, you can see the image named with each hardware version (HAT CM4 PCIe) PiKVM image Flash the image Tip Ignore request to format your sd card, this step is not nessessary. Choose the most suitable method for you. How to flash the eMMC on a Raspberry Pi Compute Module 4 Board Link First, use the jumper cap to short the boot pin. If you use BLIKVM CM4 version Then connect the data cable to the USB OTG interface. Power on blikvm and observe the act light, the green light is always on. If you use BLIKVM PCIe version Then connect the data cable to the USB-PC interface. Power on blikvm and observe the ACT and PWR LED isn't light. After initialize EMMC through the usbboot/rpiboot, the ACT and PWR LED light is always on. EMMC knowledge If you use raspberry pi computing modules such as CM3 or CM4 EMMC\uff0cyou can initialize EMMC through the usbboot. Note that the EMMC version cannot directly use the SD card to start the image. From this video you can learn how to flash image quickly. How to flash the eMMC on a Raspberry Pi Compute Module 4 video Taking Ubuntu system as an example: Linux usbboot If you use an Micro-SD Card, you don't need to care about that. # sudo apt-get install libusb-1.0-0-dev # git clone --depth=1 https://github.com/raspberrypi/usbboot # cd usbboot # make # sudo ./rpiboot If the content shown in the figure below appears, it indicates that EMMC initialization is successful. Using RPi Imager (Linux, MacOS and Windows) Download and install the latest version of RPi Imager . Run RPi Imager: Press CHOOSE OS and select Use custom image at bottom of the list: After clicking on this item, select the image file ( .img.xz ), then click CHOOSE STORAGE : Insert the memory card into the card reader. Choose the card reader from this list. Be careful and choose the right device: After choosing the memory card, press the WRITE button. Confirm the operation when you are asked about it: Wait for the process to finish. Get yourself a coffee or do some stretching :) Tip The process may hang at 99% for a long time, this is okay, just wait for it to complete 8.Remove the memory card after successful completion: Tip If an error occurs during flashing or booting PiKVM, repeat the process.","title":"Flashing OS"},{"location":"flashing_os/#flasing-the-os-image","text":"Micro-SD Card Requirements Minimum 16 Gb Class 10 is strongly recommended Why are there two versions of software, BLIKVM and PiKVM? What is the difference between the two versions? Which one should I choose? Can I use the official image of PiKVM? At the beginning of the BLIKVM project, the hardware was developed, and the software directly used PiKVM. With the continuous progress of the project, BLIKVM has developed its own software version of new architecture, which also lays the foundation for deeper cooperation with its own hardware; The core functions of BLIKVM and PiKVM are the same for users. Some subdivision functions are not the same. For example, BLIKVM supports multiple languages; Select according to your own use experience; You can use the PiKVM official image, but you need to make some adaptations according to the different hardware, mainly involving screens, fans, etc. Since the PiKVM official image is always updated, the specific adaptations need to be seen according to the specific situation you encounter at that time;","title":"Flasing the OS image"},{"location":"flashing_os/#download-the-image","text":"","title":"Download the image"},{"location":"flashing_os/#blikvm-software","text":"You can find BliKVM v1 CM4, v2 PCIe, v3 HAT, v4 Allwinner BLIKVM software image, v1 v2 v3 use a same image. BLIKVM image The web UI style is as follows:","title":"BLIKVM software"},{"location":"flashing_os/#base-on-pikvm-software","text":"Raspberry 4B and CM4 board use different PiKVM software image. After entering the link, you can see the image named with each hardware version (HAT CM4 PCIe) PiKVM image","title":"Base on PiKVM software"},{"location":"flashing_os/#flash-the-image","text":"Tip Ignore request to format your sd card, this step is not nessessary. Choose the most suitable method for you. How to flash the eMMC on a Raspberry Pi Compute Module 4","title":"Flash the image"},{"location":"flashing_os/#board-link","text":"First, use the jumper cap to short the boot pin. If you use BLIKVM CM4 version Then connect the data cable to the USB OTG interface. Power on blikvm and observe the act light, the green light is always on. If you use BLIKVM PCIe version Then connect the data cable to the USB-PC interface. Power on blikvm and observe the ACT and PWR LED isn't light. After initialize EMMC through the usbboot/rpiboot, the ACT and PWR LED light is always on. EMMC knowledge If you use raspberry pi computing modules such as CM3 or CM4 EMMC\uff0cyou can initialize EMMC through the usbboot. Note that the EMMC version cannot directly use the SD card to start the image. From this video you can learn how to flash image quickly. How to flash the eMMC on a Raspberry Pi Compute Module 4 video Taking Ubuntu system as an example:","title":"Board Link"},{"location":"flashing_os/#linux-usbboot","text":"If you use an Micro-SD Card, you don't need to care about that. # sudo apt-get install libusb-1.0-0-dev # git clone --depth=1 https://github.com/raspberrypi/usbboot # cd usbboot # make # sudo ./rpiboot If the content shown in the figure below appears, it indicates that EMMC initialization is successful.","title":"Linux usbboot"},{"location":"flashing_os/#using-rpi-imager-linux-macos-and-windows","text":"Download and install the latest version of RPi Imager . Run RPi Imager: Press CHOOSE OS and select Use custom image at bottom of the list: After clicking on this item, select the image file ( .img.xz ), then click CHOOSE STORAGE : Insert the memory card into the card reader. Choose the card reader from this list. Be careful and choose the right device: After choosing the memory card, press the WRITE button. Confirm the operation when you are asked about it: Wait for the process to finish. Get yourself a coffee or do some stretching :) Tip The process may hang at 99% for a long time, this is okay, just wait for it to complete 8.Remove the memory card after successful completion: Tip If an error occurs during flashing or booting PiKVM, repeat the process.","title":"Using RPi Imager (Linux, MacOS and Windows)"},{"location":"hdmi-csi-i2s/","text":"HDMI to CSI&I2S bridge guide Convert HDMI signal acquisition into CSI signal and I2S audio signal. Introduction This module takes the incoming HDMI signal and converts it into a separate CSI signal and I2S audio signal. HDMI input supports up to 1080P60Hz. It works well on raspberry pi, there are three versions of this module in history(C779\u3001C780\u3001C790). C790 is the latest version. C790 has mitigate HDMI backpowering,also has two csi channels and four csi channels at the same time. Features C790 hardware parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 4 CSI-2 channels & clock The CSI-2 interface, with 15 pin FPC seat, spacing 1.0 mm, is located on the front of the C790 module. The CSI-2 interface, with 22 pin FPC seat, spacing 0.5 mm, is located on the back of the C790 module. Size: 30 x 45 mm Install:4 x M2.5 Power supply:3.3V Weight: 10g Pi 4B only support 1080P50Hz, limited by the number of CSI-2 channels. CM4 support 1080P60HZ, So if you must use 1080P60Hz input, please use CM4 and C790 together. interface C790 has two csi output interface. In fornt of C790, the CSI-2 interface is 15 pin FPC seat, spacing 1.0 mm. In back of C790, the CSI-2 interface is 22 pin FPC seat, spacing 0.5 mm. size Install C790 on raspberry pi for reference C780 C780A hardware parameters HDMI input: supports up to 1080P50Hz on raspberry pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install:6 x M2.5 Power supply:3.3V Weight: 10g C780B hardware parameters HDMI input: supports up to 1080P60Hz on raspberry pi HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 4 CSI-2 channels & clock CSI-2 interface: 22 pin FPC seat, spacing 0.5 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install:6 x M2.5 Power supply:3.3V Weight: 10g interface The wiring of audio part is shown in Figure. size The size of C780 is shown in Figure. There are 6 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. As shown in Figure, the user can directly fix the module on the raspberry pi zero.C780 is designed to be broken, and the hole spacing before breaking can be perfectly installed with most series of raspberry pi. C779 hardware parameters HDMI input: supports up to 1080P50Hz on raspberry pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 35 x 50 mm Install:4 x M2.5 Power supply:3.3V Weight: 10g size The size of C779 is shown in Figure. There are 4 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. CSI Interface Definitions The CSI (Camera Serial Interface) interfaces C779 and C780A have 15 pins each, while the C780B interface has 22 pins. The C790 interface is unique as it supports both 15 and 22 PIN configurations. Software demo The use guide of C790/C780/C779 depends on the official Raspberry Pi OS version you are using. Different versions have different usage methods. If you have some questions, Join our BLIKVM Discord Community for Support, FAQ & News! To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If \u201cuname -a\u201d reports anything less, then fix this before proceeding. pi@raspberrypi:~ $ uname -a Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. Update & upgrade the raspberry pi system (It will take a long time depend on the different country) sudo apt-get update sudo apt-get upgrade 2. Enable camera module (the camera is enabled by default in Raspberry pi Bullseys OS) sudo raspi-config sudo reboot Navigate to \u2018Interfacing Options\u2019 and hit Enter. Now select the \u2018Camera\u2019 option, and hit the Enter key to enable it. Select \u201cFinish\u201d and select to reboot your Raspberry Pi. reboot is important!! 3. Edit /boot/config.txt (that will need sudo) sudo nano /boot/config.txt Add the line: dtoverlay=tc358743 Add the line if your shield support audio like C780 or C790. dtoverlay=tc358743-audio please append the If (and only if) you have a device such as the C780 or C790 that supports the 22pin connector with all 4 lanes wired out, and are using a Compute Module with the CAM1 connector that also has all 4 lanes wired up, you can use: dtoverlay=tc358743,4lane=1 !!! note \"4. Check the amount of memory assigned to the CMA heap with \u201cdmesg | grep cma\u201d. The first line should be along the lines of\" pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 If it reports less than 96MB assigned to CMA, then edit /boot/cmdline.txt and add to the start of the line. Do NOT add any carriage returns. cma=96M !!! note \"5. Reboot. If all is well you should get a /dev/video0 device, and \u201cv4l2-ctl \u2013list-devices\u201d will tell you that it is provided by Unicam. After connecting all the cables, power on the Raspberry Pi, the C790 indicator light is normally green, and after opening the Raspberry Pi terminal, enter the following command:\" pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 !!! note \"6. This driver puts all the control in the hands of the user, or the user\u2019s application. By default there is no EDID loaded into the chip to allow it to tell the HDMI source what resolutions are supported. There are EDID editors around. If you create a file edid.txt, then you can push this to the device using\" The comment of edid.txt file: 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt #copy the above commend in edid.txt, save&exit; pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan 7. The driver does NOT automatically switch to the resolution detected. Use the command: pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: You MUST set the timings via \u201cv4l2-ctl \u2013set-dv-bt-timings\u201d. You can pass in an index to the detected mode, or use: v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. 8. The chip supports two formats \u2013 BGR3 (the default) and UYVY. BGR3 is 24bpp, and UYVY is YUV4:2:2 16bpp. Over the normal 2 CSI-2 lanes the data rate is such that BGR3 can run at a maximum of 1080p30, whilst UYVY will go up to 1080p50. Use the following command to select UYVY, however your application may override that. v4l2-ctl -v pixelformat=UYVY 9. Check that the audio drivers / card is available to ALSA. pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1 means that the card number for the TC358743XBG is \u201c1\u201d and it might be different. 10. Install GStreamer tool. sudo apt install gstreamer1.0-tools Check gstreamer tool version: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note: Different versions have different command line parameters, which is very annoying. 11. Use gstreamer to record video and audio #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. foo.mkv is the output file. If your gstreamer is version 1.8 or above, you can try the following test command. In addition, alsasrc device=hw:1 represents the sound card of TC358743, you can use \u201carecord -l\u201d to query. #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: We recommend that you modify the above framerate parameter to the actual frame rate of your HDMI signal, the actual frame rate value is from the result of \u2018v4l2-ctl \u2013query-dv-timings\u2019 command. For the above HDMI device, because the frame rate is 60, so we modify the framerate parameter to 60 like the followint command. Record the video only: gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Record the video and audio: (if your shield supports audio also) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Packing List C790 Test video C780A test:https://www.youtube.com/watch?v=ecqyINoiHNQ C780B test:https://www.youtube.com/watch?v=nc-hwPT2Uak&t=15s Purchase link Purchase\uff1a C790 & C780 Purchase\uff1a C779","title":"HDMI to CSI & Audio"},{"location":"hdmi-csi-i2s/#hdmi-to-csii2s-bridge-guide","text":"Convert HDMI signal acquisition into CSI signal and I2S audio signal.","title":"HDMI to CSI&amp;I2S bridge guide"},{"location":"hdmi-csi-i2s/#introduction","text":"This module takes the incoming HDMI signal and converts it into a separate CSI signal and I2S audio signal. HDMI input supports up to 1080P60Hz. It works well on raspberry pi, there are three versions of this module in history(C779\u3001C780\u3001C790). C790 is the latest version. C790 has mitigate HDMI backpowering,also has two csi channels and four csi channels at the same time.","title":"Introduction"},{"location":"hdmi-csi-i2s/#features","text":"","title":"Features"},{"location":"hdmi-csi-i2s/#c790","text":"hardware parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 4 CSI-2 channels & clock The CSI-2 interface, with 15 pin FPC seat, spacing 1.0 mm, is located on the front of the C790 module. The CSI-2 interface, with 22 pin FPC seat, spacing 0.5 mm, is located on the back of the C790 module. Size: 30 x 45 mm Install:4 x M2.5 Power supply:3.3V Weight: 10g Pi 4B only support 1080P50Hz, limited by the number of CSI-2 channels. CM4 support 1080P60HZ, So if you must use 1080P60Hz input, please use CM4 and C790 together. interface C790 has two csi output interface. In fornt of C790, the CSI-2 interface is 15 pin FPC seat, spacing 1.0 mm. In back of C790, the CSI-2 interface is 22 pin FPC seat, spacing 0.5 mm. size Install C790 on raspberry pi for reference","title":"C790"},{"location":"hdmi-csi-i2s/#c780","text":"C780A hardware parameters HDMI input: supports up to 1080P50Hz on raspberry pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install:6 x M2.5 Power supply:3.3V Weight: 10g C780B hardware parameters HDMI input: supports up to 1080P60Hz on raspberry pi HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 4 CSI-2 channels & clock CSI-2 interface: 22 pin FPC seat, spacing 0.5 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install:6 x M2.5 Power supply:3.3V Weight: 10g interface The wiring of audio part is shown in Figure. size The size of C780 is shown in Figure. There are 6 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. As shown in Figure, the user can directly fix the module on the raspberry pi zero.C780 is designed to be broken, and the hole spacing before breaking can be perfectly installed with most series of raspberry pi.","title":"C780"},{"location":"hdmi-csi-i2s/#c779","text":"hardware parameters HDMI input: supports up to 1080P50Hz on raspberry pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip:Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 35 x 50 mm Install:4 x M2.5 Power supply:3.3V Weight: 10g size The size of C779 is shown in Figure. There are 4 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws.","title":"C779"},{"location":"hdmi-csi-i2s/#csi-interface-definitions","text":"The CSI (Camera Serial Interface) interfaces C779 and C780A have 15 pins each, while the C780B interface has 22 pins. The C790 interface is unique as it supports both 15 and 22 PIN configurations.","title":"CSI Interface Definitions"},{"location":"hdmi-csi-i2s/#software-demo","text":"The use guide of C790/C780/C779 depends on the official Raspberry Pi OS version you are using. Different versions have different usage methods. If you have some questions, Join our BLIKVM Discord Community for Support, FAQ & News! To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If \u201cuname -a\u201d reports anything less, then fix this before proceeding. pi@raspberrypi:~ $ uname -a Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. Update & upgrade the raspberry pi system (It will take a long time depend on the different country) sudo apt-get update sudo apt-get upgrade 2. Enable camera module (the camera is enabled by default in Raspberry pi Bullseys OS) sudo raspi-config sudo reboot Navigate to \u2018Interfacing Options\u2019 and hit Enter. Now select the \u2018Camera\u2019 option, and hit the Enter key to enable it. Select \u201cFinish\u201d and select to reboot your Raspberry Pi. reboot is important!! 3. Edit /boot/config.txt (that will need sudo) sudo nano /boot/config.txt Add the line: dtoverlay=tc358743 Add the line if your shield support audio like C780 or C790. dtoverlay=tc358743-audio please append the If (and only if) you have a device such as the C780 or C790 that supports the 22pin connector with all 4 lanes wired out, and are using a Compute Module with the CAM1 connector that also has all 4 lanes wired up, you can use: dtoverlay=tc358743,4lane=1 !!! note \"4. Check the amount of memory assigned to the CMA heap with \u201cdmesg | grep cma\u201d. The first line should be along the lines of\" pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 If it reports less than 96MB assigned to CMA, then edit /boot/cmdline.txt and add to the start of the line. Do NOT add any carriage returns. cma=96M !!! note \"5. Reboot. If all is well you should get a /dev/video0 device, and \u201cv4l2-ctl \u2013list-devices\u201d will tell you that it is provided by Unicam. After connecting all the cables, power on the Raspberry Pi, the C790 indicator light is normally green, and after opening the Raspberry Pi terminal, enter the following command:\" pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 !!! note \"6. This driver puts all the control in the hands of the user, or the user\u2019s application. By default there is no EDID loaded into the chip to allow it to tell the HDMI source what resolutions are supported. There are EDID editors around. If you create a file edid.txt, then you can push this to the device using\" The comment of edid.txt file: 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt #copy the above commend in edid.txt, save&exit; pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan 7. The driver does NOT automatically switch to the resolution detected. Use the command: pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: You MUST set the timings via \u201cv4l2-ctl \u2013set-dv-bt-timings\u201d. You can pass in an index to the detected mode, or use: v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. 8. The chip supports two formats \u2013 BGR3 (the default) and UYVY. BGR3 is 24bpp, and UYVY is YUV4:2:2 16bpp. Over the normal 2 CSI-2 lanes the data rate is such that BGR3 can run at a maximum of 1080p30, whilst UYVY will go up to 1080p50. Use the following command to select UYVY, however your application may override that. v4l2-ctl -v pixelformat=UYVY 9. Check that the audio drivers / card is available to ALSA. pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1 means that the card number for the TC358743XBG is \u201c1\u201d and it might be different. 10. Install GStreamer tool. sudo apt install gstreamer1.0-tools Check gstreamer tool version: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note: Different versions have different command line parameters, which is very annoying. 11. Use gstreamer to record video and audio #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. foo.mkv is the output file. If your gstreamer is version 1.8 or above, you can try the following test command. In addition, alsasrc device=hw:1 represents the sound card of TC358743, you can use \u201carecord -l\u201d to query. #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: We recommend that you modify the above framerate parameter to the actual frame rate of your HDMI signal, the actual frame rate value is from the result of \u2018v4l2-ctl \u2013query-dv-timings\u2019 command. For the above HDMI device, because the frame rate is 60, so we modify the framerate parameter to 60 like the followint command. Record the video only: gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Record the video and audio: (if your shield supports audio also) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9)","title":"Software demo"},{"location":"hdmi-csi-i2s/#packing-list","text":"C790","title":"Packing List"},{"location":"hdmi-csi-i2s/#test-video","text":"C780A test:https://www.youtube.com/watch?v=ecqyINoiHNQ C780B test:https://www.youtube.com/watch?v=nc-hwPT2Uak&t=15s","title":"Test video"},{"location":"hdmi-csi-i2s/#purchase-link","text":"Purchase\uff1a C790 & C780 Purchase\uff1a C779","title":"Purchase link"},{"location":"hid/","text":"Virtual Keyboard The virtual keyboard supports the use of combination keys. To do this, click and hold the corresponding virtual key with the mouse, drag it outside the virtual keyboard, and then release it to complete the operation of the combination key. For example, using the ctrl+alt+del combination key has the following effect: Currently, when pressing cmd+other keys simultaneously on a Mac computer, the other keys will not be released when cmd is released. This bug has not been fixed yet. Users can solve this problem by clicking on the incorrectly released key on the virtual keyboard first.","title":"Keyboard"},{"location":"hid/#virtual-keyboard","text":"The virtual keyboard supports the use of combination keys. To do this, click and hold the corresponding virtual key with the mouse, drag it outside the virtual keyboard, and then release it to complete the operation of the combination key. For example, using the ctrl+alt+del combination key has the following effect: Currently, when pressing cmd+other keys simultaneously on a Mac computer, the other keys will not be released when cmd is released. This bug has not been fixed yet. Users can solve this problem by clicking on the incorrectly released key on the virtual keyboard first.","title":"Virtual Keyboard"},{"location":"make-image/","text":"Make your own image When you have made modifications to an image and want to create your own image, you can follow the steps below on Linux to create a minimal image. Firstly, use the gparted software to open the SD card of the image you want to create. Use gparted to partition the unused space and set it as unallocated. This ensures that this portion of empty space without any valid content is not included in the image creation. Next, use the fdisk command to view the size of the available space, as shown in the following image, which is 10151935. Then, use the dd command to write to an empty img file. Set the count value to be greater than the size of the volume end obtained from fdisk by at least 1. touch blikvm-armbian-v4-20230623.img sudo dd if=/dev/sdb of=./blikvm-armbian-v4-20230623.img bs=512 count=10151936 Wait for the dd command to finish executing.","title":"Make Image"},{"location":"make-image/#make-your-own-image","text":"When you have made modifications to an image and want to create your own image, you can follow the steps below on Linux to create a minimal image. Firstly, use the gparted software to open the SD card of the image you want to create. Use gparted to partition the unused space and set it as unallocated. This ensures that this portion of empty space without any valid content is not included in the image creation. Next, use the fdisk command to view the size of the available space, as shown in the following image, which is 10151935. Then, use the dd command to write to an empty img file. Set the count value to be greater than the size of the volume end obtained from fdisk by at least 1. touch blikvm-armbian-v4-20230623.img sudo dd if=/dev/sdb of=./blikvm-armbian-v4-20230623.img bs=512 count=10151936 Wait for the dd command to finish executing.","title":"Make your own image"},{"location":"modify_pikvm_image/","text":"Modifying PiKVM image to work with BliKVM hardware Because the blikvm hardware implementation scheme and PiKVM hardware implementation scheme are not exactly the same, you need to modify some errors through the following configuration for the official image of PiKVM. Of course, you can use the configured image . Fan config Since BliKVM's fan hardware is different to PiKVM's, you need to replace the control fan script first. The following default starting fan temperature is 40 degrees Celsius su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro Edit the /etc/kvmd/override.yaml file and add the following content to remove the web UI error warning about fans. kvmd: info: fan: unix: '' Check EDID file for 1080P60Hz input The function of the EDID file is to set the controlled computer to input according to the expected resolution. Since the image EDID file of PiKVM in different periods does not necessarily meet 1080P60Hz, when you use the CM4 version of hardware, it is found that the default output of the controlled computer is not 1080P60Hz, you can modify /etc/kvmd/tc358743-edid.hex to the following contents 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 make sure /boot/config.txt has the 4lane=1 entry in it for 1080p60hz support # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio If you use webrtc can't get audio, try to edit /etc/kvmd/janus/janus.plugin.ustreamer.jcfg to add audio support. audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" }","title":"Config for PiKVM OS"},{"location":"modify_pikvm_image/#modifying-pikvm-image-to-work-with-blikvm-hardware","text":"Because the blikvm hardware implementation scheme and PiKVM hardware implementation scheme are not exactly the same, you need to modify some errors through the following configuration for the official image of PiKVM. Of course, you can use the configured image .","title":"Modifying PiKVM image to work with BliKVM hardware"},{"location":"modify_pikvm_image/#fan-config","text":"Since BliKVM's fan hardware is different to PiKVM's, you need to replace the control fan script first. The following default starting fan temperature is 40 degrees Celsius su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro Edit the /etc/kvmd/override.yaml file and add the following content to remove the web UI error warning about fans. kvmd: info: fan: unix: ''","title":"Fan config"},{"location":"modify_pikvm_image/#check-edid-file-for-1080p60hz-input","text":"The function of the EDID file is to set the controlled computer to input according to the expected resolution. Since the image EDID file of PiKVM in different periods does not necessarily meet 1080P60Hz, when you use the CM4 version of hardware, it is found that the default output of the controlled computer is not 1080P60Hz, you can modify /etc/kvmd/tc358743-edid.hex to the following contents 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 make sure /boot/config.txt has the 4lane=1 entry in it for 1080p60hz support # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio If you use webrtc can't get audio, try to edit /etc/kvmd/janus/janus.plugin.ustreamer.jcfg to add audio support. audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" }","title":"Check EDID file for 1080P60Hz input"},{"location":"msd/","text":"Mass Storage Drive Reinstall the system Video BliKVM's USB device simulation feature allows you to remotely mount images on the virtual machine's mass storage drive, making it easy to install or reinstall operating systems and other software. This can be a useful feature for system administrators who need to manage multiple virtual machines remotely. By mounting an image on the mass storage drive, you can quickly and easily set up or configure a new virtual machine without having to physically connect a USB drive or other external storage device. Note: the size of the MSD is limited by the size of your sd card or eMMC module. Web UI Currently, except for uploading images that are not yet supported, all other tasks can be completed through the web UI Upload images manually (without Web UI) Confirm that the following four paths exist. If you are using the official latest image of blikvm, and it is fully configured, there is no need to check. /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy SSH logs in to blikvm, executes the rw command, and changes the system permission to writable. rw In your PC ,use scp cmd send iso file to kvm board. scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ excute msd cmd.wait until excute end. If you don't use option paramter\uff1a The default size of the USB flash disk is 5GB. The default filename is scan /mnt/msd/user dir. The default msd name is ventoy. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make If your iso is large than 5GB.You can specify the optional parameter - s xxx, xxx is the Size. If you need specify iso ,you can use -f xxx.iso. If you want to specify the msd name, you can use -n xxx. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso Tips: cp progress slowly, Please be patient. If you want to excute other cmd, you can use other option. c option contains : make/conn/disconn/clean connect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn disconnect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn clean msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean throuht web restart PC, enter BIOS, modify boot priority,set blikvm USB first. according to step, select operate system , format partition and install system.","title":"MSD"},{"location":"msd/#mass-storage-drive","text":"Reinstall the system Video BliKVM's USB device simulation feature allows you to remotely mount images on the virtual machine's mass storage drive, making it easy to install or reinstall operating systems and other software. This can be a useful feature for system administrators who need to manage multiple virtual machines remotely. By mounting an image on the mass storage drive, you can quickly and easily set up or configure a new virtual machine without having to physically connect a USB drive or other external storage device. Note: the size of the MSD is limited by the size of your sd card or eMMC module.","title":"Mass Storage Drive"},{"location":"msd/#web-ui","text":"Currently, except for uploading images that are not yet supported, all other tasks can be completed through the web UI","title":"Web UI"},{"location":"msd/#upload-images-manually-without-web-ui","text":"Confirm that the following four paths exist. If you are using the official latest image of blikvm, and it is fully configured, there is no need to check. /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy SSH logs in to blikvm, executes the rw command, and changes the system permission to writable. rw In your PC ,use scp cmd send iso file to kvm board. scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ excute msd cmd.wait until excute end. If you don't use option paramter\uff1a The default size of the USB flash disk is 5GB. The default filename is scan /mnt/msd/user dir. The default msd name is ventoy. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make If your iso is large than 5GB.You can specify the optional parameter - s xxx, xxx is the Size. If you need specify iso ,you can use -f xxx.iso. If you want to specify the msd name, you can use -n xxx. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso Tips: cp progress slowly, Please be patient. If you want to excute other cmd, you can use other option. c option contains : make/conn/disconn/clean connect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn disconnect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn clean msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean throuht web restart PC, enter BIOS, modify boot priority,set blikvm USB first. according to step, select operate system , format partition and install system.","title":"Upload images manually (without Web UI)"},{"location":"port-forwarding/","text":"Port forwarding If your ISP provides an external IP address for the router, you can configure Port forwarding to access BliKVM: The web interface uses the HTTP protocol and occupies port 80; If your hardware is v1 v2 v3 and you are using web rtc transmission, the port is 8188; If your hardware is v4 and you are using mjepg transmission, the port is 8008; Note that the port does not support modification and can only be configured for forwarding; If you do not have an external IP address, we suggest trying to use Tailscale VPN \u3002","title":"Port Forwarding"},{"location":"port-forwarding/#port-forwarding","text":"If your ISP provides an external IP address for the router, you can configure Port forwarding to access BliKVM: The web interface uses the HTTP protocol and occupies port 80; If your hardware is v1 v2 v3 and you are using web rtc transmission, the port is 8188; If your hardware is v4 and you are using mjepg transmission, the port is 8008; Note that the port does not support modification and can only be configured for forwarding; If you do not have an external IP address, we suggest trying to use Tailscale VPN \u3002","title":"Port forwarding"},{"location":"rtc/","text":"RTC Clock The purpose of an RTC (Real-Time Clock) is to provide real-time information about the current date and time for a device or system. It is an independent clock chip or module that has its own power source, allowing it to maintain accurate time even when the device is powered off or experiences a power outage. Due to shipping restrictions on international deliveries, the RTC hardware is shipped without a battery, and users need to purchase a CR1220 button cell battery themselves. The specific RTC clock model used in different versions of BliKVM may vary, and the usage methods may differ slightly. BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563 1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc0 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30 BliKVM V4 - pcf8563 1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc1 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"RTC clock"},{"location":"rtc/#rtc-clock","text":"The purpose of an RTC (Real-Time Clock) is to provide real-time information about the current date and time for a device or system. It is an independent clock chip or module that has its own power source, allowing it to maintain accurate time even when the device is powered off or experiences a power outage. Due to shipping restrictions on international deliveries, the RTC hardware is shipped without a battery, and users need to purchase a CR1220 button cell battery themselves. The specific RTC clock model used in different versions of BliKVM may vary, and the usage methods may differ slightly.","title":"RTC Clock"},{"location":"rtc/#blikvm-v2-pcie-and-blikvm-v3-hat-pcf8563","text":"1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc0 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563"},{"location":"rtc/#blikvm-v4-pcf8563","text":"1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc1 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V4 - pcf8563"},{"location":"serial_over_usb/","text":"Serial-over-USB connection The BliKVM device can be accessed through the serial port terminal. 1.For hardware connection, you should use the USB to ttl module to connect the USB of the computer to the uart of BliKVM. If you are using the Hat version, please connect the serial ports GPIO14 and GPIO15. If you are using the PCIe version, connect the GTR pin marked by the PCB 2.Install terminal login tools on the computer. For example, you can install putty tools on Windows 3. Use the putty instruction. Enter the correct COM port. The default baud rate is 115200. Select serial as the connection method, and then click Open\uff08Use PiKVM firmware as an example\uff09 If your computer cannot correctly recognize the USB to TTL module, please follow the steps below to install the driver for your computer Connect the usb-a connector to your admin host (in this example, it's on a windows host). As a result, device manager will show a new USB Serial device in Other devices. Download and extract/run drivers. In this example, I downloaded and extracted the ZIP file. https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all Update driver for the new USB Serial device, point it to where you extracted the files, and click Next then Close. If done right, the new USB serial device should now show up under Ports as USB-SERIAL CH340 (COMX).","title":"Serial-over-USB"},{"location":"serial_over_usb/#serial-over-usb-connection","text":"The BliKVM device can be accessed through the serial port terminal. 1.For hardware connection, you should use the USB to ttl module to connect the USB of the computer to the uart of BliKVM. If you are using the Hat version, please connect the serial ports GPIO14 and GPIO15. If you are using the PCIe version, connect the GTR pin marked by the PCB 2.Install terminal login tools on the computer. For example, you can install putty tools on Windows 3. Use the putty instruction. Enter the correct COM port. The default baud rate is 115200. Select serial as the connection method, and then click Open\uff08Use PiKVM firmware as an example\uff09 If your computer cannot correctly recognize the USB to TTL module, please follow the steps below to install the driver for your computer Connect the usb-a connector to your admin host (in this example, it's on a windows host). As a result, device manager will show a new USB Serial device in Other devices. Download and extract/run drivers. In this example, I downloaded and extracted the ZIP file. https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all Update driver for the new USB Serial device, point it to where you extracted the files, and click Next then Close. If done right, the new USB serial device should now show up under Ports as USB-SERIAL CH340 (COMX).","title":"Serial-over-USB connection"},{"location":"static_ip/","text":"Set static IP To configure a static IP address on a BliKVM image, you can follow these steps: SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/dhcpcd.conf Within the file, locate the section that starts with \"# Example static IP configuration\". Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: interface eth0 static ip_address=192.168.1.100/24 static routers=192.168.1.1 static domain_name_servers=192.168.1.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet.","title":"Set Static IP "},{"location":"static_ip/#set-static-ip","text":"To configure a static IP address on a BliKVM image, you can follow these steps: SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/dhcpcd.conf Within the file, locate the section that starts with \"# Example static IP configuration\". Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: interface eth0 static ip_address=192.168.1.100/24 static routers=192.168.1.1 static domain_name_servers=192.168.1.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet.","title":"Set static IP"},{"location":"switch-guide/","text":"HDMI Switch Mannul BliKVM-Switch-V1.0 uses and tests video, supporting BliKVM and PiKVM Introduction BliKVM-Switch-V1.0 is a four channel HDMI+USB switch, which supports panel button, desktop controller, KVM remote to switch between computers. Maximum support of the switch itself 4K@60HZ Plug and play, drive free. BliKVM-Switch-V1.0 uses the same hardware solution as XH-HK4401, AG7210 HDMI switching chip supports up to 4K@60Hz, CH444G USB switching chip supports USB2.0. The difference is that BliKVM-Switch-V1.0 is equipped with KVM USB cable, which can realize KVM port selection. BliKVM-Switch-V1.0 is compatible with BliKVM and PiKVM. points for attention The switch can be powered directly from the USB input to the computer, that is, the switch can work normally without power supply. If the USB power supply of the controlled computer cannot make the switch work, the switch can be powered independently. The switch package only provides a USB power cable, but does not provide a power adapter. The customer needs to configure a power adapter (5V). Desktop controller can control HDMI switch with USB cable. For customers who do not use KVM, this is another way of switching for easy cable management. HDMI input support up to 4096x2160/60Hz resolution 4K 60Hz input, the power is about 200 mW. Interface diagram Front and back interface diagram, the control interface in the right figure is the remote control interface. Schematic Diagram of Side Interface. Equipment connection diagram. Software configuration If you are using BliKVM software and have powered on the switch and connected the cables before starting BliKVM, no additional configuration is needed. BliKVM will automatically detect the switch when it starts. If automatic detection fails, you can manually specify the switch device. First, confirm the device descriptor name of the switch by using the terminal, such as /dev/ttyUSB0 . Then, edit the switch_handle field in /usr/bin/blikvm/package.json and assign /dev/ttyUSB0 to it. Afterward, restart BliKVM. Click MORE in the lower left corner, find the BliKVM switch column, and then switch. Note that the flashing blue dot of the corresponding channel indicates that the switch insertion is recognized and is in the current channel. If there is no blue dot, the switch insertion is not recognized\u3002 If you use PiKVM software, please configure it according to the following instructions. Log in to PiKVM through SSH. The user name and password are root; Uses the rw command on the terminal to change the system to a read-write system; Edit /etc/kvmd/override. yaml this file to make it contain the following contents. That is, add after the original content. kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] Use the ro command on the terminal to reset the system to a read-only system; Use 'systemctl restart kvmd' on the terminal to restart the service; Enter the PiKVM web interface and click the GPIO menu. You should see 4 inputs, one of which has a green circle to indicate that it is currently selected. Click Other Inputs to change the selected host. Control protocol If you want to use the blicube switch on other platforms, please refer to the following protocol The communication baud rate is 19200 The message sent to switch by switching to channel 1 is SW1\\r\\nG01gA The message sent to switch by switching to channel 2 is SW2\\r\\nG02gA The message sent to switch by switching to channel 3 is SW3\\r\\nG03gA The message sent to switch by switching to channel 4 is SW4\\r\\nG04gA The message returned by the switch for the current channel is: G01gA , G02gA , G03gA , G04gA Packing list product quantity note HDMI KVM Switch(4-channel) 1 110mm * 60mm * 33mm Desktop controller 1 USB cable of Desktop controller 4 length: 1.2m HDMI(Standard) cable 5 length: 1.5m USB power cable 1 length: 0.8m USB cable of KVM 1 length: 1.5m USB cable of Desktop controller 1 length: 1m","title":"Multiport KVM-over-IP"},{"location":"switch-guide/#hdmi-switch-mannul","text":"BliKVM-Switch-V1.0 uses and tests video, supporting BliKVM and PiKVM","title":"HDMI Switch Mannul"},{"location":"switch-guide/#introduction","text":"BliKVM-Switch-V1.0 is a four channel HDMI+USB switch, which supports panel button, desktop controller, KVM remote to switch between computers. Maximum support of the switch itself 4K@60HZ Plug and play, drive free. BliKVM-Switch-V1.0 uses the same hardware solution as XH-HK4401, AG7210 HDMI switching chip supports up to 4K@60Hz, CH444G USB switching chip supports USB2.0. The difference is that BliKVM-Switch-V1.0 is equipped with KVM USB cable, which can realize KVM port selection. BliKVM-Switch-V1.0 is compatible with BliKVM and PiKVM. points for attention The switch can be powered directly from the USB input to the computer, that is, the switch can work normally without power supply. If the USB power supply of the controlled computer cannot make the switch work, the switch can be powered independently. The switch package only provides a USB power cable, but does not provide a power adapter. The customer needs to configure a power adapter (5V). Desktop controller can control HDMI switch with USB cable. For customers who do not use KVM, this is another way of switching for easy cable management. HDMI input support up to 4096x2160/60Hz resolution 4K 60Hz input, the power is about 200 mW.","title":"Introduction"},{"location":"switch-guide/#interface-diagram","text":"Front and back interface diagram, the control interface in the right figure is the remote control interface. Schematic Diagram of Side Interface. Equipment connection diagram.","title":"Interface diagram"},{"location":"switch-guide/#software-configuration","text":"If you are using BliKVM software and have powered on the switch and connected the cables before starting BliKVM, no additional configuration is needed. BliKVM will automatically detect the switch when it starts. If automatic detection fails, you can manually specify the switch device. First, confirm the device descriptor name of the switch by using the terminal, such as /dev/ttyUSB0 . Then, edit the switch_handle field in /usr/bin/blikvm/package.json and assign /dev/ttyUSB0 to it. Afterward, restart BliKVM. Click MORE in the lower left corner, find the BliKVM switch column, and then switch. Note that the flashing blue dot of the corresponding channel indicates that the switch insertion is recognized and is in the current channel. If there is no blue dot, the switch insertion is not recognized\u3002 If you use PiKVM software, please configure it according to the following instructions. Log in to PiKVM through SSH. The user name and password are root; Uses the rw command on the terminal to change the system to a read-write system; Edit /etc/kvmd/override. yaml this file to make it contain the following contents. That is, add after the original content. kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] Use the ro command on the terminal to reset the system to a read-only system; Use 'systemctl restart kvmd' on the terminal to restart the service; Enter the PiKVM web interface and click the GPIO menu. You should see 4 inputs, one of which has a green circle to indicate that it is currently selected. Click Other Inputs to change the selected host.","title":"Software configuration"},{"location":"switch-guide/#control-protocol","text":"If you want to use the blicube switch on other platforms, please refer to the following protocol The communication baud rate is 19200 The message sent to switch by switching to channel 1 is SW1\\r\\nG01gA The message sent to switch by switching to channel 2 is SW2\\r\\nG02gA The message sent to switch by switching to channel 3 is SW3\\r\\nG03gA The message sent to switch by switching to channel 4 is SW4\\r\\nG04gA The message returned by the switch for the current channel is: G01gA , G02gA , G03gA , G04gA","title":"Control protocol"},{"location":"switch-guide/#packing-list","text":"product quantity note HDMI KVM Switch(4-channel) 1 110mm * 60mm * 33mm Desktop controller 1 USB cable of Desktop controller 4 length: 1.2m HDMI(Standard) cable 5 length: 1.5m USB power cable 1 length: 0.8m USB cable of KVM 1 length: 1.5m USB cable of Desktop controller 1 length: 1m","title":"Packing list"},{"location":"tailscale/","text":"Tailscale VPN Tailscale can be used to access your BliKVM from the public internet. It is a convenient and free networking tool for setting up a small VPN network. This document provides an example for accessing your BliKVM over the internet, but you can also use Zerotier or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the Tailscale documentation. BliKVM\u5b89\u88c5Tailscale First, make sure that your system has read-write access. If it's a read-only system, use the rw command to make it writable. Then, proceed with the Tailscale installation by running the following command: curl -fsSL https://tailscale.com/install.sh | sh Note that in some regions, such as China, downloading Tailscale directly might be problematic due to network restrictions. Please configure your network accordingly. Adding BliKVM to your Tailscale Network Register an account on the Tailscale website and generate your own keys in the settings. On the BliKVM terminal, use the following command to add BliKVM to your Tailscale network: sudo tailscale up --authkey=your-auth-key --accept-routes If everything goes well, you can run ip addr show tailscale0 on the BliKVM terminal to view the IP address assigned by Tailscale for the virtual network. Here's an example output: 3: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100.126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever The IP address, such as 100.126.223.28, can be used to access the BliKVM web interface from your host machine. \u4e3b\u673a\u5b89\u88c5Tailscale Download and install Tailscale from the Tailscale website on your controlling host machine. Log in with your Tailscale account, and then you can check the Tailscale admin page to verify if both your machines are online. Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://<tailscale_kvm_ip>","title":"Tailscale VPN"},{"location":"tailscale/#tailscale-vpn","text":"Tailscale can be used to access your BliKVM from the public internet. It is a convenient and free networking tool for setting up a small VPN network. This document provides an example for accessing your BliKVM over the internet, but you can also use Zerotier or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the Tailscale documentation.","title":"Tailscale VPN"},{"location":"tailscale/#blikvmtailscale","text":"First, make sure that your system has read-write access. If it's a read-only system, use the rw command to make it writable. Then, proceed with the Tailscale installation by running the following command: curl -fsSL https://tailscale.com/install.sh | sh Note that in some regions, such as China, downloading Tailscale directly might be problematic due to network restrictions. Please configure your network accordingly.","title":"BliKVM\u5b89\u88c5Tailscale"},{"location":"tailscale/#adding-blikvm-to-your-tailscale-network","text":"Register an account on the Tailscale website and generate your own keys in the settings. On the BliKVM terminal, use the following command to add BliKVM to your Tailscale network: sudo tailscale up --authkey=your-auth-key --accept-routes If everything goes well, you can run ip addr show tailscale0 on the BliKVM terminal to view the IP address assigned by Tailscale for the virtual network. Here's an example output: 3: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100.126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever The IP address, such as 100.126.223.28, can be used to access the BliKVM web interface from your host machine.","title":"Adding BliKVM to your Tailscale Network"},{"location":"tailscale/#tailscale","text":"Download and install Tailscale from the Tailscale website on your controlling host machine. Log in with your Tailscale account, and then you can check the Tailscale admin page to verify if both your machines are online. Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://<tailscale_kvm_ip>","title":"\u4e3b\u673a\u5b89\u88c5Tailscale"},{"location":"update/","text":"Software update introduction Introduction The currently available versions of the BLIKVM project are hosted in the release package of the github. The update software function needs to keep the device connected. There are currently two ways to update the software. Method 1: Click the update button through the web interface, and the program will be updated automatically. Restart is required after the update. Method 2: Manually run the script on the KVM terminal to update, and restart after the update. Common causes of upgrade errors The device is not connected to the network; Network access to github is limited; We strongly recommend performing the update while you are in close proximity to the BliKVM hardware you are upgrading. The reason is if anything goes wrong you can intervene. If you are familiar with command-line operations, we recommend manually updating so that you can monitor the command-line status in real time. If the update is abnormal and the web interface cannot exit the update status, use ssh to the terminal can and restart to recover. Manually run the script to update In the terminal rw sudo -i cd /opt/bin/blikvm/ git pull --rebase python3 /opt/bin/blikvm/script/update.py ro Observe the output of the terminal. When you see the message of successful upgrade, the terminal enters reboot, and the reboot takes effect. If you are unable to update successfully due to network issues, you can download the latest release.tar.gz package on another PC with a stable network connection and follow the instructions below for installation. SSH into the device terminal and use tar -zxvf release.tar.gz to extract the release.tar.gz file. rw sudo -i cd /your release path/ python3 install_release.py --releasepath=./ ro You can compare the versions before and after in /usr/bin/blikvm/package.json. If you have upgraded to the specified version, the installation is successful, and you can reboot for the changes to take effect. Web UI update After clicking the More Options button, find the CheckUpdate button and click it. If the available version is found, the pop-up box in the figure below will appear. Click OK to enter the upgrade process. The web interface is temporarily inoperable during the upgrade process. View the current update status by manually refreshing the page. When the message of successful update appears, it means that the update has been successful. Click the restart button, and the new version of software will take effect.","title":"Upgrade"},{"location":"update/#software-update-introduction","text":"","title":"Software update introduction"},{"location":"update/#introduction","text":"The currently available versions of the BLIKVM project are hosted in the release package of the github. The update software function needs to keep the device connected. There are currently two ways to update the software. Method 1: Click the update button through the web interface, and the program will be updated automatically. Restart is required after the update. Method 2: Manually run the script on the KVM terminal to update, and restart after the update. Common causes of upgrade errors The device is not connected to the network; Network access to github is limited; We strongly recommend performing the update while you are in close proximity to the BliKVM hardware you are upgrading. The reason is if anything goes wrong you can intervene. If you are familiar with command-line operations, we recommend manually updating so that you can monitor the command-line status in real time. If the update is abnormal and the web interface cannot exit the update status, use ssh to the terminal can and restart to recover.","title":"Introduction"},{"location":"update/#manually-run-the-script-to-update","text":"In the terminal rw sudo -i cd /opt/bin/blikvm/ git pull --rebase python3 /opt/bin/blikvm/script/update.py ro Observe the output of the terminal. When you see the message of successful upgrade, the terminal enters reboot, and the reboot takes effect. If you are unable to update successfully due to network issues, you can download the latest release.tar.gz package on another PC with a stable network connection and follow the instructions below for installation. SSH into the device terminal and use tar -zxvf release.tar.gz to extract the release.tar.gz file. rw sudo -i cd /your release path/ python3 install_release.py --releasepath=./ ro You can compare the versions before and after in /usr/bin/blikvm/package.json. If you have upgraded to the specified version, the installation is successful, and you can reboot for the changes to take effect.","title":"Manually run the script to update"},{"location":"update/#web-ui-update","text":"After clicking the More Options button, find the CheckUpdate button and click it. If the available version is found, the pop-up box in the figure below will appear. Click OK to enter the upgrade process. The web interface is temporarily inoperable during the upgrade process. View the current update status by manually refreshing the page. When the message of successful update appears, it means that the update has been successful. Click the restart button, and the new version of software will take effect.","title":"Web UI update"},{"location":"usb-splitter-guide/","text":"USB/PWR Splitter guide 1. Introduction The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage. 2.Mechanical Diagram 3.Test video USB splitter Video 4.3D printable case A simple snap fit case for the USB splitter. Download file","title":"USB Splitter"},{"location":"usb-splitter-guide/#usbpwr-splitter-guide","text":"","title":"USB/PWR Splitter guide"},{"location":"usb-splitter-guide/#1-introduction","text":"The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage.","title":"1. Introduction"},{"location":"usb-splitter-guide/#2mechanical-diagram","text":"","title":"2.Mechanical Diagram"},{"location":"usb-splitter-guide/#3test-video","text":"USB splitter Video","title":"3.Test video"},{"location":"usb-splitter-guide/#43d-printable-case","text":"A simple snap fit case for the USB splitter. Download file","title":"4.3D printable case"},{"location":"wifi/","text":"Wifi Configure Because BLIKVM has many kinds of hardware and supports different OS, such as BLIKVM OS and PiKVM OS, different OS confifure wifi methods may not be the same. Please confirm the hardware and OS usage before using the method in this document. Please confirm that the hardware you use supports wifi function, for example, the CM400200 version does not have wifi function; If the SOC of KVM hardware is CM4, please confirm whether wifi antenna is connected; PiKVM OS is arch linux; BLIKVM OS raspberry pi series is debian system, and H616 series is armbian system; v1 v2 v3 use raspi-config for wifi configure on raspberry pi debian system Log in to ssh, command: ssh blikvm@ip The system is reloaded as writable. Command: rw Start raspi-config, command: sudo raspi-config Select System Options Select Wireless LAN Select the country where wifi is located, and China will select CN. If it has been set before, this step will skip to 7 Enter the ssid (name) of Wi-Fi Enter the Wi-Fi password. If there is no password, press Enter directly At this time, you will return to the interface in Step 4, press the tab key to select , and press Enter Check whether to connect to wifi. Command: ifconfig wlan0. If you see the ip obtained, you are connected Mount the system as read-only. Command: ro v4 Hardware using Armbian System with armbian-config Log in via SSH using the command: ssh blikvm@ip to access the Armbian system. Enter the following command to launch the armbian-config tool: sudo armbian-config In the armbian-config menu, navigate and select options using the arrow keys and press Enter. Scroll down to the \"Network\" option using the arrow keys and press Enter to enter the submenu. In the \"Network\" submenu, select the \"Wireless\" option and press Enter to enter the Wi-Fi configuration menu. In the Wi-Fi configuration menu, select the \"Connect to Wi-Fi\" option and press Enter to enter the Wi-Fi connection setup. armbian-config will list the available wireless interfaces and already configured networks. Select the wireless interface you want to connect to and press Enter. armbian-config will display the list of available Wi-Fi networks. Use the arrow keys to select the Wi-Fi network you want to connect to and press Enter. If the Wi-Fi network is password-protected, armbian-config will prompt you to enter the Wi-Fi password. Enter the password and press Enter. Wait for a moment while the Armbian system attempts to connect to the specified Wi-Fi network. If the connection is successful, you will see a corresponding message on the screen. Exit the armbian-config tool. Please note that the menu options and configurations mentioned above may vary slightly depending on the specific version of the Armbian system. Make sure to follow the appropriate steps based on your system version and configuration.","title":"Wifi Config"},{"location":"wifi/#wifi-configure","text":"Because BLIKVM has many kinds of hardware and supports different OS, such as BLIKVM OS and PiKVM OS, different OS confifure wifi methods may not be the same. Please confirm the hardware and OS usage before using the method in this document. Please confirm that the hardware you use supports wifi function, for example, the CM400200 version does not have wifi function; If the SOC of KVM hardware is CM4, please confirm whether wifi antenna is connected; PiKVM OS is arch linux; BLIKVM OS raspberry pi series is debian system, and H616 series is armbian system;","title":"Wifi Configure"},{"location":"wifi/#v1-v2-v3-use-raspi-config-for-wifi-configure-on-raspberry-pi-debian-system","text":"Log in to ssh, command: ssh blikvm@ip The system is reloaded as writable. Command: rw Start raspi-config, command: sudo raspi-config Select System Options Select Wireless LAN Select the country where wifi is located, and China will select CN. If it has been set before, this step will skip to 7 Enter the ssid (name) of Wi-Fi Enter the Wi-Fi password. If there is no password, press Enter directly At this time, you will return to the interface in Step 4, press the tab key to select , and press Enter Check whether to connect to wifi. Command: ifconfig wlan0. If you see the ip obtained, you are connected Mount the system as read-only. Command: ro","title":"v1 v2 v3 use raspi-config for wifi configure on raspberry pi debian system"},{"location":"wifi/#v4-hardware-using-armbian-system-with-armbian-config","text":"Log in via SSH using the command: ssh blikvm@ip to access the Armbian system. Enter the following command to launch the armbian-config tool: sudo armbian-config In the armbian-config menu, navigate and select options using the arrow keys and press Enter. Scroll down to the \"Network\" option using the arrow keys and press Enter to enter the submenu. In the \"Network\" submenu, select the \"Wireless\" option and press Enter to enter the Wi-Fi configuration menu. In the Wi-Fi configuration menu, select the \"Connect to Wi-Fi\" option and press Enter to enter the Wi-Fi connection setup. armbian-config will list the available wireless interfaces and already configured networks. Select the wireless interface you want to connect to and press Enter. armbian-config will display the list of available Wi-Fi networks. Use the arrow keys to select the Wi-Fi network you want to connect to and press Enter. If the Wi-Fi network is password-protected, armbian-config will prompt you to enter the Wi-Fi password. Enter the password and press Enter. Wait for a moment while the Armbian system attempts to connect to the specified Wi-Fi network. If the connection is successful, you will see a corresponding message on the screen. Exit the armbian-config tool. Please note that the menu options and configurations mentioned above may vary slightly depending on the specific version of the Armbian system. Make sure to follow the appropriate steps based on your system version and configuration.","title":"v4 Hardware using Armbian System with armbian-config"}]}
\ No newline at end of file
diff --git a/generated/en/serial_over_usb/index.html b/generated/en/serial_over_usb/index.html
index f75da406..b64570f2 100644
--- a/generated/en/serial_over_usb/index.html
+++ b/generated/en/serial_over_usb/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -297,7 +297,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -347,7 +347,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -357,12 +357,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -371,28 +371,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -480,13 +480,13 @@ <h1 id="serial-over-usb-connection">Serial-over-USB connection</h1>
             </div>
 </div>
 </a>
-<a aria-label="Next: USB flash Drive" class="md-footer__link md-footer__link--next" href="../msd/" rel="next">
+<a aria-label="Next: MSD" class="md-footer__link md-footer__link--next" href="../msd/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              USB flash Drive
+              MSD
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/sitemap.xml b/generated/en/sitemap.xml
index 41aeb4aa..187c358e 100644
--- a/generated/en/sitemap.xml
+++ b/generated/en/sitemap.xml
@@ -2,157 +2,157 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
 </urlset>
\ No newline at end of file
diff --git a/generated/en/sitemap.xml.gz b/generated/en/sitemap.xml.gz
index 2c80eb6d..2e3817a6 100644
Binary files a/generated/en/sitemap.xml.gz and b/generated/en/sitemap.xml.gz differ
diff --git a/generated/en/static_ip/index.html b/generated/en/static_ip/index.html
index 80cfb487..b8d97c85 100644
--- a/generated/en/static_ip/index.html
+++ b/generated/en/static_ip/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -267,7 +267,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -277,12 +277,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -297,7 +297,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -347,7 +347,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -357,12 +357,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -371,28 +371,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/en/switch-guide/index.html b/generated/en/switch-guide/index.html
index 843fb55b..ed261209 100644
--- a/generated/en/switch-guide/index.html
+++ b/generated/en/switch-guide/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>Multiport KVM over IP - BliKVM Handbook</title>
+<title>Multiport KVM-over-IP - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              Multiport KVM over IP
+              Multiport KVM-over-IP
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -346,7 +346,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -356,17 +356,17 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <label class="md-nav__link md-nav__link--active" for="__toc">
-          Multiport KVM over IP
+          Multiport KVM-over-IP
           <span class="md-nav__icon md-icon"></span>
 </label>
 <a class="md-nav__link md-nav__link--active" href="./">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 <nav aria-label="Table of contents" class="md-nav md-nav--secondary">
 <label class="md-nav__title" for="__toc">
@@ -408,28 +408,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -663,7 +663,7 @@ <h2 id="packing-list"><strong>Packing list</strong></h2>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: USB splitter" class="md-footer__link md-footer__link--prev" href="../usb-splitter-guide/" rel="prev">
+<a aria-label="Previous: USB Splitter" class="md-footer__link md-footer__link--prev" href="../usb-splitter-guide/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -672,17 +672,17 @@ <h2 id="packing-list"><strong>Packing list</strong></h2>
 <span class="md-footer__direction">
                 Previous
               </span>
-              USB splitter
+              USB Splitter
             </div>
 </div>
 </a>
-<a aria-label="Next: make image" class="md-footer__link md-footer__link--next" href="../make-image/" rel="next">
+<a aria-label="Next: Make Image" class="md-footer__link md-footer__link--next" href="../make-image/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              make image
+              Make Image
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/tailscale/index.html b/generated/en/tailscale/index.html
index bf5d40a4..0c3e2428 100644
--- a/generated/en/tailscale/index.html
+++ b/generated/en/tailscale/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item md-nav__item--active">
@@ -294,7 +294,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -304,12 +304,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -324,7 +324,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -374,7 +374,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -384,12 +384,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -398,28 +398,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -513,7 +513,7 @@ <h2 id="tailscale"><strong>主机安装Tailscale</strong></h2>
 </main>
 <footer class="md-footer">
 <nav aria-label="Footer" class="md-footer__inner md-grid">
-<a aria-label="Previous: Port forwarding" class="md-footer__link md-footer__link--prev" href="../port-forwarding/" rel="prev">
+<a aria-label="Previous: Port Forwarding" class="md-footer__link md-footer__link--prev" href="../port-forwarding/" rel="prev">
 <div class="md-footer__button md-icon">
 <svg viewbox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12Z"></path></svg>
 </div>
@@ -522,7 +522,7 @@ <h2 id="tailscale"><strong>主机安装Tailscale</strong></h2>
 <span class="md-footer__direction">
                 Previous
               </span>
-              Port forwarding
+              Port Forwarding
             </div>
 </div>
 </a>
diff --git a/generated/en/update/index.html b/generated/en/update/index.html
index 96635300..218257b7 100644
--- a/generated/en/update/index.html
+++ b/generated/en/update/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -294,7 +294,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -304,12 +304,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -324,7 +324,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -374,7 +374,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -384,12 +384,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -398,28 +398,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -552,13 +552,13 @@ <h2 id="web-ui-update"><strong>Web UI update</strong></h2>
             </div>
 </div>
 </a>
-<a aria-label="Next: keyboard" class="md-footer__link md-footer__link--next" href="../hid/" rel="next">
+<a aria-label="Next: Keyboard" class="md-footer__link md-footer__link--next" href="../hid/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              keyboard
+              Keyboard
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/usb-splitter-guide/index.html b/generated/en/usb-splitter-guide/index.html
index 0cd89d5f..a9da541f 100644
--- a/generated/en/usb-splitter-guide/index.html
+++ b/generated/en/usb-splitter-guide/index.html
@@ -9,7 +9,7 @@
 <meta content="Thomas Von" name="author"/>
 <link href="../assets/images/favicon.png" rel="icon"/>
 <meta content="mkdocs-1.4.2, mkdocs-material-8.5.10" name="generator"/>
-<title>USB splitter - BliKVM Handbook</title>
+<title>USB Splitter - BliKVM Handbook</title>
 <link href="../assets/stylesheets/main.472b142f.min.css" rel="stylesheet"/>
 <link href="../assets/stylesheets/palette.08040f6c.min.css" rel="stylesheet"/>
 <style>:root{--md-admonition-icon--note:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 7.775V2.75a.25.25 0 0 1 .25-.25h5.025a.25.25 0 0 1 .177.073l6.25 6.25a.25.25 0 0 1 0 .354l-5.025 5.025a.25.25 0 0 1-.354 0l-6.25-6.25a.25.25 0 0 1-.073-.177zm-1.5 0V2.75C1 1.784 1.784 1 2.75 1h5.025c.464 0 .91.184 1.238.513l6.25 6.25a1.75 1.75 0 0 1 0 2.474l-5.026 5.026a1.75 1.75 0 0 1-2.474 0l-6.25-6.25A1.75 1.75 0 0 1 1 7.775zM6 5a1 1 0 1 0 0 2 1 1 0 0 0 0-2z"/></svg>');--md-admonition-icon--abstract:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M2.5 1.75a.25.25 0 0 1 .25-.25h8.5a.25.25 0 0 1 .25.25v7.736a.75.75 0 1 0 1.5 0V1.75A1.75 1.75 0 0 0 11.25 0h-8.5A1.75 1.75 0 0 0 1 1.75v11.5c0 .966.784 1.75 1.75 1.75h3.17a.75.75 0 0 0 0-1.5H2.75a.25.25 0 0 1-.25-.25V1.75zM4.75 4a.75.75 0 0 0 0 1.5h4.5a.75.75 0 0 0 0-1.5h-4.5zM4 7.75A.75.75 0 0 1 4.75 7h2a.75.75 0 0 1 0 1.5h-2A.75.75 0 0 1 4 7.75zm11.774 3.537a.75.75 0 0 0-1.048-1.074L10.7 14.145 9.281 12.72a.75.75 0 0 0-1.062 1.058l1.943 1.95a.75.75 0 0 0 1.055.008l4.557-4.45z"/></svg>');--md-admonition-icon--info:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm6.5-.25A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75zM8 6a1 1 0 1 0 0-2 1 1 0 0 0 0 2z"/></svg>');--md-admonition-icon--tip:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.499.75a.75.75 0 0 1 1.5 0v.996C5.9 2.903 6.793 3.65 7.662 4.376l.24.202c-.036-.694.055-1.422.426-2.163C9.1.873 10.794-.045 12.622.26 14.408.558 16 1.94 16 4.25c0 1.278-.954 2.575-2.44 2.734l.146.508.065.22c.203.701.412 1.455.476 2.226.142 1.707-.4 3.03-1.487 3.898C11.714 14.671 10.27 15 8.75 15h-6a.75.75 0 0 1 0-1.5h1.376a4.489 4.489 0 0 1-.563-1.191 3.833 3.833 0 0 1-.05-2.063 4.636 4.636 0 0 1-2.025-.293.75.75 0 1 1 .525-1.406c1.357.507 2.376-.006 2.698-.318l.009-.01a.748.748 0 0 1 1.06 0 .75.75 0 0 1-.012 1.074c-.912.92-.992 1.835-.768 2.586.221.74.745 1.337 1.196 1.621H8.75c1.343 0 2.398-.296 3.074-.836.635-.507 1.036-1.31.928-2.602-.05-.603-.216-1.224-.422-1.93l-.064-.221c-.12-.407-.246-.84-.353-1.29a2.404 2.404 0 0 1-.507-.441 3.063 3.063 0 0 1-.633-1.248.75.75 0 0 1 1.455-.364c.046.185.144.436.31.627.146.168.353.305.712.305.738 0 1.25-.615 1.25-1.25 0-1.47-.95-2.315-2.123-2.51-1.172-.196-2.227.387-2.706 1.345-.46.92-.27 1.774.019 3.062l.042.19a.753.753 0 0 1 .01.05c.348.443.666.949.94 1.553a.75.75 0 1 1-1.365.62c-.553-1.217-1.32-1.94-2.3-2.768a85.08 85.08 0 0 0-.317-.265c-.814-.68-1.75-1.462-2.692-2.619a3.74 3.74 0 0 0-1.023.88c-.406.495-.663 1.036-.722 1.508.116.122.306.21.591.239.388.038.797-.06 1.032-.19a.75.75 0 0 1 .728 1.31c-.515.287-1.23.439-1.906.373-.682-.067-1.473-.38-1.879-1.193L.75 5.677V5.5c0-.984.48-1.94 1.077-2.664.46-.559 1.05-1.055 1.673-1.353V.75z"/></svg>');--md-admonition-icon--success:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M13.78 4.22a.75.75 0 0 1 0 1.06l-7.25 7.25a.75.75 0 0 1-1.06 0L2.22 9.28a.75.75 0 0 1 1.06-1.06L6 10.94l6.72-6.72a.75.75 0 0 1 1.06 0z"/></svg>');--md-admonition-icon--question:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 1.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13zM0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm9 3a1 1 0 1 1-2 0 1 1 0 0 1 2 0zM6.92 6.085c.081-.16.19-.299.34-.398.145-.097.371-.187.74-.187.28 0 .553.087.738.225A.613.613 0 0 1 9 6.25c0 .177-.04.264-.077.318a.956.956 0 0 1-.277.245c-.076.051-.158.1-.258.161l-.007.004a7.728 7.728 0 0 0-.313.195 2.416 2.416 0 0 0-.692.661.75.75 0 0 0 1.248.832.956.956 0 0 1 .276-.245 6.3 6.3 0 0 1 .26-.16l.006-.004c.093-.057.204-.123.313-.195.222-.149.487-.355.692-.662.214-.32.329-.702.329-1.15 0-.76-.36-1.348-.863-1.725A2.76 2.76 0 0 0 8 4c-.631 0-1.155.16-1.572.438-.413.276-.68.638-.849.977a.75.75 0 1 0 1.342.67z"/></svg>');--md-admonition-icon--warning:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.22 1.754a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368L8.22 1.754zm-1.763-.707c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575L6.457 1.047zM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0zm-.25-5.25a.75.75 0 0 0-1.5 0v2.5a.75.75 0 0 0 1.5 0v-2.5z"/></svg>');--md-admonition-icon--failure:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M3.404 12.596a6.5 6.5 0 1 1 9.192-9.192 6.5 6.5 0 0 1-9.192 9.192zM2.344 2.343a8 8 0 1 0 11.313 11.314A8 8 0 0 0 2.343 2.343zM6.03 4.97a.75.75 0 0 0-1.06 1.06L6.94 8 4.97 9.97a.75.75 0 1 0 1.06 1.06L8 9.06l1.97 1.97a.75.75 0 1 0 1.06-1.06L9.06 8l1.97-1.97a.75.75 0 1 0-1.06-1.06L8 6.94 6.03 4.97z"/></svg>');--md-admonition-icon--danger:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M10.561 1.5a.016.016 0 0 0-.01.004L3.286 8.571A.25.25 0 0 0 3.462 9H6.75a.75.75 0 0 1 .694 1.034l-1.713 4.188 6.982-6.793A.25.25 0 0 0 12.538 7H9.25a.75.75 0 0 1-.683-1.06l2.008-4.418.003-.006a.02.02 0 0 0-.004-.009.02.02 0 0 0-.006-.006L10.56 1.5zM9.504.43a1.516 1.516 0 0 1 2.437 1.713L10.415 5.5h2.123c1.57 0 2.346 1.909 1.22 3.004l-7.34 7.142a1.25 1.25 0 0 1-.871.354h-.302a1.25 1.25 0 0 1-1.157-1.723L5.633 10.5H3.462c-1.57 0-2.346-1.909-1.22-3.004L9.503.429z"/></svg>');--md-admonition-icon--bug:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M4.72.22a.75.75 0 0 1 1.06 0l1 .999a3.492 3.492 0 0 1 2.441 0l.999-1a.75.75 0 1 1 1.06 1.061l-.775.776c.616.63.995 1.493.995 2.444v.327c0 .1-.009.197-.025.292.408.14.764.392 1.029.722l1.968-.787a.75.75 0 0 1 .556 1.392L13 7.258V9h2.25a.75.75 0 0 1 0 1.5H13v.5c0 .409-.049.806-.141 1.186l2.17.868a.75.75 0 0 1-.557 1.392l-2.184-.873A4.997 4.997 0 0 1 8 16a4.997 4.997 0 0 1-4.288-2.427l-2.183.873a.75.75 0 0 1-.558-1.392l2.17-.868A5.013 5.013 0 0 1 3 11v-.5H.75a.75.75 0 0 1 0-1.5H3V7.258L.971 6.446a.75.75 0 0 1 .558-1.392l1.967.787c.265-.33.62-.583 1.03-.722a1.684 1.684 0 0 1-.026-.292V4.5c0-.951.38-1.814.995-2.444L4.72 1.28a.75.75 0 0 1 0-1.06zM6.173 5h3.654A.173.173 0 0 0 10 4.827V4.5a2 2 0 1 0-4 0v.327c0 .096.077.173.173.173zM5.25 6.5a.75.75 0 0 0-.75.75V11a3.5 3.5 0 1 0 7 0V7.25a.75.75 0 0 0-.75-.75h-5.5z"/></svg>');--md-admonition-icon--example:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M5 5.782V2.5h-.25a.75.75 0 0 1 0-1.5h6.5a.75.75 0 0 1 0 1.5H11v3.282l3.666 5.76C15.619 13.04 14.543 15 12.767 15H3.233c-1.776 0-2.852-1.96-1.899-3.458L5 5.782zM9.5 2.5h-3V6a.75.75 0 0 1-.117.403L4.73 9h6.54L9.617 6.403A.75.75 0 0 1 9.5 6V2.5zm-6.9 9.847L3.775 10.5h8.45l1.175 1.847a.75.75 0 0 1-.633 1.153H3.233a.75.75 0 0 1-.633-1.153z"/></svg>');--md-admonition-icon--quote:url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M1.75 2.5a.75.75 0 0 0 0 1.5h10.5a.75.75 0 0 0 0-1.5H1.75zm4 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zm0 5a.75.75 0 0 0 0 1.5h8.5a.75.75 0 0 0 0-1.5h-8.5zM2.5 7.75a.75.75 0 0 0-1.5 0v6a.75.75 0 0 0 1.5 0v-6z"/></svg>');}</style>
@@ -58,7 +58,7 @@
 <div class="md-header__topic" data-md-component="header-topic">
 <span class="md-ellipsis">
             
-              USB splitter
+              USB Splitter
             
           </span>
 </div>
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -266,7 +266,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -276,12 +276,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -296,7 +296,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -346,7 +346,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -357,11 +357,11 @@
 <li class="md-nav__item md-nav__item--active">
 <input class="md-nav__toggle md-toggle" data-md-toggle="toc" id="__toc" type="checkbox"/>
 <label class="md-nav__link md-nav__link--active" for="__toc">
-          USB splitter
+          USB Splitter
           <span class="md-nav__icon md-icon"></span>
 </label>
 <a class="md-nav__link md-nav__link--active" href="./">
-        USB splitter
+        USB Splitter
       </a>
 <nav aria-label="Table of contents" class="md-nav md-nav--secondary">
 <label class="md-nav__title" for="__toc">
@@ -394,7 +394,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -403,28 +403,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
@@ -577,13 +577,13 @@ <h2 id="43d-printable-case"><strong>4.3D printable case</strong></h2>
             </div>
 </div>
 </a>
-<a aria-label="Next: Multiport KVM over IP" class="md-footer__link md-footer__link--next" href="../switch-guide/" rel="next">
+<a aria-label="Next: Multiport KVM-over-IP" class="md-footer__link md-footer__link--next" href="../switch-guide/" rel="next">
 <div class="md-footer__title">
 <div class="md-ellipsis">
 <span class="md-footer__direction">
                 Next
               </span>
-              Multiport KVM over IP
+              Multiport KVM-over-IP
             </div>
 </div>
 <div class="md-footer__button md-icon">
diff --git a/generated/en/wifi/index.html b/generated/en/wifi/index.html
index 76de264d..9d771ff0 100644
--- a/generated/en/wifi/index.html
+++ b/generated/en/wifi/index.html
@@ -201,7 +201,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../first_steps/">
-        First steps
+        First Steps
       </a>
 </li>
 <li class="md-nav__item">
@@ -226,7 +226,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../port-forwarding/">
-        Port forwarding
+        Port Forwarding
       </a>
 </li>
 <li class="md-nav__item">
@@ -289,7 +289,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../hid/">
-        keyboard
+        Keyboard
       </a>
 </li>
 <li class="md-nav__item">
@@ -299,12 +299,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../flashing_os/">
-        Flasing OS
+        Flashing OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../OLED-display/">
-        OLED display
+        OLED Display
       </a>
 </li>
 <li class="md-nav__item">
@@ -319,7 +319,7 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../msd/">
-        USB flash Drive
+        MSD
       </a>
 </li>
 <li class="md-nav__item">
@@ -369,7 +369,7 @@
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../atx-guide/">
-        ATX guide
+        ATX Guide
       </a>
 </li>
 <li class="md-nav__item">
@@ -379,12 +379,12 @@
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../usb-splitter-guide/">
-        USB splitter
+        USB Splitter
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../switch-guide/">
-        Multiport KVM over IP
+        Multiport KVM-over-IP
       </a>
 </li>
 </ul>
@@ -393,28 +393,28 @@
 <li class="md-nav__item md-nav__item--section md-nav__item--nested">
 <input checked="" class="md-nav__toggle md-toggle md-toggle--indeterminate" data-md-toggle="__nav_6" id="__nav_6" type="checkbox"/>
 <label class="md-nav__link" for="__nav_6">
-          development
+          Development
           <span class="md-nav__icon md-icon"></span>
 </label>
-<nav aria-label="development" class="md-nav" data-md-level="1">
+<nav aria-label="Development" class="md-nav" data-md-level="1">
 <label class="md-nav__title" for="__nav_6">
 <span class="md-nav__icon md-icon"></span>
-          development
+          Development
         </label>
 <ul class="md-nav__list" data-md-scrollfix="">
 <li class="md-nav__item">
 <a class="md-nav__link" href="../make-image/">
-        make image
+        Make Image
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../modify_pikvm_image/">
-        config for PiKVM OS
+        Config for PiKVM OS
       </a>
 </li>
 <li class="md-nav__item">
 <a class="md-nav__link" href="../Dev-BliKVM-v4-Allwinner/">
-        v4 dev guide
+        v4 Allwinner Dev Guide
       </a>
 </li>
 </ul>
diff --git a/generated/ja/sitemap.xml b/generated/ja/sitemap.xml
index f14b89a2..9c1ea7e9 100644
--- a/generated/ja/sitemap.xml
+++ b/generated/ja/sitemap.xml
@@ -2,67 +2,67 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
 </urlset>
\ No newline at end of file
diff --git a/generated/ja/sitemap.xml.gz b/generated/ja/sitemap.xml.gz
index 8743f2a4..967a8cc0 100644
Binary files a/generated/ja/sitemap.xml.gz and b/generated/ja/sitemap.xml.gz differ
diff --git a/generated/ru/sitemap.xml b/generated/ru/sitemap.xml
index a7ef0102..947c9c51 100644
--- a/generated/ru/sitemap.xml
+++ b/generated/ru/sitemap.xml
@@ -2,57 +2,57 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
 </urlset>
\ No newline at end of file
diff --git a/generated/ru/sitemap.xml.gz b/generated/ru/sitemap.xml.gz
index 5d84ba02..dc163ece 100644
Binary files a/generated/ru/sitemap.xml.gz and b/generated/ru/sitemap.xml.gz differ
diff --git a/generated/zh/sitemap.xml b/generated/zh/sitemap.xml
index 41aeb4aa..187c358e 100644
--- a/generated/zh/sitemap.xml
+++ b/generated/zh/sitemap.xml
@@ -2,157 +2,157 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-08-13</lastmod>
+         <lastmod>2023-08-14</lastmod>
          <changefreq>daily</changefreq>
     </url>
 </urlset>
\ No newline at end of file
diff --git a/generated/zh/sitemap.xml.gz b/generated/zh/sitemap.xml.gz
index f500220c..e3d8bfcd 100644
Binary files a/generated/zh/sitemap.xml.gz and b/generated/zh/sitemap.xml.gz differ