Replies: 4 comments
-
I have a draft, not Best Practice, but it works for me at the moment. I created a unit file for FUXA and reloaded systemd on the Raspberry Pi:
The Executable is a bash script in my install directory, that mimics the manual start of FUXA:
To start/stop my FUXA connection to the modbus-device and the webservice on port 1881
To enable/disable this service for autostart
|
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Interesting, didn't know P(rocess) M(anager) 2. Thank you, amazing work! |
Beta Was this translation helpful? Give feedback.
-
I could reduce the fuxa unit file by introducing the WorkingDirectory that fuxa needs as environment:
No bash script required any longer. |
Beta Was this translation helpful? Give feedback.
-
Dear FUXA developers,
I installed FUXA on my Raspberry Pi and can start it with sudo fuxa.
My first project with FUXA works and connects to a Modbus-TCP device to get some registers. Excellent, the best opensource HMI I could find so far!
But I have the problem to start the fuxa script at boottime and using my project.
I tried writing a fuxa.service for systemd based on your script /usr/bin/fuxa and it starts fuxa successfully on Port 1881. But it starts with an empty project and unconfigured devices then.
Is there a way other than starting fuxa manually on a Linux system?
Kind regards
Beta Was this translation helpful? Give feedback.
All reactions