1) Whenever there is a failure on Modbus, an error POST into the server to a specific URL, with error description.
2)Log (syslog) to a file every "sample" or set of variables in the ARM device. We should have a file that supports FIFO of let's say 1000 readings. Just in case we have problems.This should be made, in between readings, in order not to slow down program execution. For Logger we could just redirect stdout and stderr to a specific file using dup2
other URL @blabno We will have to make a specific URL for this.
I think it's best that you just log exceptional errors in syslog. Please scan the program for corner cases.
You could also make a log that prints in a file every sample is reading for Modbus. (just for debugging). Maybe you can set a CFLAG for this feature.
We need to have the following features:
1) Whenever there is a failure on Modbus, an error POST into the server to a specific URL, with error description.
2)Log (syslog) to a file every "sample" or set of variables in the ARM device. We should have a file that supports FIFO of let's say 1000 readings. Just in case we have problems.This should be made, in between readings, in order not to slow down program execution. For Logger we could just redirect stdout and stderr to a specific file using dup2