ANALYZER FOR COMPUTER NUMERICAL CONTROL MACHINESDashboard — Guideline
Only values with a real mapped source belong here.
- Select the correct machine family and axis configuration before interpreting signals, parameters or reconstruction results.
- 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
Machine State
Quick Actions
Device Capability
Mobile / Laptop
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.
01 03 00 00 00 01 84 0A. A valid Modbus write frame typed here is refused in READ ONLY mode. Sending is blocked while a Modbus transaction waits for its response.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
Modbus RTU
Native / Future
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
Classification
Relevant signal candidates for this machine type
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
Write Policy
Example
Memory / Shadow — Guideline
The browser build handles logical snapshots and imported data, not arbitrary physical RAM access.
- Create versioned snapshots of known configuration.
- Keep original dumps immutable when imported.
- Separate known from inferred regions.
- Use ACNC Next/native tools for JTAG/SWD/flash imaging.
Logical Shadow
| Layer | Status | Source | Confidence |
|---|
Snapshot
Reconstruction — Guideline
Convert surviving evidence and measurements into candidate configuration.
- Only enabled axes belonging to the selected machine profile should be reconstructed.
- Identify controller, axis, drive and encoder first.
- Use multiple physical measurements where possible.
- Do not infer servo tuning from geometry alone.
- Every generated parameter needs evidence, source, confidence and verification state.
Measurement → Scale
| # | Axis | Encoder delta | Movement | counts/unit |
|---|
Axis reconstruction — enabled axes of the machine profile
Machine Configuration Package
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
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
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
Machine types
Local / Online
Support
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