DaveS

Many thanks La Cebra. When we get a clear enough night that Sequence via MLPT can make the plate solving exposures etc I'll try running it again. As Waldemar has suggested it's probably something in the Settings that either I've missed, or is causing a conflict. These things should be in the manual. People (Especially those, like me, who aren't programmers) can make mistakes that lead to puzzling results. I'm sure Dr Keller knows where the problem lies, he just neglected to document it.

OK, well I've sort-of solved the Exposure Setting problem. I looked at a working version that I have on an old laptop and realised that I'd unchecked a lot of boxes (Readout mode, Dome opening, Cover opening) that I thought didn't apply, so went back and rechecked them, and now Exposure Settings works, ie I can open the exposure setting page and set up exposure sequences. It had also been affecting the Autofocus setting (I was just looking, I don't have an autofocuser) as well, which was crazy. Which of those boxes was the key I don't know, but I'm not going to risk breaking it again. That just leaves the actual Sequence Run problem, and why software should throw up unhandled exceptions at all, that just looks like bad / lazy writing.

Thanks both I tried deleting Sequence, and all it related program data files then re-installing, and re-setting my location and hardware, but the problem persists, and now I cannot even try with the exposure settings ans I get the unhandled exception error. ATM the weather is wet, and as the computer kit is in a box on a platform with the telescope I will have to wait a while before going out. RDM from my office computer is throwing up access permission issues which I just cannot be bothered to work through as my blood pressure is already too high and my hair too thin!

Ah, many thanks I did not see the Print Screen key on my micro keyboard (Needed to fit a covered desk outside). At least someone else agrees with my assessment. I hear distant rumors of a new "improved" (Yeah right, will believe it when I see it) software that is platform independent. If it runs under Linux maybe I can ditch windows and the software-breaking "updates".

I'm sorry, but that has to be my conclusion after fruitless battles with "Unhandled Exception Errors". Sequence will do an Autopoint routine, and will do a MLPT with plate solving but actually trying to run a sequence brings up an unhandled Exception error I had been able to set exposures even though the sequence crashes but now this happens. I was looking at the exposure setting in case I'd made an error, but now I cannot even do that. Clicking on continue brings up this rump of a screen apologies for the photos, but I don't know how to do screen grabs in Win10 I had been getting the sequence exception on my old Win7 laptop and thought it was just a rubbish computer, but now I'm getting the same thing on a new Win10 computer I can only conclude it's rubbish software. Sorry ASA, you make absolutely brilliant mounts, the best there are, but the software? Argh Seriously disgruntled.

Thanks Waldemar, Much appreciated.

I'm planning on adding a DDM85 Basic to my imaging collection, but cannot now find the base plate drilling pattern to mount it on a pier. I know there used to be such information on this site, but it looks to have disappeared. Does anyone have the PDF file for this they would be willing to share?

Just for reference, the last UK list price for a DDM60 Pro was £7900, I got mine ex-demo at £6300.

Well it gets stranger. I think I've tracked it down to a problem reading the filters from the wheel, possibly in Maxim. By avoiding this it looks like I can run Sequence as I could before, at least as far as plate solving for PinPoint. Still cannot run an actual sequence.

I think this has occured after a .net update. Just trying to open Sequence gets an unhandled exception error from .net framework referring to index out of bounds of the array. I've updated Sequence to 2.11 and tryed "repairing" the .net framework to no avail. Anyone else had this? Or any ideas on where to go from here?

I'd like to know as well, as the same thing happens to me. I'd put it down to the the cantankerousness of software.

Hi Mark. Sorry for the delay, been busy. Thanks, I did get past the "no autofocus" problem, I remembered to click "save" this time which I neglected to do previously. Another problem has now raised its head, an "unhandled exeption error" on clicking "run now". I'm now investigating what vital step I've missed.

Thanks Robert, I'll look into that when I get home. I thought I had the settings checked but perhaps I'd forgotten to save them.

I was trying to run a sequence for the first time last night when I hit a snag. Sequence wouldn't let me procede as I don't have an autofocuser which it was expecting. I tried to find a way of telling it that there's no autofocus and get on with it anyway, but didn't see anything, and the manual wasn't much help. So how do I go about it? And no, I'm not about to buy one just yet.

I have found it's useful to do in intermediate configuration to allow for any collimation error. I found that if I didn't then after meridian flip I could be miles out, but if I did an intermediate configuration I would land near the centre of the sensor.

I'll check the settings next dry period, but the last time I ran a plate solve it gave me correct values refining the figures I put in.

However, having paper manuals avoids cluttering my screens further, with Autoslew, C du C, Maxim, and Sequence. I can also flip through it easily while running the software. There's a use for both This reply is to the previous post.

I found tonight that syncing on the zenith position after doing the homefind greatly helps the first slew hit the target. This time Deneb was very near the centre of the crosshairs. Unfortunately when I tried an Autopoint run I only had 4 solves, so something's out. I'll take my software stick in to work tomorrow and print out the manuals, much easier to study than on the screen.

OK. Done another 4 star PA pointing file, getting better. Went from Homefind to first star without zenith sync, but..... My first star (Deneb) was so far off I had to use a RDF and gamepad to centre it. After that the subsequent 3 stars (Avoiding anything too close to the meridian or south or near the pole) hit very close to the centre of the crosshairs, now the calculation gave me errors of about 2.4' before correction, and 0.34 and 1.5' after. I think I'll call it a night as I need to turn in early and anything more will likely take more time. Happy for now!

Thanks guys I'll have another go the next clear night, though I'm still "under the weather". I'll leave out the zenith sync and go straight to CduC for my first sync and keep away from the meridian. due to my view, using stars east of the meridian makes sense anyway. Autoslew is reporting PA errors as no more than single digit minutes of arc, the latest being under 2' for both axes. Finally I've uninstalled 5.19 and installed 5.20, and it connects OK, which it didn't before. I think Stellariumscope was interfering with things. I did a trial Autogrid with Sequence and didn't get the fatal error. Hooray!

I've been getting to grips with modelling for PA and collimation, but fear it's giving me the run-around. I haven't got as far a building a whole sky model yet. The following is copied from a conversation with Mike Paling and slightly edited. What I've been doing is turning the motors on and letting Autofind tune the motors (Only getting 64% ATM, I did have 75% until I made some changes and rebalanced) before doing a Homefind, then slewing to the Park1 (Zenith) position and refining it with a spirit level before synching. In Cartes du Ciel I select a star (ATM either Vega or Deneb), and start capturing images, using the "continuous" setting in Maxim DL's camera control. When I have the star centred in Maxim's crosshairs I click "synch" in CduC. This will be my first alignment star. I then do a new Homefind Position. This is now where things get "wobbly". I click on Start Pointing File, whereupon a get a warning telling me to re-synch the mount else I'll get large offsets. I thought I *had* synched it. OK, select the same star from the Objects icon, slew (Still on crosshairs) and click the synch icon. Try again, same message. Oh well, start anyway. Use the star I'm on as No1, click the target with the tick in it to say it's centred, then on to No2, go near meridian and fairly south, repeat, star No3 is to the east and on the equator (-ish), then No4 fairly high but not to near the pole (I tend to use alpha Cassiopeia ATM). Click Stop pointing file, and calculate the result. Chances are I'll see crazy offsets measured in *hundreds* of arc minutes for all the parameters (Once I saw the PA offset measuring 1000 minutes!), even though each star was landing close to the centre of the frame. Clear that model and start again, also looking at the bottom of the Autoslew window where it reports the alignment offset for each star. This time I get sensible offsets (Even though I get the same warning about re-synching), so proceed to the PA tool, find star in the specified area and do the PA. So far, so good, however.... I've not done a full model yet, as when I've tried going across the meridian I get the crazy offsets again (Even though the target star is still hitting near the crosshairs), so something else to sort out. I tried to use Autogrid in Sequence but got a fatal error (See the thread about it). So.... can anyone throw some light on what I'm missing out, or doing wrong? I've got the PA error down to no more than 1.5' on each axis, and the collimation down from 126 (126 what? Minutes?) to about 12.5

Thanks George. Yes, I remember that thread from when I was first considering a DDM mount. When I was speaking to Rupert from Astrograph at the last Astrofest he did say that 'scopes on DDM mounts tended to aquire balance weights in surprising places. I now need to actually *think* about my plan of campaign.

Thanks, Luis. Sorry, been away for a while. the problems I've been having appear to be software related in Win 7 itself rather than Autoslew, apart from an annoying USB related glitch with the connection to the Trius camera which I had to unplug and replug several times during my pointing file build. I think a higher quality cable set here is called for. I have been finding out the hard way just how sensitive the mount is to balance. As I had changed the flattener spacing, and with it the focus distance I decided to tweak the balance using the tool in the Drive menu. Bad idea! The first run showed the lines very nearly aligned, should have left well alone, as the mount had been running fine up till then. But I thought I could refine it further. Even worse idea, compounded by not thinking to mark the original tube position so I would have something to come back to. Upshot being that after an hour and a half of nudging the tube back and forth in the rings, and getting serious aches in my hand (Incipient arthritis?) whilst cursing up hill and down dale, as we say, I have a mount that will not even turn the motors on without errors. So my job for tomorrow is to get that wretched balance right. Pity I've wasted the last clear night this week. Which brings me to my only real gripe, which is the manuals. Nowhere do I see anything about the balance tool, I'm going on what I remember from when it was set up. Hardware and software this cutting edge deserves better manuals, especially given the leap from just about any lesser mount. Sorry, as I say my only gripe, and not to do with either the hardware or software.

Hi, and thanks for the link. ATM I'm using the USB cable that came with the mount to connect it. The problems I had were with the drivers, and may have been caused by interference by other software that runs mounts, as I had StellariumScope installed as well as Eqmod. I've since got rid of the former, but need to connect a mount to be able to uninstall Eqmod (Why I don't know). A minor problem is that due to the configuration of balance weights I need USB cables with right-angled connectors to get to the hub. I may have to make my own.

Thanks George. Beginning to realise just how steep the curve is, fortunately I have a reputation as a cantankerous old so-and-so. I think a lot of the "problems" I've been having are down to my own errors, rather than the ASA way of doing things. I may need to check the balance, as I changed the flattener spacing, and with it the focus distance since the original set up. I'll have a go at updating Autoslew to the latest version, and hope I can get rid of the connection errors I had been getting. The next clear night I hope to nail down the PA, then move on to refining the collimation before building larger models. I still have to get fully to grips with Sequence and MLPT, but they will come.