Multiple Unhandled Exception

[calaban]

Hi

I've struggled with errors for some time now. I have tried USB RJ45 extension adaptors, active repeater cables - both USB2 and 3, have certified 1m USB2 cable, anti movement clips, .. etc. Still having issues.

Using BYE 3.1.9, Win7, 5DIII and 1DX.

Lots of repeated "Unhandled Exception". Can click "Continue" and keep going but usually it's just the start of a downward spiral.

Attached is the text from the error message, I hope it may help.

Cheers Richard

Unhandled Exception RT.txt

[calaban]

Hi Guys

I owe you an update.

Changed motherboard from Asrock to Supermicro. Realised that the USB to RS232 converter cable to mount did not have an active extender cable - installed one. Wired all my 6 battery packs in parallel and then from that 'power rail' connect power to the devices - screen, computer, mount, dew heaters, ....

Bottom line, last 3 shoot sessions completely error free, no software issues at all.

Thanks for your support.

Regards Richard

[admin]

2 hours ago, calaban said:

UPDATE - winter in Perth, Aust however had a go last night. What I did was use CCD cameras only (No EOS or BYE used) . PHD2 guiding, all ASCOM stuff, Stellarium, same ASROCK ITX computer, battery power etc etc.

'Good' news is not one error.

Have removed BYE and installed into a different folder. Will try this next time, not sure why there's a difference in doing this but yes computers and be funny things.

If this is a result of a bad installation, installing in s separate folder will ensure the new installation is a clean one.

[calaban]

Hi

Setup again last night in the backyard. Same everything as my last post however this time with 5DII on the main lens.

First, installed BYE 3112 RC9 in a new folder. Started running a few programs and then BYE. Went to Settings to set a few things, got to Name Item 9 and 'bang'. See Snap 09 and txt file of that name. Hit Continue and each time I then clicked on BYE same error popped up (several times until I finished the Naming sequence).

Then OK for a while - 40 odd minutes - and then Unhandled Error, this time titled BYE 5DIII. Hit Continue and kept on going.

Clouds rolled in soon after and that was it.

I've been struggling with this for a year now. (At least it feels like that).

Not one error a few nights ago with no EOS / BYE but then last night the above and attached. All the same gear and set-up.

Regards Richard

BYE 5D-MKIII Un H Ex.txt

Filename Template Editor Un H Ex.txt

[astroman133]

So you get the reported exceptions with multiple cables and multiple cameras. Have you tried a different PC? What other I/O is going on at the same time? Autoguiding? Is the PC a high end machine, or a low-end machine like a Surface or Netbook?

[admin]

Looks like you have an installation gone bad OR .net may not be up do date.

I would start by reinstalling BYE in s separate folder and see if this fixes the issue.  

Regards,

[astroman133]

Sorry, but your screen shots are not readeable. BYE log file may be more useful.

If I understand correctly one of the crashes occurred when the camera was not even connected...when you were on the Settings screen defining the file name template. Is that so? That is very strange.

BYE 3.1.9 has been very stable and no other user has reported anything similar. And it happens with 2 different PCs? This seems like a Windows or .NET issue. Are you up to date with system updates? It may also be related to interaction by an anti-virus program.

 

[admin]

As Rick said, we can' event read the error from the screen shot.

However, this is not a BYE error, it seems like a low level Windows error.  

Is .net up do date as Rick suggested?

[calaban]

Hi Guylain & Rick

Better crops attached, the first think I do is connect the 5DIII so yes it was connected when I was in Settings. Had about 10 of these error before exiting Settings. Then 40 minutes later the BYE 5DIII error.

Yes everything up to date.

On the Friday (Post above on my Saturday) used ASI 0712 MC on main lens and QHY5L-II on guide lens. Not one error for the evening.

On Monday, same computer, same software, power, operator, same updates, same everything just that ASI 071 MC replaced by 5DIII on the main lens.

BTW - when you say install in different folder - both "Install BackyardEOS Folder" and "Start Menu Folder" or just the BackyardEOS folder.

Next time will remember to copy the BYE logs. Maybe a development idea there, ability to automatically save the logs a la PHD2.

Appreciate the support.

Regards Richard

 

[astroman133]

When Guylain suggests to install BYE in a different folder he means the Destination Folder. The Start Menu folder does not matter.

The logs are not deleted. So if you have logs from a session with the exceptions, you should zip them up and send them to Guylain.  Not all the logs. Just those from that evening.

I would also suggest that you make all your settings changes with the camera not connected to the PC. Does BYE behave itself or do you still get exceptions?

This is a strange issue that nobody else has that affects only BYE, but not other applications.

[admin]

I'm not sure where to go from here.  This seems to be a .net error.

************** Exception Text **************
System.IO.IOException: The handle is invalid.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.__Error.WinIOError()
   at System.Threading.EventWaitHandle.Set()
   at System.Windows.Forms.Control.ThreadMethodEntry.Complete()
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
   at System.Windows.Forms.Control.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)

 

What I was able to find out from the files you attached in your fist post is that this appears to be caused by DevExpress,

You don't need to use all lines in the filename template editor.  You have have several items on one line.  Something link <duration>_<iso>_<somethingelse> on one line may allow you to have your file name without using all lines.  This may help.

[calaban]

Guys

I can see that I took the screen shots at 5:32pm and 6:35pm however the errors occurred before that, how long before I'm not sure.

Found the BYE Logs - nice system BTW - and have attached logs for a period before the above times.

Regards Richard

BYE Log for BYE 5DIII UnH Error.txt

BYE Log for Filename Template Editor UnH Error.txt

[astroman133]

The provided log files are fragments. They do not show the information around BYE startup or camera connection.

They do, however, show, that you are communicating with a TemperHum. Do the exceptions disappear if you remove the TemperHum device?

[calaban]

Sorry, misunderstood "Not all the logs", understand now.

The TemperHum was connected when just CCD's used. OK next time can try without it.

Log files covering the two events attached.

Thx

logfile-[20170717-17h50m02s140]-[2032]-2017-07-17.txt

logfile-[20170717-17h56m19s661]-[3780]-2017-07-17.txt

[calaban]

Guys

Thanks for the comments.

Yes, multiple cameras - 1DX and 5DIII - multiple cable options and two PC's, both ASRock ITX with PICO 120W PSU, Win7, always Windows Updated, one Q2900 the other N3700. Rarely all hooked up at once. Split over two PC's or some gear on one or the other - just get errors.

Yes, PHD2 with QHY5L-II Mono.

Test inside - replicate 'field conditions' - all is fine. Take it outside and all falls apart.

One thing I thought of was ASCOM, EQMOD, PHD2 etc not replicated when inside. So yesterday started testing inside with these running, the error occurred and I started this post. Since then have installed 3.1.11.

This morning testing again, removed the V-800 USB GPS module as an idea (both PC's have one), ASCOM and PHD2 running, tested for a little while, started this reply and half way though typing - ERROR. Two logs attached.

Sometimes switching to Frame & Focus BYE defaults to 102,400 ISO and does not do LV Sim. It still works for focusing but will not respond to changes in shutter, aperture or ISO. Maybe a different thread.

Will try next by installing BYE in different folder - let you know what happens. I'm starting to think its ASCOM, EQMOD compatibility with ........ ?

Regards Richard

BYE Log.txt

NET Framework Error.txt

[astroman133]

I was thinking that your unhandled exceptions could be due to too much USB traffic that is why I asked how powerful your PC is. It seems to be more common on lower powered netbooks.

It does not seem likely that a different installation would make a difference. If there were a problem with BYE, more users would be reporting it. To date the reports have come from users with what appear to be underpowered computers.

I would try both with and without PHD to see if that makes a difference in your symptoms.

[astroman133]

Do you have "Auto power off" disabled in the camera?

In one of the log files I see "2017-07-17 18:59:39,925 [OnStateEventHandler] INFO  - StateEvent_Shutdown Fired! (inParameter=0)". I believe that this tells BYE that the camera is shutting down. The most likely causes of this are a low battery or Auto power off is enabled and the camera has been idle for a period of time. Once the camera has been shut down, subsequent access by BYE could cause the SDK to report "Invalid handle" errors.
 

[calaban]

Auto Power is Off,

The battery was flashing at one point and needed changing.  18:59 is well after the errors.

[calaban]

Auto Power Off is Disabled - more correct

[calaban]

UPDATE - winter in Perth, Aust however had a go last night. What I did was use CCD cameras only (No EOS or BYE used) . PHD2 guiding, all ASCOM stuff, Stellarium, same ASROCK ITX computer, battery power etc etc.

'Good' news is not one error.

Have removed BYE and installed into a different folder. Will try this next time, not sure why there's a difference in doing this but yes computers and be funny things.