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
In the read cycle, the program additionally transfers card data to the server.
The problem is as follows:
When a script is started by a command from a terminal window, the program launch is not always correct, namely, the program starts, but the reading does not always start.
It was noticed that if a sufficiently long time more than 5 minutes passes after the system is turned on or restarted, the script works stably, but if I start the program immediately after the system starts, for example, within a minute, the script does not work correctly, but if you interrupt it CTL> C and restart, everything starts working correctly. And then you can repeatedly stop and start this software - everything works.
The problem was discovered when I added the launch to the autostart file at system startup.
Thank.
The text was updated successfully, but these errors were encountered:
Hello!
There is a problem with the launch of a similar program.
Platform - Raspberry Pi 3 B+, OS Raspbian with a graphic shell.
The script is written in Python 2.7 -
Read_sim_QQ.py (https://github.com/PaulLos/RPi-QQ.git)
In the read cycle, the program additionally transfers card data to the server.
The problem is as follows:
When a script is started by a command from a terminal window, the program launch is not always correct, namely, the program starts, but the reading does not always start.
It was noticed that if a sufficiently long time more than 5 minutes passes after the system is turned on or restarted, the script works stably, but if I start the program immediately after the system starts, for example, within a minute, the script does not work correctly, but if you interrupt it CTL> C and restart, everything starts working correctly. And then you can repeatedly stop and start this software - everything works.
The problem was discovered when I added the launch to the autostart file at system startup.
Thank.
The text was updated successfully, but these errors were encountered: