Jump to content

Canada's top-tier Telescopes & Accessories

calaban

Members
  • Content Count

    15
  • Joined

  • Last visited

About calaban

  • Rank
    Red Giant

Recent Profile Visitors

476 profile views
  1. 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
  2. Auto Power Off is Disabled - more correct
  3. Auto Power is Off, The battery was flashing at one point and needed changing. 18:59 is well after the errors.
  4. 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
  5. 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
  6. 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
  7. Guys, installed 3.1.12 RC9 in separate folder and this issue seems fixed. Thanks Richard
  8. 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
  9. Hi Running BYE 3.1.11 (reinstalled in a different folder), take a few images, focus and adjust setup in Frame & Focus and after a short while and after switching back to Frame and Focus, I lose the Aperture notification. Change Shutter to Bulb and Aperture reappears but no Duration. Back to set shutter speed (Manual) and Aperture there until I change Shutter speed and Aperture lost again. See two attached images. Camera EOS 1DX. ITX Computer. Noting of interest in the BYE Logs. Have TemperHUM version : [TEMPer1F_H1V1.4F] Thanks, appreciate the support, Richard
  10. 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.
  11. 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
  12. 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
  13. Guys Thank you for the replies. Exposure Simulation setting was the problem. Now 'enabled' and all good. Sorry - simple one - simple when you know ! Cheers
  14. Hi The screen is black in Live View and any adjustment to ISO or Shutter Speed or ......... makes no change to the Live image. Taking the picture however and making adjustments you can see the changes. I also have a 5DIII and that works fine in Live View, I can make adjustments to the camera settings in LV and the changes take affect on the screen - increase ISO and the stars are brighter. The 1DX seems to have fixed setting in LV that result in a black screen. Up the ISO and Shutter time and still black in LV but take the shot and you can start to see the stars. Hope its an easy one. Using BYE 3.18 Premium. Various computers / laptop - same story. Thanks in advance.
  15. Interesting - I have the same or very similar problem with my 'old' 1DX. The screen is black in Live View and any adjustment to ISO or Shutter Speed or ......... makes no change to the Live image. Taking the picture however and making adjustments you can see the changes. I also have a 5DIII and that works fine in Live View, I can make adjustments to the camera settings in LV and the changes take affect on the screen - increase ISO and the stars are brighter. The 1DX seems to have fixed setting in LV that result in a black screen. Up the ISO and Shutter time and still black in LV but take the shot and you can start to see the stars. Hope its an easy one. Thanks in advance.
×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use