Subject: From: Date:

RE: [ECS] FW: [ECS] Error in ECS.LOG Dan Hoehnen Wed, 26 Aug 1998 22:09:11 -0400 (EDT)

---

Mark and Michael,

This means that the dde command from ecs is not getting to ace.  The way 
the dde link to ace works is that ace has a control that is linked to ecs 
via dde.  Whenever ecs sends a dde message to ace it causes this 
control's 'change event' to fire.  The 'change event' code then runs, 
which forwards the msg from ecs to all clients and adds it to the ecs dde  
monitor window.  

It is possible to miss a msg from ecs if 2 consecutive msgs are 
identical.  If identical, no change event will be fired and so the msg 
will not be processed.  But, I don't think this is possible since each 
item name is in the msg and each item name is unique. 

Mark, can ecs re-send if it gets a dde error?

On Wed, 26 Aug 1998, Michael David wrote:

> Hi Dan!
> 
> Another possible clue:
> 
> The "I" commands ECS is sending, that ACE is not responding to, do not show
> up in the ECS DDE Monitor window during the update.
> 
> Cheers!
> 
> Michael David
> michael@michaeldavid.com
> 
> 
> -----Original Message-----
> From:	Dan Hoehnen [mailto:dhoehnen@infinet.com]
> Sent:	Wednesday, August 26, 1998 8:56 PM
> To:	ecs-list@vancouver.ml.org; michael@michaeldavid.com
> Cc:	ECS List
> Subject:	RE: [ECS] FW: [ECS] Error in ECS.LOG
> 
> Michael,  That's odd.  I would have expected there to be some errors.  I
> may have to re-think my theory on why there are errors when ace is
> updating item statuses.  But, I'm glad it works.
> 
> On Wed, 26 Aug 1998, Michael David wrote:
> 
> > Hi Dan!
> >
> > I'm not using  Mark's ECS DDE delay environment variable.  BTW, I appear
> to
> > have no timing problems when I send and "I" to ECS requesting a complete
> > inventory.  ECS spits out all 1624 items and ACE gets them all just fine;
> no
> > errors on either side.
> >
> > Cheers!
> >
> > Michael David
> > michael@michaeldavid.com
> >
> >
> > -----Original Message-----
> > From:	Dan Hoehnen [mailto:dhoehnen@infinet.com]
> > Sent:	Wednesday, August 26, 1998 9:00 AM
> > To:	ecs-list@vancouver.ml.org
> > Cc:	Michael David
> > Subject:	Re: [ECS] FW: [ECS] Error in ECS.LOG
> >
> > Mark,
> >
> > OK, I now understand what you mean by "respond".  VB handles all of the
> > handhsaking btwn the dde source and destination.  So, I have no control
> > over this response.  I can only assume the response is getting missed
> > because of timing problems.  I run into the same problem if I just send
> > an "I" command to ecs and then ecs returns all items configured.  ECS
> > sends the items so fast that ace can not keep up.  Well, I'm not really
> > sure it is because ace can not keep up, but it is definitely some kind of
> > timing problem.
> > <snip>
> >
> >
> 
> 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/             *
> *************************************************************************
> 
> 
> 
> 
> 

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/             *
*************************************************************************

---