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.

stargazine_ep24_banner.thumb.jpg.56e65b9c9549c15ed3f06e146fc5f5f1.jpg

thomasv

Fornax Lightrack II experiments

Recommended Posts

I've picked up a second hand Lightrack II recently, so was keen to test it. My plan was to use the guiding assistant in PHD to get a graph of the tracking performance, but initially the mount wouldn't move. After a search, I had to modify the guiding cable that came with the mount, as it was wired up 'the other way' to the one required for QHY5L. After that it calibrated fine and could run the test. Below is a 22min graph of the unguided performance, while it's not within the 2" peak-to-peak quoted, it's still pretty good. 

Next I've tried it with a canon 300mm lens (unguided again), the picture is a crop of a 10min exposure, slightly eggy, but again pretty happy with that. 

log1a.thumb.PNG.04b61079e93ea9b3c1d3f5dc3cbb632b.PNG 

10min_col_50p_crop2.jpg.4deb3617db5af6cc561815d116ea9046.jpg

setup.jpg.9f987168c073c083645dee2335f0763f.jpg

  • Like 1

Share this post


Link to post
Share on other sites

Interesting.

I was wondering how I can guide my Lightrack II

I own an Orion StarShoot autoguiding pro (I believe the camera is a QHY5L-II).

- How to set up PHD2 (since you can only guide in RA, special setup is required?)

- what modifications do I have to make to the cable?

Also, I just returned my Fornax wedge and ordered the skywatcher wedge, how do you like it? I am a bit worried it could be a bit light. What is the total weight of your gear mounted on the lightrack?

Can you make fine ajustments in ALT with little efforts?

Share this post


Link to post
Share on other sites

Hi, sorry for the delayed reaction, I'm away on holiday.

There are two options for the ST-4 cable wiring and the cable supplied by Fornax is configured as per SBIGs convention. Basically you need to reverse the connections, what was pin 1 becomes pin 6, etc. Of course this is easiest done at the headphone type connector end, make a note of the original colours of wires going to the 3 pins, and reconnect as described. Normally you can see what order the coloured wires are at the st4 end.

Sorry I don't have my pc with me, so can't tell you exactly where, but you do have to tick the RA guide only option, I think it's on the main screen.

The skywatcher wedge is ok with the lightrack, i'm sure the fornax wedge is better, I just didn't want to remorgage the house for one. With a bit of practice you can make fine adjustments, the trick is not to loosen the locking screw completely, just enought to be able to move with the adjustment screw. I think my setup is about 4kg.

 

post-33644-0-32286000-1517100710_thumb.jpg

Share this post


Link to post
Share on other sites

Thank you for your reply. I just got my autoguider camera ORION SAGPRO (which I understand is a QHY camera)

I have connected the camera St-4 to the lightrack with the provided RJ12-3.5mm jack, in PHD selected "on camera" mount and set DEC guiding to "off" in advanced settings.

Upon opening the 3.5mm jack I see the following three cables:

image.png.d6051580a950f286502a8537d8df0853.png

According to the SBIG scheme  they are :

- blue: +DEC 

- yellow : -DEC

- black: No connection

And therefore to make it compatible with QHY wiring they must become:

 

- blue --> purple

- yellow --> green

- black --> red

 

Now, the doubt I have is why would they control DEC if the Lightrack only moves in RA and DEC is disabled in PHD????

 

image.png.5aef587186a848a2190d4e56712f61d2.png

 

Share this post


Link to post
Share on other sites

Hi,

I wonder if the colours are assigned in the reverse order to the pin numbers. I'm not actually sure what the picture represent, is it the connector on the cable, or the socket, and looking from which direction.

I've checked, I did what you describe:

- blue --> purple

- yellow --> green

- black --> red

You can test if the PHD commands get through to the mount by using the manual guide option and listening to the sound of the mount. The high pitched whistle doesn't change, but there is a lower frequency noise (murmur) that changes frequency slightly if you issue left/right commands.

 

Share this post


Link to post
Share on other sites

Modification done

- blue --> purple

- yellow --> green

- black --> red

I can hear the "murmur" changing frequancy when I hit East/West in Manual Mode (you have to push your ear to the Lightrack case to hear the murmur)

I will try guiding as soon as the sky clears up a bit

Share this post


Link to post
Share on other sites

Sounds promising, great. Would be interested in seeing a graph of the tracking performance with PHD's guiding assistant like I posted above to compare against the performance of my 2nd hand unit.

 

Share this post


Link to post
Share on other sites

How did you get the above graph for unguided performance? I am new to PHD and want to make sure we compare apples to apples

Share this post


Link to post
Share on other sites

You start guiding as normal, which will first calibrate the system. Then tools --> guiding assistant will open a new window, disable 'dec backlash' measurement and start. This will then disable the guiding and uses the guide camera to measure the accuracy of tracking, leave it running for about 20mins. Make sure that the camera type (pixel size) and guide scope focal length are set correctly under PHD general settings, so that the results in arcsec are correct.

You will need to download a separate piece of SW called PHD log viewer to then analyze and display the guiding performance. This takes the PHD guide log file as input, which is normally in your Documents folder /PHD. 

 

Share this post


Link to post
Share on other sites

I did a test tonight. The test is done with a 350mm imaging scope, which is balanced. Polar alignment with Polemaster

guiding camera pixel size and scope focal length are set in PHD2, DEC guiding is set to OFF in advanced settings

Below the logs

Guided: it seems that guiding is working properly, since the trend-line is responding to guiding pulses. I can get nice round stars at 4min subs exposure

image.thumb.png.f1de04805ef712417f9c9539c8f7aa0a.png

 

However, after starting Guiding assistant, I get this weird graph below:

image.png.0d7f04a182ca133ebe10752da92139da.png

 

I don't think the lightack has such bad behavior as I can take nice 2 min subs  unguided, so, what is going on?

Share this post


Link to post
Share on other sites

I wonder if something has moved at 22:17, the trace is nice and horizontal before, then there is a jump and then iit starts to diverge, indicating probably that polar alignment has shifted? Don't know what it could be, tripod or wedge, would you mind posting a picture of the setup?

 

 

Share this post


Link to post
Share on other sites

The first part with horizontal Trace is the guided part, as soon as I start guiding assistant and guiding is stopped, there you get the jump and the Trace starts to diverge.

 

Share this post


Link to post
Share on other sites

OK, sorry. Can you tick the DEC box near the bottom to display the DEC trace. If both are drifting away in a straight line, I would have thought it's ought to be a polar alignment problem. I thought that guiding assistant gave an estimate of the polar alignment error, but I now can't find it anywhere in the log viewer, so I think it may only display it while it's running live.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By pete_81
      Hi guys,
      With new mount and upgraded scope features, now looking to venture into imaging.
      Before I start, I'm not looking to get feedback on polar alignment, mono guidecam, better imaging cameras, etc; this is more a 'dummies guide' setup discussion! I'm not expecting to get great images at this stage, just more the options available, getting over some issues, so that I can jump outside on a clear night with an ideal, foolproof(!), setup for either imaging or visual as time would permit and what may work best for me. As you may guess from the topic name, I'm a mac user (Macbook Pro) and would rather keep to this if possible (whilst I do have Windows (and Ubuntu) via parallels, I'd rather not use these).
      I've got a setup which has worked well for visual, and obviously want to have a couple of 'staple' setups that I can use depending on expectations of night observing or imaging. So far, the best one for me has been the Skywatcher Wifi Synscan controller, which has worked a treat with my Android phone - I use the Synscan app to complete alignment and GOTO stars/planets/DSO etc, or Stellarium_plus after completing alignment. This removes the need for the Synscan Handset and any USB cables to the mount altogether. But I don't know if this will work for guiding.
      That then brings me to my issue on mac - connecting USB(A) between Macbook and Handset, I've attempted to control the mount through Stellarium. Trying each of the available connections (/dev/tty.usbsetial-1420, /dev/cu.usbsetial-1420, and just for sake of it, the /dev/tty.Bluetooth-Incoming-Port and /dev/cu.Bluetooth-Incoming-Port) in the dropdown menu under DeviceSettings/SerialPort, I cannot get the mount to connect (well, more like selecting the telescope and clicking the "Start" on the TelescopeControl just results in the spinning icon and I have to Force-Quit Stellarium and start again with the same result each time. Annoyingly (for fellow mac users!), Parallels/Windows/Stellarium connects and controls the mount fine! As the mount is the newer "pro" type, I also have a USB connection directly under the hand-controller RJ45 and AutoGuider ST4 sockets, but using this still results in the same issue. Another issue I have seen is that when I unplug the USB from the computer when connected to the handset, the date on the controller jumps significantly - for example, last night at ~23:30, I was transported through the local wormhole galaxy to Jan 2048 according to Synscan! Obviously unplugging isn't going to happen during a genuine session, but just wondering if this is a possible issue somewhere?!
      Any other mac users connecting USB directly to the SW 'Pro' mounts?
      Software wise, would folks generally suggest steering away from Stellarium towards KStars or SkySafari(Plus) for controlling the mount?
      Can the Wifi dongle be used for controlling mount from computer (any OS) or do I need to go USB either to handset or directly to mount?
      Is there an issue in using Mac USB to the telescope compared to 'straight' Windows (i.e. PC/laptop with Windows instead of virtual)?
      Anyway, back to topic... I've a Nikon DSLR to use for primary camera at this stage, which would be triggered independently from guiding software. PHD2 is my hopeful choice of guiding software (is EKOS with KStars similar?), with T7C guide-camera on 240mm f/4 guidescope, and at this stage, I can confirm PHD2 at least connects to the camera on OS-X. There is an ST4 port on the camera, but having read several topics, I think I want to pulse-guide directly - is this correct or is ST4 best for this setup? This sorta comes back to software and connections - my understanding is one of the following cable setups for guiding (as a minimum) :
      Guiding-camera => USB(A) => Macbook => PHD2 => USB(A) => SynscanHandset => AZEQ6
      Guiding-camera => USB(A) => Macbook => PHD2 => USB(A) => AZEQ6
      Guiding-camera => USB(A) => Macbook => PHD2 => Wifi => SynscaWifi Adapter on AZEQ6
      [using ST4: ST4_on_AZEQ6 => Guiding-camera => USB(A) => Macbook => PHD2] (no additional connections needed if ST4 is used)
      Additionally, I'd like to use an observatory package, say Stellarium/KStars/SkySafari, to select objects and drive the mount, then use guiding software to keep good 'tracking'.
      Where in this train does EQMac fit in, or when is it used?
      What about the 2019 addition to EQMod (ASCOM Alpaca)? Can this be used or is it already in other packages?!
      For Windows users, how does EQMod fit in (if I go down route of getting Windows laptop for controlling things, is the setup similar to above?
      There may be bits in the above that repeat, and for that, I'm sorry, just want to get across the message that I'm new to the guiding but haven't quite settled down into the software/hardware I'm expecting to use for 'goto' and 'guiding'
      TLDR:
      For a mac user, what setup and software are folks using for guiding and observatory softwares for the newer USB-on-mount 'AZEQ6/EQ6-R Pro' mounts from SW?
    • By Sidecontrol
      Has anyone had any experience installing ASCOM driver onto the EQM 35 pros SynScan hand controller for using with PHD2?  I'm watching a tutorial using PHD2 and the chap is using ASCOM for connecting his computer to his guide camera instead of using a cable.  So the computer becomes the middle man instead of the mount.
      Thanks,
      Mark
    • By astrosathya
      Recently I had belt modded my HEQ5-PRO and last night i gave it a full run and i was absolutely stunned to say the least about the guiding results I achieved. I was left wondering if its even too good to be true! 
      Below are Before and After images of guiding.


    • By khulzad
      Hi all,
      First of all mine english is not so good so sorry for that.
      I am a new to astrophotography. And my setup is
      Mount          : Skywatcher EQM 35 PRO
      Tube             : Skywatcher Explorer 150PDS (newtonian)
      Camera         : Canon 550D
      Guide scope : Svbony 60mm compact guide scope
      Guide cam    : Svbony SV105
      I know my setup is weak and cheap but for now I have them (budged problem  )
      I started the hobby at May and I took some photos that not bad for beggining. I reached 60-90 seconds without guiding.
       

      After that I thought that the time for starting improve the guiding and I bought guiding scope and cam. I know the cam is not for guiding but it was cheap, and I am planing to change it  with mono guide cam (like zwo asi120 mono) at next months.
      But my first experience for PHD2 was terrible.

      I've detected some errors and tried to fix them.
      First thing there was a unbalancing. I mounted the guide scope on the position of finder scope which is very close to edge of the main scope.

      So I fixed it (after the night I tried to guide with PHD2) and put it on the bracelet (over and middle of the main tube)
      And second thing was that there is a backlash and I tried to fix it too. I opened to gear of dec and adjusted to gear mesh.
      Except them the alignment was not so good because location was in the city (bortle scale 9) and I haven't got finder scope as you know. So I am not sure that if the stars (3 star alignment method) are correct because with nacked eye I could't see them. Next time I will do better alignment with finder for sure.
      After them I am planing to try next weekend again. But before that I need your advises to eliminate the problems which I couldn't detect or I don't how to fix them.
      For example I can not see any pulse for RA on the graph what does it mean and how can I fix it.
      And also I am not sure if there is any problem with ascom. There is no option in the drop list for EQM 35 PRO. So I choose ASCOM.SkyWatcher.Telescope and I downloaded/installed ascom driver from webpage of skywatcher.

      Thank you
      PHD2_DebugLog_2020-09-21_100115.txt PHD2_GuideLog_2020-09-21_100115.txt
    • By knobby
      Hi All, wondered if you could help me make sense of this ... new HEQ5 - belt modded by FLO, all feels good, minuscule backlash but strange guiding.
      Admittedly first time using it but baffled.
      Failed calibration see image below and guiding seemed to be Ra and Dec following each other.
      Stars look ok ish (@ 1500 mm )
      Needle galaxy is poor as only about 10 mins each in RGB
      note - it was hazy and did keep losing star in OAG
       
      Thanks for looking
      PHD2_DebugLog_2020-05-19_221608.txt
       



×
×
  • Create New...

Important Information

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