Install FUXA on the reComputer RK Series

Last updated:

FUXA is a browser-based SCADA/HMI and dashboard platform. It can connect to data sources such as MQTT, Modbus, and OPC UA and turn their values into visual monitoring screens. This guide shows how to install FUXA on reComputer RK3576 and confirm that its service and web editor are working.

Environment: reComputer RK3576 DevKit running ARM64 Armbian (Debian Bookworm) with Docker installed. Because the latest image can change, pin a verified image version or digest when you need a reproducible deployment.

Before you begin

  • Connect the RK3576 and your computer to a trusted network.
  • Have SSH or terminal access to the RK3576 and a working Docker Engine.
  • Check that the system drive has enough free space for the image to avoid a failed pull.

On the RK3576, check the environment:

bash
uname -m
cat /etc/os-release
docker --version
df -h /

uname -m should report aarch64. If Docker is not installed, install and start Docker Engine using instructions appropriate for your Armbian image before continuing.

Step 1: Pull the FUXA ARM64 image

bash
sudo docker pull --platform linux/arm64 frangoteam/fuxa:latest

If the pull times out, check connectivity to Docker Hub. A proxy configured only in your SSH shell does not automatically configure the Docker daemon; if your network requires a proxy, follow the Docker daemon proxy instructions with your network's proxy address.

Step 2: Start the container

After pulling the image, run the FUXA container:

bash
sudo docker run -d \
  --name fuxa-rk3576 \
  --platform linux/arm64 \
  --network host \
  --restart unless-stopped \
  -v fuxa_rk3576_appdata:/usr/src/app/FUXA/server/_appdata \
  -v fuxa_rk3576_db:/usr/src/app/FUXA/server/_db \
  -v fuxa_rk3576_logs:/usr/src/app/FUXA/server/_logs \
  -v fuxa_rk3576_images:/usr/src/app/FUXA/server/_images \
  frangoteam/fuxa:latest

-d runs FUXA in the background, so a container ID rather than a webpage is the expected output. The named volumes preserve project data, history, logs, and uploaded images. This command uses Linux host networking, so it does not need -p 1881:1881. Keep port 1881 within a trusted network, and configure access control before exposing FUXA more widely.

Step 3: Verify the service

bash
sudo docker ps --filter name=fuxa-rk3576
sudo docker logs --tail 40 fuxa-rk3576
curl -I http://127.0.0.1:1881/
hostname -I

The container should show Up, the logs should report FUXA started!, and the local web request should return an HTTP response. Use the RK3576's LAN address from hostname -I on a computer on the same trusted network:

  • Runtime page: http://<RK3576_IP>:1881/
  • Web editor: http://<RK3576_IP>:1881/editor

The runtime page may initially be blank because no visualization has been created yet.

Step 4: Check the editor

Open the editor and select MainView in the Views panel. As a small check, place a text element from the General tools onto the canvas, enter a short label such as RK3576 FUXA test, save with the disk icon, and use the preview button. Confirm that the saved label appears in the runtime view.

At this point FUXA is installed and its editor is usable. No live device data, MQTT connection, alarm, or SCADA process has been configured yet.

Troubleshooting

  • The page does not load from your computer: Check the container status, curl -I http://127.0.0.1:1881/ on the RK3576, its LAN IP, and the network/firewall path to port 1881.
  • The runtime page is blank: Open /editor and save a view. A blank initial runtime page alone is not an installation failure.
  • The image pull fails: Check free disk space and Docker daemon network/proxy configuration. Do not remove unrelated images without reviewing them.

Next steps

After installation, see the FUXA documentation to connect a data source, bind tags to gauges and charts, and view live data on the runtime page.