Re: translator question

["Robert Green" <ROBERT_GREEN1963@xxxxxxxxx>]

"Dave Houston" <nobody@xxxxxxxxxxxx> wrote in message

> I've never used the Bobcat. My experience was with the ASCII strings in
the
> CPU-XA, Ocelot & Leopard. IIRC I was told they were added specifically to
> support HAI's ProLink ASCII protocol. They had a maximum length (32 chrs?)
> and were also useful with their modem.
>
> I think the Bobcat has the same basic specs. The only added delay should
be
> the time it takes to send the command (rather short) over ADNET (9600 bps)
> as the strings are stored in the Bobcat.

The end of the thread indicated that the Bobcat suffered from the lost
comamnd problem but the serial port built into the Ocelot was buffered and
would not drop commands.

> Two cycles through C-Max code is rather nebulous. It might be a few
> milliseconds depending on the size of the program.

I may not be a programmer but I do remember lots of software that had to be
reworked for faster PC's because of the liberal use of such timing loops.
It was real problem with games and such that had worked on XTs and ATs but
failed on much faster Pentium machines.  I don't know enough about CMAX to
know whether there's a better way to induce a delay, though, so it may be
all they have.

--
Bobby G.


> "Robert Green" <ROBERT_GREEN1963@xxxxxxxxx> wrote:
>
> >"Dave Houston" <nobody@xxxxxxxxxxxx> wrote in message
> >news:43d96d96.395835687@xxxxxxxxxxxxxxxx
> >> "Robert Green" <ROBERT_GREEN1963@xxxxxxxxx> wrote:
> >>
> >> [snip, snip, snip]
> >> >What concerns me the most about serial comms with the ADI devices
> >> >are comments that I have read implying there's no command buffering
and
> >that
> >> >if serial data comes in too quickly, it will be lost.
> >>
> >> I don't recall any problems. other than allowing for an X10 command to
> >> complete before sending another.
> >
> >Here's the comment I saw that worried me:
> >
> >"Sending large messages may be a problem if the CAV6.6 is timing
sensitive
> >in receiving commands since you'll need to concatenate multiple shorter
> >ASCII Bobcat messages together. Adding to the challenge is that the
command
> >queue for the ASCII Bobcat doesn't appear to be buffered. If you send a
> >second message to the Bobcat before the first has been sent, the second
> >message will replace the first.
> >
> >I've found that I need to wait two cycles through my C-Max code between
> >sending ASCII Bobcat messages in order for each message to be reliably
sent.
> >You'll probably need to experiment to determine how many cycles are
needed
> >for your situation. Hooking the ASCII Bobcat up to a serial terminal can
be
> >an invaluable tool for determining the needed cycle count.
> >
> >Hope this helps,
> >-Bill "
> >
>
>http://www.appdigsupport.com/cgi-bin/ultimatebb.cgi?ubb=get_topic;f=7;t=000
3
> >61
>