LCDproc development and user support list

Text archives Help


e: [Lcdproc] Crystalfontz 635 usb lcd noise


Chronological Thread 
  • From: stewartputnam AT comcast.net (Stewart W. Putnam)
  • Subject: e: [Lcdproc] Crystalfontz 635 usb lcd noise
  • Date: Fri Mar 31 15:42:01 2006

Andrew Foss wrote:

> Great, could just slow us down enough to overcome, whatever buffer
> limits are along the way and probably 250ms is way higher than you
> need:-)
>
> Now to see what to submit to the project, as a bug or how to fix?
>
> lcdproc folks any suggestions?
>
> andrew
>
I've modified things into a significantly different cf63x driver.
Sending as a patch would be a much larger file.

My main interest was working with temperatures and fans; enabling that
under linux.

I created a packet que so that it sends ( and resends if needed ) one
packet, and does not send the next until the module sends an
acknowledgement receipt for the one at the head of the que.

I put some LOTS of timing & measuring into it:

> pack count min t max t avg dump resent
> 32402 0.017347 0.069677 0.022924 0 0
> Set_LCD_Contents_Line_One
> 26945 0.017320 0.083974 0.022926 0 0
> Set_LCD_Contents_Line_Two
> 315874 0.000074 0.151029 0.016695 0 0
> Set_LCD_Special_Character_Data
> 580 0.005963 0.029548 0.012339 0 0
> Set_Up_Fan_Reporting
> 2825 0.008965 0.049142 0.014337 0 0
> Set_Fan_Power


that is says the maximim time for a packet to be sent, processed, and
acknowledged was 0.151029 seconds. Thats for ~ 380,000 packets over
39514 seconds. ( None needed to be resent & none were given up on. )

For myself I've written a big complex driver that reads /proc and output
from the lm-sensors package and logs all that integrated ...

uptime,load,top1,%,top2,%,xawtv%,XFree86%,LCDd%,it87:CPU Temp,it87:M/B
Temp,inflow:ml/s,fan4:pwr,fan4:RPM,cool1,cool2,cool3,air1,air2,air3,air4,air5,air6,air7,air8,...warm1,...warm2,...warm3,watts


34,33.9,init,9.73,klogd,0.29,0.00,0.00,0.00,13,26,13.396876,000,0000,18.5000,18.6250,18.6875,18.4375,18.9375,19.4375,20.4375,23.3750,19.6875,19.4375,18.5000,19.5000,19.5000,19.6250,52.75


50,29.5,gdmlogin,3.58,events/0,0.00,0.00,0.54,0.00,13,27,13.665658,000,0000,18.6250,18.7500,18.8125,18.6250,19.1250,19.6250,20.3125,23.5625,19.8750,19.6875,18.6875,19.5625,19.6250,19.8125,53.81


...
39514,6.4,bonobo-activati,0.06,ksoftirqd/0,0.00,-1558.84,-2175.66,0.00,22,44,13.648685,080,0002,26.1875,26.3750,26.3750,24.5625,25.9375,26.5000,28.2500,31.1875,27.7500,29.6250,27.8125,27.6250,27.6875,27.8125,80.02



That is uptime in seconds, % cpu load, top 2 cpu pigs by name and %
load, xawtv + XFree86 + LCDd load values regardless of wheather they are
in the top 2 by load or not, lm sensors data, then fan / flowmeter
datas, then 14 of the CF63x temperature sensors, then one derrived value
"watts" total watts of waste heat captured by my water cooler ...

Anyone particularly interested in this use of the CF LCDs can download
this driver from Crystalfontz LCD Forum - please verify that lcdproc is
GPL <http://www.crystalfontz.com/forum/showthread.php?s=&threadid=3019>
, http://www.crystalfontz.com/forum/showthread.php?s=&threadid=3019

I've attatched here a stripped down version. It lacks anything to do
with lm-sensors or /proc reading or creating lcd screens about my
particular computer.

The basics of temperature recarding and fan management I hope can be
read from the included LCDd.conf-lines file.

For the driver to log to a /var/log/CF63x file, you need to create that
file and set its' permissions by hand.



  • e: [Lcdproc] Crystalfontz 635 usb lcd noise, Stewart W. Putnam, 03/31/2006

Archive powered by MHonArc 2.6.18.

Top of page