Subject: From: Date:

RE: [ECS] Comm Error with JDS Time Commander Plus in v.4.008 Rob Hicks Mon, 25 Sep 2000 14:42:35 -0600

---

Mark,

I've been running the previous version (Windows) for several months (I'm
guessing the whole summer).

I've also been running the Linux version. I haven't run it for a quite
awhile though. I'll download the latest and see if it comes up lame with the
JDS as well.

I do remember that you made a change on the Linux side (and probably in the
Windows code as well) with the serial module because I was getting buffer
errors under Linux. Could that be the problem?

Relative to the JDS Time Commander Plus, I'd like to throw it as far as ...
but right now I'd rather spend my money on something a little more
productive:-).

Rob

-----Original Message-----
From: Mark Gilmore [mailto:omnip@usit.net]
Sent: Monday, September 25, 2000 2:34 PM
To: ecs-list@netbloc.com
Subject: Re: [ECS] Comm Error with JDS Time Commander Plus in v.4.008

Hi Rob,
The JDS code is the LAST think on this earth that I would
intentially mess with, as the JDS "protocol" is the nastiest
beast I have EVER seen :-).
But I MAY have made a change to a serial I/O module that
that could cause the problem. Can you run your previous
ECS for a while to make SURE that it is caused by the upgrade ?
tanx
--
Mark Gilmore
Omnipotence (ECS home automation software)
http://omnipotencesoftware.com
423-745-0026
Hours: Mon-Sat, 9AM-8PM/EST


Rob Hicks wrote:
>
> I just upgraded my Windows ECS box from 4.4.004 to 4.4.008. I'm running a
> JDS Time Commander Plus with 2 I/O expansion boards.
>
> I'm getting the following error under 4.4.008:
>
> 13:03:19:ERROR:CCE3:COM1 (COMM err #2:RX overrun) (Item "TC+ Base")
> 13:03:21:ERROR:Unexpected hex char "!" (7!):!!09/25047320a47! (Item "TC+
> Base")
>
> 13:25:01:ERROR:CCE3:COM1 (COMM err #2:RX overrun) (Item "TC+ Base")
> 13:25:03:ERROR:Unexpected hex char "!" (0!):!!09/25048622c30! (Item "TC+
> Base")
>
> "TC+ Base" in the Time Commander Plus base station (station #0).
>
> I'm getting this error about every 20 minutes. Curiously, when the error
is
> received, the PLC interface stops working (won't detect any inputs) but
the
> state does not change (does not become not operational) so I can't
> automatically reset the interface using an ECS event.
>
> I have looked carefully at my events and don't think that any of them are
a
> problem. Just for grins, I noticed that the interface is supposed to
become
> receiving when ECS requests and receives states from TC+ Base so I decided
> to have my events set temperatures when the TC+Base state is receiving. It
> didn't work. As near as I can tell, the state never changes. Is this a
bug?
>
> To help debug the errors, I set debug to On. It ran without a hitch for
over
> 12 hours. I stopped it and started again without debug. It errored out
after
> 20 minutes. I turned debug back on and it ran without a hitch again for
well
> over 6 hours.
>
> As an additional attempt to isolate malicious events, I changed the
initial
> call status of all my events to "yes." Without debug on, ECS errored out
> with the same type of error after about 20 minutes. I then loaded up an
> ECS.CFG file with only 1 item in it and ran it without debug. It errored
out
> again after about 20 minutes.
>
> Did something happen to the PLC-Interface-2G interface since 4.4.004?
>
> Rob

---