G-Series Gaming Keyboards

[anchorman]

I just purchased a new G-15 keyboard and my 2007 imac will not recognize it.  Per instructions, I plugged in the keyboard and installed the OS X drivers but my system will not recognize the keyboard plugged in.  The usb ports are functioning properly as everything else I plug into them works just fine. 

On a side note I plugged the keyboard into my old windows pc and it says the device is damaged and windows did not recognize it.  Bad keyboard?  Should I take it back to exchange or are there other troubleshooting steps I can take? 

Message Edited by anchorman on 01-23-2009 01:50 PM

[Theodric]

Does it work to enter/use the BIOS of your old Windows PC? If not, sounds like you got a dud and I'd work on getting it exchanged.

[IoanPopovici]

Problem:

LCD Manager keeps itunes from closing (must use force quit)

[Theodric]

I downloaded the OS X software package for the new G19 keyboard, manually extracted the various nested archives and discovered that the Performance Monitor included in that distribution now includes dual-core support, AND more accurately (by 25%!) reflects memory usage on a 4GB system. Piccy:

Now I reckon the above is far beyond unsupported or even recommended, but I'm just putting my discovery out there for the community. If you don't know how to extract installer archives, you probably should not be messing with this kind of stuff. There's no telling what just installing the package will do with unsupported hardware (maybe work, maybe make everything explode?)

A big thanks to the devs for fixing this little issue-- really looking forward to the gold release and SDK!!

Message Edited by Theodric on 02-03-2009 01:54 PM

[Chris_P]

The G19 version is the current version and is absolutely supported software for G11, G13, and G15 keyboards.

[TheMonkey]

Hi there

I'm running the latest version of the LCD Manager (3.01.310) with a G15 keyboard and wanted to point out a few little more bugs i've been experiencing.

Before I start, I should point out my computer setup. I am running a high end 8 Core Mac Pro 3.2GHz with 16GB RAM, with sound out via digital optical. 

Firstly, the Media control applet still doesn't seem to be working at all. The buttons on the keyboard I imagine are stand alone and do work (the next track, previous track, etc), but the applet looks strange. It appears frozen with "Logitech Software Media Display" in large letters, a pause icon on the left overlayed on the "D" from Display, and a status bar going the length of the display from left to right, which is frozen on what I would estimate is about 2%. No matter what I does not make this operate.

Secondly, I get a solid bar on my CPU meter. This does not bother me, but sometimes for no reason that solid bar turns into 2 horizontal bars, and freezes. I imagine this is because it is trying to read 2 cores when in fact there are 8. I do like how the read out has 2 decimals, and the refresh rate is okay. When comparing the CPU% to the OS Activity Monitor, it seems pretty accurate so its no real big deal, when it is a single bar.

I hope these issues are explained thouroughly and can be recreated on your end.

Cheers and thanks,

Michael

[Theodric]

Chris, I just want to express the pleasant surprise and warm fuzzies I'm getting from Logitech actually choosing to support a product which was released ages ago and since discontinued, and also from the choice to keep to one consistent API for the B&W LCDs so we can all join in the fun. I would expect most manufacturers to have long ago abandoned the G15 v1 with planned obsolescence and forced upgrades (which would make me sad, as I love this keyboard and its 18 programmable macro keys). Keep it up, and tell your salesguys don't worry, I'll still buy a G19 for the office!

[Jerr]

I am also having the same problem where iTunes won't close when the LCD Media Display is running. iTunes either has to be Force Quit or I have to quit the LCD Media Display (Activity Monitor).

OS X 10.5.6

LCD Manager V3.01.310

iTunes 8.0.2

[tdegrunt]

All in all I'm very happy Logitech supports the Mac, I love the G13 and use it on a daily basis. 

However, with the driver/software version 3.00.236 on Mac OSX 10.5.6, I'm having some issues (haven't tried older versions):

LGDDevAgent: 

- App crashes when started, what is the application for?

G-series Key Profiler: 

- G13 key profiles don't seem to persist to the G13 device 

- If I switch to per example WoW and the profiler is not running, the WoW profile doesn't get selected

- Application locks up when a color is selected for a key-pad mode (M1, M2, M3) and then restarted, this can be reproduced by:

  1) Double click the color-area next to a key-pad mode

  2) The color pane will open, from the bottom set of colors select one of the whites (these are the favorites), close the color pane

  3) Save the profile

  4) Quit the application, disconnect the device

  5) Start the application - it will lock up, error in Console:

2/5/09 8:21:48 PM G-series Key Profiler[261] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -redComponent not defined for the NSColor NSCalibratedWhiteColorSpace 1 1; need to first convert colorspace.'  

This problem can only be solved by deleting the com.logitech.* files from ~/Library/Preferences

- The app (G-series Key Profiler) is put it the startup items, but on computer reboot, all logitech related apps completely lock up,

   when removing the app from the startup items (keep LCDManager) it works if you start  G-series Key Profiler once the LCDManager is started.

General, but already reported - the screen doesn't work with WoW (but far less important than anything above).

[mynous]

I am having problems installing the GamePanel Software. Everything goes fine installing however when it prompts me to connect the G-series keyboard, the program does not recognize it. I have tried unplugging and reconnecting the keyboard (G15v1) with no success. When I open system profiler the keyboard shows up as the Logitech G15 Gaming keyboard however the logitech program cannot seem to recognize it.

I was wondering if anyone else has had a similar problem or solution.

I am running 10.5.5, I may try updating and attempting again to see if may fix the problem.