![]() Anyway, at the risk of masking the problem (and at A-B's suggestion), I set the watchdog time value at the max value of 255 (x 10 msec). We swapped out the processor and still had the problem about a week later. Also, the scan times are about 1/10 of the watchdog timer setting. ![]() However, my code has nothing exotic in it (see attachment). Usually, the watchdog timer indicates a self inflicted software problem such as an endless loop. (I had set the auto clear fault and auto run pits on powerup. The only way to clear that one was to cycle power. The expansion I/O configuration in the user program did not match the actual configuration, or specified a module that was not found, or the data size for the module was greater than what the module is capable of holding". When I cleared the fault from the error screen, I immediately would get: "Error 187 - I/O configuration mismatch, check module 1. At seemingly random times (about 1 or 2/week), I was getting: "Error 22 - The user watchdog scan time has been exceeded". ![]() I'm having an interesting problem with a Micrologix 1500 installation.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |