Yioryos Asprobounitis | 12 Jun 2012 08:17
Picon
Favicon

Re: Re: XO battery/performance[ Devel Digest, Vol 76, Issue 21]


>   Perhaps your comm settings are wrong? 
> 115200,n,8,1 is what they 
> should be set to.  

That did the trick (thus my change in the wiki)
James Cameron | 12 Jun 2012 08:49
Favicon

Re: Re: XO battery/performance[ Devel Digest, Vol 76, Issue 21]

On Mon, Jun 11, 2012 at 11:17:06PM -0700, Yioryos Asprobounitis wrote:
> 
> 
> > ? Perhaps your comm settings are wrong??
> > 115200,n,8,1 is what they 
> > should be set to.? 
> 
> That did the trick (thus my change in the wiki)

I think it was coincidence.  Please try without it.

--

-- 
James Cameron
http://quozl.linux.org.au/
Yioryos Asprobounitis | 12 Jun 2012 18:15
Picon
Favicon

Re: Re: XO battery/performance[ Devel Digest, Vol 76, Issue 21]

> > > ? Perhaps your comm settings are wrong??
> > > 115200,n,8,1 is what they 
> > > should be set to.? 
> > 
> > That did the trick (thus my change in the wiki)
> 
> I think it was coincidence.  Please try without it.

At least in my setting ie XO-1.75 embedded keyboard model with the "problem" battery and the adapter
connected to the UART 4 port and XO-1.75 HS keyboard running screen, n,8,1 makes all the difference.
Someone else may want to try this with XO-1.75s (os13)

Here is the log when I was trying with/without 

3805384:SDI: Host not ready

3805838: Vb: 6616  I: -454  W: -3003  SOC:87 ACR:-20656 PL:1 L:0 sleep: 0

3806843: Vb: 6634  I: -539  W: -3575  SOC:87 ACR:-20656 PL:1 L:0 sleep: 0

3807004:SDI: Host ready

event mask was 0xffff, is now
0xffff

ÆãąùçîÉåáãáÄÀáÏääìÈÍæŽÎ‡ÂÃÄ%ùÎÂâÆäàùÂàíÀùÃÂãÄÀùÂâãÄàùÂàáÆàùÂÂÃäÅù‚‡€…ùÎâÃÈàùÃÂäÅùîçã‚âƒäàùÂâãæÁùâ‚€…ùâÂäâÂâäâù††€…ù†ãÄùÃâãÄâùâÂÁÄÀùâÃÈàùâ†ÀùââÄàùâàáÄàùÆÂãàùÂÂäàÂâáÄàùÃâãÄÀùÃÂáæâùÂâƒäâùâÂãÄ
àùâãäàù‡ÂÃÄÀùâÂãÄÀùÂàÃÄÀù‚‚†ÀÀùÂàãæÀùâàãÀàùâÂÂäâùÃâãäÀùÂâãæÁùâÂÄÀùâÂÂä
ùÂâ†ÄÅù‡ÂŠÀùÂàþĄùÃÂäàù‚ÂÄÀùÂâÄàùâàÂäÀùÃàÂäâùÂâáäàù‚ÂÂÄàùâÂãÀùÇáå…ùââãæâùâÂÁäâùÂàÀÁù4030807:
Vb: 6584  I: -404  W: -2659  SOC:87 ACR:-20708 PL:1 L:0 sleep: 0

(Continue reading)

James Cameron | 13 Jun 2012 00:59
Favicon

Re: Re: XO battery/performance[ Devel Digest, Vol 76, Issue 21]

On Tue, Jun 12, 2012 at 09:15:48AM -0700, Yioryos Asprobounitis wrote:
> > > > ? Perhaps your comm settings are wrong??
> > > > 115200,n,8,1 is what they 
> > > > should be set to.? 
> > > 
> > > That did the trick (thus my change in the wiki)
> > 
> > I think it was coincidence.?? Please try without it.
> 
> At least in my setting ie XO-1.75 embedded keyboard model with the
> "problem" battery and the adapter connected to the UART 4 port and
> XO-1.75 HS keyboard running screen, n,8,1 makes all the difference.

Thanks for testing again.  Richard was using a convention that screen
does not use.  The reason I thought it was coincidence was that the
screen program does not behave any differently for me with or without
,n,8,1 and the source code of screen confirms there should be no
difference:

http://dev.laptop.org/~quozl/z/1SeZgA.txt

This is the function that processes the baud rate option.  It is the
only place in the code where serial port configuration is set.  There
is nothing in there that should notice the presence or absence of
,n,8,1

That it works differently for you, reproducibly, means there is some
other effect happening, and we should try to get to the bottom of it.
Unexplained effects can lead to problems later on.

(Continue reading)

Yioryos Asprobounitis | 13 Jun 2012 08:07
Picon
Favicon

Re: Re: XO battery/performance[ Devel Digest, Vol 76, Issue 21]


> Could you please do another test, to verify that screen is
> not
> configuring the serial port any differently with or without
> ,n,8,1.
> You don't need to connect the two laptops together, just use
> the one
> you use as the serial terminal.  The test uses the stty
> program to
> display the serial port configuration.

Here you are.
However I need to have the the 2 XOs connected because without it /dev/ttyUSB0 does not exist and if I connect
just the adapter then stty fails with resource busy

$ screen /dev/ttyUSB0 115200
********* Today the output was readable! :-? ********
[screen is terminating]
[olpc <at> xo-74-39-1a ~]$ stty --all < /dev/ttyUSB0
speed 115200 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^H; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 100; time = 2;
-parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts
-ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl ixon -ixoff
-iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
-isig -icanon iexten -echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

(Continue reading)

James Cameron | 13 Jun 2012 08:25
Favicon

Re: Re: XO battery/performance[ Devel Digest, Vol 76, Issue 21]

On Tue, Jun 12, 2012 at 11:07:44PM -0700, Yioryos Asprobounitis wrote:
> James wrote:
> > Could you please do another test, to verify that screen is not
> > configuring the serial port any differently with or without
> > ,n,8,1.  You don't need to connect the two laptops together, just
> > use the one you use as the serial terminal.? The test uses the
> > stty program to display the serial port configuration.
> 
> Here you are.

Thanks.  Your results prove the ,n,8,1 is ineffective, and it must
have been line noise that caused your unreadable output last time.

> However I need to have the the 2 XOs connected because without it
> /dev/ttyUSB0 does not exist and if I connect just the adapter then
> stty fails with resource busy

stty will fail with device or resource busy if screen is running at
the time that stty is run.  Or, modemmanager may have been trying to
send AT commands to the serial adapter to see if it is a modem.  This
is one reason why I don't like using our OLPC Fedora builds as serial
terminals!

http://wiki.laptop.org/go/Serial_adapters#Linux has a note about
modemmanager.

So it probably wasn't connecting the two laptops that resolved the
device or resource busy error for you.  It was the passing of time,
enough to let modemmanager finish probing.

(Continue reading)

Yioryos Asprobounitis | 13 Jun 2012 09:16
Picon
Favicon

Re: Re: XO battery/performance[ Devel Digest, Vol 76, Issue 21]


> 
> You can reduce the chance of contact noise derailing the
> transmission
> by connecting the two laptops in a specific order:
> 

or maybe adding ,n,8,1 in the command ?...

(I still think is a good idea to add it in the wiki. Even with the notion that although not necessary may reduce
unexpected results stemming from line noise or race with the modem manager ;)
James Cameron | 13 Jun 2012 09:56
Favicon

Re: Re: XO battery/performance[ Devel Digest, Vol 76, Issue 21]

On Wed, Jun 13, 2012 at 12:16:13AM -0700, Yioryos Asprobounitis wrote:
> 
> > 
> > You can reduce the chance of contact noise derailing the
> > transmission
> > by connecting the two laptops in a specific order:
> > 
> 
> or maybe adding ,n,8,1 in the command ?...

No, that will make no difference.

> (I still think is a good idea to add it in the wiki. Even with the
> notion that although not necessary may reduce unexpected results
> stemming from line noise or race with the modem manager ;)

Heh.

,n,8,1 should not be added to the Wiki for the usage of the screen
program, because it does nothing, and I would not have the Wiki
deceive anybody.

The line noise depends on the power supplies being used, and the
amount of isolation, and the way in which the contacts are mated
... so many variables, if we documented them all we'd have a tutorial
on using serial ports ... in an age where they are rarely used by most
people.

--

-- 
James Cameron
(Continue reading)

Yioryos Asprobounitis | 12 Jun 2012 18:26
Picon
Favicon

Re: XO battery/performance [Devel Digest, Vol 76, Issue 21]

> From: "Richard A. Smith" <richard <at> laptop.org>
> To: devel <at> lists.laptop.org
> Subject: Re: XO battery/performance [Devel Digest, Vol 76,
> Issue 4]
> Message-ID: <4FD5E76C.3010405 <at> laptop.org>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> On 06/10/2012 01:07 AM, Yioryos Asprobounitis wrote:
> 
> >
> > Took some time and a lot of juggling and ended up to a
> lot of
> > questionmarks in black diamonds so I do not really know
> if I did it
> > right or wrong, but here is the screen log just the
> same.
> 
> You may or may not have done anything wrong but the output
> is not valid. 
>   Perhaps your comm settings are wrong? 
> 115200,n,8,1 is what they 
> should be set to.  Its exactly the same as if you were
> connected to the 
> OFW or Linux output.
> 

OK Attached are the screenlogs from the serial output

screenlog.charging is yesterdays log whith half full to fully charged battery 
screenlog.23h.brief is the b3-b0 session 23h later 
(Continue reading)

Richard A. Smith | 16 Jun 2012 21:07
Favicon

Re: XO battery/performance [Devel Digest, Vol 76, Issue 21]

On 06/12/2012 12:26 PM, Yioryos Asprobounitis wrote:

> OK Attached are the screenlogs from the serial output
>
> screenlog.charging is yesterdays log whith half full to fully charged battery

2339275:LDACR Update request ACR:-19791 LDACR:-19792
2339471:GC_LDACR=-19792 SOC = 58
2470692:LDACR Update request ACR:-19722 LDACR:-19792
2470857:GC_LDACR=-19792 SOC = 95
2477403:LDACR Update request ACR:-19719 LDACR:-19720
2477565:GC_LDACR=-19720 SOC = 96
2665019:  LCS:8 CFC:4 CHG=1 Vb:7395 Vavg:0x5eb3
Bat Full

Your battery jumped from 58% to Full while only receiving around 30mAh 
of charge.  So it has issues.

For an older battery I would suspect charge balance symptom but your 
serial number starts with 008 which is beyond the lot of problem 
batteries and you have indicated you already ran bat-recover.

So either your battery was not really at 58% or its suffered a lot of 
capacity loss.

The next step would be to do a full discharge/recharge/discharge cycle 
while running olpc-pwr-log (stop powerd first) to measure the existing 
capacity.

A quick summary of the procedure:
(Continue reading)


Gmane