I got a PogoPlug Pro and have installed ArchLinuxARM onto it but the FTDI FT232RL based LinkUSB adaptor will not work with it properly. The older FT232BM type adaptors work ok but not the newer ones. The ArchLinuxARM guys are working on getting a newer kernel sorted for this device but they're not there yet...
So it's on the back-burner for a while longer... Alex > -----Original Message----- > From: Willard Korfhage [mailto:[email protected]] > Sent: Monday, 18 July 2011 4:14 a.m. > To: [email protected] > Subject: Re: [Owfs-developers] OWFS on PogoPlug Pro > > I just got owfs 2.8p12 and temploggerd working on a Dockstar yesterday, > and I would think that PogoPlug Pro would be very similar. Here is my > recipe for getting it working on a Dockstar with Arch Linux. I haven't > run through this a second time yet to figure out where I wrote down the > details incorrectly or omitted a step, but will do so in the next couple > days because I have another Dockstar to convert. > > 1. Put Arch Linux on the machine. There are various guides for that, but > yesterday a fellow wrote a blog entry about installing another system on > a Pogoplug Pro, and the first 60% of the entry is really just about how > to put Arch Linux on the machine. By the way, I can recommend crashplan > as a backup system. > > http://www.opticality.com/blog/2011/07/16/installing-crashplan-on-a- > pogoplug-pro/ > > 2. Install python2, swig, fuse, rrdtool and ttf-dejavu. The last of > these is fonts that temploggerd needs. There is owfs in the Arch linux > packages as an unsupported, user-submitted package, but it is 2.8p8, and > I decided to try the latest. > > 2. Download owfs and temploggerd from sourceforge. You have to make 2 > simple changes to the configure script for owfs because the default > python for Arch Linux in python 3. The configure script looks for > python up through 2.5, but Arch Linux installs 2.7, so you need to > update the script to check for that. > > Find the line > > for ac_prog in python-config python2.5-config python2.4-config > python2.3-config > > and make it into > > for ac_prog in python-config python2-config python2.5-config > python2.4-config python2.3-config > > And then find the line > > for ac_prog in python python2.5 python2.4 python2.3 python2.2 python2.1 > python2.0 python1.6 python1.5 python1.4 python > > and make it into > > for ac_prog in python python2 python2.5 python2.4 python2.3 python2.2 > python2.1 python2.0 python1.6 python1.5 python1.4 python > > This change, or looking for python2.7, ought to be incorporated into > the main build. > > Looking in the owfs package, I see that an alternative to changing the > configuration script is to run > > ./configure --with-python="/usr/bin/python2" > --with-pythonconfig="/usr/bin/python2-config" > > 3. Do the usual ./configure, make, sudo make install on both owfs and > temploggerd. owfs ends up in /opt/owfs. Temploggerd gets spread around > bit, but we'll get to that in a moment. First, check that owfs works. > > I put a DS9490R into the dockstar, and attached an iButtonLink sensor > that I had handy. I ran /opt/owfs/bin/owserver -u by hand, then ran > /opt/owfs/bin/owdir and found that it listed both the USB interface and > the temperature sensor. Running owread /<id>/temperature gave me the > temperature and verified that it was working properly. To get it to run > when it boots, I think I need to put the command into /etc/rc.local, but > I haven't done that yet. > > With the owserver working, I turned my attention to temploggerd. First, > I needed a web server, so I picked lighttpd and installed that. The only > change I made to lighttpd.conf was to add > > server.modules +=("mod_cgi") > cgi.assign = ( ".cgi" => "" ) > > The first line enables cgi, and the second line tells it to run cgi > script directly rather than invoke something else to interpret it. > > Now on to temploggerd. The binary for temploggerd is in /usr/local/bin, > the configuration file lands by default in /usr/local/lib/temploggerd, > and the image and template directories are in > /usr/local/share/temploggerd. > > I found configuring temploggerd frustrating initially because I wasn't > really clear on all the details, but it is one of those "easy once you > understand it" tasks. Here is my config file, designed just to show 1 > temperature sensor. > > > # This is the default values > # Empty owfs_dir means "search in /proc/mounts for fuse mount" > owfs_dir "" > # if owshell_path is set, the simple owfs shell-commands > owdir,owread,owpresent > # will be used instead of reading from a mounted fuse-filesystem. > owshell_path "/opt/owfs/bin/" > owshell_params "-s 4304" > rrdfile_path "/srv/http/temploggerd/rrd/" > rrdfile "temperature.rrd" all_temperature.cgi.templ > sensor_temperature.cgi. > templ > rrdfile_description "temperature.rrd" "Temperatures" > > # and for those sensors which didn't specify any rrd-file. > rrdfile_default "temperature.rrd" > rrdcgi_file "/usr/bin/rrdcgi" > www_dir "/srv/http/" > base_dir "/temploggerd/" > rrdimg_path "rrd/" > images_path "images/" > cgi_dir "/srv/http/cgi-bin/" > cgi_path "/cgi-bin/" > tmp_file "/tmp/temploggerd.tmp" > images_dir "/usr/local/share/temploggerd/images/" > tmpl_dir "/usr/local/share/temploggerd/templates/" > tmpl_all_cgi "all.cgi.templ" > tmpl_all_default "all_temperature.cgi.templ" > tmpl_sensor_default "sensor_temperature.cgi.templ" > tmpl_files "index.html" "style.css" "time_links.html" > "manual_selection.html" > "meta_tags.html" > #add_new_sensor_script "add_new_sensor.sh" > > # Add some own settings > rrdfile "temperature.rrd" all_temperature.cgi.templ > sensor_temperature.cgi. > templ > > ignore 81.761C26000000 > > sensor 28.33AF5B010000 "Temperature" temperature temperature.rrd > > > > Basically, I set the paths to the proper locations, put in a line to > ignore the usb interface, and put in the final line for the temperature > sensor. > > As I said initially, I haven't fully verified that I got all the steps > written down properly, and I haven't run through other functions yet to > verify that everything works, but going to http://dockstar/temploggerd > does let me click though the links and show a graph. This should be > enough to get you going, and I will put up a verified recipe later. > > > On 7/17/2011 2:29 AM, Alex Shepherd wrote: > > Hi Guys, > > > > Does anyone have a build/configure recipe for OWFS& PopoPlug Pro or > > comments on how to go about configuring it to run OWFS? > > > > I was thinking of getting the Seagate DockStation but decided to go for the > > PogoPlug Pro as it is cheaper, has more USB ports (I'll need 3 for 3 x > > LinkUSB adaptors + 1 USB Stick) and AFAICT it seems to have support for > OWFS > > + Temploggerd already. > > > > Regards > > > > Alex Shepherd > > > > > > ---------------------------------------------------------------------------- -- > AppSumo Presents a FREE Video for the SourceForge Community by Eric > Ries, the creator of the Lean Startup Methodology on "Lean Startup > Secrets Revealed." This video shows you how to validate your ideas, > optimize your ideas and identify your business strategy. > http://p.sf.net/sfu/appsumosfdev2dev > _______________________________________________ > Owfs-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
