Ok, I finally have got a free-pascal unit implementing major OWnet protocol
client functions.
It can be compiled right now under unix only, as the fpc TTcpClient class
used for TCP is not portable,
so I have a plan to substitute it with synapse in the future.
For a while, if somebody interested I c
Thank you Preben, George!
I'v got Hans's code. I will try convert it into Lazarus project and mail
back results.
On 08/26/2013 11:06 PM, George Zouganelis wrote:
there is also a module available under ownet/pascal (
http://owfs.cvs.sourceforge.net/viewvc/owfs/owfs/module/ownet/pascal/ )
there is also a module available under ownet/pascal (
http://owfs.cvs.sourceforge.net/viewvc/owfs/owfs/module/ownet/pascal/ )
On Aug 26, 2013, at 15:59 , "Preben Bille Brahe" wrote:
> I have found the mail from 2013-04-07 where Hans Erik Busk announced the
> Delphi component. If you access h
I have found the mail from 2013-04-07 where Hans Erik Busk announced the
Delphi component. If you access his homepage http://busk.dk/ he is
providing a link to the following:
http://busk.dk/Resources/owfs_delphiClient.zip
The original mail additionally provides his email address spam1 at the
above
Yes, there were topic with this same name opened by Hans Erik Busk at
april 2013 about his delphi component already implementing some
functionality. I hope this could be starting point for me, but Icant
figure out how to pick up his old topic or contact himother way to
obtain his source.
On 08
delphi / lazarous is a very old todo list, put it on owfs could be
very nice and wellcome!
2013/8/25 Попов Алексей :
> Hello Hans!
>
> I want take a look at yours delphi owserver client class/component and
> possibly make attempt to port it into FPC/Lazarus environment.
> Unfortunately, the link
Hello Hans!
I want take a look at yours delphi owserver client class/component and possibly
make attempt to port it into FPC/Lazarus environment.
Unfortunately, the link http://busk.dk/owfs_delphiClient.zip you have posted
does not working now. It seems file was removed from server.
Can you ple
Hello Hans!
I want take a look at yours delphi owserver client class/component and possibly
make attempt to port it into FPC/Lazarus environment.
Unfortunately, the link http://busk.dk/owfs_delphiClient.zip you have posted
does not working now. It seems file was removed from server.
Can you ple
Do you mean setting parameters in the owserver or in the individual sensors?
I am using an array of DS18B20, and I have now refreshed my memory about
these devices :-)
They have a couple of registers where a lower and upper alarmvalue can
be set. I hve never seen a real advantage in doing that, a
Ownet (connection to a owserver) just get set and read directory entries,
if you can set temperature unit in owserver, you have done 1/3 of commands,
if you can set one value with your api, please provide a example of set,
read and retrive dir entries, that's 99% that everybody need
Em 07/04/2013 1
I am not quite sure what you mean.
I have only worked with an usb master and temperature sensors as it is
the only one I have access to.
The 'C', 'F', 'K', and 'R' is set by the flags although, like the
pressure scales, I have not defined those values in the unit, but that
is easily done if nee
You can set some owserver parameters, its works like setting a gpio device
pin, try the directories from owserver that set whats the temperature unit
for example, try to write 'C' or 'F' to it, if it works, you can set gpio
devices too
Em 07/04/2013 15:14, "Hans Erik Busk" escreveu:
> Actually th
Actually ther is only one public function call:
function ask(pCallType, pFlags: UInt32; pTxt: AnsiString;
var pAnswer: TStringlist):integer;
It returns the errorcode as delivered from owserver, and the value(s)
obtained is in the pAnswer stringlist.
The
Please, if possible send example with 'get' and 'set' and 'dir' commands to
retrieve and send information about files and directories, i think its all
we need in api client side, errors can be handled by app like no value from
server, but maybe in a next release an error interface will be nice
Em 0
Nice, a clean interface is the best ownet need, about lazarus i think only
a test could work, its nice since lazarus can work in posix world and
windows world. But good work men, it will nice to have your client for
delphi with us
Em 07/04/2013 12:55, "Hans Erik Busk" escreveu:
> I don't know muc
I don't know much about lazarus as I through my work have to use delphi,
but I don't think there should be any major problem as long as lazarus
have a TcpClient like that of delphi. I deliberatly avoided using Indy
or IpWorks components to increase compatibility with other delphi versions.
Anoth
nice, maybe you could test it in lazarus too? does it comes with examples?
the delphi api was a old todo thing in my tasks, but i stopped owclient
development some time ago
2013/4/7 Hans Erik Busk
> I have developed a delphi class for reading from owserver.
> It is rather basic at the moment, a
I have developed a delphi class for reading from owserver.
It is rather basic at the moment, as I have only access to temperature
sensors.
I have not implemented proper error reporting as I have not been able to
find the possible errorcodes :-(
In the zipfile is also a small testprogram that perf
18 matches
Mail list logo
