System configuration: APC910 + 2 x 5AP1130.185C - 000. The SDK function is used for the interlock of the two screens. The current situation is that under the normal use of the screen - locking function, there are occasional situations where the screen cannot be locked or unlocked. Monitoring shows that the ADI function block reports an error 170, as shown in the following figure. What is the cause of this fault and how can we solve it?
Hi,
haven’t seen that so far, but it sounds a bit like a concurrent access to the ADI device, and/or a timing topic.
Is there any other software running on the system that uses ADI?
Is the behavior changing if waiting some short time inside your software (for example “some milliseconds”) between the SelectPanel and the UnlockPanel call?
Another question, only because I’m curious: in your screenshot, it looks like that the function is called every two seconds. Is this only for testing or because of a retry after error, or is the software really accessing the panel every 2 seconds?
Best regards.
Hi Alexander,thank you very much for your answer. We haven’t used other ADI functions. Also, our current program executes once every 2 - second cycle. Perhaps the problem is due to the hypervisor. I’ll try following Job’s solution first. Thank you.
1 Like
Hi Job，yes, we are using the hypervisor. We’ll first try the method you provided to see if it works. Thank you very much.
1 Like
Hi,
I totally agree, using hypervisor means automatically a concurrent access situation and ADI must run in hypervisor mode, so you should try Jobs advice, I’m pretty sure it will help.
Best regards.
Hi,Job, I have checked the registry settings of the APC910. The ADI hypeivisor mode is turned on by default, as shown in the following picture.However, the malfunction still occurs frequently. Are there any other reasons that could cause it? My program is currently executed in a cycle every 2 seconds
You could check to boot Windows without hypervisor. Is your interaction with ADI then stable? If its still appearing then something else in Windows drivers/programs are influencing it.
Other then that i don’t have any additional tips what could cause your issue.
Please reach out to the support department if no one else in the community has more tips for you.
I’m not sure if upgrading the ADI driver version will work. The current relevant driver versions are shown in the figure below. In addition, when we used the same ADI function at another customer’s site, there was no feedback of any faults. However, they didn’t use the hypervisor technology. By comparison, it is most likely that the fault is caused by the hypervisor. Moreover, our application software is currently planned to change the cycle from 2 seconds to 1.6 seconds, so that it is not an integer multiple of 500 milliseconds, to see if this can have an effect.
Hi,
when changing the software anyway, maybe it’s worth a try to implement a internal retry mechanism after a shorter period of time if the error was thrown, for example “if error → wait 500ms → try again → then restart the normal wait period”.
Best regards.