Yes, I'm aware of diffs and I think/hope I've done the conversion
correctly.
Here's my LCD specs:
http://bytality.com/files/OWFS_Hardware_Files/40x4_LCD_specs___lc4857-lv-4x40.pdf
Here's my pin connections:
LCD_H Driver pinout --> 4x20 LCD pin - Description
01 --> 13 - Power Supply Groun
Hasn't been tested, yet. I have the board but haven't wired it up.
The liveCD is too old to have support for the DS2408 versions.
I think the current order of fixes is
1. Simultaneous
2. directory speed
3. owperl and DS2408 writes
4. LCD
So probably a week or so.
Paul Alfille
On 11/19/06, [EM
Make sure that you have your wiring correct since the pinout of the 4x40 is
different than all the others 2x40 or smaller.
Eric
[EMAIL PROTECTED] wrote:
> I seem to be having similar troubles too. I'm using a hobby-boards
> driver on a 4x40 LC4857FG-SNYLV (which is essentially two 2x40 LCD's
I seem to be having similar troubles too. I'm using a hobby-boards
driver on a 4x40 LC4857FG-SNYLV (which is essentially two 2x40 LCD's
put onto 1 board and I'm only using one of them ) It just gives me a
write error. Can anyone tell me exactly what that means? Is it
indicative of a wiring
Does the same error/bug exist for ow_ds9097U.c ?
On my WRT54G router I get really bad search time. 15 devices are listed in
minimum 3.3seconds (owserver + owfs). 100 loops will take about 5 minutes!
/Christian
[EMAIL PROTECTED]:~# cat /tmp/1wire/bus.0/system/adapter/name.ALL
DS9097
So I finally got a couple hours, pulled the latest CVS this morning and
tried the tests again:
[EMAIL PROTECTED]:~$ time for i in /var/1wire/mount/28*; do cat
$i/temperature; done 22.6875 25.3125 24
36.5 25.25 35.625 33.9375 36.8125 24.3125
29
From: Tim Müller-Seydlitz
Hi Paul,
I had quite some trouble to make owfs work with SuSE 10.0.
I traced it down to permission problems if I accessed owfs without being
superuser.
As I find the tool very useful, I would like to share my feedings:
In the directory /etc/udev/rules.d/
I created the
Am Sonntag, 19. November 2006 00:53 schrieb Paul Alfille:
> Ahha!
>
> It looks like a logic error -- if no device is found, the code still tests
> for a CRC error in the serial number, and probably asks for retries.
>
AH! That was simple. Thanks for hunting this down, Paul.
> Fixed in the CVS.
>