Space Navigator PE Driver Development Thread

[taylorgauss]

Hey mine just arrived. I have read through this post but am unable to find the Xerces-c_2_7.dll file. Can someone help me out. Thanks


EDIT Found it deep in the archives. XML Time

[inh]

Quote: Originally Posted by guizai

thanks INH, your work , CherryBomb's and Sama's have been awesome!!!

INH: I did everything you said, I only have the volume up and down working with the buttons. I used the config that you posted earlier. Does it matter what skin is being used? I will have to sit down and read through the whole config file. I'm prolly just doing something simple wrong. Thanks.

I need to clean up the config.xml a bit, i think. Actually.. In my skin files, i have a lil code to send a message to the app to switch contexts. I use digitalfx 2.0 skin in roadrunner, so when im in the media player or most things, i want it to control the media player, but when im on the games screen, i want it to behave like a mouse =]

let me dig up the code..

[taylorgauss]

inh,

Im using your config file too and have the same controls as guizai. I am not quite sure how to configure that file to my liking. I don't need it to behave as a mouse currently I mostly just want media control. I see where you have the controls in the file. Does positive and negative refer to opposite movements like forward and backward where forward could be up and backward could be down? If i changes the contexts do i need to change the actions as well? Sorry for my lack of knowledge in this area. I hope to learn though! THanks

[inh]

No problem, give me a few mins, and ill post up a better config for you, as well as the way to have it do differnt things. I also try and explain things a lil better

[taylorgauss]

Great I really really appreciate your help, and look forward to your wisdom!

[inh]

Ok, i guess this will be the start of my SpaceNav driver guide.. Attached are two config.xml files. One is the one I am currently using, which was really just a test to get the app to do different things based on where i was in the roadrunner skin. The second is one that will just act as a medai controller all the time.

Now, In the config i use that supports context switching you will see this code, in which it defines the two contexts i use, media controlling and mouse simulting:

Code:

  <deviceContexts>
    <deviceContext name="Media" device="SpaceNavigator">
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 0 pan left/right -->
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 1 pan foreward/back -->
      <axe threshold="500" type="binary" posAction="RR Play/Pause" negAction=""/> <!-- axe 2 push/pull -->
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 3 tilt foreward/back -->      
      <axe threshold="200" type="binary" posAction="RR Prev" negAction="RR Next"/> <!-- axe 4 tilt left/right -->
	  <axe threshold="100" 
        type="exponential"
        startPulse="1"
        endPulse="20"
        posAction="RR Volume Up"
        negAction="RR Volume Down" /> <!-- axe 5 Twist -->
	  <buttons>
        <button downAction="RR Mute"
          upAction="" />
        <button downAction="RR FullVisu"
          upAction="" />
      </buttons>
	</deviceContext>
	<deviceContext name="Mouse" device="SpaceNavigator">
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 0 pan left/right -->
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 1 pan foreward/back -->
      <axe threshold="500" type="binary" posAction="" negAction=""/> <!-- axe 2 push/pull -->
	  <axe simulateMouseMove="y"
        threshold="50"
        divisor="30" />
	  <axe simulateMouseMove="x"
        threshold="50"
        divisor="30" />
	  <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 5 twist -->
	  <buttons>
		<button simulateMouseButton="left" />
		<button simulateMouseButton="right" />
	  </buttons>
	</deviceContext>
  </deviceContexts>

The DeviceContextName is the name of the context, and the device is the interface. You can choose differnt interfaces, but in both configs i only have the space navigator setup, so they will always be the same.

[inh]

Notice this code, for the media context:

Code:

<axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 0 pan left/right -->
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 1 pan foreward/back -->
      <axe threshold="500" type="binary" posAction="RR Play/Pause" negAction=""/> <!-- axe 2 push/pull -->
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 3 tilt foreward/back -->      
      <axe threshold="200" type="binary" posAction="RR Prev" negAction="RR Next"/> <!-- axe 4 tilt left/right -->
	  <axe threshold="100" 
        type="exponential"
        startPulse="1"
        endPulse="20"
        posAction="RR Volume Up"
        negAction="RR Volume Down" /> <!-- axe 5 Twist -->

This defines the actions to be used for each axis of the SN (space navigator.) If you want to just use the fifth axis, which is twisting, then you NEED to have 4 other definitions before it, because that is how the program determines which one is which, since they aren't defined. they just go in order.

posAction and negAction determine what to do when the device is moved that way on each axis. I dont recall which way is which for each control, but generally up is pos, and right is pos.. Just play with the control and you'll figure it out..

Now about the actions. They must be defined in order for the program to know what to do, hence the 'action' section

Code:

  <actions>
    <sendWindowMessage name="Context Up"
      type="CopyData"
      window="SpaceNavigatorDriver"
      message="CONTEXT;Up"/>
    <sendWindowMessage name="Context Down"
      type="CopyData"
      window="SpaceNavigatorDriver"
      message="CONTEXT;Down"/>
    <sendWindowMessage name="RR Volume Up"
      type="CopyData"
      window="RoadRunner"
      message="VOL+"/>
    <sendWindowMessage name="RR Volume Down"
      type="CopyData"
      window="RoadRunner"
      message="VOL-"/>
	  <sendWindowMessage name="RR Mute"
      type="CopyData"
      window="RoadRunner"
      message="MUTE"/>
	  <sendWindowMessage name="RR Play/Pause"
      type="CopyData"
      window="RoadRunner"
      message="PLAY"/>
	  <sendWindowMessage name="RR Next"
      type="CopyData"
      window="RoadRunner"
      message="NEXT"/>
	  <sendWindowMessage name="RR Prev"
      type="CopyData"
      window="RoadRunner"
      message="PREV"/>

Basically, most of them just send a message to RR (roadrunner) the same way you would set a button code.

Context Swtiching:

TO enable the driver to send differnt commands dependig on what skin file is loaded (like the menu, or the audio player, etc) RR needs to send a message to the app. This is done with a few lines of code.

In each skin file you want to support, like menu.skin, games.skin, audioplayer.skin, etc, you need to add this line somewhere in there:

Code:

TMR,1

Then in exectbl.ini you need to add the following code:

Code:

"TIMER","SENDMSG;SpaceNavigatorDriver;CONTEXT;Media",Audio_Player.skin
"TIMER","SENDMSG;SpaceNavigatorDriver;CONTEXT;Media",Menu.skin
"TIMER","SENDMSG;SpaceNavigatorDriver;CONTEXT;Media",Menu2.skin
"TIMER","SENDMSG;SpaceNavigatorDriver;CONTEXT;Mouse",Games.skin

Basically, this says that if Audio_Player.skin is loaded, send a message to the spacenavigatordriver app, which says "CONTEXT;Media" and then the app will look for a context named "Media" and start using it.

When the games skin is loaded, it tells the app to use the mouse context, in which it simulates a mouse =]

I think this covers everything...

myconfig.xml.txt is the one i use, mediaconfig.xml.txt is the one setup to just do media controls. It needs to be renamed config.xml and placed in the same folder as the space nav driver.exe program. Just overwrite the default one.

[incudie]

Wow thanks a lot Inh.

I have a much better understanding of how this thing works.

[taylorgauss]

Yeah, thanks a ton. I really appreciate it.

[inh]

No problem guys. I've been meaning to write a guide since i think im the only person besides the author that understands it

Let me know if you guys get it working =]

[incudie]

Yeah I got your config working right after you posted it (Using it for Volume control and as a mouse under the games section). Only problem I had was clicking. Left/Right buttons on SN did not execute MouseClicks. When I get home tonight I'll try and figure it out then adjust it for my own needs and if it works, post the config for anyone that might be interested. (In my car I'm hoping to use it as the primary input device and have it be a mouse 24/7 but also keep volume control for RR. (Not sure if its possible yet but well see...).

[cherrybomb]

Quote: Originally Posted by inh

No problem guys. I've been meaning to write a guide since i think im the only person besides the author that understands it

Let me know if you guys get it working =]

Frankly, I think you understand it better than I do, at least from a practical standpoint.

I'm too lazy/dense to memorize it all, and do intend to (eventually) write a config app. ;-)

Might actually have a spare moment or two to work on the few things you've mentioned this week. Yay me! :-)

[inh]

You should definatly be able to control volume with a twist and the mouse at the same time, just add the axis commands in there. You'll have to set some of them to not to anything (like where i have them set as digital with no action defined) so that you can set axis 5 for volume.

About the buttons not working, no idea.. Might be something with your system..

Cherrybomb, im keepin my fingers crossed =] I finally figured out where I'm going to mount this thing, so I'm even more motivated

[cherrybomb]

Quote: Originally Posted by inh

Cherrybomb, im keepin my fingers crossed =] I finally figured out where I'm going to mount this thing, so I'm even more motivated

Yeah, I suspect once I actually try to use the thing in my vehicle I'll be more motivated as well.

Gotta get a USB hub installed in my center console, then I can start playing with it.

I'm just so happy to have a working setup finally, I'm a bit afraid to mess with it.. lol

[inh]

hehe i know what ya mean! It's going to be a bit before I have a chance to install it, but just finding a place the bland it in where it would be in reach and look good was a challenge (take a look at some CRX interior pics and you'll see what I mean)

When i get a chance, I think I'm going to crack mine open again and see about changing LED colors, just for kicks. Hell.. maybe puts some RGB LEDs in there.. Now THAT would be awesome..