malc-c

I've just written up an article for my local AS newsletter based on a broad outline of imaging, and how it all connects. It's very generalising but hopefully gives you an understanding in to how it all goes together. Again, the article is a broad spectrum and there are other ways to do things. It doesn't go into details for each application, that is not the scope of the article. It's really for an outline on one way, and the most common way to connect up the hardware, and how the process works. Hope it helps Fully automated imaging.pdf

Using the recommended EQDIR lead this is how you connect the DSLR, Mount and Guidecamera - That's all you need

Can you take some photos of the leads and the set up as I've read through you post and I'm still confused. If you are using an EQDIR cable then there is no need to use the handset, but you mention disconnecting the EQDIR cable form the handset This is and EQDIR cable. You remove the handset from the synscan box and plug this in to the same socket the handset uses . The other end plugs into a USB socket on your computer. DO NOT try and use any other USB to serial convertor it could damage the mount. Then download EQMOD and install that on your computer. You already have mentioned you have ASCOM on the computer so it should install without issue. Check Device Manager in windows, and under PORTS right click on the COM port that matches the EQDIR cable and select properties - make sure the baud setting is 9600 From ALL PROGRAMS > EQMOD > EQASCOM select TOOLBOX and then under Setup select EQASCOM and click DRIVER SETUP. Make sure the port selected is the same as the one that is allocated to the EQDIR cable, and the baud is also 9600 - You also need to add your site info and then OK to exit With the TOOLBOX still open now power up the mount and click the TEST CONNECTION button. If all has been set up right it will launch EQMOD. Next to the slew controls (NSWE) is a box with 1 showing - click in this and set it to 4 form the dropdown list. Now click on any of the NSWE buttons -holding down the left mouse button to hold the NSWE button down should make the mount move..... Opening APT and it should connect via ASCOM to EQMOD. As mentioned above - your main camera and guide camera should be connected via USB to the PC - forget the ST4 connections. EDIT: Just to add that you don't need to run the TOLLBOX after its been set up - just run EQMOD dierct

Great, so what did you change

Can you confirm that the port settings in the properties is the same as that set in EQASCOM (ignore the CH340 reference I've plugged in an Arduino just for illustration purposes )

Just to clarify / recap: * Using the sysnscan handset works * on PC1 all the software and drivers install without error, device manager shows the EQDIR as a COM port and the baud rate set in the properties is set to 9600 * on PC1 with the same EQDIR cable installed opening up EQASCOM TOOLBOX and selecting the same COM port results in a communications error * you have tried a second EQDIR cable on PC1 * you have tried a fresh install on PC2 using the original EQDIR cable * you have tried the second EQDIR cable on the fresh install and that too fails to communicate with the mount

If it's physically rocking then to me that sounds like a meshing issues with the gearing (worm). End float as David has suggested and backlash adjustment should sort that out (I had a similar issue on my HEQ5 some years ago)

I've not used it in anger myself, but following a review I did for our society newsletter, one of our members who's images have graced the covers of Astronomy Now tried it and now can't say a thing against it.

Can you elaborate... How are you connecting the mount to the PC (EQDIR cable?) and what software are you using, EQMOD or GSServer ? Normally these applications, coupled with the planetariums software and the guiding software control the mount positioning, tracking and guiding If you can provide us with more details and information on what you want to do then maybe people can advise you accordingly.

If when you connected the handset it reported "no response both axis" then that would mean the micro-controllers on the motor board in the mount may have been blown. As the handset connects and you can control the scope with it then this rules out a physical issue with the mount. One simple test to check communication with the mount is to download the mount firmware updating application. Connect the EQDIR cable between the mount and the computer, load the application and then ensure the option to auto detect the serial port is checked, and then scan for the mount. The software should then display the current firmware of the motor board once it's found the port and communicated with the mount. If it reports no mount found then this would suggest either the EQDIR cable is faulty, the USB port on the laptop is faulty or the drivers for either or both have an issue. The fact you've tried two machines, with fresh install of drivers, and nothing will talk to the mount suggests to me its the EQDIR cable that is at fault. The only way to confirm that is to part with another £30 or so and purchase a replacement EQDIR cable

Assuming it uses any industry standard it might, but then the controllers on the display may be different, or the graphical characteristics might be different (these are not two line displays - they are GLCDs). If you fitted an off the shelf one and the damaged one used a different pin out you could risk damaging the controller itself. My guess is that as per previous posts where screens have been cracked, if it were that simple they would have used an off the shelf replacement and documented it in those threads for future reference. Secondhand handsets do come up for sale from time to time, but not often...

APT doesn't control telescopes directly. It controls cameras via ASCOM compliant drivers You have two choices for the physical connection between the computer and the mount, and its an either / or choice. * Use a suitable lead to connect to the Synsacn Handset. This can either be a USB to serial connector and the standard serial cable that probably came with the mount. (This is a long cable that looks like a a telephone extension lead, but with a standard serial 9 pin connector at the other end, or a USB A to B cable depending on the version of handset you have), and then have the handset connected to the mount via the handset port on the mount. You must have the handset set to PC-DIRECT mode in order for communications to pass through from the PC to the mount * Use a dedicated EQDIR cable that replaces the handset altogether as it connects to the port the handset normally connects to and then the other end plugs into a USB port on the laptop / computer. You then need to run an ASCOM compliant "driver" for the telescope. This will either be EQMOD or GSServer. You will also need the ASCOM platform installed on the computer, which as you haven't said anything about any software reporting ASCOM related errors I think we can presume that this is already installed. Then connect your main camera, and your guide camera directly to the computer via USB. Forget about ST4 connections. ST4 was mainly used for direct connection between the guide camera and mount with the handset in control, as you are using the computer to control the guiding and mount this isn't required. Now even if you are connecting through the handset in PC_DIRECT mode forget the handset as a means of control. Use a planetarium application such as CdC. You will need to enter the location details and time into both EQMOD and CdC. CdC should then be used to connect to the mount via EQMOD. You can then unpark the scope and right click on a target and select slew to instruct the mount to move. Then open up APT and PHD2. Connect PHD2 to the guide camera (again we're assuming the driver is installed) and the mount. Do the usual calibrations etc and let it guide. Then in APT select the main camera, and set up a sequence or take a test image. All being well all the applications and hardware will play nice and you won't have any errors or issues. Hope that helps... if you still have any issue then PLEASE explain to us exactly how you have set up the mount and what connections and software you are using.... I've made the assumption the computer is running windows... but could have wasted my time typing this reply if you are running LINUX as you haven't really been forthcoming with information.

Is your hand controller one of the newer versions with USB, or are you using a USB to serial adapter and the standard serial cable that connects via a small telephone type plug ? Personally I would use an EQDIR cable Such as this one and connect direct to the mount. Are you using EQMOD to control the scope? I'm confused (easily done) when you state APT and cable in the same sentence... if you could elaborate on exactly how you set up and run through your workflow it might help us understand what might be the issue

How are you detecting the wobble, and what is your definition of wobble. Is it a spike in a PHD2 graph, is it regular such as a PE ?

I often think that there are too many applications that do the same job. A decade ago you had your telescope control application, namely EQMOD. Then you had a planetarium application which was your database of targets, but would connect through ASCOM to EQMOD so goto's could be instructed. Then APT and BackyardEOS came along and (AFAIK) just handled imaging side of things. PHD (the original) interfaced to the ASCOM platform, and talked to the guide camera and EQMOD to perform its duties. These days all that is integrated, and you have options to control the mount from the imaging software. Same imaging software can interface to PHD2, although I'm not an advanced user to suggest in what capacity which application becomes the master in this... Also with so many apps now all integrating on the ASCOM platform, there is no clarity as to issues in loading them in a certain order, so for example of PHD2 is loaded after APT, does APT still find PHD2 and connect or does it give up after checking on the initial launch ? I tend to load up CdC, then connect to the telescope which launches EQMOD, then load PHD2, and then APT. I unpark the scope, use CdC to slew to a target, minimise both, then take a framing / focusing shot with APT using the 400D, and if I'm happy with it, then run PHD2 to start guiding. I then g back to APT and load up a plan and let it run... I don't use 90% of the other features of APT.

Really? - When I was working out the size of the observatory, and how the scope could be parked (and this was with the 200P / EQ5 set up before I got the HEQ5 mount) I mocked up the area on the patio of where the walls would be to ensure I could move around and use the scope without knocking the scope or having to limbo under the counter weights. That area is 8' x 8', and gave around 18" clear all round. The shed in the background (where the observatory now resides) is 7' x 5'.... clearly four 200P / eq5's would not fit in that space !!

As far as I know it's proprietary - and as Synta would class it as a non serviceable part you would need to replace the whole handset. Its more really the physical construction rather than the characteristics of the display that is the issue.

Because I have a 200P on a pier in an observatory. The scope room is 2.2m x 1.8m internally. This allows you to walk around the scope without the need to duck under or limbo. You could store a 200P or similar size scope in a 4' x 4' space (I can see how it can be anything less as the OTA is longer than 3'), but I can's see it being practical. I would really like to see 4 x 200P on an HEQ5 (or similar spec setups) operate in 7 x 7 !

7' x 7' will just about provide enough clearance for a 200p without the need to limbo around it. There is no way you could accommodate two piers in that size shed

How are you controlling the telescope? I can't advise on the specifics for your mount, but generally PHD requires an "driver" application such as EQMOD (for Skywatcher / Orion) as PHD2 doesn't (AFAIK) provide direct control / interfacing to the mount. It integrates through the ASCOM platform to the imaging software, any planetarium software and the telescope control software. Drivers are listed on the ASCOM website (seems Mead don't produce their own drivers for their scopes !) Listed here the LX200GPS is about 2/3 the way down the page. I've not been able to locate any application for PC control, but there are various software packages listed on Meads site, so I guess they produce something that provides that functionality.

That is a decent bit of kit that will get you started, and has a motorised focuser too (which retails for around £55). For a little more than your £200 budget there are some alternatives if you wanted new. Skywatcher Explorer 130P - £259 Swkwatcher StarQuest 130 - £225 These are showing as in stock, which these days is something of a miracle !

Well other than actually going there in person, if they choose not to deal with customers telephoning or emailing them then there isn't much more you can do to get an update on when you might get your order completed.

Thanks for the update. So being so young they are not really at that stage where they are really gong to appreciate things the same way an 8 or 9 year old will. The problem is that no one will be able to really recommend something that will suit your needs as everyone's expectations are different. My first glance through a telescope was at a bright star low down in the south one summers evening. I was that stoked to see it was Saturn, with is rings nicely tilted you would have thought I had juts discovered it... But then when I tried to see a bright galaxy I was very disappointed as even though it was a 4.5" aperture reflector, it just couldn't perform how I thought it should. An this is what I fear may happen with the scope you have in mind. It will show you the moon, and resolve the large craters, and mountains. It will show Jupiter as a bright, but small disk, surrounded by up to 4 bright full stops (the major moons). It will show you Saturn, although its not best placed at the moment. But to see DSO's it's not really going to perform that well. You'll see star clusters nicely, and possibly make out the Orion nebular which is probably the largest / brightest nebula from the UK, but don't expect to see anything like the images in the books. Part of the problem is location, and if you have access to a darker sky then you'll get more form your scope than form the back garden in a town house. Also it's down to the individual. Some have better eyesight and can pick out detail better than others, so irrespective of telescope size, one person will see more than another. It also depends on your circumstances. This time a couple of years ago, spending £200 on something that may not get used that much, or turned out to be below my expectation wouldn't have been a problem for me... today that might not be something I could ill afford, and I get the sense from your post that money needs to be spent wisely? Best advice I can offer is to see if there is a local astronomical club or society near you. Pop along to one of their meetings, or (as most do) a start party / observing session and have a look through members scopes or binoculars. That way you can see what results you are likely to get through a scope of given aperture, or focal length. It will certainly help you decide if spending £200 now is the right thing, or possibly save a bit more and get something a little more capable of what you are hoping to see. I just noticed the new post whilst I was typing this... Adding a barlow to double the focal length will not improve things, it makes the image darker, and possibly unusable. This is the thing, to use an analogy, two cars, one with a small 750cc engine the other with a 3000cc 300HP V8 in it. Both are capable of travelling form A to B, but the second car will be able to cope with the hills better and travel at 70-80 with ease, where as the first car will still get to the destination, but will struggle with the hills and might not even reach 70mph. Adding a turbo or nitro kit to the 750cc engine, which it will make a little difference, won't improve things to the point where it matches the 3lt car.

Most of which is covered in that linked thread... What happens if you try connecting via a different device (laptop or another mobile phone). If that fails, and none of the suggestions in that thread work (such as resetting the mount or moving location) then the options are to return the mount if its within warranty, or purchase the optional wi-fi dongle which seems to have resolved the issue for the other users who experience the same problem

Impossible to answer with the lack of information provided. You say you want to get your kids involved, how old are they?. Through my experience of after school clubs, working with cubs / scouts / guides etc, and when my wife was a childminder, the clients kids, there was more of a wow factor when they looked at the sky and the moon through small 8 x 40 binoculars than when they clicked the mouse to take an image through a computer controlled 8" reflector. If your kids are serious, and not likely to get bored and want to go back on their phones after 30 seconds, then look at getting them each their own 8 x 40 binoculars. Not only will they get more use as they will look at anything through them, so if you ever went on country walks etc they can be used then, but will give them an excellent introduction to the night sky. But you know your children, and the Heritage is a nice table top telescope.