1. Home
  2. OnLogic Systems
  3. Industrial Fanless Line
  4. Helix HX310 and HX330 Technical Resources

Helix HX310 and HX330 Technical Resources

Drivers and Manuals

User Manual

BIOS Manual

Drivers (Windows 10) (manual install via Device Manager)

Linux Support

This model uses the new Intel GPY115/EC1000S Ethernet controller provided by the Elkhart Lake platform. Currently no mainstream Linux distributions have driver support for the Ethernet ports. Linux is not supported on this model.

PXE boot support

Intel has not yet provided drivers to enable PXE booting (network booting). PXE is currently not supported.

Frequently Asked Questions (FAQ)

How do I install the wall mount or DIN mount

Refer to page 26 in the system manual for mounting diagrams

How much power does this system draw?

The system draws approximately 26 watts at full load. We recommend a 36 watt or higher power supply.

How do I install drivers?

Download the drivers using the link above and then follow this guide to install them.

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 bottom 3 Phillips P2 screws from the back of the system
  • Remove the two screws from the bottom of the case
  • Pry the bottom lid off using a flathead screwdriver
  • The internals of the system are now accessible, including the RAM, Primary SSD, Secondary SSD, WiFi card, and CMOS battery.


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.

  • Follow the Disassembly Guide directly above
  • Locate the jumper blown shown here in purple

  • The top jumper in this image controls auto power on. It is called the AT/ATX jumper.
  • Use needlenose pliers or your fingernails to grab the jumper and remove it from the pins.
  • Reinstall the jumper as shown.
  • Auto power on is now enabled (AT Mode)

Clearing the CMOS

  • Follow the Disassembly Guide directly above
  • Locate the jumper blown shown here in purple

  • The bottom jumper shown here (closest to the outside of the system) will clear the CMOS.
  • Use needlenose pliers or your fingernails to grab the jumper and remove it from the pins.
  • Reinstall the jumper as shown.
  • Leave the jumper in place for 30 seconds.
  • Restore the jumper to its original position

Replacing the CMOS battery

  • Follow the Disassembly Guide directly above
  • The CMOS battery is held in by a light adhesive. Pull the battery off the board and take care not to damage any components on the board.
  • Pull the wire straight up to unplug the battery from the board.
  • Plug the new battery into the board
  • Peel off the adhesive and stick it in place so it does not rattle around.
  • The BIOS settings and time will be reset when the unit is powered back on the next time.

Using the TPM 2.0 Module

As with other newer model systems, this model includes a firmware TPM by default. It functions similarly to a TPM 2.0 module. If the optional dedicated TPM 2.0 module is added to the system, the firmware TPM will need to be disabled to allow it to function.

The firmware TPM can be disabled in the BIOS:

  • Power on the system and press the Del key to access the Front Page menu.
  • Choose the Setup Utility option.
  • Under the advanced tab, open the chipset configuration menu.
  • Disable Platform Trust Technology
  • Press F10 to save and exit.
  • The dedicated TPM will now be functional. You can verify it is detected in TPM.MSC or Device Manager.

Digital IO and CAN

The Helix 300 and 310 systems offer optional CAN bus and isolated Digital IO 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 OS is transparent to the user. This interface may be used to send and receive CAN messages alongside setting and reading the Digital IO. 

Quickstart

Requirements: An HX300 or HX310 with Windows and the latest HECI driver. The HECI Windows driver is provided and supported by Intel, and will be preinstalled on HX300 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.

  1. Download the HX300’s hardware control command line application.
  2. Open a command window, and navigate to the location of the downloaded file.
    1. Press the Windows Key + R
    2. Type cmd.exe and hit Enter
    3. In the window that opens navigate to the download location:
      1. e.g.  cd C:\User\Username\Downloads
  3. Run some example commands:
    1. hwc.exe --help to show commands and usage.
    2. hwc.exe can send 123 11223344 to send a CAN message.
    3. hwc.exe dio write 0 true to set the state of output zero as high.

Application Integration

While in many cases it is sufficient to make calls to the hx300’s command line utility, OnLogic is working on example code for C++ and Rust demonstrating how to send and read messages from the HECI driver. This section will be updated when the code has been released.

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:

BitsDescription
0 – 7HECI Command Identifier:
0x01: System Information:
0x02: Digital IO
0x04: Can Bus
8Set as ‘1’ if this message is a response from the PSE
9Set as ‘1’ if this message contains a valid data body
10 – 25Packed ‘argument’ for a given command. Format depends on the command identifier. 
26 – 31Status of last command
32 – 39Data format of body:
0: Raw data
1: Version information
2: CAN message
4: DIO message
7: ASCII String
40 – 168Body of message data, usually in the form of another packed structure.
Updated on September 14, 2021

Was this article helpful?

Related Articles

Need Additional Support?
Can’t find the answer you’re looking for? Don’t worry, we’re here to help!
Contact Support