I know this sounds ridiculous, but that is my conclusion after trying all permutations. My startIndigo.sh script used to be
indigo_server indigo_mount_synscan indigo_ccd_altair indigo_ccd_playerone indigo_focuser_moonlite
when the mount was controlled via USB.
Recently I made a "wifi dongle" for the mount, partly for fun, partly to eliminate a cable. It tested fine when the indigo_mount_synscan driver was the only one loaded, but going back to the normal script (above), as soon as I attempted to connect the Mount it failed with "indigo_mount_synscan[synscan_open:89]: Failed to connect to synscan://192.168.0.244:11880 @ UDP".
So I updated startIndigo, taking drivers out, changing the sequence etc and eventually found that including the altair driver makes it fail. For me, its not a showstopper; I can load altair manually with the control panel after the rest have started (that tested OK this afternoon), but I thought I should report it.
I know this sounds ridiculous, but that is my conclusion after trying all permutations. My startIndigo.sh script used to be
indigo_server indigo_mount_synscan indigo_ccd_altair indigo_ccd_playerone indigo_focuser_moonlitewhen the mount was controlled via USB.
Recently I made a "wifi dongle" for the mount, partly for fun, partly to eliminate a cable. It tested fine when the indigo_mount_synscan driver was the only one loaded, but going back to the normal script (above), as soon as I attempted to connect the Mount it failed with "indigo_mount_synscan[synscan_open:89]: Failed to connect to synscan://192.168.0.244:11880 @ UDP".
So I updated startIndigo, taking drivers out, changing the sequence etc and eventually found that including the altair driver makes it fail. For me, its not a showstopper; I can load altair manually with the control panel after the rest have started (that tested OK this afternoon), but I thought I should report it.