You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the sailtrack-x708_* scripts are written in bash. Consider moving to an other language for these scripts. This would make it easier to modify and debug, and it would make them more consistent with the other non-bash scripts.
The text was updated successfully, but these errors were encountered:
It seems also that we have some problem with GPIO pin, in particular reading the satuts of sailtrack-x708_pwr.service I've seen this.
root@sailtrack-core:/# systemctl status sailtrack-x708_pwr.service
● sailtrack-x708_pwr.service - SailTrack-X708_PWR
Loaded: loaded (/etc/systemd/system/sailtrack-x708_pwr.service; enabled; preset: enabled)
Active: active (running) since Fri 2024-03-15 18:17:04 CET; 1h 23min ago
Main PID: 279 (sailtrack-x708_)
Tasks: 2 (limit: 1069)
CPU: 10min 15.569s
CGroup: /system.slice/sailtrack-x708_pwr.service
├─ 279 /bin/bash /boot/sailtrack/sailtrack-x708_pwr
└─119326 "[sailtrack-x708_]"
Mar 15 19:40:20 sailtrack-core sailtrack-x708_pwr[279]: /boot/sailtrack/sailtrack-x708_pwr: line 20: /sys/class/gpio/gpio5/value: No such file or directory
Upon further investigation, it seems this problem stems from a malfunction with the Geekworm X708 V2 shield. Despite the error message, the script itself appears to be functioning correctly.
To address this issue and ensure consistency, I'm currently developing a Python script to replace the existing bash script.
Currently, the
sailtrack-x708_*
scripts are written in bash. Consider moving to an other language for these scripts. This would make it easier to modify and debug, and it would make them more consistent with the other non-bash scripts.The text was updated successfully, but these errors were encountered: