VMD-L Mailing List

From: Carsten Olbrich (ocarsten_at_googlemail.com)
Date: Mon Dec 03 2007 - 07:46:02 CST

John,
  the output of "vrpn_print_devices device0_at_localhost" looks like:
     Analog device0_at_localhost:
          0.00, -0.01, 0.00, -0.02, 0.00, 0.00 (6 chans)
     Analog device0_at_localhost:
          0.00, -0.01, 0.00, -0.02, 0.00, 0.00 (6 chans)
     Button device0_at_localhost, number 0 was just pressed
     Button device0_at_localhost, number 0 was just released
     Button device0_at_localhost, number 1 was just pressed
     Button device0_at_localhost, number 1 was just released
   I can not identify a odd behaviour. Should the output have a certain order?
   In my case there it is: x y z psi1 psi2 phi
   I also tried "vrpn_ping device0_at_localhost" which don't print
anything - is this the right behaviour?

Regards,
 Carsten

On Nov 30, 2007 7:32 PM, John Stone <johns_at_ks.uiuc.edu> wrote:
> Carsten,
> Interesting, from what you're telling me, I wonder if the VRPN
> driver has a bug in it. Do you see odd behavior when you use the
> VRPN text client that prints the position/orientation and button status
> of the device? (e.g. when you press a button, do strange things happen
> to the orientation values that are sent from the VRPN server?) If we can
> narrow down where this odd behavior is originating, I suspect it will
> be easy to fix.
>
> Cheers,
> John Stone
> vmd_at_ks.uiuc.edu
>
>
> On Fri, Nov 30, 2007 at 05:58:32PM +0100, Carsten Olbrich wrote:
> > When I push the first button the yellow cone is revered to the right
> > side and the vmd console displays atom information but only if there
> > is atom at the cone end.
> >
> > Regards,
> > Carsten
> >
> > On Nov 30, 2007 5:24 PM, John Stone <johns_at_ks.uiuc.edu> wrote:
> > >
> > > Carsten,
> > > Interesting, the "quatlib" warning you mention is coming from VRPN,
> > > not from code in VMD itself. You may want to report that to the VRPN
> > > mailing list as it's probably a bug of some sort. Regarding the
> > > buttons, what do you get if you use this option:
> > > device spacenavbuttons vrpnbuttons://exciton/device0:0,1,2,3
> > >
> > > Cheers,
> > > John Stone
> > > vmd_at_ks.uiuc.edu
> > >
> > >
> > > On Fri, Nov 30, 2007 at 05:16:46PM +0100, Carsten Olbrich wrote:
> > > > 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
> > > > >
> > >
> > > --
> > >
> > > 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
> > >
> >
> >
> >
> > --
> > With best regards / Mit freundlichen Grüßen
> >
> > Carsten Olbrich
> >
> > -------------------------------------------------------------------------
> > Carsten Olbrich
> > Jacobs University Bremen *
> > Phone: (+49) 421 200 3222
> > Fax: (+49) 421 200 3229
> > Campus Ring 1 (Room III.49b)
> > 28759 Bremen
> > Germany
> > * formerly International University Bremen
> > -------------------------------------------------------------------------
>
> --
>
> 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
>