BS2p 1-Wire Gadgets
Archiver
Posts: 46,084
The BS2p offers us the ability to access an almost unlimited number
of Dallas 1-Wire devices through a single Stamp I/O pin. That's a
Good Thing--there are lots of nifty 1-Wire devices offered by Dallas
Semiconductor.
But the BS2p's 1-Wire capabilities needn't necessarily be confined
to the Dallas array of products. A few days ago a commonly-seen
question was posed regarding controlling multiple outputs without
using up a bunch of Stamp pins. Conventional solutions (shift
registers, custom chips etc.) were suggested. That question started
me thinking about Stamp-friendly emulations of standard logic ICs,
strung out along a 1-Wire bus, accessed via OWIN/OWOUT statements,
and consuming (between them) only one I/O pin.
As an example, consider the 8-bit latch function above. On my bench
I have an 18-pin DIP Scenix SX18 microprocessor connected to I/O 7 of
a BS2p. The SX18 "thinks" it's a 1-Wire device--it's programmed to
communicate using the 1-Wire protocol, has its own 64-bit serial ID,
and responds correctly to the standard ROM function commands (SKIP
ROM, READ ROM, MATCH ROM, SEARCH ROM). In other words, it can work
with OWIN and OWOUT statements, and can share a 1-Wire bus (i.e.
single Stamp I/O pin) with many other 1-Wire devices. This one is
further programmed as an 8-bit output latch (it could just as easily
have been an input latch, pulse detector, or ...). With simple OWOUT
statements on the BS2p, I can set the output states of 8 pins on the
SX18:
OWOUT BUS, RESET_PRE, [noparse][[/noparse]SKIP_ROM, LATCH_OUT, byte_out]
This is a very simple case of what seems to me a powerful and useful
capability for the BS2p. A microprocessor such as the Scenix SX
series can emulate the functionality of many/most digital ICs or
discrete component circuits used with a Stamp, with greater control
and flexibility in most cases. Add to that a single Stamp pin
interface shared with you-name-it other gadgets, and the
possibilities can make one salivate. If there's interest, I'll look
at building and offering further 1-Wire compatible gadgets.
Steve
of Dallas 1-Wire devices through a single Stamp I/O pin. That's a
Good Thing--there are lots of nifty 1-Wire devices offered by Dallas
Semiconductor.
But the BS2p's 1-Wire capabilities needn't necessarily be confined
to the Dallas array of products. A few days ago a commonly-seen
question was posed regarding controlling multiple outputs without
using up a bunch of Stamp pins. Conventional solutions (shift
registers, custom chips etc.) were suggested. That question started
me thinking about Stamp-friendly emulations of standard logic ICs,
strung out along a 1-Wire bus, accessed via OWIN/OWOUT statements,
and consuming (between them) only one I/O pin.
As an example, consider the 8-bit latch function above. On my bench
I have an 18-pin DIP Scenix SX18 microprocessor connected to I/O 7 of
a BS2p. The SX18 "thinks" it's a 1-Wire device--it's programmed to
communicate using the 1-Wire protocol, has its own 64-bit serial ID,
and responds correctly to the standard ROM function commands (SKIP
ROM, READ ROM, MATCH ROM, SEARCH ROM). In other words, it can work
with OWIN and OWOUT statements, and can share a 1-Wire bus (i.e.
single Stamp I/O pin) with many other 1-Wire devices. This one is
further programmed as an 8-bit output latch (it could just as easily
have been an input latch, pulse detector, or ...). With simple OWOUT
statements on the BS2p, I can set the output states of 8 pins on the
SX18:
OWOUT BUS, RESET_PRE, [noparse][[/noparse]SKIP_ROM, LATCH_OUT, byte_out]
This is a very simple case of what seems to me a powerful and useful
capability for the BS2p. A microprocessor such as the Scenix SX
series can emulate the functionality of many/most digital ICs or
discrete component circuits used with a Stamp, with greater control
and flexibility in most cases. Add to that a single Stamp pin
interface shared with you-name-it other gadgets, and the
possibilities can make one salivate. If there's interest, I'll look
at building and offering further 1-Wire compatible gadgets.
Steve
Comments
>
>This is a very simple case of what seems to me a powerful and useful
>capability for the BS2p. A microprocessor such as the Scenix SX
>series can emulate the functionality of many/most digital ICs or
>discrete component circuits used with a Stamp, with greater control
>and flexibility in most cases. Add to that a single Stamp pin
>interface shared with you-name-it other gadgets, and the
>possibilities can make one salivate. If there's interest, I'll look
>at building and offering further 1-Wire compatible gadgets.
Brilliant idea, Steve!
Reg
A 100% reliable, half-duplex serial Stamp-Stamp communication across
a simple data path (wire, resistor, rf, ir...) is problematic,
code-intensive and consumes a lot of I/O pins, assuming flow control
in both directions on both Stamps. I don't see right off how the
native 1-Wire I/O capability improves things--the receiving Stamp
would still have to be OWINning when the sending Stamp OWOUTs or data
would get dropped.
An intervening smart buffer could solve that problem and provide
virtually full-duplex communication. That's certainly one possible
"designer one-wire solution", to steal er....borrow Tracy's term. Or
the smart buffer could be accessed via SERIN & SEROUT, SHIFTIN &
SHIFTOUT or other pre-BS2p I/O statements.
The beauty of using the BS2p's 1-Wire functions is that the same
Stamp I/O pin could be used in the next instruction to access a GPS
data string stored in a second smart buffer, or a clock, a PS/2
keyboard, mouse, a memory controller, thermometer, 1 of 16
multiplexer, UART, the list goes on and on...
Regarding Dallas Semi's ownership of the protocol--I'd be very
interested to know if Parallax incurred a licensing fee or agreement
or whatever to use the protocol with the BS2p (agreed, using it is
not the same as impinging on family code and unique ID stuff).
Steve
Your posting got me thinking. Is the BS2p finally the answer to having two
Stamps reliably talk to each other? Years of discussion has taken place
about the use of one and two line communication between stamps. I have
tried most of it and at best, I have gotten slow links via serial lines
(1200 baud or less.) I'm trying to imagine how the new "pseudo-interrupt"
could be used with 1-Wire communication to finally give me a realtime link
between two processors. This is just off the top of my head, without having
gone back and looked at the 1-Wire commands and all of their options.
Any thoughts folks?
Mike
At 10:18 AM 3/14/2001 +0800, you wrote:
>The BS2p offers us the ability to access an almost unlimited number
>of Dallas 1-Wire devices through a single Stamp I/O pin. That's a
>Good Thing--there are lots of nifty 1-Wire devices offered by Dallas
>Semiconductor.
>________________________________
Mike Walsh
walsh@i...
I have two BS2 stamps talking to each other at 9600 baud via one wire , and a
BS2E talking to a BS2 at 9600 baud via RF with no problems. Does that
help??
Sid
Newzed@a...
Here's a toast to your suggestion of designer one-wire solutions!
I find some of the Dallas offerings kind of quirky, for example,
there are the clever hacks they have come up with for reading wind
vanes and humidity sensors.
I wonder, does Dalsemi have some kind of patent or lock on the
implementation of this protocol? There is the issue of unique device
ids and serial numbers, that sooner or later would have to be
"registered". The devices from outfits like Pointsix
<http://www.pointsix.com/> seem to be exlusively based on Dallas
chips.
The one-wire stuff is really appealing from the standpoint of
multidrop instrumentation--stringing multiple devices out on a pair
of wires (or triplet for more power), with the capability to add on
additional devices any time, simply by tapping into the existing
wiring, and with the automatic identification of new devices on the
buss.
However, I find some of the claims, like a 2000 foot network on Cat-5
cable, kind of hard to swallow. One-wire is basically a single
ended, not differential (per RS422,RS485) signalling system, and it
relies on a passive resistor to pull up the signal line. The timing
is critical, with time windows on the order of 10 to 60 microseconds.
(Compare that with RS232 at 9600 baud, where each bit is about 100
microseconds and both polarities are actively driven.) Of course
that is no problem when the devices are close together, but 2000 feet
of twisted pair....? The protocol does have the CRC check, but a lot
of bits have to get through for it to work right...? I would like
to hear from anyone who has used it in an extensive network.
-- regards,
Tracy Allen
electronically monitored ecosystems
http://www.emesystems.com
>The BS2p offers us the ability to access an almost unlimited number
>of Dallas 1-Wire devices through a single Stamp I/O pin. That's a
>Good Thing--there are lots of nifty 1-Wire devices offered by Dallas
>Semiconductor.
>
>But the BS2p's 1-Wire capabilities needn't necessarily be confined
>to the Dallas array of products. A few days ago a commonly-seen
>question was posed regarding controlling multiple outputs without
>using up a bunch of Stamp pins. Conventional solutions (shift
>registers, custom chips etc.) were suggested. That question started
>me thinking about Stamp-friendly emulations of standard logic ICs,
>strung out along a 1-Wire bus, accessed via OWIN/OWOUT statements,
>and consuming (between them) only one I/O pin.
plus one more if it needs strong pullup.
>
>As an example, consider the 8-bit latch function above. On my bench
>I have an 18-pin DIP Scenix SX18 microprocessor connected to I/O 7 of
>a BS2p. The SX18 "thinks" it's a 1-Wire device--it's programmed to
>communicate using the 1-Wire protocol, has its own 64-bit serial ID,
>and responds correctly to the standard ROM function commands (SKIP
>ROM, READ ROM, MATCH ROM, SEARCH ROM). In other words, it can work
>with OWIN and OWOUT statements, and can share a 1-Wire bus (i.e.
>single Stamp I/O pin) with many other 1-Wire devices. This one is
>further programmed as an 8-bit output latch (it could just as easily
>have been an input latch, pulse detector, or ...). With simple OWOUT
>statements on the BS2p, I can set the output states of 8 pins on the
>SX18:
>
>OWOUT BUS, RESET_PRE, [noparse][[/noparse]SKIP_ROM, LATCH_OUT, byte_out]
>
>This is a very simple case of what seems to me a powerful and useful
>capability for the BS2p. A microprocessor such as the Scenix SX
>series can emulate the functionality of many/most digital ICs or
>discrete component circuits used with a Stamp, with greater control
>and flexibility in most cases. Add to that a single Stamp pin
>interface shared with you-name-it other gadgets, and the
>possibilities can make one salivate. If there's interest, I'll look
>at building and offering further 1-Wire compatible gadgets.
>
>
>Steve
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
My post should have been addressed to Mike, not Steve. Sorry.
Sid
soon, when I double up stamp processors, on my robot.
At 01:03 PM 3/15/2001 EST, you wrote:
>Steve
>
>I have two BS2 stamps talking to each other at 9600 baud via one wire , and a
>BS2E talking to a BS2 at 9600 baud via RF with no problems. Does that
>help??
>
>Sid
>Newzed@a...
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
Sincerely
Kerry
Admin@M...
WWW server hosting [url=Http://mntnweb.com]Http://mntnweb.com[/url]
Kerry Barlow
p.o. box 21
kirkwood ny
13795
Here's a toast to your suggestion of designer one-wire solutions!
I find some of the Dallas offerings kind of quirky, for example,
there are the clever hacks they have come up with for reading wind
vanes and humidity sensors.
I wonder, does Dalsemi have some kind of patent or lock on the
implementation of this protocol? There is the issue of unique device
ids and serial numbers, that sooner or later would have to be
"registered". The devices from outfits like Pointsix
<http://www.pointsix.com/> seem to be exlusively based on Dallas
chips.
The one-wire stuff is really appealing from the standpoint of
multidrop instrumentation--stringing multiple devices out on a pair
of wires (or triplet for more power), with the capability to add on
additional devices any time, simply by tapping into the existing
wiring, and with the automatic identification of new devices on the
buss.
However, I find some of the claims, like a 2000 foot network on Cat-5
cable, kind of hard to swallow. One-wire is basically a single
ended, not differential (per RS422,RS485) signalling system, and it
relies on a passive resistor to pull up the signal line. The timing
is critical, with time windows on the order of 10 to 60 microseconds.
(Compare that with RS232 at 9600 baud, where each bit is about 100
microseconds and both polarities are actively driven.) Of course
that is no problem when the devices are close together, but 2000 feet
of twisted pair....? The protocol does have the CRC check, but a lot
of bits have to get through for it to work right...? I would like
to hear from anyone who has used it in an extensive network.
-- regards,
Tracy Allen
electronically monitored ecosystems
http://www.emesystems.com
>The BS2p offers us the ability to access an almost unlimited number
>of Dallas 1-Wire devices through a single Stamp I/O pin. That's a
>Good Thing--there are lots of nifty 1-Wire devices offered by Dallas
>Semiconductor.
>
>But the BS2p's 1-Wire capabilities needn't necessarily be confined
>to the Dallas array of products. A few days ago a commonly-seen
>question was posed regarding controlling multiple outputs without
>using up a bunch of Stamp pins. Conventional solutions (shift
>registers, custom chips etc.) were suggested. That question started
>me thinking about Stamp-friendly emulations of standard logic ICs,
>strung out along a 1-Wire bus, accessed via OWIN/OWOUT statements,
>and consuming (between them) only one I/O pin.
plus one more if it needs strong pullup.
>
>As an example, consider the 8-bit latch function above. On my bench
>I have an 18-pin DIP Scenix SX18 microprocessor connected to I/O 7 of
>a BS2p. The SX18 "thinks" it's a 1-Wire device--it's programmed to
>communicate using the 1-Wire protocol, has its own 64-bit serial ID,
>and responds correctly to the standard ROM function commands (SKIP
>ROM, READ ROM, MATCH ROM, SEARCH ROM). In other words, it can work
>with OWIN and OWOUT statements, and can share a 1-Wire bus (i.e.
>single Stamp I/O pin) with many other 1-Wire devices. This one is
>further programmed as an 8-bit output latch (it could just as easily
>have been an input latch, pulse detector, or ...). With simple OWOUT
>statements on the BS2p, I can set the output states of 8 pins on the
>SX18:
>
>OWOUT BUS, RESET_PRE, [noparse][[/noparse]SKIP_ROM, LATCH_OUT, byte_out]
>
>This is a very simple case of what seems to me a powerful and useful
>capability for the BS2p. A microprocessor such as the Scenix SX
>series can emulate the functionality of many/most digital ICs or
>discrete component circuits used with a Stamp, with greater control
>and flexibility in most cases. Add to that a single Stamp pin
>interface shared with you-name-it other gadgets, and the
>possibilities can make one salivate. If there's interest, I'll look
>at building and offering further 1-Wire compatible gadgets.
>
>
>Steve
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
I'd be very interested in seeing the snips of code from both BS2E and BS2
to send and receive. Is your receiving BS2 tied up polling the serial port
for data? I've had problems with the Stamps (all versions) reliably
communicating at 9600 baud. I'd appreciate any help or suggestions.
Thanks,
Mike
At 01:03 PM 3/15/2001 -0500, you wrote:
>Steve
>
>I have two BS2 stamps talking to each other at 9600 baud via one wire , and a
>BS2E talking to a BS2 at 9600 baud via RF with no problems. Does that
>help??
>
>Sid
>Newzed@a...
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
_________________________________
Mike Walsh
walsh@i...
associated with long runs of 1 wire cabling. There is a man on the list who
made a special 1 wire hub, which allows shorter lengths of wire to be routed
to various locations, all coming back to the hub, and from there to the
microprocessor ( PC in this case) he is selling these hubs, for a small
price, I dont know if he has any left.
They have been talking quite a bit about this issue, and the work arounds,
and solutions. People that are interested may wish to sign up to the 1 wire
mailing list
http://lists.dalsemi.com/mailman/listinfo/weather, you can also search the
archives from this link.
I have a 1 wire weather station, so try to keep abreast of whats going on
there as well.
Kerry
At 10:04 AM 3/15/2001 -0800, you wrote:
>Hi Steve,
>
>Here's a toast to your suggestion of designer one-wire solutions!
>
>I find some of the Dallas offerings kind of quirky, for example,
>there are the clever hacks they have come up with for reading wind
>vanes and humidity sensors.
>
>I wonder, does Dalsemi have some kind of patent or lock on the
>implementation of this protocol? There is the issue of unique device
>ids and serial numbers, that sooner or later would have to be
>"registered". The devices from outfits like Pointsix
><http://www.pointsix.com/> seem to be exlusively based on Dallas
>chips.
>
>The one-wire stuff is really appealing from the standpoint of
>multidrop instrumentation--stringing multiple devices out on a pair
>of wires (or triplet for more power), with the capability to add on
>additional devices any time, simply by tapping into the existing
>wiring, and with the automatic identification of new devices on the
>buss.
>
>However, I find some of the claims, like a 2000 foot network on Cat-5
>cable, kind of hard to swallow. One-wire is basically a single
>ended, not differential (per RS422,RS485) signalling system, and it
>relies on a passive resistor to pull up the signal line. The timing
>is critical, with time windows on the order of 10 to 60 microseconds.
>(Compare that with RS232 at 9600 baud, where each bit is about 100
>microseconds and both polarities are actively driven.) Of course
>that is no problem when the devices are close together, but 2000 feet
>of twisted pair....? The protocol does have the CRC check, but a lot
>of bits have to get through for it to work right...? I would like
>to hear from anyone who has used it in an extensive network.
>
> -- regards,
> Tracy Allen
> electronically monitored ecosystems
> http://www.emesystems.com
>
>
>
>
>>The BS2p offers us the ability to access an almost unlimited number
>>of Dallas 1-Wire devices through a single Stamp I/O pin. That's a
>>Good Thing--there are lots of nifty 1-Wire devices offered by Dallas
>>Semiconductor.
>>
>>But the BS2p's 1-Wire capabilities needn't necessarily be confined
>>to the Dallas array of products. A few days ago a commonly-seen
>>question was posed regarding controlling multiple outputs without
>>using up a bunch of Stamp pins. Conventional solutions (shift
>>registers, custom chips etc.) were suggested. That question started
>>me thinking about Stamp-friendly emulations of standard logic ICs,
>>strung out along a 1-Wire bus, accessed via OWIN/OWOUT statements,
>>and consuming (between them) only one I/O pin.
>
>plus one more if it needs strong pullup.
>
>
>>
>>As an example, consider the 8-bit latch function above. On my bench
>>I have an 18-pin DIP Scenix SX18 microprocessor connected to I/O 7 of
>>a BS2p. The SX18 "thinks" it's a 1-Wire device--it's programmed to
>>communicate using the 1-Wire protocol, has its own 64-bit serial ID,
>>and responds correctly to the standard ROM function commands (SKIP
>>ROM, READ ROM, MATCH ROM, SEARCH ROM). In other words, it can work
>>with OWIN and OWOUT statements, and can share a 1-Wire bus (i.e.
>>single Stamp I/O pin) with many other 1-Wire devices. This one is
>>further programmed as an 8-bit output latch (it could just as easily
>>have been an input latch, pulse detector, or ...). With simple OWOUT
>>statements on the BS2p, I can set the output states of 8 pins on the
>>SX18:
>>
>>OWOUT BUS, RESET_PRE, [noparse][[/noparse]SKIP_ROM, LATCH_OUT, byte_out]
>>
>>This is a very simple case of what seems to me a powerful and useful
>>capability for the BS2p. A microprocessor such as the Scenix SX
>>series can emulate the functionality of many/most digital ICs or
>>discrete component circuits used with a Stamp, with greater control
>>and flexibility in most cases. Add to that a single Stamp pin
>>interface shared with you-name-it other gadgets, and the
>>possibilities can make one salivate. If there's interest, I'll look
>>at building and offering further 1-Wire compatible gadgets.
>>
>>
>>Steve
>>
>>
>>
>>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
Sincerely
Kerry
Admin@M...
WWW server hosting [url=Http://mntnweb.com]Http://mntnweb.com[/url]
Kerry Barlow
p.o. box 21
kirkwood ny
13795
Good afternoon
I have two BS2s on my robot, one on the bottom deck and one on the top deck.
The bottom Stamp controls the servos and the top stamp controls the video
camera and transmitter and RF receiver output. Pin 15 of the bottom stamp
is conmnected to pin 5 of the top stamp. The robot can operate in a
controlled mode, where it executes a series of planned maneuvers, or in the
remote mode where the BS2E transmitter module transmits one or two bytes of
data which the robot decodes as a maneuver. In the controlled mode, the top
stamp, the video circuit and the bottom stamp are turned on in that order by
neans of miniature switches in the power supply. As soon as the bottom stamp
stabilizes it says:
N9600 con 16468
com var word
begin
serout 15, N9600, 50, [noparse][[/noparse]"S"]
serin 15, N9600, [noparse][[/noparse]com]
'At this point the bottom stamp sits and waits for a serin.
After the serin I say:
if com = "G" then move
'move is a routine thats reads data and executes the proper maneuvers
'when the bottom stamp has executed all the planned maneuvers ----
serout 15, N9600, 50, [noparse][[/noparse]"Q"]
On the top stamp:
N9600 con 16468
com var word
begin
serin 5, N9600, [noparse][[/noparse]com]
if com = "S" then start
start
high 3 'turns on video camera
high7 'turns on video transmitter
low 8 'turns on "Ready " light
serout 5, N9600, 50, [noparse][[/noparse]"G"] 'tells bottom stamp it has video on and is
ready
serin 5, N9600, [noparse][[/noparse]com] 'waits for bottom stamp to tell it is done
if com = "Q" then quit
quit
high 8
low 3
low 7
goto begin
Two things to remember - the bottom stamp MUST be turned on last so the top
stamp has time to stabilize before the bottom stamps sends the first serout.
Second, 16468 cannot be used for the baud rate, as in
serout 15, 16468, [noparse][[/noparse]"S"]
You must tell both stamps either N9600 or ON9600, preferably N9600.
Programming in the "remote" mode is a bit more complicated but I will be glad
to send the code if you like. Hope you can understand what I have written.
It's a little difficult to try to explain two interacting programs at the
same time.
Regards
Sid
> implementation of this protocol? There is the issue of unique device
> ids and serial numbers, that sooner or later would have to be
> "registered". The devices from outfits like Pointsix
> <http://www.pointsix.com/> seem to be exlusively based on Dallas
> chips.
I've wondered about this too. I know they have a TM on 1-Wire, so you'd at
least (at least) have to call it something else. We've played with using
1-Wire for PAK interfaces, but I haven't had the time to look at the legal
ramifications of doing so.
Al Williams
AWC
* etc.
>Regarding Dallas Semi's ownership of the protocol--I'd be very
>interested to know if Parallax incurred a licensing fee or agreement
>or whatever to use the protocol with the BS2p (agreed, using it is
>not the same as impinging on family code and unique ID stuff).
I'd guess the licensing or registration issue would arise in
implementation of a slave device. Make all the masters you want!...
They control the slave market! It's a new twist on the razor versus
the razor blades economic model.
>The beauty of using the BS2p's 1-Wire functions is that the same
>Stamp I/O pin could be used in the next instruction to access a GPS
>data string stored in a second smart buffer, or a clock, a PS/2
>keyboard, mouse, a memory controller, thermometer, 1 of 16
>multiplexer, UART, the list goes on and on...
Maybe Occam's razor...
http://math.ucr.edu/home/baez/physics/occam.html
At 2:09 PM -0500 3/15/01, Kerry Barlow wrote:
>The Dallas weather mail list has extensive coverage of the problems
>associated with long runs of 1 wire cabling. There is a man on the list who
>made a special 1 wire hub, which allows shorter lengths of wire to be routed
>to various locations, all coming back to the hub, and from there to the
>microprocessor ( PC in this case) he is selling these hubs, for a small
>price, I dont know if he has any left.
>They have been talking quite a bit about this issue, and the work arounds,
>and solutions. People that are interested may wish to sign up to the 1 wire
>mailing list
>http://lists.dalsemi.com/mailman/listinfo/weather, you can also search the
>archives from this link.
>I have a 1 wire weather station, so try to keep abreast of whats going on
>there as well.
>Kerry
How far is your weather station from the PC? I wonder, is Dallas
still offering the good deal on the prototype weather station? The
one from Texas Weather is now quite expensive. I see Pointsix now
has a onewire interface for the Palm PC (both isolated & not).
-- regards
Thomas Tracy Allen PhD
electronically monitored ecosystems
http://www.emesystems.com
mailto:tracy@e...
telephone wire. I have never known of a problem with this setup, it has been
running for 2 years now this way. I do not know of a source for cheaper
weather stations. People on the weather list had been asking this question
also. I did not follow the threads unfortunatly, because I had my station
already.
I also added a 2nd indoor 1 wire thermometer to the system, I simply solderd
its leads to the telephone wire, before it went outdoors.
For anyone curios my station is at
http://mntnweb.com/weather/newweather.html
At 12:38 PM 3/15/2001 -0800, you wrote:
>At 11:50 AM +0800 3/15/01, S Parkis wrote:
>>Regarding Dallas Semi's ownership of the protocol--I'd be very
>>interested to know if Parallax incurred a licensing fee or agreement
>>or whatever to use the protocol with the BS2p (agreed, using it is
>>not the same as impinging on family code and unique ID stuff).
>
>I'd guess the licensing or registration issue would arise in
>implementation of a slave device. Make all the masters you want!...
>They control the slave market! It's a new twist on the razor versus
>the razor blades economic model.
>
>>The beauty of using the BS2p's 1-Wire functions is that the same
>>Stamp I/O pin could be used in the next instruction to access a GPS
>>data string stored in a second smart buffer, or a clock, a PS/2
>>keyboard, mouse, a memory controller, thermometer, 1 of 16
>>multiplexer, UART, the list goes on and on...
>
>Maybe Occam's razor...
> http://math.ucr.edu/home/baez/physics/occam.html
>
>
>At 2:09 PM -0500 3/15/01, Kerry Barlow wrote:
>>The Dallas weather mail list has extensive coverage of the problems
>>associated with long runs of 1 wire cabling. There is a man on the list who
>>made a special 1 wire hub, which allows shorter lengths of wire to be routed
>>to various locations, all coming back to the hub, and from there to the
>>microprocessor ( PC in this case) he is selling these hubs, for a small
>>price, I dont know if he has any left.
>>They have been talking quite a bit about this issue, and the work arounds,
>>and solutions. People that are interested may wish to sign up to the 1 wire
>>mailing list
>>http://lists.dalsemi.com/mailman/listinfo/weather, you can also search the
>>archives from this link.
>>I have a 1 wire weather station, so try to keep abreast of whats going on
>>there as well.
>>Kerry
>
>How far is your weather station from the PC? I wonder, is Dallas
>still offering the good deal on the prototype weather station? The
>one from Texas Weather is now quite expensive. I see Pointsix now
>has a onewire interface for the Palm PC (both isolated & not).
>
> -- regards
> Thomas Tracy Allen PhD
> electronically monitored ecosystems
> http://www.emesystems.com
> mailto:tracy@e...
>
>
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
Sincerely
Kerry
Admin@M...
WWW server hosting [url=Http://mntnweb.com]Http://mntnweb.com[/url]
Kerry Barlow
p.o. box 21
kirkwood ny
13795
Thanks for taking the time to explain. I'll play with this tonight and see
if it makes any sense to me at 11 PM!
thanks,
Mike
At 03:20 PM 3/15/2001 -0500, you wrote:
>For Mike and for Kerry Barlow
>
>Good afternoon
>
>I have two BS2s on my robot, one on the bottom deck and one on the top deck.
>The bottom Stamp controls the servos and the top stamp controls the video
>camera and transmitter and RF receiver output. Pin 15 of the bottom stamp
>is conmnected to pin 5 of the top stamp. The robot can operate in a
>controlled mode, where it executes a series of planned maneuvers, or in the
>remote mode where the BS2E transmitter module transmits one or two bytes of
>data which the robot decodes as a maneuver. In the controlled mode, the top
>stamp, the video circuit and the bottom stamp are turned on in that order by
>neans of miniature switches in the power supply. As soon as the bottom stamp
>stabilizes it says:
>
>N9600 con 16468
>com var word
>
>begin
>serout 15, N9600, 50, [noparse][[/noparse]"S"]
>serin 15, N9600, [noparse][[/noparse]com]
>
>'At this point the bottom stamp sits and waits for a serin.
>
>After the serin I say:
>
>if com = "G" then move
>
>'move is a routine thats reads data and executes the proper maneuvers
>
>'when the bottom stamp has executed all the planned maneuvers ----
>
>serout 15, N9600, 50, [noparse][[/noparse]"Q"]
>
>
>
>On the top stamp:
>
>N9600 con 16468
>com var word
>
>begin
>
>serin 5, N9600, [noparse][[/noparse]com]
>if com = "S" then start
>
>start
>high 3 'turns on video camera
>high7 'turns on video transmitter
>low 8 'turns on "Ready " light
>
>serout 5, N9600, 50, [noparse][[/noparse]"G"] 'tells bottom stamp it has video on and is
>ready
>
>serin 5, N9600, [noparse][[/noparse]com] 'waits for bottom stamp to tell it is done
>if com = "Q" then quit
>
>quit
>high 8
>low 3
>low 7
>goto begin
>
>Two things to remember - the bottom stamp MUST be turned on last so the top
>stamp has time to stabilize before the bottom stamps sends the first serout.
>Second, 16468 cannot be used for the baud rate, as in
>
>serout 15, 16468, [noparse][[/noparse]"S"]
>
>You must tell both stamps either N9600 or ON9600, preferably N9600.
>
>Programming in the "remote" mode is a bit more complicated but I will be glad
>to send the code if you like. Hope you can understand what I have written.
>It's a little difficult to try to explain two interacting programs at the
>same time.
>
>Regards
>Sid
>
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
_________________________________
Mike Walsh
walsh@i...
that would read wheel encoders from the robot and send to PC, and read
navigation instructions from PC to robot. I was wondering what RF
transmitters/receivers you used and what your code was (you mentioned
something of "remote" mode).
Thanks a lot!
Paul
Original Message
From: <Newzed@a...>
To: <basicstamps@yahoogroups.com>
Sent: Thursday, March 15, 2001 3:20 PM
Subject: Re: [noparse][[/noparse]basicstamps] BS2p 1-Wire Gadgets
> For Mike and for Kerry Barlow
>
> Good afternoon
>
> I have two BS2s on my robot, one on the bottom deck and one on the top
deck.
> The bottom Stamp controls the servos and the top stamp controls the video
> camera and transmitter and RF receiver output. Pin 15 of the bottom
stamp
> is conmnected to pin 5 of the top stamp. The robot can operate in a
> controlled mode, where it executes a series of planned maneuvers, or in
the
> remote mode where the BS2E transmitter module transmits one or two bytes
of
> data which the robot decodes as a maneuver. In the controlled mode, the
top
> stamp, the video circuit and the bottom stamp are turned on in that order
by
> neans of miniature switches in the power supply. As soon as the bottom
stamp
> stabilizes it says:
>
> N9600 con 16468
> com var word
>
> begin
> serout 15, N9600, 50, [noparse][[/noparse]"S"]
> serin 15, N9600, [noparse][[/noparse]com]
>
> 'At this point the bottom stamp sits and waits for a serin.
>
> After the serin I say:
>
> if com = "G" then move
>
> 'move is a routine thats reads data and executes the proper maneuvers
>
> 'when the bottom stamp has executed all the planned maneuvers ----
>
> serout 15, N9600, 50, [noparse][[/noparse]"Q"]
>
>
>
> On the top stamp:
>
> N9600 con 16468
> com var word
>
> begin
>
> serin 5, N9600, [noparse][[/noparse]com]
> if com = "S" then start
>
> start
> high 3 'turns on video camera
> high7 'turns on video transmitter
> low 8 'turns on "Ready " light
>
> serout 5, N9600, 50, [noparse][[/noparse]"G"] 'tells bottom stamp it has video on and is
> ready
>
> serin 5, N9600, [noparse][[/noparse]com] 'waits for bottom stamp to tell it is done
> if com = "Q" then quit
>
> quit
> high 8
> low 3
> low 7
> goto begin
>
> Two things to remember - the bottom stamp MUST be turned on last so the
top
> stamp has time to stabilize before the bottom stamps sends the first
serout.
> Second, 16468 cannot be used for the baud rate, as in
>
> serout 15, 16468, [noparse][[/noparse]"S"]
>
> You must tell both stamps either N9600 or ON9600, preferably N9600.
>
> Programming in the "remote" mode is a bit more complicated but I will be
glad
> to send the code if you like. Hope you can understand what I have
written.
> It's a little difficult to try to explain two interacting programs at the
> same time.
>
> Regards
> Sid
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
I first used the TWS/RWS from Reynolds Electronics (6.50 each) which
communicated quite well at 2400 baud. I discovered that my video transmitter
completely blocked the RWS receiver so I bought as 433 MHz transmitter and
receiver from Parallax to see if they would work better. Unfornuately they
didn't but I am still using them. They are a lot more expensive but they
have a trace anenna on the PCB which is much better than a 14" piece of wire
sticking up in the air.
As far as RF communication between your Boebot and a PC I really don't know
how you would go about that. You would have to pipe the receiver output into
a terminal program that would run at 2400 baud. A much simpler way to me is
to hook your receiver to another stamp, then have that stamp serout the data
it receives to the PC via output pin 16, which is in the stamp DB9 connector.
If you want to send navigation instructions in real time back to the Boebot
you would have to have another receiver on the Boebot and another transmitter
on the second stamp, or use a transceiver on both stamps. In my case, when I
am in the remote mode, my BS2E transmitter module has a 12-key keypad which
transmits a unique byte of data for each key, giving me 12 possible
instructions. The stamp on the Boebot receives the data, determines what
instruction the byte signifies, then retransmits the proper instruction to
the second stamp on the Boebot which then tells the servos what to do. I had
to use two stamps on the Boebot because one stamp controls the video system
plus accepting receiver input, the other the servos, whiskers and IR
detectors.
If you want to go this route I will be glad to send you the transmitter
module code and the two codes for the two stamps on the Boebot.
Sid