need help enabling a 3DConnexion device in prusa slicer 2.2

quattro

(@quattro)

Eminent Member

need help enabling a 3DConnexion device in prusa slicer 2.2

Debian Testing, udev rules are in place. works in blender after apt install spacenavd.

dmesg:

[ 1893.109622] usb 3-9.1.4: new low-speed USB device number 11 using xhci_hcd
[ 1893.215180] usb 3-9.1.4: New USB device found, idVendor=256f, idProduct=c635, bcdDevice= 4.37
[ 1893.215182] usb 3-9.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1893.215183] usb 3-9.1.4: Product: SpaceMouse Compact
[ 1893.215184] usb 3-9.1.4: Manufacturer: 3Dconnexion
[ 1893.230764] input: 3Dconnexion SpaceMouse Compact as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9.1/3-9.1.4/3-9.1.4:1.0/0003:256F:C635.0006/input/input40
[ 1893.289738] hid-generic 0003:256F:C635.0006: input,hidraw3: USB HID v1.11 Multi-Axis Controller [3Dconnexion SpaceMouse Compact] on usb-0000:00:14.0-9.1.4/input0

lsusb:
Bus 003 Device 011: ID 256f:c635 3Dconnexion SpaceMouse Compact

note: Ctrl+M in prusa slicer does not show anything when done in planar/3d tab.

even:

./PrusaSlicer-2.2.0+linux-x64-202003211856.AppImage --loglevel=5

does not show anything remotely related to hid or hidraw.

any ideas?

Posted : 22/12/2020 1:15 pm

Area51

(@area51)

Member

RE: need help enabling a 3DConnexion device in prusa slicer 2.2

I'm not sure, what the question is.

The Connexion 3D SpaceMouse works in my Linux Mint 19.3 x64 with no special drivers or enabling. PrusaSlicer communicates directly with the device.

Running with loglevel=5 should show if the the SpaceMouse is found by PS.

Have you tried another USB port.

Have a look at my models on Printables.com 😉

Posted : 23/12/2020 11:47 am

quattro

(@quattro)

Eminent Member

Topic starter answered:

RE: need help enabling a 3DConnexion device in prusa slicer 2.2

the question is: "how to make it work?"

I tried other ports, here is the trace output:

quattro@helloit  ~/Desktop  ./PrusaSlicer-2.2.0+linux-x64-202003211856.AppImage --loglevel=5
[2020-12-23 13:23:48.728695] [0x00007f5a3d9bd540] [info] Checking if indices need to be installed from resources...
[2020-12-23 13:23:48.759285] [0x00007f5a3d9bd540] [trace] System language detected (user locales and such): en_US
[2020-12-23 13:23:48.759325] [0x00007f5a3d9bd540] [trace] Switching wxLocales to en_US
[2020-12-23 13:23:49.644054] [0x00007f5a3d9bd540] [info] Undo / Redo snapshot taken: New Project, Undo / Redo stack memory: 0MB Resident memory: 71MB; Shared memory: 45MB; Private memory: 26MB; Peak memory usage: 71MB
[2020-12-23 13:23:51.120480] [0x00007f5a3d9bd540] [debug] TriangleMesh::repair() started
[2020-12-23 13:23:51.121134] [0x00007f5a3d9bd540] [debug] TriangleMesh::repair() finished
[2020-12-23 13:23:51.121144] [0x00007f5a3d9bd540] [trace] TriangleMeshSlicer::require_shared_vertices - start
[2020-12-23 13:23:51.121149] [0x00007f5a3d9bd540] [trace] TriangleMeshSlicer::require_shared_vertices - stl_generate_shared_vertices
[2020-12-23 13:23:51.121201] [0x00007f5a3d9bd540] [trace] TriangleMeshSlicer::require_shared_vertices - end
[2020-12-23 13:23:51.123962] [0x00007f5a3d9bd540] [debug] TriangleMesh::repair() started
[2020-12-23 13:23:51.124248] [0x00007f5a3d9bd540] [debug] TriangleMesh::repair() finished
[2020-12-23 13:23:51.124263] [0x00007f5a3d9bd540] [trace] TriangleMeshSlicer::require_shared_vertices - start
[2020-12-23 13:23:51.124267] [0x00007f5a3d9bd540] [trace] TriangleMeshSlicer::require_shared_vertices - stl_generate_shared_vertices
[2020-12-23 13:23:51.124288] [0x00007f5a3d9bd540] [trace] TriangleMeshSlicer::require_shared_vertices - end
[2020-12-23 13:23:52.519925] [0x00007f5a3d9bd540] [info] Checking for cached configuration updates...
[2020-12-23 13:23:52.520039] [0x00007f5a3d9bd540] [info] Confing bundle not installed for vendor BIBO, skipping: 
[2020-12-23 13:23:52.520066] [0x00007f5a3d9bd540] [info] Confing bundle not installed for vendor Creality, skipping: 
[2020-12-23 13:23:52.520089] [0x00007f5a3d9bd540] [info] Confing bundle not installed for vendor LulzBot, skipping: 
[2020-12-23 13:23:52.525391] [0x00007f5a3d9bd540] [debug] Vendor: Prusa Research, version installed: 1.1.11, version cached: 1.1.11
[2020-12-23 13:23:52.525451] [0x00007f5a3d9bd540] [info] No configuration updates available.
[2020-12-23 13:23:52.697676] [0x00007f5a377fe700] [info] Downloading PrusaSlicer online version from: ` https://files.prusa3d.com/wp-content/uploads/repository/PrusaSlicer-settings-master/live/PrusaSlicer.version` 
* Trying 185.115.1.124...
* TCP_NODELAY set
* Connected to files.prusa3d.com (185.115.1.124) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=files.prusa3d.com
* start date: Nov 12 18:38:40 2020 GMT
* expire date: Feb 10 18:38:40 2021 GMT
* subjectAltName: host "files.prusa3d.com" matched cert's "files.prusa3d.com"
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
> GET /wp-content/uploads/repository/PrusaSlicer-settings-master/live/PrusaSlicer.version HTTP/1.1
Host: files.prusa3d.com
User-Agent: PrusaSlicer/2.2.0+linux-x64
Accept: */*

< HTTP/1.1 200 OK
< Server: nginx
< Date: Wed, 23 Dec 2020 12:23:53 GMT
< Content-Length: 6
< Connection: keep-alive
< Last-Modified: Wed, 23 Dec 2020 12:00:30 GMT
< ETag: "6-5b720700b3824"
< Accept-Ranges: bytes
< 
* Connection #0 to host files.prusa3d.com left intact
[2020-12-23 13:23:53.648725] [0x00007f5a377fe700] [info] Got PrusaSlicer online version: `2.2.0`. Sending to GUI thread...
[2020-12-23 13:23:53.650269] [0x00007f5a377fe700] [info] Syncing configuration cache
[2020-12-23 13:23:53.650298] [0x00007f5a377fe700] [warning] No such vendor: BIBO
[2020-12-23 13:23:53.650306] [0x00007f5a377fe700] [warning] No such vendor: Creality
[2020-12-23 13:23:53.650317] [0x00007f5a377fe700] [warning] No such vendor: LulzBot
[2020-12-23 13:23:53.650326] [0x00007f5a377fe700] [info] Downloading index for vendor: Prusa Research
[2020-12-23 13:23:53.650360] [0x00007f5a377fe700] [info] Get: ` http://files.prusa3d.com/wp-content/uploads/repository/PrusaSlicer-settings-master/live/PrusaResearch//index.idx` 
-> `/home/quattro/.PrusaSlicer/cache/PrusaResearch.idx-update`
via tmp path `/home/quattro/.PrusaSlicer/cache/PrusaResearch.idx-update.121151.download`
* Trying 185.115.1.124...
* TCP_NODELAY set
* Connected to files.prusa3d.com (185.115.1.124) port 80 (#0)
> GET /wp-content/uploads/repository/PrusaSlicer-settings-master/live/PrusaResearch//index.idx HTTP/1.1
Host: files.prusa3d.com
User-Agent: PrusaSlicer/2.2.0+linux-x64
Accept: */*

< HTTP/1.1 301 Moved Permanently
< Server: nginx
< Date: Wed, 23 Dec 2020 12:23:53 GMT
< Content-Type: text/html; charset=iso-8859-1
< Content-Length: 403
< Connection: keep-alive
< Location:  https://files.prusa3d.com/wp-content/uploads/repository/PrusaSlicer-settings-master/live/PrusaResearch/index.idx 
< 
* Ignoring the response-body
* Connection #0 to host files.prusa3d.com left intact
* Issue another request to this URL: 'https://files.prusa3d.com/wp-content/uploads/repository/PrusaSlicer-settings-master/live/PrusaResearch/index.idx'
* Trying 185.115.1.124...
* TCP_NODELAY set
* Connected to files.prusa3d.com (185.115.1.124) port 443 (#1)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=files.prusa3d.com
* start date: Nov 12 18:38:40 2020 GMT
* expire date: Feb 10 18:38:40 2021 GMT
* subjectAltName: host "files.prusa3d.com" matched cert's "files.prusa3d.com"
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
> GET /wp-content/uploads/repository/PrusaSlicer-settings-master/live/PrusaResearch/index.idx HTTP/1.1
Host: files.prusa3d.com
User-Agent: PrusaSlicer/2.2.0+linux-x64
Accept: */*

< HTTP/1.1 200 OK
< Server: nginx
< Date: Wed, 23 Dec 2020 12:23:54 GMT
< Content-Length: 8599
< Connection: keep-alive
< Last-Modified: Wed, 23 Dec 2020 12:00:30 GMT
< ETag: "2197-5b720700b5b93"
< Accept-Ranges: bytes
< 
* Connection #1 to host files.prusa3d.com left intact
[2020-12-23 13:23:54.194637] [0x00007f5a377fe700] [debug] Got index for vendor: Prusa Research: current version: 1.1.11, recommended version: 1.1.11

Posted : 23/12/2020 12:27 pm

Area51

(@area51)

Member

RE: need help enabling a 3DConnexion device in prusa slicer 2.2

When starting PS 2.3.0 RC2 with loglevel=5, I get this listing:

...
[2020-12-23 14:02:17.846422] [0x00007efc83fff700] [warning] No such vendor: LulzBot
[2020-12-23 14:02:18.598068] [0x00007efca2481700] [info] Connected 3DConnexion device:
[2020-12-23 14:02:18.598076] [0x00007efca2481700] [info] Manufacturer/product: 3Dconnexion/SpaceNavigator
[2020-12-23 14:02:18.598080] [0x00007efca2481700] [info] Manufacturer id.....: 1133 (46d)
[2020-12-23 14:02:18.598083] [0x00007efca2481700] [info] Product id..........: 50726 (c626)
...

Have you tried the latest PS version 2.3.0 RC2 - I know there has been changes to SpaceMouse code in this version?

Make sure the rules file is placed correct with the right permissions.

Have a look at my models on Printables.com 😉

Posted : 23/12/2020 1:11 pm

quattro

(@quattro)

Eminent Member

Topic starter answered:

RE: need help enabling a 3DConnexion device in prusa slicer 2.2

it works!

tl;dr: it's hidraw3 not hidraw on debian testing.

2.3 RC2 put out a useful error message:

[2020-12-25 11:47:36.871153] [0x00007f58c8920700] [error] 3DConnexion device cannot be opened: /dev/hidraw3 You may need to update /etc/udev/rules.d

it said /dev/hidraw3 but the sample rules file stated: KERNEL=="hidraw"

so, I copied all the lines and s/hidraw/hidraw3/'d all the copied lines, replugged the mouse, restarted PS and it worked.

Posted : 25/12/2020 10:56 am