Virtual Filesystem

Understanding the virtual filesystem that enables the deep integration of the pilot platform

What is it good for?

The virtual filesystem enables you to read data from and write data to the Pilot Modules and Pilot Mainboard. It is the main way (other than through the App when connected to the cloud through PilotNode) of interacting with the hardware.


The root directory of the pilot virtual file system is located in: /proc/pilot

Folder Structure:

  • module1
    • eeprom
  • module2
    • eeprom
  • module3
    • eeprom
  • module4
    • eeprom
  • plc
    • varconf
    • vars

Root Folder


Module Folders


eeprom Folder


The files in the eeprom folder map the eeprom of the module directly to the filesystem. That means when you read from one of the files, or write to it, the Pilot Mainboard accesses the internal memory of the module and reads from it/writes to it.

The folder contains the following files:

  • uid
  • hid
  • fid
  • user01-user10

If you modify the fid or hid file content, pilot-config cannot identify the module correctly. Please handle these fields with care!

uid - Unique identifier. This file can only be read. It is a unique number for each module.

hid - Hardware Id. The hardware this module identifies as.

fid - Firmware Id. The currently configured firmware for that module.

user01-user10 - User Defined Fields. Each of the files can store 8 bytes.

PLC Folder


This folder contains PLC related information and provides you with a powerful way to interact with PLC variables.

TODO: what is PLC ?!

results matching ""

    No results matching ""