EMBEDDED FILE TRANSFER

Embed file transfer
into the hardware you build.

No need to develop a file transfer engine of your own -- integrate INNORIX into your device's existing software.
Build the transfer behaviour your product needs, and run it the same way after mass production too.

  • Industrial PC, controllerHeat sinks, comm ports, industrial gear
  • Robot, automation equipmentJoints, arm, gripper, production gear
  • Drone, mobile equipmentPropellers, embedded system
  • Smart TV, displayDisplay, panel, set-top gear
  • Edge AI, IoT gatewayAI compute, sensors, networking
  • Vehicle embedded systemVehicle control, infotainment, ADAS

WIDE COMPATIBILITY

Keep using the hardware and
environment you already run.

From Windows and Linux based industrial PCs to Android, ChromeOS, Tizen and Embedded Linux environments. Devices running on different operating systems can be set up to connect to the INNORIX Platform.

  • Windows
  • macOS
  • Linux
  • Android
  • ChromeOS
  • Tizen
  • Embedded Linux
  • Object Storage
  • Enterprise Storage
  • Kubernetes
WindowsSupported

The Agent can run on Windows 10, 11 and Windows Server.

Supported versionsWindows 10, 11
Windows Server
Architecturex86_64 / ARM64
Install methodAgent (EXE/MSI)
AuthenticationLogin / API Key
NetworkNo extra ports needed
(TCP 443)

INTEGRATION AND TESTING

From development to testing
on real hardware, move fast.

Integrate file transfer into your device's existing software,
then connect a test device to verify the real transfer.
Files move directly between devices with no intermediate server,
so there is no transfer engine of your own to build.

  • Connect devicesConnect a range of OSes
    and devices directly
  • Verify the real transferTest large or bulk files
    right away
  • Direct transferDevice to device,
    with nothing stored in between

Connected Devices

Add Device
NameTypeOSStatusLast Seen
Industrial PCDeviceWindows 11Connected1 min ago
Test ServerServerUbuntu 22.04Connected2 min ago
Edge GatewayDeviceEmbedded LinuxConnected3 min ago
Robot ControllerDeviceLinux (ARM64)Connected4 min ago

File Transfer Test

New Transfer
firmware_v2.4.img5.2 GB
Robot Controller/data/update

5.2 GB / 5.2 GB, 1.2 Gbps, 00:00:18

Transfer Completed

5.2 GB in 18 seconds

Average 1.2 Gbps

MASS DEPLOYMENT

Validate on one device,
then deploy the same way to thousands.

Validate the connection method and configuration on a single device, then apply it to a mass deployment.

Register devices automatically during production or initial setup, and connect them to the same transfer environment without configuring each one by hand.

Deployment Package

  • Connection Settingsconnect.conf
  • Authenticationauth.key
  • Device Configurationdevice.conf
  • Deployment Scriptdeploy.sh
DeployDevice-001Device-002Device-003Device-N

Device Registration

Auto Registration
Device NameModelStatus
Device-001Model AConnected
Device-002Model AConnected
Device-003Model BConnected
Device-004Model BConnected
  • Validate the connectionCheck the connection method, credentials and
    transfer settings on a representative device.
  • Prepare the deployment packageBundle the validated connection settings, credentials
    and the install files it needs into one package.
  • Register devices automaticallyApply the package during production or install and
    devices register themselves on the platform.
  • Start operatingApply a transfer policy to registered devices and
    manage their connection state and run results.

LIFECYCLE OPERATIONS

Manage your devices' file transfers
in one place, even after they ship.

Check the connection state and transfer results of devices installed at customer sites in one place. From remote file browsing, configuration

deployment and log collection to retrying a failed transfer, run repetitive file work centrally.

  • Check connection stateSee every device's connection state
    and transfer results in real time
  • Browse and collect files remotelyCollect logs and data files
    from the field remotely
  • Deploy configuration filesDeploy settings and update files
    to multiple devices at once
  • Retry failed transfersResume an interrupted transfer, or
    resend only the files that are missing

Runs

New Run
NameTypeTarget DevicesStatusProgressStarted

Run details

FailedView logs

Error retry

TypeUpload
Target Devices4 devices
File Size1.1 GB
StartedOct 9, 14:03
Completed–
DurationRetrying

Target devices

View all
Device-001Running
Device-002Running
Device-003Running
Device-004Running

TECHNICAL FAQ

Frequently asked questions

Which industrial operating systems does INNORIX support?

Connection can be set up for environments such as Windows, Linux, Android, ChromeOS, Tizen and Embedded Linux. Actual Agent support has to be confirmed per operating system version, CPU architecture and device specification.

Does the Agent always have to be installed on an industrial device?

Ordinary device connection uses the INNORIX Agent. For a device it cannot be installed on, a technical review is needed to see whether a separate integration is possible.

Can it be used on ARM-based embedded devices?

ARM support depends on the operating system, the CPU architecture, the runtime and the Agent builds provided. Compatibility has to be confirmed against the device specification.

Can files be collected without visiting the field device?

If the device is connected to INNORIX and there are access rights to the file path needed, files can be browsed and transferred remotely.

Can hundreds of devices be registered automatically?

Bulk registration can be set up by deploying the Agent together with its settings. How it is deployed depends on how the devices are operated.

Can files transfer directly between an industrial device and a central server?

In supported network and connection environments, direct device-to-device file transfer can be set up. The connection method and the network policy may need review in advance.

Can files be accessed while a device is offline?

While a device is offline, real-time file access and transfer cannot be carried out. What can run after it reconnects, and the waiting policy, have to be confirmed against your setup.

Can devices across several sites be managed in one place?

The devices connected and the transfer execution state can be seen together in Devices and Runs in INNORIX Studio.

Can device logs and configuration files be collected automatically?

Use INNORIX's transfer flows with schedule and condition settings to set up repeated file collection. The actual device paths and permission conditions have to be confirmed.

What information do you need to apply this to our industrial devices?

The operating system and version, the CPU architecture, memory and storage, how it connects to the network, and the size and frequency of the files to transfer are enough to assess whether it can be applied.