Subject: From: Date:

Re: [ECS] Command-J, Dallas Digital Temperature chips and schedule looping Mark Gilmore Mon, 17 Aug 1998 08:27:10 -0700

---

Hi Alan,

Congrads on figuring out how to read the temp in the 1st place :-).
I need to document this or add an Item Type for it (its on my list).

ECS should be setting the Item per the response from the HV.
I assume that the HV software is reporting the temp properly ?
If not, you probably a hardware or HV-software installation
problem, and so it is failing to return a status.

OTHWERWISE, please do the following:
1) Select the cmd-j in question in the Group Screen.
2) Press <ctrl-x> (DEBUG=1) & <alt-c> (CAPTURE ON).
   IGNORE ANY NASTY-LOOKING SCROLLING INFO.
3) Set the item to EXECUTE and wait until the item's state
   changes back from EXECUTE (denoting command completion).
4) Press <alt-c> (CAPTURE OFF) & <ctrl-x> NINE more times
   (DEBUG=0).
5) Email me CPT.TMP. This will show me what is going on.

Alan Platt wrote:
> 
> As a novice at ECS, I'm slowly learning how to use the Dallas Semiconductor
> ICs using ECS (ie W95) v. 3.4.020 and HomeVision. I use the Command-J item
> type, with the command set depending on the IO# of each IC, for example
> Q0601,and set to EXECUTE.. It works fine, except that the temperature data
> is not updated until I stop, exit and then restart ECS. There has to be
> something basic that I'm missing here. All other inputs (like analog
> voltages and digital inputs) work fine and are continuously updated.
> 
> Any help will be much appreciated. I hate the thought of attempting
> subroutine calls, or the equivalent.
> 
> Thanks.
> 
>   ------------------------------------------------------------------------
> 
>                      Name: winmail.dat
>    winmail.dat       Type: application/ms-tnef
>                  Encoding: base64

---