Subject: From: Date:

RE: [ecs] RE: Ocelot Analog reads Reynolds,Martin Wed, 4 Aug 2004 08:30:11 -0700

Wed, 4 Aug 2004 08:30:11 -0700

---

It's scary when you start to recognize these strings...

 

There are two possibilities. One is that the Ocelot is failing to read the secu-16 properly.
The other is that the Ocelot is reporting incorrectly to ECS. There are some protocol
problems with the Ocelot.

 

I would suggest writing a small program for the Ocelot that captures a zero reading
and turns on a light or somesuch obvious trick. I don't expect the light to go on, based
on previous experience. 

 

         

From: Rob Hicks [mailto:rob.hicks@comcast.net] 
Sent: Wednesday, August 04, 2004 7:59 AM
To: ecs@netbloc.com
Subject: RE: [ecs] RE: Ocelot Analog reads

 

Mark,

 

I have been tracing the output from the sensor with an oscilloscope. During the event
in question, the oscilloscope showed a sensor voltage of 0.79+-3 on the Ocelot-Secu-16
ani input port. In other words, the Ocelot should have returned 40 as the result, not
0.  I realize that the oscilloscope could be aliasing the result but I don't think so.

 

--Rob

 

         

From: Mark Gilmore [mailto:mark1@markgilmore.net] 
Sent: Wednesday, August 04, 2004 8:54 AM
To: Rob Hicks
Cc: ecs@netbloc.com
Subject: [ecs] RE: Ocelot Analog reads

 

It's as I suspected: The Ocelot is sometimes returning 0 for this ANI:

0 response (see val in asterisks):
        Srv:Get SECU ani data
        8/04 07:29:45 TX: 2a 00 00 8b b4 00 a4 78
        8/04 07:29:45 RX: 2a 00 00 8b b4 00 29 00 27 00 fd 00 fd 00 *00* 00 ff ff ff

        8/04 07:29:45 SetPrpV:Ocelot.Ana-In=5/7/0 updater=Ocelot sendupdate=1

36 (24 hex) response:
        Srv:Get SECU ani data
        8/04 07:30:46 TX: 2a 00 00 8b b4 00 a4 78
        8/04 07:30:46 RX: 2a 00 00 8b b4 00 29 00 27 00 fd 00 fd 00 *24* 00 ff ff ff

        8/04 07:30:46 SetPrpV:Ocelot.Ana-In=5/7/36 updater=Ocelot sendupdate=1

I think that Martin may be seen a similar problem (I'm forwarding this email to the
list).
But are we *sure* that this input is not really 0 sometimes ?

At 08:25 AM 8/4/2004 -0600, you wrote:



Mark,

 

Ive attached logs for the temperature sensor and the Ocelot set at level 2. The latest
0read on the analog appears to have happened at 8:04:54.

 

--Rob

 

         

From: Mark Gilmore [mailto:mark1@markgilmore.net] 
Sent: Wednesday, August 04, 2004 5:17 AM
To: Rob Hicks
Subject: Re: Ocelot Analog reads

 

i strongly suspect that ecs is the "messenger" here.
set Ocelot.Diagnose to 2, so I can see the ani data packet.

At 09:29 PM 8/3/2004 -0600, you wrote:


Mark,

 

Randomly about every ½ hour my ECS object tied to a temperature sensor reads a zero.
Im pretty sure that the temperature sensor does not have any problems. Im using fairly
stable temperature sensors. And, I never had problems with my TimeCommander Plus using
the same sensors reading what appear to be bogus values. I have enabled level 2 logging
on a sensor (attached). Any ideas why this happens? Ive scanned the sensor with an oscilloscope
and havent seen any erratic behavior.

 

--Rob

 

 


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com <http://www.grisoft.com/> ).
Version: 6.0.726 / Virus Database: 481 - Release Date: 7/22/2004

Mark Gilmore
http://OmnipotenceSoftware.com <http://omnipotencesoftware.com/> 



---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com <http://www.grisoft.com/> ).
Version: 6.0.726 / Virus Database: 481 - Release Date: 7/22/2004

Mark Gilmore
http://OmnipotenceSoftware.com <http://omnipotencesoftware.com/> 

---

---