Update Interlock Set?????

[devinashed]

While looking at the 'AESWDriver.exe' output I saw the following messages.
I haven't got a clue what this means,
Should I be concerned.

On 1 occasion the paylink unit started flashing green led - 'Application not running' yet the app and driver were running, but the driver window was continuously spiting out what you see below (and not accepting coins).

Code: Select all

02:13
Update Interlock Set. (304988 != 304987 / 304987)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (305420 != 305419 / 305419)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (309673 != 309672 / 309672)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (310845 != 310844 / 310844)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (312049 != 312048 / 312048)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (313880 != 313879 / 313879)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (314284 != 314283 / 314279)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (317574 != 317573 / 317573)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (318456 != 318455 / 318455)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (319580 != 319579 / 319573)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (320119 != 320118 / 320118)
Interlock Now Clear. (After 1 tries.)
Update Interlock Set. (321085 != 321084 / 321084)
Interlock Now Clear. (After 1 tries.)

[davebush]

Update Interlock Set. (304988 != 304987 / 304987)
Interlock Now Clear. (After 1 tries.)

Occaisonal occurrences of this are fine. It indicates that the Driver thread was checking for updates whilst your program was in the middle of a DLL call updating the interface area.

As the DLL calls are very short, if you get this a lot it indicates that your application is calling update functions very frequently. (The number quoted is incremented on each update call.)

If the intelock clears immediately (1 tries) it shows that there is no long term problem.

There is no direct connection between these messages and your observed problem, but the implication is that your application was "hammering" the interface for some reason.

For further analysis I really need to see a diagnostic log.