In reality it was ok for stationery vehicles. The idea being you connected it your laptop and it was acting like an oversized SatNav. There is also a tear-down post on cloudynights forum ( but the pictures are too low res to be of any use.In 2006 I purchased the latest Microsoft Autoroute 2007 which came on DVD and offered a free GPS USB Dongle. Even the firmware download addresses are intact. Celestron is using WiFly firmware without attempting to really hide who is the author. I am not recommending any of this! You can also look inside the windows drivers with the hex editor to find which chipset manufacturer really has written the code - sometimes there are left-over notes from the original manufacturer - people are lazy. Second - try each driver from /lib/modules/your_kernel_version/kernel/drivers/usb/serial/ with the same procedure - it may work but there is remote chance you will brick your scope if it is really badly designed and programed. First - look inside and check what chib they have used - warranty void ( - I would not do that.
On the other hand they have certainly used some off the shelf part - and most if not all have drivers in linux kernel. # I have connected the telescope in Windows8.1. Snd 50779 11 snd_bcm2835,snd_pcm_oss,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_seq_oss,snd_seq_device,snd_mixer_oss
Snd_seq_device 3445 4 snd_seq,snd_rawmidi,snd_seq_oss,snd_seq_midi Snd_seq 52634 6 snd_seq_midi_event,snd_seq_oss,snd_seq_dummy,snd_seq_midi Snd_seq_midi_event 5370 2 snd_seq_oss,snd_seq_midi no result!īluetooth 317981 37 bnep,btbcm,hci_uart,rfcomm pl2303 ttyUSB0: error sending break = -71ĩ. SMC9514 Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub SMSC9512/9514 Fast Ethernet Adapterīus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. (Things gone right!)īus 001 Device 005: ID 1c4f:0026 SiGma Micro Keyboardīus 001 Device 004: ID 09da:c10a A4Tech Co., Ltd.īus 001 Device 007: ID 04cc:0000 ST-Ericssonīus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. I checked the VID and PID is written in the new_id file. In terminal: echo 04cc 0000 > /sys/bus/usb-serial/drivers/pl2303/new_idĥ. I found new_id file in the directory: /sys/bus/usb-serial/drivers/pl2303/new_idĤ. In terminal: modprobe pl2303 (It shows no error message)ģ. As root I put: blacklist cdc_acm in /etc/modprobe.d/acm_nf and /etc/modprobe.d/nfĢ. The commands didn't show any positive result.
0 kommentar(er)
