Re: Firmware being used on the wireless routers

Hello!
Indeed.
I looked at the list of gear, and naturally the one I want to use isn't on
the list. Although all of their later models are on it. This tells me that
Wireless-B isn't on that group's things-to-do list.

--
Gregg C Levine hansolofalcon <at> worldnet.att.net
"The Force will be with you always." Obi-Wan Kenobi
 
-----Original Message-----
From: owfs-developers-bounces <at> lists.sourceforge.net
[mailto:owfs-developers-bounces <at> lists.sourceforge.net] On Behalf Of Eric
Allen
Sent: Thursday, November 29, 2007 11:31 AM
To: owfs-developers <at> lists.sourceforge.net
Subject: Re: [Owfs-developers] Firmware being used on the wireless routers

The firmware for which we have precompiled packages is OpenWRT, which has a
list of supported hardware here. That's all I know.
On Nov 29, 2007 1:31 AM, Gregg Levine < gregg.drwho8 <at> gmail.com> wrote:
Hello!
Would one of you please sort out this assertion? Essentially the 
alternative firmware for the LinkSys (and probably others) brand of
wireless routers, is only targeting the families who communicate using
the G standard as opposed to the B one.

My access point, also a B one is starting to act funny, and I'd like 
to add that router to my setup, where it would supply extra wired
ports, and even the wireless access ones. (It turns out that one of

DS2480 "Cannot detect DS2480 or LINK interface" in 2.7

Today I changed our 1wire network over to a different computer, which
I put 2.7.0 on. I got "Cannot detect DS2480 or LINK interface" most
times (on one interface - we have 3 - it worked sometimes).

Out of curiosity I went back to 2.6p8 (the old computer had 2.4-1 with
ownet-python added by hand, since I faced similar problems with 2.6-1
I think) and it works fine now (at least no error when starting).

I looked at the ds2480_detect code, and there seems to be some changes, notably

if (((setup[3] & 0xF1) == 0x00) &&
                ((setup[3] & 0x0E) ==
DS2480_baud(in->connin.serial.speed, &pn)) &&
                ((setup[4] & 0xF0) == 0x90) &&
                ((setup[4] & 0x0C) == DS2480_baud(in->connin.serial.speed, &pn))
                ) {

has gone and new calls to DS2480_configuration_code are done.

Michael

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

Re: DS2480 "Cannot detect DS2480 or LINK interface" in 2.7

Hi all,

sorry for not reading the older posts, there was a similar error with
ds9097u (I did not realize that that is actually a ds2480b).

Our adapter is homemade, but is probably identical to the ds9097u,
connected to a terminal server, from there going through a little pcb
that adds 5V power to the bus-line and provides a RJ45 socket.
rs232 adapter: http://www.aip.de/People/wbittner/1wire/RS232Adapter.pdf
helper pcb: http://www.aip.de/People/wbittner/1wire/Einspeisung.pdf

I tried again with 2.7 (on the old computer this time, debian/sarge )

owserver --foreground --error_level 9 --error_print 2 -p 3004 -d /dev/ttyr00
   CALL: PARSENAME path=[]
  DEBUG: main_threadid = 1075642496
  DEBUG: ServerProcessOut = 1084033968
  DEBUG: ServerProcessAccept 3004[1084033968] try lock 0
  DEBUG: ServerProcessAccept 3004[1084033968] locked 0

and the other computer  (debian/etch)

owserver --foreground --error_level 9 --error_print 2 -p 3004 -d /dev/ttyr00
   CALL: PARSENAME path=[]
CONNECT: Cannot detect DS2480 or LINK interface on /dev/ttyr00.
  DEBUG: COM_close: flush
  DEBUG: COM_close: restore
  DEBUG: COM_close: close
   CALL: PARSENAME path=[]
DEFAULT: Cannot detect DS9097 (passive) interface on /dev/ttyr00.

Re: Firmware being used on the wireless routers

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: DS2480 "Cannot detect DS2480 or LINK interface" in 2.7

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: DS2480 "Cannot detect DS2480 or LINK interface" in 2.7

> Well the first thing that stands out is the device name, ttyr00. Is that
> correct?

Yes, that's on a moxa serial port server. Very weird software, but it
somehow works (most times). As I said, with 2.6p8 no problem, and
2.7p0 works on a different machine (sarge running 2.6.8) but not on
etch running 2.6.18). I also tried a etch/2.6.22 machine, same error.
On my laptop with a physical rs232 connection (running etch w/2.6.2x)
same thing (2.7p0 fails, 2.6p8 works).

Michael

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

Re: Firmware being used on the wireless routers

On Dec 2, 2007 7:16 AM, Paul Alfille <paul.alfille <at> gmail.com> wrote:
> In general the G is backward-compatible with B.
>
> Paul Alfille
>
>
>
> On Dec 1, 2007 12:52 AM, Gregg C Levine <hansolofalcon <at> worldnet.att.net >
> wrote:
> > Hello!
> > Indeed.
> > I looked at the list of gear, and naturally the one I want to use isn't on
> > the list. Although all of their later models are on it. This tells me that
> > Wireless-B isn't on that group's things-to-do list.
> >

Hello!
Indeed. And according to the bright guys at Fluke Networks, it
certainly is backward compatible as you've stated.

Now if it actually comes down to this, I'll probably order RSN from
Amazon a LinkSYS Wireless-G router, the kind that I know all of you
are using, and do the things that are supposed to be done to enable
both OWFS support, and even seeing how custom firmware is running on
it.

But I was indeed actually looking forward to having one of the earlier
models roosting here. I suppose my next step is to rouse the gang at
Seattle Wireless and ask them about this......
--

-- 
Gregg C Levine gregg.drwho8 <at> gmail.com
"This signature was once found posting rude
 messages in English in the Moscow subway."

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

owhttpd server question

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: owhttpd server question

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Pressure sensing and One Wire sensors

Hello!
I just took possession of a pair of pressure sensors from Freescale. These
two are along the lines of the series they make for sensing air pressure,
and indeed they can be ordered with the appropriate ports. These were
selected as just the sensors instead.

Now the question: Each device returns a differential voltage depending on
the amount of pressure applied. Typically I would have a part present its
output into an Op-Amp and then into an Analog to Digital conversion device
for further processing. How would I do this step and make use of the OWFS
mechanisms? I have here a number of samples from Maxim/Dallas, including
several DS2438s and one DS2450 (currently).

--
Gregg C Levine hansolofalcon <at> worldnet.att.net
"The Force will be with you always." Obi-Wan Kenobi
  

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4