I am looking to understand the cause of the following message that is displayed in the status table of my loggers:
"Results for last program compiled: Warning: Watchdog timer Minion Signature __ triggered"
where the underscore is C3 in case 1 and U11 in case 2.
In case 1 it occured with a CR1000X and the problem began after updating to the latest O.S. It caused the logger to restart itself around midnight every day. C3 has a serial connection (a COM9522B sat modem)
In case 2 it occured with CR6s, observed with both O.S. 11.00 and 11.01. No O.S. update was performed; the loggers had the compiler warning and had been accumulating watchdog errors previously. U11 has a serial connection as well (a "Shape Array" inclinometer).
In both cases, the compiler warning disappeared after simply stopping the program and then restarting it.
I am mainly concerned about the potential for this issue to reccur unexpectedly but it would be good to understand the root cause regardless.
This post is under review.
Jut in case you do not get informed by another method or route, a new OS has been released today for both the dataloggers CR1000X V6.00 and CR6 V12.00. Among the many changes listed on the website for the new OS versions, is the following :
27. (Minor) Fixed a "Watchdog Timer Minion Signature Ux Triggered" caused by SerialOpen().
The new OS's can be downloaded from the website.
I too recieved the message Warning: Watchdog timer Minion Signature C1 triggered. And in this case C1 is the Tx port for the SAA232 from Measurand. I have not found a solution to the issue and the CR6 data logger has quit reading both the SAA and the connected Vibrating Wire Piezometers.