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. DEBUG: COM_close: flush DEBUG: COM_close: restore DEBUG: COM_close: close DEBUG: main_threadid = 3084216544 DEBUG: ServerProcessOut = 3084213168 DEBUG: ServerProcessAccept 3004[3084213168] try lock 0 DEBUG: ServerProcessAccept 3004[3084213168] locked 0 DEBUG: ServerProcess: break signo=2 DEBUG: ow_net.c:ServerProcess() shutdown initiated DEBUG: Shutting down 0 of 1 thread -1210754128 DEBUG: ow_net.c:ServerProcess() shutdown done DEBUG: ow_exit 0 CALL: Starting Library cleanup CALL: Closing Cache CALL: Closing input devices DEBUG: FreeIn: busmode=2 CALL: Closing outout devices CALL: Finished Library cleanup seems to be related to etch, any clues? Michael On Dec 1, 2007 1:45 PM, Michael Weber <[EMAIL PROTECTED]> wrote: > 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 > -- Dr. Michael Weber Astrophysikalisches Institut Potsdam An der Sternwarte 16 D-14482 Potsdam Tel: 0331 7499 632 Fax: 0331 7499 200 email: [EMAIL PROTECTED] ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
