SpaceMouse Enterprise Emulation / Custom Descriptor

[alextrical]

Now that the "SpaceMouse Pro" definition is working nicely and the PR #344 and PR #346 are ready for merge,
I'm looking at moving the work over to the "SpaceMouse Enterprise" due to its larger higher button count and a high degree of crossover with the "SpaceMouse Pro".

I have changed the VID (0x046D or 0x256F) and PID (0xC633) to the ones required for the driver to be successfully identified by the 3Dconnexion driver as a "SpaceMouse Enterprise", and the axis' work as expected, however the button presses are being ignored. I can see that the values are being mapped by HID-Rempapper by viewing the device output with evtest

I can only assume that there is a configuration value that the 3DConnexion driver is checking to verify the device, differently than for the "SpaceMouse Pro" version. What would i need to do with the real device to identify the required information to correctly emulate the "SpaceMouse Enterprise" device?

Below are the button usages for both devices:

Usage	SpaceMouse Pro	SpaceMouse Enterprise
0x00010030	Axis X	Axis X
0x00010031	Axis Y	Axis Y
0x00010032	Axis Z	Axis Z
0x00010033	Axis RX	Axis RX
0x00010034	Axis RY	Axis RY
0x00010035	Axis RZ	Axis RZ
0x00090001	MENU	MENU
0x00090002	FIT	FIT
0x00090003	T	T
0x00090005	R	R
0x00090006	F	F
0x00090009	Roll CW	Roll CW
0x0009000d	1	1
0x0009000e	2	2
0x0009000f	3	3
0x00090010	4	4
0x00090011		5
0x00090012		6
0x00090013		7
0x00090014		8
0x00090015		9
0x00090016		10
0x00090017	ESC	ESC
0x00090018	ALT	ALT
0x00090019	SHIFT	SHIFT
0x0009001a		CTRL
0x0009001b	3D Lock	3D Lock
0x00090024		ENTER
0x00090025		DELETE
0x00090067		V1
0x00090068		V2
0x00090069		V3
0x000900af		TAB
0x000900b0		SPACE

[RustyWraith]

Hello! Great work! I was able to make space mouse emulator using your fork.
Do you know, is there way to use one input device (mouse, trackball) and then spilt mapping to two different emulated devices (space mouse and ordinary mouse)?
Dual Pico setup uses UART to chain inputs, so in theory one should be able to send inputs to another board and split functionality.

[alextrical]

Really glad to hear that it is working for you. I need to get around to cleaning up a pull request so that the developer is happy for it to be merged into the main project. (though I'm not sure how to update a branch here to align with main. Last time i tried it was rejected as it looked like i was trying to pass off their work as my own :( )

Unfortunately I'm not sure how to do this myself. Hopefully @jfedor2 will see this and be able to assist.
Ideally if the branch spacemouse-our-descriptor can be aligned with main, I can make my pull request again with only the changes that I made.

[Muratxx5]

If you send the HID button report descriptions for Enterprise as shown below, the 3DXWARE driver will be able to understand which button was pressed.
(0x1C, 6, "Report 28 — 6B Array (Enterprise Short Press)")
(0x1D, 6, "Report 29 — 6B Array (Enterprise Long Press)")

[alextrical]

@Muratxx5 Thank you for this information. I will look into how i can get HID-Rempapper to send button reports in that format.