AIS Edge Device: connect every machine, keep every record.
The edge runtime and engineering studio from Automation & IIoT Services. AIS Edge reads your PLCs, OPC servers and line devices, runs your production logic as flowcharts anyone can read, and delivers every record to your databases, brokers, MES, ERP and historians, through network outages and power cuts.
Developing · pilots welcome
AIS Edge Studio on a simulated production line, with a narrated guided tour in English or Japanese. It runs entirely in your browser; nothing is sent anywhere.
- Every connection, from PLCs to AWS and Azure, is a native client written by us from the published standard: no middleware, no ODBC or JDBC, no relay PC, no Java or Docker requirement
- 90+ device protocols: PLCs, drives, robots, meters, substations and buildings, every device TAKEBISHI DeviceXPlorer connects (400+ device types) by tag name over DxpLink, plus an EtherCAT® master and CC-Link IE stations in software on a standard Intel port (in testing, simulation only)
- Tags taken by label name straight from GX Works2 and GX Works3 projects, so nobody retypes an address list
- Store-and-forward on every output: a record is deleted only when the far end confirms it, through broker, database and network outages and a power cut mid-send
- Jobs drawn as standard flowcharts with 28 triggers and 66 actions, checked by the engine's own rules before they reach the device
- Secure by default: no default password, four user roles, HTTPS, TLS with certificate checks on every connection, one allow list for every service, one audit log; LDAP / Active Directory and single sign-on
- One portable C program with fixed memory on Linux or Windows industrial PCs; about 2 ms SLMP round trip in the lab. Studio, messages and dashboards in English and Japanese
Production logic people can read.
A job is one trigger and one flowchart: start, actions, yes/no decisions, an error path, end. The classic PLC request and completion handshake is a trigger, not code. One-Shot runs a job with a step-by-step trace, and a built-in plant simulator means jobs and dashboards are designed and tested before a device exists. Studio runs in any browser, served by the device; we draw from common industry tools to help influence its design.
Where every connection stands.
Every protocol is written by AIS from its published specification and ships with a simulator and byte-exact tests. We sort them into three groups, and say plainly which one each is in.
Released / verified
Run against the real product, server or reference test suite.
- MELSEC SLMP on a real iQ-R and iQ-F; TAKEBISHI DeviceXPlorer over DxpLink, client and server (DeviceXPlorer 7.7); another AIS Edge over TLS
- OPC UA server with historical access, alarms and conditions, and methods
- SQL Server, PostgreSQL, MySQL, MariaDB, Oracle, SQLite, MongoDB and InfluxDB
- MQTT, Kafka, AMQP 1.0 and 0-9-1, STOMP, NATS with JetStream, JMS on ActiveMQ Classic and Artemis, CoAP and LwM2M with DTLS
- AWS request signing (AWS's published test suite); the FTP / FTPS server on the device
In testing
Built and passing in simulation or against independent open-source peers; no real device or live service yet.
- EtherCAT® master, EtherCAT TSN; CC-Link IE Field Basic, CC-Link IE TSN Class A / B, and CC-Link IE Field and Controller software stations; Ethernet TSN and gPTP
- The other PLC families, drives, instruments, robots and machines
- Substations, meters and buildings
- OPC UA and DA clients, the clouds, MES and ERP presets, historians
- Signed updates and fleet rollout, LAN settings with automatic revert, the Windows service and container image
Planned
Next on the list, or waiting for hardware or partners.
- On real hardware next: EtherCAT with other vendors' devices and sub-millisecond cycles on Intel i210 / I225, then the ETG conformance test; CC-Link IE Field and Controller against a Mitsubishi station; CC-Link IE TSN against a Mitsubishi manager station
- In development: CC-Link IE passive tap (data collection by listening only); EtherCAT SubDevice
- New drivers: Mitsubishi MELFA robots, FANUC robots natively, FANUC FOCAS and Mitsubishi CNC adapters
- Platforms: Mitsubishi C Controller and RD55UP packages
AIS is a member of the EtherCAT Technology Group (ETG) and the CC-Link Partner Association (CLPA). A protocol with a conformance program is claimed in a shipping product only after its conformance test. EtherCAT® is a registered trademark and patented technology, licensed by Beckhoff Automation GmbH, Germany.
Every PLC on the floor, and the devices around it.
Each driver is written from the vendor's published protocol document and ships with its own simulator and byte-level tests. Verified means tested against the real product, server or a reference test suite. Interop means tested against a named independent open-source implementation; Supported means tested against a simulator built from the specification, with field validation on customer equipment to follow; Assumed means built from public documentation, with a test on a real device still to come. Interop, Supported and Assumed together are what the status summary above calls in testing. Planned and In development are on the roadmap below.
| Protocol | Devices | Status |
|---|---|---|
| SLMP / MC protocol 3E and 4E | Mitsubishi MELSEC iQ-R, iQ-F, Q, L; labels read by name on iQ-R | Verified iQ-R and iQ-F in our lab |
| MELSEC remote password, routes and target CPUprotected CPUs, other stations, multi-CPU systems, extended file registers (ER), 4E pipelining | MELSEC iQ-R, Q, L | Supported |
| MC protocol 1E | Mitsubishi FX3 Ethernet modules, A-compatible | Supported |
| MELSEC MC protocol, serial1C, 2C, 3C, 4C frames; FX computer link | Q/L/iQ-R serial modules, FX | Supported |
| OPC UA clientBasic256Sha256, Aes128, Aes256; sign and encrypt; subscriptions; method calls | Any OPC UA server: Siemens S7-1200/1500, B&R, Bosch Rexroth, Rockwell, Beckhoff, OPC gateways and SCADA | Interop independent OPC UA stack |
| OPC DA clientDA 2.05a and 3.0, local or DCOM; Windows | Any classic OPC DA server | Supported |
| TAKEBISHI DeviceXPlorer over DxpLinkclient and server, by tag name | Every device DeviceXPlorer connects (400+ device types); AIS Edge also serves its own tags to DeviceXPlorer as a DxpLink server | Verified DeviceXPlorer 7.7, both ways |
| Modbus TCP and RTU | Any Modbus device; meters, drives, IO-Link masters | Supported |
| Omron FINS (UDP / TCP) | Omron CS / CJ / CP / NJ / NX | Supported |
| Beckhoff ADS | TwinCAT 2 / 3, including symbolic access | Supported |
| Panasonic MEWTOCOL-COM | FP7, FP0H, FP-XH | Supported |
| LS ELECTRIC XGT | XGK, XGI, XGB | Supported |
| YOKOGAWA FA-M3 PC link | FA-M3 | Supported |
| KEYENCE KV Host Link | KV-8000 / 7000 / 5000 / Nano | Assumed device names checked against the KV-8000 manual; command formats pending |
| SHARP SATELLITE JW computer link | JW20H, JW30H, JW300 (JW-255CM, JW-25TCM, Z-339J, JW-300CM) | Supported |
| TOSHIBA PROSEC T computer linkserial, and EN311 Ethernet | PROSEC T1, T2, T3, T3H | Supported |
| JTEKT TOYOPUC computer linkall 2ET commands, relay through FL-net and link modules | TOYOPUC PC10, PC3J, Nano, Nano 10GX | Supported |
| EtherNet/IP CIPtags by name, UDTs, arrays; CIP objects | Allen-Bradley Logix 5000, Micro800; OMRON NJ/NX | Interop cpppo, OpENer |
| EtherNet/IP PCCC | SLC 500, MicroLogix, PLC-5 | Interop cpppo |
| Siemens FETCH/WRITEISO-on-TCP (RFC 1006) | S7 CPs 343-1 / 443-1 | Supported |
| Allen-Bradley DF1full and half duplex | SLC 500, MicroLogix, PLC-5 | Supported |
| OMRON Host LinkC-mode and FINS | OMRON serial ports | Supported |
| Koyo DirectNET | AutomationDirect DL205 / DL405 | Supported |
| Siemens 3964(R) / RK 512 | CP 340 / 341 / 441 | Supported |
| GE SNP-X | GE Series 90-30 / 90-70 | Supported |
| Opto 22 Optomux | Optomux digital and analog bricks | Supported |
| FATEK FBs | FBs / FBE | Supported |
| Unitronics PCOM | Vision / Samba / UniStream | Supported |
| Opto 22 OptoMMP | SNAP PAC, groov EPIC / RIO | Supported |
| MTConnect and SHDR | Machine tools: agents and adapters; the edge is an MTConnect agent too | Interop MTConnect Institute cppagent, both ways |
| SNMP v1 / v2c / v3 | Switches, routers, UPS, PDUs; traps start jobs | Supported |
| CoAP and LwM2MDTLS 1.2 with keys or certificates | Constrained IoT devices; OMA and IPSO objects | Verified libcoap, Californium, Leshan |
| Line devicesTCP, UDP, serial, HTTP | Barcode and RFID readers, scales, label printers, vision systems, robots | Supported |
| Any device, and messages the PLC sends | ||
| User Protocolrequests, replies, checksums, points and areas, described in Studio without code | Simple serial and Ethernet devices without a driver: scales, drives, controllers | Supported |
| MELSEC fixed-buffer and socket messagesBUFSND, SOCSND | MELSEC Ethernet modules and built-in ports sending to the edge | Supported |
| OMRON FINS messages from the PLCSEND, RECV, CMND | OMRON CS / CJ / CP / NJ / NX | Supported |
| Rockwell CIP messages from the PLCMSG instructions; PCCC typed reads and writes | Logix, CompactLogix, Micro800; SLC 500, MicroLogix, PLC-5 | Supported |
| Bluetooth LE beaconsiBeacon, Eddystone; presence, detected and lost events | Beacons on people, carts and tools | Assumed adapter test pending |
| Keyboard-wedge scanners | USB barcode scanners that type like a keyboard (Linux) | Supported |
| GSM modemreceived SMS start jobs; signal strength | Serial GSM / LTE modems with AT commands | Supported |
| Folder watch, property files, timers | New or changed files, settings files and clock ticks start jobs | Supported |
| AIS Edge to AIS Edgetags, writes and remote job calls, queued through link loss, over TLS | Another AIS Edge Device | Verified between two AIS Edge runtimes |
| Industrial networks | ||
| EtherNet/IP I/O (class 1 scanner)EDS files | Remote I/O, valve manifolds, IO-Link masters | Interop OpENer |
| FL-net (OPCN-2)a full node: common memory, messages | JEMA FL-net controllers | Supported |
| Ethernet POWERLINK | Managing and controlled nodes | Interop openPOWERLINK |
| PROFINET DCP | Find, name and address PROFINET devices | Interop p-net |
| GE Ethernet Global Data | PACSystems, Series 90, Mark VIe | Assumed device test pending |
| PRP and HSR (IEC 62439-3) | Redundant networks | Assumed device test pending |
| EtherCAT® masterETG.1500 class B; CoE, FoE, EoE, SoE; ESI and ENI; distributed clocks | EtherCAT drives, I/O and encoders, on a standard Intel port | Interop an open-source master and our simulated devices; no real hardware yet |
| EtherCAT TSN, EtherCAT Automation Protocoldraft EtherCAT TSN profile | EtherCAT over TSN networks; data between controllers | Supported simulation only |
| CC-Link IE Field Basicmaster and remote station, CSP+ profile | MELSEC iQ-R and iQ-F masters; Field Basic devices | Supported simulation only |
| CC-Link IE TSNClass A and Class B device station, manager station | CC-Link IE TSN networks | Supported simulation only |
| CC-Link IE Field, software stationintelligent or remote device station; RX/RY/RWr/RWw both ways | A standard PC port as a station on a CC-Link IE Field network | Supported simulation only; Mitsubishi station test next |
| CC-Link IE Controller, software stationtwisted pair; LB/LW both ways | A standard PC port as a normal station on the network | Supported simulation only; Mitsubishi station test next |
| Ethernet TSNIEEE 802.1Qbv schedules, launch time, OPC UA PubSub over Ethernet | TSN-capable Ethernet | Supported in software; Intel i210 / I225 next |
| gPTP time sync (IEEE 802.1AS) | Time-synchronised data across machines | Interop ptp4l |
| CC-Link IE passive tapdata collected by listening only, no station added | CC-Link IE Controller, Field, Field Basic and TSN networks | In development |
| EtherCAT SubDevice | AIS Edge as a slave in another vendor's EtherCAT network | In development |
| Substations, meters and buildings | ||
| IEC 61850 MMSreports, controls, files, SCL import | Protection relays and IEDs | Interop libiec61850 |
| IEC 61850 GOOSE and Sampled Values | Station and process bus | Interop libiec61850 |
| R-GOOSE and R-SV (IEC 61850-90-5) | Routed GOOSE and SV over IP | Assumed device test pending |
| IEC 61400-25 | Wind turbines | Interop libiec61850 |
| IEC 60870-6 TASE.2 / ICCPdata values and data sets | Control centres | Assumed device test pending |
| IEC 60870-5-104 and -101TLS per IEC 62351 | RTUs and relays | Assumed device test pending |
| DNP3 (IEEE 1815)events, controls, TLS | RTUs, IEDs, meters | Interop opendnp3 |
| DLMS/COSEM (IEC 62056) | Electricity, gas and water meters | Interop Gurux |
| IEC 62056-21 / IEC 61107 | Meter optical and serial readout | Assumed device test pending |
| M-Bus and wireless M-Bus / OMS | Heat, water, gas and electricity meters | Supported |
| Emerson ROC Plus | ROC800, FloBoss 107, DL8000 flow computers | Supported |
| BACnet/IP and BACnet MS/TP | Building controllers | Interop BACnet Stack |
| KNXnet/IP | KNX interfaces and routers | Interop knxd, xknx |
| oBIX 1.1 | Niagara and other building servers | Supported |
| EnOcean | Wireless building sensors through ESP3 gateways | Interop enocean |
| Z-Wave, Zigbee, DALI, 1-Wire, X10, OpenTherm | Through their controllers and gateways | Assumed device test pending |
| VSCP, xPL, xAP | Open building and home buses | Supported |
| Drives, instruments, robots and machines | ||
| Mitsubishi inverter computer link | FR-A800 / E800 / F800 / A700 inverters | Supported |
| Mitsubishi servo RS-422 communication | MR-J3 / J4 / J5 servo amplifiers | Supported |
| Siemens USS, Danfoss FC | SINAMICS, MICROMASTER; VLT drives | Supported |
| Fuji FRENIC, Hitachi inverter protocols | General-purpose inverters | Supported |
| OMRON CompoWay/F, RKC, Azbil CPL, Shinko | Temperature and process controllers | Supported |
| Azbil NX (CPL over Ethernet) | Azbil NX network instrumentation | Supported |
| HART-IP | HART and WirelessHART through gateways | Assumed device test pending |
| IO-Link JSON REST, IODD files | IO-Link masters and devices | Supported |
| CANopen | CANopen drives and I/O | Interop CANopenNode |
| NMEA 0183 / IEC 61162 | GNSS, weather and depth instruments | Interop pynmea2 |
| METTLER TOLEDO MT-SICS | Scales and balances | Supported |
| Mitutoyo U-WAVE | Wireless gauges through the U-WAVE-R receiver | Supported |
| EPICS Channel Access, PV Access; DDS / RTPS | Laboratory and accelerator controls; DDS systems | Interop EPICS base, Cyclone DDS |
| SECS/GEM (HSMS) | Semiconductor equipment | Interop secsgem |
| Universal Robots RTDE and Dashboard | UR cobots | Interop UrRtde |
| ABB Robot Web Services, Yaskawa HSES, Epson RC+ | Robot controllers | Supported |
| Yamaha RCX, IAI X-SELstatus, positions, variables, I/O; no motion commands | Yamaha RCX340 / RCX3; IAI X-SEL, SSEL, ASEL, PSEL, TT | Supported |
| Atlas Copco Open Protocol | Tightening controllers | Supported |
| Cognex DataMan, In-Sight; KEYENCE SR | Code readers and vision | Supported |
| Zebra ZPL and SGD | Label printers | Supported |
| Mitsubishi Electric MELFA robotsnative PC link to CR800 / CR750 controllers | MELFA robots: status, positions, variables, I/O | Planned |
| FANUC robots, nativebeyond EtherNet/IP and OPC UA, which work today | R-30iB controllers | Planned |
| FANUC FOCAS and Mitsubishi CNC adaptersthrough the CNC maker's library on the customer's PC | FANUC 0i / 30i, Mitsubishi M800 / M80 (OPC UA and MTConnect work today) | Planned |
| Haas machine data collection | Haas CNC machines | Assumed device test pending |
| CNC DPRNTprint output, field by field | FANUC and Mitsubishi CNCs | Assumed device test pending |
Siemens controllers are supported through OPC UA, which current Siemens CPUs provide natively. AIS Edge is also an OPC UA server (with historical access, alarms and conditions, and methods; verified with the independent asyncua test suite, 43 of 43 and 37 of 37 security cases), an OPC DA server on Windows, a DxpLink server for TAKEBISHI DeviceXPlorer, a Modbus TCP server, an MQTT broker, an FTP / FTPS server, an MTConnect agent and an SNMP agent, so SCADA and historians can read it directly.
An EtherCAT master and CC-Link IE stations, in software, on a standard Intel port.
AIS is a member of the EtherCAT Technology Group and the CC-Link Partner Association, and builds both protocol families into AIS Core, the protocol engine shared by AIS Edge, AIS SoftPLC and AIS HMI. They are written clean-room from the specifications. All of it passes in simulation; real devices come next, and nothing here is claimed against real hardware yet.
| Protocol | What AIS Edge does | Proven so far |
|---|---|---|
| EtherCAT® | MainDevice to ETG.1500 class B over raw Ethernet or UDP: scan, topology, state machine, process image, distributed clocks, recovery, ENI import. Mailbox CoE, FoE, EoE and SoE; ESI, ENI and SII files. Tags come straight from the PDO entries. | Interop eight simulated devices, among them a CiA 402 drive, a servo, I/O and an encoder; an open-source master scans our simulated devices to OP |
| EtherCAT TSN, EAP | The draft EtherCAT TSN profile and the EtherCAT Automation Protocol between controllers | Supported simulation |
| CC-Link IE Field Basic | Master and remote station (1, 2 or 4 occupied stations); CSP+ profile read and write, with a CSP+ file for GX Works3 generated by the edge | Supported simulation, end to end |
| CC-Link IE TSN | Device station Class A (any network port) and Class B (gPTP, launch times, 802.1Qbv schedule), and a manager station | Supported simulation on virtual Ethernet |
| CC-Link IE Field | Software slave station (intelligent or remote device station): RX/RY/RWr/RWw both ways and the transient server, on one Intel port behind a gigabit switch | Supported simulation; first test against a Mitsubishi RJ71EN71 next |
| CC-Link IE Controller | Software normal station on the twisted-pair network: LB/LW both ways, transient answers from its own link devices | Supported simulation; RJ71EN71 test next |
| CC-Link IE passive tap | Cyclic data collected by listening only, with no station added to the network (Controller, Field, Field Basic, TSN) | In development |
| EtherCAT SubDevice | AIS Edge as a slave in another vendor's EtherCAT network | In development |
EtherCAT and CC-Link IE Field Basic are device kinds in the runtime and in Studio, in English and Japanese, with a live view of the scan, states, PDO values and SDO access. EtherCAT, Field Basic and TSN Class A run on any Ethernet port; TSN Class B, the manager station and EtherCAT distributed clocks need an Intel i210 or I225 / I226 port with hardware time stamps and a real-time Linux kernel. Safety over EtherCAT and EtherCAT P are not planned. The EtherCAT name is claimed in a shipping product only after the ETG conformance test. EtherCAT® is a registered trademark and patented technology, licensed by Beckhoff Automation GmbH, Germany.
The tools a plant's engineers and IT ask for, on the device.
Built on 21 October 2026: an FTP server whose files start jobs, network settings that cannot lock you out, signed updates that roll themselves back, one tag browser, Python in a job and an encrypted local database with its own SQL workspace. Each is checked on the device and kept in the audit log. In testing here means passing our own end-to-end tests, not yet in a plant.
| Tool | What it does | Status |
|---|---|---|
| FTP / FTPS server | Folders each user is locked into, device users and FTP-only accounts, quotas, resume, UTF-8 or Shift_JIS names, the device allow list. A received file starts a job. | Verified curl, Python ftplib, lftp; 1,800 malformed commands |
| LAN settings and routes | DHCP or static IPv4 / IPv6, gateway, DNS, VLANs, static routes, host name. Checked first, shown as a diff, then confirm-or-revert: unless Studio confirms from the new address within 120 s, the old settings return, even after a reboot. | Interop Debian's own network tools; simulated for the others |
| Signed updates and fleet rollout | Signed packages, refused if unsigned, tampered, for another processor or older. Installed side by side, health-checked, rolled back automatically on a crash loop, hang or failed project load. Fleet: a canary first, then batches, stopping on the first failure. | In validation on the industrial PC next |
| One tag browser | OPC UA, OPC DA and PLC labels, plus imports of Siemens TIA Portal tag tables, Modbus register maps, SunSpec models and KNX group addresses; search and export. The same component in every AIS tool. | Interop OPC UA; the file imports assumed |
| Run and stop the PLC | A job step for RUN, STOP, PAUSE, latch clear, reset, error clear and clock on MELSEC SLMP and OMRON FINS, with confirmation, a separate right and the audit log | Supported byte-exact to the manuals |
| Python scripting | Python in a job step, in separate supervised processes: time and memory limits, restart on crash, tag access only within the step's write list, network closed unless switched on. Script library, editor, test run. | In testing 56 end-to-end checks |
| Local database and SQL | Encrypted SQLite, an SQL API that is read-only by default, and a Studio workspace: schema tree, SQL editor, results, query plan, safe row editing, CSV import, backup and restore | In testing 104 end-to-end checks |
| Configuration from a job | Import an approved configuration bundle (dry run, checked, applied as a whole, rolled back if it does not load) or switch to an administrator-defined security policy set with an expiry | In testing 66 end-to-end checks |
Straight into the systems that need the data.
The edge device speaks each database's own wire protocol and each broker's own protocol, with TLS and certificate checks. Every output keeps its records on the device until the far end has them.
| System | How AIS Edge connects | Status |
|---|---|---|
| Microsoft SQL Server | Native TDS, TLS including forced encryption, stored procedures with output parameters | Verified SQL Server 2025 |
| PostgreSQL | Native protocol, TLS | Verified PostgreSQL 18 |
| MySQL / MariaDB | Native protocol, binary prepared statements, TLS | Verified MySQL 8.4, MariaDB 11.8 |
| MongoDB | Native wire protocol, TLS, replica sets, transactions | Verified MongoDB 8.0 |
| Oracle Database | Native protocol, TLS (TCPS), PL/SQL procedures with OUT parameters | Verified Oracle Database 26ai Free |
| IBM Db2 | Native DRDA protocol | Supported tested on a simulator |
| SQLite | A database file on the edge device itself | Verified |
| MQTT 3.1.1 / 5.0, Sparkplug B | Client to any broker or cloud, and an MQTT broker on the device for a Unified Namespace | Verified Mosquitto |
| MQTT 3.1, shared subscriptions, request and replyautomatic version, standby brokers, 64 KiB messages | Older brokers; several edges sharing a topic; jobs answering MQTT 5, NATS, STOMP and AMQP 0-9-1 requests | Interop Mosquitto, nats-server, RabbitMQ |
| Apache Kafka | Idempotent producer and consumer groups, TLS and SCRAM | Verified Kafka 4.4 |
| AMQP 1.0 and 0-9-1 | RabbitMQ, ActiveMQ Artemis, Azure Service Bus and Event Hubs, IBM MQ, Solace | Verified RabbitMQ 4.0, Artemis 2.44 |
| NATS, STOMP, MQTT-SN, WebSocket, OPC UA PubSub | Outputs and triggers; NATS with JetStream de-duplication | Verified nats-server 2.15, RabbitMQ STOMP |
| MES and ERP | REST and OData with OAuth 2.0; presets for Oracle Fusion Cloud Manufacturing, SAP Digital Manufacturing, Microsoft Dynamics 365 SCM, Rockwell Plex; ISA-95 / B2MML messages | Supported built from each vendor's published API; validated per customer |
| Maintenance, ERP and business apps | Presets for IBM Maximo Manage, IFS Cloud, SAP MII, Cybozu kintone; any SOAP 1.1 / 1.2 web service with WSDL import and WS-Security | Supported built from each vendor's published API; validated per customer |
| MotionBoard | Real-time data | Assumed record format from public descriptions; test pending |
| Data platforms | Snowflake SQL API, Databricks SQL, Google Cloud Pub/Sub, Google BigQuery, Siemens Insights Hub, statsd | Supported tested against reference services; live accounts next |
| Water Standard Platform (Japan) | The edge as the platform's IoT gateway: monitoring, cyclic data, control values, signed and encrypted | Assumed platform test pending |
| InfluxDB | Line protocol, v1 and v2 write API | Verified InfluxDB 2.10 |
| AVEVA PI, GE Vernova Proficy, Canary | Their published web APIs | Supported validated per customer |
| Ignition, ICONICS Hyper Historian | They log the edge's tags through its OPC UA server, or Sparkplug B (OPC DA for GENESIS64 on Windows); one-click setup in Studio | In validation |
| Java Message Service (JMS) | ActiveMQ Classic over its native OpenWire protocol, ActiveMQ Artemis over AMQP 1.0, STOMP and OpenWire: Text, Bytes and Map messages with JMS headers, properties and selectors | Verified ActiveMQ Classic 6.3, Artemis 2.44 |
| AWS IoT Core | Certificate or provisioning by claim, port 443 for locked-down plants, Device Shadow to tags, cloud Jobs start AIS jobs | Supported tested locally; live AWS next |
| AWS services | IoT SiteWise from the model objects, S3, SQS, SNS, Kinesis, DynamoDB, CloudWatch and Logs, Lambda, Timestream; IAM sign-in for RDS / Aurora and MSK | Supported AWS signing test suite; emulator; live AWS next |
| Microsoft Azure | IoT Hub (telemetry, device twin to tags, direct methods to jobs, cloud-to-device), Device Provisioning Service, Event Grid (MQTT and HTTP), Storage Queues; Service Bus and Event Hubs over AMQP | Supported tested locally with Microsoft's Azurite; live Azure next |
| MSMQ | Microsoft Message Queuing from Microsoft's published protocol, for existing MES and HMI systems | Supported tested against a spec-based peer |
| Files and messages | CSV and log files in UTF-8 or Shift-JIS, e-mail with TLS, FTP / FTPS upload and download (passive or active), SMS through a GSM modem | Supported |
| SFTP | Upload over SSH with a pinned host key or known hosts | Interop OpenSSH |
| HTTP proxy and Digest | The plant's proxy with its own login for web, cloud and MQTT-over-WebSocket outputs; HTTP Digest (MD5, SHA-256) | Supported |
| Kerberos integrated login | SQL Server and web services with the plant's Windows domain accounts | Interop MIT Kerberos |
| Entra ID for SQL Server | Azure SQL and SQL Server logins with Microsoft Entra ID | Supported live Azure next |
Store and forward
Every output has its own durable queue. In our test runs, outages of brokers, databases and the network, a kill of the runtime and a power cut mid-send lose 0 records.
Historian on the device
Logging sets by interval, on change or on a trigger, with compression and a trend viewer; about 20,000 samples per second on an industrial PC, forwarded when systems are back.
Dashboards on every screen
Operator screens from 37 widgets for phones, tablets and wall screens: seven chart types, SPC charts with Cp and Cpk, SQL tables, and input widgets checked again by the device. Values are pushed in about 0.2 s, and the same tags open in our AIS HMI.
Jobs for real plant data
Arrays, binary buffers with checksums, JSON with jq, named time zones, compression, Do Once and week-of-month schedules, buffered history steps. 8,192 tags, 64 devices and 128 jobs on the standard edge device.
Identity and access
LDAP and Active Directory (interop-tested with OpenLDAP), single sign-on with OpenID Connect for Entra ID, AD FS and Keycloak, one allow list for every service, ordered allow and deny rules, and encryption of the data at rest.
Run it like IT
Encrypted backups, safe and deployment modes, factory reset, rotating logs with scheduled export, the time zone and a file editor in Studio. A Windows service and a container image are in validation.
Designed in Studio, served by the device.
Desktop, tablet and phone layouts of the same dashboard: values, gauges, lamps, trends with history, setpoints with limits and buttons with confirmation. A lost link shows "no data" at once, never a stale value as live. Every AIS Edge on the network is found automatically, and one page shows the whole fleet.
The data layer under your HMI and SCADA.
AIS Edge Device collects, decides and delivers at the line; AIS HMI runs the plant's screens, ISA-18.2 alarms, recipes, audit trail and reports. Together they are one platform: start with the edge device and its dashboards, and grow into HMI and SCADA without re-engineering.
- One tag model. The edge device publishes its tags in AIS HMI's own format, so screens bind to them as they are
- One screen format. An edge dashboard exports as an AIS HMI screen, and back
- One data path. AIS HMI reads and writes through the edge device; if the link drops, values show "no data" and writes are refused, never a stale value as live
- One set of users. Operators and viewers come from the edge device's users; every write is in the audit log
The AIS HMI bridge to AIS Edge is verified against a real AIS Edge runtime; the screen export both ways is in testing.
Where AIS Edge Device stands, and where it is going.
What is built and tested today, what we are validating with real systems, what is in testing and in development, what comes next, and what is planned. Featured: the CC-Link IE family, EtherCAT® and TSN. The order of planned items may change with customer demand. Every protocol is built from its published specification, and where a protocol has a conformance program we claim it only after passing it.
- Built and tested · 2026
The platform
90+ device protocols (PLCs, drives, robots, CNCs, meters, substation IEDs, building controllers) plus a no-code User Protocol builder, messages sent by MELSEC, OMRON and Rockwell PLCs, Bluetooth beacons and edge-to-edge links, OPC UA client and server (historical access, alarms and conditions, methods), OPC DA, seven native databases, MQTT and Sparkplug B with an on-device broker, Kafka, AMQP, NATS, STOMP, JMS / OpenWire, MSMQ, CoAP and LwM2M, AWS (IoT Core, SiteWise and ten services) and Azure (IoT Hub, DPS, Event Grid, Storage Queues), Google Pub/Sub and BigQuery, Snowflake and Databricks, MES, ERP, maintenance and historian connections, SFTP, Ethernet TSN scheduling and OPC UA PubSub over Ethernet (in software), store-and-forward, the on-device historian, dashboards with charts, SPC and inputs, users and audit, LDAP / Active Directory and single sign-on, encryption at rest, LAN discovery, English and Japanese. Added on 21 October: the FTP / FTPS server, LAN settings with automatic revert, one tag browser, Python scripting, an encrypted local database with an SQL workspace, and PLC run / stop commands.
- In validation
With real plants and systems
Field validation on customer equipment; TSN on Intel i210 / I225 hardware; live AWS and Azure accounts; Ignition and ICONICS Hyper Historian; Db2 on a real server; MES and ERP connections on customer tenants; signed updates and fleet rollout on our industrial edge PC; the Windows service and the container image; Bluetooth beacons on a real adapter; camera barcode scanning on phones.
- In testing · featured
EtherCAT® master and CC-Link IE stations, in simulation
An EtherCAT master with EtherCAT TSN; CC-Link IE Field Basic master and remote station; CC-Link IE TSN Class A / B device and manager; CC-Link IE Field and Controller software stations; gPTP time sync (IEEE 802.1AS). All passing in simulation, with no real hardware yet.
- In development
CC-Link IE passive tap and EtherCAT SubDevice
Cyclic data collected from a CC-Link IE network by listening only, with no station added; and AIS Edge as a slave in another vendor's EtherCAT network.
- Next · on real hardware
EtherCAT and CC-Link IE with real devices
EtherCAT with other vendors' drives and I/O, sub-millisecond cycles and distributed clocks on Intel i210 / I225, then the ETG conformance test; CC-Link IE Field and Controller against a Mitsubishi RJ71EN71, then as device kinds in Studio; CC-Link IE TSN against a Mitsubishi manager station.
- Next
Mitsubishi platforms and secure remote access
Packages for the Mitsubishi C Controller and the MELSEC iQ-R RD55UP; operating-system image updates; support access to the machines through the same box, designed with IEC 62443 in mind.
- Planned
Robots and CNCs, natively
Mitsubishi Electric MELFA robots and FANUC robots in their own protocols; FANUC FOCAS and Mitsubishi CNC data through the CNC maker's library. Today these machines are reached through OPC UA, MTConnect, EtherNet/IP or SLMP.
- Planned
CC-Link IE Control (optical fiber)
Through Mitsubishi Electric's PCIe network interface board in the industrial PC.
Industry packs
- IPC-CFX and IPC-HERMES-9852 (electronics assembly)
Memberships
- EtherCAT Technology Group (ETG) member
- CC-Link Partner Association (CLPA) member
- PROFINET IO (planned, with membership)
Platforms
- Linux and Windows industrial PCs
- Mitsubishi C Controller (in development)
- MELSEC iQ-R RD55UP (in development)
Engineering
- Permissive licences only, no GPL
- Each protocol a module an OEM build can leave out
- More than 300 test programs and 64 end-to-end suites with about 3,000 checks, plus the interoperability suites, on every build
Interested in a pilot?
If your plant needs fast, dependable data from Mitsubishi or mixed equipment, we'd like to hear about it. Try the demo first, or tell us about your plant.