Parallax StampWorks connection to Amulet EasyGUI?

Archiver

I'm doing initial testing with the Amulet EasyGUI 5.7 Starter Kit
(http://www.amulettechnologies.com/easyGUI_570info.html) and the
Parallax Basic Stamp BS2 Stamp Works
(http://www.parallax.com/detail.asp?product_id=27297).

I'm using the Amulet numeric field widget, which sends a five
character string $11, "0400" once per second. The Basic Stamp does
not see the repeating character string from the Amulet via the "RS-232
Interfacing" DB9 connector, thru pin 14 of the Basic Stamp. The
character string is seen OK via the "Download" DB9 connector. The
only difference between the programs is Rx = 14 or 16. The Basic
Stamp is set up to display incoming characters on the little LCD which
comes with the StampWorks.

I've done a lot of tests. I'm using standard RS-232 cables. Here is
a list of what works and what doesn't.

OK HyperTerm COM1 seen by Basic Stamp Download port
OK HyperTerm COM2 seen by Basic Stamp Download port
OK HyperTerm COM1 seen by Basic Stamp "RS-232 Interface" via pin 14
OK HyperTerm COM2 seen by Basic Stamp "RS-232 Interface" via pin 14
OK Amulet to PC COM1 port seen by HyperTerm
OK Amulet to PC COM2 port seen by HyperTerm
OK Amulet to Stampworks Download port seen by Basic Stamp
FAILED Amulet to Stampworks "RS-232 Interfacing" port

Is there something special about the StampWorks "RS-232 Interface"?
I'm wondering if maybe the Amulet isn't sending enough voltage... or what?

Has anybody successfully connected the Amulet EasyGUI 5.7 to a
Parallax StampWorks kit via a the "RS-232 Interface" with a standard
serial cable?

Thanks.
Bradley S Schmidt

Archiver

I'm doing initial testing with the Amulet EasyGUI 5.7 Starter Kit
(http://www.amulettechnologies.com/easyGUI_570info.html) and the
Parallax Basic Stamp BS2 Stamp Works
(http://www.parallax.com/detail.asp?product_id=27297).

I'm using the Amulet numeric field widget, which sends a five
character string $11, "0400" once per second. The Basic Stamp does
not see the repeating character string from the Amulet via the "RS-232
Interfacing" DB9 connector, thru pin 14 of the Basic Stamp. The
character string is seen OK via the "Download" DB9 connector. The
only difference between the programs is Rx = 14 or 16. The Basic
Stamp is set up to display incoming characters on the little LCD which
comes with the StampWorks.

I've done a lot of tests. I'm using standard RS-232 cables. Here is
a list of what works and what doesn't.

OK HyperTerm COM1 seen by Basic Stamp Download port
OK HyperTerm COM2 seen by Basic Stamp Download port
OK HyperTerm COM1 seen by Basic Stamp "RS-232 Interface" via pin 14
OK HyperTerm COM2 seen by Basic Stamp "RS-232 Interface" via pin 14
OK Amulet to PC COM1 port seen by HyperTerm
OK Amulet to PC COM2 port seen by HyperTerm
OK Amulet to Stampworks Download port seen by Basic Stamp
FAILED Amulet to Stampworks "RS-232 Interfacing" port

Is there something special about the StampWorks "RS-232 Interface"?
I'm wondering if maybe the Amulet isn't sending enough voltage... or what?

Has anybody successfully connected the Amulet EasyGUI 5.7 to a
Parallax StampWorks kit via a the "RS-232 Interface" with a standard
serial cable?

Thanks.
Bradley S Schmidt

Archiver

Are you sending the response to the $11? If not. Amulet will STOP
asking for the byte value.

The sequence should be:

Amulet asks the server (BasicStamp) for variable 01 : $11 $30 $31
The server (BasicStamp) must send back an ACK or the
value of variable "01"

BasicStamp sends: $21 $30 $31 $30 $38
Which means the value of variable "01" is "08"

If you don't know the value of variable 01 yet or cannot respond,
send an ACK which is the single hex value: $10. If you fail to do
this then the Amulet will stop sending $11 and hence will never get
the value.

Gary

--- In basicstamps@yahoogroups.com, "ebcdicebcdic <bradleys@s...>"
<bradleys@s...> wrote:
> I'm doing initial testing with the Amulet EasyGUI 5.7 Starter Kit
> (http://www.amulettechnologies.com/easyGUI_570info.html) and the
> Parallax Basic Stamp BS2 Stamp Works
> (http://www.parallax.com/detail.asp?product_id=27297).
>
> I'm using the Amulet numeric field widget, which sends a five
> character string $11, "0400" once per second. The Basic Stamp does
> not see the repeating character string from the Amulet via the "RS-
232
> Interfacing" DB9 connector, thru pin 14 of the Basic Stamp. The
> character string is seen OK via the "Download" DB9 connector. The
> only difference between the programs is Rx = 14 or 16. The Basic
> Stamp is set up to display incoming characters on the little LCD
which
> comes with the StampWorks.
>
> I've done a lot of tests. I'm using standard RS-232 cables. Here is
> a list of what works and what doesn't.
>
> OK HyperTerm COM1 seen by Basic Stamp Download port
> OK HyperTerm COM2 seen by Basic Stamp Download port
> OK HyperTerm COM1 seen by Basic Stamp "RS-232 Interface" via pin 14
> OK HyperTerm COM2 seen by Basic Stamp "RS-232 Interface" via pin 14
> OK Amulet to PC COM1 port seen by HyperTerm
> OK Amulet to PC COM2 port seen by HyperTerm
> OK Amulet to Stampworks Download port seen by Basic Stamp
> FAILED Amulet to Stampworks "RS-232 Interfacing" port
>
> Is there something special about the StampWorks "RS-232 Interface"?
> I'm wondering if maybe the Amulet isn't sending enough voltage...
or what?
>
> Has anybody successfully connected the Amulet EasyGUI 5.7 to a
> Parallax StampWorks kit via a the "RS-232 Interface" with a
standard
> serial cable?
>
> Thanks.
> Bradley S Schmidt

Archiver

Thanks for the suggestion. I tried putting in a SEROUT for $10, and
it doesn't make any difference. I still get the repeating $11,"0400"
across the "Download" DB9 connector, and nothing across the "RS-232
Interface" DB9 connector. I also looked at the Amulet Serial Protocol
Reference, and it indicates that the Amulet will time out after 200
msec and stop. The Numeric Field widget apparently considers each
"update" as a separate event which resets the timeout. That's why I
see repeating $11,"0400" from the Amulet, even just with HyperTerm in
Windows.

--- In basicstamps@yahoogroups.com, "gtdesrosi <gtdesrosi@c...>"
<gtdesrosi@c...> wrote:
> Are you sending the response to the $11? If not. Amulet will STOP
> asking for the byte value.
>
> The sequence should be:
>
> Amulet asks the server (BasicStamp) for variable 01 : $11 $30 $31
> The server (BasicStamp) must send back an ACK or the
> value of variable "01"
>
> BasicStamp sends: $21 $30 $31 $30 $38
> Which means the value of variable "01" is "08"
>
> If you don't know the value of variable 01 yet or cannot respond,
> send an ACK which is the single hex value: $10. If you fail to do
> this then the Amulet will stop sending $11 and hence will never get
> the value.
>
> Gary
>
> --- In basicstamps@yahoogroups.com, "ebcdicebcdic <bradleys@s...>"
> <bradleys@s...> wrote:
> > I'm doing initial testing with the Amulet EasyGUI 5.7 Starter Kit
> > (http://www.amulettechnologies.com/easyGUI_570info.html) and the
> > Parallax Basic Stamp BS2 Stamp Works
> > (http://www.parallax.com/detail.asp?product_id=27297).
> >
> > I'm using the Amulet numeric field widget, which sends a five
> > character string $11, "0400" once per second. The Basic Stamp does
> > not see the repeating character string from the Amulet via the "RS-
> 232
> > Interfacing" DB9 connector, thru pin 14 of the Basic Stamp. The
> > character string is seen OK via the "Download" DB9 connector. The
> > only difference between the programs is Rx = 14 or 16. The Basic
> > Stamp is set up to display incoming characters on the little LCD
> which
> > comes with the StampWorks.
> >
> > I've done a lot of tests. I'm using standard RS-232 cables. Here is
> > a list of what works and what doesn't.
> >
> > OK HyperTerm COM1 seen by Basic Stamp Download port
> > OK HyperTerm COM2 seen by Basic Stamp Download port
> > OK HyperTerm COM1 seen by Basic Stamp "RS-232 Interface" via pin 14
> > OK HyperTerm COM2 seen by Basic Stamp "RS-232 Interface" via pin 14
> > OK Amulet to PC COM1 port seen by HyperTerm
> > OK Amulet to PC COM2 port seen by HyperTerm
> > OK Amulet to Stampworks Download port seen by Basic Stamp
> > FAILED Amulet to Stampworks "RS-232 Interfacing" port
> >
> > Is there something special about the StampWorks "RS-232 Interface"?
> > I'm wondering if maybe the Amulet isn't sending enough voltage...
> or what?
> >
> > Has anybody successfully connected the Amulet EasyGUI 5.7 to a
> > Parallax StampWorks kit via a the "RS-232 Interface" with a
> standard
> > serial cable?
> >
> > Thanks.
> > Bradley S Schmidt

Archiver

A couple of further thoughts...

The server has only 200ms to respond to the Amulet otherwise it will
stop sending messages (asking for the values).

If you don't want to respond to an Amulet message, you still have to
respond with and ACK ($10) otherwise the Amulet will discontinue
sending messages. So, for example, the Amulet may send $15 to
request the word value or $12 to request the string value. Just send
back a $10 to acknowledge and ignore the message. You're probably
doing an Amulet:UART.byteValue() call, though.

Physical hardware issues might be txd/rxd switched (easy to do),
Baud rate not correct. Make sure there's a;

<META NAME="Amulet" Content="baud=19200">

tag in your html telling the Amulet at what baud rate to transfer.

Also, since your using StampWorks, I'm assuming your going through
the RS232 interfacing portion of the board. I'm using a MAX232A
level converter here an it works fine. The StampWorks board uses
something different to convert to RS232 voltage levels so who knows.
The problem could be as simple as using inverted vs non-inverted
signals. Also, make sure that the grounds are connected together
(Amulet & StampWorks).

Since you mentioned that the messages are being sent every second,
I'm assuming you have a;

<PARAM NAME="updaterate" VALUE="1.00">

as one of the applet params. However, the stamp still must respond
within the 200ms timeframe.

Hope some of this helps.
Gary

--- In basicstamps@yahoogroups.com, "ebcdicebcdic <bradleys@s...>"
<bradleys@s...> wrote:
> I'm doing initial testing with the Amulet EasyGUI 5.7 Starter Kit
> (http://www.amulettechnologies.com/easyGUI_570info.html) and the
> Parallax Basic Stamp BS2 Stamp Works
> (http://www.parallax.com/detail.asp?product_id=27297).
>
> I'm using the Amulet numeric field widget, which sends a five
> character string $11, "0400" once per second. The Basic Stamp does
> not see the repeating character string from the Amulet via the "RS-
232
> Interfacing" DB9 connector, thru pin 14 of the Basic Stamp. The
> character string is seen OK via the "Download" DB9 connector. The
> only difference between the programs is Rx = 14 or 16. The Basic
> Stamp is set up to display incoming characters on the little LCD
which
> comes with the StampWorks.
>
> I've done a lot of tests. I'm using standard RS-232 cables. Here is
> a list of what works and what doesn't.
>
> OK HyperTerm COM1 seen by Basic Stamp Download port
> OK HyperTerm COM2 seen by Basic Stamp Download port
> OK HyperTerm COM1 seen by Basic Stamp "RS-232 Interface" via pin 14
> OK HyperTerm COM2 seen by Basic Stamp "RS-232 Interface" via pin 14
> OK Amulet to PC COM1 port seen by HyperTerm
> OK Amulet to PC COM2 port seen by HyperTerm
> OK Amulet to Stampworks Download port seen by Basic Stamp
> FAILED Amulet to Stampworks "RS-232 Interfacing" port
>
> Is there something special about the StampWorks "RS-232 Interface"?
> I'm wondering if maybe the Amulet isn't sending enough voltage...
or what?
>
> Has anybody successfully connected the Amulet EasyGUI 5.7 to a
> Parallax StampWorks kit via a the "RS-232 Interface" with a
standard
> serial cable?
>
> Thanks.
> Bradley S Schmidt

Archiver

I've got my bar graph and numeric field now following values I'm
sending via a "slider" on the Amulet. It works fine on the "Download"
port and still not via the "RS-232 Interface". I'm going to assume
that there's some basic incompatibility with the "RS-232 Interface"
and use the "Download" port and not worry about it. I'll probably
pick up a MAX232A or something so I don't have to keep swapping
cables. In the meantime, I'll use what works. Thanks Gary.

--- In basicstamps@yahoogroups.com, "gtdesrosi <gtdesrosi@c...>"
<gtdesrosi@c...> wrote:
> A couple of further thoughts...
>
> The server has only 200ms to respond to the Amulet otherwise it will
> stop sending messages (asking for the values).
>
> If you don't want to respond to an Amulet message, you still have to
> respond with and ACK ($10) otherwise the Amulet will discontinue
> sending messages. So, for example, the Amulet may send $15 to
> request the word value or $12 to request the string value. Just send
> back a $10 to acknowledge and ignore the message. You're probably
> doing an Amulet:UART.byteValue() call, though.
>
> Physical hardware issues might be txd/rxd switched (easy to do),
> Baud rate not correct. Make sure there's a;
>
> <META NAME="Amulet" Content="baud=19200">
>
> tag in your html telling the Amulet at what baud rate to transfer.
>
> Also, since your using StampWorks, I'm assuming your going through
> the RS232 interfacing portion of the board. I'm using a MAX232A
> level converter here an it works fine. The StampWorks board uses
> something different to convert to RS232 voltage levels so who knows.
> The problem could be as simple as using inverted vs non-inverted
> signals. Also, make sure that the grounds are connected together
> (Amulet & StampWorks).
>
> Since you mentioned that the messages are being sent every second,
> I'm assuming you have a;
>
> <PARAM NAME="updaterate" VALUE="1.00">
>
> as one of the applet params. However, the stamp still must respond
> within the 200ms timeframe.
>
> Hope some of this helps.
> Gary
>
> --- In basicstamps@yahoogroups.com, "ebcdicebcdic <bradleys@s...>"
> <bradleys@s...> wrote:
> > I'm doing initial testing with the Amulet EasyGUI 5.7 Starter Kit
> > (http://www.amulettechnologies.com/easyGUI_570info.html) and the
> > Parallax Basic Stamp BS2 Stamp Works
> > (http://www.parallax.com/detail.asp?product_id=27297).
> >
> > I'm using the Amulet numeric field widget, which sends a five
> > character string $11, "0400" once per second. The Basic Stamp does
> > not see the repeating character string from the Amulet via the "RS-
> 232
> > Interfacing" DB9 connector, thru pin 14 of the Basic Stamp. The
> > character string is seen OK via the "Download" DB9 connector. The
> > only difference between the programs is Rx = 14 or 16. The Basic
> > Stamp is set up to display incoming characters on the little LCD
> which
> > comes with the StampWorks.
> >
> > I've done a lot of tests. I'm using standard RS-232 cables. Here is
> > a list of what works and what doesn't.
> >
> > OK HyperTerm COM1 seen by Basic Stamp Download port
> > OK HyperTerm COM2 seen by Basic Stamp Download port
> > OK HyperTerm COM1 seen by Basic Stamp "RS-232 Interface" via pin 14
> > OK HyperTerm COM2 seen by Basic Stamp "RS-232 Interface" via pin 14
> > OK Amulet to PC COM1 port seen by HyperTerm
> > OK Amulet to PC COM2 port seen by HyperTerm
> > OK Amulet to Stampworks Download port seen by Basic Stamp
> > FAILED Amulet to Stampworks "RS-232 Interfacing" port
> >
> > Is there something special about the StampWorks "RS-232 Interface"?
> > I'm wondering if maybe the Amulet isn't sending enough voltage...
> or what?
> >
> > Has anybody successfully connected the Amulet EasyGUI 5.7 to a
> > Parallax StampWorks kit via a the "RS-232 Interface" with a
> standard
> > serial cable?
> >
> > Thanks.
> > Bradley S Schmidt

Archiver

Bradley,

I have a few comments.

First, I would definitely start out with the slowest baud possible.
Since the Amulet supports 9600, 19200, 57600 and 115200 bps, I would
first start out at 9600 bps and set up your stamp for 9600 bps as
well.

Second, I'm not sure if you already have the following meta tag in
your html, but definitely put it in if you don't because it adds an
extra 4ms delay between Amulet bytes to the Stamp :

<META NAME="Amulet" Content="BASICStamp">

Third,

A time-out will occur when commands are not responded to and that
specific message will not be repeated. For example, lets assume your
numeric field is set up for an update rate of 1 second. The Amulet
sends a request and waits for 200 msec for a valid response. If no
response comes through, the Amulet times out and clears its buffers
and begins transmitting any new messages (which can be generated by
the numeric field since it has an update rate of 1 second).

Hope this helps.

Ed

--- In basicstamps@yahoogroups.com, "ebcdicebcdic <bradleys@s...>"
<bradleys@s...> wrote:
> I've got my bar graph and numeric field now following values I'm
> sending via a "slider" on the Amulet. It works fine on
the "Download"
> port and still not via the "RS-232 Interface". I'm going to assume
> that there's some basic incompatibility with the "RS-232 Interface"
> and use the "Download" port and not worry about it. I'll probably
> pick up a MAX232A or something so I don't have to keep swapping
> cables. In the meantime, I'll use what works. Thanks Gary.
>
> --- In basicstamps@yahoogroups.com, "gtdesrosi <gtdesrosi@c...>"
> <gtdesrosi@c...> wrote:
> > A couple of further thoughts...
> >
> > The server has only 200ms to respond to the Amulet otherwise it
will
> > stop sending messages (asking for the values).
> >
> > If you don't want to respond to an Amulet message, you still have
to
> > respond with and ACK ($10) otherwise the Amulet will discontinue
> > sending messages. So, for example, the Amulet may send $15 to
> > request the word value or $12 to request the string value. Just
send
> > back a $10 to acknowledge and ignore the message. You're probably
> > doing an Amulet:UART.byteValue() call, though.
> >
> > Physical hardware issues might be txd/rxd switched (easy to do),
> > Baud rate not correct. Make sure there's a;
> >
> > <META NAME="Amulet" Content="baud=19200">
> >
> > tag in your html telling the Amulet at what baud rate to transfer.
> >
> > Also, since your using StampWorks, I'm assuming your going
through
> > the RS232 interfacing portion of the board. I'm using a MAX232A
> > level converter here an it works fine. The StampWorks board uses
> > something different to convert to RS232 voltage levels so who
knows.
> > The problem could be as simple as using inverted vs non-inverted
> > signals. Also, make sure that the grounds are connected together
> > (Amulet & StampWorks).
> >
> > Since you mentioned that the messages are being sent every
second,
> > I'm assuming you have a;
> >
> > <PARAM NAME="updaterate" VALUE="1.00">
> >
> > as one of the applet params. However, the stamp still must
respond
> > within the 200ms timeframe.
> >
> > Hope some of this helps.
> > Gary
> >
> > --- In basicstamps@yahoogroups.com, "ebcdicebcdic
<bradleys@s...>"
> > <bradleys@s...> wrote:
> > > I'm doing initial testing with the Amulet EasyGUI 5.7 Starter
Kit
> > > (http://www.amulettechnologies.com/easyGUI_570info.html) and the
> > > Parallax Basic Stamp BS2 Stamp Works
> > > (http://www.parallax.com/detail.asp?product_id=27297).
> > >
> > > I'm using the Amulet numeric field widget, which sends a five
> > > character string $11, "0400" once per second. The Basic Stamp
does
> > > not see the repeating character string from the Amulet via
the "RS-
> > 232
> > > Interfacing" DB9 connector, thru pin 14 of the Basic Stamp. The
> > > character string is seen OK via the "Download" DB9 connector.
The
> > > only difference between the programs is Rx = 14 or 16. The Basic
> > > Stamp is set up to display incoming characters on the little
LCD
> > which
> > > comes with the StampWorks.
> > >
> > > I've done a lot of tests. I'm using standard RS-232 cables.
Here is
> > > a list of what works and what doesn't.
> > >
> > > OK HyperTerm COM1 seen by Basic Stamp Download port
> > > OK HyperTerm COM2 seen by Basic Stamp Download port
> > > OK HyperTerm COM1 seen by Basic Stamp "RS-232 Interface" via
pin 14
> > > OK HyperTerm COM2 seen by Basic Stamp "RS-232 Interface" via
pin 14
> > > OK Amulet to PC COM1 port seen by HyperTerm
> > > OK Amulet to PC COM2 port seen by HyperTerm
> > > OK Amulet to Stampworks Download port seen by Basic Stamp
> > > FAILED Amulet to Stampworks "RS-232 Interfacing" port
> > >
> > > Is there something special about the StampWorks "RS-232
Interface"?
> > > I'm wondering if maybe the Amulet isn't sending enough
voltage...
> > or what?
> > >
> > > Has anybody successfully connected the Amulet EasyGUI 5.7 to a
> > > Parallax StampWorks kit via a the "RS-232 Interface" with a
> > standard
> > > serial cable?
> > >
> > > Thanks.
> > > Bradley S Schmidt