Michael F. Toups
Michael F. Toups replied to the topic 'Help with DIY CCD driver' in the forum. 7 years ago

GIlles,

Thanks for the suggestion, it helped.

So I ran the indiserver from the command line and used KStars to connect to it as a remote on 127.0.0.1.

(Yes I did install the udev rules.)

So evidently I have a problem with ftdi connecting to the camera. So this was very bad, but see next block for an improvement,

indiserver -v -m 100 indi_cam84_ccd
2016-11-25T23:41:12: startup: indiserver -v -m 100 indi_cam84_ccd 
2016-11-25T23:41:12: Driver indi_cam84_ccd: pid=8414 rfd=3 wfd=6 efd=7
2016-11-25T23:41:12: listening to port 7624 on fd 4
2016-11-25T23:41:12: Driver indi_cam84_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-11-25T23:41:12: Driver indi_cam84_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-11-25T23:41:12: Driver indi_cam84_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-11-25T23:41:12: Driver indi_cam84_ccd: snooping on CCD Simulator.FILTER_NAME
2016-11-25T23:42:08: Client 0: new arrival from 127.0.0.1:54250 - welcome!
2016-11-25T23:42:18: Driver indi_cam84_ccd: USING LIBFTDI********************************
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error open interface A
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error open interface B
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error set bitbang mode interface B
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error set baud interface A (-3:USB device unavailable)
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error set baud interface B (-3:USB device unavailable)
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi BRA=-1 BRB=-1 TA=5000 TB=5000
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error set latency interface A
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error set latency interface B
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi BRA=-1 BRB=-1 TA=24000 TB=24000
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi interface A read chunksize 4096
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi interface B read chunksize 4096
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi interface A write chunksize 4096
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi interface B write chunksize 4096
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error purge RX interface A
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error purge TX interface A
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error purge RX interface B
2016-11-25T23:42:18: Driver indi_cam84_ccd: libftdi error purge TX interface B
2016-11-25T23:42:18: Driver indi_cam84_ccd: write failed on channel 2)
2016-11-25T23:42:18: Driver indi_cam84_ccd: write failed on channel 2)
2016-11-25T23:42:18: Driver indi_cam84_ccd: write failed on channel 2)
2016-11-25T23:42:18: Driver indi_cam84_ccd: write failed on channel 2)
2016-11-25T23:42:18: Driver indi_cam84_ccd: write failed on channel 2)
2016-11-25T23:42:18: Driver indi_cam84_ccd: write failed on channel 2)
2016-11-25T23:42:18: Driver indi_cam84_ccd: write failed on channel 2)

Starting the indiserver using a sudo was much better but have tons of read errors and the image is garbage. At least values are being returned now.


ccd: USING LIBFTDI********************************
2016-11-26T02:49:27: Driver indi_cam84_ccd: libftdi BRA=1400000 BRB=5600000 TA=5000 TB=5000
2016-11-26T02:49:27: Driver indi_cam84_ccd: libftdi BRA=1400000 BRB=5600000 TA=24000 TB=24000
2016-11-26T02:49:27: Driver indi_cam84_ccd: libftdi interface A read chunksize 4096
2016-11-26T02:49:27: Driver indi_cam84_ccd: libftdi interface B read chunksize 4096
2016-11-26T02:49:27: Driver indi_cam84_ccd: libftdi interface A write chunksize 4096
2016-11-26T02:49:27: Driver indi_cam84_ccd: libftdi interface B write chunksize 4096
2016-11-26T02:49:40: Driver indi_cam84_ccd: libftdi BRA=800000 BRB=3200000 TA=24000 TB=24000
2016-11-26T02:50:09: Driver indi_cam84_ccd: Start exposure bin 1 x 0 y 0 w 3000 h 2000 s 5.000000 l 1
2016-11-26T02:50:10: Driver indi_cam84_ccd: write 15V tick
2016-11-26T02:50:14: Driver indi_cam84_ccd: write exp tick
2016-11-26T02:50:14: Driver indi_cam84_ccd: reading : begin
2016-11-26T02:50:15: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 851<>12000 - 4 / 999 
2016-11-26T02:50:15: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 10667<>12000 - 5 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 7221<>12000 - 6 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 256<>12000 - 7 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 6539<>12000 - 10 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 4608<>12000 - 20 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 3499<>12000 - 28 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 7562<>12000 - 29 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 0<>12000 - 30 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 10038<>12000 - 31 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 6656<>12000 - 32 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 512<>12000 - 36 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 0<>12000 - 37 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 8672<>12000 - 38 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 85<>12000 - 39 / 999 
2016-11-26T02:50:16: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 1792<>12000 - 42 / 999 
2016-11-26T02:50:17: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 6027<>12000 - 45 / 999 
2016-11-26T02:50:17: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 11573<>12000 - 48 / 999 
2016-11-26T02:50:17: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 5888<>12000 - 52 / 999 
2016-11-26T02:50:17: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 7221<>12000 - 57 / 999 
2016-11-26T02:50:17: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 1878<>12000 - 58 / 999 
2016-11-26T02:50:17: Driver indi_cam84_ccd: poseExecute bin==1 readfailed 256<>12000 - 62 / 999 
..........................etc................

Note I need to run about 80 baud or so (at least with the Ascom drivers) or the image is partially or totally corrupted.

Michael

Read More...