Love gizmod. I've got it working beautifully with a PowerMate, but now i would like to see what i could possibly do to make it work with my NuLOOQ. Will gizmod work with the Logitech NuLOOQ "out of the box" (using the generic Linux USB HID driver) or will something special need to be done?
Many Thanks
Vek
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I actually have no idea! From what I can tell it looks like it should support HID, in which case gizmod will work with it out of the box (although it may require some configuration). But I really don't know.
Do you already have the device? Does it work as a regular USB HID device?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do have a NuLooq here on my desk. From what i've been told, it will work with the spacenav daemon ( http://spacenav.sourceforge.net/ ), if you modify the code just a bit. The spacenav daemon sees my Nulooq, and lights up one of the LEDs, but aside from that i've not gotten very far, so i cannot say with any degree of certainty that "it work as a regular USB HID".
My "gut" tells me that it does work with basic USB HID however, as i've loaded no separate kernel driver for it and i do not believe that the spacenav daemon is running a user space driver, yet it sees my device.
There is scant info out there about getting the NuLooq to work with linux and since all of the spacenav info I've run across is geared towards the actual 3Dconnex SpaceNav devices (6 axis controllers), i haven't had no success doing anything with it.
The whole point is to get it to work with gizmod (not spacenav), but i gave the spacenav daemon a whirl thinking that i might at least learn something in the process that would be beneficial in getting it to work with gizmod. All that being said however, it looks like i might be a bit out of my league in trying to make this happen (i'm not yet too familiar with xinput concepts and so forth).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Cool. Looks like it should work fine! I think it'll just need a new set of config scripts created to map its events to desired actions.
Unfortunately the wiki is currently down as sourceforge is migrating it from one software to another so I can't point you to the docs on how to do that.
As soon as it goes back up I'll post a link. Are you a programmer? Do you know Python? If yes and yes, you could likely easily adapt existing scripts, however it'll be easier to wait for the wiki to go up.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Recently (very recently) i picked up a book on Python and thought i might put forth some effort into learning to do a few things. That being said, i'm still at the "Hello World" stage at the moment. Perhaps, if nobody beats me to the punch, i'll make this a study project, but i expect that will be a ways on down the road from where i am now.
Thanks for the info and good to see that it should be at least possible to pull off without having to write a lower level driver in C.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Love gizmod. I've got it working beautifully with a PowerMate, but now i would like to see what i could possibly do to make it work with my NuLOOQ. Will gizmod work with the Logitech NuLOOQ "out of the box" (using the generic Linux USB HID driver) or will something special need to be done?
Many Thanks
Vek
Hi Vek,
I actually have no idea! From what I can tell it looks like it should support HID, in which case gizmod will work with it out of the box (although it may require some configuration). But I really don't know.
Do you already have the device? Does it work as a regular USB HID device?
I do have a NuLooq here on my desk. From what i've been told, it will work with the spacenav daemon ( http://spacenav.sourceforge.net/ ), if you modify the code just a bit. The spacenav daemon sees my Nulooq, and lights up one of the LEDs, but aside from that i've not gotten very far, so i cannot say with any degree of certainty that "it work as a regular USB HID".
My "gut" tells me that it does work with basic USB HID however, as i've loaded no separate kernel driver for it and i do not believe that the spacenav daemon is running a user space driver, yet it sees my device.
There is scant info out there about getting the NuLooq to work with linux and since all of the spacenav info I've run across is geared towards the actual 3Dconnex SpaceNav devices (6 axis controllers), i haven't had no success doing anything with it.
The whole point is to get it to work with gizmod (not spacenav), but i gave the spacenav daemon a whirl thinking that i might at least learn something in the process that would be beneficial in getting it to work with gizmod. All that being said however, it looks like i might be a bit out of my league in trying to make this happen (i'm not yet too familiar with xinput concepts and so forth).
Can you paste the output of `gizmod -g` with the nulooq connected?
No prob. I've clipped all the sound card stuff that followed initialization and circled the "navring" on the NuLooq a bit.
GizmoDaemon v3.4 -=- (c) 2007, Tim Burrell <tim.burrell@gmail.com>
Debug Mode Enabled
Registering Devices:
Standard - Directory [input]
Standard - 3Dconnexion NuLOOQ Navigator [event0] vId: 0x46d pId: 0xc640
Keyboard - Das Keyboard [event1] vId: 0x46a pId: 0x48
Mouse - PS/2+USB Mouse [event2] vId: 0x4f3 pId: 0x210
LIRC device node [/dev/lircd] does not exist -- disabling LIRC support
Loading User Scripts:
CatchAllDebug - CatchAll Event Mapping for Testing
PowermateVisualizer - Powermate Visualization Handler [0 Powermates]
KeyboardDefault - Default Fancy Keyboard Event Mapping
PowermateButtonTimeout - ButtonTimeout Powermate Event Mapping
PowermateDefault - Default Powermate Event Mapping
RemoteControl - Remote Control Event Mapping
onEvent: WindowFocus [FocusIn] -- <WindowTitle:xterm> <FormalName:xterm> <Class:XTerm>
Attached to Sound Card [hw:0] -- Audigy 2 Platinum [SB0240P]
onEvent: Standard -- /dev/input/event0 | [EV_REL] c: 0x2 Val: 0x958
onEvent: Standard -- /dev/input/event0 | [EV_KEY] <BTN_TOUCH> c: 0x14a v: 0x1
onEvent: Standard -- /dev/input/event0 | [EV_ABS] c: 0x18 Val: 0xa
onEvent: Standard -- /dev/input/event0 | [EV_REL] c: 0x2 Val: 0x968
onEvent: Standard -- /dev/input/event0 | [EV_ABS] c: 0x18 Val: 0xb
onEvent: Standard -- /dev/input/event0 | [EV_REL] c: 0x2 Val: 0x980
onEvent: Standard -- /dev/input/event0 | [EV_ABS] c: 0x18 Val: 0xc
onEvent: Standard -- /dev/input/event0 | [EV_REL] c: 0x2 Val: 0x996
onEvent: Standard -- /dev/input/event0 | [EV_ABS] c: 0x18 Val: 0xd
onEvent: Standard -- /dev/input/event0 | [EV_REL] c: 0x2 Val: 0x9b0
onEvent: Standard -- /dev/input/event0 | [EV_ABS] c: 0x18 Val: 0xe
onEvent: Standard -- /dev/input/event0 | [EV_REL] c: 0x2 Val: 0x9ce
onEvent: Standard -- /dev/input/event0 | [EV_REL] c: 0x2 Val: 0x9f2
onEvent: Standard -- /dev/input/event0 | [EV_ABS] c: 0x18 Val: 0xf
onEvent: Standard -- /dev/input/event0 | [EV_REL] c: 0x2 Val: 0xa08
Cool. Looks like it should work fine! I think it'll just need a new set of config scripts created to map its events to desired actions.
Unfortunately the wiki is currently down as sourceforge is migrating it from one software to another so I can't point you to the docs on how to do that.
As soon as it goes back up I'll post a link. Are you a programmer? Do you know Python? If yes and yes, you could likely easily adapt existing scripts, however it'll be easier to wait for the wiki to go up.
I'm no coder that's for sure.
Recently (very recently) i picked up a book on Python and thought i might put forth some effort into learning to do a few things. That being said, i'm still at the "Hello World" stage at the moment. Perhaps, if nobody beats me to the punch, i'll make this a study project, but i expect that will be a ways on down the road from where i am now.
Thanks for the info and good to see that it should be at least possible to pull off without having to write a lower level driver in C.