DocScrutinizer05 changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
<wpwrak> phew. logitech M560, the mouse from hell.
<wpwrak> the middle button switch on the scroll wheel of my M215 was dying. so i looked for a new critter. the M560 looked nice. some people claimed that there would be issues with the middle button since the wheel worked in an unusual way, but then yet others said the little button next to it can act as middle button. so all should be well, right ?
<wpwrak> turns out that logitech implemented some win8-specific mouse-keyboard bastard, with virtually everything hard-wired to hostile functions. of the four more-or-less-crappy solutions/workaround i found on the intertubes, two didn't work, one requires installation of some closed-source tool that does a gazillion of things, maybe including "fixing" the mouse, and the fourth finally worked. needless to say, trying to puzzle it out by lookin
<wpwrak> g at xev, xbindkeys -k or -mk, et al. was hopeless, too.
<DocScrutinizer05> hmmm
<DocScrutinizer05> tried a od -x /dev/* ?
<DocScrutinizer05> err
<DocScrutinizer05> od -x /dev/input/<*>
<DocScrutinizer05> I seen that M560 critter in a blister pack lately and wondered if that "little button next to scrollwheel" wasn't again just a mechanical lever to clutch the pitch snap of the scrollwheel, for "freewheeling" vs "stepping" mode
<DocScrutinizer05> btw weird scrollwheel middle button function and a little pushbutton switch next to it acting like the genuine middle mouse button is exactly the _default_ config of the MX-revolution aka MX5500
<wpwrak> naw, the freewheeling is what you get if you press and release the wheel. press and release again and it is stepped again.
<DocScrutinizer05> also the mentioned "mouse+kbd hybrid" is exactly what MX-Revolution does, I found out by inspecting all devices in /dev/input/ with od. Anyway meanwhile the mapping of scancodes to key events is absolutely fine for the MX
<wpwrak> the button sends some windows curse, mainly as "keyboard"
<DocScrutinizer05> yes, *exactly* what MX-Revo does in _default_ mode. You know, you can config/program the mouse itself
<wpwrak> for the m560 there are contradictory configurations. and the one you get with the "help" of the program that will then interpret the config is wrong. i'm not sure how they accomplish that :)
<wpwrak> yes, with a window-only tool (setpoint) or that closed-source monstrosity (hidpoint). apparently, there's no public programming info
<DocScrutinizer05> maybe you wanna check my revoLUTIONconTROL stuff?
<wpwrak> revoco.c looks interesting. thanks !
<wpwrak> how the heck does one change free-spinning vs. click by software ?
* whitequark is looking at manufacturing ceramics
<wpwrak> pottery ! :)
<whitequark> so i could make an alumina green body using direct coagulation casting
<whitequark> take alumina, ammonia polyacrylate, magnesium oxide, mix, then form
<DocScrutinizer05> wpwrak: revoco -mode ? sth like that
<whitequark> you don't need a press this way
<whitequark> it's a sol-gel process. you can even machine the resulting "gel", it's cohesive enough
<whitequark> then you sinter it as usual
<whitequark> after that you need a ceramic-metal seal. in the industry they sinter a molybdenum manganese oxide powder over the ceramic in the atmosphere of wet hydrogen
<DocScrutinizer05> wpwrak: ^^^
<whitequark> and i want to get involved with literally no part of that process
<wpwrak> DocScrutinizer05: no, i mean: that's a mechanical characteristic. how can software alter that ?
<whitequark> there are nicer things like active brazing alloys
<DocScrutinizer05> it has a little servo built in
<whitequark> you have an AgCuTi alloy, where the Ti content apparently makes the solder eat the ceramic (!) thus wetting it
<whitequark> which actually sounds realistic for a change
<DocScrutinizer05> the Revolution and MX-5500 had. No other mouse since had
<wpwrak> hmm yes, this one feels all mechanical
<whitequark> the annoying part is that they don't sell these alloys so i'll have to manufacture them myself
<wpwrak> whitequark: be thankful that the underlying physics are in place already :)
<whitequark> ... you say so, but i keep googling various steps of this and finding papers from like 2013
<wpwrak> whitequark: that's merely their discovery :)
<DocScrutinizer05> wtf is a "atmosphere of wet hydrogen" ?
<whitequark> hydrogen and water mix
<whitequark> water vapor
<DocScrutinizer05> ooh
<whitequark> it's happening at about 1100 degrees, too
<DocScrutinizer05> :nod:
<whitequark> deeply unpleasant process from every angle
<wpwrak> DocScrutinizer05: alas, i don't see anything about programming buttons functions in revoco.c
<wpwrak> everybody just seems to do this with xbindkeys
<DocScrutinizer05> errm nope, the mouse only delivers keycodes
<DocScrutinizer05> err scancodes
<DocScrutinizer05> you however can profram the action of scrollwheel button
<wpwrak> there's also an obscure udev-based approach but i didn't get that to work
<DocScrutinizer05> progam
<DocScrutinizer05> lemme check what I got for my MX
<DocScrutinizer05> apart from revoco manual=3
<DocScrutinizer05> err nope
<DocScrutinizer05> NOT revoco manual, revoco auto!!
<DocScrutinizer05> I'm using auto=9
<DocScrutinizer05> jr@saturn:~> revoco mode
<DocScrutinizer05> note: MX-5500 support is experimental
<DocScrutinizer05> click-by-click
<DocScrutinizer05> switching to freewheeling when speed of scrolling exceeds "9" (whatever units that is)
wej has quit [Ping timeout: 250 seconds]
<DocScrutinizer05> so _all_ buttons deliver some scancode for me, most in dev/input/mouse, some in /dev/input/event1(?)
<DocScrutinizer05> something is mapping those scancodes to key/mouse events
<wpwrak> that may be udev. there, i saw rules for mapping scan codes. alas, the stuff that should supposedly work for the M560 doesn't
<wpwrak> also, the mouse sends a whole string of such nastiness, so that may trip things, too
<DocScrutinizer05> I just checked my udev stuff and it seems systemd fucked it up
<wpwrak> from poettering, with love :)
<DocScrutinizer05> >:-(
wej has joined #qi-hardware
<DocScrutinizer05> recently found: http://compsoc.man.ac.uk/~shep/pedals.html (please read more than headline, it had useful info for me) and http://homepages.cwi.nl/~aeb/linux/kbd/scancodes-8.html#kccb2
<wpwrak> yes, that's (one of) the system(s) i tried to use. didn't have any effect.
<wpwrak> anyway, i now have the critter halfway satisfactorily mapped
<DocScrutinizer05> /usr/lib/udev/hwdb.d/20-usb-vendor-model.hwdb ::
<DocScrutinizer05> usb:v046DpC51A*
<DocScrutinizer05> ID_MODEL_FROM_DATABASE=MX Revolution/G7 Cordless Mouse
<wpwrak> it goes keystrokes -> xte -> click, so i won't have "middle-click and drag" or such, but maybe that's enough
<DocScrutinizer05> and
<DocScrutinizer05> usb:v046DpC525*
<DocScrutinizer05> ID_MODEL_FROM_DATABASE=MX Revolution Cordless Mouse
<DocScrutinizer05> /usr/lib/udev/rules.d/97-hid2hci.rules
<DocScrutinizer05> has (excerpt): http://privatepaste.com/20a369d943
<DocScrutinizer05> don't ask me wtf is hid2hci
<DocScrutinizer05> need to paste full file, it's too funny http://privatepaste.com/b1544beb09
<DocScrutinizer05> aaah, /usr/lib/udev/hid2hci: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32,BuildID[sha1]=11d11fc14fe19a91e80a9141c767d55bf5b319fd, stripped
<DocScrutinizer05> cool this systemd-udevd
<DocScrutinizer05> http://privatepaste.com/eba65a3fa7 makes sense, this is a BT wireless mouse
<DocScrutinizer05> nfc who does mapping, and where
<DocScrutinizer05> btw I prolly couldn't live without MMB-dragging, used to zoom in pdf viewers et al
<DocScrutinizer05> used to pan in eagle
<DocScrutinizer05> http://privatepaste.com/7b618fc71c xev MMB press + release, if that helps
rodgort has quit [Ping timeout: 245 seconds]
<DocScrutinizer05> and od /dev/input/mouse0 yields: 000c08 for MMB-press and 000000 for MMB-release
jekhor_ has quit [Ping timeout: 240 seconds]
rodgort has joined #qi-hardware
<DocScrutinizer05> btw that small button next to scrollwheel is mapped to XF86_SEARCH(?) on my system/mouse
<DocScrutinizer05> now maybe some savvy people in here can tell me what's the problem when:
<DocScrutinizer05> neo900:~ # write dos1 pts/0
<DocScrutinizer05> write: you have write permission turned off
<DocScrutinizer05> neo900:~ # mesg
<DocScrutinizer05> is y
<DocScrutinizer05> (dos1 as well has mesg y))
<DocScrutinizer05> I've seen suggestions to check /var/log/audit but that's empty
idundidit has quit [Remote host closed the connection]
wpwrak has quit [Ping timeout: 272 seconds]
nicksydney has quit [Ping timeout: 244 seconds]
Haswell has quit [Quit: Saliendo]
jekhor_ has joined #qi-hardware
<eintopf> back
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
jwhitmore has joined #qi-hardware
pcercuei has joined #qi-hardware
pcercuei has quit [Quit: leaving]
pcercuei has joined #qi-hardware
pcercuei has quit [Quit: leaving]
pcercuei has joined #qi-hardware
jwhitmore has quit [Ping timeout: 245 seconds]
xiangfu has joined #qi-hardware
pcercuei has quit [Ping timeout: 252 seconds]
pcercuei has joined #qi-hardware
jekhor_ has quit [Ping timeout: 264 seconds]
jekhor_ has joined #qi-hardware
jekhor_ has quit [Read error: Connection reset by peer]
jekhor_ has joined #qi-hardware
jekhor__ has joined #qi-hardware
jekhor has joined #qi-hardware
jekhor_ has quit [Ping timeout: 256 seconds]
jekhor__ has quit [Ping timeout: 252 seconds]
porchao has joined #qi-hardware
wpwrak has joined #qi-hardware
jwhitmore has joined #qi-hardware
jekhor_ has joined #qi-hardware
jekhor has quit [Ping timeout: 252 seconds]
zeiris has quit [Remote host closed the connection]
zeiris has joined #qi-hardware
jwhitmore has quit [Ping timeout: 264 seconds]
pcercuei has quit [Ping timeout: 265 seconds]
jekhor_ has quit [Ping timeout: 264 seconds]
jekhor_ has joined #qi-hardware
sb0__ has quit [Quit: Leaving]
jekhor_ has quit [Ping timeout: 250 seconds]
FDCX has quit [Remote host closed the connection]
jekhor_ has joined #qi-hardware
Mike25226 has joined #qi-hardware
<Mike25226> Would this be a suitable place to discuss the creation of a powerful 2.4GHz/5GHz PCB Antenna for wifi?
arossdotme has quit [Ping timeout: 256 seconds]
<viric> o
<viric> no
<Mike25226> Any suggestions of where I might be able to find help with my topic? (If i understand correctly what Copyleft hardware is... my topic would be classified as such)
arossdotme has joined #qi-hardware
<whitequark> PCB antennas are fairly standard
<whitequark> look for appnotes from wifi chip vendors
<whitequark> or not even wifi, anything that runs on 2.4