I'm running the trial of CCDAP since Sunday and I've been getting a couple of errors depending on the direction I go. I'm sure it's just a few simple settings that I've missed. I have the following pieces of software and hardware that I’m trying to get CCDAP to communicate with:

Software-
CCDAP v4.15.8
TheSky6 v6.0.0.61
MaxImDL v5.07
FocusMax v3.4.30
PinPoint Engine v5.0.14 full version as a trial (Visual PinPoint Application v5.0.3)
GSC 1.1
ASCOM v5.0a
Windows XP Professional SP3
.NET Framework v1.1, v1.1 Hotfix (KB928366), v2.0 Service Pack 2, v3.0 Service Pack 2, v3.5 SP1
Also, .NET Compact Framework v2.0 SP2


Hardware-
Meade RCX400 using LX200GPS 5.0.0 driver
Meade DSI IIIc
Starlight Xpress Lodestar
Moonlite Focuser which uses the EasyFocus ASCOM driver
Right now I’m imaging through an 80mm ED APO mounted on my RCX and guiding with the RCX. The Moonlite focuser is on the 80mm ED APO.

I've been able to get everything to run in some combination, but not everything with CCDAP.

The first error I saw was when I clicked the Connect button in CCDAP and I got an error that stated that "FocusMax was not installed or Focuser not responding. Resetting Focuser Control to none." I tried uninstalling FocusMax and reinstalling, but got the same thing. (BTW I did install using the installer and then pasted the patch .exe over the original .exe). If I proceed with focuser control set to none, then I did manage to run through a test session where I was able to slew to target, plate solve, start guiding and take images. I didn't have the guider settings set up correctly so I didn't get any good image data, but it seemed to run through the processes correctly.

Next I tried opening FocusMax first (which opened up MaxIm and connected the camera) and then opening CCDAP and connecting. All seemed well, except that it appears that FocusMax wouldn't allow CCDAP to see that I had a camera attached. So I repeated the startup procedure, but this time I disconnected the camera before connecting with CCDAP. This seemed to work. I saw all of the correct software in the Software Versions window and everything looked good. The Unhandled Exception error came shortly after the session started. I have attached a copy of the log file and I will also post a screenshot of the one of the unhandled exception errors (they all said the same thing). Sorry for the length of this post, but I hope this is all good information to try to find a solution. Like I said, it's probably something simple that I've screwed up in the setup of everything.

Thanks for your help,

Mike Canfield

ccdap20091001_204338.log (4 KB, 10 downloads) CCDAP Log

Here is the screenshot attachment of the Unhandled Exception error.

Thanks,

Mike Canfield

CCDAP_Error2.doc (260 KB, 11 downloads) Unhandled Exception Screenshot

Hi Mike,

Regarding the FocusMax issue, see CCDAP Help/Troubleshooting Techniques, Hint topic. You need to start the underlying applications before starting CCDAP. Not all apps initialize sequentially or gracefully when invoked by CCDAP. You should always start the application and connect to the related hardware first.

Regarding the exception, I need to see the first 115 lines of exception message. Click on the Details button and copy and post the text.

Thanks John.

I'll look over the troubleshooting techniques today. I won't get a chance to reproduce the error until this evening, but I'll post the details as soon as I get them.

Mike Canfield

Please find the unhandled exception error details attached.

Thanks,

Mike Canfield

Unhandled_Exception_Details.txt (4 KB, 7 downloads) Unhandled Exception Error Details

John,

It just hit me that you probably wanted me to post the text directly, not it an attachment. The following is a duplicate of the previous error details.

Thanks,

Mike Canfield


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at n.c1()
at n.adv()
at y.ab()
at n.aby()
at n.gx(Object A_0, EventArgs A_1)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
CCDAutoPilot
Assembly Version: 4.15.8.0
Win32 Version: 4.15.8.0
CodeBase: file:///C:/Program%20Files/CCDWare/CCDAutoPilot4/CCDAutoPilot.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
RestoreState
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/CCDWare/CCDAutoPilot4/RestoreState.DLL
----------------------------------------
SyD.Shareware.Registration
Assembly Version: 2.3.2007.1
Win32 Version: 2.3.2007.1
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/SyD.Shareware.Registration/2.3.2007.1__4a5d6e6bca524051/SyD.Shareware.Registration.dll
----------------------------------------
OutlookPanes
Assembly Version: 1.0.4.0
Win32 Version: 1.0.4.0
CodeBase: file:///C:/Program%20Files/CCDWare/CCDAutoPilot4/OutlookPanes.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Runtime.Serialization.Formatters.Soap
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Serialization.Formatters.Soap/2.0.0.0__b03f5f7f11d50a3a/System.Runtime.Serialization.Formatters.Soap.dll
----------------------------------------
Interop.PinPoint
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/CCDWare/CCDAutoPilot4/Interop.PinPoint.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Mike,

Thanks. An attachment is fine.

After entering target information, did you save your target list? See Menu/Target Lists/Save. That may have caused the problem. If you did save it and still saw a problem, please post the target list as an attachment.

Hi John,

I'll give you the 2 target lists I've made up. Both were producing the error. Test2 list is the one I ran that produced the error details that I posted. Since all of this was for testing the trial, I originally had NGC 224 & NGC 598 on the same list and got the exception error. Then I split them up thinking maybe the list was screwy or something. As far as saving target lists go, I have been saving the list as soon as any changes were made. This includes changing the start time of the target, which I was doing a lot to try to re-run the session. But I am certain that I was getting the list saved. One odd thing that I noticed is that when I looked for the target list files, they were under System Profiles not Target Lists. Maybe I just saved them in the incorrect location, but do they need to be in Target Lists? I assume the files can be stored anywhere on the drive, you just need to load the appropriate list into CCDAP to run it. Also, I wanted to mention that on the first night of testing I was able to get CCDAP to slew to NGC 224, plate solve, perform a correcting slew, begin guiding and then begin imaging. As I emtioned before, the results were not pretty, but that was due to my not having the correct guider settings entered. But CCDAP did perform as it should have, IMO. The only thing is that I did not have FocusMax going during that time. That was the same night I got the FocusMax error. As I'm sitting here typing this, I'm thinking I should have tried running the session with focuser set to None to see what happens. I'll go back out this afternoon and try that just to see if it will run the session like it did on the first night out. I should also mention that at present, I have to setup all of my equipment and polar align each night. So some of my testing has been in the shop where I keep the scope when not in use just so that I don't hawl all of the equipment out, align, etc. and find that I have to fiddle with errors all night. I hope to have an observatory built around the beginning of the year, which is the main reason for my looking at CCDAP. If this sounds like it could be presenting a problem for testing please let me know and I'll do a full setup.

From what I've been able to see, CCDAP is awesome. Once all of the little bugs are worked out of my system it should be a REAL time saver.

Thanks for your help on all of this,

Mike Canfield

Test2.xml (55 KB, 4 downloads) Test2 Target List

Here is the other Target List.

Test_List.xml (55 KB, 6 downloads) Test_List Target List

Hi Mike,

The target list can be stored anywhere on the hard disk.

I ran both target lists in simulators without a problem.

It may be something with FocusMax. Can you post your log as an attachment from your successful run so that I can see your configuration?

Did you have Focus before Target Start checked on the Options page?

When you are under the stars sometime, try Focus Now on the Focusing page to see if the automation interface between CCDAP and FocusMax is working properly in your system.

Hi John,

I did have Focus before Target Start checked when the unhandled exception errors have ocurred. I believe I also had it checked during the successful runs with focuser set to None, but I can't remember for sure. I assume that if no focuser was selected it would ignore the fact that it was checked? Same thing with Focus checked on the LightFrames tab and also refocus every xx min on the Focusing tab?

I have attached a log file which runs through the session until after one exposure has been taken of NGC 224. I'll post another of the same thing, but with NGC 598. I aborted the each run when I was having problems with the guide star.

I was thinking that I should have tried the Focus Now option earlier. Hopefully the weather will clear up at some point this week. Right now the forcast is for clouds all week, but I'll get out there as soon as I can to try it. Although, I guess I can press the button just to see if it communicates at all. I'll try that this afternoon and get back to you.

Thanks,

Mike Canfield

ccdap20090927_212748.log (7 KB, 4 downloads) NGC 224 Successful Log File

Here is the successful log file for NGC 598.

ccdap20090927_213608.log (10 KB, 5 downloads) NGC 598 Successful Log File

Hi again John,

I tried the Focus Now button, but I forgot that I un-installed and re-installed FocusMax and lost my V-Curve. I don't think FocusMax will allow me to try to focus until it has a V-Curve saved. Maybe I'm incorrect, but the focuser didn't make any movements. I aborted the run after a minute or so. I am going to attach the log file from this test just in case you can see something useful. Also, I did try setting focuser to None and running the session. It appeared to run normally. Of course I had to abort this session as well. I'll post it as well.

Thanks,

Mike Canfield

ccdap20091003_174910.log (4 KB, 4 downloads) Focus Now Log File

Here is today's session with Focuser set to None.

ccdap20091003_172247.log (5 KB, 6 downloads) Focuser set to None Log File

Mike,

You can't run FocusMax without V-curves - it just doesn't work that way.

I strongly suggest you start the underlying applications in the order suggested in the help file. If you have to close any apps for any reason, be sure to close all of them in the revers of the order opened. Use task manager if there is any doubt if an app is closed or not. For example, if you close Maxim and FocusMax is still open and then close FocusMax, it may or may not close. Check in task manager.

Once you have the individual apps up and running and connected to their related hardware, then start CCDAP.

As a side note, suggest you bin your guider 2x2. You will generally get better results. Of course you will need to reinitialize.