Panduan Instalasi & Penggunaan

Browser yang Didukung

AliScada diakses dari browser — tidak ada instalasi client. Semua browser modern didukung.

AliScada is accessed from a browser — no client installation. All modern browsers are supported.

Download & Ekstrak

1. Download file AliScada_vX.X_win_x64.zip dari halaman Harga atau link yang diberikan vendor.

   Download AliScada_vX.X_win_x64.zip from the Pricing page or the link provided by the vendor.

2. Ekstrak ZIP ke folder pilihan Anda — misalnya C:\AliScada\.
   Hindari folder dengan spasi dalam path (mis. "Program Files").

   Extract the ZIP to a folder of your choice — e.g. C:\AliScada\.
   Avoid folders with spaces in the path (e.g. "Program Files").

3. Struktur folder setelah diekstrak:

   Folder structure after extraction:

Menjalankan

1. Double-click start.bat. Jendela command prompt akan terbuka dan menampilkan log server.

   Double-click start.bat. A command prompt window will open and display the server log.

2. Tunggu 5–10 detik hingga muncul pesan AliScada ready. Browser terbuka otomatis ke http://localhost:3000.

   Wait 5–10 seconds until the AliScada ready message appears. The browser opens automatically to http://localhost:3000.

3. Login menggunakan akun admin (lihat Akun Default).

   Log in using the admin account (see Default Accounts).

4. Untuk menghentikan: double-click stop.bat atau tutup jendela CMD AliScada.

   To stop: double-click stop.bat or close the AliScada CMD window.

Akses dari PC Lain (Jaringan)

1. Di PC server, buka CMD → ketik ipconfig → catat IPv4 Address (contoh: 192.168.1.50).

   On the server PC, open CMD → type ipconfig → note the IPv4 Address (e.g. 192.168.1.50).

2. Dari PC lain di jaringan yang sama, buka browser → akses http://192.168.1.50:3000

   From another PC on the same network, open a browser → access http://192.168.1.50:3000

3. Jika tidak bisa terhubung, izinkan port di firewall Windows:
   Windows Defender Firewall → Advanced Settings → Inbound Rules → New Rule → Port → TCP → 3000 → Allow

   If you cannot connect, allow the port in Windows Firewall:
   Windows Defender Firewall → Advanced Settings → Inbound Rules → New Rule → Port → TCP → 3000 → Allow

Update ke Versi Baru

1. Jalankan stop.bat untuk menghentikan server.

   Run stop.bat to stop the server.

2. Backup folder data\ — berisi semua database dan history Anda.

   Back up the data\ folder — it contains all your databases and history.

3. Salin semua file versi baru ke folder instalasi, kecuali folder data\.

   Copy all new version files to the installation folder, except the data\ folder.

4. Jalankan start.bat. Migrasi skema database berjalan otomatis.

   Run start.bat. Database schema migration runs automatically.

Cara 1 — Manual (Quick Start)

Cocok untuk uji coba cepat. Server berjalan selama sesi terminal aktif.

Suitable for quick testing. The server runs as long as the terminal session is active.

Linux x64 — Ubuntu / Debian / PC Server

# 1. Copy file ke server (dari Windows, via SCP)
scp AliScada_vX.X_linux_x64.tar.gz user@ip-server:/tmp/

# 2. Di server Linux — ekstrak dan set permission
sudo mkdir -p /opt/aliscada
sudo tar -xzf /tmp/AliScada_vX.X_linux_x64.tar.gz \
     -C /opt/aliscada --strip-components=1
sudo chmod +x /opt/aliscada/AliScada \
              /opt/aliscada/start.sh \
              /opt/aliscada/stop.sh

# 3. Jalankan
/opt/aliscada/start.sh

# Buka browser: http://ip-server:3000

Raspberry Pi 4 / 5 — ARM64 (OS 64-bit)

# 1. Copy file ke Raspberry Pi
scp AliScada_vX.X_linux_arm64.tar.gz pi@ip-raspberry:/tmp/

# 2. Ekstrak dan set permission
sudo mkdir -p /opt/aliscada
sudo tar -xzf /tmp/AliScada_vX.X_linux_arm64.tar.gz \
     -C /opt/aliscada --strip-components=1
sudo chmod +x /opt/aliscada/AliScada \
              /opt/aliscada/start.sh \
              /opt/aliscada/stop.sh

# 3. Jalankan
/opt/aliscada/start.sh

# Buka browser: http://ip-raspberry:3001

Raspberry Pi 2 / 3 — ARMv7 (OS 32-bit)

scp AliScada_vX.X_linux_armv7.tar.gz pi@ip-raspberry:/tmp/

sudo mkdir -p /opt/aliscada
sudo tar -xzf /tmp/AliScada_vX.X_linux_armv7.tar.gz \
     -C /opt/aliscada --strip-components=1
sudo chmod +x /opt/aliscada/AliScada \
              /opt/aliscada/start.sh \
              /opt/aliscada/stop.sh

/opt/aliscada/start.sh

cd /opt/aliscada
npm install \
  aedes@0.50.1 bcryptjs@2.4.3 cors@2.8.5 dotenv@16.4.5 \
  express@4.18.3 jsonwebtoken@9.0.2 modbus-serial@8.0.18 \
  mqtt@5.15.1 mysql2@3.22.3 net-snmp@3.26.3 \
  node-bacnet@0.2.4 node-opcua-client@2.169.0 node-opcua-server@2.169.0 \
  nodemailer@6.9.0 nodemon@3.1.0 pg@8.20.0 \
  serialport@10.5.0 socket.io@4.7.5 sql.js@1.12.0 winston@3.13.0

Stop & Lihat LogStop & View Log

/opt/aliscada/stop.sh             # Hentikan server
tail -f /opt/aliscada/aliscada.log  # Log real-time

Cara 2 — Systemd (Instalasi Produksi)

Gunakan cara ini agar AliScada otomatis berjalan saat perangkat dinyalakan dan restart sendiri jika crash. Berlaku untuk semua arsitektur (x64, arm64, armv7).

Use this method so AliScada starts automatically when the device is powered on and restarts itself if it crashes. Applies to all architectures (x64, arm64, armv7).

# 1. Install systemd service
sudo cp /opt/aliscada/aliscada.service /etc/systemd/system/
sudo systemctl daemon-reload

# 2. Aktifkan auto-start saat boot
sudo systemctl enable aliscada

# 3. Jalankan sekarang
sudo systemctl start aliscada

# 4. Verifikasi status
sudo systemctl status aliscada

Perintah Systemd Sehari-hari

sudo systemctl start   aliscada    # Jalankan
sudo systemctl stop    aliscada    # Hentikan
sudo systemctl restart aliscada    # Restart
sudo systemctl status  aliscada    # Cek status
sudo systemctl enable  aliscada    # Auto-start saat boot
sudo systemctl disable aliscada    # Nonaktifkan auto-start

# Log live
sudo journalctl -u aliscada -f

# 100 baris log terakhir
sudo journalctl -u aliscada -n 100 --no-pager

build-exe.bat — Windows Standalone EXE

PersyaratanRequirements: Node.js v18+ terinstal di mesin buildinstalled on the build machine.

1. Double-click build-exe.bat — jendela CMD baru terbuka otomatis.

   Double-click build-exe.bat — a new CMD window opens automatically.

2. Script menjalankan langkah-langkah berikut secara otomatis:

   The script runs the following steps automatically:

   LangkahStep	ProsesProcess
   [1]	Install @yao-pkg/pkg secara lokal (~50 MB, hanya pertama kali)Install @yao-pkg/pkg locally (~50 MB, first time only)
   [2]	Build frontend dengan Vite (npm run build)Build frontend with Vite (npm run build)
   [3]	Install backend production packages (npm install --omit=dev)Install backend production packages (npm install --omit=dev)
   [4]	Copy frontend build ke backend/public/Copy frontend build to backend/public/
   [5]	Kompilasi AliScada.exe dengan pkg — target node18-win-x64, compressed Brotli Pertama kali: download Node 18 binary (~30 MB, ~2–5 menit)Compile AliScada.exe with pkg — target node18-win-x64, Brotli compressed First time: downloads Node 18 binary (~30 MB, ~2–5 min)
   [6]	Copy runtime files: sql-wasm.wasm, public\, bindings\ (native .node modules), data\Copy runtime files: sql-wasm.wasm, public\, bindings\ (native .node modules), data\
   [7]	Generate config.json dan .envGenerate config.json and .env
   [8]	Generate start.bat dan stop.batGenerate start.bat and stop.bat

3. Output tersimpan di dist\AliScada_v1.4_exe\:

   Output saved to dist\AliScada_v1.4_exe\:

   AliScada_v1.4_exe\
   ├── AliScada.exe        ← single executable
   ├── sql-wasm.wasm       ← SQLite WASM engine (wajib ada)
   ├── public\             ← frontend static files (wajib ada)
   ├── bindings\           ← native .node modules (serialport, dll.)
   ├── config.json         ← konfigurasi yang bisa diedit
   ├── .env
   ├── data\               ← kosong; DB dibuat saat pertama run
   ├── start.bat
   └── stop.bat

build-linux-docker.bat — Linux Binary (x64 / arm64 / armv7)

PersyaratanRequirements: Docker Desktop for Windows dengan WSL2 backend aktifwith WSL2 backend enabled.

1. Double-click build-linux-docker.bat.

2. Pilih arsitektur target dari menu:

   Choose the target architecture from the menu:

   PilihanOption	ArsitekturArchitecture	Target	Node.js
   1	x64	Ubuntu / Debian / PC (x86-64)	18
   2	arm64	Raspberry Pi 4 / 5 (OS 64-bit)	18
   3	armv7	Raspberry Pi 3 / 2 (OS 32-bit)	16
   4	ALL	Build ketiga arsitektur sekaligusBuild all three architectures at once	—

3. Build berjalan di dalam Docker container (node:18-bullseye):

   • arm64 dan armv7 menggunakan native amd64 container + cross-compile — tidak memerlukan QEMU.
   • node_modules di-cache di Docker named volumes → build berikutnya ~2–3 menit.

   Build runs inside a Docker container (node:18-bullseye):

   • arm64 and armv7 use native amd64 container + cross-compile — no QEMU required.
   • node_modules cached in Docker named volumes → subsequent builds ~2–3 minutes.

4. Output tersimpan di dist\:

   Output saved to dist\:

   dist\AliScada_v1.4_linux_x64\          ← folder
   dist\AliScada_v1.4_linux_x64.tar.gz    ← paket terkompresi untuk deploy
   dist\AliScada_v1.4_linux_arm64\
   dist\AliScada_v1.4_linux_arm64.tar.gz
   dist\AliScada_v1.4_linux_armv7\
   dist\AliScada_v1.4_linux_armv7.tar.gz

Deploy ke Linux / Raspberry Pi

# 1. Copy tar.gz ke device
scp dist\AliScada_v1.4_linux_arm64.tar.gz user@192.168.1.50:/tmp/

# 2. Extract ke /opt/aliscada
sudo mkdir -p /opt/aliscada
sudo tar -xzf /tmp/AliScada_v1.4_linux_arm64.tar.gz -C /opt/aliscada --strip-components=1
sudo chmod +x /opt/aliscada/AliScada /opt/aliscada/start.sh /opt/aliscada/stop.sh

# 3. Jalankan manual
/opt/aliscada/start.sh

# 4. Install sebagai systemd service (auto-start)
sudo cp /opt/aliscada/aliscada.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable aliscada
sudo systemctl start aliscada

Windows

Cara A — Taruh ffmpeg.exe di folder AliScada (disarankan)Method A — Place ffmpeg.exe in the AliScada folder (recommended)

1. Download dari ffmpeg.org/download.html → pilih Windows builds → unduh ffmpeg-master-latest-win64-gpl.zip

   Download from ffmpeg.org/download.html → choose Windows builds → download ffmpeg-master-latest-win64-gpl.zip

2. Ekstrak ZIP → masuk folder bin\ di dalamnya → salin ffmpeg.exe

   Extract the ZIP → go into the bin\ folder inside → copy ffmpeg.exe

3. Tempel ffmpeg.exe ke folder yang sama dengan AliScada.exe

   Paste ffmpeg.exe into the same folder as AliScada.exe

4. Restart AliScada — webcam terdeteksi otomatis dalam 30 detik (tidak perlu restart lagi setelah itu)

   Restart AliScada — the webcam is auto-detected within 30 seconds (no restart needed after that)

Path yang diperiksa secara otomatis (urutan prioritas)Automatically checked paths (priority order)

<folder AliScada>\ffmpeg.exe        ← disarankan← recommended
<folder AliScada>\bin\ffmpeg.exe
C:\ffmpeg\bin\ffmpeg.exe
C:\Program Files\ffmpeg\bin\ffmpeg.exe
C:\Program Files (x86)\ffmpeg\bin\ffmpeg.exe
PATH sistem (jika ffmpeg sudah ada di PATH)System PATH (if ffmpeg is already in PATH)

Cara B — Tambahkan ffmpeg ke PATH sistemMethod B — Add ffmpeg to system PATH

1. Ekstrak ffmpeg ke C:\ffmpeg\

   Extract ffmpeg to C:\ffmpeg\

2. Tambah C:\ffmpeg\bin ke PATH:
   Control Panel → System → Advanced system settings → Environment Variables → Path → Edit → New → ketik C:\ffmpeg\bin

   Add C:\ffmpeg\bin to PATH:
   Control Panel → System → Advanced system settings → Environment Variables → Path → Edit → New → type C:\ffmpeg\bin

3. Restart AliScada

   Restart AliScada

VerifikasiVerification

ffmpeg -version

Linux

Linux Docker Edition

Tambahkan baris ini ke Dockerfile Anda sebelum instruksi COPY atau CMD:

Add this line to your Dockerfile before the COPY or CMD instruction:

RUN apt-get update && apt-get install -y ffmpeg && rm -rf /var/lib/apt/lists/*

Linux x86-64 — Standalone

Cara A — Package manager (disarankan):Method A — Package manager (recommended):

sudo apt install ffmpeg   # Debian / Ubuntu
sudo yum install ffmpeg   # CentOS / RHEL (perlu EPEL repo)

Cara B — Static build (tanpa install, tanpa root):Method B — Static build (no install, no root):

# Download dari github.com/BtbN/FFmpeg-Builds/releases
# Pilih: ffmpeg-master-latest-linux64-lgpl.tar.xz (~120 MB)

tar -xf ffmpeg-master-latest-linux64-lgpl.tar.xz
cp ffmpeg-master-latest-linux64-lgpl/bin/ffmpeg /opt/aliscada/
chmod +x /opt/aliscada/ffmpeg

Raspberry Pi 4 / 5 — ARM64 (OS 64-bit)

Cara A — Package manager:Method A — Package manager:

sudo apt install ffmpeg

Cara B — Static build:Method B — Static build:

# Download: ffmpeg-master-latest-linuxarm64-lgpl.tar.xz (~107 MB)
tar -xf ffmpeg-master-latest-linuxarm64-lgpl.tar.xz
cp ffmpeg-master-latest-linuxarm64-lgpl/bin/ffmpeg /opt/aliscada/
chmod +x /opt/aliscada/ffmpeg

Raspberry Pi 2 / 3 — ARMv7 (OS 32-bit)

sudo apt install ffmpeg

Verifikasi (semua Linux)Verification (all Linux)

ffmpeg -version

Windows

notepad C:\AliScada\config.json

Linux

sudo nano /opt/aliscada/config.json

Isi FileFile Contents

{
  "port":          3000,         // Port HTTP server
  "mqttPort":      1883,         // Port MQTT broker internal
  "jwtSecret":     "ganti-ini", // WAJIB diganti di produksi
  "logLevel":      "info",      // error | warn | info | debug
  "saveLogToFile": false        // true = simpan ke logs/combined.log
}

1. Buka browser → akses AliScada → login dengan akun admin.

   Open a browser → access AliScada → log in with the admin account.

2. Klik tombol Studio (pojok kanan atas halaman) → pilih menu License.

   Click the Studio button (top-right corner) → select the License menu.

3. Salin Machine ID menggunakan tombol Copy. Machine ID unik untuk setiap perangkat/instalasi.

   Copy the Machine ID using the Copy button. The Machine ID is unique to each device/installation.

4. Kirim Machine ID ke vendor melalui info@aliscada.com beserta tier lisensi yang diinginkan. Anda akan menerima license key.

   Send the Machine ID to the vendor at info@aliscada.com with the desired license tier. You will receive a license key.

5. Paste license key di form Activate License → klik Activate.

   Paste the license key in the Activate License form → click Activate.

Perbandingan Tier LisensiLicense Tier Comparison

Ringkasan Protokol yang Didukung

Modbus TCP

Modbus TCP adalah protokol paling umum untuk PLC dan perangkat industri yang terhubung via Ethernet. AliScada bertindak sebagai Master — membaca dan menulis register ke perangkat slave.

Modbus TCP is the most common protocol for PLCs and industrial devices connected via Ethernet. AliScada acts as the Master — reading and writing registers to slave devices.

Konfigurasi DeviceDevice Configuration

Tipe Register TagTag Register Types

Tipe Data TagTag Data Types

Byte Order (untuk 32-bit & 64-bit)Byte Order (for 32-bit & 64-bit)

Modbus RTU

Modbus RTU berkomunikasi melalui port serial RS-485 atau RS-232. Biasanya digunakan dengan konverter USB-to-RS485 di komputer server.

Modbus RTU communicates via RS-485 or RS-232 serial port. Typically used with a USB-to-RS485 converter on the server computer.

Register type, data type, dan byte order sama seperti Modbus TCP di atas.

Register type, data type, and byte order are the same as Modbus TCP above.

MQTT

AliScada mendukung dua mode MQTT:

AliScada supports two MQTT modes:

• MQTT Client (mqtt_client) — AliScada terhubung ke broker MQTT eksternal (Mosquitto, HiveMQ, EMQX, dll.) dan subscribe/publish topic.
• MQTT Broker (mqtt_broker) — AliScada menjalankan broker MQTT internal (Aedes). Perangkat IoT terhubung langsung ke AliScada tanpa software broker terpisah.

• MQTT Client (mqtt_client) — AliScada connects to an external MQTT broker (Mosquitto, HiveMQ, EMQX, etc.) and subscribes/publishes topics.
• MQTT Broker (mqtt_broker) — AliScada runs an internal MQTT broker (Aedes). IoT devices connect directly to AliScada without separate broker software.

Konfigurasi Device MQTT ClientMQTT Client Device Configuration

Konfigurasi Tag MQTTMQTT Tag Configuration

Tipe Payload

OPC UA Client

OPC UA adalah standar komunikasi industri modern yang digunakan oleh PLC Siemens (S7-1200/1500), Beckhoff TwinCAT, Schneider EcoStruxure, KEPServerEX, Ignition, dan banyak lainnya.

OPC UA is a modern industrial communication standard used by Siemens PLCs (S7-1200/1500), Beckhoff TwinCAT, Schneider EcoStruxure, KEPServerEX, Ignition, and many others.

Konfigurasi DeviceDevice Configuration

Konfigurasi Tag OPC UAOPC UA Tag Configuration

BACnet/IP Client

BACnet/IP digunakan di sistem BMS (Building Management System) dan HVAC — kontroler Distech Controls, Andover, Siemens Desigo, Johnson Controls Metasys, dan lainnya.

BACnet/IP is used in BMS (Building Management System) and HVAC systems — Distech Controls, Andover, Siemens Desigo, Johnson Controls Metasys controllers, and others.

Konfigurasi DeviceDevice Configuration

Tipe Objek BACnet yang DidukungSupported BACnet Object Types

Alamat tag ditulis dalam format KODE_OBJEK:INSTANCE, contoh: 0:1001 untuk Analog Input nomor 1001, 4:5 untuk Binary Output nomor 5.

Tag addresses use the format OBJECT_CODE:INSTANCE, e.g. 0:1001 for Analog Input number 1001, 4:5 for Binary Output number 5.

Modbus Server (Slave)

Dalam mode ini AliScada berperan sebagai Modbus slave — sistem eksternal (PLC master, HMI lain) dapat menulis nilai ke register AliScada. Nilai yang ditulis masuk sebagai nilai tag dan dapat ditampilkan di dashboard atau dipakai dalam alarm.

In this mode AliScada acts as a Modbus slave — external systems (PLC master, other HMIs) can write values to AliScada registers. Written values enter as tag values and can be displayed on dashboards or used in alarms.

Tag dengan tipe modbus_server menggunakan Holding Register. Tipe data yang didukung: uint16, int16, bool, float (2 register, big-endian), double (4 register, big-endian).

Tags of type modbus_server use Holding Registers. Supported data types: uint16, int16, bool, float (2 registers, big-endian), double (4 registers, big-endian).

Source Tag

Setiap tag modbus_server dapat dikonfigurasi dengan Source Tag opsional. Jika diset, register Modbus selalu mengembalikan nilai live dari tag sumber tersebut ke Modbus master — sehingga sistem eksternal dapat membaca nilai tag AliScada lainnya (misal: hasil kalkulasi script, nilai sensor Modbus RTU) melalui satu interface Modbus TCP slave. Online Value di Tag Editor juga akan mencerminkan nilai sumber secara real-time.

Each modbus_server tag can be configured with an optional Source Tag. If set, the Modbus register always returns the live value of the source tag to the Modbus master — so external systems can read other AliScada tag values (e.g. script calculation results, Modbus RTU sensor values) through a single Modbus TCP slave interface. The Online Value in Tag Editor will also mirror the source value in real-time.

SNMP Client

SNMP (Simple Network Management Protocol) digunakan untuk membaca status dan metrik dari perangkat jaringan seperti switch, router, UPS, server, dan perangkat industri yang mendukung MIB standar. AliScada mendukung SNMP v1 dan v2c.

SNMP (Simple Network Management Protocol) is used to read status and metrics from network devices such as switches, routers, UPS, servers, and industrial devices supporting standard MIBs. AliScada supports SNMP v1 and v2c.

Konfigurasi Device SNMP ClientSNMP Client Device Configuration

OID Browser (Walk)

Klik Walk OIDs di DeviceConfig setelah mengisi host/port/community untuk menelusuri semua OID yang tersedia. Pilih subtree MIB sebagai titik awal walk. Hasil dapat difilter berdasarkan OID atau deskripsi.

Click Walk OIDs in DeviceConfig after filling in host/port/community to browse all available OIDs. Select a MIB subtree as the walk starting point. Results can be filtered by OID or description.

Konfigurasi Tag SNMPSNMP Tag Configuration

Subtree MIB yang UmumCommon MIB Subtrees

SNMP Agent

Mode SNMP Agent membalik peran: AliScada bertindak sebagai server SNMP yang merespons permintaan dari SNMP manager eksternal seperti PRTG, Zabbix, Nagios, Cacti, atau snmpwalk. Semua nilai tag yang aktif di tag engine dipublikasikan otomatis — tidak perlu konfigurasi tag terpisah.

SNMP Agent mode reverses the roles: AliScada acts as an SNMP server responding to requests from external SNMP managers such as PRTG, Zabbix, Nagios, Cacti, or snmpwalk. All active tag values in the tag engine are published automatically — no separate tag configuration needed.

Konfigurasi Device SNMP AgentSNMP Agent Device Configuration

Struktur OID (enterpriseOid.1.kolom.N)OID Structure (enterpriseOid.1.column.N)

Contoh — Enterprise OID 1.3.6.1.4.1.99999, tag ke-3 bernama "Pressure":

Example — Enterprise OID 1.3.6.1.4.1.99999, 3rd tag named "Pressure":

• 1.3.6.1.4.1.99999.1.1.3 → Pressure
• 1.3.6.1.4.1.99999.1.2.3 → 4.5
• 1.3.6.1.4.1.99999.1.3.3 → 1 (good)
• 1.3.6.1.4.1.99999.1.4.3 → bar

BACnet MS/TP

BACnet MS/TP (Master/Slave Token Passing) adalah protokol BACnet yang berjalan di atas kabel RS-485 serial — berbeda dengan BACnet/IP yang menggunakan Ethernet. MS/TP umum ditemukan di sistem BMS (Building Management System), kontroller HVAC, dan perangkat otomasi gedung yang menggunakan kabel twisted-pair dua kawat.

BACnet MS/TP (Master/Slave Token Passing) is a BACnet protocol running over RS-485 serial cable — unlike BACnet/IP which uses Ethernet. MS/TP is commonly found in BMS (Building Management System), HVAC controllers, and building automation devices using two-wire twisted-pair cabling.

Konfigurasi Device BACnet MS/TPBACnet MS/TP Device Configuration

Format Alamat TagTag Address Format

Tag BACnet MS/TP menggunakan format TYPE:INSTANCE — sama dengan BACnet/IP. Selector device di TagEditor menampilkan semua device bertipe bacnet_client maupun bacnet_mstp_client.

BACnet MS/TP tags use the TYPE:INSTANCE format — same as BACnet/IP. The device selector in TagEditor shows all devices of type bacnet_client and bacnet_mstp_client.

Free Protocol

Free Protocol memungkinkan AliScada terhubung ke perangkat TCP atau serial yang menggunakan format frame yang sepenuhnya dikonfigurasi oleh pengguna — bukan Modbus atau MQTT. Cocok untuk: timbangan digital, barcode reader, GPS receiver, meter serial, sensor custom, atau perangkat embedded dengan protokol komunikasi sendiri.

Free Protocol allows AliScada to connect to TCP or serial devices using a frame format that is fully user-configured — not Modbus or MQTT. Suitable for: digital scales, barcode readers, GPS receivers, serial meters, custom sensors, or embedded devices with their own communication protocol.

Konfigurasi DeviceDevice Configuration

Mode Parsing TagTag Parsing Modes

Setiap tag Free Protocol memiliki dua mode parsing yang dapat dipilih:

Each Free Protocol tag has two parsing modes to choose from:

TX Frame Framing (per Tag)

Urutan perakitan frame TX: PREFIX + payload + CHECKSUM + SUFFIX + EOL

TX frame assembly order: PREFIX + payload + CHECKSUM + SUFFIX + EOL

ASCII Write Template — Placeholder

Frame Preview

Bagian Frame Preview di TagEditor menampilkan pratinjau byte TX yang akan dikirim, diperbarui secara real-time saat Anda mengetik template. Berguna untuk memverifikasi bahwa padding, checksum, dan urutan byte sudah benar sebelum menyambungkan ke perangkat.

The Frame Preview section in TagEditor shows a preview of the TX bytes to be sent, updated in real-time as you type the template. Useful to verify that padding, checksum, and byte order are correct before connecting to the device.

Write Value From Tag

Field Write Value From Tag menentukan tag sumber yang nilainya akan digunakan sebagai {VALUE_*} dalam Write Template. Jika diisi, AliScada mengambil nilai tag tersebut setiap kali frame TX dikirim — bukan nilai yang di-set secara manual. Cocok untuk meneruskan nilai sensor ke perangkat lain.

The Write Value From Tag field specifies the source tag whose value will be used as {VALUE_*} in the Write Template. If set, AliScada reads that tag's value each time a TX frame is sent — instead of a manually set value. Ideal for forwarding sensor values to another device.

Write Trigger

Menentukan kapan AliScada mengirim frame TX secara otomatis. Tersedia 3 mode:

Determines when AliScada automatically sends TX frames. 3 modes available:

Tag Write-OnlyWrite-Only Tags

Tag Free Protocol yang hanya memiliki Write Template (tanpa Poll Frame atau Parse Regex) adalah tag write-only. Tag ini tidak di-poll dan tidak menerima data dari perangkat. Kualitasnya otomatis diset ke GOOD saat startup — bukan BAD — sehingga Write Trigger dapat bekerja segera.

Free Protocol tags that only have a Write Template (no Poll Frame or Parse Regex) are write-only tags. These tags are not polled and do not receive data from the device. Their quality is automatically set to GOOD at startup — not BAD — so Write Triggers can work immediately.

Tipe Tag Khusus

Selain tag yang terhubung ke protokol di atas, AliScada juga mendukung tipe tag berikut:

In addition to tags connected to the protocols above, AliScada also supports the following tag types:

// Daya nyata dari tegangan × arus × faktor daya// Active power from voltage × current × power factor
return tags["VL1_Tegangan"] * tags["IL1_Arus"] * tags["PF_FaktorDaya"];

// Konversi unix timestamp ke string tanggal// Convert unix timestamp to date string
return toDatetime(tags["ts_kirim"].value, 'DD/MM/YYYY HH:mm:ss');

// Waktu server saat ini tanpa tag tambahan// Current server time without extra tags
return nowDatetime('HH:mm:ss');

// Selisih waktu dalam menit sejak event terakhir// Elapsed time in minutes since last event
const selisih = nowUnix() - tags["last_event"].value;
return Math.floor(selisih / 60);

Konfigurasi Channel (Email & Telegram)

Buka Studio → Notifications → Channel Settings.

Open Studio → Notifications → Channel Settings.

Email (SMTP)

1. Centang Enable untuk mengaktifkan channel Email.

   Check Enable to activate the Email channel.

2. Isi konfigurasi SMTP:

   Fill in the SMTP configuration:

3. Atur Send on new alarm / Send on alarm clear sesuai kebutuhan.

   Configure Send on new alarm / Send on alarm clear as needed.

4. Atur Min Severity — hanya alarm dengan severity ≥ nilai ini yang dikirim (info / warning / high / critical).

   Set Min Severity — only alarms with severity ≥ this value are sent (info / warning / high / critical).

5. Atur Alarm Cooldown — jeda minimum antar notifikasi alarm yang sama (dalam menit).

   Set Alarm Cooldown — minimum interval between identical alarm notifications (in minutes).

6. Klik Send Test Email untuk memverifikasi, lalu klik Save Configuration.

   Click Send Test Email to verify, then click Save Configuration.

Telegram Bot

1. Buat bot baru via @BotFather di Telegram → ketik /newbot → ikuti instruksi → salin Bot Token (format: 123456789:AAEF...).

   Create a new bot via @BotFather in Telegram → type /newbot → follow instructions → copy the Bot Token (format: 123456789:AAEF...).

2. Cari bot Anda di Telegram → kirim pesan /start. Langkah ini wajib sebelum bot bisa mengirim pesan ke Anda.

   Find your bot in Telegram → send the message /start. This step is required before the bot can send messages to you.

3. Dapatkan Chat ID — setelah kirim /start, buka URL berikut di browser:

   Get the Chat ID — after sending /start, open the following URL in your browser:

   https://api.telegram.org/botTOKEN/getUpdates

   Cari field "id" di dalam "from" — itulah Chat ID Anda (contoh: 136816235). Untuk grup/channel: tambahkan bot sebagai member dan gunakan Chat ID negatif (contoh: -100123456789).

   Find the "id" field inside "from" — that is your Chat ID (e.g. 136816235). For groups/channels: add the bot as a member and use the negative Chat ID (e.g. -100123456789).

4. Di Studio → Notifications → Telegram Bot: centang Enable, isi Bot Token dan Chat ID. URL getUpdates ditampilkan otomatis dari token yang Anda isi.

   In Studio → Notifications → Telegram Bot: check Enable, fill in Bot Token and Chat ID. The getUpdates URL is shown automatically from the token you enter.

5. Klik Send Test Message untuk verifikasi, lalu klik Save Configuration.

   Click Send Test Message to verify, then click Save Configuration.

Aturan Nilai Tag (Tag Event Rules)

Kirim notifikasi saat nilai sebuah tag memenuhi kondisi tertentu — misalnya saat suhu melebihi batas, atau pompa berhenti (nilai = 0).

Send a notification when a tag value meets a specific condition — for example when temperature exceeds a limit, or a pump stops (value = 0).

Buka Studio → Notifications → Tag Event Rules → klik + Add Rule.

Open Studio → Notifications → Tag Event Rules → click + Add Rule.

Contoh Template PesanMessage Template Example

⚠️ {name} terpicu!
Tag   : {tag}
Nilai : {value} (kondisi: {condition})
Waktu : {timestamp}

Decimal Digits & Int Scale

Widget Digital, Gauge, Setpoint, dan Process Tank mendukung dua opsi penskalaan untuk register yang menyimpan nilai integer berskala (umum di Modbus INT16/UINT16).

Digital, Gauge, Setpoint, and Process Tank widgets support two scaling options for registers storing scaled integer values (common in Modbus INT16/UINT16).

Contoh: Sensor suhu mengirim 293 untuk 29,3 °C. Set Decimal Digits = 1 dan aktifkan Int Scale. Widget menampilkan 29.3 °C, jarum gauge menunjuk ke 29,3, dan level tank terisi sesuai skala 0–100 °C.

Example: A temperature sensor sends 293 for 29.3 °C. Set Decimal Digits = 1 and enable Int Scale. The widget displays 29.3 °C, the gauge needle points to 29.3, and the tank level fills according to the 0–100 °C scale.

Distribusi Widget (Space Evenly)Distribute Widgets (Space Evenly)

Saat 2 atau lebih widget dipilih (Shift+klik), toolbar menampilkan tombol Align dan Distribute.

When 2 or more widgets are selected (Shift+click), the toolbar shows Align and Distribute buttons.

Notifikasi dari Widget (Write Event)Widget Notifications (Write Event)

Widget Button, Toggle, Setpoint, dan Slider dapat mengirim notifikasi setiap kali operator menulis nilai dari runtime dashboard.

Button, Toggle, Setpoint, and Slider widgets can send notifications every time an operator writes a value from the runtime dashboard.

Konfigurasi di Studio → Dashboards → pilih widget → Properties Panel → Notification on Write.

Configure at Studio → Dashboards → select widget → Properties Panel → Notification on Write.

1. Centang Enable notification on write.

   Check Enable notification on write.

2. Pilih channel: Email dan/atau Telegram.

   Select channel: Email and/or Telegram.

3. Isi Subject dan Message dengan template kustom. Klik chip variabel untuk menyisipkannya ke posisi kursor.

   Fill in Subject and Message with custom templates. Click variable chips to insert them at the cursor position.

Variabel Template WidgetWidget Template Variables

Persiapan — Instalasi DriverPrerequisites — Driver Installation

Sebelum menggunakan fitur ini, pastikan driver database sudah terinstal di server AliScada:

Before using this feature, make sure the database driver is installed on the AliScada server:

npm install mysql2   # MySQL / MariaDB
npm install pg       # PostgreSQL

Koneksi & Konfigurasi

Buka Studio → Ext DB, klik + Target Ekspor Baru, lalu isi formulir:

Open Studio → Ext DB, click + New Export Target, then fill in the form:

Klik Uji Koneksi untuk memverifikasi koneksi sebelum menyimpan.

Click Test Connection to verify the connection before saving.

Mode TriggerTrigger Mode

Saat Berubah — Sub-mode Tag TriggerOn Change — Tag Trigger Sub-modes

Saat tag trigger dipilih, dua field tambahan muncul:

When a tag trigger is selected, two additional fields appear:

Tag yang DieksporExported Tags

Di bagian Tag yang Diekspor, kelola tag yang akan diteruskan ke database eksternal:

In the Exported Tags section, manage the tags to be forwarded to the external database:

• + Tambah tag — pilih tag dari dropdown
• ▴ / ▾ — ubah urutan tag dalam daftar
• ● / ○ — aktifkan atau nonaktifkan tag tanpa menghapusnya
• × — hapus tag dari daftar

• + Add tag — select a tag from the dropdown
• ▴ / ▾ — change tag order in the list
• ● / ○ — enable or disable a tag without deleting it
• × — remove tag from the list

Schema Tabel yang Dibuat OtomatisAuto-Created Table Schema

AliScada membuat tabel di database eksternal secara otomatis jika belum ada:

AliScada automatically creates the table in the external database if it does not yet exist:

-- MySQL
CREATE TABLE IF NOT EXISTS `tag_history` (
  id        BIGINT AUTO_INCREMENT PRIMARY KEY,
  ts        BIGINT       NOT NULL,   -- Unix timestamp (milidetik)
  tag_name  VARCHAR(255) NOT NULL,
  value     DOUBLE,
  quality   TINYINT      DEFAULT 1,  -- 1 = good
  INDEX idx_tag_ts (tag_name, ts)
)

-- PostgreSQL
CREATE TABLE IF NOT EXISTS "tag_history" (
  id       BIGSERIAL PRIMARY KEY,
  ts       BIGINT       NOT NULL,
  tag_name VARCHAR(255) NOT NULL,
  value    DOUBLE PRECISION,
  quality  SMALLINT     DEFAULT 1
)

Untuk mengonversi kolom ts ke format waktu yang terbaca:

To convert the ts column to a readable time format:

• MySQL: FROM_UNIXTIME(ts / 1000)
• PostgreSQL: to_timestamp(ts / 1000.0)

Cara Membatasi Akses Dashboard

1. Buka Studio → Users → cari baris user yang ingin dibatasi.

   Open Studio → Users → find the user row you want to restrict.

2. Klik tombol Set Access di kolom Dashboards.

   Click the Set Access button in the Dashboards column.

3. Panel Dashboard Access terbuka menampilkan semua dashboard beserta checkbox.

   The Dashboard Access panel opens showing all dashboards with checkboxes.

4. Centang dashboard yang boleh diakses oleh user ini. Dashboard yang tidak dicentang tidak bisa dibuka oleh user tersebut.

   Check the dashboards this user is allowed to access. Unchecked dashboards cannot be opened by that user.

5. Klik Save Access.

   Click Save Access.

Menentukan Home Page (Halaman Pembuka)

Saat mode Restricted, kolom Home page muncul di kanan setiap baris dashboard yang dicentang.

In Restricted mode, the Home page column appears to the right of each checked dashboard row.

1. Centang minimal satu dashboard di panel Set Access.

   Check at least one dashboard in the Set Access panel.

2. Klik ikon ☆ di kolom Home page pada baris dashboard yang dijadikan halaman pembuka. Ikon berubah menjadi ★.

   Click the ☆ icon in the Home page column on the dashboard row to set as the opening page. The icon changes to ★.

3. Untuk mengosongkan, klik ★ kembali.

   To clear it, click ★ again.

4. Jika dashboard yang dipilih sebagai home page diuncentang, pilihan ★ otomatis dihapus.

   If the dashboard selected as home page is unchecked, the ★ selection is automatically removed.

5. Klik Save Access.

   Click Save Access.

Urutan Prioritas Halaman Pembuka

Cara Mengganti Bahasa

1. Di header aplikasi (kanan atas), cari tombol kecil bertuliskan ID atau EN.

   In the application header (top right), find the small button labeled ID or EN.

2. Klik untuk toggle:
   Tombol ID → klik → antarmuka beralih ke Bahasa Indonesia.
   Tombol EN → klik → antarmuka beralih ke English.

   Click to toggle:
   ID button → click → interface switches to Indonesian.
   EN button → click → interface switches to English.

3. Pilihan bahasa tersimpan di browser (localStorage) — tidak perlu dipilih ulang setiap login.

   Language preference is saved in the browser (localStorage) — no need to reselect on every login.

Cakupan Terjemahan

Cara Mengaktifkan Overlay

1. Buka Studio → Dashboards → klik dashboard yang ingin dikonfigurasi → masuk ke Dashboard Builder.

   Open Studio → Dashboards → click the dashboard to configure → enter the Dashboard Builder.

2. Klik area kosong pada canvas (pastikan tidak ada widget yang terpilih). Panel kanan akan menampilkan Canvas & Overlay Settings.

   Click an empty area on the canvas (ensure no widget is selected). The right panel will show Canvas & Overlay Settings.

3. Di bagian Overlay Window, pilih dashboard lain pada dropdown:
   ▲ Top Layer — dirender di atas semua widget dashboard utama.
   ◆ Middle Layer — dirender di atas widget biasa, di bawah widget dengan z-order sangat tinggi.
   ▼ Bottom Layer — dirender di bawah semua widget dashboard utama (underlay).

   In the Overlay Window section, select another dashboard from the dropdown:
   ▲ Top Layer — rendered above all main dashboard widgets.
   ◆ Middle Layer — rendered above normal widgets, below widgets with very high z-order.
   ▼ Bottom Layer — rendered below all main dashboard widgets (underlay).

4. Opsional — atur Pos X / Y untuk menggeser seluruh layer overlay dari pojok kiri atas canvas. Default (0, 0) berarti overlay diposisikan persis di titik asal canvas.

   Optional — set Pos X / Y to shift the entire overlay layer from the top-left corner of the canvas. Default (0, 0) means the overlay is positioned exactly at the canvas origin.

5. Klik Save Dashboard. Overlay akan muncul secara langsung di runtime.

   Click Save Dashboard. The overlay will appear immediately in runtime.

Start Position (Offset X / Y) per Layer

Setiap layer overlay dapat diposisikan secara independen menggunakan offset piksel dari sudut kiri atas canvas utama.

Each overlay layer can be positioned independently using pixel offsets from the top-left corner of the main canvas.

Contoh: Dashboard "top menu" berukuran 1280×100 ingin ditampilkan sebagai footer (posisi bawah canvas 1280×700). Set Bottom Layer → "top menu" → Pos X: 0, Pos Y: 600.

Example: A "top menu" dashboard sized 1280×100 should be displayed as a footer (bottom of 1280×700 canvas). Set Bottom Layer → "top menu" → Pos X: 0, Pos Y: 600.

Preview Overlay di Builder

Gunakan tombol 👁 View Overlay di panel Overlay Windows untuk menampilkan ghost preview semua layer yang dikonfigurasi langsung di atas canvas builder — tanpa meninggalkan editor.

Use the 👁 View Overlay button in the Overlay Windows panel to show a ghost preview of all configured layers directly on the builder canvas — without leaving the editor.

• Ghost widget dari tiap layer tampil dengan dashed border berwarna: biru (Bottom), kuning (Middle), ungu (Top).
• Label kecil di sudut (▼ Bottom / ◆ Middle / ▲ Top) menunjukkan layer masing-masing.
• Ghost widget bersifat non-interaktif — drag/resize widget utama tetap berjalan normal.
• Klik ✕ Hide Overlay untuk menutup preview.

• Ghost widgets from each layer appear with a colored dashed border: blue (Bottom), yellow (Middle), purple (Top).
• Small labels at the corner (▼ Bottom / ◆ Middle / ▲ Top) indicate each layer.
• Ghost widgets are non-interactive — drag/resize of main widgets works normally.
• Click ✕ Hide Overlay to close the preview.

Use Case — Menu Navigasi Bersama

Buat satu dashboard khusus berisi widget tombol navigasi (FKey Navigate). Jadikan dashboard tersebut sebagai Top Layer di semua dashboard lain. Jika menu berubah, cukup edit satu dashboard overlay — semua dashboard lain otomatis mengikuti perubahan.

Create a dedicated dashboard containing navigation button widgets (FKey Navigate). Set that dashboard as the Top Layer in all other dashboards. If the menu changes, just edit the one overlay dashboard — all other dashboards automatically follow the change.

Batasan

Tipe Shape yang Tersedia

Cara Menambahkan Shape

1. Buka Dashboard Builder → klik + Add Widget.

   Open Dashboard Builder → click + Add Widget.

2. Di bagian Shape pada palette, klik tipe shape yang diinginkan (Rect, Rounded Rect, Ellipse, Line, Arbitrary Line, Arc, Pie, atau Polygon).

   In the Shape section of the palette, click the desired shape type (Rect, Rounded Rect, Ellipse, Line, Arbitrary Line, Arc, Pie, or Polygon).

3. Widget muncul di canvas. Drag untuk memindahkan, tarik handle pojok/tepi untuk mengubah ukuran.

   The widget appears on the canvas. Drag to move, pull corner/edge handles to resize.

4. Klik widget untuk membuka panel Properties di kanan → atur warna, garis, dan properti spesifik tipe yang dipilih.

   Click the widget to open the Properties panel on the right → set colors, lines, and type-specific properties.

Properti Umum (Semua Tipe)

Properti Spesifik per Tipe

Editor Visual Titik — Arbitrary Line

Untuk tipe Arbitrary Line, panel Properties menampilkan editor mini berukuran 220×140 px yang merepresentasikan area widget secara proporsional. Editor ini memungkinkan pengeditan titik-titik polyline secara visual menggunakan mouse:

For the Arbitrary Line type, the Properties panel shows a 220×140 px mini editor that represents the widget area proportionally. This editor allows visual editing of polyline points using the mouse:

Editor menampilkan garis pratinjau berwarna sesuai Border Color yang dipilih, beserta nomor urut setiap titik (dimulai dari 0). Titik pertama berwarna hijau, titik lainnya berwarna biru. Tombol Clear all menghapus semua titik sekaligus.

The editor shows a preview line colored according to the selected Border Color, along with the sequential number of each point (starting from 0). The first point is green, others are blue. The Clear all button removes all points at once.

Tips Penggunaan

Tiga Tipe Payload MessagePack

Konfigurasi di Tag Editor

1. Buka Studio → Tags → pilih tag MQTT → klik Edit.

   Open Studio → Tags → select the MQTT tag → click Edit.

2. Di dropdown Payload Type, pilih salah satu: MessagePack, MessagePack (Base64), atau MessagePack (Hex).

   In the Payload Type dropdown, select one of: MessagePack, MessagePack (Base64), or MessagePack (Hex).

3. Opsional — jika payload berisi object/map, isi Field Path dengan dot notation untuk mengekstrak field yang diinginkan.
   Contoh: payload msgpack = {"sensors": {"temp": 23.5}} → Field Path = sensors.temp.
   Biarkan kosong jika payload langsung berupa angka/boolean tunggal.

   Optional — if the payload contains an object/map, fill in Field Path with dot notation to extract the desired field.
   Example: msgpack payload = {"sensors": {"temp": 23.5}} → Field Path = sensors.temp.
   Leave empty if the payload is a single number/boolean.

4. Klik Save.

   Click Save.

Contoh — ESP32 dengan ArduinoJson + MessagePack

// Kirim payload msgpack binary ke MQTT
#include <ArduinoJson.h>

JsonDocument doc;
doc["temp"] = 23.5f;
doc["hum"]  = 65;

uint8_t buf[64];
size_t len = serializeMsgPack(doc, buf, sizeof(buf));
mqttClient.publish("sensors/data", buf, len, false, 0);

Di AliScada: Payload Type = MessagePack, Field Path = temp (untuk tag temperatur) atau hum (untuk tag kelembaban).

In AliScada: Payload Type = MessagePack, Field Path = temp (for temperature tag) or hum (for humidity tag).

Auto Backup

AliScada v1.4 menyertakan layanan backup otomatis terjadwal. Backup mencakup seluruh database termasuk data historis tag — berbeda dengan Project Export yang hanya menyimpan konfigurasi.

AliScada v1.4 includes a scheduled automatic backup service. Backup covers the entire database including tag historical data — unlike Project Export which only saves configuration.

Mengaktifkan Auto Backup via UIEnable Auto Backup via UI

Auto backup nonaktif secara default. Aktifkan melalui Dev Studio → History Settings (login sebagai admin):

Auto backup is disabled by default. Enable it via Dev Studio → History Settings (logged in as admin):

1. Buka Dev Studio → History Settings.

   Open Dev Studio → History Settings.

2. Scroll ke bagian "Auto Backup" (bagian paling bawah halaman).

   Scroll to the "Auto Backup" section (at the bottom of the page).

3. Klik toggle Enabled hingga berubah menjadi biru.

   Click the Enabled toggle until it turns blue.

4. Atur Backup Interval (jam) dan Max Backups to Keep sesuai kebutuhan.

   Set the Backup Interval (hours) and Max Backups to Keep as needed.

5. Klik "Save Backup Settings".

   Click "Save Backup Settings".

6. Opsional: klik "▶ Backup Now" untuk langsung membuat backup pertama tanpa menunggu jadwal otomatis.

   Optional: click "▶ Backup Now" to immediately create the first backup without waiting for the automatic schedule.

# Aktifkan backup setiap 12 jam, simpan 14 copy terakhir
curl -X POST http://localhost:3000/api/system/backup/config \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"enabled": true, "intervalHours": 12, "maxBackups": 14}'

# Trigger backup sekarang (tanpa menunggu jadwal)
curl -X POST http://localhost:3000/api/system/backup/run \
  -H "Authorization: Bearer <token>"

# Lihat status, konfigurasi, dan daftar file backup
curl http://localhost:3000/api/system/backup/status \
  -H "Authorization: Bearer <token>"

Parameter BackupBackup Parameters

Lokasi File BackupBackup File Location

Download File BackupDownload Backup Files

Setiap file backup dapat diunduh langsung dari browser untuk disimpan di media eksternal (NAS, USB, cloud). Fitur ini tersedia di dua tempat:

Each backup file can be downloaded directly from the browser to save on external media (NAS, USB, cloud). This feature is available in two places:

• Database Files (Section 3) — tombol Download untuk mengunduh scada.db dan history_archive.db yang sedang aktif. Database akan di-flush ke disk terlebih dahulu agar file yang diunduh selalu dalam kondisi terbaru.
• Backup Files (Section 4) — tombol Download di setiap baris untuk mengunduh salinan backup yang sudah ada di folder data/backups/.

• Database Files (Section 3) — Download button to download the active scada.db and history_archive.db. The database is flushed to disk first to ensure the downloaded file is always the latest state.
• Backup Files (Section 4) — Download button on each row to download backup copies already in the data/backups/ folder.

Cara Restore dari Backup via UI (Hot-Restore)How to Restore from Backup via UI (Hot-Restore)

AliScada v1.4 mendukung hot-restore — mengganti database aktif tanpa perlu menghentikan server. Server akan reload otomatis dengan downtime ~5–10 detik.

AliScada v1.4 supports hot-restore — replacing the active database without stopping the server. The server reloads automatically with ~5–10 seconds of downtime.

1. Buka Dev Studio → History Settings → Auto Backup.

   Open Dev Studio → History Settings → Auto Backup.

2. Di tabel "Backup Files", temukan file scada_YYYYMMDD_HHMMSS.db yang ingin di-restore.

   In the "Backup Files" table, find the scada_YYYYMMDD_HHMMSS.db file to restore.

3. Klik tombol Restore di baris tersebut. Dialog konfirmasi akan muncul.

   Click the Restore button on that row. A confirmation dialog will appear.

4. Baca peringatan dengan seksama. Ketik RESTORE (huruf kapital semua) di kolom konfirmasi untuk mengaktifkan tombol.

   Read the warning carefully. Type RESTORE (all caps) in the confirmation field to activate the button.

5. Klik "Restore Database". Sistem akan mengganti database aktif dan me-reload semua layanan. Halaman akan refresh otomatis setelah selesai.

   Click "Restore Database". The system will replace the active database and reload all services. The page will refresh automatically when done.

Konfigurasi History untuk Skala BesarHistory Configuration for Large Scale

Dengan jumlah tag yang besar (>500 tag), pengaturan history berpengaruh langsung pada ukuran database dan performa sistem. Semua parameter disimpan di config.json dan dapat diubah melalui menu System → History Settings.

With a large number of tags (>500 tags), history settings directly affect database size and system performance. All parameters are stored in config.json and can be changed via the System → History Settings menu.

Penjelasan parameter:

Parameter explanation:

• heartbeatSecs — interval penulisan ulang nilai tag yang tidak berubah. Nilai besar = baris lebih sedikit ditulis per jam.
• flushSecs — seberapa sering data di-commit ke SQLite. Nilai besar = transaksi lebih jarang tapi lebih besar.
• retentionDays — berapa hari data live disimpan di scada.db. Data lebih lama dipindah ke archive. Kritis untuk ukuran database.
• archiveRetentionDays — berapa hari data archive disimpan sebelum dihapus permanen.

• heartbeatSecs — interval for rewriting tag values that have not changed. Larger value = fewer rows written per hour.
• flushSecs — how often data is committed to SQLite. Larger value = less frequent but larger transactions.
• retentionDays — how many days live data is kept in scada.db. Older data moves to archive. Critical for database size.
• archiveRetentionDays — how many days archive data is kept before permanent deletion.

Estimasi Ukuran DatabaseDatabase Size Estimate

Checklist Maintenance RutinRoutine Maintenance Checklist

📅 HarianDaily

• Cek System → Logs — tidak ada ERROR berulang di level critical.
• Cek Dev Studio → Devices — semua device yang seharusnya online menampilkan status Connected.
• Pantau memori server via System → Status — nilai RSS tidak boleh terus naik setiap hari (indikasi memory leak).

• Check System → Logs — no repeated ERROR at critical level.
• Check Dev Studio → Devices — all devices that should be online show Connected status.
• Monitor server memory via System → Status — RSS value should not keep rising every day (memory leak indicator).

📆 MingguanWeekly

• Verifikasi autobackup berjalan — buka Dev Studio → History Settings → Auto Backup, cek kolom "Last backup" menunjukkan waktu terbaru.
• Cek ukuran file data/scada.db — jika >500 MB pertimbangkan kurangi retentionDays.
• Cek folder data/backups/ — pastikan rotasi berjalan dan jumlah file sesuai maxBackups.
• Salin backup terbaru ke media eksternal (NAS/USB/cloud).
• Review Audit Log — cek aksi tidak biasa (login gagal berulang, perubahan konfigurasi di luar jam kerja).

• Verify autobackup is running — open Dev Studio → History Settings → Auto Backup, check that the "Last backup" column shows a recent time.
• Check data/scada.db file size — if >500 MB consider reducing retentionDays.
• Check the data/backups/ folder — ensure rotation is working and file count matches maxBackups.
• Copy the latest backup to external media (NAS/USB/cloud).
• Review Audit Log — check for unusual actions (repeated login failures, configuration changes outside business hours).

🗓️ BulananMonthly

• Cek ukuran data/history_archive.db — jika >5 GB pertimbangkan kurangi archiveRetentionDays.
• Test restore backup — restore file backup ke environment test untuk memverifikasi backup valid dan dapat dipulihkan.
• Cek sisa disk space server — historian tumbuh terus, pastikan disk tidak penuh (>20% free).
• Review tag yang disabled tapi masih terdaftar — hapus jika tidak diperlukan untuk menjaga database tetap bersih.

• Check data/history_archive.db size — if >5 GB consider reducing archiveRetentionDays.
• Test backup restore — restore a backup file to a test environment to verify the backup is valid and recoverable.
• Check server disk space — the historian keeps growing, ensure the disk is not full (>20% free).
• Review disabled tags that are still registered — delete if no longer needed to keep the database clean.

🔄 Setiap Upgrade AliScadaEvery AliScada Upgrade

1. Lakukan backup manual sebelum upgrade dimulai — klik "▶ Backup Now" di Dev Studio → History Settings → Auto Backup.

   Perform a manual backup before starting the upgrade — click "▶ Backup Now" in Dev Studio → History Settings → Auto Backup.

2. Lakukan juga Project Export dari UI (sebagai backup konfigurasi terpisah).

   Also perform a Project Export from the UI (as a separate configuration backup).

3. Simpan kedua file tersebut di luar server sebelum melanjutkan upgrade.

   Save both files off the server before proceeding with the upgrade.

4. Setelah upgrade, verifikasi semua device reconnect dalam 60 detik pertama dan periksa System Logs untuk error.

   After the upgrade, verify all devices reconnect within the first 60 seconds and check System Logs for errors.

Peringatan Penting untuk AdminImportant Warnings for Admin

Browser tidak bisa membuka AliScada

Tunggu 10–15 detik setelah start, kemudian refresh. Jika masih gagal, cek status server:

# Linux — cek apakah service berjalan
sudo systemctl status aliscada

# Lihat log error
sudo journalctl -u aliscada -n 50 --no-pager

Port sudah digunakan (EADDRINUSE)

Port 3000 atau 1883 sudah dipakai aplikasi lain. Cari proses yang memakai port tersebut:

# Linux
sudo lsof -i :3000
sudo lsof -i :1883

# Windows (CMD)
netstat -ano | findstr :3000

Edit config.json → ganti port ke nilai lain (mis. 3001) → restart.

Permission denied saat jalankan AliScada (Linux)

sudo chmod +x /opt/aliscada/AliScada \
              /opt/aliscada/start.sh \
              /opt/aliscada/stop.sh

Raspberry Pi — "Exec format error"

Binary yang digunakan tidak sesuai arsitektur. Cek arsitektur Pi:

The binary used does not match the architecture. Check Pi architecture:

uname -m
# aarch64 → gunakan file linux_arm64
# armv7l  → gunakan file linux_armv7

Server berhenti otomatis tiap 2 jamServer stops automatically every 2 hours

Ini adalah batasan Trial Mode. Server shutdown setelah 2 jam per sesi untuk melindungi lisensi. Restart server untuk melanjutkan, atau aktifkan lisensi penuh (Starter ke atas) untuk menghilangkan batas ini.

This is a Trial Mode limitation. The server shuts down after 2 hours per session to protect the license. Restart the server to continue, or activate a full license (Starter or above) to remove this limit.

Reset database

# Linux
sudo systemctl stop aliscada
sudo mv /opt/aliscada/data/scada.db /opt/aliscada/data/scada.db.bak
sudo systemctl start aliscada
# Database baru dibuat otomatis → akun: admin / admin123# New database created automatically → account: admin / admin123

Referensi CepatQuick Reference

Windows

1. Jalankan stop.bat untuk menghentikan server.

   Run stop.bat to stop the server.

2. Backup folder data\ jika ada data yang perlu disimpan.

   Back up the data\ folder if there is any data to keep.

3. Hapus seluruh folder instalasi AliScada.

   Delete the entire AliScada installation folder.

Linux (dengan systemd)Linux (with systemd)

sudo systemctl stop    aliscada
sudo systemctl disable aliscada
sudo rm /etc/systemd/system/aliscada.service
sudo systemctl daemon-reload

# Backup data jika diperlukan# Back up data if needed
cp -r /opt/aliscada/data ~/aliscada-backup

# Hapus instalasi# Remove installation
sudo rm -rf /opt/aliscada