How is OnSystemStatus supposed to work?

[viper]

I have a thread that sits on a wait() when I want to send a control to the ISY but isISYReady() == false. In the OnSystemStatus method, if "busy == false", I wake the thread and let it send the control to the ISY. I have never seen a "busy == false" when handling OnSystemStatus. So, once my control sending thread detects isISYReady() == false, it never comes out of the wait.

 

Any suggestions?

 

Tom

[viper]

Please ignore this for now. I have more testing to do. It may be that all I see is busy == false and not busy == true.

 

Tom

[viper]

Next attempt here. It seems busy == false every time OnSystemStatus is called. Initially, my "control sending thread" would then attempt to send the control. I have now changed it so that if isISYReady() == false, it goes back into the wait. With trace points, I see that more than 90% of the time, the "control sending thread" is getting isISYReady() == false after being woke. In the one instance I saw isISYReady() == true, the control got sent and the light changed state. Just a reminder, I have 8 cores, so there is very little "thread waiting on execution queue".

 

Does any of this make sense?

 

Tom

[Michel Kohanim]

Hi Tom,

 

Please send your code snippet to support@Universal-devices.com and we'll take a look.

 

With kind regards,

Michel