as an update I've used the timing as described here instead of python: https://stackoverflow.com/questions/16548528/command-to-get-time-in-milliseconds
(I wasn't using it before because one of the other linuxes I was working with doesn't support %N in date formatting)
it works much better, now...
That is just the timing, as I was unable to get ms resolution with shell script I think. I could look more into that, I remember it was possible and didn't work, but I guess raspian should probably have that. I can try either that or just a python script then.
Basically I am wanting to run a test where I cut power to something for some time with the time ranging from 100's of ms to a few seconds. The unreliability is not a dealbreaker (as long as my python calls from sh script to get reasonable timing, which I should measure with oscilloscope...
dpkg-query: no packages found matching xscreensaver
not sure, but I think the screen blanking isn't relevant on lite configuration from that. From google it seems there is similar thing for console blanking I can disable.
Hello,
I have been running some tests using embedded linux (specifically raspberry pi) to switch a relay off and back on with specific timing. I have been having trouble with the timing being a bit unreliable and when I time my script there is huge different between the real time and user time...
Is it possible if I run echo u > /proc/sysrq-trigger to get the linux back to the same state it was before without waiting for a restart. My use case is an embedded linux system that needs to deal with sudden (though with short notice because of supercapacitors) loss of power, and possibly...