# K801 / K802 / K803 / K804

## <mark style="color:blue;">1- Product Overview</mark>

### <mark style="color:blue;">1.1- Introduction</mark>

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F6tgsJrXjeQFwLc0XquzU%2F1.png?alt=media)

### <mark style="color:blue;">1.2- Safety</mark> <a href="#mmm6g67oklt6" id="mmm6g67oklt6"></a>

<details>

<summary><mark style="color:blue;">Safety Precautions, Safeguards &#x26; Information</mark></summary>

**Safe use and installation instructions**

1. Install the device securely. Be careful handling the device to prevent injury and do not drop.
2. Equipment is intended for installation in Restricted Access Area.
3. To protect against excessive RF exposure, maintain at least 20cm from any user and the RF antennas. Only use provided dual band antennas of 2dBi/2dBi gain.
4. Wall or ceiling mounting device requires use of a mounting plate or bracket. The plate or bracket must be of metal construction and have a minimum thickness of 1mm.
5. Use M4x0.5mm Flat Head screws to attach mounting plate or mounting brackets to threaded holes on bottom or rear of chassis. Screws should be a minimum length of 4mm. Add 1mm of screw length for every mm of additional thickness of plate or bracket beyond 1.5mm.
6. Safe operating temperature and non-condensing humidity ratings must be adhered to, please refer to the specifications table for safe operating temperature and humidity ratings.
7. Safe Storage temperature must be adhered to, please refer to the specifications table for safe storage temperature ratings.
8. Keep the device away from liquids and flammable materials.
9. Do not clean the device with liquids. The chassis can be cleaned with a cloth.
10. Allow at least 2 inches of space around all sides of the device for proper cooling. If the device is mounted to a vertical surface then recommended device orientation is so that heatsink fins allow air to rise unobstructed. Alternative orientations may result in reduced operational temperature range.
11. This device is intended for indoor operation only.
12. Use UL Listed external power supply with rated output 24-36Vdc.
13. Wiring methods used for the connection of the equipment to the mains supply shall be in accordance with the National Electrical Code, NFPA 70, and the Canadian Electrical Code, Part I, CSA C22.1.
14. Allow ample space for terminal block wiring connections such that the wires do not bend and are protected from accidental damage.
15. Install the device only with shielded network cables.
16. Only use SAE approved cables for automotive installation.
17. The installer should be experienced in aftermarket installation and familiar with general practices for installing electronics devices in vehicles.
18. The device should not be installed in the driver’s area of a vehicle.
19. The device should be mounted in accordance with accepted aftermarket practices and materials for vehicle installation.
20. Only use UL Listed connectors for connection to automotive fuse panels.
21. Radio device is not intended for emergency service use.
22. Service and repair of the device must be done by qualified service personnel. This includes, but is not limited to, replacement of the CMOS battery. Replacement CMOS battery must be of the same type as the original.
23. Proper disposal of CMOS battery must comply with local governance.
24. Product must only be connected to a certified router, switch or similar network equipment
25. Product is intended for indoor use only.
26. Product cannot be connected to the public network.\\

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FyM2HghEySsZ1jjQAv76A%2Fimage.png?alt=media\&token=ce687720-8f80-4f95-850c-5a37a3ac94de)**WARNING:** There is danger of explosion if the CMOS battery is replaced incorrectly. Disposal of battery into fire or a hot oven, or mechanically crushing or cutting of a battery can result in an explosion.

</details>

<details>

<summary><mark style="color:blue;">Précautions et guide d’installation</mark></summary>

Ne pas ouvrir ou modifier l'appareil. L'appareil utilise des composants conformes aux réglementations FCC et EC. La modification de l'appareil peut annuler ces certifications.

1. Installez l'appareil en toute sécurité. Manipulez l'appareil avec précaution pour éviter de vous blesser et ne le laissez pas tomber.
2. L'équipement est destiné à être installé dans une zone à accès restreint
3. Pour vous protéger contre une exposition RF excessive, maintenez au moins 20 cm de tout utilisateur et des antennes RF. Utilisez uniquement les antennes double bande fournies avec un gain de 2 dBi/2 dBi.
4. Le dispositif de montage au mur ou au plafond nécessite l'utilisation d'une plaque ou d'un support de montage. La plaque ou le support doit être en métal et avoir une épaisseur minimale de 1 mm.
5. Utilisez des vis à tête plate M4x0,5 mm pour fixer la plaque de montage ou les supports de montage aux trous filetés au bas ou à l'arrière du châssis. Les vis doivent avoir une longueur minimale de 4 mm. Ajoutez 1 mm de longueur de vis pour chaque mm d'épaisseur supplémentaire de plaque ou de support au-delà de 1,5 mm.
6. La température ambiante de fonctionnement doit être comprise entre 0 °C et 45 °C avec une humidité relative sans condensation de 10 à 90 %.
7. L'appareil peut être stocké à des températures comprises entre -10 °C et 85 °C.
8. Gardez l'appareil à l'écart des liquides et des matériaux inflammables.
9. Ne nettoyez pas l'appareil avec des liquides. Le châssis peut être nettoyé avec un chiffon.
10. Laissez au moins 2 pouces d'espace autour de tous les côtés de l'appareil pour un refroidissement correct. Si l'appareil est monté sur une surface verticale, l'orientation recommandée de l'appareil est de sorte que les ailettes du dissipateur thermique permettent à l'air de monter sans obstruction. Des orientations alternatives peuvent entraîner une plage de températures de fonctionnement réduite..
11. Cet appareil est destiné à une utilisation en intérieur uniquement.
12. Utilisez une alimentation externe homologuée UL avec une sortie nominale de 24 à 36 Vdc.
13. Les méthodes de câblage utilisées pour le raccordement de l'équipement à l'alimentation secteur doivent être conformes au Code national de l'électricité, NFPA 70, et au Code canadien de l'électricité, Partie I, CSA C22.1.
14. Prévoyez suffisamment d'espace pour les connexions de câblage du bornier afin que les fils ne se plient pas et soient protégés contre les dommages accidentels.
15. Installez l'appareil uniquement avec des câbles réseau blindés.
16. Utilisez uniquement des câbles approuvés par SAE pour une installation automobile.
17. L'installateur doit avoir de l'expérience dans l'installation du marché secondaire et être familiarisé avec les pratiques générales d'installation d'appareils électroniques dans les véhicules.
18. L'appareil ne doit pas être installé dans le poste de conduite d'un véhicule.
19. L'appareil doit être monté conformément aux pratiques acceptées du marché secondaire et aux matériaux d'installation du véhicule.
20. Utilisez uniquement des connecteurs répertoriés UL pour la connexion aux panneaux de fusibles automobiles.
21. L'appareil radio n'est pas destiné aux services d'urgence.
22. L'entretien et la réparation de l'appareil doivent être effectués par un personnel qualifié. Cela inclut, mais sans s'y limiter, le remplacement de la batterie CMOS. La batterie CMOS de remplacement doit être du même type que celle d'origine.
23. L'élimination appropriée de la batterie CMOS doit être conforme à la gouvernance locale.
24. Le produit doit uniquement être connecté à un commutateur de routeur.
25. Le produit est destiné à une utilisation en intérieur uniquement.
26. Le produit ne peut pas être connecté au réseau public.

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FjlkL6VfACtMElAeJofMX%2Fimage.png?alt=media\&token=a04e65fc-80cd-429e-9840-832672a08f09)**ATTENTION:** Il existe un risque d'explosion si la pile CMOS n'est pas remplacée correctement. L'élimination de la batterie dans le feu ou dans un four chaud, ou l'écrasement ou le découpage mécanique d'une batterie peut entraîner une explosion.

</details>

<details>

<summary><mark style="color:blue;">安全使用和安裝說明</mark></summary>

請勿打開或修改設備。 該設備使用符合FCC和CE法規的組件。 修改設備可能會使這些認證無效。

牢固地安裝設備。 小心處理設備以防止受傷，不要跌落。

設備旨在安裝在受限訪問區域。

為防止過度暴露於射頻，請與任何用戶和射頻天線保持至少 20 厘米的距離。 僅使用提供的 2dBi/2dBi 增益的雙頻天線。

牆壁或天花板安裝設備需要使用安裝板或支架。 板或支架必須是金屬結構，並且最小厚度為 1 毫米。

使用 M4x0.5mm 平頭螺釘將安裝板或安裝支架連接到機箱底部或後部的螺紋孔。 螺釘的最小長度應為 4 毫米。 超過 1.5mm 的板或支架每增加 1mm 的厚度，就增加 1mm 的螺釘長度。

環境工作溫度必須在 0 °C 至 45 °C 之間，非冷凝相對濕度為 10-90%。

該設備可在 -10 °C 至 85 °C 的溫度下儲存。

使設備遠離液體和易燃材料。

請勿使用液體清潔設備。 機箱可以用布清潔。

在設備四周留出至少 2 英寸的空間，以便適當冷卻。 如果設備安裝在垂直表面上，則推薦的設備方向是散熱片允許空氣暢通無阻地上升。 替代方向可能會導致工作溫度範圍減小。

該設備僅適用於室內操作。

使用額定輸出為 24-36Vdc 的 UL 認證外部電源。

用於將設備連接到主電源的接線方法應符合國家電氣規範 NFPA 70 和加拿大電氣規範第 I 部分 CSA C22.1。

為端子塊接線連接留出足夠的空間，以使電線不會彎曲並防止意外損壞。

僅使用屏蔽網線安裝設備。

僅使用 SAE 批准的電纜進行汽車安裝。

安裝人員應具有售後安裝經驗並熟悉在車輛中安裝電子設備的一般做法。

該設備不應安裝在車輛的駕駛員區域。

該設備應按照公認的售後市場慣例和車輛安裝材料進行安裝。

僅使用 UL 列名的連接器連接汽車保險絲板。

無線電設備不適用於緊急服務。

設備的維護和修理必須由合格的服務人員進行。 這包括但不限於更換 CMOS 電池。 更換的 CMOS 電池必須與原裝電池的類型相同。

CMOS 電池的正確處置必須遵守當地的管理規定。

產品只能連接到路由器交換機。

產品僅供室內使用。

產品無法連接到公共網絡。

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FVy7LoVep3QqqR9UbZEw2%2Fimage.png?alt=media\&token=ff965ffb-98d6-47a4-a1b1-015684336625)**警告**：如果 CMOS 電池更換不正確，有爆炸的危險。 將電池丟入火中或熱烘箱中，或以機械方式壓碎或切割電池都可能導致爆炸。

**警語（本體及說明書）：須以中文標示。**

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FjOjWll4inTorcEAHpaLm%2Fimage.png?alt=media&#x26;token=df9b6b4a-5cdc-4f65-916a-f91f72c688fe" alt=""><figcaption></figcaption></figure>

</details>

### <mark style="color:blue;">1.3- Box Contents & Accessories</mark> <a href="#mmm6g67oklt6" id="mmm6g67oklt6"></a>

* 5-pin Power Terminal Block Connector (Dinkle 2ESDVM-05P)
* 20-pin DIO/CAN/SW Terminal Block Connector (Dinkle 0159-0320)
* SATA Power and Data Cables if not installed (OnLogic CBD123)

If you purchased additional items such as mounting brackets, power supplies or antennas, they will be located in the system box or within the outer shipping carton.

For more information on accessories and additional features, visit the Karbon 800 pages at:

US

<https://www.onlogic.com/k801/>

<https://www.onlogic.com/k802/>

<https://www.onlogic.com/k803/>

<https://www.onlogic.com/k804/>

EU

<https://www.onlogic.com/eu-en/k801/>

<https://www.onlogic.com/eu-en/k802/>

<https://www.onlogic.com/eu-en/k803/>

<https://www.onlogic.com/eu-en/k804/>

### <mark style="color:blue;">1.4- Product Specifications</mark> <a href="#jddbzfth62sn" id="jddbzfth62sn"></a>

<table><thead><tr><th width="183.5999755859375">Feature</th><th>Details</th></tr></thead><tbody><tr><td>Variants</td><td><p>K801 - High-Performance Rugged Low-Profile Computer</p><p>K802 - High-Performance Rugged Computer w/ModBay</p><p>K803 - High-Performance Rugged Computer w/PCIe</p><p>K804 - High-Performance Rugged Computer w/ModBay &#x26; PCIe</p></td></tr><tr><td>Processor</td><td><p>Intel 12th Gen Alder Lake-S (LGA1700)</p><p>Core i3, i5, i7 &#x26; i9 up to 16-core 24-thread</p></td></tr><tr><td>Memory</td><td>2x DDR4-2666 SO-DIMM up to 64GB total (non-ECC or ECC)</td></tr><tr><td>Chipset</td><td>Intel W680</td></tr><tr><td>Integrated Graphics</td><td>Intel UHD Graphics 730 (i3) or 770 (i5, i7, i9)</td></tr><tr><td>Front I/O</td><td><p>4x USB 3.2 Gen 2 Type-A 2xM2.5x0.45 threaded hole</p><p>2x Serial RS-232/422/485</p><p>20-pin GPIO terminal block (DIO, CAN bus, Ext. switch)</p><p>1x 3.5 mm audio jack</p><p>2x 3FF Mini-SIM slots</p><p>1x External fan connector</p><p>2x Hot-swap drive bays (optional, K802 &#x26; K804)</p><p>8x Status LEDs</p><p>1x Power button</p></td></tr><tr><td>Back I/O</td><td><p>2x or 6x 2.5 GbE LAN (optional 2x PoE)</p><p>2x USB 3.2 Gen 2 Type-A with 1x M2.5x0.45 threaded hole</p><p>2x DisplayPort (full-size, DP 1.4, DP++, HDMI 1.4)</p><p>2x ModBay expansion slots (K802 &#x26; K804)</p><p>5-pin Power input</p></td></tr><tr><td>Expansion &#x26; Storage</td><td><p>1x M.2 2280 M-key (PCIe Gen 4 x4)</p><p>1x M.2 2280 M-key (PCIe Gen 4 x4, SATA)</p><p>1x M.2 3042/3052/2280 B-key (PCIe x2, SATA, USB 3.0, USB 2.0)</p><p>1x M.2 2230 E-key (Wi-Fi) (PCIe x1, USB 2.0)</p><p>1x mPCIe (PCIe x1, USB 2.0)</p><p>1x PCIe Gen 4 x16 slot (K803 &#x26; K804)</p><p>2x 2.5" SATA SSD/HDD drives 0-15mm max (hot-swap optional, 7-9.5mm max) (1x K803, 2x K802 &#x26; K804)</p><p>K804 Options:</p><p>1) 1x PCIe x16 in x16 PCIe slot with dual slot height (4.4" H x 9.5" L)</p><p>2) 2x PCIe x16 (8 lanes each) with single slot height (4.4" H x 9.5" L)</p><p>K803:</p><p>1x PCIe x16 in x16 PCIe slot with single slot height (4.4" H x 9.5" L)</p></td></tr><tr><td>Special Features</td><td><p>User-Programmable OnLogic Microcontroller (MCU)</p><p>Automotive Ignition Power Sensing</p><p>Optional TPM 2.0 module (Nuvoton NPCT750)</p></td></tr><tr><td>Operating Systems</td><td>Windows 11</td></tr><tr><td>LAN Controllers</td><td><p>1x Intel I225-LM with AMT support</p><p>1x or 5x Intel I225-IT</p></td></tr><tr><td>Voltage Input</td><td>12 ~ 48V DC up to 30A (19 ~ 48V DC with PCIe expansion over 75W)</td></tr><tr><td>Dimensions</td><td><p>K801 = 240 x 60 x 267mm (9.45 x 2.36 x 10.51")</p><p>K802 &#x26; K803 = 240 x 82 x 267mm (9.45 x 3.23 x 10.51")</p><p>K804 = 240 x 143 x 267mm (9.45 x 5.63 x 10.51")</p></td></tr><tr><td>Mounting</td><td><p>Wall Mount</p><p>Wall Mount with Vibration Isolation</p><p>DIN Rail Mount</p></td></tr><tr><td>Operating Temperature</td><td><p>-40°C ~ 70°C (35W TDP CPU)</p><p>-40°C ~ 50°C (65W TDP CPU)</p></td></tr><tr><td>Storage Temperature</td><td>-40°C ~ 85°C</td></tr><tr><td>Operating Humidity</td><td>10~95% relative, non-condensing</td></tr><tr><td>Storage Humidity</td><td>0~95% relative, non-condensing</td></tr><tr><td>Shock &#x26; Vibration</td><td><p>Shock: Tested according to IEC 60068-2-27 and MIL-STD-810H</p><p>Vibration: Tested according to IEC 60068-2-64 and MIL-STD-810H</p></td></tr></tbody></table>

| <img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FzdIfkWMJALkWlFZoMOBX%2Fimage.png?alt=media&#x26;token=5d0360ba-65b4-4aea-bec1-baa6929d03d8" alt="" data-size="original"> | FCC 47 CFR Part 15 Subpart B (Class A)                                                                                      |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| <img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F90RiYrTqLB8O3u5RJcEH%2Fimage.png?alt=media&#x26;token=911643df-ab4a-4fef-8095-78dbdfc01455" alt="" data-size="original"> | <p>EN 60950-1 & EN 62368-1</p><p>CISPR 32/EN 55032</p><p>CISPR 35/EN 55035</p><p>Radio Equipment Directive (2014/53/EU)</p> |
| <img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FZbmsi1jiEr29eDyrF4aN%2Fimage.png?alt=media&#x26;token=1c2564e7-8ad3-45f2-8e61-b6a8dae5b912" alt="" data-size="original"> | RoHS 3 (2015/863/EU)                                                                                                        |
| <img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FR1NCrofmNOynx2SkSiMX%2Fimage.png?alt=media&#x26;token=b1538526-82f1-4fc4-8e29-0fd03e487a1a" alt="" data-size="original"> | WEEE Directive (2012/19/EU)                                                                                                 |
| <img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FGKo7EiJBrcbvgEhDoU9i%2Fimage.png?alt=media&#x26;token=d285df2a-befa-48da-b225-b877ab69f948" alt="" data-size="original"> | <p>IEC 60068-2-27</p><p>IEC 60068-2-64</p><p>MIL-STD-810H</p>                                                               |
| <img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fi8VCn7P5q4aYiAZyUFEL%2Fimage.png?alt=media&#x26;token=50b7367b-329f-4bf3-a607-a7248d1397ba" alt="" data-size="original"> | Power Immunity According to E-Mark ISO 7637-2 & ISO 16750-2                                                                 |
| <img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F9IosejMUrjeq7lvuujQB%2Fimage.png?alt=media&#x26;token=2111ec81-9b3c-46f7-8ce7-09d40b4afaa9" alt="" data-size="original"> | EN 50121-3-2                                                                                                                |
| <img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FHXpgMdoY8HF8Y98DJn6o%2Fimage.png?alt=media&#x26;token=b7750f97-3f8c-4563-8c7b-57147439ef82" alt="" data-size="original"> | IEC 60601-1-2, 4th ed.                                                                                                      |
| <img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FlIq7kz7rbhCJFmjp27Sg%2Fimage.png?alt=media&#x26;token=a7758ac7-9a51-4fd7-9308-a2fddcf6cad1" alt="" data-size="original"> | EN 60945, 4th ed.                                                                                                           |

## <mark style="color:blue;">2- Technical Specifications</mark>

### <mark style="color:blue;">2.1- External Features</mark> <a href="#id-3asmuz5yourf" id="id-3asmuz5yourf"></a>

#### <mark style="color:blue;">Front I/O Definition</mark> <a href="#owitqzrk38aq" id="owitqzrk38aq"></a>

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FHcZQYK6E404T85qtWWEb%2F11.jpeg?alt=media)

#### <mark style="color:blue;">Rear I/O Definition</mark> <a href="#ws5o27uiefsa" id="ws5o27uiefsa"></a>

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FI4tlf659d8GNxUKf13NH%2F12.png?alt=media)

#### <mark style="color:blue;">Serial Ports</mark> <a href="#m8q5r5wh8x92" id="m8q5r5wh8x92"></a>

The serial ports on the Karbon 800 series motherboard support RS-232, RS-422 Full-Duplex, and RS-485 half-Duplex configurations. The serial port communication mode can be selected in the BIOS configuration. In addition, 5V & 12V power can be enabled on pin 9 in the same BIOS menu. Pin 9 is rated to provide 250mA of current. Refer to the [BIOS manual](https://support.onlogic.com/product-documentation/rugged-products/karbon-k800-series/k800-bios-manual) for configuration instructions.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FVU6Es0MluOh8IwtImNlR%2Fimage.png?alt=media&#x26;token=a26e6f5f-6adc-4778-bdbe-d07027351583" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">Modbay Expansion</mark> <a href="#hze87psvggh3" id="hze87psvggh3"></a>

**The Karbon 800 series K802 and K804 models feature two Modbay expansion slots. Each slot supports PCIe Gen 3 x2, USB 3.1 Gen 2, and USB 2.0. OnLogic offers a variety of ModBay cards including RJ45 LAN or PoE, M12 LAN or PoE, USB 3, and a carrier card with two additional mPCIe slots (1x PCIe x1 + USB 2.0 and 1x USB 2.0 + SMBUS).**

#### <mark style="color:blue;">DIO, CAN, Ext. Power Switch</mark> <a href="#vrgzxuccw51a" id="vrgzxuccw51a"></a>

The Karbon 800 series 20-Pin header provides the following interfaces: 8-bit (4-in, 4-out) Digital Input Output (DIO) or General Purpose Input Output (GPIO) with optically isolated terminals, one CAN bus connection, and an optional external power switch connection.

The DIO is optically isolated, meaning that the terminal is separated from other motherboard features for protection. The DIO terminal requires external power from a 5\~48V DC source through Pin 20 with GND to Pin 19 in order to function.

The Isolated Power Supply (ISO PSU) can be a voltage source from 5\~48V to interface with external digital IO. The maximum power draw from the supply should not exceed 0.6A under normal operating conditions. Individual DOut pins will be damaged by loads in excess of 150mA. The ISO PSU must be a DC Limited Power Source (LPS) power supply.

Mating power switch cables should be a twisted-pair wire with floating shield to assure proper immunity to EMI/RFI. It is recommended to keep wires at less than 3 meters in length. Any remote power switch connected between pins 1 and 2 should be momentary contact type only.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FWh8njV4OMZQRn0sNHzjg%2Fimage.png?alt=media&#x26;token=085ffb3b-0a52-4a50-b122-ab830aed7dba" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">DIO Connection Diagram</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FpnpcwRIjCkTGn8Md8MF1%2Fimage.png?alt=media&#x26;token=f7a8c598-81e1-4c67-ac0b-c6af05a93206" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">Status LEDs</mark> <a href="#w3gch2dbk74w" id="w3gch2dbk74w"></a>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F3aokppf0TzRQO0uQ3GDQ%2Fimage.png?alt=media&#x26;token=e8449bff-0593-4d18-bdc6-3bc0b139b08a" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">Automotive Ignition Power Sensing (IGN)</mark> <a href="#napjcgxvco0x" id="napjcgxvco0x"></a>

The Karbon 800 series 5-pin power input terminal offers automotive ignition sensing. The ignition sensing timing for power on and off delays can be modified through OnLogic’s microcontroller (MCU) using serial commands. These commands can be used to enable or disable the ignition sensing feature, to set the timing delay for system startup after ignition is detected, and to set the timing delay for system soft and hard shutdown after ignition is lost.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FhNcMJdwi0njGOrMJ44fi%2Fimage.png?alt=media&#x26;token=c4e1ca2e-6404-45f4-947f-e021d1f00c88" alt=""><figcaption></figcaption></figure>

The system should always be used with the supplied 5-pin terminal block and power input should use all 4 power pins (2\~5).

The system is operational from 12V\~48V DC and the maximum rated current of the connector is 15A per pin. A minimum wire gauge of 16 AWG is recommended for 24V installations. Higher power or lower voltage configurations may necessitate a heavier gauge power harness to reduce power loss in the cabling. Always use a wire gauge that is rated for the operational current of your configuration.

When connecting to the mating terminal block plug, only multi-strand wire with a crimped ferrule end should be used. The terminal block screws must be torqued to the rated value (0.5 Nm).

#### <mark style="color:blue;">Networking</mark> <a href="#vmy3qhnz03qo" id="vmy3qhnz03qo"></a>

The Karbon 800 series features up to six 2.5 GbE LAN ports. Two of these LAN ports are PoE capable using an optional onboard module. When the PoE module is installed, the two PoE ports will provide up to 32W of combined power. This power output is enough to support a single port up to 25.5W (IEEE 802.3at), two ports up to 15.4W each (IEEE 802.3af), or two ports with a combined draw up to 32W (e.g. 7W and 25W).

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FgOGoguvulRtCqC695sXL%2Fimage.png?alt=media&#x26;token=dce737a2-bec4-4d05-a8e9-487c619817e5" alt=""><figcaption></figcaption></figure>

The Karbon 800 supports additional LAN expansion using OnLogic ModBay cards. ModBay cards can be used to add up to eight additional RJ45 LAN or PoE ports, or up to six additional M12 X-coded LAN or PoE ports. The ModBay LAN and PoE expansion cards provide 1 GbE LAN ports using dedicated Intel I210-IT network controllers for each port. Maximum ModBay PoE power output depends on the system voltage input, total system power draw, and operating temperature.

#### <mark style="color:blue;">USB Ports</mark> <a href="#id-8etti22igly1" id="id-8etti22igly1"></a>

There are six USB 3.2 Gen 2 Type A ports on the Karbon 800 series. All six USB ports are capable of delivering 10 Gbps of bandwidth per port and are rated to 5V @ 900mA of power delivery per USB-IF specification. Optional ModBay cards can be used to add up to eight additional USB 3.2 Gen 2 ports. All USB ports also support USB 2.0 connectivity and have 1xM2.5x0.45 threaded hole per 2 USB ports. Refer to Appendix C for PoE power budgets.

#### <mark style="color:blue;">DisplayPort</mark> <a href="#d086epmji660" id="d086epmji660"></a>

There are two full-size DisplayPorts on the Karbon 800 series. Both ports support DP 1.4 at 4K 60Hz and support MST (Multi Stream Topology). An MST hub can be used to support up to four independent displays. Please refer to Intel documentation for additional Alder Lake-S display output specifications [here](https://www.intel.com/content/www/us/en/products/platforms/details/alder-lake-s.html).

#### <mark style="color:blue;">SIM Cards</mark> <a href="#bhdgmaa3cr3r" id="bhdgmaa3cr3r"></a>

Two 3FF Micro-SIM card slots are available on the front panel of the Karbon 800 platform allowing native support for 4G LTE and 5G cellular modems. The SIM signals can be directed to either the mPCIe or M.2 3042/3052/2280 B-key internal expansion slots. Both SIM signals can be connected to the M.2 3042/3052/2280 B-key to support modems with SIM failover capability. This selection is controlled in BIOS. The default BIOS setting will connect SIM1 to the mPCIe and SIM2 to the M.2 3042/3052/2280 B-key. Please refer to the [BIOS user manual](https://support.onlogic.com/product-documentation/rugged-products/karbon-k800-series/k800-bios-manual) for additional information.

The SIM slot is a Push-Push type slot. To insert or remove the SIM card from the front panel of the Karbon platform, please use a small implement to push the card into the slot until it clicks. To remove the card, push with a small implement until the card clicks, then pull on the free end of the card to remove it.

#### <mark style="color:blue;">RTC Reset Button</mark> <a href="#id-30ckx1upv8a2" id="id-30ckx1upv8a2"></a>

Karbon 800 Aseries features an RTC reset button that can be accessed using a paperclip or SIM card removal tool. Be sure the system is powered off and unplugged before resetting with the button. The RTC reset button is found next to the power button.

#### <mark style="color:blue;">Expansion Port Pinout</mark>

#### <mark style="color:blue;">M.2 B-key Pinout</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fs0hpnF9i9m6mYDwMKouU%2Fimage.png?alt=media&#x26;token=15acc54e-fd83-4333-b246-66f1247c235f" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">M.2 M-key Pinout</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F0eJDCdOH7SivMpYn1SXO%2Fimage.png?alt=media&#x26;token=aaa62d34-2dac-4c49-ab8e-8e26dc26854a" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">M.2 E-key Pinout</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FbKPCFtiE7N5eHXV5IDjo%2Fimage.png?alt=media&#x26;token=007d428d-c1c8-438f-8fd3-b5897034e59c" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">mPCIe Pinout</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FEykl05ifMswYVynynIIx%2Fimage.png?alt=media&#x26;token=42fbd8e9-6c37-42fc-b77c-a05a88edd9e3" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">PoE Power Budget</mark> <a href="#bh8q5ka7gwss" id="bh8q5ka7gwss"></a>

The nominal power budget for all PoE ports on the Karbon 800 series is provided below. These values are provided for room temperature operating conditions. Increased ambient temperature will limit the maximum safe operating power for the Karbon 800 series. Please contact OnLogic for specific derating information for your installation.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FH9kqBGObPF1Xn2nIuKlF%2Fimage.png?alt=media&#x26;token=b7cb7563-e581-47d2-8af3-c100800da28f" alt=""><figcaption></figcaption></figure>

### <mark style="color:blue;">2.2- Motherboard Connectors</mark> <a href="#bh8q5ka7gwss" id="bh8q5ka7gwss"></a>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FqGqZFIMuwUIAQcAlj2lz%2Fimage.png?alt=media&#x26;token=300c30f7-36a1-45c5-a8a4-46ea1b79058f" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="100"></th><th></th></tr></thead><tbody><tr><td><strong>Item</strong></td><td><strong>Description</strong></td></tr><tr><td>A1</td><td>Power button</td></tr><tr><td>A2</td><td>Audio Jack</td></tr><tr><td>A3</td><td>8-bit Isolated DIO (4-in, 4-out), CAN bus, External Switch</td></tr><tr><td>A4</td><td>COM RS-232/422/485 ports (2x)</td></tr><tr><td>A5</td><td>USB 3.2 Gen 2 Type-A ports (4x)</td></tr><tr><td>A6</td><td>3FF Mini-SIM slots (2x)</td></tr><tr><td>A7</td><td>External fan header</td></tr><tr><td>A8</td><td>5-pin Power input with ignition sense</td></tr><tr><td>A9</td><td>Auxiliary power for GPU Power card</td></tr><tr><td>A10</td><td>DisplayPorts (2x)</td></tr><tr><td>A11</td><td>2.5 GbE LAN ports (2x or 6x)</td></tr><tr><td>A12</td><td>USB 3.2 Gen 2 Type-A ports (2x)</td></tr><tr><td>A13</td><td>PCIe Gen 4.0 x16 connector</td></tr><tr><td>A14</td><td>PCIe Aux power and fan control header</td></tr><tr><td>A15</td><td>CMOS battery</td></tr><tr><td>A16</td><td>TPM header</td></tr><tr><td>A17</td><td>Onboard PoE header</td></tr><tr><td>A18</td><td>SATA III ports (2x)</td></tr><tr><td>A19</td><td>M.2 2280 M-key (PCIe Gen 4 x4)</td></tr><tr><td>A20</td><td>ModBay connectors (2x)</td></tr><tr><td>A21</td><td>SATA power headers (2x)</td></tr><tr><td>A22</td><td>4-pin Aux power expansion (12V, 5V)</td></tr><tr><td>A23</td><td>mPCIe slot (PCIe Gen 3 x1, USB 2.0)</td></tr><tr><td>A24</td><td>DDR4 SO-DIMM slots (2x)</td></tr><tr><td>A25</td><td>M.2 2280 M-key slot (PCIe Gen 4 x4, SATA)</td></tr><tr><td>A26</td><td>M.2 2230 E-key slot (PCIe Gen 3 x1, USB 2.0)</td></tr><tr><td>A27</td><td>M.2 3042/3052/2280 B-key slot (PCIe Gen 3 x2, USB 3.0, USB 2.0)</td></tr></tbody></table>

#### <mark style="color:blue;">M.2 2280 M-key 1</mark> <a href="#bbajrup9avl5" id="bbajrup9avl5"></a>

This expansion slot is capable of supporting PCIe Gen 4 x4 and is routed directly to the CPU. This slot is designed to support NVMe storage drives. A full pinout table for this expansion slot is provided in Appendix C.

#### <mark style="color:blue;">M.2 2280 M-key 2</mark> <a href="#hy8yrl4wlm3z" id="hy8yrl4wlm3z"></a>

This expansion slot is capable of supporting PCIe Gen 4 x4 or SATA III and is routed to the chipset. This slot is designed to support NVMe or SATA storage drives. A full pinout table for this expansion slot is provided in Appendix C.

#### <mark style="color:blue;">M.2 3042/3052/2280 B-key</mark> <a href="#z88g62ewlrpw" id="z88g62ewlrpw"></a>

This expansion slot is capable of supporting PCIe Gen 3 x2, SATA III, USB 3.2 Gen 2, USB 2.0, and dual SIM card inputs from the external I/O. This slot is designed to support various expansion cards such as SATA storage drives and 4G LTE or 5G cellular cards. A full pinout table for this expansion slot is provided in Appendix C.

The SIM1 and SIM2 3FF Micro-SIM card slots are connected to this slot. The routing can be selected in the BIOS. The default setting routes SIM1 to the mPCIe slot and SIM2 to the M.2 B-key slot, but both SIM cards can be routed to the M.2 B-key slot to support modems with SIM failover capability. Please refer to the [BIOS user manual](https://support.onlogic.com/product-documentation/rugged-products/karbon-k800-series/k800-bios-manual) for more information.

#### <mark style="color:blue;">M.2 2230 E-key</mark> <a href="#id-1wbuv7fuxgsy" id="id-1wbuv7fuxgsy"></a>

This expansion slot is capable of supporting PCIe Gen 3 x1 and USB 2.0 signals. This slot is designed to support M.2 2230 Wi-Fi expansion cards. A full pinout table for this expansion slot is provided in Appendix C.

#### <mark style="color:blue;">mPCIe</mark> <a href="#pewqwu32ki4i" id="pewqwu32ki4i"></a>

This expansion slot is capable of supporting PCIe Gen 3 x1, USB 2.0, and SIM card input from the external I/O. This slot is designed to support full-length cards. Half-length cards can be installed using an adapter. A full pinout table for this expansion slot is provided in Appendix C.

The SIM1 3FF Micro-SIM card slot is multiplexed to both the mPCIe and M.2 B-key slots. The default setting routes SIM1 to the mPCIe slot and SIM2 to the M.2 B-key slot. Please refer to the [BIOS user manual](https://support.onlogic.com/product-documentation/rugged-products/karbon-k800-series/k800-bios-manual) for more information.

#### <mark style="color:blue;">TPM Header</mark> <a href="#es04vm2litpw" id="es04vm2litpw"></a>

The Karbon 800 series supports an optional discrete TPM 2.0 module. OnLogic offers a wide-temp TPM 2.0 module based on the Nuvoton NPCT750 (SKU: TPM01).

#### <mark style="color:blue;">Onboard PoE Header</mark> <a href="#id-9skk323apwbx" id="id-9skk323apwbx"></a>

The Karbon 800 series has a PoE header which uses an optional module to enable PoE on two of the onboard 2.5 GbE LAN ports. On the two LAN models, both ports 1 and 2 will have PoE enabled. On the six LAN models, ports 2 and 3 will have PoE enabled which leaves port 1 as the AMT-enabled remote management port. Please refer to section 2.7 Networking for additional PoE output information.

#### <mark style="color:blue;">Aux Power Expansion Header</mark> <a href="#gns1d0ulmfdt" id="gns1d0ulmfdt"></a>

The Karbon 800 series has a power header that can support up to 2A of 5V and 12V power. This header is designed for internal expansion cards that require additional power above what is provided by the expansion slots. This header is a 2.5mm Pitch 4-pin JST XH Connector, with the pinout shown below.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FPlkA3nNfekYFZuBh7BOj%2Fimage.png?alt=media&#x26;token=a0c2b20d-a2a8-42e9-bae2-f51c0d65bb29" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">SATA Headers</mark> <a href="#xnz9ogfeodon" id="xnz9ogfeodon"></a>

There are two SATA data and SATA power headers on the Karbon 800 motherboard. The data ports support SATA III 6Gbps storage devices. Each SATA power header delivers 12V and 5V output. The OnLogic CBD123 SATA data and power cable is recommended for use with these ports and 2.5” SSD storage drives.

#### <mark style="color:blue;">PCIe Gen 4.0 x16 Connector</mark> <a href="#jlbwrvc529bt" id="jlbwrvc529bt"></a>

The Karbon 800 series features one PCIe x16 connector on the motherboard. This connector is paired with OnLogic risers to support multiple PCIe configurations in the K803 and K804 models.

#### PCIe x16 Riser (K803) <a href="#ntkhp0r3necq" id="ntkhp0r3necq"></a>

This riser supports a single-height PCIe Gen 4 x16 expansion card in the K803. There is one fan header on the riser as well to support the fan in the chassis. The K803 will fit PCIe cards up to 4.4” H x 9.5” L x 0.57" W (111.8 x 241.3 x 14.5 mm).

#### PCIe x16 Riser (K804) <a href="#hxr3irkcr48x" id="hxr3irkcr48x"></a>

This riser supports a dual-height PCIe Gen 4 x16 expansion card in the K804. Additionally, there are six SATA power headers to support a 6x 2.5” SSD RAID array when paired with a discrete RAID adapter, and fan headers to power the internal fans in the K804 PCIe expansion bay. The K804 will fit PCIe cards up to 4.8” H x 10” L x 1.37" W (121.9 x 254 x 34.8 mm).

#### Dual PCIe x8 Riser (K804) <a href="#id-1ye7m5vm25sy" id="id-1ye7m5vm25sy"></a>

This riser supports two single-height PCIe Gen 4 x16 expansion cards in the K804. The slots will mechanically accept PCIe x16 cards, however each slot will only provide PCIe Gen 4 x8 lanes. K804 will automatically detect this riser and enable bifurcation of the native PCIe x16 slot on the motherboard. There are fan headers on the riser to power the internal fans in the K804 PCIe expansion bay.

#### <mark style="color:blue;">DDR4 SO-DIMM Slots</mark> <a href="#rgxvb63oo2gg" id="rgxvb63oo2gg"></a>

The Karbon 800 series supports up to two DDR4 SO-DIMM slots rated up to 3200MHz. The system will support non-ECC memory with all CPU options and ECC memory with a Core i5 (Except i5-12400), i7 and i9 CPUs.

### <mark style="color:blue;">2.3- Power Management</mark> <a href="#yrmb4midipsf" id="yrmb4midipsf"></a>

#### <mark style="color:blue;">Connecting the power supply</mark> <a href="#connecting-the-power-supply" id="connecting-the-power-supply"></a>

If you need to assemble the system’s power input connector, follow these steps to locate and wire the correct parts.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-9b5414b7f953708cfb00393e0aa7e53c69bfb056%2Ff93e3fbc39afd7adf1a0e416aa95ef2033a2099ab282e563fd0d009dddf9f697.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

* Unbox the power brick and grab the 5 pin green/black terminal block from the accessory box.
* Using a flathead screwdriver, turn the two indicated screws counter-clockwise a few turns.
* The metal holes at the bottom will open up.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-63c8cf8edff5fef0331f192d8c84eb9ff4e40150%2F9a1832b8970038a7ba3bef630946fc26bd166229eadd620342ece751a585c459.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

* Insert the power supply wires as shown

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-b62dc54d0387202b40e3b11e4d9ace088c468cb6%2F175397283617abe873e9f53172823a06d4a44971e1e4af1d76bcaa1f39f664dc.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

* Turn the screws clockwise to tighten. Firmly hand tighten.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-7da64d4f707d026c462d7c1702516de53857a8ba%2Fdaa773f358295e00628941a5caf140f342a4f63f5f9b8508d7ef0ef5c6e356b5.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* Connect the green/black terminal block to the K800. It is now ready for use. Note that the labeling on the back of the system matches the wires you just installed.

#### <mark style="color:blue;">Protection Circuitry</mark> <a href="#id-4qoqmja2k4i7" id="id-4qoqmja2k4i7"></a>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F3mtRI9FvjWDRwgxL3uEg%2Fimage.png?alt=media&#x26;token=e160d983-d8a6-4d57-a0c0-5150b01c826f" alt=""><figcaption></figcaption></figure>

These DC levels specified are the absolute max values for the pins for function and safety of the system. The protection circuitry allows for brief transient voltages above these levels without the system turning off.

#### <mark style="color:blue;">Wake-Up Events</mark> <a href="#ohvzxi1466dk" id="ohvzxi1466dk"></a>

Karbon 800 supports multiple power states. The wake-up events can be configured in the MCU and BIOS. This section describes the power management functions you can perform and gives information on protection circuitry for power adapters.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FVAyz8Q8TGFBQz9mwWlHC%2Fimage.png?alt=media&#x26;token=b0dcb4cf-0aa5-4143-b6c6-5ac21da013bd" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">**Auto Power On**</mark>

The K800 can be configured to turn on automatically when DC power is connected. This is useful for power outage recovery or if the unit is mounted in a hard to reach location. You can enable Auto Power On by following the steps listed below.

* Note: In future revisions the name of this setting will be changed. “Auto power ON’ under the Power tab will be the new name and location.

1. Power on the system and press Del a few times to access the “Front Page” menu
2. Choose “Setup Utility”
3. Navigate to Advanced > PCH-IO Configuration

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-ccfa4df60215882c0a2b3b61e7de196aedb3e625%2F76952fa292106ed3cbc8b6d731f2fe7d125bef8cf3d00d5a33fa7cdbd114a7a1.png?alt=media" alt="" height="396" width="448"><figcaption></figcaption></figure>

4. Locate “State After G3”
5. Change it to”s0 State” to enable auto power on.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-4a7a3a56dd6a336d1b2b647ecbb457591561e015%2F512db9b1a2c44f3489ddfd4eb6928ec73abf61d85829a740eaaeb2095b1f492d.png?alt=media" alt="" height="357" width="381"><figcaption></figcaption></figure>

6. Press F10 to Save & Exit

### <mark style="color:blue;">**2.4- Add-in Modules**</mark>

The Karbon 800 series K802 and K804 models feature two Modbay expansion slots. Each slot supports PCIe Gen 3 x2, USB 3.1 Gen 2, and USB 2.0.  OnLogic offers a variety of ModBay cards including RJ45 LAN or PoE, M12 LAN or PoE, USB 3, and a carrier card with two additional mPCIe slots.

#### <mark style="color:blue;">Modbay 4x LAN Expansion</mark> <a href="#clp9iiyi7z73" id="clp9iiyi7z73"></a>

The 4x LAN Expansion (MODBAY-4LAN01) adds additional RJ45 GbE LAN ports to the K802 and K804. This ModBay uses dedicated Intel I210-IT network controllers for each port which support speeds up to 1 Gbps.

Operating Temperature: -40\~70°C

#### <mark style="color:blue;">Modbay 4x PoE Expansion</mark> <a href="#htd6yora8if5" id="htd6yora8if5"></a>

The 4x PoE Expansion (MODBAY-4POE01) adds additional RJ45 GbE PoE LAN ports to the K802 and K804. This ModBay uses dedicated Intel I210-IT network controllers for each port which support speeds up to 1 Gbps. Additionally, each port supports PoE output. The power budget for PoE is dependent on the voltage of the system power input.Refer to Appendix C for PoE power budgets.

Operating Temperature: -40\~70°C

#### <mark style="color:blue;">Modbay 3x M12 LAN Expansion</mark> <a href="#gcm8krko5sfu" id="gcm8krko5sfu"></a>

The 3x M12 LAN Expansion (MODBAY-M12LAN01) adds additional M12 X-coded GbE LAN ports to the K802 and K804. This ModBay uses dedicated Intel I210-IT network controllers for each port which support speeds up to 1 Gbps.

Supported cables:

* CABLE-M12-RJ45-5M (5 Meter X-coded M12 to RJ45)
* CABLE-M12-RJ45-10M (10 Meter X-coded M12 to RJ45)

Operating Temperature: -40\~70°C

#### <mark style="color:blue;">Modbay 3x M12 PoE Expansion</mark> <a href="#id-6jq0u8qzuelb" id="id-6jq0u8qzuelb"></a>

The 3x M12 PoE Expansion (MODBAY-M12POE01) adds additional M12 X-coded GbE PoE LAN ports to the K802 and K804. This ModBay uses dedicated Intel I210-IT network controllers for each port which support speeds up to 1 Gbps. Additionally, each port supports PoE output. The power budget for PoE is dependent on the voltage of the system power input. Refer to Appendix C for PoE power budgets.

Supported cables:

* CABLE-M12-RJ45-5M (5 Meter X-Coded RJ45 to M12)
* CABLE-M12-RJ45-10M (10 Meter X-Coded RJ45 to M12)

Operating Temperature: -40\~70°C

#### <mark style="color:blue;">Modbay 2x 10Gb LAN Expansion</mark> <a href="#id-70ts99xc23pl" id="id-70ts99xc23pl"></a>

The 2x 10Gb LAN Expansion (MODBAY-10GLAN01) adds RJ45 10 GbE LAN ports to the K802 and K804. This ModBay uses a single X550 network controller which supports individual port speeds up to 10 Gbps and a maximum combined speed up to 15 Gbps across both ports.

Operating Temperature: -40\~40°C

#### <mark style="color:blue;">Modbay 4x USB3 Expansion</mark> <a href="#bn3wxtdg5z0t" id="bn3wxtdg5z0t"></a>

The 4x USB3 Expansion (MODBAY-4USB01) adds additional USB 3.2 Gen 2 Type-A ports to the K802 and K804. This ModBay uses two USB controllers which support individual port speeds up to 10 Gbps and a maximum combined speed up to 15 Gbps across all ports. The controllers are the ASM3142 (PCIe Gen 3 x2 to 2x USB 3.2 Gen 2) and the USB7206i (1x USB 3.2 Gen 2 to 2x USB 3.2 Gen 2). Each port is rated to 5V @ 900mA of power delivery per USB-IF specification. These ports can only wake in Modern Standby and are not active in Sleep and Hibernate system states.

Operating Temperature: -40\~50°C

#### <mark style="color:blue;">M12 LAN Expansion (optional, must be factory installed)</mark> <a href="#m12-lan-expansion-optional-must-be-factory-installed" id="m12-lan-expansion-optional-must-be-factory-installed"></a>

The 3x M12 LAN Expansion (MODBAY-M12LAN01) adds additional M12 X-coded GbE LAN ports to the K802 and K804. This ModBay uses dedicated Intel I210-IT network controllers for each port which support speeds up to 1 Gbps.\
Supported cables:\
● CABLE-M12-RJ45-5M (5 Meter X-coded M12 to RJ45)\
● CABLE-M12-RJ45-10M (10 Meter X-coded M12 to RJ45)\
Operating Temperature: -40\~70°C

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-f9d16924104b61ce8000cbacf9a41b0f99163eb9%2F1825cadba35a69fda8edbc84cdd3f28b11c52e145477ac30aa38867eed716405.png?alt=media" alt="" height="444" width="512"><figcaption></figcaption></figure>

### <mark style="color:blue;">**2.5- Thermal Results**</mark>

The thermal performance of the Karbon 800 was validated by loading the system to simulate expected workloads while the test system was exposed to high ambient temperatures in a thermal chamber environment. Two different workloads were considered, a 16-core 35W load and a 16-Core 65W load evaluated up to 70°C in a K801 chassis which is the worst case thermal scenario. The results were analyzed by comparing the average clock speed over the duration of the test to the expected base clock speed.

#### <mark style="color:blue;">Testing Conditions</mark> <a href="#bbkwe94lj9gd" id="bbkwe94lj9gd"></a>

* Temperature Range: -40 \~ 70°C
* Step size: 10°C (except for a jump from 0°C to 30°C during both tests)
* CPU, SSD, and RAM loaded

#### <mark style="color:blue;">Results Summary</mark> <a href="#id-8t0mtn4xpiv6" id="id-8t0mtn4xpiv6"></a>

The i9-12900 CPU (65W) was able to maintain above 80% base clock speeds as defined by Intel on both the performance cores and efficiency cores up to 50°C ambient temperature. Significant throttling occurred at higher temperatures under the test workload and the CPU did not have thermal headroom for any additional turbo power.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FhHPmjqpPCcs1FMjIBRwU%2Fimage.png?alt=media&#x26;token=824d3a58-5ff7-469e-85e8-6e9cad8d772c" alt=""><figcaption></figcaption></figure>

The i9-12900T CPU (35W) was able to maintain above 100% base clock speeds as defined by Intel on both the performance cores and efficiency cores up to 70°C ambient temperature. This indicates that there was thermal headroom for turbo power over the entire 2 hour run at 70°C.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fz2JG69Lm3VfE2NO26euq%2Fimage.png?alt=media&#x26;token=93b5348f-9f31-4738-8d20-06752443d521" alt=""><figcaption></figcaption></figure>

### <mark style="color:blue;">2.6- Block Diagram</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FoT9pEVDLAHSoloMuxu7N%2FCobalt%20Point%20Block%20Diagram-1.1.0.drawio.png?alt=media&#x26;token=031fca7f-15d2-4e9f-afbe-739d15a89273" alt=""><figcaption></figcaption></figure>

## <mark style="color:blue;">3- Installation & Mechanical</mark>

### <mark style="color:blue;">3.1- Dimensions</mark>

#### <mark style="color:blue;">K801 System Dimensions</mark> <a href="#o7eujup85e0m" id="o7eujup85e0m"></a>

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FIjVooX4y4LgT5uw5qwUS%2F13.png?alt=media)

#### <mark style="color:blue;">K802 System Dimensions</mark> <a href="#wl8lhnqjuu9e" id="wl8lhnqjuu9e"></a>

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FVy89k60RmPwLxpciG8az%2F14.png?alt=media)

#### <mark style="color:blue;">K803 System Dimensions</mark> <a href="#id-6v5itagl1bf1" id="id-6v5itagl1bf1"></a>

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FqSuFEQcsVVmgQrTe0R0a%2F15.png?alt=media)

#### <mark style="color:blue;">K804 System Dimensions</mark> <a href="#jq3zg8setg2x" id="jq3zg8setg2x"></a>

![](https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FQVw9zZt99GBLpYpnfMKj%2F16.png?alt=media)

### <mark style="color:blue;">3.2- Mounting Instructions</mark>

#### <mark style="color:blue;">K801 Wall Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FHU7tiFAi1WIwWaIJzXjC%2Fimage.png?alt=media&#x26;token=4357e81a-d1c6-46b6-bc5b-e11e7e59f1d3" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K801 DIN Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FJFiwqB1RH2kIo25ijoWl%2Fimage.png?alt=media&#x26;token=bcb36d14-84dd-448c-9e0f-af04f8618301" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K801 Vibration Isolation Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FX3ipyiXqtDTMirOkv3yv%2Fimage.png?alt=media&#x26;token=7815eaab-232d-44b5-b795-b484299d1a36" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K802 Wall Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FMNoA1jZRfv8gFTg4GSgQ%2Fimage.png?alt=media&#x26;token=460a09f9-e899-4a6b-8329-109650d6ee09" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K802 DIN Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FUt9HAszOeOqY2TBKbDAo%2Fimage.png?alt=media&#x26;token=6a753205-8b78-4327-8165-93bab64c0136" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K802 Vibration Isolation Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F3Ku7OcnskGTxCvHub7ci%2Fimage.png?alt=media&#x26;token=695b2286-8530-4b4c-ad9d-745583606a6e" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K803 Wall Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F14VRZuBeG9q927Lvx4Hd%2Fimage.png?alt=media&#x26;token=207ee554-64ee-41b0-a187-de7ceaf50c1f" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K803 DIN Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FDhGg9Y5siCv8rwuk1Mqj%2Fimage.png?alt=media&#x26;token=1ff76f7e-b76d-4e0d-b610-2b60e42e8d95" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K803 Vibration Isolation Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F99muKH6YmUOvpiAwvllW%2Fimage.png?alt=media&#x26;token=3b86d165-d337-4df2-a426-0996fbd69b85" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K804 Wall Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F01KWe1esmAszPHQMzrMw%2Fimage.png?alt=media&#x26;token=fb6bed16-760b-4bbb-9a7b-159d3b116bbb" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K804 DIN Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FzkY43hY1dAPvqu2z5DQE%2Fimage.png?alt=media&#x26;token=53d7697a-d6c3-4c2d-ad97-fd571c58682a" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K804 Vibration Isolation Mount</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FFPxPpRpcHRBIdAfPwVlT%2Fimage.png?alt=media&#x26;token=df33087c-d99c-4309-8759-3cdf88e1fccf" alt=""><figcaption></figcaption></figure>

### <mark style="color:blue;">3.3- Internal Access</mark>

#### <mark style="color:blue;">K801 Internal Access</mark> <a href="#k801-disassembly" id="k801-disassembly"></a>

Opening the system does not void the manufacturer’s warranty, however, some precautions are necessary to avoid damaging the unit. Damage caused while opening or modifying the system internals may not be covered by the warranty.

* Perform this disassembly in an area free of static discharge
* Before beginning, touch a grounded metal surface to discharge your body of static electricity

1. Turn the unit upside down and remove the 6 screws from the bottom plate.
2. Pry the bottom plate off

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-2e3d306ebff4cf9cb2d13fdca75b73b58a8e03b1%2Fef781a98b6e9c6ea7d4056b6e2ca35591a1d32439785f735f33ce9215f945ddc.png?alt=media" alt="" height="318" width="432"><figcaption></figcaption></figure>

3. In case the thermal pads become displaced during disassembly, a reference guide is shown below. Note that the blue film will not be present as it is removed during initial assembly.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-e8202cb0c933e18de2242585afece9a398728ade%2F995849b63a006539313d5e6f627c5409070e09849e38978da24f19f7305c2e0c.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

#### <mark style="color:blue;">K802 Internal Access</mark> <a href="#k802-disassembly" id="k802-disassembly"></a>

Opening the system does not void the manufacturer’s warranty, however, some precautions are necessary to avoid damaging the unit. Damage caused while opening or modifying the system internals may not be covered by the warranty.

* Perform this disassembly in an area free of static discharge
* Before beginning, touch a grounded metal surface to discharge your body of static electricity

1. Turn the unit upside down and remove the 6 screws from the bottom plate.
2. Pry the bottom plate off

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-2e3d306ebff4cf9cb2d13fdca75b73b58a8e03b1%2Fef781a98b6e9c6ea7d4056b6e2ca35591a1d32439785f735f33ce9215f945ddc.png?alt=media" alt="" height="318" width="432"><figcaption></figcaption></figure>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-4dc225a536272e51856168e336c377449fbcf500%2F3e5810da1e2508d44e97bd918be7e8b552a8a78d04110ce0e7a06e65c7f1e1b1.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

3. Unplug the SATA power and data cables (if equipped)

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-12029c19f4fdccc11b3a0510f8b3eddc6f997994%2Fad1d3f7b0da62d5c8cce77f2dde0554fb577fbb17e1fa52162429e0df807979a.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

4. Grab the metal plate where shown
5. Lift upwards and pull towards you to remove the plate
6. In case the thermal pads become displaced during disassembly, a reference guide is shown below. Note that the blue film will not be present as it is removed during initial assembly.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-f903c6591f728cafd2f0ff2fc42409de3355e2bb%2F95a090ce9ddf40afaaf72ab5ed820a3a9fa41b26229a21edfae52a55770680cf.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

#### <mark style="color:blue;">K803 Internal Access</mark> <a href="#k803-disassembly" id="k803-disassembly"></a>

Opening the system does not void the manufacturer’s warranty, however, some precautions are necessary to avoid damaging the unit. Damage caused while opening or modifying the system internals may not be covered by the warranty.

* Perform this disassembly in an area free of static discharge
* Before beginning, touch a grounded metal surface to discharge your body of static electricity

1. Turn the unit upside down and remove the 6 screws from the bottom plate.
2. Pry the bottom plate off

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-2e3d306ebff4cf9cb2d13fdca75b73b58a8e03b1%2Fef781a98b6e9c6ea7d4056b6e2ca35591a1d32439785f735f33ce9215f945ddc.png?alt=media" alt="" height="318" width="432"><figcaption></figcaption></figure>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-2b6f2663c70cdeaf214ef30fd06c78f2c2f2d39f%2Fa5c39bec359a79ea36757c32ff3af42efcd3276bb016b2ede0ca9e9685425db7.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

3. The internals of the system can now be accessed.
4. The riser card (for PCIe installation) can be difficult to install/remove. It is not recommended to remove this part, but if needed, the metal plate can be lifted upwards slightly. For example to access the RAM slots.\
   **Any damage caused while removing/installing the mid-plate is not covered by warranty.**

#### <mark style="color:blue;">K804 Internal Access</mark> <a href="#k804-disassembly" id="k804-disassembly"></a>

Opening the system does not void the manufacturer’s warranty, however, some precautions are necessary to avoid damaging the unit. Damage caused while opening or modifying the system internals may not be covered by the warranty.

* Perform this disassembly in an area free of static discharge
* Before beginning, touch a grounded metal surface to discharge your body of static electricity

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-627659dcdcd5bef0e546e4b6a19e694b06b1a95f%2Fbb323629ee541074eb5c6bd634e389d16937d94e69675407b6c83f20e957b1b2.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

1. Turn the system upside down and remove the 6 Torx T8 screws from the sides.
2. Remove the bottom plate.

### <mark style="color:blue;">3.4 - System Servicing</mark> <a href="#installation-of-parts" id="installation-of-parts"></a>

PCIe cards can be installed to the K803, and K804 expansion bays. The maximum dimensions for a PCIe card depend on the platform, and are as follows:

**K803 Max PCIe Dimensions**: Single slot height, 111mm H x 241mm L (4.4” H x 9.5″ L in)\
**K804 Max PCIe Dimensions**: Single OR Double slot height, 111mm H x 241mm L (4.4” H x 9.5″ L in)

#### <mark style="color:blue;">**Installing a PCIe Card (K803)**</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-9f3c57caaa5432015bd4aa4e949564197a558024%2Fa732e4d267e3c6bf9d01b1f5390e1c143311027b8462d6e4c37cbffc9c1cc64b.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

1. Remove the retaining screw from the outside of the case.
2. Remove the metal slot cover.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-b70748ebfdee218fa799ebf28fa55eb5431f2cd4%2F60705a6e7db608dd6baa3d88ce02008b4f1e1cc4fb09be97d84e6d0923dbb033.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

3. Insert the PCIe card into the slot. Ensure it fully seats.
4. Loosen the screws on the brace bracket. Move the bracket so it touches the card. This will prevent it from moving.
5. Tighten the screws back down.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-e6f95d7009245b02a380a8c98422cb4a7797a459%2F994de1e83da256c42d00a4564996ce3a6649dddd6523476bfa889c57a78b1a62.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

6. Reinstall the external mounting screw.
7. Card installation complete.

#### <mark style="color:blue;">**Installing a PCIe Card (K804)**</mark> <a href="#installing-a-pcie-card" id="installing-a-pcie-card"></a>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-f4c639b3a10c844764677d1f2eef0d3a6efa79bc%2Fba1efad4144b2b0b1cab31cf99216a0b8875a32d1e36e0e3cc46e06943a2a866.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

1. Remove the two exterior screws from the PCIe retention bracket.
2. Remove any PCIe blanks.
3. If you are installing a single slot card, snap them apart and reinstall 1 PCIe blank into the upper slot.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-45f1b44caaa2170202b26a27f3c851a21b479461%2F570a336d44fc95405267f3b267669f1d77db7fbf72dc3e362bb8fd6d73de3964.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

4. Insert the PCIe card
5. Ensure it clicks into the slot and the backplate slots into the system.
6. Connect any required PCIe 6/8 pin power connectors. Cables can be found in your accessory box.\
   \&#xNAN;***Note:** PCIe power board may be optional, depending on the system’s configuration.*

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-1ef3033d66f717343e6298b6fc61c911ae91baba%2F6fc8d010830bd42d8f26a014e35ccaa8acd619324575e776c472d4e7368201d8.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

7. Reinstall the retention clip and hand tighten both screws.
8. Reinstall the bottom cover and the process is complete.

#### <mark style="color:blue;">**Installing the optional External Fan**</mark> <a href="#installing-the-optional-external-fan" id="installing-the-optional-external-fan"></a>

The external fan is an optional add-on for the K700 & K800 series, which provides active cooling. This adds a 120mm case fan and moves approximately 110 CFM of airflow.\
\
The K700 and K800 series use the same external fan. It can be installed by removing the branding plate (on the top of the system) and installing the following screws:

* x2 on the top (under the branding plate)
* x1 on the side

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-ba5c2001709690c46a4bcb81187ebc539f184d24%2Fbb1f80cdef889ed7f325379616b035bbe4d652211bfe672e0bd01d330726bd0b.png?alt=media" alt="" height="395" width="413"><figcaption></figcaption></figure>

The external fan uses a magnetic dust filter. The filter should be cleaned regularly. If the filter is misplaced, our replacement part SKU is FANCPD-MESH. This can be ordered by reaching out to our sales team.

#### <mark style="color:blue;">**Installing M.2 Storage**</mark> <a href="#installing-m-2-storage" id="installing-m-2-storage"></a>

1. Slide M.2 storage drive into slot
2. Gently press drive down flat and secure with M.2 screw
3. Apply thermal pad

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-1bc92a34bced2ecd84c1d57bbbd668af3549b7dd%2F9698e2c665b25af26baee3f726462ad420d83a1fea3c052b02eb794a580aebcb.png?alt=media" alt="" height="348" width="438"><figcaption></figcaption></figure>

#### <mark style="color:blue;">**Installing the PoE module**</mark> <a href="#installing-the-poe-module" id="installing-the-poe-module"></a>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-758742661c08b554d456edb12bf6aebd0a16882a%2F485c6ced4da0d42192406b1f2f6fd281b5ece2b0e079c4412d80ee22a93dbab9.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

The PoE kit includes the PoE modules itself, plus needed standoffs, screws, and thermal pad for the installation.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-eda60d4e080812b8511bd263f6fd9ea315f66f40%2Fe94f4bf6c446010aab6afe522cfc6f6019b220cade6d94bf7fb9fe611d7728a1.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* Install the standoffs. Gently hand tighten – they are fragile.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-79abd5d403882514bb0d9cbb916ccd182ea1bec8%2F60ef4961ace3cb19b93466acb9c8764cc6381cf7c7522672954656f6ff83c1bf.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* Install PoE module onto connector. **Double check that the pins align.**
* Install 2x screws
* Peel and stick thermal pad

### <mark style="color:blue;">3.5- CAD & Drawings</mark>

#### <mark style="color:blue;">K801 Dimensional Drawings</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FRaBnEO03bqrsNJJbjDIJ%2Fimage.png?alt=media&#x26;token=3ad1afa3-a2d0-4f14-a242-8bb19ddeb467" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K801 CAD Files</mark>

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FuFetXJXbRH0z6JjZibrZ%2FK801_All_Mounting_With_Fan.zip?alt=media&token=fbecc084-63a1-4af7-9eb5-cbbe84351899>" %}

#### <mark style="color:blue;">K802 Dimensional Drawings</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FofESNocy5g6CfuRsahKk%2Fimage.png?alt=media&#x26;token=6cc27e8a-0750-40df-8317-e70e8644e634" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K802 CAD Files</mark>

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FN94a9j6hVOCohC5wXvIS%2FK802_All_Mounting_With_Fan.zip?alt=media&token=63dc19d4-70ef-4488-b199-748c13ddc55a>" %}

#### <mark style="color:blue;">K803 Dimensional Drawings</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FPQE8L59yDw1tneUNEt5m%2Fimage.png?alt=media&#x26;token=ea803c78-2242-42c5-9772-912096693d75" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K803 CAD Files</mark>

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FbDOsTsnGqUWjVjN3Eeq4%2FK803_All_Mounting_With_Fan.zip?alt=media&token=b46e8e21-24b0-47ff-831b-1946b50ed41e>" %}

#### <mark style="color:blue;">K804 Dimensional Drawings</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FMfqS7luOzaNQ9isamm0i%2Fimage.png?alt=media&#x26;token=fb9ae9da-6708-4add-bfb4-6509e911ddf9" alt=""><figcaption></figcaption></figure>

#### <mark style="color:blue;">K804 CAD Files</mark>

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FYZ3ShBcIQeACXk0BkeGw%2FK804_All_Mounting_With_Fan.zip?alt=media&token=a2d7b3a8-925a-46b9-8d39-811afccb2b9d>" %}

## <mark style="color:blue;">4- Software & Firmware</mark>

Linux requires Kernel 5.16 or higher to operate as expected.

### <mark style="color:blue;">4.1- BIOS</mark>

#### BIOS Updates <a href="#bios-updates" id="bios-updates"></a>

| Bios Version | Link                                                                                             |
| ------------ | ------------------------------------------------------------------------------------------------ |
| B017         | [Download](https://static.onlogic.com/resources/bios/K800/K800_BIOS_B017/K800_BIOS_B017/EFI.zip) |
| B005         | [Download](https://static.onlogic.com/resources/bios/K800/K800_BIOS_B005.zip)                    |

[Changelog](https://static.onlogic.com/resources/bios/K800/K800_BIOS_B017/K800_BIOS_B017/Changelog%20K800%20BIOS%20B017.txt)

Refer here for the full [K800 BIOS Manual](https://support.onlogic.com/product-documentation/rugged-products/karbon-k800-series/k800-bios-manual)

### <mark style="color:blue;">4.2- Drivers & Downloads</mark>

[K800 Windows 11 Drivers](https://static.onlogic.com/resources/drivers/OnLogic-K800-Drivers.zip) ( or [INF files for server deployment](https://static.onlogic.com/resources/drivers/OnLogic-K800-Drivers-INF.zip))

[K800 Windows 10 Drivers](https://static.onlogic.com/resources/drivers/OnLogic-K800-Drivers-10.0_x64.zip) (Follow our guide for [Updating System Drivers](https://support.onlogic.com/support-articles/how-tos/operating-systems/windows/update-system-drivers))

### <mark style="color:blue;">4.3- Features & Configuration</mark> <a href="#yrmb4midipsf" id="yrmb4midipsf"></a>

#### <mark style="color:blue;">Setting up RAID and installing Windows 11</mark>

#### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* An 8GB or larger flash drive (USB 3.0 model recommended for speed)
* A PC running Windows 10 or 11
* The Media Creation Tool, [downloadable from here.](https://go.microsoft.com/fwlink/?linkid=2156295)
* The RAID driver, [downloadable from here](https://static.onlogic.com/resources/drivers/K800RAID-WinSetup.zip).

#### Creating the flash drive <a href="#creating-the-flash-drive" id="creating-the-flash-drive"></a>

* Download and run the Media Creation Tool, linked above

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-172297c9cc445febfbcfde2258cf9ce84d21022d%2F232b870c7d062f794ff2fa17f6c7a3c8779d86d035a7cbf7df67f5eaa29bdebb.png?alt=media" alt="" height="25" width="159"><figcaption></figcaption></figure>

* Accept the license agreement

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-e7dd8feb85fe3494f08340d31cde738a69ceec92%2F3a4830f6ae8f46df93bd6955d8ad9ee8031cc647d95614acd9f734e3260906a5.png?alt=media" alt="" width="533"><figcaption></figcaption></figure>

* Click Next

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-bdc5f6a7eb7bef0eafe5674a367c0de672c3b099%2Fef84a0d3bbd77714767c19dba8c421cf13aa68990c547735791ad4c37d60ea4e.png?alt=media" alt="" width="532"><figcaption></figcaption></figure>

* Choose the “USB flash drive” option and click Next

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-3c60c4ebe4351b5920bf1e9ee93d183f82fb9c74%2F5191bb6ba016aff11633d2b25cdde90c71ac71badd73ab1fc7612f15dbfe9549.png?alt=media" alt="" width="533"><figcaption></figcaption></figure>

* Choose your flash drive from the list and click Next
* If the drive does not show, ensure it is formatted as FAT32 or try a different drive.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-cf81c89ad19d4fe72675e9973dcba72e27ad0db7%2F6f7f549af8dd9c1f4db5a1d19d43032b883bedeca578c1d8db48c81b2af65bd0.png?alt=media" alt="" width="533"><figcaption></figcaption></figure>

* The Windows 11 installer will now download from the Internet and make the flash drive bootable. This will take several minutes depending on the speed of your flash drive and Internet connection.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-3aad1584d55b210e3143099819340dc064eff5d9%2Fe4ced69000ff55b54324a88322bf5a9b63fa5edc6bce61ba3bdecb2f8a0e2228.png?alt=media" alt="" width="533"><figcaption></figcaption></figure>

* When the tool finishes, click Finish to close it.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-a2f4d72843fbac557eae84821df600c57ac47b14%2Ff34c2d6a135dc660c6c4d563026c54582726bc3724cbb1b77ea0849081e95250.png?alt=media" alt="" width="532"><figcaption></figcaption></figure>

* Download the RAID driver (linked above)
* Extract the .zip file and copy the contents to the Windows setup USB flash drive.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-fbffed992f1aa8e60e44fb921bf4a7121b35d06c%2Faf98db19bacb41a65e9e70b1708958ca3f082a10d23581e06454275b41ee9b3d.png?alt=media" alt="" width="371"><figcaption></figcaption></figure>

* Safely eject the flash drive and unplug it from the PC.
* Insert the flash drive into the K800

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-8f3596d1c50fcd5a14ac65c111d7189b341f6f2d%2Fbadaa1d1ed5a970ee76bf39fd10af0d5144b2a1956d38eea55261f996b07b1e7.png?alt=media" alt="" height="122" width="256"><figcaption></figcaption></figure>

#### <mark style="color:blue;">Enabling RAID</mark> <a href="#enabling-raid" id="enabling-raid"></a>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-0999a52137e8e306451ed92288be8e670fec4e5c%2F61b4e0143e489c0a44bf8a5a7f30b87f00d40b87d2b3f3b0abab66ed261cb89b.png?alt=media" alt="" width="496"><figcaption></figcaption></figure>

* Begin by powering on the K800 and immediately press the Del key a few times to access the menu
* Using the arrow keys, navigate down to “Setup Utility” and press enter

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-11c4fdfac8a5af2de5b696ab2a3ad9abe91a7b26%2F286b1cf23532278af01cd98a46a9226f5a629a619e7f09d3011259aaa8a93f8e.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* Navigate to the “Advanced” tab
* Set “Expert Mode” To “Enabled”

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-7613d676d3d8a61e9d2bf526154d3ce632f31723%2Ffd1e34c908397d815a6efdb56ce611953f00b2ba711926102c144e455542dfb4.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* Open the “System Agent (SA) Configuration” menu

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-799d4dcadff8dfd973973ad8ac824c9ef23a044f%2Fd03768c324692180bd955396187fa82be6a950ded918fbc7de6986cd5dc124ea.png?alt=media" alt="" width="456"><figcaption></figcaption></figure>

* Open the “VMD setup menu” menu

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-7e46d254b3e0b8287a66bae0c94a9cc6966b0987%2F93812bd9f4694074dd887f068aef8776e4ae429bc41908659fd3b60e977c2acf.png?alt=media" alt="" width="441"><figcaption></figcaption></figure>

* Set “Enable VMD Controller” to “Enabled”

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-50a1d61ae7df21f3153cf70aed68c1aa9605814f%2Fb660a8e6800e450ea6ba233233fa36e64a315a0d14a295b41e46e2aa63f17e70.png?alt=media" alt="" height="137" width="319"><figcaption></figcaption></figure>

* Press F10 to Exit Saving Changes

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-bf9b7f62d539a7c21d56adbc77d371264d9a58e6%2F7b5f2c435921c39bb44c73c68a97d2f919bf6534fc2600fc85f79ffb936120f2.png?alt=media" alt="" width="293"><figcaption></figcaption></figure>

* Tap the Del key again and go back to the “Front Page” menu
* Enter the “Device Manager” menu

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-1e8b859ea96255151e586e45992825c7fa947465%2Ff12860a1ad04f63a5ac3df61c380c1e5b02e4dca904c84f711f1c277ca9e7eb7.png?alt=media" alt="" width="482"><figcaption></figcaption></figure>

* Enter the “Intel(R) Rapid Storage Technology” Menu

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-d9f81b2e545730d897438da0935d0c7ecb17d30d%2F0dc47a7f50c004857eea4204d579ba8e35c20077b280e85cce6b99d315f25eea.png?alt=media" alt="" width="501"><figcaption></figcaption></figure>

Choose “Create RAID Volume”

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-4b01ff05c6fd0423ed55fce850abb18e576dc6be%2Fffb112e3d9a2558956879c68e8ab86a06b2174fc703c1545fd7e3473ca7fa68f.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* Set the “RAID Level” to “RAID1 (Mirror)”
* RAID0 is supported but generally not recommended as there is no redundancy.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-d95c4748df92de9efa141a77fcf974f43bd0ae9b%2F447d111bc97c630a9e3fb94736bf04bf8b7bfd5a0c6534a61622b4abf47a9e4b.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* Press enter on each disk and select the X to select it for RAID.
* You must choose at least 2 disks and they should be of the same size/type.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-51b0201c5e4cba3b733f967339577d1764af1faf%2Febc9b10e2a9d47c4cc182c2912ed2a2ea22454c5e05d78a1bd3544c4f58f5b44.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

* Choose “Create Volume”

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-739de4c0ffb12890aaf23fd3e940f958e08207f9%2F7cfb0c587d53231cfa61deb586f5493c6a94462289474ee534d63863c4d276c0.png?alt=media" alt="" width="497"><figcaption></figcaption></figure>

* Creation is very quick. You will now see the RAID volume listed with status “normal”

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-d48997d8e8cd5769cfdef6be1c64c4bdcfd6d948%2F41c6433c89ed899e85feefd84c68b60ab48e54dfec062769b8bbe5ecdf0960ac.png?alt=media" alt="" width="326"><figcaption></figcaption></figure>

* Press F10 to save (the system will not give any feedback)
* Press escape to go back to the “Front Page”
* Select “Continue”

#### <mark style="color:blue;">Installing Windows</mark> <a href="#installing-windows" id="installing-windows"></a>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-f5a7629016338a18d34675362d400bb4798039d4%2Fa67792a51fb2b470dd074bf156f55c435bc2887fb22ec9dbbb343d2aa321fc7a.png?alt=media" alt="" width="473"><figcaption></figcaption></figure>

* If you have not done so already, make sure the flash drive you created earlier is connected to the K800 PC.
* Boot from the flash drive.
* When the flash drive boots, you will be presented with this screen.
* Click “Install now”

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-f887320123b71e1d0435a96fdbe5eeeaed549f53%2F4856f86d633fe43ff630e9edf653772b1bc057f02b72b39fe0d865a3a99b7c37.png?alt=media" alt="" width="491"><figcaption></figcaption></figure>

* Enter the product key from the bottom of your OnLogic PC and click Next.
* You can skip this step and enter it later if preferred. Click “I don’t have a product key”

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-7ea241234cec1ad5ca1edb2a1639f2aaff83e4f4%2F08d99f5af02a93f6f5429f8a07851a9e66aa2d1baffd50126fb55c9bb3c656e1.png?alt=media" alt="" width="487"><figcaption></figcaption></figure>

* If prompted (typically when you don’t enter a product key), select your version of Windows.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-3895464acf736142ff35e3ec4b5196f4759af147%2F06fb498190d6886c102b1d5426f1d0eda0465234045c57a4018747d39da55422.png?alt=media" alt="" width="491"><figcaption></figcaption></figure>

* Accept the license agreement and click Next

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-f35a04f39a23fe1f2fb8a8574b3ea79b359808df%2Fe8eebb4fe1e34259d09703cfb13546b162bbc1c8c5969b90938f4a6a30027660.png?alt=media" alt="" width="487"><figcaption></figcaption></figure>

* Choose the option for Custom installation

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-e87847851157b45539e7fde61f1476e6fdf31a71%2F7cbeaeb27c241ffa8525f738dbef60fe7c110b3938e6159a4c911293cff01c36.png?alt=media" alt="" width="485"><figcaption></figcaption></figure>

* Note that no storage drive will be detected at first
* Click on “Load Driver”

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-a0a8283a833e502a2f36407ae66a07a0aa746b13%2F46df05acf27891c89eaefe486595530227eff51004f205b726a55b0760abbe4e.png?alt=media" alt="" width="385"><figcaption></figcaption></figure>

* Click “Browse”

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-d577f9a66c1b2ae6f4a893c7a571d90ddb47567c%2F3604975b90631e0a01b6a573e9ac97e0ee9020551e04ea3382945cfd091a76dd.png?alt=media" alt="" width="252"><figcaption></figcaption></figure>

* Expand the USB drive and select the RAID driver folder you copied to the flash drive earlier.
* Click OK.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-e13e0e8d1c706d13d93933b0391fcc72cd90199d%2Fadcf5903fe1c151d2db40d8d49bb9df6e69b267be2df643764419048928a23c6.png?alt=media" alt="" width="481"><figcaption></figcaption></figure>

* Select the top option only (467F)
* Click Next

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-4098bf397f1f200fe6e2bb9d600e76f0cc4dd8c8%2F3a0fb109f870c15c31f9e8526648e2ab1b8a691e6bf1848d8eccf05d6b8d3589.png?alt=media" alt="" width="476"><figcaption></figcaption></figure>

* After a few seconds of loading, you will be returned to the drive screen and the RAID volume will appear.
* Click “Next” to format it and proceed with the installation.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-f870c73015327a526df9279fa503cf70ddf607c0%2F925bc4dd9ab5f4cdfb25369666f5ddf915314f790d9326b088b2a2aca05e6b80.png?alt=media" alt="" width="229"><figcaption></figcaption></figure>

* The Windows installation will begin.

#### <mark style="color:blue;">First Boot & Setup</mark> <a href="#first-boot-setup" id="first-boot-setup"></a>

Refer to our [Windows 11 Setup Guide](https://support.onlogic.com/support-articles/how-tos/operating-systems/windows/windows-11-pro-reinstallation) for the next steps.

### <mark style="color:blue;">4.4- MCU Documentation</mark>

#### <mark style="color:blue;">Overview</mark> <a href="#kr6fzjp1ka7o" id="kr6fzjp1ka7o"></a>

The microcontroller toolchain on the Karbon-800 series controls several features, among which are:

* Automotive Ignition Power Sensing
* CAN 2.0 A/B
* Wet Contact Digital Input/Output (DIO)
* Status LEDs
* Input voltage monitoring
* RTOS Capabilities

Microcontroller functionality is exposed via two serial ports, through which the user can send and receive CAN messages, interact with the DIO bank, and select from a number of automotive configurations. One port is dedicated to Karbon 800’s CAN bus, while the other doubles as a serial terminal for accessing the DIO interface and automotive settings. Automotive configuration settings are saved to non-volatile memory, meaning that the MCU settings will be retained after a long power-off.

#### User Microcontroller Updates <a href="#microcontroller-updates" id="microcontroller-updates"></a>

| Microcontroller Version | Changelog                                                                                     | Link                                                                                                              |
| ----------------------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| v1.3.1.2                | – CAN bus fixes: Fully reset CAN peripheral when bus is opened, fixes unresponsive interfaces | [Download](https://static.onlogic.com/resources/firmware/binaries/K800/Z02-0006A312_Cobalt_User_MCU_v1.3.1.2.bin) |

Obtain the User MCU update utility here \[ [MCU Firmware Update w/ ZMU](https://support.onlogic.com/support-articles/how-tos/firmware-bios-drivers/mcu-firmware-update-w-zmu) ] and follow the steps to flash the User MCU with the firmware above.

#### Power Sequence Microcontroller Updates <a href="#power-sequence-microcontroller-updates" id="power-sequence-microcontroller-updates"></a>

| **Microcontroller Version** | **Changelog**    | **Link**                                                                                                |
| --------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------- |
| v2.1.6                      | – Ignition Fixes | [Download](https://static.onlogic.com/resources/firmware/binaries/K800/cobalt_pwrseq_update_v2.1.6.bin) |

Obtain the Power Sequence MCU update utility here \[ [Karbon-800 Series Power Sequence MCU Firmware Update](https://support.onlogic.com/support-articles/how-tos/firmware-bios-drivers/power-sequence-mcu-firmware-update) ] and follow the steps to flash the Power Sequence MCU with the firmware above.

#### <mark style="color:blue;">Accessing the Microcontroller (MCU)</mark> <a href="#accessing-the-microcontroller-mcu" id="accessing-the-microcontroller-mcu"></a>

The embedded microcontroller unit (MCU) is used to interface and control various aspects of the system such as CAN, DIO, and ignition sensing. To communicate with the MCU, follow the steps below for your installed OS.

#### Windows <a href="#windows-2" id="windows-2"></a>

1. Download the PuTTy tool from [putty.org](https://www.putty.org/)
2. Look in Device Manager and find the highest numbered USB serial device, COM5 in this example
3. Open Putty. Set the connection type to Serial and change COM1 to the COM # you found in the previous step. This example uses COM5.
4. Click “Open”. This will open a virtual connection to the MCU (no physical cable is required)

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-cc5a52a355939c2495939ca8a24857f835a4e78b%2Faab31c1b1164632c90ed8843c65ec0df3b389b684724ccccd9cece17ead1fee7.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

5. To confirm you have the correct port open, type “help” and press enter. The help text should appear. If it does not, try a different COM port.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-bc7ff3cedbb07ff8856b52184af16248e72c7359%2Fb6f8ff2f745a6fc9f252fcb4ab2f1c8128969960e567df351b7c3d5d0cd22610.png?alt=media" alt="" height="333" width="576"><figcaption></figcaption></figure>

***

#### Linux <a href="#linux-2" id="linux-2"></a>

1. Use a program such as PuTTy to interface with the microcontroller (MCU). You can run the following command to install it (you will need an active internet connection for this):\
   `sudo install putty`
2. The MCU will typically enumerate as **`ttyACM0`**. It enumerates as a serial-interfaceable USB device. If you run into issues accessing **`ttyACM0`**, you can run the following command to identify the other port(s):\
   `sudo dmesg | grep tty`

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-233f0b90b474f455a37d964f2f40f0622d93cb5d%2F82681f01421483a13f0a3c83b6096b71f6a14e7c19b30cbf90476d74943ce79b.png?alt=media" alt="" height="135" width="839"><figcaption></figcaption></figure>

3. In this example, the MCU is on **`ttyACM0`**. Open PuTTy, enter the port #, and set the connection type as “Serial”. The other settings can be left on their defaults (i.e. baudrate = 9600).

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-d6affbd981ce4f034ead883458066c968ec95ba0%2Fd87f3869b917d380faeaf16dcbe6f4162601a37a9e9535cd78571a90176926a9.png?alt=media" alt="" height="575" width="656"><figcaption></figcaption></figure>

4. To confirm you have the correct port open, type “help” and press enter. The help text should appear. If it does not, try a different port #.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-bc7ff3cedbb07ff8856b52184af16248e72c7359%2Fc80d7433a4f34795c23f278b42d457a9c32294186c3bd9fa2f8388a5e63b91a5.png?alt=media" alt="" height="333" width="576"><figcaption></figcaption></figure>

***

#### Microcontroller Commands <a href="#microcontroller-commands" id="microcontroller-commands"></a>

A full list of microcontroller commands be be found here in the User MCU Shell documentation here:

[**MCU Documentation**](https://static.onlogic.com/resources/firmware/documentation/shell.html)

#### <mark style="color:blue;">Automotive Timings</mark> <a href="#automotive-timings" id="automotive-timings"></a>

#### Feature Overview <a href="#feature-overview" id="feature-overview"></a>

The ignition sense feature can be used to turn the Karbon unit on and off with a battery, or vehicle’s ignition. It can also be used in non-automotive applications using a switch instead.

An example configuration is shown below. The switch connects positive DC power to the IGN pin. The unit will turn on when power is applied to the IGN pin, and turn off when power is removed. These events have configurable delays.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-e5268b51d0da30a36d27ee3e469660e194b0b7b9%2F919d5bd7f1a084337c9a8f709ee681d16692fbb4b2ec61f7150d15d6c02e0b32.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

#### Enabling and controlling ignition sense <a href="#enabling-and-controlling-ignition-sense" id="enabling-and-controlling-ignition-sense"></a>

Ignition sensing can be enabled and adjusted through a virtual COM connection to the system’s microcontroller (MCU). You can open this communication to the MCU using a program such as PuTTy. Refer to the above section [Accessing the Microcontroller (MCU)](#accessing-the-microcontroller-mcu) for help accessing the MCU.

Ignition sensing simulates a power button press. **In Windows**, the default behavior of the power button press is to put the system into Sleep mode. You will want to change that to “Shut Down” instead.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-bf5dc08e237f81b131f19f087c9f8c7516a6f8ff%2F0fec2c4d970fdfc97e8e4a756dc8bcbed9ea9857655fcb648ba47c3334f72454.png?alt=media" alt="" height="622" width="586"><figcaption></figcaption></figure>

#### Example ignition settings <a href="#example-ignition-settings" id="example-ignition-settings"></a>

The following shows an example configuration for automotive timings. Enter each command one by one.

For further help text, type **`lpmcu config`**

| Command                                                                                                                         | Effect                                                                                                                                                                        |
| ------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `lpmcu config automotive-mode true`                                                                                             | Enables automotive mode                                                                                                                                                       |
| <p>Command:<br><code>lpmcu config startup-timer \[X]</code><br><br>Example:<br><code>lpmcu config startup-timer 10</code></p>   | <p>Effect:<br>turn on X seconds after IGN pin receives power<br><br>Example:<br>turn on 10 seconds after IGN pin receives power</p>                                           |
| <p>Command:<br><code>lpmcu config hard-off-timer \[X]</code><br><br>Example:<br><code>lpmcu config hard-off-timer 60</code></p> | <p>Effect:<br>force shutdown system after X seconds (failsafe to protect battery)<br><br>Example:<br>force shutdown system after 60 seconds (failsafe to protect battery)</p> |
| <p>Command:<br><code>lpmcu config soft-off-timer \[X]</code><br><br>Example:<br><code>lpmcu config soft-off-timer 20</code></p> | <p>Effect:<br>shutdown X seconds after IGN pin loses power<br><br>Example:<br>shutdown 20 seconds after IGN pin loses power</p>                                               |

#### <mark style="color:blue;">CAN & DIO</mark> <a href="#can-dio" id="can-dio"></a>

The Karbon 800 has an embedded NXP i.MX RT1050-series microcontroller that can communicate with the host processor over USB. Its features include:

* Configuring the system LEDs
* Reading/writing the system DIO
* Using system Digital Outputs in PWM mode
* Configuring system automotive settings
* Managing the system CAN interface

To provide access to these features, the MCU supports a composite USB-CDC VCOM connection (VID: 0x353F, PID: 0xA101):

* Interface 0: A UART terminal supporting commands for a range of features
* Interface 2: A dedicate USB serial CAN interface

`C:\Users>python -m serial.tools.list_ports -v`

COM15

`desc: USB Serial Device (COM15)`

`hwid: USB VID:PID=353F:A101 SER=500100D20F3861D2 LOCATION=1-11:x.2 <--- CAN Port`

COM16

`desc: USB Serial Device (COM16)`

`hwid: USB VID:PID=353F:A101 SER=500100D20F3861D2 LOCATION=1-11:x.0 <--- UART Port`

The MCU shell is a fully-featured virtual UART shell exposed over the MCU’s first USB CDC-ACM interface. This shell supports both command history and line editing, and can optionally serve as an output target for driver log messages. For a complete command reference see, the [**shell command reference**](https://static.onlogic.com/resources/firmware/documentation/shell.html).

#### Firmware Updates

In order to support over-the-air firmware updates, the K800 has a two stage bootloader; a ROM bootloader, that can be started with physical access to the system, and a USB bootloader that supports updates from the OS.\
\
**Entering the ROM Bootloader (manual)**:\
1\. Detach the K800 system from wall power\
2\. Use a paper clip to depress the settings switch located above the front USB 3.0 ports\
3\. With the switch held down, re-attach system power\
4\. The MCU should now boot into the NXP ROM bootloader\
\
**Entering the USB Bootloader (manual)**:\
1\. Boot the K800 to the operating system\
2\. Use a paper clip to depress the settings switch located above the front USB 3.0 ports\
3\. With the switch held down, send the ‘reset’ command to the MCU’s UART port\
4\. The MCU should now boot into the second stage USB bootloader

#### DIO/CAN/Power Switch header <a href="#dio-can-power-switch-header" id="dio-can-power-switch-header"></a>

The Karbon 800 series 20-Pin header provides the following interfaces: 8-bit (4-in, 4-out) Digital Input Output (DIO) or General Purpose Input Output (GPIO) with optically isolated terminals, one CAN bus connection, and an optional external power switch connection.\
\
The DIO is optically isolated, meaning that the terminal is separated from other motherboard features for protection. The DIO terminal requires external power from a 5\~48V DC source through Pin 20 with GND to Pin 19 in order to function.\
\
The Isolated Power Supply (ISO PSU) can be a voltage source from 5\~48V to interface with external digital IO. The maximum power draw from the supply should not exceed 0.6A under normal operating conditions. Individual DOut pins will be damaged by loads in excess of 150mA. The ISO PSU must be a DC Limited Power Source (LPS) power supply.\
\
Mating power switch cables should be a twisted-pair wire with floating shield to assure proper\
immunity to EMI/RFI. It is recommended to keep wires at less than 3 meters in length. Any remote power switch connected between pins 1 and 2 should be momentary contact type only.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-564276f5c38af6a6095a7618d99a0ca00952f898%2Ff1cd38168bf38cebaaf2d6f1f83acbc62ea2d21d6ff618b614752d9e3e2b5877.png?alt=media" alt="" height="352" width="603"><figcaption></figcaption></figure>

**Connection Diagrams**

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-65adf8a8dc13096fa841ee2bb221ef1e2fffa6d4%2F3d6de905c1dd799c4582dd251624a33dcf8452dfc0f8b7ffa56a27ac27188989.png?alt=media" alt="" height="131" width="420"><figcaption></figcaption></figure>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-88ce35645b96103a094e3fcba7fe7f322908bb40%2Fb681b3773046f914b68f609b96da54c2df11813f4819d7c69ac567f8f5867bc2.png?alt=media" alt="" height="533" width="595"><figcaption></figcaption></figure>

#### <mark style="color:blue;">DIO & LEDs</mark> <a href="#dio-leds" id="dio-leds"></a>

**Examples:**

All digital inputs/outputs support reading the current logical state of the pin. Digital outputs additionally support setting the output state of the pin, and digital inputs support reporting the transition count of the pin (both edges). The K800 also support configuring digital outputs as PWMs, and configuring the PWM output’s pulse and duty cycle. For a additional command reference see, the [**shell command reference**](https://static.onlogic.com/resources/firmware/documentation/shell.html). The DIO can also be changed to Byte Mode as documented below.

`# Turn on LED 0 output`\
`uart:~$ dio set LED0 0 true`\
`# Check the state of Digital Input 0`\
`uart:~$: dio get DIO0 input 0`

While the microcontroller shell is intended for human interaction, it can be used to programmatically control the MCU. To avoid a number of pitfalls when doing so, observe the following best practices:

* On Linux, use the symlinked device nodes inside `/dev/serial/by-id` instead of hardcoding `/dev/ttyACMx` device names. `/dev/ttyACMx` numbering is
* unstable; `/dev/serial/by-id/usb-OnLogic_<device>-if00` will reliably point to the terminal interface.
* When writing Linux shell scripts, ensure that the echo flag is disabled on the TTY by running `stty -F /dev/serial/by-id/<device> -echo` before
* interacting with the shell. Most serial libraries (pyserial, serialport-rs, etc.) will automatically disable this flag.
* When sending a command, precede it with a ‘\x03’ byte to clear the terminal’s line buffer and ensure that the command is interpreted correctly. Follow the command with a ‘\r’ or ‘\n’ character to execute the command.
* Send less than 64 bytes at a time. To send longer commands, explicitly flush the port’s output buffer in between each block of 64 bytes.

**Byte Mode**

When using byte mode, DIO commands are sent in the form of command packets, and each command will receive a status (and optional data) as a response.

The command header is eight bytes in length:

| Bytes | Description                               | Options                                                                                                   |
| ----- | ----------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| 0     | The message ‘start of frame’ byte.        | Must be 0x01, or the message will be rejected. For non request/response frames, it is instead set as 0x02 |
| 1     | Indicates the kind of command transmitted | Must be one of the Valid Command Kinds                                                                    |
| 2 – 3 | The status of the last command            | Should be zero when sending a command, one of Status Codes when receiving                                 |
| 4     | The length of the transfered command data | Must be less than 56, and equal to the length of the command body in bytes                                |
| 5-7   | Reserved                                  | Must be 0x00                                                                                              |

All command headers must indicate the type of data to follow, by setting the command kind:

| Kind     | Value (u8) | Size     | Description                                                                    |
| -------- | ---------- | -------- | ------------------------------------------------------------------------------ |
| DIO      | 0x00       | 8 bytes  | Commands that get and set the state of MCU controlled digital IO banks         |
| CAN      | 0x01       | 6 bytes  | Sideband configuration and reporting for CAN devices                           |
| Reset    | 0x02       | 0 bytes  | Causes a cold-reset of the microcontroller                                     |
| Version  | 0x03       | 8 bytes  | Reports the firmware version of the running application image                  |
| Ignition | 0x04       | 10 bytes | Configures automotive and power features on supported devices                  |
| Disable  | 0x05       | 0 bytes  | Disables byte processing of incoming data, and returns to an interactive shell |

Each command sent will recieve a response from the microcontroller. This response may contain data, but can always be examined to determine if the command succeeded.

| Code                       | Value  | Description                                                                                |
| -------------------------- | ------ | ------------------------------------------------------------------------------------------ |
| Success                    | 0x0000 | The last command was processed successfully                                                |
| Invalid Device             | 0x0001 | The device indicated by the command exceeded the number of devices available to the system |
| Unbound Device             | 0x0002 | The device targetted exists, but the MCU was unable to attach to and communicate with it   |
| DIO – Invalid Pin          | 0x0003 | The target pin exceeded the number of inputs or outputs actually present                   |
| DIO – Pin Read Failed      | 0x0004 | Reading the state of the targetted pin failed for an unknown reason                        |
| DIO – Pin Write Faield     | 0x0005 | Writing the state of the targetted pin failed for an unknown reason                        |
| DIO – Set Mode Unsupported | 0x0006 | Setting the DIO mode to push-pull or sink-source is not supported                          |
| Invalid Command            | 0x0007 | The subcommand requested was outside of the valid range for the message kind               |
| Bad Message Kind           | 0x0008 | The message kind was not one of Valid Command Kinds                                        |
| Version – Read Failed      | 0x0009 | Reading the application version failed for an unknown reason                               |

The DIO command format is as follows:

| Bytes | Description                                                                                                                    | Options                                                                   |
| ----- | ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------- |
| 0     | The DIO action to perform on the device                                                                                        | Must be one of DIO Actions                                                |
| 1     | The bank of digital IO to target, or the number of devices                                                                     | Must be between 0 and the number of DIO banks available on the platform   |
| 2     | The pin index to get or set                                                                                                    | The output pin index starts at 0, the input index starts at 0 + n-outputs |
| 3     | The current state of the pin (if read), or the state to set (if written), or the mode to set (mode 0=sourcing, mode 1=sinking) | 0 or 1                                                                    |
| 4 – 7 | The edge-count of the pin, or the number of inputs/outputs                                                                     | 0 – MAX\_UNSIGNED\_INT (u32)                                              |

The digital IO command supports the following actions:

| Action      | Value (u8) | Description                                                                    |
| ----------- | ---------- | ------------------------------------------------------------------------------ |
| Get         | 0x00       | Read the state and count of an input, or just the state of an output           |
| Set         | 0x01       | Set the logical state of a digital output                                      |
| Set Count   | 0x02       | Set the edge count of a digital input to the passed value                      |
| Set Mode    | 0x03       | Switch between sink-source and open-collector drive mode on supported hardware |
| Num Devices | 0x04       | Reports the number of DIO banks available on the device                        |
| Num Outputs | 0x05       | Reports the number of outputs available to the indicated device                |
| Num Inputs  | 0x06       | Reports the number of inputs available to the indicated device                 |

#### <mark style="color:blue;">CAN</mark> <a href="#can" id="can"></a>

The Karbon 800 has an on-board CAN (Controller Area Network) 2.0 A/B interface. In general, the CAN bus consists of two main signal lines, CAN High and CAN Low. CAN High is biased at a high voltage potential of \~3.5 Volts and CAN Low is biased at a low voltage potential of \~1.5 Volts. The nominal voltage measured between the two signal lines is \~2.5 Volts, serving as a reliable indicator of the K800 CAN bus operational status. Additionally, the CAN bus operates in two states: dominant and recessive. Dominance is represented by logic level 0 and recessive is represented by logic level 1. The K800 CAN interface supports configurable bitrates from 100k – 1M and two message parsing modes: slcan and std.

*slcan*: an abbreviation for serial line can, is a virtualizing protocol used to transmit CAN messages over serial communication. This bridges the gap between the operating system and the unique differential signaling utilized in the CAN protocol. slcan makes the CAN bus appear as a network interface on the operating system, and can be even be identified as such when looking through the kernel buffer on Ubuntu via

```
sudo dmesg
```

Specifically, the K800 supports the following bitrates using slcan interface:

```
10     20     50     100    125    250    500    800    1000  Kbits/s
```

*std*: CAN bus send and receive messages are communicated in their native CAN format. This allows for direct low-level communication between the in-system K800 microcontroller and CAN-compatible devices. The std method of operating the CAN bus can be used without the need for intermediate serialization to communicate with an operating system.

Further details about the CAN bus can be found in the provided resources:

1. <https://en.wikipedia.org/wiki/CAN_bus#Frames>
2. <https://community.nxp.com/t5/NXP-Tech-Blog/101-Controller-Area-Network-CAN-standard/ba-p/1217054>

#### <mark style="color:blue;">Configuring the K80X as a CAN device</mark> <a href="#configuring-the-k80x-as-a-can-device" id="configuring-the-k80x-as-a-can-device"></a>

This section describes the physical connection and software configuration needed to set up the K80X platform as a CAN controller in either the Microsoft Windows or Ubuntu Linux based operating systems. Example programs are written in both Python (for both Windows and Linux) and Bash (for Linux).

**Materials Required:**

1. Hookup or twisted pair wires
2. 120 Ohm termination resistors (depending on the CAN setup)
3. CAN member devices compliant with CAN 2.0 A/B. In our example we will use a second K80X to act as the endpoint device.

**Example Network Implementation:**

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-d03fd9f7232df47a4eb47cba8a99fd7c7b3c2bff%2F0cdc61aca57986c13c7d67720dff4fc4b1fed813ae45bddce65ff87a29b5a7be.png?alt=media" alt=""><figcaption></figcaption></figure>

Diagram of a simplified CAN bus network. The figure above shows: 1) Two termination resistors at each end of the bus, 2) required endpoints of the bus acting as either transmitters or receivers, 3) High and Low CAN bus lines, and 4) additional (optional) network members connected on the same signal lines.

**Operation Instructions:**

The use of the K800 CAN bus can be achieved in four steps.

**Step 1**: Locate CAN High and CAN Low terminals on the 20-Pin header next to the system power button.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-ebf02113e07a3b76ebf28ccfb960e8ad76016cc5%2F5d052f67aeba99f4e1d7884838f39cb3de9e42322768e67205bff4505b29b2b7.png?alt=media" alt=""><figcaption></figcaption></figure>

**Step 2:** Connect CAN Low, CAN High, and (commonly used) ground wires to their designated locations using the Dinkle 0159-0320 20 pin connector. Additionally, bridge CAN Low and CAN High terminals with the proper termination resistor (120 Ohm in this example).

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-fc50bde35a0ed34dec832855bd8cfadf61c11b7a%2Ff67f161064cb30b3aa206b0bcc427814fd44dca88f5642edac0cad792059db99.png?alt=media" alt=""><figcaption></figcaption></figure>

**Step 3**: Configure the second K80X system with the same wiring connecting the CAN High and Can Low signals of each system. Ensure a second 120 Ohm resistor is used as close as possible to the second K80X 20 Pin connector.

**Step 4**: Activate the software interface to operate the CAN bus.

The GitHub repository here:

<https://github.com/onlogic/K800-CAN-supplemental-material>

Provides two utilities with instructions on controlling CAN bus parameters and sending/receiving CAN data in the code comments. Both the software utilities use slcan as the interface to communicate with the CAN bus. The installation commands for required dependencies are included in the header comments of each respective code file.

**Python3 CAN Utility \[Ubuntu and Windows Compatible] :** <https://github.com/onlogic/K800-CAN-supplemental-material/blob/main/k800_can_utility.py>

Usage on Windows:

```
python k800_can_utility.py [-h] [-m {s,r}] [-b {10,20,50,100,125,250,500,750,1000}] [-l {off,on}]
```

Usage on Linux:

```
sudo python3 k800_can_utility.py [-h] [-m {s,r}] [-b {10,20,50,100,125,250,500,750,1000}] [-l {off,on}]
```

<mark style="color:red;">NOTE: Run the Python CAN utility with sudo privileges on Ubuntu.</mark>

Output of —help flag for the Python command line argument:

```
python k800_can_utility.py --help

usage: k800_can_utility.py [-h] [-m {s,r}] [-b {10,20,50,100,125,250,500,750,1000}] [-l {off,on}]

K800 CAN Bus Utility

options:
  -h, --help            show this help message and exit

  -m {s,r}, --mode {s,r
                        send (s) or receive (r): send generated data or continually receive

  -b {10,20,50,100,125,250,500,750,1000}, --bitrate {10,20,50,100,125,250,500,750,1000}
                        CAN bus baudrate in kbps (ranges allowed by slcan: [10, 20, 50, 100, 125, 250, 500, 750, 1000]
  -l {off,on}, --leds {off,on}

Incorporate LED check functionality in program

```

Examples in:

Windows:

```
python k800_can_utility.py -m s -b 500 -l on

python k800_can_utility.py -m r
```

Linux:

```
sudo python3 k800_can_utility.py -m r -b 1000 -l off

sudo python3 k800_can_utility.py -m s
```

**Bash Script Utility \[Ubuntu Compatible Only] :**

<https://github.com/onlogic/K800-CAN-supplemental-material/blob/main/k800_can_utility.sh>

1\. First, set permissions to be executable by user who owns the file:

```
chmod u+x k800_can_utility.sh
```

2\. Then run the executable using:

```
./k800_can_utility.sh {s|r} <bit_rate> <led>
```

Examples:

```
./k800_can_utility.sh s 100 off
./k800_can_utility.sh r 20 on
./k800_can_utility.sh r  # Uses default bit_rate and no LED check
```

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-a138a2f0b85306e17ac06782ced4eea87650aeb5%2Fa1fdcea308064be748c35a37f3dc912b239078d1c5fa65ad3f8cb91c0f1528ca.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-ceaedaeeb1e06bf9cf9a6a66843ad94aa97cde20%2F4ad67b01c5e49820e65283fb9268e906d03c8e4f7efc0b263b6c1d4751b8352e.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-796be3e606e11c51e30a7428f0b98a999f048c60%2F5ab7d72aa0b3478b8bc5f27b1c8069f254262963d0e88a607b14d5f20dd0c811.png?alt=media" alt=""><figcaption></figcaption></figure>

Two channels, a blue channel representing CAN High and orange representing CAN Low. Both CAN High and CAN Low will default to a 2.5 nominal voltage in the absence of a signal. This is useful for debugging if there is uncertainty whether the signal is properly broadcasting.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-12de59075e7480ee6d09af511b9b61153dccca24%2F0fe5d0ba09ff59e3add24ff1e2e632479958c0f015dfc3d44481057b112ac32f.png?alt=media" alt=""><figcaption></figcaption></figure>

\[Optional] If the LED flags are active in either the Python script or the Bash script, the onboard LEDs on the K800 will turn on and off before and after each CAN session, respectively.

**Sample Program Outputs:**

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-03dea7eef33891dffe80743b4715b2bbeedbac4a%2F51c9b1cec65dec6aa44fd73f3cc7ece610260ced4e3088f0a98ad62d63543ae0.png?alt=media" alt="" height="314" width="959"><figcaption></figcaption></figure>

Initializing output from: *sudo python3 k800\_can\_utility.py -m r -b 100 -l on.* This indicates the proper eMCU Port location, Hardware ID, and Device.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-1f0163383237a4aa42c3e71ca6dd2766307b36c7%2Ff497705b677b5e56ed7e0ae62683f273e85e201a1c05ced0f1fde96dab85cdac.png?alt=media" alt="" height="379" width="954"><figcaption></figcaption></figure>

Terminal output of ‘*receive mode’* using the Python utility through the command:\
\&#xNAN;*sudo python3 k800\_can\_utility.py -m r -b 100 -l on*

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-6aca34ca07dcebe3b48ebbff40883c594b82ded6%2F64aab6afeef728a36cc0ac828fbe37f01a6ebb1974edb8184b2e01e45420fdc1.png?alt=media" alt="" height="385" width="925"><figcaption></figcaption></figure>

Terminal output of ‘*send mode’* using the Python utility through the command:\
\&#xNAN;*sudo python3 k800\_can\_utility.py -m s -b 100 -l on*

## <mark style="color:blue;">5- Support & Compliance</mark>

Do not open or modify the device. The device uses components that comply with FCC and CE regulations. Modification of the device may void these certifications.

### <mark style="color:blue;">5.1- Troubleshooting & FAQ</mark>

#### <mark style="color:blue;">Frequently Asked Questions (FAQ)</mark> <a href="#frequently-asked-questions-faq" id="frequently-asked-questions-faq"></a>

<details>

<summary><strong>Which LAN ports support PoE?</strong></summary>

The K800 can be configured with optional PoE hardware, adding PoE functionality to existing ports, or adding additional PoE ports. Check your configuration to see if your unit has PoE installed.

The optional PoE module supports the 802.3at standard @ up to 25.5 watts per port.

PoE can be added to the native Ethernet ports on either ports 1 & 2 (on the x2 LAN models), or ports 2 & 3 (on the x6 LAN models). Additional ports may be added with the Karbon Modbay cards.\
K800 series 2-LAN model:

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-bde4935e10e083c7fedd9b7060e794f39b672c84%2F284338edc8129cd2a7db6a3b542802288482e92b28b8b8c5b68cb46d6ffec5cc.png?alt=media" alt="" height="443" width="649"><figcaption></figcaption></figure>

K800 series 6-LAN model:

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-e2e45ddb4e18726ffb7c0d56ede1fa40378df001%2F81d0fd0e05fd9f73efc2cacf4d7f6e5d1c45ff7e33911c2e1aa993dc44d5e282.png?alt=media" alt="" height="447" width="655"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>What Operating Systems are supported?</strong></summary>

Windows 10 IoT 2021 and Windows 11 are supported. In most applications it is NOT necessary to disable the e-cores.\
\
The K800 also supports Ubuntu 22.04 for Intel IoT with Kernel version 5.15. Other Ubuntu and Kernel versions are not supported on the K800 series.

</details>

<details>

<summary><strong>What chipset do the Ethernet ports uses?</strong></summary>

The onboard LAN ports use the I225. The optional 10gig Modbay expansion card uses the X550.

</details>

<details>

<summary><strong>What Baudrate is supported on the K800 COM ports?</strong></summary>

The K800 series supports up to 115200 baudrate on the COM ports. Higher baud rates can be achieved by implementing the CAN port.

</details>

<details>

<summary><strong>How do I disable TurboBoost on the CPU?</strong></summary>

TurboBoost can be disabled in the BIOS of the system. Navigate to **Advanced** and set **Expert Mode** to **Enabled**. Then, go to:\
**Power & Performance** -> **CPU – Power Management Control** -> **Boot Performance** -> Set to **Max Non-Turbo Performance**

</details>

<details>

<summary><strong>How do I enable the external SIM slot?</strong></summary>

The K800 series can be configured with an internal modem, the [**AMIT series modems**](https://support.onlogic.com/product-documentation/components-and-expansion/wireless-connectivity/amit-mdg100-and-mdg200). If configured with a SIM card, this would be installed internally, directly on the modem. However the modem can be configured to use the external SIM slots to allow easier switching by users. It is recommended to configure the following BIOS setting to enable both external SIM slots:

**Setup Utility -> Advanced** page **-> PCH-IO -> OnLogic Feature Configuration -> SIM Card Muxing ->** Set to “**Mode 4**“\
Make sure to Save & Reset via the F10 function key or through the **Exit** page.

</details>

<details>

<summary><strong>How do I use the integrated video ports, instead of the GPU?</strong></summary>

The K800 series can be configured with a GPU. For some customers this is used to drive multiple high-resolution displays, and the video output will automatically output through the GPU. However in some cases you may want to use the GPU for specific computational applications, and use the integrated DisplayPorts. To enable this option, you will want to change the “Primary Display” output in the BIOS. Navigate to:

**Setup Utility -> Advanced** page **->** Set **“Expert Mode”** to **Enabled**\
Then go to:\
**Setup Utility -> Advanced -> System Agent (SA) Configuration -> Graphics Configuration -> Primary Display ->** Change to **“IGFX”**\
Make sure to Save & Reset via the F10 function key or through the **Exit** page.

</details>

#### <mark style="color:blue;">Motherboard Reset (Clear CMOS)</mark>

If the K800 fails to power on or is otherwise unresponsive, a CMOS reset may help. Follow the procedure outlined below to clear the CMOS.

1. Unplug the system completely – remove power and all peripherals
2. Use a long, thin tool, such as a straighten a paperclip
3. Locate the unlabeled CMOS reset hole next to the HDD LED
4. Using the tool/paperclip, depress the button inside for 30 seconds.

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fgit-blob-0fce82bcc6a2e1a591945e2968f3407da791bad4%2F6d28f6173f0dc8bacc45b14427acb8f494911bc1d0244cafdfc17980d0b3d396.png?alt=media" alt="" height="338" width="484"><figcaption></figcaption></figure>

5. Reconnect the system and turn it back on.
6. Do not touch the system for 2 minutes. It may reboot several times while it reconfigures the CMOS.
7. If successful, the unit should boot back up and run normally. It is now ready to use again. If the unit is still not responsive, reboot it one more time and then contact OnLogic Tech Support.

#### <mark style="color:blue;">**Can’t access the BIOS, System loads straight into the OS**</mark> <a href="#cant-access-the-bios-system-loads-straight-into-the-os" id="cant-access-the-bios-system-loads-straight-into-the-os"></a>

The system supports Fast Boot, which is a configurable BIOS setting. With Fast Boot enabled, the unit will disable booting to Network, Optical, and USB/removable drives. Video and USB devices (such as keyboards) will not initialize until the OS loads. This can make it difficult to reinstall an OS, or change any BIOS settings, and make the BIOS harder to access. To enter the BIOS follow the steps below for your specific OS.

**Windows**

From the Start Menu, hold Shift and click Restart to access the Recovery screen, then go to “Advanced” and select “UEFI Firmware Settings”. The system will reboot and allow access in the the BIOS. You may need to repeatedly press DEL/F2 keys while the system is rebooting.

**Linux**

From Terminal, run the following command:\
`systemctl reboot --firmware-setup`

This will trigger the system to reboot and allow access into the the BIOS. You may need to repeatedly press DEL/F2 keys while the system is rebooting.

Once you’ve accessed the BIOS, you can find the Fast Boot setting under the Boot tab.

#### <mark style="color:blue;">10Gb Ethernet Modbay disappears from OS</mark> <a href="#id-10gb-ethernet-modbay-disappears-from-os" id="id-10gb-ethernet-modbay-disappears-from-os"></a>

K800 series systems outfitted with the 10Gb Modbay (MODBAY-10GLAN01) may experience issues while in use, causing the ports to crash and become unusable. To fix this issue, download this file and follow the Update Instructions.\
\&#xNAN;*Note that the system must be booted into a Windows environment for this Update. A temporary Windows installation can be used on the system, or the unit(s) can be returned to OnLogic. Contact OnLogic Tech Support for RMA details.*\
\
\&#xNAN;***Orders shipped after 11/20/2023 already have this update applied***

[**10GLAN01 Upgrade Instructions**](https://static.onlogic.com/resources/firmware/documentation/OnLogic%20MODBAY-10GLAN01%20Update%20Instructions.zip)

#### <mark style="color:blue;">**10Gb Ethernet Modbay limited speed**</mark> <a href="#id-10gb-ethernet-modbay-limited-speed" id="id-10gb-ethernet-modbay-limited-speed"></a>

If you have a 10 Gb Modbay installed in your system, and it is not operating at full speed, you may need to update the ethernet controller firmware. It should be at least version 3.6 or higher.

There are different update steps depending on if you’re running Windows or Linux. Download the relevant steps and follow the steps in the downloaded file:

| [**Windows**](https://static.onlogic.com/resources/firmware/documentation/update10GB_firmware_WINDOWS.txt) | [**Linux**](https://static.onlogic.com/resources/firmware/documentation/update10GB_firmware_LINUX.txt) |
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |

#### <mark style="color:blue;">CAN bus connection instability</mark> <a href="#can-bus-connection-instability" id="can-bus-connection-instability"></a>

To resolve issues with CAN bus access on the K800 system, update to microcontroller firmware version 1.3.2+2 or higher [here](#microcontroller-updates).

### <mark style="color:blue;">5.2- Regulatory</mark>

#### <mark style="color:blue;">CE</mark> <a href="#ej8y7khrhko3" id="ej8y7khrhko3"></a>

The computer system was evaluated for medical, IT equipment, automotive, maritime and railway EMC standards as a class A device. The computer complies with the relevant IT equipment directives for the CE mark. Modification of the system may void the certifications. Testing includes: EN 55032, EN 55035, EN 60601-1, EN 62368-1, EN 60950-1, EN 50121-3-2, EN 60945 and UN Regulation No. 10 ISO 17650-2 & ISO 7637-2.

#### <mark style="color:blue;">FCC Statement</mark> <a href="#id-442unxm16958" id="id-442unxm16958"></a>

This device complies with part 15 of the FCC rules as a Class A device. Operation is subject to the following two conditions: (1) this device may not cause harmful interference and (2) this device must accept any interference received, including interference that may cause undesired operation.

#### <mark style="color:blue;">ISED</mark> <a href="#iogze6y7rwzd" id="iogze6y7rwzd"></a>

This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device.

Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes: (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.

**CAN ICES-003(A) / NMB-003(A)**

#### <mark style="color:blue;">UKCA</mark> <a href="#synek56no4wr" id="synek56no4wr"></a>

The computer system was evaluated for medical, IT equipment, automotive, maritime and railway EMC standards as a class A device. The computer complies with the relevant IT equipment directives for the UKCA mark.

#### <mark style="color:blue;">VCCI</mark> <a href="#t3o8wdc2llzs" id="t3o8wdc2llzs"></a>

This is a Class A product based on the standard of the Voluntary Control Council for Interference (VCCI). If this equipment is used in a domestic environment, radio interference may occur, in which case the user may be required to take corrective actions.

#### <mark style="color:blue;">Downloadable Documents</mark>

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FEs0CxA9Aj3JzxeAmGWSH%2FTAA%20Compliance.pdf?alt=media&token=13e92203-b5af-4bdf-aba3-290ed071727f>" %}

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FGYFj14pN3vlbtt8hf4RS%2FK8YY%203rd%20Ed%20CB%20Cert%20US-45790-UL.pdf?alt=media&token=252ba928-f8e1-4725-afae-2ba3ed0ab565>" %}

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fi7D8WyWgYtPNhqW6KTgB%2FMTBF%20Summary.pdf?alt=media&token=cc50ce88-f353-43af-8d31-9c112637c722>" %}

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FpOq5VFxUCuoNzvxkiznL%2FFCC%20%26%20Canada%20ISED%20DoC.pdf?alt=media&token=84abf071-38ca-4cb9-82a1-6f45dab895bb>" %}

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2Fs80d3xpaFw4wNl6k5rmr%2FCE%20DoC.pdf?alt=media&token=2801f8a5-dda9-4f1d-ae78-628179c0f9f4>" %}

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2F38gAHTlkTomsaeqyKFDE%2FIEC%20Shock%20and%20Vibration%20DoC.pdf?alt=media&token=6a54e5bc-9ba4-451f-ae7e-2558f48cb361>" %}

{% file src="<https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FJXXnc6u2Qh7KD1sjOHC9%2FMaritime%20Attestation%20of%20Compliance.pdf?alt=media&token=c3207eb2-a92b-41d3-8ba7-d7d2379516a1>" %}

### <mark style="color:blue;">5.3- Security Advisory</mark>

For the latest security advisories concerning OnLogic products, including vulnerability disclosures and necessary updates, please refer to our official Security Advisories page. It is recommended to regularly check this resource for critical security information.\
[**Access Security Advisories**](https://support.onlogic.com/support-articles/security-advisories)

### <mark style="color:blue;">5.4- Appendices</mark>

#### <mark style="color:blue;">Revision History</mark>

<figure><img src="https://3062424488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlLHqs7kbNoKOFTwGOfH6%2Fuploads%2FZL9p056MuNGLhpfpRTa3%2Fimage.png?alt=media&#x26;token=9fad4cf2-3538-4316-b2e2-323567e71f5f" alt=""><figcaption></figcaption></figure>