Jump to content

tbaehnck

Beta Tester
  • Content Count

    82
  • Joined

  • Last visited

About tbaehnck

  • Rank
    Member
  • Birthday 09/25/1969

Profile Information

  • Gender
    Male
  • Location
    Norderstedt, Germany

Recent Profile Visitors

86 profile views
  1. Thank you. I have looked at the solution of kolec but it is not so convenient. I test voyager in the last weeks also. And it seems exact what i'm looking for. It does all that I want, okay without mlpt, than it would be perfect. But I will go for it. If anybody interessed in, you find it here https://software.starkeeper.it/. For two cameras you need the 2 array version. Leonardo the or one of the programmers was so helpful to me also with remote support. It was fantastic.
  2. Hi, for redundancy reasons I would like to have the possibility to access the ASA with a second computer. Is this reliably possible with a USB server wich I connect with ethernet? Does anyone have any experience with this and which devices can you recommend? Reliability is the first priority and USB 3.0 is not necessary. Thank you Thomas
  3. Waldemar thansk a lot for your effort. Dithering is a must have feature, and of course i can setup a second computer with another Software but what I like to have is that the two imaging instances communicate with each other. So if Setup1 is ready and like to dither setup 2 is still exposing due i.e. different download times or something else, camera 1 should wait and just start when camera 2 is ready also. Also setup 2 should wait if setup 1 is calibrating the guider or make an autofocus routine. I hope that makes it a little bit clearer for what I'm looking for.
  4. Hi ASA friends, I'm very pleased with Sequence and MLPT on my DDM60pro overall, but I am now looking for a solution for a Dual setup with two cameras on one mount. As I know there ist no software out there wich supports mlpt, but sequence can only support one camera. I found some software products wich be able to control two cameras with synchronized dithering on paper. Voyager and N.I.N.A. Voyager works together with MaximDL, N.I.N.A. will not. Have anyone experience with the software above? Or what kind of solution are you using? BTW: I given up waiting for a new software from ASA. Thanks and best regards Thomas
  5. HI Daniel, no, thats not the setting for your needs. "New autofocus after every line" means, if you have different objects (lines in the sequence run window) that every object will start with a new focus. The other option you have, is to use the setting autofocus every XX minutes. Thats what I use. autofocus after each filter is not possible because you can use offsets either in sequence or in your ascom driver. That is much quicker and saves you a lot of time. All you have to do is to focus each filter separately ones time and write down your difference values to your reference filter i.e. L-Filter. Hope it helps. Best regards Thomas
  6. Hi Daniel, I use a Navilock NL-602U since years and it work flawlessly. It has a magnet at the bottom, so I can easy attached it at the pier. BR Thomas
  7. Hi all, I can report, that the problem is solved . i install the the ascom driver of the atik 460 new, install sequence again and what I think the most important I didn't check the "don't use readout mode" option in the ccd settings. My camera doesn't have different readout modes, but if I didn't check the option and click "read from ccd" the readout mode change to "standard". And now all work fine. I still have errors in the sequence log (error setting readoutmode to 0) but no crash of the programm and I will be able to use sequence for more than pointingfiles again. . Thanks for helping and clear skies Thomas
  8. Hi Nigel, In between I made a new clean installation of Windows 7 with all updates before I install autoslew and sequence. But the same error has come up again. After a phone call with Asa yesterday, I deleted the system.ini of sequence and made all settings again, but this doesn't work neither. Autoslew and sequence are the the latest stable ones, no betas. Other software on the astronomy PC is focusmax, maximdl 5, pinpoint, and ccdinspector. Thats all.
  9. Hi Mark, First thank you for your answer and sorry for doing it so late. I tried it but it doesn't help. Then I have done a full new installation of Windows, autopsies, sequence etc. And I get the same error. Any ideas, anybody? Thank you and best regards
  10. Hi all, I've a problem since a few weeks with sequence. I thought after I switch to another autoslew-version but not sure about it. I have AS 5.2.4.7 and Sequence 0.2.1.1 and also try 0.2.1.3 with the same error. If I start a sequence I get this error message: Informationen über das Aufrufen von JIT-Debuggen anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung. ************** Ausnahmetext ************** System.NullReferenceException: Die Objektvariable oder die With-Blockvariable wurde nicht festgelegt. bei Microsoft.VisualBasic.CompilerServices.Symbols.Container..ctor(Object Instance) bei Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack) bei Sequencer.RunSequence.RefocusFilter(Int16 NewFilterNr) bei Sequencer.RunSequence.ChangeToFilterAndRefocus(Int16 Filter) bei Sequencer.RunSequence.StartSequence() bei Sequencer.frmSequenceRun.cmdRun_Click(Object sender, EventArgs e) bei System.Windows.Forms.Control.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bei System.Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.ButtonBase.WndProc(Message& m) bei System.Windows.Forms.Button.WndProc(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Geladene Assemblys ************** mscorlib Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8793 (QFE.050727-8700). CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll. ---------------------------------------- Sequencer Assembly-Version: 0.2.1.3. Win32-Version: 0.2.1.3. CodeBase: file:///C:/Program%20Files/Sequence/Sequencer.exe. ---------------------------------------- System.Windows.Forms Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll. ---------------------------------------- System Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8791 (QFE.050727-8700). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll. ---------------------------------------- System.Drawing Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.5495 (Win7SP1GDR.050727-5400). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll. ---------------------------------------- Microsoft.VisualBasic Assembly-Version: 8.0.0.0. Win32-Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll. ---------------------------------------- Microsoft.VisualBasic.Compatibility Assembly-Version: 8.0.0.0. Win32-Version: 8.0.50727.5483. CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic.Compatibility/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.Compatibility.dll. ---------------------------------------- Interop.PinPoint Assembly-Version: 1.0.0.0. Win32-Version: 1.0.0.0. CodeBase: file:///C:/Program%20Files/Sequence/Interop.PinPoint.DLL. ---------------------------------------- mscorlib.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8793 (QFE.050727-8700). CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll. ---------------------------------------- Interop.MaxIm Assembly-Version: 1.0.0.0. Win32-Version: 1.0.0.0. CodeBase: file:///C:/Program%20Files/Sequence/Interop.MaxIm.DLL. ---------------------------------------- System.Xml Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8773 (QFE.050727-8700). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll. ---------------------------------------- System.Configuration Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll. ---------------------------------------- 63tk0aa1 Assembly-Version: 0.2.1.3. Win32-Version: 2.0.50727.8791 (QFE.050727-8700). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll. ---------------------------------------- Microsoft.VisualBasic.resources Assembly-Version: 8.0.0.0. Win32-Version: 8.0.50727.5420 (Win7SP1.050727-5400). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/8.0.0.0_de_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dll. ---------------------------------------- System.Windows.Forms.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll. ---------------------------------------- ************** JIT-Debuggen ************** Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der Konfigurationsdatei der Anwendung oder des Computers (machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden. Die Anwendung muss mit aktiviertem Debuggen kompiliert werden. Zum Beispiel: Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten Ausnahmen an den JIT-Debugger gesendet, der auf dem Computer registriert ist, und nicht in diesem Dialogfeld behandelt. The the sequence log file: 00:49:54.619: ************************************************************************ 00:49:54.622: Starting Sequence on Target C:\ProgramData\ASA\Sequence\Target Files\NGC 4216.trg with Exposure settings C:\ProgramData\ASA\Sequence\ExposureSettings\L_180s_mlpt.exp 00:49:54.626: Running now Nr. 1 of this Sequence 00:49:54.748: Starting Sequence C:\ProgramData\ASA\Sequence\Target Files\NGC 4216.trg 00:49:54.749: Target RA: 12h16m52,7s DE: +13d02m34s 00:49:54.750: Focus RA: DE: 00:49:54.754: Focus star was not defined and focus is disabled but I need a place to synch, so autoselected with RA = 12h16m52,7sDE= +14d21m12s 00:49:54.755: Checking now for Pier side for object 00:49:54.766: Cannot finish complete Object on Eastside 00:49:54.774: Have to start on East side because cannot be started on West side 00:49:54.775: Not same Target, check if we have to Autofocus or Synch 00:49:55.626: No Autofocus, because NeverDuringSequence is selected 00:49:55.626: Moving Scope to Autofocus Positon 00:49:55.682: Slewing to 12h16m52,7 +14°21m12 Pierside East Any Idea whats going wrong and what to do? Thanks and best regards Thomas
  11. Hi all, the DDM60 will remember the Last Postion, im my case "Position Park 1". If you don't touch the mount and absolutley don't move one of the axis, you can start from there without a new homefind. Otherwise you can't. I can live with that. Cost me 1 Minute to do a homefind. Best regars Thomas
  12. Hi Dirk, no I'm not using CCD Autopilot. I'm trying to use sequence for my semi automationprocess, but as a few other folks, I have crashes of sequence the last time i have used it. I have lost two wonderful nights of imaging. Very bad. Bad Schwartau? I'm driving by nearly every day on my travel to work. Best regards Thomas
  13. Hi sdufoer, Hi Dirk with my DDM60pro I have no problems with that and there was no changes between the autoslew versions, as I know. I'm running AS 5.2.4.0 at the moment and MaximDL5 In autoslew I have checked "Flip Guidedirections after Meridianflip" in "Control/autoguider Settings". In MaximDL camera Control/Guide/Settings/advanced I checked "Reverse X" in "on Pier Flip" In the guide tab I have NOT checked "pier flip" or "auto pier flip" but in autoslew "prefer west" in "Mount/Flip Options" With these settings I never had a problem after a meridian flip. Hope it helps. BR Thomas
  14. Hi Nigel, in theory you are correct. What I recognized was that there si always a small amount difference when syncing with sequence and e.x. MaximDl which not be can described with year now/ y2000 problematic. e.x. when i sync in maximdl with plate solve a frame and after that without moving the telescope do the same in sequence, sequence shows me a little offset. But to your question normally it doesn't matter in which software the sync will be made. BR Thomas
  15. Hola Juan: Bienvenido al foro. No hablo español, así que tengo que usar un traductor. No sé por qué no debería funcionar. Sequence sólo controla MaximDL y si la cámara funciona correctamente, también funcionará en Sequence incluyendo MLPT. ¿Tiene sentido la traducción? Cariños, Thomas
×
×
  • Create New...