Subject: From: Date:

Re: [ECS] FW: [ECS] Error in ECS.LOG Dan Hoehnen Tue, 25 Aug 1998 22:35:49 -0400 (EDT)

---

Michael,

I seem to have missed your previous msg on this problem.  Please re-send 
to me if you still have it.

I looked at my code that updates item status info and I think I have 
found the problem.  Let me explain how it works and how I changed it and 
maybe you or Mark can say if it sounds liek what I did will work.

Currently, when ace requests the status of an item, ace then goes into a 
loop waiting for the status.  The loop is only exited when a status msg 
is received from ecs, the user presses the CANCEL button or ace times out 
waiting for the response from ecs.  So, ace is still receiving status 
msgs from ecs during this, in fact that is exactly what ace is waiting 
for.  The problem, I think, is that ace is waiting for ANY status message 
from ecs, not the status for the most recent item requested.  So, if ace 
requests the status of item 'One' and then while waiting for its status 
to come back from ecs, ecs sends the status for item 'Two', ace will exit 
the loop and request the status of the next item.  

I have changed it so that ace now waits for the status corresponding to 
the last item requested.  If while waiting, another status msg comes in 
for another item, ace will process it normally and then continue waiting 
for the status of the last item requested. 

This is implemented in version 1.1.10, which I will upload shortly.

I can not test this out right now, so you will have to let me know if it 
works or not.  

On Tue, 25 Aug 1998, Michael David wrote:

> Hi Mark and Dan!
> 
> I downloaded the new Beta version of ECS, and ECS is now showing which item
> state-change packets ACE is not responding to.
> 
> Here's what I THINK is happening:
> 
> As I mentioned in a previous email, ECS was giving me this error when ACE
> was doing a "bulk update" of the status of all monitored ECS items.  ACE
> does this by sending an "I" command to ECS for each item ACE is set up to
> monitor.
> 
> In my case, I have 300 or so items to update, which, if I wasn't seeing the
> errors, would probably take about 2 minutes to go through.  As it is now,
> because of the errors, it takes about four minutes.
> 
> So, after clicking on "Update" in ACS' ECS config window, ACE then goes
> through and requests the status of  each item, and ECS responds to each
> request.  But, while this is going on, other ECS items are changing states,
> and ECS immediately sends the status of those items to ACE.  But, since ACE
> is still busy going through it's entire list, it misses these status-change
> packets, and ECS reports the error.
> 
> Make sense?
> 
> So Dan, is there a way for ACE to accept, and respond to, state-change
> packets while going through an update?
> 
> Cheers!
> 
> Michael David
> michael@michaeldavid.com
> 
> 
> -----Original Message-----
> From:	Mark Gilmore [mailto:markgilmore@cococo.net]
> Sent:	Tuesday, August 25, 1998 11:47 AM
> To:	ecs-list@vancouver.ml.org
> Subject:	Re: [ECS] Error in ECS.LOG
> 
> Michael, The redac is unrelated - I failed to service (log) the error, and
> so it "fell into" other logic. I corrected this in the beta that I am about
> to upload. It will at least report the real item invlolved.
> The error means that the client is not responding to a state-change packet.
> --
> Mark Gilmore
> Omnipotence
> Voice:423-745-0026
> FAX  :423-745-1714
> http://members.a2zsol.com/omnipotence.html
> 

Dan Hoehnen                            
dhoehnen@infinet.com                   
He who dies with the most toys, wins! 
*************************************************************************
* Home Automation Index: http://www.infinet.com/~dhoehnen/ha/list.html  *   
*                                                                       *
* Port16.ocx & Port32.ocx - Give Visual Basic access to I/O ports       *
*                http://www.infinet.com/~dhoehnen/software/             *
*************************************************************************

---