ANALYZER FOR COMPUTER NUMERICAL CONTROL MACHINES
Install ACNC as an app
This browser supports installation of the PWA on this device.
Dashboard — Guideline
Only values with a real mapped source belong here.
- Select the correct machine family and axis configuration before interpreting signals or parameters.
- Confirm mode, interface, protocol and connection state.
- Unmapped values remain N/A.
- Do not interpret overview values as controller truth unless their source is identified.
Machine Overview
Preview mode does not simulate machine motion. Live values appear only when a real data mapping exists. The cards below follow the machine profile (sidebar → Machine).
ACNC for Android BETA
Freeware · direct USB serial via USB-OTG · works offline · no internet permission
Version
0.4-beta
Requires
Android 7.0 or newer with USB Host (OTG) and a USB-C/Micro-USB OTG adapter
USB serial chips
Prolific PL2303 (e.g. LogiLink UA0042A), FTDI, CH340/CH341, CP210x, CDC ACM
SHA-256 (APK)
306311dec55a6247e6acdf62471c3dc5696aefe2c18cfbff6659655cde33da9f
Signing certificate
CN=ACNC, O=Dromation, C=SI · SHA-256 6D:30:F2:95:46:58:2D:00:DD:D3:A0:81:F9:74:36:1C:70:4B:16:D0:EC:62:D1:F1:C4:79:DF:0E:91:4D:43:6A
Installation
- Download the APK on the phone (or copy it to the phone).
- Open the file and allow installing apps from this source when Android asks.
- Open ACNC → Continue → Devices.
- Connect the USB serial adapter with an OTG adapter, press Refresh, then Request permission.
Beta: not yet tested with every phone and adapter. ACNC starts read-only and never writes to a machine automatically.
By downloading you accept the ACNC license
(third-party notices).
Machine State
Drive Ready: N/ACycle: N/A
E-Stop: N/AAlarm: N/ACoolant: N/A
Connection
Disconnected
Protocol
Modbus RTU
Machine
Not set
Controller
Unknown / detect
Machine type
Other / Unknown
Axes
Not configured
Subsystems
—
Quick Actions
Device Capability
Web Serial
Checking...
PWA
Checking...
Server processing
None required
Machine data upload
Disabled by design
Mobile / Laptop
Laptop: use Web Serial where supported, or optional ACNC Bridge. Mobile/tablet: UI/PWA works; direct USB/serial depends on OS/browser. ACNC Bridge companion is the future cross-browser path.
Devices — Guideline
See the complete chain from this phone/computer to the machine. Only real, detected hardware is shown.
- Connect the USB serial adapter (on a phone via USB-OTG) and press Scan devices.
- In a desktop browser use Request serial port; on Android use the ACNC Bridge app and allow USB permission.
- Select the physical interface, serial settings and target profile from machine documentation — ACNC never guesses them.
- Run the Connection test to see which step fails. No data is ever written automatically.
Connection chain
Serial settings, physical interface and protocol are taken from the sidebar (Connection). Browsers only see devices you granted; they cannot list every USB device.
Raw results from Android UsbManager and usb-serial-for-android — visible directly on the phone, no Android Studio / logcat needed.
UsbManager devices: –
| Name | VID | PID | Class | Subclass | Protocol | Interfaces | Category | Serial driver match | Driver | Permission | Port open | State |
|---|
Native hardware log
| Timestamp | Event | Details |
|---|
Hardware access / installation status
Target device profile
Deterministic check of every stage from platform to machine. Reports only what is observed — a step that cannot be observed is never shown as OK.
| # | Stage | Result | Detail |
|---|
Driver status (registry)
Metadata only — the real driver (Android prober, Linux kernel, Windows COM driver) must still accept the device.
| Family | VID | Known PIDs | Android | Linux | Windows | Status |
|---|
| Timestamp | Event | Transport | Device | Driver | Result | Detail |
|---|
Terminal — Guideline
Use raw serial communication only after verifying port settings.
- Connect a supported adapter.
- Choose ASCII or HEX deliberately.
- Do not send undocumented commands to a production machine.
- Export logs before risky troubleshooting.
HEX: two digits per byte, e.g.
01 03 00 00 00 01 84 0A. A valid Modbus write frame typed here is refused unless the safety mode is DANGEROUS. Sending is blocked while a Modbus transaction waits for its response.RX 0 B · TX 0 B
Control lines
Shown only when the connected backend exposes them. Changing DTR/RTS can reset or signal some devices — explicit action only.
Capture
Records every RX/TX chunk with timestamp and byte count (up to 20 000 frames) for export.
Not capturing.
Protocols — Guideline
Configure RS232/RS485 and Modbus RTU from known machine documentation.
- Verify baud, data bits, stop bits and parity.
- RS485 requires a compatible physical adapter.
- Use one Modbus transaction at a time.
- Writes require explicit enable and confirmation.
RS232 / RS485
Baud
9600
Parity
none
Stop bits
1
Modbus RTU
Writes: current value is read first, then confirmation, write, read-back and comparison.
Idle.
Native / Future
CAN, PROFINET, JTAG/SWD and vendor SDK access require ACNC Next / native bridge. They are not presented as browser-live functions.
Register Data
| # | Address | Decimal | HEX | Status |
|---|
Signals — Guideline
Build a normalized signal map from observed, documented or imported data.
- Record source and address.
- Separate confirmed signals from hypotheses.
- Correlation is evidence, not proof of causality.
| Name | Type | Source | Address | Value | Unit | Sampling | Frequency | Confidence |
|---|
Signal Relationships
EXAMPLE ONLY
CYCLE_START
└── SAFETY_OK
└── SPINDLE_ENABLE
└── SPINDLE_READY
Classification
No automatic classification result is shown unless a real inference engine and evidence are available.
Relevant signal candidates for this machine type
Used only to rank candidates. A signal's identity is never declared from the machine type alone.
I/O Map — Guideline
Document physical and logical I/O with traceable evidence.
- Record DI/DO/AI/AO/BUS/VIRTUAL type.
- Add connector/terminal and electrical level where known.
- Record normal and fault states only when verified.
| Name | Type | Direction | Address | Connector | Level | Normal | Fault | Function | Confidence |
|---|
Parameters — Guideline
Inspect and reconstruct parameters without assuming suspicious values are automatically corrupted.
- Verify datatype, scaling and unit.
- 65535 / 0xFFFF can have several meanings.
- Keep source and confidence for every proposal.
- Before write: read old value, confirm, write, re-read and verify.
| Name | Group | Address | Current | Unit | Datatype | Source | Confidence | Status | Proposed | Action |
|---|
Parameter groups for this machine
Semantic groups only — no controller addresses are defined or assumed.
Write Policy
Generic parameter writes are blocked unless a real mapped protocol profile exists.
Example
Example rows are marked EXAMPLE and are never treated as live controller values.
Advanced reconstruction & shadow — ACNC Next
This free demo intentionally stops at reading, decoding and basic diagnostics of what the controller already exposes. The following capabilities require stronger guarantees around verification, traceability and support, and are part of ACNC Next (proprietary, developed by Dromation in cooperation with Kovigal d.o.o.) rather than this public edition:
- Axis scaling reconstruction — deriving encoder scale/soft limits from supervised measurements, with regression and outlier analysis.
- Per-axis reconstruction records — tracked source, confidence and verification state for engineer-entered axis configuration.
- Logical Shadow — a parameter/I-O/calibration/firmware shadow snapshot of the machine's configuration.
- Machine Configuration Package — building and exporting a consolidated, reusable configuration artifact.
What this demo still gives you on this machine: parameter/signal/I-O mapping, suspicious-value flagging, the read-only Controller State Reader, and local consistency diagnostics — see Parameters, Reader and Diagnostics.
Auto Communication Discovery — Guideline
ACNC finds and ranks the most likely line settings by itself. You do not have to guess baud rate, parity, stop bits or flow control.
- Connect the adapter (USB-OTG on Android). Select it on the Devices screen if several are attached.
- Press AUTO DISCOVER. ACNC opens, listens and closes the port for every setting — nothing is sent.
- Only with documented read-only requests (controller profile or State Reader) a short active read stage follows.
- Use the best candidate, check it against the controller documentation, then save it as an Initiation Map.
Auto communication discovery
Discovery settings
Documented Modbus read for the active stage (optional)
Documented read commands added on the State Reader screen are included automatically. ACNC never sends random or brute-forced bytes.
Score ranks candidates only (0–100). VERIFIED requires a protocol-level response to a documented read request. USB transport errors and unsupported settings are listed separately — they say nothing about the line settings.
| # | Setting | Stage | RX | Frames | Valid | ASCII | CTS/DSR/DCD | Score | Confidence | Fault |
|---|
Raw RX during discovery
Every received byte with timestamp, setting, HEX and ASCII — also when nothing can be decoded.
Initiation Map
A saved profile is used only when VID/PID, driver, machine and controller profile match — otherwise PROFILE NOT VERIFIED FOR THIS DEVICE.
| Name | Device | Serial | Confidence | This device |
|---|
Fault tree — panel shows state but ACNC cannot read it
Discovery FMEA
S/O/D are provisional generic ratings (1–10) — review them for your machine. RPN = S × O × D.
| Failure mode | Cause | Effect | Detection | Mitigation | S | O | D | RPN |
|---|
Controller State Reader — Guideline
Read the existing controller state only. Nothing on the machine is modified.
- Connect the adapter (Devices) with the settings from the controller documentation.
- Start with PASSIVE READ — ACNC transmits nothing and shows every received byte.
- Only if the controller is silent: ACTIVE READ ONLY with Modbus FC01–FC04 or documented read commands.
- Values without documentation stay raw. Never assume datatypes or scaling.
Mode
Read method
Allowed in ACTIVE READ ONLY: Modbus RTU FC01–FC04 (CRC checked) and exact documented read commands. FC05/06/15/16 and every other frame are rejected before the transport.
RS485 transport
Status
Read only. ACNC never toggles DTR/RTS automatically in this mode.
Diagnostic counters
Decodes FC01, 02, 03, 04, 05, 06, 15, 16 sent by other devices on the line. Direction (request/response) is inferred for FC05/06. ACNC does not transmit here.
| Time | Dir | Slave | FC | Address | Qty | Data | CRC |
|---|
Modbus read-only master
ACTIVE READ ONLY only. Function codes 01–04. Each read is logged.
Documented read commands (controller profile)
| Name | HEX | Reference |
|---|
Every value shows where it came from. Nothing is filled in without a source. Values stay raw until a documented datatype/scaling exists.
| Field | Value | Source | Timestamp | Confidence | Verification |
|---|
Registers read / observed (raw)
| Slave | FC | Address | Raw | HEX | Source | Timestamp |
|---|
Alarms · I/O · Drives
Alarms, I/O (DI/DO/AI/AO) and drive state can only be shown once a documented read map for this controller exists. They are displayed only — ACNC has no acknowledge, reset, clear or force function.
Auto communication discovery
Line settings are found on the Auto Discovery screen (passive matrix, handshake stage, documented read-only requests, Initiation Map).
Read-only log
Every read request and every blocked write attempt.
| Time | Operation | Protocol | Result | Reason |
|---|
Fault tree — controller state not available
State Reader FMEA
S/O/D are provisional generic ratings (1–10) — review them for your machine. RPN = S × O × D.
| Failure mode | Cause | Effect | Detection | Mitigation | S | O | D | RPN |
|---|
Diagnostics — Guideline
Use FTA and FMEA to structure troubleshooting and prevent premature conclusions.
- Start from the observed symptom.
- Link alarms, signals and parameters.
- Keep hypotheses separate from verified causes.
- Record the next safe test.
Fault Tree Analysis
MACHINE WILL NOT START
OR
├── Safety fault
├── Drive fault
└── Configuration fault
FMEA
| Failure mode | Effect | Detection | Prevention |
|---|---|---|---|
| Wrong axis scaling | Wrong movement distance | Measured displacement | Multi-point verification |
| Wrong datatype | Extreme value | Range validation | Typed map |
Diagnostic Findings
Top event: ACNC cannot communicate with machine (OR). Status comes only from the last connection test: EXCLUDED / POSSIBLE / SUSPECTED / UNKNOWN — a root cause is never confirmed automatically.
Connection FMEA
Generic connection failure modes (not machine-specific). Enter Severity, Occurrence and Detection (1–10); RPN = S × O × D.
| Failure mode | Cause | Effect | Detection | Mitigation | S | O | D | RPN |
|---|
Sessions — Guideline
Maintain traceability of engineering work.
- Log connection changes and communication.
- Export important sessions before configuration changes.
- Avoid unnecessary personal/confidential information.
| Timestamp | Type | Direction | Protocol | Details |
|---|
Settings & Privacy — Guideline
Review local processing, privacy and deployment behavior.
- Machine communication remains local in this static build.
- Support uses user-initiated webmail / mail app / EML export.
- Privacy acknowledgement never authorizes machine writes.
Language
Translation catalogue can be added later.
ACNC for Android BETA
Freeware · direct USB serial via USB-OTG · works offline · no internet permission
Version
0.4-beta
Requires
Android 7.0 or newer with USB Host (OTG) and a USB-C/Micro-USB OTG adapter
USB serial chips
Prolific PL2303 (e.g. LogiLink UA0042A), FTDI, CH340/CH341, CP210x, CDC ACM
SHA-256 (APK)
306311dec55a6247e6acdf62471c3dc5696aefe2c18cfbff6659655cde33da9f
Signing certificate
CN=ACNC, O=Dromation, C=SI · SHA-256 6D:30:F2:95:46:58:2D:00:DD:D3:A0:81:F9:74:36:1C:70:4B:16:D0:EC:62:D1:F1:C4:79:DF:0E:91:4D:43:6A
Installation
- Download the APK on the phone (or copy it to the phone).
- Open the file and allow installing apps from this source when Android asks.
- Open ACNC → Continue → Devices.
- Connect the USB serial adapter with an OTG adapter, press Refresh, then Request permission.
Beta: not yet tested with every phone and adapter. ACNC starts read-only and never writes to a machine automatically.
By downloading you accept the ACNC license
(third-party notices).
License
ACNC Web demo and ACNC for Android are freeware demo editions — © Dromation, developed in cooperation with Kovigal d.o.o. Free for personal, non-commercial and educational use; commercial use requires an agreement with Dromation.
Hardware access / installation status
Machine types
Informational. Planned types are prepared in the data model but have no logic yet and cannot be selected.
Local / Online
Machine data
Local browser only
Backend
None required
Server CPU
Static files only
Future
Optional ACNC Next C++ Agent / mobile companion
Support
Destination: info@acnc.dromation.com
Privacy / GDPR
This in-app summary complements the full privacy notice shown before the application starts.
Demo version
This is a demonstration version of ACNC, developed by Dromation in cooperation with Kovigal d.o.o.
Local processing
Supported machine communication, local logs, local image previews and engineering exports are designed to remain on the user’s device unless deliberately shared.
GDPR rights
Where GDPR applies, relevant rights may include information, access, rectification, erasure, restriction, portability, objection, withdrawal of consent where consent is the legal basis, and the right to complain to a competent supervisory authority.
Engineering separation
Privacy acceptance does not authorize writes, movement, PLC changes, firmware changes or controller-memory modification.
Contact
info@acnc.dromation.com