Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.



  • Content Count

  • Joined

  • Last visited

Community Reputation

144 Excellent

1 Follower

About SteveBz

  • Rank
    Proto Star

Profile Information

  • Location
    West Sussex
  1. Are you on Windows or Linux? On linux, it's just treated as a webcam as in /dev/video0 etc. On windows I don't know, but I guess it's the same. It was probably made for a microscope and converted for a telescope. It's not terribly sensitive, but you can use it for a guidescope on brighter stars. You can also get planetary images, although they're not great. I upgraded to a QHY5 which is much much better. You can also use a zwo asi120mm for 100 odd quid off alibaba express. Good luck, Steve.
  2. Just found a Celestron manual with 9 settings. Maybe I just need to test it.
  3. Have you done this? You've got quite a lot of Newtonians. Is there much difference between them? I have a 114 mm and 200 mm and the difference is so huge I only use the smaller one for outreach and testing. Steve.
  4. As I read it, it's slew until I tell you to stop. I've attached the full protocol, but as I understand it, the first three parameters are "fixed rate slew", "positive or negative" and "RA/DEC", not necessarily in that order. Then you give it a rate. Like this: The text says: For fixed rates, simply use a value from 1-9 (or 0 to stop) to mimic the equivalent hand control rates. Note: in most configurations, issuing the slew commands will override (or conflict with) the tracking mode of the mount. Hence it is always best to disable tracking first using the Tracking Commands, issue the slew command, and then re-enable tracking. The main exception to this is when tracking equatorially - the fixed rate slews at 1 or 2 will not override tracking. This can be useful to simulate auto-guiding. But the rates are: So there seems to be a tension between the two definitions over what happens for zero. I may just test it, but it's hard to measure rates like .5x and 1x, without a vernier calliper. Regards Steve synscanserialcommunicationprotocol_version33.pdf
  5. Hi Dr Juju, You said that before, and I'd love to. It just a long process. I think you saw my previous attempt, but it's on pause until I can get something working to look upwards. Then I'll have some spare time. Regards, Steve
  6. Hi Guys, I'm trying to automate my scope and I've upgraded from a Skywatcher Enhanced handset controlled by an Arduino to a goto Synscan controlled by a Raspberry Pi with Python. I have control of the handset now, but I'm having difficulty interpreting the manual. It says send the slew command (eg 'P' +chr(2)+chr(16)+chr(36)+chr(rate))or something like that. Rate is supposed to be 1-9 or zero for stop, but there are 10 rates with 0 =. 5x. How does that work? Does it mean 0.5x is not available? I'm a bit thrown. Regards, Steve.
  7. Excellent! I could never get Mate 16.04 to work.
  8. It looks about the same with more ports and memory. Is that what you see? The CPU doesn't look any different.
  9. I have the RPi 3b+ and struggle to put it under stress. I have been thinking of moving plate-solving to it, as it would speed things up. Maybe that's what the RPi 4 is for.
  10. Nice. OK. After a lot of building work my pc ended up on the wrong side of the house, so I installed a RPi on the scope-shed side and I talk to that with a python program. Everything in the scope-shed is driven by an Arduino. The RPi really just acts as a WiFi relay. Now the eq5 with Handset is being replaced with eq5 goto, the Arduino needs updating, but I could run a usb from the RPi to the Synscan. S
  11. So the one I'm doing, because it seems to be the least additional work, is using the handset as a relay. It seems to use a simple st4 type connection with three wires. Tx, Rx and Gnd. I just want Synscan's definition of these to be the same as Arduino's S
  12. Are you saying you can't see the point of directly driving the motors, or connecting the Arduino to the handset. The former I probably agree, and the latter I could be pursuaded of, but it's the latter I'm doing.
  13. This is the one I have. synscanserialcommunicationprotocol_version33(2).pdf The commands look quite simple as long as I don't blow it up with the wrong voltage to the wrong pins. S
  14. Yes, that what I started to do, now I'm going to ignore the a4988s and go straight to Synscan. The box I've built has the Bluetooth hc-05 which means I can run it without cables. Plus it has all the i2c stuff like sky temperature monitors and so forth. So it's quite useful in its own right. I could however bypass it with a USB cable with a MAX232 to 6p6c cable and that would give me the same thing, just an extra cable. And who'd notice with the jungle of cables we all have! I'll post the Synscan docs I have. S
  15. Hi Dr J, Well it started that way when my Starwatcher handset blew up, but then I was offered the chance to use a Synscan Goto, and I wanted to modify the Arduino project for the synscan. If it was easier to put the handset I a drawer I would. I guess then I'd need an eight pin ethernet cable and ports. Would it otherwise be easier? What do you think? Regards Steve.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.