This article also applies to the IGN210.
Documents and Downloads
PSE Guide (for DIO, CAN, Ignition sensing)
– Using the K400 PSE on Windows 10
– Using the K400 PSE on Ubuntu
Drivers
Version | Release Date | Link | Release Notes |
---|---|---|---|
Windows 10 | 10/11/2023 | Download Drivers | Includes updated PSE drivers. *Note that these drivers require BIOS version A070 or newer. It is recommended to update to the latest BIOS version listed below. |
BIOS Updates
Version | Release Date | Link | Release Notes |
---|---|---|---|
A077 | 03/07/2024 | Download BIOS | Fixes PSE Feature troubles from 1.76 and enables 2x COM capability. Includes regular stability improvements. |
Hardware Control Application (HWC)
Version | Release Date | Link | Release Notes |
---|---|---|---|
v1.2.1 | 10/11/2023 | Download HWC | Fixes issue with Version-Check warning. * Note that the CAN baudrate is fixed at 1M. Please see our C-Based PSE-Examples for setting the baudrate programmatically. |
Frequently Asked Questions (FAQ)
The K400 series use the i210-IT network controllers. They support speeds of 10/100/1000 Mbps.
Windows 10 IoT Enterprise and Ubuntu 20.04 IoT are the only supported OSes at this time. Windows 10 Pro will install but is not supported. For Ubuntu, please refer to Using the K400 with Ubuntu for Intel Iot.
Refer to page 21 in the user manual for mounting diagrams
The system draws approximately 35 watts at full load. We recommend a 60 watt or higher power supply. Refer to page 28 of the user manual for further power consumption details.
Download the drivers using the link above and then follow this guide to install them.
Note: The secondary SIM slot on the K430 is not compatible with OnLogic modems. It is for future expansion. The primary SIM slot can be mapped to either the mPCIe or m.2 slots via a BIOS setting.
Please refer to the information below on how to access the CAN and DIO modules. For Ubuntu applications, refer to Using the K400 PSE on Ubuntu for Intel Iot
Note: Packages such as SocketCAN are not supported.
Enabling Auto Power on
The system 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.
- Power on the system and immediately press the Del key a few times until you see the “Front Page” menu
- Arrow down and choose “Setup Utility” by pressing enter
- Under the advanced tab, open the “RC Advanced Menu”
- Open the “PCH-IO Configuration” menu
- The auto power on setting is called “State After G3”.
- Set it to S0 State to enable auto power on
- Set it to S5 State to disable auto power on
- Press F10 to save and exit. Then you are all set.
Disassembly Guide
Opening the system does not void the warranty, however, some precautions are necessary to avoid damaging the unit. Any damaged caused will not be covered by 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
- Remove the 4 Torx T8 screws from the bottom of the chassis
- Use a small flathead screwdriver to pry the bottom plate off using the notch.
- If the unit has one of the K430 expansion modules, remove the 4 screws from the midplate and lift it straight out.
- If the system has the optional x2 LAN expansion board, remove the x2 additional screws as well.
- The internals of the system are now accessible.
Troubleshooting
Clearing the CMOS
If the system fails to power on or output video, clearing the CMOS can often help. To clear the CMOS, the system needs to be opened and an internal switch needs to be pressed.
Opening the system does not void the warranty, however, some precautions are necessary to avoid damaging the unit. Any damaged caused will not be covered by 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
- Power off and unplug the system. Disconnect all ports.
- Remove the 4 Torx T8 screws from the bottom of the chassis
- Use a small flathead screwdriver to pry the bottom plate off using the notch.
- Locate the golden clear CMOS button
- Hold down the clear button for 30 seconds.
- Re-assemble the system. Do not over tighten the screws.
- Re-connect the system and power it on.
- Do not touch it for 2 minutes. Wait and see if it outputs video.
- If not, contact OnLogic tech support for an RMA using the button on the right sidebar. >
Windows Bluescreen after BIOS update
After updating to BIOS version A074 or later, Windows may display a Bluescreen error with message “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED”. You will need to adjust the BIOS settings to make it work.
Go into the BIOS and change the following x2 options
- Advanced -> Expert mode -> Enabled
- Advanced -> RC advanced menu -> PCH-IO Configuration -> PinCntrl Driver GPIO Scheme -> Disabled
Press F10 to save the BIOS settings and reboot. If the OS is able to recover, it should boot up. If not, you may need to reinstall the Windows OS.
Ubuntu boots up slowly / doesn’t turn off completely
If you are having issues with Ubuntu randomly crashing, taking several minutes to boot up, or an issue with not fully turning off, try Enabling the PinCntrl Driver GPIO Scheme:
- Access the BIOS by pressing DEL while the system is booting up
- Enable Expert Mode under Advanced
- Enable Pin Control Driver GPIO Scheme:
Advanced/
RC AdvancedMenu/
PCH-IO Configuration/
PinCntrl Driver GPIO Scheme -> Enable - Press F10 to
Save & Exit
Automotive Ignition Timings
Feature Overview
The ignition sense feature can be used to turn the Karbon unit on and off with a vehicle’s ignition. It can also be used in non-automotive applications using a switch instead.
An example configuration is shown below for Windows. 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.
Enabling and controlling ignition sense
- Download the control application from the link above
- Run Command Prompt as administrator
- Navigate to the directory where you put the control application.
- Example: In this picture, the HWC file is saved to the Desktop. Navigating there allows access to the file.
- Once you have navigated to the directory that the HWC file is located, execute the following commands in order:
hwc ign set ignition-sense -v 1
hwc ign set low-power-mode -v 1
hwc ign set shutdown-timer -v 10
hwc ign set startup-timer -v 10
hwc ign set hard-off-timer -v 3000
Change Windows Settings
- 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.
- Windows “fast startup” will interfere with ignition sensing, so this should be disabled.
- Power down the system and you can turn it back on by connecting positive power to the IGN pin. This will give you a basic ignition timings setup with 10 second delays. Reference the table below for customizations.
Ignition Sensing Commands
hwc ign set command -v value
hwc ign get command
Command | Description | Possible Values |
ignition-sense | Enables or disables ignition sense | 0=off, 1=on |
low-power-mode | Reduces idle power consumption (recommended on when ignition sense is used) | 0=off, 1=on |
startup-timer | The delay between IGN power being applied and the unit turning on | 1-2147483647 (seconds) |
shutdown-timer | The delay before Windows is shut down when IGN power is cut | 1-2147483647 (seconds) |
hard-off-timer | After the shutdown timer has completed, power will be fully cut after X number of seconds. This is useful in case the system freezes at shutdown. | 1-2147483647 (seconds) |
low-voltage-timer | The low voltage shutdown can be delayed by X number of seconds. A value of at least 10 is recommended to avoid voltage drop related shutdowns – i.e. when the engine is started. | 30-2147483647 (seconds) |
shutdown-voltage | The unit can shut itself down when a certain low voltage threshold is reached. This helps prevent over discharging a battery. (1150 => 11.5V) | 600-4700 (centi-volts) |
DIO and CAN
The Karbon K410 and K430 series systems offer CAN bus and (optionally) isolated DIO (Digital Input/Output) support. This functionality is through the processor’s supporting ARM microcontroller, known as the Programmable Services Engine (PSE).
The PSE is isolated from the core processor, runs its own OS (Zephyr RTOS), but can be sent messages over the system’s Host Embedded Controller Interface (or HECI). The Zephyr OS is transparent to the user. This interface may be used to send and receive CAN messages alongside setting and reading the Digital IO.
Note: Packages such as SocketCAN are not supported.
Quickstart
Requirements: A K410 or K430 with Windows and the latest HECI driver. The HECI Windows driver is provided and supported by Intel, and will be preinstalled on K410 units purchased with Windows. If Windows is installed by the user, the driver is included with our driver package linked at the top of this page.
Note: We recommend you update to the latest BIOS version for the best compatibility with this application.
- Download the K410’s hardware control command line application.
- Open a command window, and navigate to the location of the downloaded file.
- Press the Windows Key + R
- Type
cmd.exe
and hitEnter
- In the window that opens navigate to the download location:
- e.g.
cd C:\User\Username\Downloads
- e.g.
- Display the built-in help text:
hwc.exe --help
DIO Examples
The (optional) MOD110 digital input/output (DIO) expansion adds up to eight digital inputs and outputs to the system, and an additional CAN port. It also optionally provides support for pulse width modulation (PWM) on three of the eight digital output pins, and support for using a quadrature encoder peripheral (QEP) in place of the first and/or second group of three digital inputs.
See our dedicated DIO article on how to get started with theexpansion module, the MOD110.
Application Integration
See Using the K400 PSE with Ubuntu for information about C sample code and a reference on command packing and communication.
The HECI interface uses packed structures to send data between the host and PSE. Specific type structures are provided in the sample code, but an outline of the message format is available below:
Bits | Description |
0 – 7 | HECI Command Identifier: 0x01: System Information: 0x02: Digital IO 0x04: Can Bus |
8 | Set as ‘1’ if this message is a response from the PSE |
9 | Set as ‘1’ if this message contains a valid data body |
10 – 25 | Packed ‘argument’ for a given command. Format depends on the command identifier. |
26 – 31 | Status of last command |
32 – 39 | Data format of body: 0: Raw data 1: Version information 2: CAN message 4: DIO message 7: ASCII String |
40 – 168 | Body of message data, usually in the form of another packed structure. |