INDUSTRIAL DEVICE FILE TRANSFER
Transfer files on industrial devices
directly, from anywhere.
From factory equipment to industrial PCs and embedded devices. Connect INNORIX and you can transfer the logs, configuration files and operational data stored on field devices remotely.
Without developing a separate file transfer program for each device, browse the files on a connected device and move them straight to the system that needs them.
CONNECT YOUR DEVICE
Install the Agent on a device
and connect it right away.
Install the INNORIX Agent on an industrial device and link it to your account, and you can manage that device remotely.
An ordinary device connects by signing in after the Agent is installed, or through QR authentication; devices deployed in volume can be configured to register automatically.
- Sign-inInstall the Agent, sign in with your account and register the device.
- QR authenticationDevices that are hard to type on connect through QR authentication.
- Bulk registrationDeployed devices register themselves during installation.
- Install INNORIX AgentInstall package for the device environment
- Sign in with your account after installing the AgentAccount authentication
- Device: Factory-Edge-01Device details confirmed
- Connected to StudioRegistered in the Studio device list
- Install INNORIX AgentInstall package for the device environment
- Sign in with your account after installing the AgentAccount authentication
- Device: Factory-Edge-01Device details confirmed
- Connected to StudioRegistered in the Studio device list
BROAD COMPATIBILITY
Different operating systems,
one platform to connect them.
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.
Instead of operating a separate file transfer system per device, manage the devices in supported environments from a single Devices list.
- Windowsx64 · ARM64
- Linuxx86_64 · aarch64
- Androidarm64-v8a · armeabi-v7a
- ChromeOSx86_64 · aarch64
- Tizenarmv7l · aarch64
- Embedded Linuxx86_64 · aarch64 · armv7linnorix-agent-embedded.tar.gz
- Check supported architectures and Agent installation requirements
- Install package and connection guidance for the device environment
REMOTE FILE ACCESS
Collect the files inside a device
without going to the site.
You do not have to visit in person every time you need to check a log or a diagnostic file stored on a field device. Browse the permitted paths on a connected device and transfer the files you need to a central server or an analysis environment.
Even with devices spread across several factories and remote sites, collect and check files remotely.
- Factory AFactory-Edge-01 · Embedded LinuxOnline
- Factory BFactory-Edge-02 · LinuxOnline
- Remote SiteRemote-Gateway-03 · AndroidOnline
/data/gateway/Available
- uplink.logSelected
- sensor-dump.bin
- diagnostics.zip
MASS PROVISIONING
Hundreds of devices,
without registering them one by one.
Where industrial devices are produced in volume or deployed across many sites, signing in and registering each device individually is inefficient.
Deploy the Agent together with a configuration file and have each device register itself with INNORIX as it is installed. That removes the work of connecting every new device by hand.
Deployment packageAutomatic registration per device
- Agent installerInstall package for the device environment
- ConfigurationConnection targets and permitted paths
- Provisioning credentials••••••••••••
New devices registered
- Factory-Edge-101Embedded LinuxConnected
- Factory-Edge-102Embedded LinuxConnected
- Factory-Edge-103Embedded LinuxConnected
- Deployment package prepared
- Device installation
- Automatic registration per device
DIRECT DEVICE TRANSFER
Device to device,
move files directly.
There is no need to upload a file from an industrial device to a relay store first and download it again. Transfer files directly between connected devices and cut out the unnecessary copies between the field and the central system.
From factory equipment to an analysis server, from a central server to a field device. Move files in whichever direction you need.
- Industrial Device/device/data/Selected
- production-log.zip4.8 GB
- Central Server/data/factory/
- production-log.zip4.8 GB
production-log.zipCompleted
- Industrial Device
- Central Server
CENTRALIZED DEVICE OPERATIONS
Run distributed industrial devices
from a single screen.
Check the status of devices connected across regions and sites in Studio, and manage their file transfer results in one place.
Review each device's connection state and its recent transfer records to see which device a file moved from.
- Factory-Edge-01Embedded LinuxOnline
- Factory-Edge-02LinuxOnline
- Remote-Gateway-03AndroidOffline
Factory-Edge-013 today
- sensor-data.csv→ Central Server · 10:24:11Completed
- diagnostics.zip→ Analysis Server · 09:12:04Completed
- device-config.json← Central Server · 08:55:18Completed
/var/log/device/ · /device/data/
GET STARTED
Connect your industrial devices to INNORIX.
Check the supported operating systems and device environments, then install the Agent. Once a device is connected you can browse and transfer its files from Studio.
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.
Every one of these capabilities,on a single platform.
The capability on this page is one of the many file transfer features INNORIX Platform provides. From file transfer to automation and unified operations, try every feature free.
Start FreeLooking at connecting industrial devices?
We check your devices' operating systems and CPU architectures and review the connection methods that apply with you.
- Agent requirements per OS and CPU architecture
- Technical review of embedded and special devices
- Guidance on bulk device registration and deployment