cjdawson

16 hours ago, Superuser techmods said:

I'm new to the lx90 I understand how to get polar aligned ok, but not using sharpcap on a fork mounted wedge, how do you use the polar alignment settings as I thought they were for an eq mount.

I have sharpcap pro I'll try it out if anyone has a how to guide thanks

Welcome to SGL.

Using Sharpcap Pro with an LX-90 is a great way of getting excellent PA.  All that you need to do is follow the wizard on screen, which will walk you through the process.

On the LX-90, the manual adjustment bolts are the Alt-Az alignment bolts.   The Az bolts are the ones on the bottom part of the tripod that presses against the tab that sicks out.

The Alt adjustment is the four bolts that hold the wedge at the desired angle.  You should have a really long bolt that you can use to fine tune the alt, it does this by literally rocking the whole of the fort mount section.

Apart from that, the rest of the instructions are exactly the same as any video tutorial that you can find on PA using Sharpcap Pro.

I'd highly recommend it.

Colin.

This is perfect timing for me.    I'm in the process of building and AllSky camera and want to use a 3B+ for it and power it using PoE.    I've got a 3B+ running a development platform at moment, but it's kinda being pushed to it's limit to make it work.   I'm planning on getting a PI 4 4GB - from what I read, They've severly underestimated how popular that version is going to be, hence all the out of stock messages and swap out the 3B+ from my dev platform for a PI 4.  Then I'll be able to use the 3B+ for my all sky camera

Finally, after a complete sidetrack of a project as the Meade Driver for my telescope wasn't up to the task and I've now created a new open source ASCOM driver for the Meade telescopes.   Known to work with the Meade LX-90 and has had a successful test on the Meade LX200-GPS. 

I can now announce that I've finally got the first test version of AscomGps ready to roll.

Here's the link to the blog post that has the software download link.

http://cjdawson.com/2019/06/22/ascom-gps/

It's still a work in progress, but I'm happy to consider this battle station fully operational.    Anyone fancy making a nice Icon for it?

To keep everyone updated.  I've been talking to Michael directly and we've solved the teething problems with the driver.  Turns out that he needed to upgrade his ASCOM platform to the latest version.  I've also done a few tweaks to the driver installer and the builds so that it now works with .net 4.0, and it also checks at install time if Ascom 6.4 SP 1 or higher is installed.

It's also confirmed working with Windows 7 as well as Windows 10.  So I can safely assume that it'll work with Windows 8 as well.   Possibly even with windows XP, but that's untested.

The V0.5.0.0 version needed .net 4.7.1. Based on your issue, I've found that I can lower the .net version two 4.0 without any ill effects on the code, so I've done that.    V0.6.0.0 onwards will be using .net 4.0 until such time as I need to upgrade for a good reason.   This is the same version that the ASCOM Platform 6.4SP1 which is the version against which I developed the driver.

@michael8554   I've just put up a new build,  version 0.6.0.0

Downgraded the .net requirement to 4.0 or higher.

I've also tested it quickly with both sharpcap and phd2, and found it working without a problem.  Let me know if you get the Failed to load served COM class assembly again.    That was unexpected.

Here's the link.

https://bitbucket.org/cjdskunkworks/meadeautostar497/downloads/Meade.net.Setup.0.6.0.0.msi

NET 5?

 eek,  I know the code is targeting .net 4.7.1.     Hmmm, I wonder how low I can go, so rather than using the latest framework, I'll try using an older one and see if that makes it easier for others to use.   I'll try and drop it down to .net 4.0.   That should be good enough for most people.

Meade Generic  is the name of the new driver. So, it showing up is good.

"Failed to load served COM class assembly ASCOM.Meade.net.Focuser.dll

Unable to load one or more of the requested types.

Retrieve the Loader Exceptions property for more info."

This has me puzzled, that means that PHD2 is trying to access  the focusser.   That's crazy.   I'll download PHD2 and try it on my dev VM and see what happens.

Let me know how you get on, and if there's anything that doesn't work 100%.   I'm sure that I'll be able to modify the code to better support the LX200GPS,  I just need to know what the actual differences are.

On 07/06/2019 at 18:53, michael8554 said:

With the current LX200GPS/R ASCOM driver, when I set a custom Guide Rate with the handbox (say 90), when I connect with PHD2 it resets to 66.

So I set to 90 after connecting with PHD2, which holds for that session, and is still present when I next switch on, but reverts to 66 next time I connect PHD2.

Andrew Johansen gave me this info regarding the ASCOM driver.

I understand that      :Rg10.0#    resets the Guide Rate.

Looking in the "Meade LX200GPS\Telescope.cls" source 
Inside the "Let Connected()"  function 
the code finds the mount and does some checks 
At about line 720, ( after everything is done ) 
it calls a function called Reconnect, which looks like it is meant to reset some old data. 
Inside Reconnect, ( at about line 2108 ) 
 they forcibly reset the guide rate 
with no way to override it. 

I know that the driver that I'm creating doesn't do this.  so, with that in mind, you might want to give it a try and see if it works any better for you.  You can install it alongside the other driver and chose which one you want to use, so again it's low risk for you.

10 hours ago, StarDodger said:

I have used this for years with my LX90 it’s very good...as a PC based control instead of the Autostar handset...

http://miltonhill.us/software/LX200_Mini_Control.html

or here for the latest version, 4th one down on page..

http://miltonhill.us/software/index.html

That's interesting.  Never saw that program before.  It looks good, shame that it needs a direct connection to the com port.  Which in turn means that you can only have it connected to the telescope.   Whereas what I'm working on is a good quality driver that will let you run several pieces of software at the same time on the scope.  I'm planning on making a handbox style application just like that, but instead of connecting directly to the scope, it'll connect via ASCOM thus meaning that it can work along side any other piece of ASCOM compliant software.

2 hours ago, michael8554 said:

I see on the ASCOM Forum that many astro manufacturer's ASCOM drivers are flakey, and the poor user often has considerable trouble correctly uninstalling and reinstalling before the thing works correctly. 

I also see on the ASCOM Downloads instructions NOT to use the 497 on the 200GPS and vice-versa. 

Hence my reservations. 

Michael 

I've also seen that message.  The reason is that the specific driver that you are referring to is old, and doesn't really work all that well.  Whilst there are a few differences in the way that the commands for for the LX-90 and the LX200, most of the commands are the same and are directly compatible.  The devil is in the detail of specific implementations and there may be some defects in the handboxes which could cause the wrong command to be sent to the scope.  In this case, it will simply be that the scope will ignore said command or interpret the command incorrectly.    For the majority of the commands it's the same.

There is a document from Meade that shows details how the commands work.

https://www.meade.com/support/TelescopeProtocol_2010-10.pdf

The driver that I've created uses these commands to communicate with the scope.  Hence why I'm saying that there's nothing to worry about.   Hope that helps to put your fears to rest.

I'm hoping that the hand box uses the same control codes as the Autostar and Audiostar.     I'm planning on creating a virtual handbox application for the for the #497 based.  Actually, I've already put in some of the controls for it into the driver code for 0.6.0.0.   hopefully I'll get that going soon enough, and have the application ready for prime time too.

12 hours ago, StarDodger said:

Why not just use StarGPS it’s a superb driver with all the functions you need and with a GPS dongle...no need to write another, just feast your handset with StarGPS and you have all the extra functions...

https://www.stargps.ca/

StarGPS is a firmware that is uploaded to the Autostar hand box.  It is not an ASCOM driver.  The Ascom Drivers allow software like SharpCap, Sequence Generator Pro, Maxim, Cartes Du Ceil, Stelarium to name a few to send commands to the scope ask it to move, and get information about where the scope is pointing.    The ASCOM driver is installed on a windows PC, to allow windows to connect to the handbox.  goes inside the handbox.   Also I'm not charging anyone anything to install and use the driver.  StarGPS isn't free.

12 hours ago, michael8554 said:

That's just asking for trouble, I won't be risking corrupting my LX200GPS !

I've posted a query on the LX200GPS Forum, there are developers there that will know the answer, but I suspect Autostar 497 and Autostar II are way different.

I'll get back to you.

Michael

 

You won't be risking corrupting anything.

An ASCOM driver is installed in windows, it issues commands to the Handbox via the serial cable.  If something goes wrong, the command simply doesn't work.  The scope will be fine.   I wouldn't ask anyone to risk anything.  I know how much the Meade Scopes cost, espcially the LX series.

I've released the first alpha test version of the driver.   It's currently 0.5.0.0

This should give all the functions of the original meade driver, plus more.  At the moment I can only support the Autostar #497, but there's no reason why it wouldn't work on an LX200, I say give it a test!   Other models too.   Any issues, let me know and I'll see what I can do to resolve them.

On 25/05/2019 at 15:50, michael8554 said:

The LX200GPS ASCOM driver has exactly the same problems, so that one next please ?

Michael 

Hmmm, I wonder if the driver I'm making will work directly with the LX200GPS,   might need a few tweaks for specific features, but pretty sure that it'll be 90% there already.  Might be worth giving it a try when I am confident enough to release a beta test version.

Hi everyone.

For anyone that uses a Meade based telescope with ASCOM, I'm sure that you are all aware that the "Meade LX200 Classic and Autostar #494, #495, and #497 (combined telescope/focuser, 5.0.4)" driver is the one to use.  However, it's old and you can only connect one piece of equipment at a time oh and certain programs like WIFI Scope, Sharpcap, Sequence generator pro all have their functionality limited because the driver doesn't implement everything.

Well, I started writing a little program that would allow me to set the date, time, site lat and long using a GPS connected to my PC.  That way both the PC and Autostar are in sync.   However, it turned out that the aforementioned driver doesn't implement the ability to set the date and time, and I think it does something funky with the site too.  (Can't remember to be honest, but I know I don't trust it.

My solution, I'm in the process of creating a new driver for the Meade AutoStar #497 and AudioStar.

Here's the link to the Wiki.

https://bitbucket.org/cjdskunkworks/meadeautostar497/wiki/Home

I was wondering what sort of interest there would be for my fellow Meade users to get some much better support for our scopes.

And again, you are introducing another piece of hardware that would need power, network etc.

This is the program that I've written.

The GPS is plugged into a USB Port on the same computer.   It's a UBlox 7 usb, it's installed into Windows 10 and is a Sensor in the device manager, so I don't need to worry about the NMEA strings.

All I have to do is load the program, choose the mount which is my case is the POTH Hub, then click connect.   Click Connect for the GPS, then click Set location, and hey presto the Telescope will get updated with the information from the GPS.

No need to add GPSD, no need to have a linux device running, no need to have anything that is not directly connected to the mount or computer.

nope, eqmod does not work with a meade mount

2 hours ago, stash_old said:

Any USB GPS device - e.g. u-blox USB GPS which works very well . Just pointing out that you dont need windows to produce a GPSD service and GPSD (a Linux Daemon) on Linux has been around for decades.

You can even pick it up on Windows(or any other OS ) via Node-Red / MQTT (IOT approach) (https://www.npmjs.com/package/node-red-contrib-gpsd) so you could produce something in a matter of hours(or less). Plus using Alpaca Ascom you can produce/interface with any Ascom driven device that accesses the GPS property - No need to reinvent the wheel. ?

Handy if you have more than one device OR ,as with most USB GPS devices ,they need to be outside and have been running for a while to get a fix - so could be left permanently running in an Obsys as the Pi Zero (w) uses very little power when compared to a Laptop/Desktop etc.

I think you are completely missing the point of the program.

Let me explain "MY" problem in detail.

1. Telescope Meade LX-90 EMC with Autostar #497 running firmware 43G.

2. Laptop running Windows 10 Pro with Ascom installed.    Intention is to use PHD2, SGPro and SharpCap.

The problem, I have a ublox gps receiver.   At the moment, there is nothing in place to get the data from the GPS receiver to the scope.   Inserting extra things like a Pi Zero, won't change that,   my laptop still needs to get the current date time, to be accutare.   I still need to set the Lat/Long for the scope.

The program that I'm writing is to take the information from my GPS and inject it into Ascom. As far as I'm aware, there isn't a program like that.

22 minutes ago, Cleetus said:

What's the difference between what you are proposing and starGPS?

StarGPS is a hardware device that plugs into the mount and adds GPS support, but you have to patch the firmware of the Autostar to their special version.

What AscomGPS is going to is allow you to use a GPS on any goto scope that has site information.  You won't need a special flavour of GPS specifically for the mount, and it won't be limited to the Autostar.  It'll work with Synscan and others too.

Actually from one of my trials yesterday, I found out that I don't even need a GPS at all to get a location as IP based Geo location was enough to get a good enough Location.

Oh, and the StarGPS costs $130 ish.   What I'm planning won't cost anything.

1 hour ago, stash_old said:

Or you could just plug it into a Pi Zero W and use GPSD to distribute GPS - works great with Linux but cant remember if Windows (any) has access to GPSD.

Plug what into a Pi Zero W?      I think there's a load of context missing that would be needed for this to make sense.

Hi everyone.

Many years ago, I wrote a piece of software called AstroGPS.  It's purpose, was to ready the input from a Garmin e-trex, to get accurate date, time and location data.  then upload that info into my telescope.  It was never ment to be a big hit as it was written specifically to perform the update on a #497 Autostar.    After using the software for a few years, I wondered off in a different direction and well kinda stopped using it.     Fast forward to today.

In my current incarnation of my scope, it's the same one just all the accessories have been adjusted.   I find myself once again looking at the problem that I had all those years ago.  What's the problem?   When setting up for a session, I want to make sure that the scope knows "where on earth" (bad joke intended) it is.

I've started tinking with some code and think that it's going to be easy enough to come up with a solution to the problem.  As I'm playing with Windows 10 these days rather than Windows XP, there's been some advanced made in the tech that will make life easier.

The first instance of the program that I'm going to write.   Is going to work like this....

1. Use the Location Services API in windows 10 to get a reading for location.

I've done a test with a u-blox USB GPS and found that it can be installed as a "sensor" in device manager, so there's no need to mess with com ports and the like.

2. This time rather than connecting directly to the scope using the serial port, I'm going to use Ascom to connect to the scope instead.

This means that I don't have to be limited to only working with the #497 Autostar.    It can be made to work for any goto based scope.

The program will also be able to make use of the GPS time stamp to set the clock on the computer to the correct local time.

One immediate feature that I know that some people will want is to be able to connect a GPS via a Serial port rather than have to use Windows Location Services as there could be privacy concerns related.

Before I get too involved in the creating the application, I thought it might be a good idea to ask if what features would make you interested in using something like this?

Yep there is a much easier way.  Cheat!

For the spinning the OTA thing, you know you are spot on when polaris doesn't fly off.  the closer you are the less that polaris will move.  After that, yes there's trial and error.  There's also the geometry of the mount that can help you.  Look at the part of the fork that's connected to the OTA.   Comming from there, both sides are black metal bars that hold the primary area solidly.     What you can do is line those up with the forks and hey presto, it's in line.    See, it's cheating and it's good enough for when I'm doing stuff visual.

I've switched over to using camera, and frankly, I cheat even more.   SharpCap Pro has a polar alignment feature I use my guide camera to do this and all I need to do is get the scope pointing within 5 degress of the pole and it's happy enough to do it's thing.   Takes alot of the guess work out of it.

Sounds like you made some major progress with the latitude adjuster

I can't imagine working with a wedge without either of the alt of Az adjustment.    I know that tweaking in the final seconds of PA is very delicate, even with them.

I just found the manual for the LX-90 wedge on the web.  This is the one that I have, turns out that I don't have a deluxe one after all.  (wasn't sure, and I've had it for years)

http://www.meadeuk.com/pdf/Meade-8-inch-Wedge-Manual.pdf

You can see in the instructions that there are things in addition to the wedge itself that give you alt and az adjustment for your wedge.

I was typing from memory.   It’s the easy alignment that I do with my scope.   I’ll put some photos up of my wedge so you can see how the extra bits look.

one more trick, put a cd between the tripod and wedge, it’ll act as a bearing and help make the AZ adjustment easier