Subject: From: Date:

Fwd: SECU-16/16I info Mark Gilmore Tue, 27 Jul 2004 16:10:25 -0700

Tue, 27 Jul 2004 16:10:25 -0700

---

Well, I spoke too soon.
I am now seeing the exact same problems with the SECU16I as I did with the 
SECU16:
Ocelot detects when an input changes, but then randomly reads incorrect 
input states.
I can't detect a pattern, other than the fact that the wrong states are 
always ON (which they should be OFF).

>Date: Tue, 27 Jul 2004 15:52:06 -0700
>To: ecsl@netbloc.com, ecs@netbloc.com
>From: Mark Gilmore <mark1@markgilmore.net>
>Subject: Fwd: SECU-16/16I info
>
>I just determined that my SECU-16 *was* setup properly (i.e. for 
>supervised-inputs - all jumpers at position 2-3).
>I was also using the required 1K ohm resister.
>So my SECU-16 problems were *not* pilot error as I suspected.
>
>>Date: Tue, 27 Jul 2004 15:42:02 -0700
>>To: ecsl@netbloc.com, ecs@netbloc.com
>>From: Mark Gilmore <mark1@markgilmore.net>
>>Subject: SECU-16/16I info
>>
>>FYI:
>>The problems I was seeing was with the SECU-16 (which I stupidly 
>>*thought* was a 16I).
>>When I connected a 16I, this inputs seemed to work as expected.
>>I now suspect that *my* problems (at least) were due to my failure to 
>>setup the I/O points as INputs
>>(though I have yet to read up on what that setup procedure is :-)).
>>Perhaps this is done via the CPUXA pgm ?
>>
>>Mark Gilmore
>>http://OmnipotenceSoftware.com
>
>Mark Gilmore
>http://OmnipotenceSoftware.com

Mark Gilmore
http://OmnipotenceSoftware.com 

---

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

---