I think for this project it's going be be easiest to simply emulate an
network connected device, I guess an LinkE is the ideal candidate ?
Has anyone done this in the past ?
Cheers
Stuart
On 26 Nov 2008, at 09:14, Stuart Poulton wrote:
> Ok, a few more details...
>
> The device I'm intereste
Ok, a few more details...
The device I'm interested sends data to the serial port every 6 seconds,
I've already got a perl script that puts this into a DB, but would be
great to get it into OWFS.
Currently it logs two parameters, temp and current.
Any perl guru's able to point me in the right di
Hi Paul,
Data arrives from a serial device every x seconds, I've got the perl to
do this already.
We can of course within the perl allocate an unique ID. It's then simply
coding the perl to respond to the query from another owserver ? This is
the bit I'm not sure about.
The other thoug
Can you explain a little bit what you need?
Are you trying to add a non-1-wire device into owfs? To really fit in, it
should have a unique ID that is roughly compatible with 1-wire. Probably the
easiest would be to make a controller that looks like a small owserver, so
any owfs program can talk to
I'm pretty sure this has been covered in the past. But here goes.
I'd like to be able to include data from a non owfs source in owfs, can
this be done ? Perhaps by the creation of a new device family ?
I'm currently reading data from the device using perl, it's two simple
parameters of current an
