DaveS

Having become totally fed up with Win-Dross stuffing up drivers etc at every carelessly coded update I am considering dumping it and switching to Linux (Probably a variety of Mint).Some software has Linux versions, while others (I think) will run under WINE in Linux. Has anyone tried this with Autoslew and Sequence? If so, with what success? Hopefully the platform agnostic software will be released to us legacy mount owners which will solve these issues.

Many thanks, and sorry for being slow to check back in. I have ordered a Sesto Senso for my TS Photoline 130 f/7. If it works as well as you say then I will probably get ofe for the FT on my ODK12 when I commission it. Now just hoping the next Win-Dross update doesn't trash more of my software.

Do ASA read these forums? Nope. probably not. I too am hoping for the new software to come along, and to work with "legacy" mounts. If truly platform independent maybe I can ditch the Win-Dross that has just stuffed up my system with a sneaky update.

I'm looking to add autofocus to my imaging train, and the Sesto Senso looks an attractive offering. Wondering if anyone on here has any experience, good or bad. TIA

Having (Cross fingers, touch wood) got Sequence playing nicely I see there is a facility for making Twilight Flats. Does anyone use this method? If so have you encountered any hitches in getting good data? Any tips/ TIA

I have windows 10 1903 on my imaging PC and have no problems opening Autoslew or Sequence. The problems I had with Sequence were from another origen.

Unless something crashes this may be my last post on the subject. Last night I ran a 4 hour sequence which I knew would involve a Meridian Flip, to see if Sequence could handle it. I kept an eye on the monitors, and as the sequence neared the pier side I went to have a look. At one point I was getting worried, as the MLPT was ticking down, and the limit was fast approaching, but all was well. As I was watching I saw the Autoslew "Telescope slewing" window pop up and the mount did the required Meridian Flip without fuss. There was next a slew to the synch / focus star followed by the new MLPT which happened without fuss, followed by the camera starting to chug through the final set of exposures. It was just a pity that cloud came in to spoil the party after one sub, however I would count the night a success.

I just hope that the "New" software that I'm hearing about will solve all these problems. It really needs to be a single integrated package with the functionality of Autoslew, Sequence, the camera control of Maxim (No need of all the other stuff) and PinPoint, plus any other tools that ASA can package in, and be debugged BEFORE release, instead of expecting end-users to be beta-testers. What irks me about the current package is having to purchase a full version of Maxim just to use the very basic functions of the camera control, not even the autosave sequence. OK, if you can afford a DDM mount it's likely you can afford Maxim as well, but it's just plain wasteful as it stands. Oh, and could we please have thorough documentation, instead of the sketchy excuse we have now, with important points either not covered, or only hinted at.

Well.... Success! (And no need for rude words ) The problem that caused the last Unhandled Exception was due to me being lazy in entering the target coordinates for that particular object. I thought I could copy and paste from the coordinates shown in Cartes du Ciel, but when I did there were no J2000 (?) coordinates shown, and I thought it didn't matter. Well, it DOES matter, since when I edited the file, manually typing in the coordinates, the other set were automatically entered. I set Sequence running last night and while waiting for the target to get high enough for Sequence to start I went inside to attend to other things. When I came out again, expecting to see the usual Error box, I found Sequence happily making the MLPT, then running the exposures. So what I have learned through all this: Sequence *needs* an autofocuser installed, even if it's only the ASCOM simulator, in which case check Never autofocus during sequence. This is actually a software bug. If your camera doesn't use readout modes check the Do not use Readout Modes box. Don't be lazy in entering the target coordinates, copy and paste will not work, type them in. And click the Automatically choose focus star. Make sure you click Apply and Save after each change. To be fair this is flagged up in the manual, but can be overlooked if working in haste. Oh, and ASA support *will* help in sorting out apparently intractable problems.

Thanks for the pointers to copy the error text I'll do that if I get another unhandled exception tonight Here is the .trg I was using last night. I have updated it since, as I may have made an error entering tho coordinates, I did not see the Corrected (?) coordinates when I had a look just now. I re-entered them and both sets of coordinated were filled out <?xml version="1.0"?> <clsTarget xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <Name>Stephan and Deer</Name> <ObjRa> 22h37m30.5s </ObjRa> <ObjDe> +34°18'31"</ObjDe> <FocRa>23h48m57.2s</FocRa> <FocDe>-02d39m06s</FocDe> <Comment>Stephan's Quintet and Deer Lick Group</Comment> <PosAngle>-----</PosAngle> </clsTarget> And the .sqe file <?xml version="1.0" encoding="Windows-1252"?> <SequenceSettings> <Lines LineNumber=" 0"> <Do>True</Do> <Numbers>1</Numbers> <Target>C:\ProgramData\ASA\Sequence\Target Files\Stephan and Deer.trg</Target> <ExposureDetails>C:\ProgramData\ASA\Sequence\ExposureSettings\3 hour RGB bin 2.exp</ExposureDetails> <MinimumAltitude>25.0</MinimumAltitude> </Lines> <Lines LineNumber=" 1"> <Do>False</Do> <Numbers>1</Numbers> <Target /> <ExposureDetails /> <MinimumAltitude>25.0</MinimumAltitude> </Lines> <Lines LineNumber=" 2"> <Do>False</Do> <Numbers>1</Numbers> <Target /> <ExposureDetails /> <MinimumAltitude>25.0</MinimumAltitude> </Lines> <Lines LineNumber=" 3"> <Do>False</Do> <Numbers>1</Numbers> <Target /> <ExposureDetails /> <MinimumAltitude>25.0</MinimumAltitude> </Lines> <Lines LineNumber=" 4"> <Do>False</Do> <Numbers>1</Numbers> <Target /> <ExposureDetails /> <MinimumAltitude>25.0</MinimumAltitude> </Lines> <Lines LineNumber=" 5"> <Do>False</Do> <Numbers>1</Numbers> <Target /> <ExposureDetails /> <MinimumAltitude>25.0</MinimumAltitude> </Lines> <Lines LineNumber=" 6"> <Do>False</Do> <Numbers>1</Numbers> <Target /> <ExposureDetails /> <MinimumAltitude>25.0</MinimumAltitude> </Lines> <Lines LineNumber=" 7"> <Do>False</Do> <Numbers>1</Numbers> <Target /> <ExposureDetails /> <MinimumAltitude>25.0</MinimumAltitude> </Lines> <Lines LineNumber=" 8"> <Do>False</Do> <Numbers>1</Numbers> <Target /> <ExposureDetails /> <MinimumAltitude>25.0</MinimumAltitude> </Lines> <Lines LineNumber=" 9"> <Do>False</Do> <Numbers>1</Numbers> <Target /> <ExposureDetails /> <MinimumAltitude>25.0</MinimumAltitude> </Lines> </SequenceSettings> I hope my less than classical English comes through the translation OK. Your "French written in English" is quite understandable If the program crashes tonight, expect more info, and possibly rude words

I have had a look at the Exposure Setting that I was using last night, and see nothing particularly unusual. Since I don't have the permissions needed to attach the file as such I have copied it as a text file in Notepad <?xml version="1.0" encoding="Windows-1252"?> <ExposureSettings> <Name>C:\ProgramData\ASA\Sequence\ExposureSettings\Stephan and Deer GB and L.exp</Name> <IsGuided>False</IsGuided> <MLPTused>True</MLPTused> <DitherAmount>5.00</DitherAmount> <GroupBySlot>True</GroupBySlot> <ExposureDetail ExposureNumber=" 0"> <Do>True</Do> <Numbers>2</Numbers> <ExposureTime>600.00</ExposureTime> <Filter>2</Filter> <Suffix>Green</Suffix> <Binning>2</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> <ExposureDetail ExposureNumber=" 1"> <Do>True</Do> <Numbers>2</Numbers> <ExposureTime>600.00</ExposureTime> <Filter>3</Filter> <Suffix>Blue</Suffix> <Binning>2</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> <ExposureDetail ExposureNumber=" 2"> <Do>True</Do> <Numbers>12</Numbers> <ExposureTime>600.00</ExposureTime> <Filter>0</Filter> <Suffix>Lum</Suffix> <Binning>1</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> <ExposureDetail ExposureNumber=" 3"> <Do>False</Do> <Numbers>1</Numbers> <ExposureTime>0.00</ExposureTime> <Filter>-1</Filter> <Suffix /> <Binning>1</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> <ExposureDetail ExposureNumber=" 4"> <Do>False</Do> <Numbers>1</Numbers> <ExposureTime>0.00</ExposureTime> <Filter>-1</Filter> <Suffix /> <Binning>1</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> <ExposureDetail ExposureNumber=" 5"> <Do>False</Do> <Numbers>1</Numbers> <ExposureTime>0.00</ExposureTime> <Filter>-1</Filter> <Suffix /> <Binning>1</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> <ExposureDetail ExposureNumber=" 6"> <Do>False</Do> <Numbers>1</Numbers> <ExposureTime>0.00</ExposureTime> <Filter>-1</Filter> <Suffix /> <Binning>1</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> <ExposureDetail ExposureNumber=" 7"> <Do>False</Do> <Numbers>1</Numbers> <ExposureTime>0.00</ExposureTime> <Filter>-1</Filter> <Suffix /> <Binning>1</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> <ExposureDetail ExposureNumber=" 8"> <Do>False</Do> <Numbers>1</Numbers> <ExposureTime>0.00</ExposureTime> <Filter>-1</Filter> <Suffix /> <Binning>1</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> <ExposureDetail ExposureNumber=" 9"> <Do>False</Do> <Numbers>1</Numbers> <ExposureTime>0.00</ExposureTime> <Filter>-1</Filter> <Suffix /> <Binning>1</Binning> <ReadoutMode>0</ReadoutMode> </ExposureDetail> </ExposureSettings> Apologies for the blurry screenshot, I grabbed it as I was working, forgot about the trick to get a region of interest, will try tonight if I get the same error. The details go on for a long list, have to scroll through them, with no way I can see to print it out or copy to clipboard. Yes, the message was "Index outside the bounds of the array" but no other indication.

Well, I got yet another, different Unhandled Exception. Sequence appeared to work as it should, slewing to a synch / focus star, made an exposure, and solve. fine, I could see everything happening on the bar at the foot of the screen, but then got the message in the screenshot. At first I thought it might have been because I'd inadvertently left the Maxim exposure window in Autosave, but a second trial with the setting changed to single produces the same result. Here is the Log, FWIW 2019_9_3_22h17m.txt

I thought I had, but then I've just seen it un-ticked. I probably neglected to save the setting. Wolfgang has replied to me with a suggestion to set the ASCOM focuser simulator, he thinks there may be a bug in the system with Sequence expecting a focuser, and crashing if one isn't installed. I tried that following Luc's suggestion but it looked to have stuffed up the Exposure Settings page. I think it's OK now. Software does my head in, there are so many interacting routines / threads / subroutines etc that finding where the *actual* problem lies, rather than where it *looks like* it lies is a real nightmare for someone who isn't a software engineer.

I have to use Maxim for the saving, as Sequence crashes with Unhandled Exception Errors before it can even make the Synch exposure. From looking at the Sequence Logs (Which I only recently found D'oh!) I can see the last entry is for Readout Mode -1 which is silly. This is the latest from an aborted trial run. 20:33:46.724: ************************************************************************ 20:33:46.724: Starting Sequence on Target C:\ProgramData\ASA\Sequence\Target Files\Crescent.trg with Exposure settings C:\ProgramData\ASA\Sequence\ExposureSettings\2 Hour Hydrogen Bin1.exp 20:33:46.740: Running now Nr. 1 of this Sequence 20:33:46.802: Starting Sequence C:\ProgramData\ASA\Sequence\Target Files\Crescent.trg 20:33:46.802: Target RA: 20h12m49.72s DE: +38d24m44.2s 20:33:46.818: Focus RA: DE: 20:33:46.833: Focus star was not defined and focus is disabled but I need a place to synch, so autoselected with RA = 20h12m49.7sDE= +39d58m35s 20:33:46.833: Checking now for Pier side for object 20:33:46.849: Could finish Object on Eastside 20:33:46.849: Can only be made on East side 20:33:46.865: Not same Target, check if we have to Autofocus or Synch 20:33:47.739: No Autofocus, because NeverDuringSequence is selected 20:33:47.771: Moving Scope to Autofocus Positon 20:33:47.864: Slewing to 20h12m49.7 +39°58m35 Pierside East 20:33:57.575: Setting Readoutmode -1 At that point it crashes. I'm just going to bring the rest of the Logs into my office computer where I can look at them at leisure.

OK, I'm in email contact with Wolfgang from ASA support, and he thinks I've done something wrong in my .ini file, as a simulation using it crashed. What though I don't know. I will wait and see what he come back with after TeamViewing my computer during a run before nuking the software.

Just running some Bias frames, that I was planning on anyway. Just Maxim connected to the camera. No problems so far.

Thanks Mark, I'll try your suggestions. My start up routine, that has been fine in the past, is: Power up the mount and its associated hardware Turn on the computer, login, wait for everything to boot up Launch Autoslew, turn on the motors and perform Homefind (It's a DDM60) Launch Cartes du Ciel, connect Telescope Launch Maxim DL, toggle Camera Control, connect camera. At this point I sometimes get a "Cannot connect filter Wheel" error, cleared by unplugging and replugging the USB from the filter wheel to the Trius Hub Slew to a convenient star (I've been using Deneb ATM), fine adjust if necessary, and click Synch in C du C Launch Sequence and Connect. Set up the Autosave sequence in Maxim, Apply, OK Slew to the target, check framing then run MLPT Run the sequence,

And now it's stuffed up an imaging run AGAIN. I son't know what it doesn't like but since I changed the filters in the wheel it's playing silly Bs with the Trius camera, so it looks like it's connected but the cooler shown -16 instead of -20 and a trial sxposure shows nothing. I set everything up as normal, slewed to Deneb and synched, fine, niche sharp stars. slew to my target, temp shows -16 and no stars. I blame Sequence since reading the filters from the wheel. I give up, time for the big hammer I think, hardware and computer and software.

I had a look, and found the .exp files but cannot attach them due to a permissions issue. There were no .sqe suggesting that Sequence crashed before it could write them.

And now the damn rubbish software is throwing up the Unhandled Exception Error when I try to set the exposure AND I DON'T KNOW WHY. I'm sorry Dr Keller, Doctor you might be but you know diddly-squat about real-world users. Now seriously angry.

Sorry for late replying, been doing boring house stuff. Thanks Luc, I'll give that a go. Seems strange that Sequence cannot accommodate not having a focuser, but brings up the scenario in the software dept..."But Herr Doktor Keller, what if someone does not have an autofocuser?" "Ach, everyone has an autofocuser..." Raining at the moment and my kit is in a cabinet outside. When it clears up I'll go and download the ASCOM simulator.

I've had none of the problems you report (Yes,I do understand), The mount (DDM60 pro) slews with utter silence, and points well, perhaps because it has a more manageable load in the form of a 130mm f/7 triplet apo with a 80mm astrographic refractor on top. So far MLPTs made for a Maxim DL Autosave sequence work well, and my images show small sharp, round stars. When tracking with a MLPT I usually only see the hundredths of arc sec figures changing. I spent quite a long time with the balance tool getting it as exact as I could, though only in RA and Dec, balance around the optic axis is still a little out. I've never seen Autoslew switch to Terrestrial Tracking, it's either been Parked and not tracking at all or else following Sidereal Tracking. At some time soon I intend to run another iteration of the polar axis alignment, as currently one axis (The RA I think) is showing 3 arc min of error which I would like to get out, I'm seeing quite large MLPT errors before correction. This will need a new Autopoint model, which Sequence is still capable of doing.

My old laptop has been throwing up USB errors with my Trius 694 camera that had me puzzled for a long time, at first I thought it was something to do with the camera, so I've stopped using it for this application. In Sequence the telescope will slew to a point that may be an autofocus star, or the first MLPT exposure, I do not know which, because it is at this point that I get the first Unhandled Exception error, with no exposure made. After closing the program and checking with Cartes du Ciel the telescope is pointing well off from the target. I have sent an email to ASA support, now waiting (Yes, haha) for a reply.

Well, I tried running a Sequence last night and got the usual Unhandled Exception message. I Clicked Continue and went to look at the exposure settings, whereupon I got the Unhandled Exception error I had before when trying to set exposurs, which suggests, something in the exposure settings file is wrong. However I could easily be wrong about this, as software has a cantankerousness all its own, and the real problem may well be somewhere else, and not obvious to a non programmer.

Slightly better, yes. The Autoslew manual now tells you *how* the balance tool works, instead of leaving you to guess, but the Sequence manual is still incomplete, or rather it's in two parts. The current one tells you how to setup sequences, but to know how to set up an Autopoint you have to look in the previous manual, which has bits missing as well. Argh! Reading the handbook / manuals for the DDM85, it looks like they were written for technicians maintaining the mounts in a professional observatory, with references to the employer's Health and Safety protocols. Annoyingly, although the sky cleared at about 11 o/c (Local BST time), by that time I was still feeling rubbish, with headache and shivers, so had an early night, rather than push it.