using the SpaceMouse 6-axis input mouse with machinekit
384 views
Skip to first unread message
Michael Haberler
Apr 18, 2015, 7:31:07 AM4/18/15
to Machinekit List
I broke down and bought this http://www.3dconnexion.com/products/spacemouse/spacemousewireless.html?_s=hplmlq2djrvcl9gfthgluhm3l6 right at the Hannover fair for €89.- (fairgrounds special), guessing it might make a neat jogging device - it does
turns out this product works right out of the box; to use the spacemouse with mk, do this:
cat /proc/bus/input/devices
...
I: Bus=0003 Vendor=256f Product=c62e Version=0111
N: Name="3Dconnexion SpaceMouse Wireless"
P: Phys=usb-0000:00:06.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb2/2-2/2-2:1.0/input/input12
U: Uniq=
H: Handlers=event8 js1
-----------------^--------- note number
B: PROP=0
B: EV=2001b
B: KEY=3 0 0 0 0 0 0 0 0
B: ABS=100 3f
B: MSC=10
B: LED=100
now..
halcmd -f -k
halcmd: loadusr hal_input -KRAL 8
--------------------------------^ number from above
and simsalabim:
halcmd: show pin input.0.*
Component Pins:
Comp Inst Type Dir Value Name Epsilon Flags
161 s32 OUT 72 input.0.abs-misc-counts 0
161 s32 IN 0 input.0.abs-misc-flat 0
161 s32 IN 0 input.0.abs-misc-fuzz 0
161 bit OUT FALSE input.0.abs-misc-is-neg 0
161 bit OUT TRUE input.0.abs-misc-is-pos 0
161 float IN 50 input.0.abs-misc-offset 0.000010 0
161 float OUT 0.44 input.0.abs-misc-position 0.000010 0
161 float IN 50 input.0.abs-misc-scale 0.000010 0
161 s32 OUT 0 input.0.abs-rx-counts 0
161 s32 IN 0 input.0.abs-rx-flat 0
161 s32 IN 0 input.0.abs-rx-fuzz 0
161 bit OUT FALSE input.0.abs-rx-is-neg 0
161 bit OUT FALSE input.0.abs-rx-is-pos 0
161 float IN 0 input.0.abs-rx-offset 0.000010 0
161 float OUT 0 input.0.abs-rx-position 0.000010 0
161 float IN 350 input.0.abs-rx-scale 0.000010 0
161 s32 OUT 0 input.0.abs-ry-counts 0
161 s32 IN 0 input.0.abs-ry-flat 0
161 s32 IN 0 input.0.abs-ry-fuzz 0
161 bit OUT FALSE input.0.abs-ry-is-neg 0
161 bit OUT FALSE input.0.abs-ry-is-pos 0
161 float IN 0 input.0.abs-ry-offset 0.000010 0
161 float OUT 0 input.0.abs-ry-position 0.000010 0
161 float IN 350 input.0.abs-ry-scale 0.000010 0
161 s32 OUT 0 input.0.abs-rz-counts 0
161 s32 IN 0 input.0.abs-rz-flat 0
161 s32 IN 0 input.0.abs-rz-fuzz 0
161 bit OUT FALSE input.0.abs-rz-is-neg 0
161 bit OUT FALSE input.0.abs-rz-is-pos 0
161 float IN 0 input.0.abs-rz-offset 0.000010 0
161 float OUT 0 input.0.abs-rz-position 0.000010 0
161 float IN 350 input.0.abs-rz-scale 0.000010 0
161 s32 OUT 0 input.0.abs-x-counts 0
161 s32 IN 0 input.0.abs-x-flat 0
161 s32 IN 0 input.0.abs-x-fuzz 0
161 bit OUT FALSE input.0.abs-x-is-neg 0
161 bit OUT FALSE input.0.abs-x-is-pos 0
161 float IN 0 input.0.abs-x-offset 0.000010 0
161 float OUT 0 input.0.abs-x-position 0.000010 0
161 float IN 350 input.0.abs-x-scale 0.000010 0
161 s32 OUT 0 input.0.abs-y-counts 0
161 s32 IN 0 input.0.abs-y-flat 0
161 s32 IN 0 input.0.abs-y-fuzz 0
161 bit OUT FALSE input.0.abs-y-is-neg 0
161 bit OUT FALSE input.0.abs-y-is-pos 0
161 float IN 0 input.0.abs-y-offset 0.000010 0
161 float OUT 0 input.0.abs-y-position 0.000010 0
161 float IN 350 input.0.abs-y-scale 0.000010 0
161 s32 OUT 0 input.0.abs-z-counts 0
161 s32 IN 0 input.0.abs-z-flat 0
161 s32 IN 0 input.0.abs-z-fuzz 0
161 bit OUT FALSE input.0.abs-z-is-neg 0
161 bit OUT FALSE input.0.abs-z-is-pos 0
161 float IN 0 input.0.abs-z-offset 0.000010 0
161 float OUT 0 input.0.abs-z-position 0.000010 0
161 float IN 350 input.0.abs-z-scale 0.000010 0
161 bit OUT FALSE input.0.btn-0 0
161 bit OUT TRUE input.0.btn-0-not 0
161 bit OUT FALSE input.0.btn-1 0
161 bit OUT TRUE input.0.btn-1-not 0
161 bit IN FALSE input.0.led-misc 0
161 bit IN FALSE input.0.led-misc-invert 0
halcmd:
values change with moving the mouse as expected
you can even wiggle the led:
setp input.0.led-misc 1
setp input.0.led-misc 0
turns out this product works right out of the box; to use the spacemouse with mk, do this:
cat /proc/bus/input/devices
...
I: Bus=0003 Vendor=256f Product=c62e Version=0111
N: Name="3Dconnexion SpaceMouse Wireless"
P: Phys=usb-0000:00:06.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb2/2-2/2-2:1.0/input/input12
U: Uniq=
H: Handlers=event8 js1
-----------------^--------- note number
B: PROP=0
B: EV=2001b
B: KEY=3 0 0 0 0 0 0 0 0
B: ABS=100 3f
B: MSC=10
B: LED=100
now..
halcmd -f -k
halcmd: loadusr hal_input -KRAL 8
--------------------------------^ number from above
and simsalabim:
halcmd: show pin input.0.*
Component Pins:
Comp Inst Type Dir Value Name Epsilon Flags
161 s32 OUT 72 input.0.abs-misc-counts 0
161 s32 IN 0 input.0.abs-misc-flat 0
161 s32 IN 0 input.0.abs-misc-fuzz 0
161 bit OUT FALSE input.0.abs-misc-is-neg 0
161 bit OUT TRUE input.0.abs-misc-is-pos 0
161 float IN 50 input.0.abs-misc-offset 0.000010 0
161 float OUT 0.44 input.0.abs-misc-position 0.000010 0
161 float IN 50 input.0.abs-misc-scale 0.000010 0
161 s32 OUT 0 input.0.abs-rx-counts 0
161 s32 IN 0 input.0.abs-rx-flat 0
161 s32 IN 0 input.0.abs-rx-fuzz 0
161 bit OUT FALSE input.0.abs-rx-is-neg 0
161 bit OUT FALSE input.0.abs-rx-is-pos 0
161 float IN 0 input.0.abs-rx-offset 0.000010 0
161 float OUT 0 input.0.abs-rx-position 0.000010 0
161 float IN 350 input.0.abs-rx-scale 0.000010 0
161 s32 OUT 0 input.0.abs-ry-counts 0
161 s32 IN 0 input.0.abs-ry-flat 0
161 s32 IN 0 input.0.abs-ry-fuzz 0
161 bit OUT FALSE input.0.abs-ry-is-neg 0
161 bit OUT FALSE input.0.abs-ry-is-pos 0
161 float IN 0 input.0.abs-ry-offset 0.000010 0
161 float OUT 0 input.0.abs-ry-position 0.000010 0
161 float IN 350 input.0.abs-ry-scale 0.000010 0
161 s32 OUT 0 input.0.abs-rz-counts 0
161 s32 IN 0 input.0.abs-rz-flat 0
161 s32 IN 0 input.0.abs-rz-fuzz 0
161 bit OUT FALSE input.0.abs-rz-is-neg 0
161 bit OUT FALSE input.0.abs-rz-is-pos 0
161 float IN 0 input.0.abs-rz-offset 0.000010 0
161 float OUT 0 input.0.abs-rz-position 0.000010 0
161 float IN 350 input.0.abs-rz-scale 0.000010 0
161 s32 OUT 0 input.0.abs-x-counts 0
161 s32 IN 0 input.0.abs-x-flat 0
161 s32 IN 0 input.0.abs-x-fuzz 0
161 bit OUT FALSE input.0.abs-x-is-neg 0
161 bit OUT FALSE input.0.abs-x-is-pos 0
161 float IN 0 input.0.abs-x-offset 0.000010 0
161 float OUT 0 input.0.abs-x-position 0.000010 0
161 float IN 350 input.0.abs-x-scale 0.000010 0
161 s32 OUT 0 input.0.abs-y-counts 0
161 s32 IN 0 input.0.abs-y-flat 0
161 s32 IN 0 input.0.abs-y-fuzz 0
161 bit OUT FALSE input.0.abs-y-is-neg 0
161 bit OUT FALSE input.0.abs-y-is-pos 0
161 float IN 0 input.0.abs-y-offset 0.000010 0
161 float OUT 0 input.0.abs-y-position 0.000010 0
161 float IN 350 input.0.abs-y-scale 0.000010 0
161 s32 OUT 0 input.0.abs-z-counts 0
161 s32 IN 0 input.0.abs-z-flat 0
161 s32 IN 0 input.0.abs-z-fuzz 0
161 bit OUT FALSE input.0.abs-z-is-neg 0
161 bit OUT FALSE input.0.abs-z-is-pos 0
161 float IN 0 input.0.abs-z-offset 0.000010 0
161 float OUT 0 input.0.abs-z-position 0.000010 0
161 float IN 350 input.0.abs-z-scale 0.000010 0
161 bit OUT FALSE input.0.btn-0 0
161 bit OUT TRUE input.0.btn-0-not 0
161 bit OUT FALSE input.0.btn-1 0
161 bit OUT TRUE input.0.btn-1-not 0
161 bit IN FALSE input.0.led-misc 0
161 bit IN FALSE input.0.led-misc-invert 0
halcmd:
values change with moving the mouse as expected
you can even wiggle the led:
setp input.0.led-misc 1
setp input.0.led-misc 0
Bas de Bruijn
Apr 18, 2015, 7:42:06 AM4/18/15
to Michael Haberler, machi...@googlegroups.com
That’s nice the mouse works as we hoped!
I’ll try to get mine working.
For interested people, they are working on a “rugged” industrial version (more stiff for those who know the office version of Michaels link).
We saw there one which was assembled in a KUKA robot control.
that would be ultimately suited for our big paws.
Some pics on the rugged version mounted as a demo.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+...@googlegroups.com.
Visit this group at http://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
Claudio Lorini
Apr 18, 2015, 8:15:52 AM4/18/15
to machi...@googlegroups.com
...i hate you both. I'm just 100 euros lighter! ;-)
Doug LaRue
Apr 18, 2015, 1:18:14 PM4/18/15
to machi...@googlegroups.com
I'm cussing at Michael(with a smile) too. I have the 3DConnexion SpaceNavigator for about 7 years collecting dust and just a few of months ago got the open source spacenavd daemon so I could use the SpaceNav with Blender and FreeCAD. I planned today to print a new part cooling duct and rework the JHead fan to add a mount but now have to fit in playing with the SpaceNav on the other printer too.
BTW, when I started on re-Braining my Mini Kossel with Machinekit, I'd told Charles I wanted to use a Wii Nunchuck with Machinekit for jogging and to control a claw on the delta effector for demo's and to make a game for my kid. This might trump that for a bit.
Doug
Bas de Bruijn
Apr 18, 2015, 3:16:01 PM4/18/15
to Claudio Lorini, machi...@googlegroups.com
Heh heh heh, wait another few months and you hate us more because you then might be another 100 lighter. They hopefully have the rugged version, where they plan (told us) on making it "hollow shaft".
...i hate you both. I'm just 100 euros lighter! ;-)
--
Bas de Bruijn
Apr 20, 2015, 5:05:40 AM4/20/15
to machi...@googlegroups.com, Michael Haberler, Doug LaRue, Claudio Lorini
I replicated this with my notebook mouse, I also have an “old” spacepilot with a lot of buttons :)
I had to change permissions on my /dev/input/input1
next step is to wire it up for jogging :)
machinekit@bbb-mk-02:~$ cat /proc/bus/input/devices
I: Bus=0003 Vendor=046d Product=c628 Version=0111
N: Name="3Dconnexion SpaceNavigator for Notebooks"
P: Phys=usb-musb-hdrc.1.auto-1/input0
S: Sysfs=/devices/ocp.3/47400000.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input1
U: Uniq=
H: Handlers=event1
B: PROP=0
B: EV=20017
B: KEY=3 0 0 0 0 0 0 0 0
B: REL=3f
B: MSC=10
B: LED=100
machinekit@bbb-mk-02:~$ ls -la /dev/input/event1
crw------- 1 root root 13, 65 Apr 20 08:37 /dev/input/event1
machinekit@bbb-mk-02:~$ sudo chmod go+rw /dev/input/event1
machinekit@bbb-mk-02:~$ ls -la /dev/input/event1
crw-rw-rw- 1 root root 13, 65 Apr 20 08:37 /dev/input/event1
machinekit@bbb-mk-02:~$ halrun
msgd:0 stopped
rtapi:0 stopped
halcmd: loadusr hal_input -KRAL 1
halcmd: show pin
Component Pins:
Owner Type Dir Value Name Epsilon Flags
71 bit OUT FALSE input.0.btn-0 0
71 bit OUT TRUE input.0.btn-0-not 0
71 bit OUT FALSE input.0.btn-1 0
71 bit OUT TRUE input.0.btn-1-not 0
71 bit IN FALSE input.0.led-misc 0
71 bit IN FALSE input.0.led-misc-invert 0
71 s32 OUT 22608 input.0.rel-rx-counts 0
71 float OUT 22608 input.0.rel-rx-position 0.000010 0
71 bit IN FALSE input.0.rel-rx-reset 0
71 float IN 1 input.0.rel-rx-scale 0.000010 0
71 s32 OUT -4937 input.0.rel-ry-counts 0
71 float OUT -4937 input.0.rel-ry-position 0.000010 0
71 bit IN FALSE input.0.rel-ry-reset 0
71 float IN 1 input.0.rel-ry-scale 0.000010 0
71 s32 OUT -686 input.0.rel-rz-counts 0
71 float OUT -686 input.0.rel-rz-position 0.000010 0
71 bit IN FALSE input.0.rel-rz-reset 0
71 float IN 1 input.0.rel-rz-scale 0.000010 0
71 s32 OUT 296 input.0.rel-x-counts 0
71 float OUT 296 input.0.rel-x-position 0.000010 0
71 bit IN FALSE input.0.rel-x-reset 0
71 float IN 1 input.0.rel-x-scale 0.000010 0
71 s32 OUT -40806 input.0.rel-y-counts 0
71 float OUT -40806 input.0.rel-y-position 0.000010 0
71 bit IN FALSE input.0.rel-y-reset 0
71 float IN 1 input.0.rel-y-scale 0.000010 0
71 s32 OUT 3738 input.0.rel-z-counts 0
71 float OUT 3738 input.0.rel-z-position 0.000010 0
71 bit IN FALSE input.0.rel-z-reset 0
71 float IN 1 input.0.rel-z-scale 0.000010 0
On 18 Apr 2015, at 13:31, Michael Haberler <mai...@mah.priv.at> wrote:
Michael Haberler
Apr 20, 2015, 5:31:16 AM4/20/15
to Bas de Bruijn, machi...@googlegroups.com, Doug LaRue, Claudio Lorini
let's steal from https://code.google.com/p/liquid-galaxy/wiki/LinuxSpaceNavigator :
add this file as /etc/udev/rules.d/80-spacemouse.rules
# cat /proc/bus/input/devices
#...
#I: Bus=0003 Vendor=256f Product=c62e Version=0111
#N: Name="3Dconnexion SpaceMouse Wireless"
#P: Phys=usb-musb-hdrc.1.auto-1/input0
#S: Sysfs=/devices/ocp.3/47400000.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input1
##U: Uniq=
#H: Handlers=js0 event1
#B: PROP=0
#B: EV=2001b
##B: KEY=3 0 0 0 0 0 0 0 0
#B: ABS=3f
#B: MSC=10
#B: LED=100
KERNEL=="event[0-9]*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c62[68e]", MODE="0664", SYMLINK+="input/spacemouse"
leave mouse plugged in, reboot, you should have /dev/input/spacemouse mode 644 which can be passed to hal_input
add this file as /etc/udev/rules.d/80-spacemouse.rules
# cat /proc/bus/input/devices
#...
#I: Bus=0003 Vendor=256f Product=c62e Version=0111
#N: Name="3Dconnexion SpaceMouse Wireless"
#P: Phys=usb-musb-hdrc.1.auto-1/input0
#S: Sysfs=/devices/ocp.3/47400000.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input1
##U: Uniq=
#H: Handlers=js0 event1
#B: PROP=0
#B: EV=2001b
##B: KEY=3 0 0 0 0 0 0 0 0
#B: ABS=3f
#B: MSC=10
#B: LED=100
KERNEL=="event[0-9]*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c62[68e]", MODE="0664", SYMLINK+="input/spacemouse"
leave mouse plugged in, reboot, you should have /dev/input/spacemouse mode 644 which can be passed to hal_input
Michael Haberler
Apr 20, 2015, 3:37:15 PM4/20/15
to Michael Haberler, Bas de Bruijn, machi...@googlegroups.com, Doug LaRue, Claudio Lorini
ahum. Note to self: read manpages - the one of hal_input is pretty clear. There were permission problems.
the proper line for the file in /etc/udev/rules.d is:
KERNEL=="event[0-9]*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c62[68e]", GROUP="plugdev"
this will make /dev/input/event1 660, assuming the mk user is in group plugdev this works
mah@epig:~$ halrun
..
lohalcmd: loadusr hal_input -KRAL 1
74 s32 IN 0 input.0.ab
...
the proper line for the file in /etc/udev/rules.d is:
KERNEL=="event[0-9]*", ATTRS{idVendor}=="256f", ATTRS{idProduct}=="c62[68e]", GROUP="plugdev"
this will make /dev/input/event1 660, assuming the mk user is in group plugdev this works
mah@epig:~$ halrun
..
lohalcmd: loadusr hal_input -KRAL 1
halcmd: show pin
Component Pins:
Component Pins:
Comp Inst Type Dir Value Name Epsilon Flags
74 s32 OUT 0 input.0.abs-rx-counts 0
74 s32 IN 0 input.0.ab
...
Bas de Bruijn
Apr 20, 2015, 3:52:57 PM4/20/15
to Michael Haberler, machi...@googlegroups.com, Doug LaRue, Claudio Lorini
here’s my situation:
I now use the 3D connection spacepilot looooooots of buttons.
machinekit@beaglebone:~$ cat /proc/bus/input/devices
I: Bus=0003 Vendor=046d Product=c625 Version=0110
N: Name="3Dconnexion SpacePilot"
P: Phys=usb-musb-hdrc.1.auto-1/input0
S: Sysfs=/devices/ocp.3/47400000.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input1
U: Uniq=
H: Handlers=mouse0 event1
B: PROP=0
B: EV=20017
B: KEY=1fffff 0 0 0 0 0 0 0 0
B: REL=3f
B: MSC=10
B: LED=540
I had to use add line below to
KERNEL=="event[0-9]*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c625", MODE="0664", GROUP=“plugdev”
after reboot everything worked w/o the rights issue, see:
machinekit@beaglebone:~$ ls -l /dev/input/
total 0
drwxr-xr-x 2 root root 80 Apr 13 06:50 by-id
drwxr-xr-x 2 root root 100 Apr 13 06:50 by-path
crw------- 1 root root 13, 64 Apr 13 06:50 event0
crw-rw-r-T 1 root plugdev 13, 65 Apr 13 06:50 event1
crw------- 1 root root 13, 63 Apr 13 06:50 mice
crw------- 1 root root 13, 32 Apr 13 06:50 mouse0
machinekit@beaglebone:~$ halrun
msgd:0 stopped
rtapi:0 stopped
halcmd: loadusr hal_input -KRAL 1
halcmd: show pin
Component Pins:
Comp Inst Type Dir Value Name Epsilon Flags
74 bit OUT FALSE input.0.btn-0 0
74 bit OUT TRUE input.0.btn-0-not 0
74 bit OUT FALSE input.0.btn-1 0
74 bit OUT TRUE input.0.btn-1-not 0
etcetera
74 bit OUT FALSE input.0.btn-9 0
74 bit OUT TRUE input.0.btn-9-not 0
74 bit OUT FALSE input.0.btn-extra 0
74 bit OUT TRUE input.0.btn-extra-not 0
74 bit OUT FALSE input.0.btn-middle 0
74 bit OUT TRUE input.0.btn-middle-not 0
74 bit OUT FALSE input.0.btn-mouse 0
74 bit OUT TRUE input.0.btn-mouse-not 0
74 bit OUT FALSE input.0.btn-right 0
74 bit OUT TRUE input.0.btn-right-not 0
74 bit OUT FALSE input.0.btn-side 0
74 bit OUT TRUE input.0.btn-side-not 0
74 bit IN FALSE input.0.led-charging 0
74 bit IN FALSE input.0.led-charging-invert 0
74 bit IN FALSE input.0.led-misc 0
74 bit IN FALSE input.0.led-misc-invert 0
74 bit IN FALSE input.0.led-suspend 0
74 bit IN FALSE input.0.led-suspend-invert 0
74 s32 OUT 0 input.0.rel-rx-counts 0
etcetera
74 float IN 1 input.0.rel-y-scale 0.000010
74 s32 OUT 0 input.0.rel-z-counts 0
74 float OUT 0 input.0.rel-z-position 0.000010
74 bit IN FALSE input.0.rel-z-reset 0
74 float IN 1 input.0.rel-z-scale 0.000010
John Morris
Apr 20, 2015, 4:22:38 PM4/20/15
to Doug LaRue, machi...@googlegroups.com
On 04/18/2015 12:18 PM, Doug LaRue wrote:
> I'm cussing at Michael(with a smile) too. I have the 3DConnexion
> SpaceNavigator for about 7 years collecting dust and just a few of
> months ago got the open source spacenavd daemon so I could use the
> SpaceNav with Blender and FreeCAD.
package(s), despite knowing little about it. Are you attaching to
Machinekit through the daemon?
I've got the US$11, serial port version. If the MK interface is through
spacenavd, then I'm golden. ;)
John
> I planned today to print a new part
> cooling duct and rework the JHead fan to add a mount but now have to fit
> in playing with the SpaceNav on the other printer too.
>
> BTW, when I started on re-Braining my Mini Kossel with Machinekit, I'd
> told Charles I wanted to use a Wii Nunchuck with Machinekit for jogging
> and to control a claw on the delta effector for demo's and to make a
> game for my kid. This might trump that for a bit.
>
> Doug
>
> --
> website: http://www.machinekit.io blog: http://blog.machinekit.io
> github: https://github.com/machinekit
> ---
> You received this message because you are subscribed to the Google
> Groups "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to machinekit+...@googlegroups.com
> <mailto:machinekit+...@googlegroups.com>.
> website: http://www.machinekit.io blog: http://blog.machinekit.io
> github: https://github.com/machinekit
> ---
> You received this message because you are subscribed to the Google
> Groups "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to machinekit+...@googlegroups.com
Doug LaRue
Apr 20, 2015, 4:31:48 PM4/20/15
to machi...@googlegroups.com, doug....@gmail.com
On Monday, April 20, 2015 at 1:22:38 PM UTC-7, John Morris wrote:
On 04/18/2015 12:18 PM, Doug LaRue wrote:
> I'm cussing at Michael(with a smile) too. I have the 3DConnexion
> SpaceNavigator for about 7 years collecting dust and just a few of
> months ago got the open source spacenavd daemon so I could use the
> SpaceNav with Blender and FreeCAD.
I'm actually a co-maintainer of the Fedora spacenavd (and FreeCAD)
package(s), despite knowing little about it. Are you attaching to
Machinekit through the daemon?
I've got the US$11, serial port version. If the MK interface is through
spacenavd, then I'm golden. ;)
John
First off, thank you John for doing that support and especailly in FreeCAD.
As for these guys using the daemon, they are not and are doing directly to the udev event I/O of the OS. I mentioned the spacenavd but then realized on the embedded BBB, unless they are also running a GUI on it and some other spaceNav type software hooking the spacenav directly to Machinekit is probably ok.
Because the BBB doesn't really have a good graphics system, running any GL based software which would/could use spacenavd would be very painfully slow.
Again, thanks tons for working on spacenavd and the FreeCAD interface.
Doug
Bas de Bruijn
Apr 21, 2015, 3:28:44 PM4/21/15
to machi...@googlegroups.com
Hi Guys,
I’ve just made a video using 3 axes of the Spacepilot to run 3 motors with Machinekit.
They're just simply wired so that the 3D mouse inputs the motor command (position).
https://youtu.be/m0OeaTcWTZA
Ultimate fun!
Cheers,
Bas
I’ve just made a video using 3 axes of the Spacepilot to run 3 motors with Machinekit.
They're just simply wired so that the 3D mouse inputs the motor command (position).
https://youtu.be/m0OeaTcWTZA
Ultimate fun!
Cheers,
Bas
Doug LaRue
Apr 21, 2015, 4:45:49 PM4/21/15
to machi...@googlegroups.com
On Tuesday, April 21, 2015 at 12:28:44 PM UTC-7, Bas de Bruijn wrote:
Hi Guys,
I’ve just made a video using 3 axes of the Spacepilot to run 3 motors with Machinekit.
They're just simply wired so that the 3D mouse inputs the motor command (position).
https://youtu.be/m0OeaTcWTZA
cool but definitely needs some desensitization. That and you need more buttons on that mouse. LOL You were not kidding when you said it had lots of buttons. Mine has 2. :(
Doug
Bas de Bruijn
Apr 21, 2015, 4:51:18 PM4/21/15
to Doug LaRue, machi...@googlegroups.com
absolutely true. There are some scale values to scale the “end” position from the counts. This is a scale of 40. I just picked up the mouse (tilting it) and the gravity pulling the knob made the motors move. Really sensitive device.
btw, next to a massive amount of buttons I also have LED’s and a LCD screen. Havent dug into the screen. Would be nice to display pin values on that :)
Doug
Viesturs Lācis
Apr 21, 2015, 5:47:08 PM4/21/15
to machi...@googlegroups.com
On Tuesday, April 21, 2015 at 10:28:44 PM UTC+3, Bas de Bruijn wrote:
Hi Guys,
I’ve just made a video using 3 axes of the Spacepilot to run 3 motors with Machinekit.
They're just simply wired so that the 3D mouse inputs the motor command (position).
https://youtu.be/m0OeaTcWTZA
You had my curiousity, now you have my attention! I have the same exact model of Spacepilot, so I would be very grateful, if you could share the config. Pretty, please!
Ryan Carlyle
Apr 21, 2015, 10:15:49 PM4/21/15
to machi...@googlegroups.com
Best jog controller ever!
Michael Haberler
Apr 22, 2015, 6:07:40 AM4/22/15
to Ryan Carlyle, Machinekit List, ralf.b...@megatron.de, stefan...@3dconnexion.com
well since this seems to become the jogging device du jour:
3Dconnexion has a channel partner for industrial applications, like machine jogging: http://www.megatron.de/en/category/linear-sensors.html; they were present at the booth as well and very helpful
I understand they might even have a hollow-shaft version which would make it an interesting teach-in device at the spindle
if interested in significant numbers, you'd might to want to talk to Ralf Buskies:
Am 22.04.2015 um 04:15 schrieb Ryan Carlyle <temp...@gmail.com>:
Best jog controller ever!
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+...@googlegroups.com.
Alexander Rössler
Apr 22, 2015, 7:58:44 AM4/22/15
to Bas de Bruijn, machi...@googlegroups.com
Very sensitive. You probably need to scale the input down to make it
controllable by normal humans.
--
Alexander
controllable by normal humans.
Alexander
Bas de Bruijn
Apr 22, 2015, 2:45:53 PM4/22/15
to <machinekit@googlegroups.com>
For those interested, I added the config here.
I ran a normal config and just pit the input in between. Good enough for me for now.
so please see these lines:
and the identical changes for the other axes.
I also added an issue as a reminder for myself to put this thread into the docs. But my current available time does not allow me to do right away.
Bas de Bruijn
Apr 22, 2015, 2:48:19 PM4/22/15
to machi...@googlegroups.com
On 22 Apr 2015, at 20:45, Bas de Bruijn <b...@basdebruijn.com> wrote:
For those interested, I added the config here.I ran a normal config and just pit the input in between. Good enough for me for now.so please see these lines:
correction on the this one, should be one row upwards. below the correct one
https://gist.github.com/luminize/6ea90bb83c21feb7b331#file-bebopr-bridge-3dmouse-hal-L75-L76
https://gist.github.com/luminize/6ea90bb83c21feb7b331#file-bebopr-bridge-3dmouse-hal-L75-L76
Bas de Bruijn
Apr 24, 2015, 7:14:39 AM4/24/15
to machi...@googlegroups.com
For those with Wacom tablets:
I connected my Wacom tablet during lunch to my Debian Weezy VM, and repeated the exercise with the wacom plugged in.
result:
http://pastebin.com/G0XCTPB8
It doesn’t work out of the box on a beagle bone because it doesn’t get recognised as an input device. That’s a driver thing though.
Cheers,
Bas
I connected my Wacom tablet during lunch to my Debian Weezy VM, and repeated the exercise with the wacom plugged in.
result:
http://pastebin.com/G0XCTPB8
It doesn’t work out of the box on a beagle bone because it doesn’t get recognised as an input device. That’s a driver thing though.
Cheers,
Bas
> --
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
> ---
> You received this message because you are subscribed to the Google Groups "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+...@googlegroups.com.
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
> ---
> You received this message because you are subscribed to the Google Groups "Machinekit" group.
Reply all
Reply to author
Forward
0 new messages