From npavel at ituner.com Wed Oct 1 18:08:58 2008 From: npavel at ituner.com (Nicu Pavel) Date: Thu, 02 Oct 2008 03:08:58 +0300 Subject: [Lcdproc] [PATCH] Add support for 20x4 picoLCD In-Reply-To: <48E21185.4060409@compusmiths.com> References: <48E21185.4060409@compusmiths.com> Message-ID: <1222906138.6477.14.camel@sanctuar> Hi, I attached a patch vs current cvs lcdproc that adds support for picoLCD 20x4 from mini-box.com: http://www.mini-box.com/PicoLCD-4X20-Sideshow The code is integrated in the same driver as our previous 20x2 lcd in picolcd.c I changed the connect/claim code a little with something that works on Fedora and Ubuntu which is similar to what Ethan has observed. The detection is made based on product/vendor ids (no extra configuration needed) A new structure has been added which list each device capabilities (which prepares for our next 256x64 LCD) Added Brightness parameter as 20x4 lcd can set the brightness to different values. Added functions for write/set custom character for both devices which are selected in device capabilities structure. Added a usb_clear_halt on IR interrupt read as 20x4 lcd doesn't seem to clear it's endpoint status after a read(this is only needed for IR). Let me know what needs to be changed so it can be merged in current cvs. Thanks, Nicu Pavel -------------- next part -------------- A non-text attachment was scrubbed... Name: patch-lcdproc-cvs-picolcd.txt Type: text/x-patch Size: 24130 bytes Desc: not available URL: From epooch at cox.net Fri Oct 3 00:09:52 2008 From: epooch at cox.net (Eric Pooch) Date: Thu, 2 Oct 2008 23:09:52 -0700 Subject: [Lcdproc] USS720 Belkin USB Parallel printer adapter driver Message-ID: <9B017728-86DE-4FE5-808D-6E11401D92DE@cox.net> Here is a driver and patch file for Belkin F5U002 USB Parallel Printer Adapters that use the Lucent USS720 USB-to-IEE 1284 Bridge chip. Documentation is included. I had considered rewriting port.h so that any drivers and LCDs using the parallel port could use USB instead, but this was much easier. I had some trouble testing the acinclude.m4 changes due to the autogen.sh script creating a configuration script that was so different from the tarball distributed one that I could not get LCDproc to compile with libusb. any help on that issue would be appreciated. Thanks --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: hd44780-USS720_driver.tgz Type: application/octet-stream Size: 5077 bytes Desc: not available URL: From w_smith at compusmiths.com Fri Oct 3 04:28:32 2008 From: w_smith at compusmiths.com (William P.N. Smith) Date: Fri, 03 Oct 2008 06:28:32 -0400 Subject: [Lcdproc] [Fwd: [support #48412]: PicoLCD on Linux?] In-Reply-To: <812fb8370809300548x14dc0d2o25aa03ecc2819be5@mail.gmail.com> References: <48E21185.4060409@compusmiths.com> <812fb8370809300548x14dc0d2o25aa03ecc2819be5@mail.gmail.com> Message-ID: <48E5F3D0.6020304@compusmiths.com> Fred Welland wrote: > And to the guy that was gonna try vista -- lemme us know the results -- > I don't even have a vista machine Well, it works, and uses the keys for running little menus, but it's pretty frustrating (which I guess is the Vista paradigm). > (and the keys have a back light on/in them???) Still not clear, but the box definitely has backlight level control. From w_smith at compusmiths.com Fri Oct 3 04:30:40 2008 From: w_smith at compusmiths.com (William P.N. Smith) Date: Fri, 03 Oct 2008 06:30:40 -0400 Subject: [Lcdproc] [Fwd: [support #48412]: PicoLCD on Linux?] In-Reply-To: <812fb8370809300548x14dc0d2o25aa03ecc2819be5@mail.gmail.com> References: <48E21185.4060409@compusmiths.com> <812fb8370809300548x14dc0d2o25aa03ecc2819be5@mail.gmail.com> Message-ID: <48E5F450.5020801@compusmiths.com> [I goofed, and sent this to Fred instead of the list] Fred Welland wrote: > Well that is a bit promising... I'll let you know. Maybe I shouldn't read too much into their shipping a product with broken drivers, or maybe they assumed that everyone buying it would be installing it on Vista, but it's a bit disconcerting. > And to the guy that was gonna try vista -- lemme us know the results -- > I don't even have a vista machine That was me, we've got a Vista machine so we can support clients, but it's as frustrating as you've heard. However, it ought to be fairly easy to plug in the PicoLCD and see if it works. > (and the keys have a back light on/in them???) Well, that's the part that's hard to tell. The configuration file has settings for the key backlights, and in fact has settings for the backlights for the individual keys, so you can indicate which keys are active. Since we know that the hardware and software are (ahem) out of sync, maybe that device has that hardware feature, and maybe it doesn't. There are two separate (and probably very different) devices at http://www.mini-box.com/picoLCD and I've got the 4x20-Sideshow version... More News As It Happens From w_smith at compusmiths.com Fri Oct 3 04:35:16 2008 From: w_smith at compusmiths.com (William P.N. Smith) Date: Fri, 03 Oct 2008 06:35:16 -0400 Subject: [Lcdproc] MiniBox USB picoLCD USB new drivers released Message-ID: <48E5F564.4030302@compusmiths.com> http://picolcd.com/drivers/ Including XP, that's nice! I'll give them a try today in my copious spare time. 8*) From w_smith at compusmiths.com Fri Oct 3 06:26:31 2008 From: w_smith at compusmiths.com (William P.N. Smith) Date: Fri, 03 Oct 2008 08:26:31 -0400 Subject: [Lcdproc] MiniBox USB picoLCD USB new drivers released In-Reply-To: <48E5F564.4030302@compusmiths.com> References: <48E5F564.4030302@compusmiths.com> Message-ID: <48E60F77.80505@compusmiths.com> William P.N. Smith wrote: > http://picolcd.com/drivers/ > > Including XP, that's nice! I'll give them a try today in my copious > spare time. 8*) Well, there's good news and bad news about the drivers at http://picolcd.com/drivers/ ============== The XP drivers (V01.17) work, and show some interesting capabilities of the device. You can generate 8 of your own 5x8 font characters and upload them to the device (display with \0 thru \7). The font fiddle screen needs a few more features (download current character, clear-all, set-all would be nice), but it's functional and you can make it do what you want. Pressing the hardware buttons make the GUI buttons flash. Sending IR commands at it makes the IR block flash in the UI. There are buttons for controlling the LEDs behind each key, but they don't do anything. Still don't know if this device is supposed to have that feature (or maybe mine is broken?) Lots of fine granular control over display, cursor, and shift functions, but some weird interactions. Not critical, but turning the cursor off probably shouldn't turn the display off... Nice looking editor for the splash screen, so you can change the power-up default. Firmware programmer screen looks nice, though using it without proper documentation and such might brick the device, so a bit scary, so I'm not going to play. Pressing the "Switch Mode" button requires a WinXP reboot to see the device again. All in all, a good first release. Shows off the capabilities of the device, though you can't actually _do_ anything with it... ================ The 'new' Linux binary drivers have the same filename and release (0.5.2) as the previous ones, but are smaller and don't include startpicolcd.sh (for instance), so they are either incomplete or something you are supposed to layer over the previous version (which is no longer at the URL above). It has a couple of new Perl modules, that look really nice: iosock.pl shows ping results from a list of hosts. tail.pl shows the tail of a file, with control over the display using the keys. [Those two programs by themselves make me want to buy a couple more of these boxes!] I really like the Linux client/server model, so I can write Perl code (or even use Telnet!) on any machine on the LAN (or Internet) and send ascii commands to the device to make it do stuff. Anyway, typical Open Source. Really neat, great new features, incomplete, unusable as-is, requires a lot of work to get running and discover new bugs. 8*) I'll report functionality if/when I get the time to fiddle... ============== No apparent changes to the Vista drivers. [Note, doesn't work on Vista Home due to lack of SideShow support in Home]. They work, they display various things, the UI is cumbersome and confusing (yeah, it's Vista), and it's not clear which SideShow/SideBar(?) apps support SideShow, so you need to fiddle a lot till you get something to work. Facebook app is kinda neat, stock ticker seems to work, lots of others I didn't bother to download and try. More News As It Happens. From andy at siliconlandmark.com Fri Oct 3 09:05:53 2008 From: andy at siliconlandmark.com (Andre Guibert de Bruet) Date: Fri, 3 Oct 2008 11:05:53 -0400 Subject: [Lcdproc] MiniBox USB picoLCD USB new drivers released In-Reply-To: <48E60F77.80505@compusmiths.com> References: <48E5F564.4030302@compusmiths.com> <48E60F77.80505@compusmiths.com> Message-ID: <84A5B8CD-A735-4BCC-9AEA-C853157DFDDB@siliconlandmark.com> On Oct 3, 2008, at 8:26 AM, William P.N. Smith wrote: > There are buttons for controlling the LEDs behind each key, but they > don't do anything. Still don't know if this device is supposed to > have that feature (or maybe mine is broken?) I picked up a couple of the 4x20's to fiddle with and I can't get either of them to perform this magic trick. > Lots of fine granular control over display, cursor, and shift > functions, but some weird interactions. Not critical, but turning > the cursor off probably shouldn't turn the display off... I've seen the very same thing. These commands are a nice demo of the device's capabilities, though. > Nice looking editor for the splash screen, so you can change the > power-up default. I'm happy I got rid of the annoying power-up default screen the device ships with! Now, if I could only get the device working on FreeBSD and OSX... :) Andy /* Andre Guibert de Bruet * 436f 6465 2070 6f65 742e 2042 6974 206a */ /* Managing Partner * 6f63 6b65 792e 2053 7973 4164 6d69 6e2e */ /* GSM: +1 734 846 8758 * 2055 4e49 5820 736c 6575 7468 2e00 0000 */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ From andy at siliconlandmark.com Fri Oct 3 09:23:32 2008 From: andy at siliconlandmark.com (Andre Guibert de Bruet) Date: Fri, 3 Oct 2008 11:23:32 -0400 Subject: [Lcdproc] [PATCH] Add support for 20x4 picoLCD In-Reply-To: <1222906138.6477.14.camel@sanctuar> References: <48E21185.4060409@compusmiths.com> <1222906138.6477.14.camel@sanctuar> Message-ID: <6150C95B-FF9F-40D8-8E35-8123C7B32654@siliconlandmark.com> On Oct 1, 2008, at 8:08 PM, Nicu Pavel wrote: > I attached a patch vs current cvs lcdproc that adds support for > picoLCD > 20x4 from mini-box.com: > http://www.mini-box.com/PicoLCD-4X20-Sideshow ... > > Let me know what needs to be changed so it can be merged in current > cvs. Thanks for your hard work on this driver! While trying to compile the picolcd driver with your changeset, I am seeing the following: picolcd.c: In function ?picoLCD_init?: picolcd.c:217: error: ?driver? undeclared (first use in this function) picolcd.c:217: error: (Each undeclared identifier is reported only once picolcd.c:217: error: for each function it appears in.) The following patch against your changeset fixes compilation on my system: --- picolcd.c.orig 2008-10-03 11:20:39.000000000 -0400 +++ picolcd.c 2008-10-03 11:20:52.000000000 -0400 @@ -214,6 +214,7 @@ } #endif if (usb_claim_interface(p->lcd, 0) < 0) { + char driver[1024]; report(RPT_ERR, "Cannot claim interface !", driver); usb_close(p->lcd); return -1; Cheers, Andy /* Andre Guibert de Bruet * 436f 6465 2070 6f65 742e 2042 6974 206a */ /* Managing Partner * 6f63 6b65 792e 2053 7973 4164 6d69 6e2e */ /* GSM: +1 734 846 8758 * 2055 4e49 5820 736c 6575 7468 2e00 0000 */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ From TELarson at west.com Tue Oct 7 14:53:35 2008 From: TELarson at west.com (Larson, Timothy E.) Date: Tue, 7 Oct 2008 15:53:35 -0500 Subject: [Lcdproc] solaris Message-ID: The lcdexec, lcdproc, and lcdvc clients won't build on Solaris because they use a daemon(int,int) call. Any thoughts on how these could be written more portably? Thanks, Tim -- Tim Larson AMT2 Unix Systems Administrator InterCall, a division of West Corporation Eschew obfuscation! -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9455 bytes Desc: not available URL: From peter at adpm.de Wed Oct 8 10:52:17 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 8 Oct 2008 18:52:17 +0200 Subject: [Lcdproc] [PATCH] Add support for 20x4 picoLCD In-Reply-To: <1222906138.6477.14.camel@sanctuar> References: <48E21185.4060409@compusmiths.com> <1222906138.6477.14.camel@sanctuar> Message-ID: <200810081852.18232.peter@adpm.de> Hi Nicu, On Thursday, 2. October 2008, Nicu Pavel wrote: > I attached a patch vs current cvs lcdproc that adds support for picoLCD > 20x4 from mini-box.com: > http://www.mini-box.com/PicoLCD-4X20-Sideshow > > The code is integrated in the same driver as our previous 20x2 lcd in > picolcd.c > I changed the connect/claim code a little with something that works on > Fedora and Ubuntu which is similar to what Ethan has observed. The > detection is made based on product/vendor ids (no extra configuration > needed) > A new structure has been added which list each device capabilities > (which prepares for our next 256x64 LCD) > Added Brightness parameter as 20x4 lcd can set the brightness to > different values. > Added functions for write/set custom character for both devices which > are selected in device capabilities structure. > Added a usb_clear_halt on IR interrupt read as 20x4 lcd doesn't seem to > clear it's endpoint status after a read(this is only needed for IR). > > Let me know what needs to be changed so it can be merged in current cvs. I committed your patch to CVS with a few changes, and also updated the documentation a bit. Plase test and report feedback. Please also have a look at the documentation. I am sure it can be extended. One thing I am not so keen on is the treatment of Backlight and Brightness. Here, I'd prefer a solution that works like the other drivers using configuration options Brightness and OffBrightness. The former is for state==BRIGHNESS_ON in get/set_brightness(), the later for state==BRIGHTNESS_OFF. Would you mind to have a look at the CFontzPacket or hd44780 driver and see how they handle it. Treating Brightness and OffBrightness this way allows setting the brightness dynamically using a server menu (provided the get_brightness() function is implemented) Thanks for supporting LCDproc Peter -- Peter Marschall peter at adpm.de From peter at adpm.de Wed Oct 8 10:57:07 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 8 Oct 2008 18:57:07 +0200 Subject: [Lcdproc] [PATCH] Add support for 20x4 picoLCD In-Reply-To: <6150C95B-FF9F-40D8-8E35-8123C7B32654@siliconlandmark.com> References: <48E21185.4060409@compusmiths.com> <1222906138.6477.14.camel@sanctuar> <6150C95B-FF9F-40D8-8E35-8123C7B32654@siliconlandmark.com> Message-ID: <200810081857.07453.peter@adpm.de> Hi, On Friday, 3. October 2008, Andre Guibert de Bruet wrote: > picolcd.c: In function ?picoLCD_init?: > picolcd.c:217: error: ?driver? undeclared (first use in this function) > picolcd.c:217: error: (Each undeclared identifier is reported only once > picolcd.c:217: error: for each function it appears in.) This should be fixed with today's commit of the updated picolcd driver to CVS (although a bit different that your solution ;-) Please try tonight's / tomorrow's tar ball. Thanks for reporting the issue Peter -- Peter Marschall peter at adpm.de From peter at adpm.de Wed Oct 8 11:01:58 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 8 Oct 2008 19:01:58 +0200 Subject: [Lcdproc] serialPOS update patch In-Reply-To: <188B7212-97B5-457A-9609-CCCD5F2E074B@cox.net> References: <188B7212-97B5-457A-9609-CCCD5F2E074B@cox.net> Message-ID: <200810081901.58400.peter@adpm.de> Hi, On Sunday, 28. September 2008, Eric Pooch wrote: > This patch fixes a few bugs when using bignum, cleans up some code, > and should add functionality for Epson ESC/POS and Logic Controls POS > displays. > --Eric Committed to CVS Thanks for supporting LCDproc Peter -- Peter Marschall peter at adpm.de From peter at adpm.de Wed Oct 8 13:04:26 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 8 Oct 2008 21:04:26 +0200 Subject: [Lcdproc] LCDProc on OS X 10.5 In-Reply-To: <2EBDC194-BDB4-44C1-9D43-B90695A8567C@cox.net> References: <2EBDC194-BDB4-44C1-9D43-B90695A8567C@cox.net> Message-ID: <200810082104.26490.peter@adpm.de> Hi, On Saturday, 27. September 2008, Eric Pooch wrote: > Sorry, I have been out of the loop for a while. Happened to me too ;-) > include kvm.h was erroneously left in the machine_Darwin.c after I > changed the way memory information was obtained. I have removed the > include and tested on earlier versions of mac os x with no problems. > It really is not needed. Patch file enclosed. Committed to CVS Thank you for your continuing support of LCDproc Peter -- Peter Marschall peter at adpm.de From epooch at cox.net Wed Oct 8 13:39:06 2008 From: epooch at cox.net (epooch at cox.net) Date: Wed, 8 Oct 2008 12:39:06 -0700 Subject: [Lcdproc] USS720 Belkin USB Parallel printer adapter driver Message-ID: <20081008153906.M8AWG.829672.imail@fed1rmwml31> I think I accidently only sent this update to myself: > Fixes a potential bug by now allowing Set Mode to continue even after > a non fatal error. > > --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: hd44780-USS720_driver.tgz Type: application/octet-stream Size: 5058 bytes Desc: not available URL: -------------- next part -------------- On Oct 2, 2008, at 11:09 PM, Eric Pooch wrote: > Here is a driver and patch file for Belkin F5U002 USB Parallel > Printer Adapters that use the Lucent USS720 USB-to-IEE 1284 Bridge > chip. Documentation is included. I had considered rewriting > port.h so that any drivers and LCDs using the parallel port could > use USB instead, but this was much easier. > > I had some trouble testing the acinclude.m4 changes due to the > autogen.sh script creating a configuration script that was so > different from the tarball distributed one that I could not get > LCDproc to compile with libusb. any help on that issue would be > appreciated. > Thanks > --Eric > > > USS720_driver.tgz>_______________________________________________ > LCDproc mailing list > LCDproc at lists.omnipotent.net > http://lists.omnipotent.net/mailman/listinfo/lcdproc From peter at adpm.de Wed Oct 8 15:16:21 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 8 Oct 2008 23:16:21 +0200 Subject: [Lcdproc] USS720 Belkin USB Parallel printer adapter driver In-Reply-To: <9B017728-86DE-4FE5-808D-6E11401D92DE@cox.net> References: <9B017728-86DE-4FE5-808D-6E11401D92DE@cox.net> Message-ID: <200810082316.22078.peter@adpm.de> Hi, On Friday, 3. October 2008, Eric Pooch wrote: > Here is a driver and patch file for Belkin F5U002 USB Parallel > Printer Adapters that use the Lucent USS720 USB-to-IEE 1284 Bridge > chip. Documentation is included. I had considered rewriting port.h > so that any drivers and LCDs using the parallel port could use USB > instead, but this was much easier. Committed to CVS with a few additions (server/drivers/Makfile.am, docs/LCDd8.in, CREDITS) > I had some trouble testing the acinclude.m4 changes due to the > autogen.sh script creating a configuration script that was so > different from the tarball distributed one that I could not get > LCDproc to compile with libusb. any help on that issue would be > appreciated. What versions of the auto* and pkg-config tools do you have ? It works on Linux with: - autoconf 2.61. - automake 1.9.6 - pkg-config 0.22 But it also worked with other version of these tools. Thanks for supporting LCDproc Peter -- Peter Marschall peter at adpm.de From jason at jasonantman.com Wed Oct 8 21:42:14 2008 From: jason at jasonantman.com (Jason Antman) Date: Wed, 08 Oct 2008 23:42:14 -0400 Subject: [Lcdproc] CrystalFontz CF635, LEDs, lcdexec Message-ID: <48ED7D96.4090401@jasonantman.com> Hi, I'm just giving LCDproc my first try. I'm using a CF635 to control 4 USB relays with a dedicated headless system. For starters, I'm using lcdexec. I have 2 questions which I haven't been able to find answers to online: 1) When I start lcdexec (only client running) it just updates the 'Clients' number on the LCDproc Server screen, and I have to use the menu to navigate to LCDexec. Once I make a choice, the menu from LCDexec just goes away. Is there any way to get the lcdexec menu to show up right away, and stay there? 2) Since there's no real way to update the lcdexec menus on-the-fly, I was hoping to use the four GPIO LEDs on the CF635 to show the status of the four relays. Firstly, does lcdproc support GPIO at all? Secondly, if so, is there any way to get lcdexec to update them? I have a Python class for the CF635, and am thinking that I may have to use that, though i never implemented button listeners and would have to do that... Thanks, Jason From swannonline at googlemail.com Thu Oct 9 05:18:32 2008 From: swannonline at googlemail.com (Steven Swann) Date: Thu, 9 Oct 2008 12:18:32 +0100 Subject: [Lcdproc] Sending commands to LCD Message-ID: <268F835F-632D-4C40-B2AF-9831D2CF308B@googlemail.com> Hello All, I hope I'm in the right place; I am currently developing some LCDd clients using ruby. I have a Noritake VFD display but I'm having to use the HD44780 driver as the NortakeVFD just outputs cryptic characters on the VFD as does the serialVFD driver. Due to this I am unable to change the brightness settings of the display. What I'm looking for is a way of sending characters to the display as commands, my serial interface requires that I send the following characters(hex) to change the brightness: 0xFE gets interface ready for command; 0x30 function set command - required by the VFD implying that the next command will be a brightness setting; 0x03..00 Set brightness, 00 = bright, 03 = dark I could incorporate this into the AVR controlling the VFD as a character string escape sequence, such as *&0 ... *&3 just like the 0xFE, but I'm hoping there is some other way I've tried incorporating this into the text of a string widget but it never works. is there a simpler way? Hope you can help... Regards, Steven From TELarson at west.com Thu Oct 9 10:32:24 2008 From: TELarson at west.com (Larson, Timothy E.) Date: Thu, 9 Oct 2008 11:32:24 -0500 Subject: [Lcdproc] option or target Message-ID: Is there a configure option or a make target or something to specify building only the server or only the clients? I've looked but don't see one, but I could be missing something. Thanks, Tim -- Tim Larson AMT2 Unix Systems Administrator InterCall, a division of West Corporation Eschew obfuscation! -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9455 bytes Desc: not available URL: From peter at adpm.de Thu Oct 9 13:47:45 2008 From: peter at adpm.de (Peter Marschall) Date: Thu, 9 Oct 2008 21:47:45 +0200 Subject: [Lcdproc] USS720 Belkin USB Parallel printer adapter driver In-Reply-To: <20081008153906.M8AWG.829672.imail@fed1rmwml31> References: <20081008153906.M8AWG.829672.imail@fed1rmwml31> Message-ID: <200810092147.46118.peter@adpm.de> Hi Eric, On Wednesday, 8. October 2008, epooch at cox.net wrote: > I think I accidently only sent this update to myself: > > Fixes a potential bug by now allowing Set Mode to continue even after > > a non fatal error. Thanks for the fix. committed to CVS. Regards PEter -- Peter Marschall peter at adpm.de From peter at adpm.de Fri Oct 10 04:14:50 2008 From: peter at adpm.de (Peter Marschall) Date: Fri, 10 Oct 2008 12:14:50 +0200 Subject: [Lcdproc] option or target In-Reply-To: References: Message-ID: <200810101214.50397.peter@adpm.de> Hi, On Thursday, 9. October 2008, Larson, Timothy E. wrote: > Is there a configure option or a make target or something to specify > building only the server or only the clients? I've looked but don't see > one, but I could be missing something. Up to a few minutes ago, there wasn't, but now there is. I have committed a change to CVS that adds a few Makefile targets: * clients * server * install-clients * install-server It is available on CVS now and will be in tonight's tar ball. Regads Peter -- Peter Marschall peter at adpm.de From peter at adpm.de Fri Oct 10 04:36:06 2008 From: peter at adpm.de (Peter Marschall) Date: Fri, 10 Oct 2008 12:36:06 +0200 Subject: [Lcdproc] solaris In-Reply-To: References: Message-ID: <200810101236.06913.peter@adpm.de> Hi, On Tuesday, 7. October 2008, Larson, Timothy E. wrote: > The lcdexec, lcdproc, and lcdvc clients won't build on Solaris because they > use a daemon(int,int) call. Any thoughts on how these could be written > more portably? Cool, it gets tested on Solaris. There's no definite solution yet, but here's a quick hack: Please paste the contents of the attached file into the files containing the daemon() call in the clients and try to re-compile. (a few tweaks may be necessary like writing a function declaration before the call, ...) Please report feedback if this works so that I can come up with a real solution. If it worked, please send information about your system too and what you needed to change in addition to the things above. This will help other users. Regards Peter -- Peter Marschall peter at adpm.de -------------- next part -------------- A non-text attachment was scrubbed... Name: daemon.c Type: text/x-csrc Size: 437 bytes Desc: not available URL: From nombrandue at tsukinokage.net Fri Oct 10 08:26:54 2008 From: nombrandue at tsukinokage.net (Seann Clark) Date: Fri, 10 Oct 2008 09:26:54 -0500 Subject: [Lcdproc] Matrix Orbit GLK driver Message-ID: <48EF662E.7040901@tsukinokage.net> All, I have a GLK19264-7T-1U-GW-E from Matrix Orbital, and am running LCDproc version 0.5.2. I posted this to the list a while back and the problems I am seeing with the LCD deals with buffers between my LCD and the driver software. Now, I don't know if anyone has worked on the driver code or not, so I want to verify this before I start working to get it working with this. If it hasn't been worked on, what would be best to make sure this is good code, and checked out for this driver? I am not very good at C, or much programming, but since this is a small driver that I have access to both ends of the connection, hardware docs, hardware, and software. This way as well I can get a good driver out for release if that is needed. If anyone can help me out with this, I would appreciate it. Thanks in advance, Seann From TELarson at west.com Fri Oct 10 09:25:10 2008 From: TELarson at west.com (Larson, Timothy E.) Date: Fri, 10 Oct 2008 10:25:10 -0500 Subject: [Lcdproc] solaris In-Reply-To: <200810101236.06913.peter@adpm.de> References: <200810101236.06913.peter@adpm.de> Message-ID: On Friday, October 10, 2008 5:36 AM, Peter Marschall <> scribbled: > There's no definite solution yet, but here's a quick hack: > Please paste the contents of the attached file into the files > containing the daemon() call in the clients and try to re-compile. (a > few tweaks may be necessary like writing a function declaration before > the call, ...) > > Please report feedback if this works so that I can come up with a real > solution. My googling indicates that daemon() is a BSD-ish function. I am wondering if there is a project somewhere providing a bsdcompat.h and libbsdcompat.a (or something similar). If so, it shouldn't be too hard to make configure check for the existence of these functions, and then use the results to optionally include/link them. But I will try your hack when I get a few moments and let you know. Tim -- Tim Larson AMT2 Unix Systems Administrator InterCall, a division of West Corporation Eschew obfuscation! -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9455 bytes Desc: not available URL: From ejohnson at camalytics.com Fri Oct 10 10:45:17 2008 From: ejohnson at camalytics.com (Eric H. Johnson) Date: Fri, 10 Oct 2008 12:45:17 -0400 Subject: [Lcdproc] Matrix Orbit GLK driver In-Reply-To: <48EF662E.7040901@tsukinokage.net> References: <48EF662E.7040901@tsukinokage.net> Message-ID: <004901c92af7$9486ca00$bd945e00$@com> Aarg, this was supposed to be posted to the list rather than to the individual. Seann, By buffer errors, do you mean you are overrunning the rate at which the MO or MO driver can handle commands? I encountered that problem with the MX400 series displays, especially at initialization when loading up the static screens and menus. Everything worked fine when using the curses driver, but would exceed the rate at which the MO driver could accept commands. I added a 5ms delay between socket communications on the client side and the problem went away. I have not looked into fixing it in the driver. Regards, Eric I have a GLK19264-7T-1U-GW-E from Matrix Orbital, and am running LCDproc version 0.5.2. I posted this to the list a while back and the problems I am seeing with the LCD deals with buffers between my LCD and the driver software. Now, I don't know if anyone has worked on the driver code or not, so I want to verify this before I start working to get it working with this. If it hasn't been worked on, what would be best to make sure this is good code, and checked out for this driver? I am not very good at C, or much programming, but since this is a small driver that I have access to both ends of the connection, hardware docs, hardware, and software. This way as well I can get a good driver out for release if that is needed. If anyone can help me out with this, I would appreciate it. From nombrandue at tsukinokage.net Fri Oct 10 10:58:08 2008 From: nombrandue at tsukinokage.net (Seann Clark) Date: Fri, 10 Oct 2008 11:58:08 -0500 Subject: [Lcdproc] Matrix Orbit GLK driver In-Reply-To: <004901c92af7$9486ca00$bd945e00$@com> References: <48EF662E.7040901@tsukinokage.net> <004901c92af7$9486ca00$bd945e00$@com> Message-ID: <48EF89A0.30606@tsukinokage.net> I didn't notice the lack of the group when I sent this, but here is the re-send to the right spot. : Eric H. Johnson wrote: > Seann, > > By buffer errors, do you mean you are overrunning the rate at which > the MO > or MO driver can handle commands? > > I encountered that problem with the MX400 series displays, especially at > initialization when loading up the static screens and menus. Everything > worked fine when using the curses driver, but would exceed the rate at > which > the MO driver could accept commands. I added a 5ms delay between socket > communications on the client side and the problem went away. I have not > looked into fixing it in the driver. > > Regards, > Eric > > > I have a GLK19264-7T-1U-GW-E from Matrix Orbital, and am running > LCDproc version 0.5.2. I posted this to the list a while back and the > problems I am seeing with the LCD deals with buffers between my LCD > and the > driver software. Now, I don't know if anyone has worked on the driver > code > or not, so I want to verify this before I start working to get it working > with this. If it hasn't been worked on, what would be best to make > sure this > is good code, and checked out for this driver? I am not very good at > C, or > much programming, but since this is a small driver that I have access to > both ends of the connection, hardware docs, hardware, and software. > This way > as well I can get a good driver out for release if that is needed. > > > If anyone can help me out with this, I would appreciate it. > > Eric, What I am seeing is garbled and overwriting on the LCD where it shouldn't be. I think the person was talking with last time on this stated that is seemed that the driver was not respecting the buffer for the LCD. Sadly I think that portion was off list, so I am trying to find that in my archives. I have played with different settings that you mentioned with the MX400 series, since I have one of those LCD's in USB form which worked fine. It just seems the data being sent to the LCD is too fast of a rate than the LCD can draw, and I don't see it as being a purely RS232 problem with it, since I can write to the LCD without a problem when not using LCDproc. The last time I saw the driver changed in the CVS was 17 months ago, so it is rather old, and the series I am using is about 6-7 months newer. I think taking care of the driver instead of hacking my O/s would be better for a larger group of people who may be using this, and adding it in, and how I did it may help others with other drivers as well. So I will research that and let the list know about it., the 5MS delay may help a lot with the software. Regards, Seann From epooch at cox.net Sat Oct 11 17:11:20 2008 From: epooch at cox.net (Eric Pooch) Date: Sat, 11 Oct 2008 16:11:20 -0700 Subject: [Lcdproc] USS720 Belkin USB Parallel printer adapter driver In-Reply-To: <200810082316.22078.peter@adpm.de> References: <9B017728-86DE-4FE5-808D-6E11401D92DE@cox.net> <200810082316.22078.peter@adpm.de> Message-ID: <649D71DC-E33D-4AD7-A039-BC2DBFB27264@cox.net> I had an old automake and an old pkg-config. Thanks. --Eric On Oct 8, 2008, at 2:16 PM, Peter Marschall wrote: > >> I had some trouble testing the acinclude.m4 changes due to the >> autogen.sh script creating a configuration script that was so >> different from the tarball distributed one that I could not get >> LCDproc to compile with libusb. any help on that issue would be >> appreciated. > > What versions of the auto* and pkg-config tools do you have ? > It works on Linux with: > - autoconf 2.61. > - automake 1.9.6 > - pkg-config 0.22 > But it also worked with other version of these tools. > > Thanks for supporting LCDproc > Peter > > > -- > Peter Marschall > peter at adpm.de > _______________________________________________ > LCDproc mailing list > LCDproc at lists.omnipotent.net > http://lists.omnipotent.net/mailman/listinfo/lcdproc From pthomas8589 at gmail.com Tue Oct 14 10:08:35 2008 From: pthomas8589 at gmail.com (Paul Thomas) Date: Tue, 14 Oct 2008 09:08:35 -0700 Subject: [Lcdproc] picolcd driver Message-ID: when I build lcdproc I don't get a picolcd.so driver. Is the picolcd in a different .so file? Am I missing something simple? thanks, Paul From bogdan_radulescu99 at yahoo.com Tue Oct 14 13:44:33 2008 From: bogdan_radulescu99 at yahoo.com (Bogdan Radulescu) Date: Tue, 14 Oct 2008 12:44:33 -0700 (PDT) Subject: [Lcdproc] picolcd driver In-Reply-To: Message-ID: <211149.84232.qm@web30205.mail.mud.yahoo.com> You should be using the --enable-drivers= parameter. ./configure --enable-drivers=picolcd Unfortunately, I think that in the latest CVS build (Sep 24) the 20x2 display driver might be broken. Let us know how this works out for you. Regards, Bogdan --- On Tue, 10/14/08, Paul Thomas wrote: > From: Paul Thomas > Subject: [Lcdproc] picolcd driver > To: lcdproc at lists.omnipotent.net > Date: Tuesday, October 14, 2008, 7:08 PM > when I build lcdproc I don't get a picolcd.so driver. Is > the picolcd > in a different .so file? Am I missing something simple? > > thanks, > Paul > _______________________________________________ > LCDproc mailing list > LCDproc at lists.omnipotent.net > http://lists.omnipotent.net/mailman/listinfo/lcdproc From pthomas8589 at gmail.com Tue Oct 14 14:50:29 2008 From: pthomas8589 at gmail.com (Paul Thomas) Date: Tue, 14 Oct 2008 13:50:29 -0700 Subject: [Lcdproc] picolcd driver In-Reply-To: <211149.84232.qm@web30205.mail.mud.yahoo.com> References: <211149.84232.qm@web30205.mail.mud.yahoo.com> Message-ID: I tried that with both the CSV and lcdproc-picolcd20x4-0.5.2-cvs.tgz version. I still don't get a picolcd.so file. thanks, Paul On Tue, Oct 14, 2008 at 12:44 PM, Bogdan Radulescu wrote: > You should be using the --enable-drivers= parameter. > ./configure --enable-drivers=picolcd > > Unfortunately, I think that in the latest CVS build (Sep 24) the 20x2 display driver might be broken. Let us know how this works out for you. > > Regards, > Bogdan > > > --- On Tue, 10/14/08, Paul Thomas wrote: > >> From: Paul Thomas >> Subject: [Lcdproc] picolcd driver >> To: lcdproc at lists.omnipotent.net >> Date: Tuesday, October 14, 2008, 7:08 PM >> when I build lcdproc I don't get a picolcd.so driver. Is >> the picolcd >> in a different .so file? Am I missing something simple? >> >> thanks, >> Paul >> _______________________________________________ >> LCDproc mailing list >> LCDproc at lists.omnipotent.net >> http://lists.omnipotent.net/mailman/listinfo/lcdproc > > > > From peter at adpm.de Wed Oct 15 01:08:24 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 15 Oct 2008 09:08:24 +0200 Subject: [Lcdproc] picolcd driver In-Reply-To: <211149.84232.qm@web30205.mail.mud.yahoo.com> References: <211149.84232.qm@web30205.mail.mud.yahoo.com> Message-ID: <200810150908.24509.peter@adpm.de> Hi Bogdan, On Tuesday, 14. October 2008, Bogdan Radulescu wrote: > Unfortunately, I think that in the latest CVS build (Sep 24) the 20x2 > display driver might be broken. Let us know how this works out for you. Can you elaborate a bit on this ? Regards Peter -- Peter Marschall peter at adpm.de From peter at adpm.de Wed Oct 15 01:13:15 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 15 Oct 2008 09:13:15 +0200 Subject: [Lcdproc] picolcd driver In-Reply-To: References: <211149.84232.qm@web30205.mail.mud.yahoo.com> Message-ID: <200810150913.15269.peter@adpm.de> Hi Paul, On Tuesday, 14. October 2008, Paul Thomas wrote: > I tried that with both the CSV and lcdproc-picolcd20x4-0.5.2-cvs.tgz > version. I still don't get a picolcd.so file. Bogdan is right, picolcd is not among the drivers that are built by default. Besides, the picolcd driver requires libusb. Perhaps you haven't installed it (or it's developemnt files). In addition to that, LCDproc requires pkg-config installed. Please report if this helps. Regards Peter -- Peter Marschall peter at adpm.de From hans at ginder.xs4all.nl Wed Oct 15 02:55:21 2008 From: hans at ginder.xs4all.nl (Hans Houwaard) Date: Wed, 15 Oct 2008 10:55:21 +0200 Subject: [Lcdproc] LCDproc and glcdlib: Display size invalid Message-ID: <559ae37dce5ec37a58393565908c369f@ginder.xs4all.nl> Hallo all, First post here, thanks for all the wonder software I'm currently trying to use. I have however run into some problems: I have build, installed and test graphlcd, newest stable, 0.9.7.8 I think. This does put output on my alphacool LC display. The alphacool display is a USB serial display with 200x64 pixels. I have then build the lcdproc 0.5.2 version and the 0.0.2 and 0.0.4 version of glcdprocdriver. I installed all of this as documented. driverpath is set correctly in the LCDd.conf file and the options for glcdlib using the serlib driver are put in. When I try and start LCDd it fails with the glcdlib driver invalid display size message. There is however no option to set this size, only character per line and lines number?in 20x4 format.?I have tried different sizes and shapes, but without any success. What is going wrong and how can I fix this? I think display size for the alphacool display is autodetected and maybe something goes wrong in communicating this to lcdproc. I don't know how to fix this, as I am no developer. Any help is highly appreciated. Hans Houwaard -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob_ml at stuffofmine.com Wed Oct 15 06:39:23 2008 From: bob_ml at stuffofmine.com (Bob Wiegand) Date: Wed, 15 Oct 2008 07:39:23 -0500 Subject: [Lcdproc] picolcd driver In-Reply-To: <200810150913.15269.peter@adpm.de> References: <211149.84232.qm@web30205.mail.mud.yahoo.com> <200810150913.15269.peter@adpm.de> Message-ID: <48F5E47B.10807@stuffofmine.com> Peter Marschall wrote: > Hi Paul, > > On Tuesday, 14. October 2008, Paul Thomas wrote: >> I tried that with both the CSV and lcdproc-picolcd20x4-0.5.2-cvs.tgz >> version. I still don't get a picolcd.so file. > > Bogdan is right, picolcd is not among the drivers that are built by default. > > Besides, the picolcd driver requires libusb. > > Perhaps you haven't installed it (or it's developemnt files). > In addition to that, LCDproc requires pkg-config installed. > > Please report if this helps. > > Regards > Peter A missing dependency is the most likely problem. Check the "config.log" file and search for "picolcd". There may be an error message telling you what's missing. -- Regards, Bob From peter at adpm.de Wed Oct 15 10:05:24 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 15 Oct 2008 18:05:24 +0200 Subject: [Lcdproc] CrystalFontz CF635, LEDs, lcdexec In-Reply-To: <48ED7D96.4090401@jasonantman.com> References: <48ED7D96.4090401@jasonantman.com> Message-ID: <200810151805.24846.peter@adpm.de> On Thursday, 9. October 2008, Jason Antman wrote: > I'm just giving LCDproc my first try. I'm using a CF635 to control 4 USB > relays with a dedicated headless system. For starters, I'm using > lcdexec. I have 2 questions which I haven't been able to find answers to > online: > > 1) When I start lcdexec (only client running) it just updates the > 'Clients' number on the LCDproc Server screen, and I have to use the > menu to navigate to LCDexec. Once I make a choice, the menu from LCDexec > just goes away. Is there any way to get the lcdexec menu to show up > right away, and stay there? No, at least not with the current code. That does not mean that I won't consider patches that enable this behaviour (as an altrnative to the current behavior). lcdexec was written as a demo of the features of LCDproc's server-side menu system. It should integrate with the other LCDproc clients, that rotate screens, without too much getting in their way. > 2) Since there's no real way to update the lcdexec menus on-the-fly, I > was hoping to use the four GPIO LEDs on the CF635 to show the status of > the four relays. Firstly, does lcdproc support GPIO at all? Secondly, if > so, is there any way to get lcdexec to update them? Some (most) LCDproc drivers provide an output() funktion that can be used by the server and controlled using the Client API function output. For the CF635, the LEDs are controlled using this function. Currently lcedexec does not support setting the outputs based on the results of commands, but this can be changed by sending patches. > I have a Python class for the CF635, and am thinking that I may have to > use that, though i never implemented button listeners and would have to > do that... What about C and sending in patches for lcdexec ;-)) Regards PEter -- Peter Marschall peter at adpm.de From peter at adpm.de Wed Oct 15 10:06:38 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 15 Oct 2008 18:06:38 +0200 Subject: [Lcdproc] ethlcd doc In-Reply-To: <48F0F55B.2090904@skyboo.net> References: <48AC661D.2060301@skyboo.net> <200809191945.37315.peter@adpm.de> <48F0F55B.2090904@skyboo.net> Message-ID: <200810151806.39099.peter@adpm.de> Hi, On Saturday, 11. October 2008, you wrote: > As i promissed some time ago i've extended an ethlcd documentation a > bit. I hope you will commit the changes :) > Please check the sentences (i could made some mistakes) - because i'm > not english native speaker nor writer :( > diff as attachment Committed to CVS. Thanks PEter -- Peter Marschall peter at adpm.de From stefanh at on-luebeck.de Mon Oct 20 10:15:24 2008 From: stefanh at on-luebeck.de (=?ISO-8859-1?Q?Stefan_Hu=DFfeldt?=) Date: Mon, 20 Oct 2008 18:15:24 +0200 Subject: [Lcdproc] LCDproc and glcdlib: Display size invalid In-Reply-To: <559ae37dce5ec37a58393565908c369f@ginder.xs4all.nl> References: <559ae37dce5ec37a58393565908c369f@ginder.xs4all.nl> Message-ID: <48FCAE9C.9000901@on-luebeck.de> Hans Houwaard schrieb: > I have then build the lcdproc 0.5.2 version and the 0.0.2 and 0.0.4 > version of glcdprocdriver. I installed all of this as documented. > driverpath is set correctly in the LCDd.conf file and the options for > glcdlib using the serlib driver are put in. When I try and start LCDd it > fails with the glcdlib driver invalid display size message. There is > however no option to set this size, only character per line and lines > number in 20x4 format. I have tried different sizes and shapes, but > without any success. I've had this problem with a glcd (glcdlib) because the TTF FontFile was invalid. -- Und Tsch?ss. Stefan ### Kilroy was here ### 2.6.20.2 up 31 days From andy at siliconlandmark.com Mon Oct 20 11:32:53 2008 From: andy at siliconlandmark.com (Andre Guibert de Bruet) Date: Mon, 20 Oct 2008 13:32:53 -0400 Subject: [Lcdproc] [PATCH] Missing malloc() return value check in picolcd.c Message-ID: <818AFFD8-7C93-4FDA-AECF-179385B37C64@siliconlandmark.com> Hi, I found an instance where the return value of malloc() was not being checked in picolcd.c. I have attached a diff that addresses the issue. Cheers, Andy /* Andre Guibert de Bruet * 436f 6465 2070 6f65 742e 2042 6974 206a */ /* Managing Partner * 6f63 6b65 792e 2053 7973 4164 6d69 6e2e */ /* GSM: +1 734 846 8758 * 2055 4e49 5820 736c 6575 7468 2e00 0000 */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ -------------- next part -------------- A non-text attachment was scrubbed... Name: picolcd.malloc.diff Type: application/octet-stream Size: 373 bytes Desc: not available URL: -------------- next part -------------- From andy at siliconlandmark.com Mon Oct 20 12:49:31 2008 From: andy at siliconlandmark.com (Andre Guibert de Bruet) Date: Mon, 20 Oct 2008 14:49:31 -0400 Subject: [Lcdproc] [PATCH] Missing malloc() return value check in picolcd.c In-Reply-To: <818AFFD8-7C93-4FDA-AECF-179385B37C64@siliconlandmark.com> References: <818AFFD8-7C93-4FDA-AECF-179385B37C64@siliconlandmark.com> Message-ID: Hi, Here's the same patch as a unified diff against HEAD. Cheers, Andy /* Andre Guibert de Bruet * 436f 6465 2070 6f65 742e 2042 6974 206a */ /* Managing Partner * 6f63 6b65 792e 2053 7973 4164 6d69 6e2e */ /* GSM: +1 734 846 8758 * 2055 4e49 5820 736c 6575 7468 2e00 0000 */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ -------------- next part -------------- A non-text attachment was scrubbed... Name: picolcd.malloc.diff Type: application/octet-stream Size: 678 bytes Desc: not available URL: -------------- next part -------------- From aronparsons at gmail.com Tue Oct 21 17:38:58 2008 From: aronparsons at gmail.com (Aron Parsons) Date: Tue, 21 Oct 2008 19:38:58 -0400 Subject: [Lcdproc] IRTrans Driver In-Reply-To: <219af8e30810211636l4dae2328n57ed1ac61a585a08@mail.gmail.com> References: <219af8e30810211636l4dae2328n57ed1ac61a585a08@mail.gmail.com> Message-ID: <219af8e30810211638v386ffeabu12cf69ce7c0a1c5d@mail.gmail.com> I updated the patch submitted at http://lists.omnipotent.net/pipermail/lcdproc/2007-February/011487.html to apply cleanly against the current CVS version. I added some basic documentation for the driver as required for new drivers. There have been no changes to the code itself. I have been using this driver with LCDproc and my Ahanix MCE303 case for a few months. It requires the IRTrans irserver daemon to be running so that LCDproc can talk to it. I am not sure about how all the devices communicate, but that is what is required according to IRTrans. I made note of this in the documentation. If there's anything else needed to get this into the trunk, please let me know (as long as it doesn't involve hacking the C code ;-) /aron -------------- next part -------------- A non-text attachment was scrubbed... Name: irtrans.patch Type: application/octet-stream Size: 35368 bytes Desc: not available URL: From iceman85 at gmail.com Fri Oct 24 12:08:09 2008 From: iceman85 at gmail.com (Dan Eisley) Date: Fri, 24 Oct 2008 14:08:09 -0400 Subject: [Lcdproc] Need help developing custom client Message-ID: <5f416d1d0810241108r280f51a5qf16ce6734d5e85ae@mail.gmail.com> Hello, I'm trying to develop a custom client for LCDProc which utilizes a menu to call selected bash shell scripts, and then allow the output of these scripts to be sent to the LCD. Can anyone suggest an existing client, or some code that may help me accomplish this goal? Any help is much appreciated. iceman85 From andy at siliconlandmark.com Fri Oct 24 12:36:17 2008 From: andy at siliconlandmark.com (Andre Guibert de Bruet) Date: Fri, 24 Oct 2008 14:36:17 -0400 Subject: [Lcdproc] Need help developing custom client In-Reply-To: <5f416d1d0810241108r280f51a5qf16ce6734d5e85ae@mail.gmail.com> References: <5f416d1d0810241108r280f51a5qf16ce6734d5e85ae@mail.gmail.com> Message-ID: <6DDB5ACD-1C5E-4DAF-B11C-8D6EC54EDD26@siliconlandmark.com> On Oct 24, 2008, at 2:08 PM, Dan Eisley wrote: > I'm trying to develop a custom client for LCDProc which utilizes a > menu to call selected bash shell scripts, and then allow the output of > these scripts to be sent to the LCD. Can anyone suggest an existing > client, or some code that may help me accomplish this goal? > > Any help is much appreciated. May I suggest using lcdexec as a starting point for such an endeavor? The outputting of the result to the LCD is featured as an idea for future development at http://lcdproc.org/devel.php3 . Regards, Andy /* Andre Guibert de Bruet * 436f 6465 2070 6f65 742e 2042 6974 206a */ /* Managing Partner * 6f63 6b65 792e 2053 7973 4164 6d69 6e2e */ /* GSM: +1 734 846 8758 * 2055 4e49 5820 736c 6575 7468 2e00 0000 */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ From iceman85 at gmail.com Fri Oct 24 13:39:54 2008 From: iceman85 at gmail.com (Dan Eisley) Date: Fri, 24 Oct 2008 15:39:54 -0400 Subject: [Lcdproc] Fwd: Need help developing custom client In-Reply-To: <5f416d1d0810241239y6ab2931do6177634b7183ea56@mail.gmail.com> References: <5f416d1d0810241108r280f51a5qf16ce6734d5e85ae@mail.gmail.com> <6DDB5ACD-1C5E-4DAF-B11C-8D6EC54EDD26@siliconlandmark.com> <5f416d1d0810241239y6ab2931do6177634b7183ea56@mail.gmail.com> Message-ID: <5f416d1d0810241239j1b31ba74wfda926dd8f1ea0c2@mail.gmail.com> ---------- Forwarded message ---------- From: Dan Eisley Date: Fri, Oct 24, 2008 at 3:39 PM Subject: Re: [Lcdproc] Need help developing custom client To: Andre Guibert de Bruet Andy, Thank you very much for your response. I have looked at lcdexec, and that fits the bill up until the point where I need to display information on the LCD screen such as a status message, bar graph or the like. Do you know when this feature will be implemented, or if it has been in a beta release? If not could I ask for further assistance in programming such a module? Thanks Dan On Fri, Oct 24, 2008 at 2:36 PM, Andre Guibert de Bruet wrote: > On Oct 24, 2008, at 2:08 PM, Dan Eisley wrote: > >> I'm trying to develop a custom client for LCDProc which utilizes a >> menu to call selected bash shell scripts, and then allow the output of >> these scripts to be sent to the LCD. Can anyone suggest an existing >> client, or some code that may help me accomplish this goal? >> >> Any help is much appreciated. > > May I suggest using lcdexec as a starting point for such an endeavor? The > outputting of the result to the LCD is featured as an idea for future > development at http://lcdproc.org/devel.php3 . > > Regards, > Andy > > /* Andre Guibert de Bruet * 436f 6465 2070 6f65 742e 2042 6974 206a */ > /* Managing Partner * 6f63 6b65 792e 2053 7973 4164 6d69 6e2e */ > /* GSM: +1 734 846 8758 * 2055 4e49 5820 736c 6575 7468 2e00 0000 */ > /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ > > From tfangio at fractech.net Fri Oct 24 15:22:12 2008 From: tfangio at fractech.net (Topher Fangio) Date: Fri, 24 Oct 2008 16:22:12 -0500 Subject: [Lcdproc] Need help developing custom client In-Reply-To: <5f416d1d0810241108r280f51a5qf16ce6734d5e85ae@mail.gmail.com> References: <5f416d1d0810241108r280f51a5qf16ce6734d5e85ae@mail.gmail.com> Message-ID: <42B18A8261FAE0428A17F9A6A539339E1187417201@EXCHCLST01.FRACTECH.LOCAL> Hi Dan, I don't know if it will help, but I have released a Ruby based library for writing applications. I haven't had the chance to write a whole lot but the library is pretty flexible and gives you the ability to use the menus like you want. I am more than willing to answer any questions you have and work with you to extend the library to be more useful and have more functions. The really nice thing is that you can write your own widgets that are based off of other charts. For instance, you can create a synthesizer graph based off of a group of vertical bar graphs. There are a few examples to get you started, but feel free to let me know if you have any problems. I just set up the new mailing lists, so they might not take effect right away. Feel free to contact me directly and I will post it to the list when they are available...I just don't want to hijack the lcdproc mailing list :-) http://sourceforge.net/projects/lcdproc-ruby/ Topher Fangio -----Original Message----- From: lcdproc-bounces at lists.omnipotent.net [mailto:lcdproc-bounces at lists.omnipotent.net] On Behalf Of Dan Eisley Sent: Friday, October 24, 2008 1:08 PM To: lcdproc at lists.omnipotent.net Subject: [Lcdproc] Need help developing custom client Hello, I'm trying to develop a custom client for LCDProc which utilizes a menu to call selected bash shell scripts, and then allow the output of these scripts to be sent to the LCD. Can anyone suggest an existing client, or some code that may help me accomplish this goal? Any help is much appreciated. iceman85 _______________________________________________ LCDproc mailing list LCDproc at lists.omnipotent.net http://lists.omnipotent.net/mailman/listinfo/lcdproc CONFIDENTIALITY NOTICE: This email message and any attachments hereto are intended only for use by the addressee(s) named herein and may contain information which is legally privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, or an authorized representative of the intended recipient, of this email message, you are hereby notified that any review, dissemination, distribution, copying, or use (including any reliance thereon) of this email message, and/or any attachment hereto, is strictly prohibited. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is free from virus or other defect and no responsibility is accepted by the sending company, its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you have received this email message in error, please immediately notify the sender by return email and permanently delete from your system, the original and any copies of this email and any attachments hereto and any printout hereof. Unauthorized interception of this email is a violation of federal criminal law. From andy.grover at gmail.com Fri Oct 24 16:36:15 2008 From: andy.grover at gmail.com (Andrew Grover) Date: Fri, 24 Oct 2008 15:36:15 -0700 Subject: [Lcdproc] Need help developing custom client In-Reply-To: <42B18A8261FAE0428A17F9A6A539339E1187417201@EXCHCLST01.FRACTECH.LOCAL> References: <5f416d1d0810241108r280f51a5qf16ce6734d5e85ae@mail.gmail.com> <42B18A8261FAE0428A17F9A6A539339E1187417201@EXCHCLST01.FRACTECH.LOCAL> Message-ID: Hi Topher, On Fri, Oct 24, 2008 at 2:22 PM, Topher Fangio wrote: > I don't know if it will help, but I have released a Ruby based library > for writing applications. I haven't had the chance to write a whole lot > but the library is pretty flexible and gives you the ability to use the > menus like you want. I am more than willing to answer any questions you > have and work with you to extend the library to be more useful and have > more functions. > There are a few examples to get you started, but feel free to let me know > if you have any problems. I just set up the new mailing lists, so they > might not take effect right away. Feel free to contact me directly and > I will post it to the list when they are available...I just don't want > to hijack the lcdproc mailing list :-) > > http://sourceforge.net/projects/lcdproc-ruby/ I just downloaded this and checked it out, I'm pretty impressed with the level of quality, especially for a "0.1" release. I'd call it a 0.9, at least! I'm actually working on updating pylcd (which has been dormant since 2002) in much the same direction -- creating an OO interface that hides lcdproc's actual over-the-wire protocol in favor of a friendlier one. One technical question: Have you found the client/screen/widget IDs to be useful in any way that warrants their setting by the user? lcdproc-ruby already has the capability to autogenerate them, the next step would be to *always* autogenerate them. Do you see a downside to that? One more q: have you found any info on what encoding text strings should be in? pylcd 0.2 strips non-ASCII chars, but there's also a note that more recent versions of lcdproc possibly make this unnecessary -- I haven't tried. I am not a Ruby programmer but having your code as an example should speed things for me. Hopefully I'll have the reborn pylcd available in a few weeks for public review. Regards -- Andy From peter at adpm.de Sun Oct 26 14:46:29 2008 From: peter at adpm.de (Peter Marschall) Date: Sun, 26 Oct 2008 21:46:29 +0100 Subject: [Lcdproc] [PATCH] Missing malloc() return value check in picolcd.c In-Reply-To: References: <818AFFD8-7C93-4FDA-AECF-179385B37C64@siliconlandmark.com> Message-ID: <200810262146.29640.peter@adpm.de> Hi, On Monday, 20. October 2008, Andre Guibert de Bruet wrote: > Here's the same patch as a unified diff against HEAD. Committed to CVS. Thanks for supporting LCDproc Peter -- Peter Marschall peter at adpm.de From peter at adpm.de Sun Oct 26 15:34:48 2008 From: peter at adpm.de (Peter Marschall) Date: Sun, 26 Oct 2008 22:34:48 +0100 Subject: [Lcdproc] IRTrans Driver In-Reply-To: <219af8e30810211638v386ffeabu12cf69ce7c0a1c5d@mail.gmail.com> References: <219af8e30810211636l4dae2328n57ed1ac61a585a08@mail.gmail.com> <219af8e30810211638v386ffeabu12cf69ce7c0a1c5d@mail.gmail.com> Message-ID: <200810262234.48902.peter@adpm.de> Hi, On Wednesday, 22. October 2008, Aron Parsons wrote: > I updated the patch submitted at > http://lists.omnipotent.net/pipermail/lcdproc/2007-February/011487.html > to apply cleanly against the current CVS version. I added some basic > documentation for the driver as required for new drivers. > > There have been no changes to the code itself. I have been using this > driver with LCDproc and my Ahanix MCE303 case for a few months. It > requires the IRTrans irserver daemon to be running so that LCDproc can > talk to it. I am not sure about how all the devices communicate, but > that is what is required according to IRTrans. I made note of this in > the documentation. > > If there's anything else needed to get this into the trunk, please let > me know (as long as it doesn't involve hacking the C code ;-) Thanks, committed to CVS. If you add a bit more documentation that would be cool. I guess there are more config options in the code that should be documented as well. Regards Peter -- Peter Marschall peter at adpm.de From aronparsons at gmail.com Tue Oct 28 22:02:03 2008 From: aronparsons at gmail.com (Aron Parsons) Date: Wed, 29 Oct 2008 00:02:03 -0400 Subject: [Lcdproc] IRTrans Driver In-Reply-To: <219af8e30810211638v386ffeabu12cf69ce7c0a1c5d@mail.gmail.com> References: <219af8e30810211636l4dae2328n57ed1ac61a585a08@mail.gmail.com> <219af8e30810211638v386ffeabu12cf69ce7c0a1c5d@mail.gmail.com> Message-ID: <219af8e30810282102g4fff4814j490311f510410c66@mail.gmail.com> I'll try to take some time and add some documentation for the other options available in the driver. Hopefully some others that have been using the out-of-tree driver can chime in on the options they're actually using; my configuration is only using the one line identified in the current documentation. /aron On Tue, Oct 21, 2008 at 7:38 PM, Aron Parsons wrote: > I updated the patch submitted at > http://lists.omnipotent.net/pipermail/lcdproc/2007-February/011487.html > to apply cleanly against the current CVS version. I added some basic > documentation for the driver as required for new drivers. > > There have been no changes to the code itself. I have been using this > driver with LCDproc and my Ahanix MCE303 case for a few months. It > requires the IRTrans irserver daemon to be running so that LCDproc can > talk to it. I am not sure about how all the devices communicate, but > that is what is required according to IRTrans. I made note of this in > the documentation. > > If there's anything else needed to get this into the trunk, please let > me know (as long as it doesn't involve hacking the C code ;-) > > /aron > From peter at adpm.de Wed Oct 29 01:59:06 2008 From: peter at adpm.de (Peter Marschall) Date: Wed, 29 Oct 2008 08:59:06 +0100 Subject: [Lcdproc] No configure warning if no pkg-config In-Reply-To: <20080929154834.HT6UK.528898.imail@fed1rmwml45> References: <20080929154834.HT6UK.528898.imail@fed1rmwml45> Message-ID: <200810290859.07032.peter@adpm.de> Hi Eric, On Monday, 29. September 2008, epooch at cox.net wrote: > I experienced a problem this weekend while trying to compile libusb > dependent drivers in lcdproc. Previously, I did not have any problems > compiling these drivers. The problem is that if pkg-config is not > installed, the configuration proceeds with no warnings or errors, even if > libusb is explicitly enabled. There is no indication of a problem or what > it is until the complier gives warnings about certain drivers needing > libusb. However, because I was only compiling the HD44780 USB drivers, > there wasn't even a compiler warning! My USB HD44780 driver just would not > get compiled. There is no documentation about requiring pkg-config for > libusb in either INSTALL or CHANGES I may make a patch, but I wanted to > make sure this was mentioned on the list in case anybody else has the same > problem. The solution is simple- just install pkg-config and set the > relevant environment variable to its path. This was a problem in Mac OS X > 10.4.8 where pkg-config is not installed by the development tools. Thanks I have committed a patch to LCDproc's CVS a few days ago tht should fx this issue. The fix works by checking whether the PKG_CHECK_MODULES macros is defined and it throws a warning when it isn't. Yould you mind to give it a test Regards Peter -- Peter Marschall peter at adpm.de From swannonline at googlemail.com Wed Oct 29 11:24:20 2008 From: swannonline at googlemail.com (Steven Swann) Date: Wed, 29 Oct 2008 17:24:20 +0000 Subject: [Lcdproc] New Amarok LCD client Message-ID: <74E5C380-7D6D-458D-AEC5-F41107880E6C@googlemail.com> Hello, Could you add my new client to the website, the basic details follow: Amarok_XML_LCD 0.1 http://kde-apps.org/content/show.php?content=92102 This Amarok script allows for user customisable screens to be created and displayed on an LCD interface using lcdproc and allows data to be dynamically updated using the DCOP bus. I don't mind if you give out my email address, Best regards, Steven Swann From andy at siliconlandmark.com Thu Oct 30 20:46:27 2008 From: andy at siliconlandmark.com (Andre Guibert de Bruet) Date: Thu, 30 Oct 2008 22:46:27 -0400 Subject: [Lcdproc] [PATCH] Remove devfs from list of reported filesystems on FreeBSD Message-ID: Hello, I have attached a patch which removes the listing of devfs-type filesystems from machine_get_fs() calls on FreeBSD. Devfs is a special filesystem that is reported as 1k in size, used at 100% and is presently cluttering the disk display. Could this get committed upon review? :) Cheers, Andy /* Andre Guibert de Bruet * 436f 6465 2070 6f65 742e 2042 6974 206a */ /* Managing Partner * 6f63 6b65 792e 2053 7973 4164 6d69 6e2e */ /* GSM: +1 734 846 8758 * 2055 4e49 5820 736c 6575 7468 2e00 0000 */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ -------------- next part -------------- A non-text attachment was scrubbed... Name: freebsd.nodevfs.patch Type: application/octet-stream Size: 651 bytes Desc: not available URL: From didik at dsp.itb.ac.id Fri Oct 31 02:50:23 2008 From: didik at dsp.itb.ac.id (Eko Didik Widianto) Date: Fri, 31 Oct 2008 15:50:23 +0700 (WIT) Subject: [Lcdproc] USB CS-LCD for HD44780 module Message-ID: <56466.167.205.24.67.1225443023.squirrel@mail.dsp.itb.ac.id> Hello, i've recode my usb cs-lcd driver and add keypad input routine. It allows up to 4x8 matrix keypad to be used as input. backlight can be controlled from LCD menu. here is the patch againts lcdproc-0.5.2. i apologize not using current cvs to diff. http://edwidianto.wordpress.com/2008/08/01/power-up-usb-cs-lcd/ -eko didik widianto On Fri, 19 Sep 2008 19:52:28 +0200 Peter Marschall wrote: > Hi, > > sorry for the late answer, > > On Monday, 4. August 2008, Eko Didik Widianto wrote: > > Yes, off course. i wrote hd44780-cslcd.[c,h] to drive that interface and it > > will be called as cslcd in ConnectionType at hd44780 context. it's stable > > now. i want to share those files (and the neccessary patch file) to this > > project. > > If you still want your connection type be included into mainline LCDproc, > please send the patches to current CVS to the LCDproc mailing list. > > Please don't forget to not only send the code, but also the necessary > documentation. > Plase have a look at > http://lcdproc.sourceforge.net/docs/current-dev.html#documentation > for what is expected. > As yours is "only" an extension of an existing driver, you don't need > to write a new file for the hd44780 driver; simply extend the existing > one with the information of your driver (you may look at ethlcd as an example) > > Regards > Peter -------------- next part -------------- A non-text attachment was scrubbed... Name: lcdproc-0.5.2-csusb.diff Type: application/octet-stream Size: 20921 bytes Desc: not available URL: