Thanks - I'll take a look at that link. In the meantime, yes, I'm aiming with Kstars but I was hoping to be able to use the buttons and stuff for other things. Sort of like my own hand controller. Focus in/out, turn stuff on/off, that kind of thing. Is that not possible? Does it only control mount movement?
And, truth be told, it's a Walmart knock-off, so it's not a real Sony DS4.
Read More...
I have this spare Sony Dualshock 4 Playstation controller lying around. It clicked in my head that it has a USB connection and so I plugged it into my Raspberry Pi running Astroberry to see if I could use it as a joystick. TL;DR: No.
I get this from "usb-devices":
T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 18 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=054c ProdID=09cc Rev=01.00
S: Manufacturer=Sony Interactive Entertainment
S: Product=Wireless Controller
C: #Ifs= 4 Cfg#= 1 Atr=c0 MxPwr=500mA
I: If#=0x0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=(none)
I: If#=0x1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=(none)
I: If#=0x2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=(none)
I: If#=0x3 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
Bus 001 Device 018: ID 054c:09cc Sony Corp. DualShock 4 [CUH-ZCT2x]
[421877.145969] usb 1-1.3: USB disconnect, device number 23
[421901.952654] usb 1-1.2: new full-speed USB device number 28 using xhci_hcd
[421902.089712] usb 1-1.2: New USB device found, idVendor=054c, idProduct=09cc, bcdDevice= 1.00
[421902.089735] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[421902.089753] usb 1-1.2: Product: Wireless Controller
[421902.089771] usb 1-1.2: Manufacturer: Sony Interactive Entertainment
[421903.003267] usb 1-1-port4: Cannot enable. Maybe the USB cable is bad?
[421903.102672] usb 1-1.4: new high-speed USB device number 30 using xhci_hcd
[421904.013294] usb 1-1-port4: Cannot enable. Maybe the USB cable is bad?
[421904.013955] usb 1-1-port4: attempt power cycle
[421905.263268] usb 1-1-port4: Cannot enable. Maybe the USB cable is bad?
[421906.173319] usb 1-1-port4: Cannot enable. Maybe the USB cable is bad?
[421906.173986] usb 1-1-port4: unable to enumerate USB device
The Pegasus Astro Pocket Powerbox (PPB) driver is not 100% to spec, according to the debug logs and Pegasus Astro's information on driver protocol (available at pegasusastro.com/wp-content/uploads/2019...al_Command_Table.pdf). Specifically, for DSLR port control.
I'm having the problem that the PPB is not consistent with what happens with the DSLR power port control and so sometimes it starts and turns the camera on and sometimes it doesn't. I cannot consistently ensure that the camera is being turned on and so have had to bypass this port for now (which is not ideal). So I took a look at the debug information. Here's what the INDI driver sends to turn the camera port of (this is correct):
DEBUG 506.958763 sec : CMD <P2:0>
DEBUG 506.975393 sec : RES <P2:0>
DEBUG 507.453585 sec : CMD <PA>
DEBUG 507.503622 sec : RES <PPB:12.1:0:19.6:42:6.3:0:0:0:0:0>
Here's what it sends to turn it on (which is not correct):
DEBUG 510.563650 sec : CMD <P2:-1>
DEBUG 510.576494 sec : RES <P2:1>
Note that the actual command sent is P2:-1 when it should be P2:1. Now, the response would indicate that it has turned the port on, but the camera does not actually turn on most of the time. I'm happy to fix the driver myself to remove the extra minus sign but the indilib.org web site seems to provide no indication on how to actually submit a bug report (though it suggest that one can do so) nor provide a location for where the source lives. So I'm submitting here.
Read More...