Hello,
Also comparing your circuit with the one on page 25 of the DS2480B manual
http://datasheets.maxim-ic.com/en/ds/DS2480B.pdf
you have the POL pin at ground, and they have it at +VDD. Could you have
polarity reversed?
That is because the MAX232 has a inverter stage build in and negates
Tilman,
I presume your output from 12/15/2006 is still accurate:
./owhttpd -d /dev/tty0 -p 3001 --foreground -msec_read=700 --error_level=9
CALL: PARSENAME path=[]
CONNECT: Cannot detect DS2480 or LINK interface on /dev/tty0.
DEBUG: COM_close: flush
DEBUG: COM_close: restore
DEBUG:
Paul, Christian,
Thanks again for your rapid-response help.
I understand that the changes are in 2.7p2? I will install the revised
version and keep you updated!
Michael
On Dec 20, 2007 5:40 PM, Paul Alfille [EMAIL PROTECTED] wrote:
Thank you -- it was my adding the new interface entry that
On Dec 21, 2007 5:27 AM, Michael Weber [EMAIL PROTECTED] wrote:
Paul, Christian,
Thanks again for your rapid-response help.
I understand that the changes are in 2.7p2? I will install the revised
version and keep you updated!
Yes
Michael
On Dec 20, 2007 5:40 PM, Paul Alfille [EMAIL
It seems like a calloc() fails in your case... Did you run out of memory in
your box?
The only way FS_ParsedName_destroy() is called from FS_OWQ_create(), is if
calloc() returns a null-pointer...
Also... Perhaps pn-selected_filetype-ag-elements 0 for some reason?
Thread 1 (process 9294):
#0
I debugged the code before... and I found a pretty serious bug where void
*Tree[6] was defined, but it should be 7 elements in that array.
I have fixed this in the CVS, so perhaps this could result into some
overwritten memory.
/Christian
Thank you -- it was my adding the new interface entry that caused the
error.
I like your fix -- adding a terminal element to the enumerating list.
Paul Alfille
On Dec 20, 2007 9:50 AM, Christian Magnusson [EMAIL PROTECTED] wrote:
I debugged the code before... and I found a pretty serious
Hi Paul,
OK, it crashed again this morning. I attach the logfile, I guess the
problem manifests itself in the
repetition of
Dec 19 08:47:48 archive OWFS[22354]: Transaction Delay 50
Dec 19 08:47:48 archive OWFS[22354]: Transaction readin = 0
Dec 19 08:47:48 archive OWFS[22354]: Transaction
running...
/Christian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael
Weber
Sent: den 19 december 2007 11:04
To: owfs-developers@lists.sourceforge.net
Subject: Re: [Owfs-developers] DS2480 Cannot detect DS2480 or LINK
interface in 2.7
Hi Paul
Both this error log, and the longer one you sent show the problem happening
in the Parsedname_Destroy routine -- porobably a bad pointer. That gives me
a goo idea of where to look. Thanks.
Paul Alfille
Oh, and the part that you worried about, the polliong for conversion to end,
is fine.
Both this error log, and the longer one you sent show the problem happening
in the Parsedname_Destroy routine -- porobably a bad pointer. That gives me
a goo idea of where to look. Thanks.
Paul,
Thanks for looking into this. I am now running owserver (2.7p1) in the
foreground following
Christian,
Here comes the gdb backlog, hope it is of any help.
Michael
Core was generated by `/usr/bin/owserver --foreground --error_level=4
--error_print=2 -d /dev/ttyr04 -'.
Program terminated with signal 11, Segmentation fault.
#0 0xb7dd7f38 in free () from /lib/tls/libc.so.6
(gdb) thread
Not really. The bus consists of a bunch of temperature sensors, and
two modules I use to do heat regulation with some kind of PWM, with a
relay in parallel for zero and 100% heating. And one A/D module which
is hardly used.
Temperatures are read frequently (minutes), the temperature regulators
Dear Paul,
Also comparing your circuit with the one on page 25 of the DS2480B manual
http://datasheets.maxim-ic.com/en/ds/DS2480B.pdf
you have the POL pin at ground, and they have it at +VDD. Could you have
polarity reversed?
The RS232 level converter normally work inverted. Please also
Do you have any hints about what in pwserver is causing a crash? What type
of traffic?
Paul Alfille
On Dec 17, 2007 4:42 PM, Michael Weber [EMAIL PROTECTED] wrote:
Tilman,
Everything works now for me. Both with 2.7p1, also the cvs version
after Paul made the changes to the 2480 setup code.
This is one of the difficult cases of 'it works for me, but not you.'
I just tested an authentic DS9097U
I guess the first question is do you have other proof that your adapter
functions correctly?
I don't of course :-)
I setup 2 of the identical PCBs. Both of them do not work. One
of them
I just post the message again as it is displayed as attachment in the mailing
list. Hope it gets represented accurately without the attachment of the PDF
containing the schematic. The previous posting has the schematic of my dS2480B
design attached
This is one of the difficult cases
Just as a minor point, your wiring of the RJ45's is non-standard
See 1wire.org under open standards
Paul Alfille
On Dec 16, 2007 5:49 AM, Tilman Glotzner [EMAIL PROTECTED] wrote:
I just post the message again as it is displayed as attachment in the
mailing list. Hope it gets represented
On Dec 16, 2007 5:35 AM, Tilman Glotzner [EMAIL PROTECTED] wrote:
I guess the first question is do you have other proof that your adapter
functions correctly?
I don't of course :-)
There are other programs, like digitemp, that might serve as a positive
control.
Also comparing your circuit
Hello,
as Michael, I build myself an an adapter based on DS2480B that is identical for
the ds9097u except for the power supply. I am using an external power supply
(the ds9097u draws power from the serial port). Unlike Michael's design and
like the ds9097u, I am using a MAX232 to convert the
This is one of the difficult cases of it works for me, but not you.
I just tested an authentic DS9097U
I guess the first question is do you have other proof that your adapter
functions correctly?
Also I'm embarrassed to admit that msec_read is no longer implemented
(despite being in the man
Well the first thing that stands out is the device name, ttyr00. Is that
correct?
Paul Alfille
On Dec 1, 2007 10:17 AM, Michael Weber [EMAIL PROTECTED] wrote:
Hi all,
DEFAULT: Cannot detect DS9097 (passive) interface on /dev/ttyr00.
Paul Alfille
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
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,
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
25 matches
Mail list logo
