Stop Bit Problem?
Archiver
Posts: 46,084
Okay heres the beef.
I have my stamp connected to a PC (or HP Protocol analyzer).
When I send messages via the debug command they come out just fine.
However when I try to send with serout as in
serout 16,84,[noparse][[/noparse]"hello"]
I get garbage. Now if I loop the statement, the garbage I get is
consistent, so I know that it is sending the correct message, but it
is messing it up exactly the same way. I know that the debug command
sends using this method. So why the problem?
Anybody have a clue?
By the way, my protocol analyser says that like every
2 or 3 bytes (consistent depending on message size) is
received at "the wrong speed". I'm thinking that maybe the stop bit
is not properly sent and it is fouling things up.
I have my stamp connected to a PC (or HP Protocol analyzer).
When I send messages via the debug command they come out just fine.
However when I try to send with serout as in
serout 16,84,[noparse][[/noparse]"hello"]
I get garbage. Now if I loop the statement, the garbage I get is
consistent, so I know that it is sending the correct message, but it
is messing it up exactly the same way. I know that the debug command
sends using this method. So why the problem?
Anybody have a clue?
By the way, my protocol analyser says that like every
2 or 3 bytes (consistent depending on message size) is
received at "the wrong speed". I'm thinking that maybe the stop bit
is not properly sent and it is fouling things up.
Comments
BS2.
The stop bit should really not be a problem.
-- Tracy
---original message--->
Okay heres the beef.
I have my stamp connected to a PC (or HP Protocol analyzer).
When I send messages via the debug command they come out just fine.
However when I try to send with serout as in
serout 16,84,[noparse][[/noparse]"hello"]
I get garbage. Now if I loop the statement, the garbage I get is
consistent, so I know that it is sending the correct message, but it
is messing it up exactly the same way. I know that the debug command
sends using this method. So why the problem?
Anybody have a clue?
By the way, my protocol analyser says that like every
2 or 3 bytes (consistent depending on message size) is
received at "the wrong speed". I'm thinking that maybe the stop bit
is not properly sent and it is fouling things up.
serout 16,16468,[noparse][[/noparse]hello]
tkonetsk@h... wrote:
>
> Okay heres the beef.
>
> I have my stamp connected to a PC (or HP Protocol analyzer).
> When I send messages via the debug command they come out just fine.
> However when I try to send with serout as in
>
> serout 16,84,[noparse][[/noparse]"hello"]
>
> I get garbage. Now if I loop the statement, the garbage I get is
> consistent, so I know that it is sending the correct message, but it
> is messing it up exactly the same way. I know that the debug command
> sends using this method. So why the problem?
>
> Anybody have a clue?
>
> By the way, my protocol analyser says that like every
> 2 or 3 bytes (consistent depending on message size) is
> received at "the wrong speed". I'm thinking that maybe the stop bit
> is not properly sent and it is fouling things up.
Stop bits are a problem. Try lengthening your stop bit if possible. A length
of 2 is sometimes required, depending on the program. I have lots of
problems with labview on different platforms (pc and mac) and each takes a
different stop bit length to be happy. I hope this helps.
Gary
g.shearer@v...
Free Electron Laser Research Center
Vanderbilt University
Nashville, Tennessee
Original Message
From: <tkonetsk@h...>
To: <basicstamps@egroups.com>
Sent: Thursday, August 31, 2000 10:36 AM
Subject: [noparse][[/noparse]basicstamps] Stop Bit Problem?
> Okay heres the beef.
>
> I have my stamp connected to a PC (or HP Protocol analyzer).
> When I send messages via the debug command they come out just fine.
> However when I try to send with serout as in
>
> serout 16,84,[noparse][[/noparse]"hello"]
>
> I get garbage. Now if I loop the statement, the garbage I get is
> consistent, so I know that it is sending the correct message, but it
> is messing it up exactly the same way. I know that the debug command
> sends using this method. So why the problem?
>
> Anybody have a clue?
>
> By the way, my protocol analyser says that like every
> 2 or 3 bytes (consistent depending on message size) is
> received at "the wrong speed". I'm thinking that maybe the stop bit
> is not properly sent and it is fouling things up.
>
>
>
>