OK, time to get started then. Can't wait forever. It would be nice to have the protocol, etc to speed this up, but it appears not to be an option.
Dmesg gives this when I connect the focuser:
44.703687] usb 2-126.96.36.199: new full-speed USB device number 7 using ehci-pci
[ 44.799169] usb 2-188.8.131.52: New USB device found, idVendor=0925, idProduct=7001
[ 44.799171] usb 2-184.108.40.206: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 44.799173] usb 2-220.127.116.11: Product: Generic HID
[ 44.799174] usb 2-18.104.22.168: Manufacturer: SharpSky Pro
[ 44.802145] hid-generic 0003:0925:7001.0002: hiddev0,hidraw1: USB HID v1.11 Device [SharpSky Pro Generic HID] on usb-0000:00:1d.0-22.214.171.124/input0
It looks like it sets up 2 things under /dev -> /dev/hidraw1 and /dev/usb/hiddev0.
Under Windows, I ran Wireshark to capture some USB traffic. I've never used Wireshark before so I don't know what I am doing with it yet.
I've attached some captured output files that I'll start working on trying to understand. One file is just connecting the focuser only. The other has connection and moving the focuser back and forth. I've attached in case someone else can understand the data and/or tell me if I'm capturing the right stuff.
It looks like the focuser is recognized as a hid device, not a serial device. I have experience with programming a driver for the latter, based on the serial over usb communication (UART). That's how quantum filter wheel was developed based on serial commands sniffed with wireshark.
For HID device, It might be the case that you will not get anywhere further with this without specification of the communication protocol.
| Orion CT8 | Askar FRA 400 | NEQ6 (hypermod) | Atik 460EX | ASI 1600 | ASI 120MM | Atik EFW2