SUCCESS!!!
While looking for indi_synscan_telescope I found this:
/usr/bin/indi_skywatcherAltAzMount
.... so I did the following:
indiserver -vv indi_skywatcherAltAzMount
.... and it conencted first time and all works a treat. I obviously haven't tried it under the stars yet, but it seems to be doing the right things!!
So in summary it does work with a FTDI 232R chip with a 10k resistor between 5v and Rx, AND using the indi_synscanAltAzMount driver.
Thanks guys! 
- now I can get on with my Python script for "Moon-Raker!"
Read More...
I now have a 10k pullup resistor fitted to the Rx line and using Minicom on the Pi I can see valid responses from the mount ....however,
Still no joy connecting using indi_eqmod_telescope (exactly the same) and indi_synscan_telescope. The latter spits out one Tx when the connect button in KStars is pressed. But it always says the following in the KStars window:
2019-03-28T15:38:12: [WARNING] Synscan Mount not responding
2019-03-28T15:38:12: [WARNING] Communication with /dev/ttyUSB0 @ 9600 failed. Starting Auto Search...
2019-03-28T15:38:12: [WARNING] Synscan Mount not responding
Using minicom on /dev/ttyUSB0 I get correct responses from the mount.
One last question. I do not have indi_synscanlegacy_telescope on my PiZero. How would I add that to the drivers?
Read More...
This morning I connected my Linux PC directly to the mount (using the FTDI USB/TTL adaptor) and from a terminal sent :j1<0D> and received back only the same each time. In fact any command is simply echoed by the mount - obviously because of the Tx/Rx being wired together... but nothing back from the mount.
Then something weird happened.....
I connected my logic analyser to the Rx line to see what was happening and hey-presto I started to see (in the terminal) valid responses from the mount.
From sending :j1<0d> I received :j1<0d> followed by =000080 , which I believe is the current Az position. Other commands also produced valid responses. As soon as I disconnected the LA it stopped responding.
I think there is a triggering problem on the front-end of the FTDI USB interface. I see you have an CH340G device.....I need to lay my hands on one of those too and see if that is maybe the secret! (I have a prolific one as well...but that is not working either).
Chip-chip-chip away...
Thanks for the support guys - I'm sure we will get there!
Read More...
I am creating a mount/scope set-up that simply finds the moon. The intention is that all there is int eh system is the Mount / scope / PiZero (GPS). The mount will be in a perminent location and therefore the pointing model should be ready for action. All the user does is turn on the system and the mount (via a Python script which I have already written using the emulator) will unpark and move to the moon's position (calculated using AstroPy). That's it.
So that means no WiFi...other than for configuration and editing of the Python script. No KStars...again other than for possible maintenance.
BUT. I still cannot make it work!
You say indi-synscan and synscan-legacy..... The only drivers I see in my 1.7.4 install are the following....in fact this is what I type in the PiZero terminal:
indiserver -vv indi_synscan_telescope
BUT this does not work.....it simply reports (in KStars) "Synscan Mount Not Responding"
I get a little further with the following:
indiserver -vv indi_eqmod_telescope
That produces the following:
2019-03-27T17:09:07: [ERROR] Error when disconnecting mount -> Invalid response to command :f1 - Reply :f1
2019-03-27T17:09:06: [WARNING] Warning: Invalid command -> Invalid response to command :j2 - Reply :j2
2019-03-27T17:09:05: [WARNING] Warning: Invalid command -> Invalid response to command :j1 - Reply :j1
2019-03-27T17:09:04: [WARNING] Warning: Invalid command -> Invalid response to command :j2 - Reply :j2
2019-03-27T17:09:03: [WARNING] Warning: Invalid command -> Invalid response to command :j1 - Reply :j1
2019-03-27T17:09:02: [WARNING] Warning: Invalid command -> Invalid response to command :j1 - Reply :j1
2019-03-27T17:09:01: [WARNING] Warning: Invalid command -> Invalid response to command :j1 - Reply :j1
2019-03-27T17:09:00: [WARNING] Warning: Invalid command -> Invalid response to command :j1 - Reply :j1
2019-03-27T17:08:59: [WARNING] Warning: Invalid command -> Invalid response to command :j1 - Reply :j1
2019-03-27T17:08:53: [WARNING] Warning: Invalid command -> Invalid response to command :j1 - Reply :j1
2019-03-27T17:08:47: [INFO] updateLocation: long = -1.083 lat = 53.95
2019-03-27T17:08:47: [INFO] Setting UTC Time to 2019-03-27T15:34:08, Offset 0
2019-03-27T17:08:47: [WARNING] Warning: Invalid command -> Invalid response to command :a1 - Reply :a1
2019-03-27T17:08:47: [INFO] EQMod Mount is online.
2019-03-27T17:08:47: [WARNING] Warning: Invalid command -> Invalid response to command :e1 - Reply :e1
2019-03-27T17:08:44: [INFO] updateLocation: long = -1.083 lat = 53.95
2019-03-27T17:08:44: [INFO] Setting UTC Time to 2019-03-27T15:34:08, Offset 0
2019-03-27T17:08:44: [ERROR] Error when disconnecting mount -> Invalid response to command :f1 - Reply :f1
2019-03-27T17:08:44: [ERROR] Error: Communication failed -> tty read failed, check connection: Timeout error
2019-03-27T17:08:39: [INFO] EQMod Mount is online.
2019-03-27T17:08:39: [WARNING] Warning: Invalid command -> Invalid response to command :e1 - Reply :e1
I do not see anything about synscan legacy!?
Read More...
Firstly - many thanks for replying. I was beginning to think I was the only one trying to do this.
It sounds like scenario 2 is the same as mine. I am using an FTDI USB to TTL convertor wired like you (GND, TX, RX) to the mount. I have soldered the connection directly to the small PCB in the mount (the one next to the RJ12) where you can CLEARLY see the PCB track shorting out the Tx & Rx wires together. That is whatt he driver complains about in the log window in KStars (same as you - running on a seperate PC... connected to the PiZero over WiFi).
Just to clarify which INDI driver you are using. I tried it with indi_eqmod)telescope.
Are you using a different driver?
Read More...
I am fully conversant with INDI on the Pi and have recently been using the Python wrapper to create some cool automation scripts for my EQ6. INDI Rocks!
I have a new project where I want a very simple PiZero controlling a SW AZ-Goto mount. The older silver/black one. I made a direct cable with FTDI chip but indi_eqmod_telescope complains about reflected commands (Tx/Rx short on MC001 motor controller?)
I have done a ton of reading online and lots of testing, including looking at the TX/Rx on my scope where I can see the MC001 motor control board responding to the EQMOD commands, but the EQMOD driver seems to be confused by seeing the reflected command comming back. Sent=:j1<0d> Recvd=:j1<0d>
Obviously the standard Synscan handset I have will talk to the mount fine, however I want to dispense with that and talk directly. Am I mad?? Is what I want to do possible?
Many thanks
Roo, UK
Read More...
I have a project where I want a very simple PiZero controlling a SW AZ-Goto mount. The older silve/black one. I made a direct cable with FTDI chip... Show more