Jump to content

sgl_imaging_challenge_6_banner_jupiter_2021.jpg.eacb9f0c2f90fdaafda890646b3fc199.jpg

 

 

DIY EQ2 Economy Autoguiding


bobro
 Share

Recommended Posts

OK, so the frac arrived yesterday. It's a Celestron 50 very poor condition but 4.99 + p&p off eBay.   Here it is:

tmp_9048-20170216_0903202002341446.jpg

Not only is it in bad nick, but it has been further disabled with (removable) baffles. Nonetheless I stuck a camera in the eyepiece holder and connected to lin_guide.  All systems go, I can see the image in lin_guide but it can't handle HD  guiding so need to step down to some other resolution which I can do with v4l2-ctl.

The issue now is that my ST-4 interface is Arduino so I need to update the lin_guide driver protocol.

Back soon.

Steve.

Edited by SteveBz
Size image
  • Like 1
Link to comment
Share on other sites

14 hours ago, SteveBz said:

OK, so the frac arrived

Great progress Steve obtaining a guidescope and getting Lin_guider to run. Will the Bosma TCE-200 be used as a guide cam? I don't understand your comment 'ST-4 interface is Arduino'. Is the Arduino the receiver for ST-4 signals and controls the (stepper) motors in the mount?

Bob

 

  • Like 1
Link to comment
Share on other sites

6 hours ago, bobro said:

I don't understand your comment 'ST-4 interface is Arduino'. Is the Arduino the receiver for ST-4 signals and controls the (stepper) motors in the mount?

More or less.  I built this:

https://hackaday.io/project/4386-arduino-st4-telescope-control

Which uses an Arduino to steer the mount.  Actually I used it because I built a small radio telescope (see my profile picture) by putting a 1.3 m satellite dish (£5 from eBay, natch) on my EQ5 and I wanted to be able to do a sky-scan with it (built in Python on my laptop).  However, now I've got an Arduino attached to the scope it can be upgraded do all sorts of other things too, eg remote focuser control, dew controller, fan controller, remote shutter controller for DSLR, tell me if it's raining on the scope, pick up the millivolt output of the satellite dish etc etc etc.

Here is the main Arduino hub, the LEDS illuminate with the relevant steering movements:

2017-02-17 06.42.09.jpg

And if you scroll down the Hackerday article to the comments, there is a link to a lin_guider file on dropbox that someone has modified to link lin_guider to this Arduino control.  I've compiled it in and now it runs.  There are a couple of run-time error messages that I'm just working through, but I hope to be testing guiding with this on the next clear night.

Regards

Steve.

  • Like 1
Link to comment
Share on other sites

Update. I have got Lin Guider working on the Pi now (PI 3) thanks to your information. I am using a webcam that I got off amazon ages ago that fits into a 1.25 eyepiece for astro viewing. It seems to work and I am planning on connecting this to a small refractor for my guide scope.

However every time it start it says Pulse driver is not initialized, guiding is not possible. I have installed all the packages in the list and the firmware too.

Do you know why I am getting this message and also how do I choose which GPIO pins to have it output signal to.

Thanks in advance for your advice

Link to comment
Share on other sites

Looks like you have similar issues to what I found. My workaround was to create a small script to initialise the GPIO pins - run before starting Lin_guider. In addition I modified the program slightly. When I get back from work later today I'll look out the changes I made and let you know adder001. I've found, once running, the program to be very reliable.

You're almost there!

Bob

  • Like 1
Link to comment
Share on other sites

1 hour ago, adder001 said:

Update. I have got Lin Guider working on the Pi now (PI 3) thanks to your information. I am using a webcam that I got off amazon ages ago that fits into a 1.25 eyepiece for astro viewing. It seems to work and I am planning on connecting this to a small refractor for my guide scope.

However every time it start it says Pulse driver is not initialized, guiding is not possible. I have installed all the packages in the list and the firmware too.

Do you know why I am getting this message and also how do I choose which GPIO pins to have it output signal to.

Thanks in advance for your advice

The pulse driver for me was a permissions problem and was resolved temporarily by running as root.  The correct answer is to set up group memberships and rules in er... udev?? which I haven't done yet.

Good luck.

  • Like 1
Link to comment
Share on other sites

Baaah, I thought I had it. I changed to root and Lin Guider came on with no error messages. Great I thought, then I noticed it had put the camera to NULL. No matter what I set or change it makes me restart LinGuider and then the next session it still shows NULL as camera even though I changed it to webcam.

If I log in as normal and type ./lin_guider then it sees my webcam and I get images shown on the screen but I also get the Pulse driver error message.

This is so weird its as if when logged in as root it cant read the usb port or something

BTW the way I changed to root was

sudo chown root lin_guider
sudo chmod +s lin_guider

which seemed to work

I also tried another way using sudo su to make me a superuser and it also displays root in the prompt area when I do this.

Very strange, Im puzzled now

Link to comment
Share on other sites

On 18/02/2017 at 17:48, bobro said:

Here is a link to the small mods I made to get Lin_guider to run for me. Note that I know little about Linux or the Raspberry PI, so treat the mod as a bit of a bodge. See the notes file for an explanation. Let me know how it goes.

http://guidingfiles.web.fastmail.co.uk/

Many thanks for your information thats very helpful, I really appreciate it. I am so close, The problem is definitely with Lin Guider somewhere as no matter what I do I still get the guiding error.

I decided to go right back to the beginning with a fresh install of raspbian, then reinstalled lin guider then the firmware did all the sudo apt-get updates, ugrades etc.

Ran as root, still no joy. The camera works fine though, just still no guiding. I even copied and pasted the modified code into my io cpp file, still no joy.

I know that the GPIO's are working because if I use wiring Pi and talk directly through terminal to the GPIO pins or use Python to make a small GPIO blink programme I can get a test LED to light or switch on or off depending on what I programme it to do.

Also the guider script works on its own as well (if i modify it I can make the LED connected on GPIO 22 switch on or off)

So this is a real puzzle now

Link to comment
Share on other sites

5 hours ago, SteveBz said:

Did you see this?  He's coded the whole thing from scratch in Python:

http://sy2000.blogspot.co.uk/2014/05/star-autoguide-with-rpi-5-python-code.html

I've run it and it works (although I don't have an RPi).  I'm trying to hack it for my Arduino.

Regards

Steve

Cheers, thats interesting I will have a look at that, Thanks

Link to comment
Share on other sites

32 minutes ago, adder001 said:

So this is a real puzzle now

If I don't run the 'Guider' script file before starting Lin_guider I get the same error message about the pulse driver. Are you running the script first? It can be run in Terminal mode to see the output. My Lin_guider version is V4.1.0.

Link to comment
Share on other sites

yeah I run it first, followed by lin guider. But something interesting is happening where I have to modify the text in the file from high to 1 or it just errors.

I wrote my own script just to confirm that it works and my version only seems to work if I use digits rather than words eg., 1 instead of high. This was tested by connecting an LED to GPIO 22

Link to comment
Share on other sites

I suspect the issue is down to the (very confusing) PI GPIO pinout between revisions. If you still have a problem after trying 4.1.0, I suggest asking a question in another part of this forum. Someone is bound to know!

Link to comment
Share on other sites

I really like your project and progress. I am actually doing something similar, but with the use of an eq1 mount. I had the economy drive as well but I opted toward using a separate stepper motor that accepts microstepping. If your interested, here is my project currently:

 

 http://www.astronomyforum.net/atm-diy-telescope-making-forum/230117-eq1-ra-only-autoguider.html

 

I also have the forum post that gave me the arduino coding if its any use for you:

 

https://forum.arduino.cc/index.php?topic=245679.0

Link to comment
Share on other sites

Thanks for the info on your excellent project. Coincidentally, I've just ordered an Arduino Nano to allow my mount tracking to be driven by PHD2. The Arduino to be loaded with Kevin Ferrare's code https://github.com/kevinferrare/arduino-st4/ and a modified relay board to interface to the motors.

With APT loaded on the PC it should make for an integrated imaging and guiding system - if my eeebook is powerful enough to drive everything!

Use of a stepper motor may give better tracking (less jitter) than the simple DC motor used in the Economy Motor Drive, though I find the biggest sources of trailing in my setup are the wind and accuracy of polar aligment (with longer exposures).

Good luck with your project - I look forward to seeing some images!

 

Edited by bobro
spelling
  • Like 2
Link to comment
Share on other sites

13 hours ago, bobro said:

Thanks for the info on your excellent project. Coincidentally, I've just ordered an Arduino Nano to allow my mount tracking to be driven by PHD2. The Arduino to be loaded with Kevin Ferrare's code https://github.com/kevinferrare/arduino-st4/ and a modified relay board to interface to the motors.

With APT loaded on the PC it should make for an integrated imaging and guiding system - if my eeebook is powerful enough to drive everything!

Use of a stepper motor may give better tracking (less jitter) than the simple DC motor used in the Economy Motor Drive, though I find the biggest sources of trailing in my setup are the wind and accuracy of polar aligment (with longer exposures).

Good luck with your project - I look forward to seeing some images!

 

Thank you so much! Like you wind and polar alignment always kill me when I'm trying to track. Since im ra guiding only my dec has to be really precise, and wind confuses phd2 while tracking. I plan to step down my telescope size from the included 114mm 900mm scope to a small wide field refractor, it will be so much more manageable. 

Good luck with your project too!

Link to comment
Share on other sites

On 19/02/2017 at 13:37, SteveBz said:

Did you see this?  He's coded the whole thing from scratch in Python:

http://sy2000.blogspot.co.uk/2014/05/star-autoguide-with-rpi-5-python-code.html

I've run it and it works (although I don't have an RPi).  I'm trying to hack it for my Arduino.

Regards

Steve

Finally gave up on Lin-Guider, I feel that I tried everything. Its like I am just trying to push water uphill, different installs raspbian o/s, Linguider versions and different firmware still no joy. Don't understand what I am doing wrong. I have followed lots of of different setup/installation instructions that people have said they have had it working but still not for me. This programme written in python however appears to work, I get a good camera view and signals to the GPIO although I have only used an LED on the pins at the moment but at least that shows that it is doing something so I thinh that I will go with this for now.

So many thanks for all the advise and I will post any developments that I have

  • Like 1
Link to comment
Share on other sites

9 hours ago, adder001 said:

Finally gave up on Lin-Guider, I feel that I tried everything. Its like I am just trying to push water uphill, different installs raspbian o/s, Linguider versions and different firmware still no joy. Don't understand what I am doing wrong. I have followed lots of of different setup/installation instructions that people have said they have had it working but still not for me. This programme written in python however appears to work, I get a good camera view and signals to the GPIO although I have only used an LED on the pins at the moment but at least that shows that it is doing something so I thinh that I will go with this for now.

So many thanks for all the advise and I will post any developments that I have

Yes, I gave up on lin_guide too. Mainly because of my non-standard  (arduino) mount. I'm customising the python code above. If I ever get it working, I'll post it. Luckily the weather is so bad that there is no urgency for it.?

Steve.

Link to comment
Share on other sites

Hi Guys,

Well I got outside briefly with the scope and guide (see earlier post) last night.  I don't have any guide-scope rings yet, so choosing a star was a bit hard, however there were lots of bugs, so I took a screen dump of a star through the guidescope, saved it as a test star and went inside to debug.  I should say it's all based on the fantastic work done by Maple Yang here:

http://sy2000.blogspot.co.uk/2014/05/star-autoguide-with-rpi-5-python-code.html

Some of the bugs are cleared up and here are a couple of screen dumps of the program:

selectstar.jpg

Tracking (simulation):

tracking.jpg

However, I'm not sure how big corrections need to be adequate to fix tracking errors, but not too great to cause oversteer.  Does anyone have any idea of the magnitude of movement that corrections should try to be?  If I have my handset set to Earth-speed or twice Earth-speed, should I shoot 1 second pulses at the motors or millisecond, or multiple second corrections?

What do people think?

Regards

Steve.

Edited by SteveBz
Adding references
  • Like 1
Link to comment
Share on other sites

Congratulations Steve on getting this far with guiding. It's very likely that many will be using PHD for guiding. If you haven't seen it, here is a link to a PHD tutorial: 

As I use Lin_guider I can give you an overview of how I 'tuned' it for my setup by trial and error setting of the guide parameters. The setup is unusual in its use of DC motors rather than stepper motors, so it will likely respond in a different way to a stepper motor system. Nevertheless, the basic principles should still hold.

Following Lin_ guider calibration, guiding was started on a star chosen by Lin_guider. The guiding graph shows the error in guiding and, of course, the aim is to make this as small as possible and correct guiding errors as quickly as possible. If the Python guiding program doesn't produce a graph it may be possible to observe the central star to see how guiding is performing.

Proportional Gain setting (RA Aggressiveness) - this is set to a value that corrects a largish error with some dampened oscillation about the mid-line. If this value is too high oscillations may grow and guiding will fail. If this value is too small (no dampened oscillation) it will take too long to correct an error. Set to 10 for my setup.

Integral setting (RA Hysteresis) - if guiding continually swings backwards and forwards, this can be reduced by adding together calculated guiding corrections, so smoothing out the calculated guide error. I didn't use this setting as stability wasn't an issue.

Minimum correction - this helps to stop tiny corrections that may not be useful (guiding noise). In my setup  a value of 50msec still seemed to provide useful correction. 

Maximum correction - large guiding corrections shouldn't be necessary, though may be calculated due to wind on the mount. Limiting the maximum correction helps stop sending the scope too far off course (it should come back as the wind effect disappears). 500msec is a good starting value for this.

DEC settings - luckily my setup doesn't suffer from DEC backlash, so I was able to tune the DEC parameters in the same way, with final values being not too different to RA. If backlash is an issue it may be better to guide DEC in only one direction.

One area I don't really understand with Lin_guider is the frequency of guiding. I think it may be down to the webcam I use which doesn't support long exposures. The result seems to be that Lin_guider can issue multiple (perhaps 5 or 6) guiding corrections each second. This is perhaps a good thing as it helps with a fast guiding response. 

Hope the above is useful to you and good luck with 'tuning' your setup.

Bob

  • Like 1
Link to comment
Share on other sites

1 hour ago, bobro said:

Proportional Gain setting (RA Aggressiveness) - this is set to a value that corrects a largish error with some dampened oscillation about the mid-line. If this value is too high oscillations may grow and guiding will fail. If this value is too small (no dampened oscillation) it will take too long to correct an error. Set to 10 for my setup.

So, I think the quick and easy thing to do is add this field to my input screen for both Dec and RA and then do the others if I need to. 

Thanks very much.

Steve.

Link to comment
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
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Elp
      Hi, first post so please bear with me, having issues with autoguiding, looked at numerous forum threads and cannot find the issue specific to my setup and the issue I am having.
      Equipment in question:
      ZWO 224 using as guide camera plugged into raspberry pi running Astroberry via USB3,
      Lynx Astro EQDIR cable plugged from USB on raspberry pi into hand controller port on AZ GTI.
       
      Configuration:
      Synscan android app successfully connected to AZ GTI via wifi and can control via mobile phone,
      AZ GTI setup to connect to raspberry pi (so it's on the raspberry pi network) AZ GTI connected successfully as it is recognised in PHD2 and EKOS,
      In PHD2 the mount is setup as INDI mount (AZ-GTI) and connects.
       
      Issue:
      PHD2 is unable to guide in either RA or declination (see screenshot error showing up), it is always one or the other. I have tried setting up multiple times, tried using the network cable which came with the camera directly from the camera into the hand controller port and setup in PHD2 as "on camera" (I suspect this setup is wrong anyway and was one of the first I tried). Polar alignment has been checked multiple times, the end result is always the same, the star field within PHD2 window will always drift in one direction so any star chosen will eventually disappear out the field of view as the mount isn't moving to follow it.
      Looking at the PHD2 graph I know it is trying to send pulses to the mount but either the movement is too much for the mount to move or something isn't happening as it should, in the example screenshot provided I tried this indoors on a fairly fast (compared to in the field) rotating star field looking at a screen so it will fail, though the mount didn't adjust at all, no matter how I've setup prior the AZ GTI refuses to adjust to follow a guide star. I have tried manually moving the mount in PHD2 and it doesn't seem to move in any direction, manually moving however does work in EKOS so the hardware seems to be plugged in correctly. EKOS even knows where the mount is pointing and can issue go-tos (although it is slightly off target at the moment).
      I am kind of at my wits end to why autoguiding isn't working, if anyone can help please assist.
      On another note if someone can advise how to configure PHD2 so the off yellow warning box colour can be changed so the error message can be read clearly - I know theres a line of code I can use in the terminal window which refers to a resource file to change to the default PHD2 colours and launches the software but the changes are never saved.
       

    • By deanchapman2705
      Hi, I'm new to this whole auto guiding thing so bare with me!
      So I have a iOptron SkyGuider Pro with a WO Zenithstar 61 and recently bought a ZWO ASI120MM Mini and guide scope to have a go at auto guiding. I followed tutorials online step by step (installing drivers, and changing the settings in PHD etc.) and managed to connect the camera and mount in PHD, start looping exposures and select a star. But when I start the calibration, it counts to 'west step 61' and comes up with "RA Calibration Failed: star did not move enough"
      I have tried reinstalling all drivers/software, using a different laptop and solutions other people have found do not help. Guide scope is focused and it's not trying to track a hot pixel.
      The star is supposed to move up and down as the mount moves during the calibration although nothing happens. So this makes me think there is something wrong with the mount or the ST4 cable from the camera to the mount. Cable securely clicks into both ends. I have heard the term "backlash" with mounts and not sure if this could be the cause? Not sure what this means or if this is possible with a star tracker?
      I can't seem to manually control the mount in PHD although I'm not sure what I'm doing. I can however, manually press the buttons on the mount itself and it moves fine.
      I've attached pictures of my setup along with the 'Guide Log' that people often ask for - PHD2_GuideLog_2021-08-23_225305.txt
      (Also, the total weight on the mount is 4.7kg and the max payload is 5kg for imaging so this should be fine?)
      Any Ideas? Let me know if you guys need anything else.
      Thanks,
      Dean
       
      Setup:
      iOptron Skyguider Pro
      WO Zenithstar 61 ii
      Guide Camera: ZWO ASI120MM Mini
      Guide Scope: 32mm F4 (focal length - 125mm)


    • By NigelHt
      I've recently started astrophotography, and after beginning with a DSLR and rotator haveprogressed to an EQM-35 GoTo mount and Zenithstar 73 telescope, with Ascom control and guiding with PHD2. While I've got some decent results, I've consistently had problems with guiding, even though I've tried adjusting the mount as described in online videos to remove backlash, and unbalancing the telescope. Initially there was obvious backlash that I could feel; I've now eliminated that, although I notice that the stiffness varies with declination (something I've seen reported by others), and it's almost impossible to avoid backlash at some declination angles without making the mount far too stiff at others.
      While I'm aware that this type of mount is always prone to backlash issues, what I'm seeing is still different to what I'd expect. If I drive the mount, say, North (either manually or as part of calibration or guiding), stop so that everything comes completely to rest, and then drive the mount South, what I see is that it continues to move North for a while before beginning to move South as expected; the behaviour is exactly the same if I start moving South then switch to moving North. The attached image is part of a typical calibration from PHD2 Log Viewer to show what I mean. As you can imagine, this completely messes up guiding unless I offset the polar alignment and guide in one direction only, or align very accurately and switch off declination guiding altogether.
      If this was simply backlash, I'd expect the mount not to move at all initially after switching direction rather than to move the wrong way, and I can't think of a mechanism to cause this behaviour. I'd be grateful if anyone can explain this, please, and give me some advice on how to cure it.

    • By blameTECHIE
      I don't expect any replies - think I'm just braindumping for the mental wellbeing aspect of a frustrating night.
      ---
      Having been ill through the week, Saturday found me feeling well enough to get outside and see if I could hook some things together and try to get FirstLight through some of my recent purchases.  I've been using my Star Adventurer mini-rig [SA non-wifi, Canon 200D (unmodified), >30yr old Tamron 200mm f3.5] but knew things were going to be very different, and was keen to get going.
      So the kit was all lined up:
      > Laptop (Win10), Raspberry Pi4 with Astroberry
      > EQ6-R Pro
      > SW 80ED-DS Pro (Kit), SVBony SV106 190mm/50mm Guide Scope
      > ZWO ASI 224MC, Canon 200D, SVBony SV205, 7TC ASI 120MC clone
      > USB GPS Dongle (G72 G-Mouse Glonass Beidou GNSS) for location
      and mains power for all via various PSUs with enough USB cables to circle the planet
      ---
      Didn't take too long to get both Win10 (ASCOM) or Astroberry (INDI) talking to the mount and progress was being made - RA/DEC all seemed fine so onto the cameras.  Found a distant object and SharpCap gave me images for all three USB devices once I had the SVBony as a Windows WebCam (RESULT!) and the same through INDI on the Astroberry, all three displayed images when enabling Streaming.
      Settled on EQ6-R, SW 80ED, ASI224MC for imaging, SV106/SV205 for guiding
      That's it (I thought!) and I broke down the rig and moved it to the lawn - I say lawn, more like a mossy bank but serves the purpose - and wait until dusk where a simple Polar Align and I'll be grabbing images of M51 Whirlpool in no time ...............

      (I must cut the lawn, even if just to get rid of the blue from spray-painting a new table a couple of weekends ago)

      (please ignore the middle dew heater, was there to remind me to put it on the guide scope later)
      ---
      PA on the Star Adventurer, 30mins (5mins for the alignment, 5mins for remembering which phone app has a PA Clock and the obligatory 20mins to find the flamin' polar illuminator!) - this has been giving me consistent 5min exposures with no trailing.
      PA on the EQ6-R is 'interesting' - I have a QHY PoleMaster but am waiting on the adapter from FLO (stock issues) so it was SharpCap alignment.
      Wait for it to get dark enough, then get focus, then wait for platesolving in a "change exposure, gain, star threshold, black threshold, platesolve again" loop for over an hour.  Woohoo, plate solved ..... oh, rotate around RA ..... and perform the same operation again ..... ARGHHH!
      Over two hours later (probably more like 3hrs+) I've got polar alignment to within 12 seconds (wishing I'd screengrabbed that now).  I really don't like the adjustment mechanism, the thread pitch is far too high for minute adjustments of alignment!
      ---
      And onto guiding ........................ or maybe not.
      PHD2, Nothing through it at all .... then remembered I'd not refocused the guide scope, then it was taking the Darks library.  Still nothing.  Opened the SV205 via SharpCap and got focus, switched back to PHD2, still nothing ...... hmm, is this just an unsupported camera (windows 'webcam').  So switched out for the 120MC copy - Amazon 7TC special.
      Repeated the SharpCap for focus, then PHD2 Darks library and BOOM I have stars showing up in PHD2 - RESULT ...... I'll leave it at that for a moment and try looking at something, see what I get from the 224MC main camera and what PHD2 gives me in the guide scope.
      So onto the next 'learning opportunity' - target selection
      ---
      Erm, how do I select a target for goto with just two camera apps .... aha, Stellarium
      No Telescope selected, easy - it went something like this:
      "Open Stellarium, select telescope, select ASCOM ... there we go ... nope, it won't connect ... restart everything (twice) ... redo settings (twice) ... check ASCOM diagnostics (all passed) ... quick google search, aha I'm not the only one, you have to select the scope within the options pane ... what options pane .... oh, scroll down ..."
      And I now have Stellarium control of the scope - again a RESULT - it's taking time but I think I'm making progress here .... hmm, it's getting bloody cold, wow, it's midnight!
      ---
      So I now have an in focus 224MC, an in focus guide scope and control over the mount, here we go ... I'll be stacking images in the morning and making millions from selling prints online
      NOPE!
      Easy targets for testing were below the horizon (basically M42) so I'll just pick Vega and make sure slewing works, imaging works and can see how guiding works.
      Nothing, no bright star at all - okay, bigger target - the moon.
      Again nothing, no bright screen - so switched out the camera for a 26mm LER EP and a diagonal and manually aligned the moon - then, and here comes stupid, refocused (!) for the moon.
      ---
      Stellarium wasn't syncing with the mount - I was 'off' on any selected target and by a lot
      Quick google search and I'm no the only one - no sync points on my clean build so wasn't that, but use of the GPS dongle for location and TIME might be the problem.
      ---
      And at this point it as 2:30am - prime viewing time last night with the moon disappearing in the West behind me - the garden slopes due-West to due-East so I only get Partial-North>East>Partial-South viewing.
      Time to give up, have a small glass of Red and look for more things to buy on SGL/Astro B&S.
      ---
      Today - well I had to break everything down to get it into the garage (too heavy to carry as one with current health) - I'll try to get the ASCOM/GPS element sorted out and maybe this evening try some targeting/lunar rate tracking so see if that major element is resolved.
      And, if you've made it this far, please accept this for your perseverance🎖️, you've earned it.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.