Hello Jan
I should have had included more info. So I am running owfs on a raspi. It
accesses ethernet 1wire masters through lan (linkhub, owserver enet).
1. login to raspi, run killall to shut owfs down
2. start owfs as described here on another machine for testing (as I can access
the master from any machine on my lan)
3. killall the testing version
4. start owfs on raspi again to get my usual system back
Between 1. and 2. I have to change connected devices, e.g. connect eservice lcd
for testing.
Using that setup I have 2 different machines running owfs, accessing the same
hardware (not at the same time). The first is the usual system I run (raspi),
the other is a machine running the build with patch as described here.
What I logged here is 2. and 3. - I omitted info from steps 1. and 4. as I
assumed them to be irrelevant for you.
>> $ git clone git://git.code.sf.net/p/owfs/code owfs-code
>> $ cd owfs-code/
>> ~/owfs-code$ ./bootstrap
>> ~/owfs-code$ ./configure
>> (get patch from
>> https://sourceforge.net/p/owfs/mailman/owfs-developers/?viewmonth=201606&viewday=28)
>>
>> ~/owfs-code$ patch -p1 < eservice_lcd.diff
>> ~/owfs-code$ make
>> ~/owfs-code$ nano owfs.conf
>> (copy content from my wiki)
>> ~/owfs-code$ module/owserver/src/c/owserver -c ~/owfs-code/owfs.conf --debug
>> -u
>>
> Uhhh, no. -c ~/owfs-code/owfs.conf and -u may be mutually exclusive. You
> haven't listed what is inside ~/owfs-code/owfs.conf.
Hmm, yes... I did not check the meaning of -u beforehand, as I was assuming you
know what I want... ;)))
Of course using -u with my config having ethernet-master does not make sence, I
removed that.
I'll send the conf file in another mail.
> Does your user have sufficient rights to access the host adaptor? Because you
> don't start owserver as root.
Another good question - but as I access lan not usb, did not get an error
message and the lcd reacted after sending the clear command, I strongly assume
it should be fine. Also the working raspi system uses sudo for owfs only, not
for owserver or owhttpd.
>> ~/owfs-code$ module/owshell/src/c/owwrite /29.2F7214000000/strobe 1
>> ~/owfs-code$ module/owshell/src/c/owwrite /29.2F7214000000/LCD_H/clear 1
>> ~/owfs-code$ module/owshell/src/c/owwrite /29.2F7214000000/LCD_H/message
>> "Foobar"
>> (copy output of 1st/debug window for maillist then quit app)
>>
> I'd like to see that log.
I tried to send it to the maillist 2 times now. It always refuses to deliver it
since its too big (>60kB) - so a moderator has to make it go through.
http://dpaste.com/2W4Z0GF
> Please try again, cleanly.
I tried again without the -u param but it did not make any change. Still lcd
background goes on after clear command. May be I need to test using the other
master. Currently the lcd is connected to the linkhub - can consider connecting
it to the enet, but would need to get 12V from somewhere else then.
Thanks for your support! Greetings
Dr. Trigon
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
