I got a few Moteinos and shoved one in a box with a battery. I'd like to
get a few sensors (1Wire and otherwise) linked up on owexternal ..
http://www.cupidcontrols.com/?p=199
Colin
On 2/11/2014 10:37, Stuart Poulton wrote:
Colin,
Couple of thoughts, which I may have mentioned previously
Colin, Stuart,
On 02/10/2014 10:30 PM, Colin Reese wrote:
Anybody chime in with status on this? I think this will be where I
go.
On 2/10/2014 06:47, Stuart Poulton wrote:
To be fair, I would have thought this was the ideal application
for
Hi Eloy,
Time for a little self promotion. The following blog post
http://labs.homelabs.org.uk/wireless-temperature-sensor-using-ciseco-rfu-328/
Does exactly this, low power battery sensors using a wireless (NOT WIFI)
layer using off the shelf components, I'm about to send of a PCB order
for
Hi Stuart,
I don't want to discount how cool I think this idea is - it's great, and
proves this can be done effectively.
On the surface, I can get this functionality from the XBee Series 2 and an
ATMega/ATTiny and have demonstrated this. You can also add 1Wire sensors to
the uC - I've had luck
These look great. How are multiple Moteinos resolved? How are remote IO
addressed on the ATMega? Is there a developed python/RPi functional
library?
Colin
On Tue, Feb 11, 2014 at 4:21 AM, Eloy Paris pe...@chapus.net wrote:
Colin, Stuart,
On 02/10/2014 10:30 PM, Colin Reese wrote:
Crap. This thing runs on SPI? I've got all my SPI allocated.
On Tue, Feb 11, 2014 at 4:21 AM, Eloy Paris pe...@chapus.net wrote:
Colin, Stuart,
On 02/10/2014 10:30 PM, Colin Reese wrote:
Anybody chime in with status on this? I think this will be where I
go.
On 2/10/2014 06:47,
Colin,
Couple of thoughts, which I may have mentioned previously
1 - Meshing introduces some restrictions when there are sleeping nodes iirc.
2 - The key to getting decent battery life is making sure that everything
sleeps at every available opportunity. For example, the radio, and uC sleep
Indeed.
I think sleep and occasional transmit within range is the way to go, at
least to start. Power the mesh nodes if need be and set them to be
receiving for propagation. I suppose one could synchronize wake times and
then mesh nodes needn't always be on.
I really like the moteinos and will
Hi Colin,
On 02/11/2014 01:14 PM, Colin Reese wrote:
Crap. This thing runs on SPI? I've got all my SPI allocated.
Yes, the RFM12B (and the new RFM69) has an SPI interface.
SPI allows for multiple slaves; you do need an independent SS signal
from the master for each slave device, though.
Yes, but I don't have to talk to the RFM. I can talk to the ATMega.
On Tue, Feb 11, 2014 at 11:05 AM, Eloy Paris pe...@chapus.net wrote:
Hi Colin,
On 02/11/2014 01:14 PM, Colin Reese wrote:
Crap. This thing runs on SPI? I've got all my SPI allocated.
Yes, the RFM12B (and the new
On 02/11/2014 01:03 PM, Colin Reese wrote:
These look great. How are multiple Moteinos resolved? How are remote IO
addressed on the ATMega? Is there a developed python/RPi functional
library?
I honestly don't know. I think that there would be some amount of code
that needs to be written on
On 02/11/2014 02:10 PM, Colin Reese wrote:
Yes, but I don't have to talk to the RFM. I can talk to the ATMega.
I am not following; what do you mean by I don't have to talk to the
RFM? If you want to send data wirelessly then someone has to talk to
the RFM. That'd be the microcontroller. So
That sounds right. My complaint was that I have all my SPI on the Pi
occupied, although in a pinch I could use another GPIO as an additional
chip select.
So what I have:
Sensor(s) -- (I2C, GPIO, etc) -- uC (ATMega) -- SPI -- RFM -- 433 --
RFM -- SPI -- uC (ATMega) -- UART -- Pi
I'll start off
On 02/11/2014 02:29 PM, Colin Reese wrote:
That sounds right. My complaint was that I have all my SPI on the Pi
occupied, although in a pinch I could use another GPIO as an additional
chip select.
So what I have:
Sensor(s) -- (I2C, GPIO, etc) -- uC (ATMega) -- SPI -- RFM -- 433
-- RFM --
I believe the USB is really just a combination of the FTDI/USB adapter and
the Moteino. The FTDI bridge is for programming, not for runtime. As far as
I know, that is.
Colin
On Tue, Feb 11, 2014 at 11:39 AM, Eloy Paris pe...@chapus.net wrote:
On 02/11/2014 02:29 PM, Colin Reese wrote:
Colin,
The FTDI bridge works the same as on an arduino, it's use for programming, or
for sending serial data from a running sketch to the PC.
Stuart
On 11 Feb 2014, at 19:47, Colin Reese wrote:
I believe the USB is really just a combination of the FTDI/USB adapter and
the Moteino. The
Hi Colin,
On 02/11/2014 02:47 PM, Colin Reese wrote:
I believe the USB is really just a combination of the FTDI/USB adapter
and the Moteino. The FTDI bridge is for programming, not for runtime. As
far as I know, that is.
The FTDI bridge is used for both programming and runtime serial port.
yes, as i thought.
On Tue, Feb 11, 2014 at 11:52 AM, Stuart Poulton webw...@gmail.com wrote:
Colin,
The FTDI bridge works the same as on an arduino, it's use for programming,
or for sending serial data from a running sketch to the PC.
Stuart
On 11 Feb 2014, at 19:47, Colin Reese wrote:
I have very little Arduino experience, but I was under the impression that
the serial console over the FTDI was typically just used for debug.
On Tue, Feb 11, 2014 at 11:54 AM, Eloy Paris pe...@chapus.net wrote:
Hi Colin,
On 02/11/2014 02:47 PM, Colin Reese wrote:
I believe the USB is
On 02/11/2014 02:58 PM, Colin Reese wrote:
I have very little Arduino experience, but I was under the impression
that the serial console over the FTDI was typically just used for debug.
What's the difference between sending a debug message to the PC or RPi
through the serial port/USB
You connect the Moteino/Arduino to the RPi using USB. Your code running
on the RPi opens /dev/ttyUSB0 (or whatever it shows up as) and talks to
the uC on the Moteino/Arduino like if it were using a true serial port
(/dev/ttyUSB0 behaves like a true serial port for all intents and
purposes).
Oh, I see. I would be talking to the moteduino directly through my FTDI/USB
on my PC. I have my USB ports busy on other things, and would use the Rx/Tx
for the local moteduino. No need for two ports for me.
On Tue, Feb 11, 2014 at 12:31 PM, Eloy Paris pe...@chapus.net wrote:
You connect the
Am 10.02.2014 00:31, schrieb Colin Reese:
Well, I want a cheap, small, low-power, bullet-proof sensor node. I want
to be able to read loads of them, preferably in a developed, extendable
framework, from a central sensor gateway, at the moment an RPi-based
control unit. Nothing seems to meet
I do not see what is the reason against the linux box. I do not think you
could get cheaper with an avr and Xbee than a tplink 703n,
http://www.ebay.com/bhp/tp-link-tl-wr703n
Vajk
On Sun, Feb 9, 2014 at 10:48 PM, Colin Reese colin.re...@gmail.com wrote:
I want to run a microcontroller with a
On 10 February 2014 12:01, Vajk Fekete vaj...@gmail.com wrote:
I do not see what is the reason against the linux box. I do not think you
could get cheaper with an avr and Xbee than a tplink 703n,
http://www.ebay.com/bhp/tp-link-tl-wr703n
I presume one would need a usb/1wire adaptor with that.
Am 10.02.2014 13:20, schrieb Colin Law:
On 10 February 2014 12:01, Vajk Fekete vaj...@gmail.com wrote:
I do not see what is the reason against the linux box. I do not think you
could get cheaper with an avr and Xbee than a tplink 703n,
http://www.ebay.com/bhp/tp-link-tl-wr703n
I presume
There are several options
- real usb 1wire host - pretty expensive
- usb serial+serial host
- use the internally available serial port (the console of the machine,
like with rpi) and use a serial 1wire host
- use some available gpio lines and do bit-banging
I went for the first because this
On 10 February 2014 13:36, Vajk Fekete vaj...@gmail.com wrote:
There are several options
- real usb 1wire host - pretty expensive
- usb serial+serial host
- use the internally available serial port (the console of the machine,
Options 2 and 3 are not going to be significantly cheaper than
On 10 February 2014 12:38, Jan Kandziora j...@gmx.de wrote:
Am 10.02.2014 13:20, schrieb Colin Law:
On 10 February 2014 12:01, Vajk Fekete vaj...@gmail.com wrote:
I do not see what is the reason against the linux box. I do not think you
could get cheaper with an avr and Xbee than a tplink
You do need some 1wire host for the AVR too.
If not, that means you plan for bit banging and a passive interface. Same
is possible with openwrt and a cheap router.
An other option is the arduino YUN, which is an arduino and a wifi module.
But the wifi module in there is a complete cheap home
I've no problem using a host chip like the ds2483, which I use all over the
place. I'd strongly prefer this to bitbanging.
On Feb 10, 2014, at 4:38, Jan Kandziora j...@gmx.de wrote:
Am 10.02.2014 13:20, schrieb Colin Law:
On 10 February 2014 12:01, Vajk Fekete vaj...@gmail.com wrote:
I do
I think serial host and bitbanging uc over xbee would work, but not for
multiple remotes.
On Feb 10, 2014, at 5:40, Colin Law clan...@gmail.com wrote:
On 10 February 2014 13:36, Vajk Fekete vaj...@gmail.com wrote:
There are several options
- real usb 1wire host - pretty expensive
- usb
Interesting. Thank you.
On Feb 10, 2014, at 4:01, Vajk Fekete vaj...@gmail.com wrote:
I do not see what is the reason against the linux box. I do not think you
could get cheaper with an avr and Xbee than a tplink 703n,
http://www.ebay.com/bhp/tp-link-tl-wr703n
Vajk
On Sun, Feb
You're not the only one there.
On Feb 10, 2014, at 5:56, Vajk Fekete vaj...@gmail.com wrote:
You do need some 1wire host for the AVR too.
If not, that means you plan for bit banging and a passive interface. Same is
possible with openwrt and a cheap router.
An other option is the
Colin,
Is the use of a Raspberry Pi / Beaglebone completely out of the question ?
Stuart
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
What about a ds2480 into an atmega running owserver code 'emulation' over wifi
with an xbee or other wifi module?
On Feb 10, 2014, at 5:56, Vajk Fekete vaj...@gmail.com wrote:
You do need some 1wire host for the AVR too.
If not, that means you plan for bit banging and a passive interface.
I already use a Pi for the main gateway. It's big with enclosure and
necessitates a PS.
Think about having a sensor gateway at one point with remote modules in each
room. It would be crazy to have a Pi in each room. Ideally the remotes could be
battery powered.
On Feb 10, 2014, at 6:20,
Sure, wasn't sure what the driver was for wireless.
I think it's safe to say that things like
Yun, TP-Link, Pi, and BBB all play in the same arena so can be ruled out.
On 10/02/14 14:25, Colin Reese wrote:
I already use a Pi for the main gateway. It's big with enclosure and
necessitates a
Silly me; atmega328 has i2c. I can use the 2483, but need to get data out.
Per the earlier conversation, can I mount the xbee serial /dev/AMA0 as a bus if
running in transparent? I believe this us possible, but limited to one bus.
This may have been previously discussed, but an API-mode
To be fair, I would have thought this was the ideal application for
http://owfs.org/index.php?page=external-sensor-design
Not sure where Paul is with support etc, if it even exits.
On 10/02/14 14:36, Colin Reese wrote:
Silly me; atmega328 has i2c. I can use the 2483, but need to get data
Yes! This is the 'glue' aspect I wrote of. If I know how to present data to
owfs, I can write my serial listener or API poller to configure it as owfs
would like.
On Mon, Feb 10, 2014 at 6:47 AM, Stuart Poulton webw...@gmail.com wrote:
To be fair, I would have thought this was the ideal
it's up to you. a wifi xbee module is about twice as much as the tplink
router I have linked.
wifi, and tcpip are pretty complex protocols. to handle encryption, data
rates and the protocols, you must have some real cpu with some real
operating system. and once we have that, it will likely be
But the xbee is smaller and doesn't require hacking a router OS, which I'm not
interested in doing. It also doesn't scale for production. It's just not
designed for the job at all. With the openwrt router, what's the interface ?
Bitbanging gpio? Usb chip?
I have not seen reasonably priced
Neither me has seen reasonable hw for 6lowpan.
Production is all different, I admit. Have to consider mid/long term
availability of the components.
Vajk
On Mon, Feb 10, 2014 at 9:44 PM, Colin Reese colin.re...@gmail.com wrote:
But the xbee is smaller and doesn't require hacking a router OS,
Anybody chime in with status on this? I think this will be where I go.
On 2/10/2014 06:47, Stuart Poulton wrote:
To be fair, I would have thought this was the ideal application for
http://owfs.org/index.php?page=external-sensor-design
Not sure where Paul is with support etc, if it even
Be good to find out, I'm certainly interested in using this with my
Wireless temp sensors, details here
http://labs.homelabs.org.uk/wireless-temperature-sensor-using-ciseco-rfu-328/
Stuart
On 11/02/14 03:30, Colin Reese wrote:
Anybody chime in with status on this? I think this will be where I
Paul,
How would you envision implementing a remote owserver over a WiFi module?
Colin
On 1/27/2014 10:54, Paul Alfille wrote:
Honestly, the easiest way is a remote owserver. That can join your
network seemlessly. You can even have a remote serial bus master and a
long serial line.
A remote
On 09.02.2014 22:13, Colin Reese wrote:
Paul,
How would you envision implementing a remote owserver over a WiFi module?
This is 100% easy and possible since many years, just take any
openwrt-router and run owserver on it.. Works pretty fine 24x7.
The other way around, low-power I'd more
I want to run a microcontroller with a remote owserver or 1Wire devices.
I don't want/need another linux box. A cheap AVR and WiFi unit like an
XBee WiFi would be ideal. Is there not AVR code that would run owserver
over a WiFi module?
Where can I find docs on owexternal? I've seen mention of
Like this:
http://www.etherweather.com/
But actively developed and wireless.
Colin
On 2/9/2014 13:41, Michael Markstaller wrote:
On 09.02.2014 22:13, Colin Reese wrote:
Paul,
How would you envision implementing a remote owserver over a WiFi module?
This is 100% easy and possible since
On 09.02.2014 22:48, Colin Reese wrote:
I want to run a microcontroller with a remote owserver or 1Wire devices.
I don't want/need another linux box. A cheap AVR and WiFi unit like an
XBee WiFi would be ideal.
Nearly any TP-Link running OpenWRT is cheaper than the single
XBee-Module? Not
Well, I want a cheap, small, low-power, bullet-proof sensor node. I want
to be able to read loads of them, preferably in a developed, extendable
framework, from a central sensor gateway, at the moment an RPi-based
control unit. Nothing seems to meet all of the criteria.
Standard XBee would
Well, if you want lowest power, small nodes I'd recommend to Google for
Contiki/6lowpan first. Integration into owfs should be really easy..
Just need one GW.
If you want low cost, existing HW and proved reliability, I guess your
better off using a $20 OpenWRT-routers simply running owfs/owserver
: [Owfs-developers] pseudo-bus serial bridge
So how does a local owfs instance read a remote server and merge networks?
Could you potentially use something like ser2net to filter and pipe serial
1wire data to a local TCP port, and then have the local owfs instance read and
merge this network
I take it your microprocessor doesn't run linux. In that case, you want it
to look like a serial bus master.
There are 3 serial bus masters that I can remember off hand: the DS9097U,
the Link and the HA5. The later 2 use a much simplified serial data stream
(simple ascii), and I think are both
Is there a good reason why a micro can't emulate a serial bus master?
On Tue, Jan 28, 2014 at 12:12 PM, Paul Alfille paul.alfi...@gmail.comwrote:
I take it your microprocessor doesn't run linux. In that case, you want it
to look like a serial bus master.
There are 3 serial bus masters that
Sorry, reading your last sentence, you did address this. Why would you not
recommend trying this? Error-prone?
On Tue, Jan 28, 2014 at 12:12 PM, Paul Alfille paul.alfi...@gmail.comwrote:
I take it your microprocessor doesn't run linux. In that case, you want it
to look like a serial bus
The emulated serial requires changing baud rates for each 1-wire
communication, and using a serial byte to send each 1-wire bit. Since most
computer UARTs have a pretty small buffer, the CPU does a lot of work
waiting for the serial data.
A microprocessor is great for low-level bit-banging, but
/)
i didn't tested this one, but they work like a multi drop network
(rs485)? for example, using one serial allow 10+ ow bus?
2014-01-28 Paul Alfille paul.alfi...@gmail.com:
The emulated serial requires changing baud rates for each 1-wire
communication, and using a serial byte to send each
Understood. Thanks for the explanation.
On 1/28/2014 16:07, Paul Alfille wrote:
The emulated serial requires changing baud rates for each 1-wire
communication, and using a serial byte to send each 1-wire bit. Since
most computer UARTs have a pretty small buffer, the CPU does a lot of
work
Honestly, the easiest way is a remote owserver. That can join your network
seemlessly. You can even have a remote serial bus master and a long serial
line.
A remote OpenWRT router, a Raspberry pi, ... All can support a 1-wire
network and will merge with a local network:
The other option is a new
Easiest, perhaps. Currently the Pi is the local master. I want the external
nodes to be low-power and relatively stupid to minimize management.
For the cost of an XBee ($17), an ATTiny85 or ATMega328 ($1-3), a regulator
($1), an enclosure ($5) a 5V PS or battery ($3-4), a breadboard ($1) and
an
you can use rs-232 to rs422 converters + rs232 to ow converter + many
usb-serial converters
rs422 allow 1500meters of distance with 4 wires, add a rs232-rs422
converter near to usb serial converter
near to onewire line, add a rs422-rs232 converter and the rs232-ow converter
this should work
So how does a local owfs instance read a remote server and merge networks?
Could you potentially use something like ser2net to filter and pipe serial
1wire data to a local TCP port, and then have the local owfs instance read
and merge this network with the local one?
Colin
On Mon, Jan 27,
you can start the owserver/owhttp/ow with many ow masters, each
bus will be a directory
bus.0/devices...
bus.1/devices...
via network i think the easier method is owserver link, or ser2net,
and maybe a cheap version with the rs422 converter
maybe 50cents per max422 devices? more 8 usd with
I want wireless, and my wireless devices talk serial.
Best I can think is to read on serial, process data into owfs friendly
format (similar to what owfs would read from owserver), and output on local
tcp. Tell owfs to read local tcp as another network.
Would it be as simple as modifying the
Am 27.01.2014 20:47, schrieb Colin Reese:
So how does a local owfs instance read a remote server and merge networks?
It does automatically. You can additionally see the remote branches as
separare bus.X/ directories if you like.
Kind regards
Jan
http://blog.philippklaus.de/2011/08/make-rs232-serial-devices-accessible-via-ethernet/
2014-01-27 Roberto Spadim robe...@spadim.com.br:
google ethernet serial you will see a lot of devices
try to get one with telnet rfc2217
(http://tools.ietf.org/html/rfc2217) that's what ser2net do
yes, but the data coming over serial would not be intelligible to owserver
without processing. If I had one at each end, then yes, but at the one-wire
end I am reading on a uC and transmitting raw readings wirelessly. If I
knew how to format them for owfs, then this approach could possibly work.
? i don't understand
check:
ethernet (wifi ethernet, ethernet)
wireless (wifi ethernet, bluetooth, zb)
serial (rs232,rs485,rs422)
ow - serial-ow converters (ds2480b), microcontroler bus (on/off gpio),
i2c-ow converters (ds2482)
what part you need?
It will look like:
1Wire network (DS18B20, DS2408, etc) -- uC (ATTiny, ATmega) GPIO, OneWire,
DallasTemperature, SoftwareSerial libraries -- XBee/Zigbee send --
XBee/Zigbee receive -- RPi
At the moment the serial output from the uC is just code I write that says
'hey, here the temperature is'.
A very similar conversation here:
http://comments.gmane.org/gmane.comp.file-systems.owfs.devel/9734
On Mon, Jan 27, 2014 at 1:33 PM, Colin Reese colin.re...@gmail.com wrote:
It will look like:
1Wire network (DS18B20, DS2408, etc) -- uC (ATTiny, ATmega) GPIO, OneWire,
DallasTemperature,
How about the DS2480B over XBee? Is it possible to run in transparent mode
and run, for example,
'owserver -d /dev/ttyAMA0 --i2c=/dev/i2c-1:ALL -p 4304'
to merge the two networks?
Would this work with multiple DS2480Bs? I suspect not, in which case I'd
probably still write my own interface
Humm, you are doing a new bus master
At owfs side if you don't use any known protocol you will wirte a new bus
master (very possible and supported)
Maybe something easier like many bluetooth-serial adapters could work, or
maybe a zigbee serial converter, plus a ds2480b could work too, but you
Each ds2480b need a new serial port
It use tx/rz and stop signal (something like change baud rate plus send a 0
character)
Em segunda-feira, 27 de janeiro de 2014, Colin Reese colin.re...@gmail.com
escreveu:
How about the DS2480B over XBee? Is it possible to run in transparent mode
and run,
maybe a serial-serial converter coudl work
think a new device (you uC) running a firmware that will receive at
one serial port a default protocol, like rfc 2217, this protocol will
change other uC serial port settings, like baud rate, send receive,
etc
at linux side you create a fuse program that
76 matches
Mail list logo
