VMD-L Mailing List

From: Carsten Olbrich (ocarsten_at_googlemail.com)
Date: Fri Nov 30 2007 - 10:16:46 CST

Hi John,

I managed to recompile VMD (without the spaceball option).
But the result nearly the same :-(
except the warnings of conflicting versions of vrpn.

It seams that the second button "works" if I use
   device spacenavbuttons vrpnbuttons://exciton/device0:1
instead of device spacenavbuttons vrpnbuttons://exciton/device0
in .vmdsensors.
In this case "works" means that if I push this button a atom
information text is printed in the vmd console
but only if one changes the offset positon otherwise the vmd console
displays continuously:
quatlib: q_vec_normalize: vector has 0 magnitude.

Regards,
 Carsten

On Nov 29, 2007 7:16 PM, John Stone <johns_at_ks.uiuc.edu> wrote:
> Hi,
> I'd suggest using the VRPN-based driver since you're using Linux.
> In order to use VMD with the bleeding-edge version of VRPN, you're going
> to need to recompile VMD from source, against the latest VRPN build.
> While VRPN client/server minor version differences often don't pose a
> problem, given that you're not seeing any motion in VMD, something may
> be incompatible between the versions. Let me know if you need more help
> getting this working.
>
> Cheers,
> John Stone
> vmd_at_ks.uiuc.edu
>
>
> On Thu, Nov 29, 2007 at 06:23:01PM +0100, Carsten Olbrich wrote:
> > Dear all,
> >
> > we bought a SpaceNavigator (PE) (3DConnexion) and I still try to get
> > this device working in Linux (SuseLinux 10.1).
> > It works fine in Windows with the corresponding driver and I don't
> > need to configure anything corresponding to VMD.
> > In Linux it looks different:
> > - I managed to install the driver and all example programs, which
> > are distributed with the driver, work fine but not VMD.
> > Therefor I added following to .vmdsensors: device spacenav
> > sballtracker://local//proc/bus/usb/005/036
> > But VMD doesn't respond on moving the device.
> > - I also tried to use VRPN (Version 7.14) with this configuration:
> > vrpn_3DConnexion_Navigator device0
> > The client "vrpn_print_devices" program can connect to the
> > vrpn_server and prints for instance
> >
> > Analog device0_at_localhost:
> > 0.09, 0.07, -0.47, 0.19, -0.17, 0.16 (6 chans)
> > Analog device0_at_localhost:
> > 0.01, 0.07, -0.47, 0.19, -0.17, 0.16 (6 chans)
> > Analog device0_at_localhost:
> > 0.01, 0.07, -0.07, 0.19, -0.17, 0.16 (6 chans)
> >
> > if I move the device.
> > Then I added following to .vmdsensors:
> > device spacenavtracker vrpntracker://exciton/device0
> > device spacenavbuttons vrpnbuttons://exciton/device0
> > The chose the tracker and the buttons in the TOOLS menu but
> > nothing happens except the message:
> >
> > vrpn: Connection request received: 127.0.0.2 45092
> > vrpn_Connection: VRPN Note: minor version number doesn't match:
> > (prefer 'vrpn: ver. 07.14', got 'vrpn: ver. 07.03 0'). This is not
> > normally a problem.
> >
> > I hope someone might help me to get our SpaceNavigator working.
> >
> > Regards,
> > Carsten
>
> --
> NIH Resource for Macromolecular Modeling and Bioinformatics
> Beckman Institute for Advanced Science and Technology
> University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801
> Email: johns_at_ks.uiuc.edu Phone: 217-244-3349
> WWW: http://www.ks.uiuc.edu/~johns/ Fax: 217-244-6078
>