I had to test it now myself again, since I got unsure if I had set 
outputs via single commands.

Here is a short howto for setting up the LinkUSB with owfs on OpenWRT 
Backfire

1. install the kernel driver for the FTDI chip on the LinkUSB:

root@dir825:~# opkg install kmod-usb-serial-ftdi
Installing kmod-usb-serial-ftdi (2.6.32.27-1) to root...
Downloading 
http://downloads.openwrt.org/backfire/10.03.1/ar71xx/packages/kmod-usb-serial-ftdi_2.6.32.27-1_ar71xx.ipk.
Installing kmod-usb-serial (2.6.32.27-1) to root...
Downloading 
http://downloads.openwrt.org/backfire/10.03.1/ar71xx/packages/kmod-usb-serial_2.6.32.27-1_ar71xx.ipk.
Configuring kmod-usb-serial.
Configuring kmod-usb-serial-ftdi.

There should now a device ttyUSB0 in /dev

2. install owfs from standard package source:

root@dir825:~# opkg install owfs
Installing owfs (2.8p4-2) to root...
Downloading 
http://downloads.openwrt.org/backfire/10.03.1/ar71xx/packages/owfs_2.8p4-2_ar71xx.ipk.
Configuring owfs.

3. make a directory for the fuse-filesystem. I use 1wire in /mnt

root@dir825:~# mkdir /mnt/1wire

4. start owfs like so for example:

root@dir825:~# owfs -d /dev/ttyUSB0 -m /mnt/1wire

5. check in the 1wire directory if the bus is up and running

root@dir825:~# ls /mnt/1wire/
01.59A3D5120000  28.1C5015020000  28.2E4115020000  28.487A15020000 
28.664515020000  28.893015020000  28.8D3C15020000  28.E35415020000 
29.646C08000000  alarm            settings         statistics       system
28.0F5715020000  28.227415020000  28.405C15020000  28.496D15020000 
28.764A15020000  28.8C4615020000  28.A04A15020000  28.F13915020000 
29.B46008000000  bus.0            simultaneous     structure        uncached


There you go!


Now on to Silvios problem:

I did set PIO.0 on 29.646C08000000 and ... NOTHING! I cannot set single 
outputs as well.
Writing to 1 to PIO.BYTE works fine though. Output 0 gets switched on, 
but PIO.0 does not get updated, it stays on 0!

So I am confirming the problem!!!

Shame on me. My previous test on OpenWRT was not very thorough!

Btw., I can read temperatures fine!




On 11/04/2012 10:44 AM, Martin Patzak (GMX) wrote:
> Silvio,
>
> I did use the standard package!
>
> Maybe you can start owfs in foreground-mode and set the error-level
> higher. This way you can compare the bus-communication happening when
> setting one bit vs. the whole byte!
>
>
>
> On 11/04/2012 09:57 AM, Silvio Schmieder wrote:
>>
>> @ Martin:
>> Did you use the owfs package from OpenWrt download folder or did you
>> compiled the package yourself?
>>
>
> ------------------------------------------------------------------------------
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> http://p.sf.net/sfu/logmein12331_d2d
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to