Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

Help needed please


cruxaustralis
 Share

Question

Hi,

I upgraded from the BYN Classic edition to the Premium one. Since the upgrade the filename doesn't include the exposure time in seconds anymore. The exposure time is correct, as entered in the imaging plan, and I wonder why the filename omits it. IMHO the settings are ok, I didn't change them with the upgrade. I added a file with the old and the new filenames and  a screenshot. Sorry the screenshot is barely ligible but a clearer image wasn't possible.  What can I do to include the exposure time in the filename?

Nikon 810A , BYN v2.1

Otelescope.odt

Link to comment
Share on other sites

  • Answers 12
  • Created
  • Last Reply

Top Posters For This Question

12 answers to this question

Recommended Posts

  • 0

Hi again. This is the logfile, and it includes another problem as well. The imaging session is aborted, IMHO for no reason, at 23.18.30. It was supposed to run till midnight. The flats session also was aborted the following night  ( easy to deal with as I usually wait close to the scope to finish the flats and can hear when the camera stops. In the case of the lights it was an unexpected and unnoticed waste of time ).

 

logfile-[20210819-21h41m17s311]-[10384]-2021-08-19.txt

Link to comment
Share on other sites

  • 0

Yes, this could be the root cause.  As a workaround, try to configure Windows to use a period as the decimal separator, currently you have it as a comma.  

EDIT: the "Error converting False to int32" is concerning.  

I also see you are using the older Nikon2015 drivers, you should try using the other option with you D810a.

 

2021-08-19 21:41:56,981 [Main] INFO  - Nikon2015/D810a drivers initialized.

------

2021-08-19 21:42:22,983 [CameraTakePictureOnMessageRecieved] DEBUG - TAKE PICTURE ::: Shutter(MANUAL) Cable(CameraUSB) Av(--) Duration(1,0) Iso(8000) Quality(RAW) Mirror(0) SaveTo(PC)
2021-08-19 21:42:26,588 [9] DEBUG - NIKON EVENT --> OnDeviceOnImageReady(1,type[1]) fired
2021-08-19 21:42:26,735 [CameraTakePictureOnMessageRecieved] ERROR - Error converting False to int32.
2021-08-19 21:42:26,741 [CameraTakePictureOnMessageRecieved] ERROR - Die Eingabezeichenfolge hat das falsche Format.
2021-08-19 21:42:26,741 [CameraTakePictureOnMessageRecieved] ERROR -    bei System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   bei System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   bei System.Convert.ToInt32(String value)

Link to comment
Share on other sites

  • 0

Hi,

sorry to have to come back to part of my issue which is the unexpected abort of the imaging session.

The error message

"Error converting False to int32" persists. Changing the decimal separator has fixed the problem with the exposure time though.

Last night the imaging plan was 60 exposures of 120 sec. Start time of the plan was 20:55 local time and the software indicated an expected end point of ~ 23 h. A check at~ 22 h showed that the imaging was still running. When I came back after 23 h I noticed that the session was aborted at 22:09 for no apparent reason. I include the logfile of last night. The original logfile was too large to be sent ( 1 MB) so I copied it into an 'odt' - file    - I hope it's still useful. Please help!

 

Logfile.odt

Link to comment
Share on other sites

  • 0

Please start a new thread in the future as the original issue has been resolved.  It's confusing for me and anyone who reads this in the future trying to solve a similar issue; they won't be able tell them apart.

Ignore the False to int32 error, it's an event fired by the camera that BYN does not need.... but logs it anyway.

Your camera was disconnected and BYN failed gracefully. This is a physical issue, not software.  Please check your battery and USB cable; a slight tug on the USB cable will do this sometimes.

Quote

2021-09-24 23:10:20,898 [4] INFO  - Camera action fired: 'MaestroDisconnect'
2021-09-24 23:10:20,901 [4] INFO  - CameraPropertyChangedArgs fired: AeMode               = ''
2021-09-24 23:10:20,902 [4] INFO  - CameraPropertyChangedArgs fired: Av                   = ''
2021-09-24 23:10:20,904 [4] INFO  - CameraPropertyChangedArgs fired: BatteryLevel         = ''
2021-09-24 23:10:20,906 [4] INFO  - CameraPropertyChangedArgs fired: CCDDataMode          = ''
2021-09-24 23:10:20,908 [4] INFO  - CameraPropertyChangedArgs fired: CameraName           = ''
2021-09-24 23:10:20,909 [4] INFO  - CameraPropertyChangedArgs fired: DelayShutterMilliseconds = ''
2021-09-24 23:10:20,911 [4] INFO  - CameraPropertyChangedArgs fired: ImageQuality         = ''
2021-09-24 23:10:20,913 [4] INFO  - CameraPropertyChangedArgs fired: ImageSize            = ''
2021-09-24 23:10:20,914 [4] INFO  - CameraPropertyChangedArgs fired: Iso                  = ''
2021-09-24 23:10:20,933 [4] INFO  - CameraPropertyChangedArgs fired: LensStatus           = ''
2021-09-24 23:10:20,939 [4] INFO  - CameraPropertyChangedArgs fired: LiveviewExposurePreview = ''
2021-09-24 23:10:20,945 [4] INFO  - CameraPropertyChangedArgs fired: LiveviewImageSize    = ''
2021-09-24 23:10:20,947 [4] INFO  - CameraPropertyChangedArgs fired: LiveviewImageZoomRate = ''
2021-09-24 23:10:20,948 [4] INFO  - CameraPropertyChangedArgs fired: MirrorLock           = ''
2021-09-24 23:10:20,948 [4] INFO  - CameraPropertyChangedArgs fired: ModelNumber          = ''
2021-09-24 23:10:20,950 [4] INFO  - CameraPropertyChangedArgs fired: ModelxD              = ''
2021-09-24 23:10:20,951 [4] INFO  - CameraPropertyChangedArgs fired: NoiseReduction       = ''
2021-09-24 23:10:20,952 [4] INFO  - CameraPropertyChangedArgs fired: SaveTo               = ''
2021-09-24 23:10:20,952 [4] INFO  - CameraPropertyChangedArgs fired: SensorPixelSize      = ''
2021-09-24 23:10:20,952 [4] INFO  - CameraPropertyChangedArgs fired: Tv                   = ''
2021-09-24 23:10:20,958 [4] INFO  - CAMERA IS DISCONNECTED!
2021-09-24 23:10:20,958 [4] INFO  - Camera state changed: 'Disconnected'
2021-09-24 23:10:20,962 [Main] INFO  - Camera SHUTDOWN!

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share


×
×
  • 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