Kazuo Horiuchi

Hello Robert-san, Thank you so much for your feedback ! Yes, you are absolutely correct. Even I start the Sequesce Run by clicking the "Start@Time" button below, the "Relax slews" is never initiated before actual exposures start. Onec actual exposures start as below, after "Name of Target" changed to highlited in GREEN, every "5 minites" I can see the "Relax slews" obviousely and it can be seen in the both "Autoslew log-file(=CIServo_log-file)" and "Sequence log-file". Now I have a confidence to resolve my serious problem to activate the "relax slews" every 30 minutes or so. Again, thank you so much for sharing your experiences and lots of advices ! Best Regards, Kazuo Horiuchi

Hello Robert-san, I am very sorry to ask you again but I have following questions on the "Relax Slews". Would you please kindly give me your feedback ? Q.1 Even I set the "Time Interval" = 5 [minunets] for test purpose, I can't see any actual slewing for more than 15 minutes. Can I see actual slewing visually every 5 minutes ? Are there any other settings/parameters to be enabled or set in order to initiate "Relax Slews" every 5[minutes] ? Q.2 Once "Relax Slews" are initiated can I see any messages in the Log-file ? Q.3 When is the starting point time to count down the "Timer Interval" = 5[minutes], ? For example, it is the time of the completion of booting up the "Sequence" software etc.. Thanks in adavnve and Best Regards, Kazuo Horiuchi

Hello Robert-san, Again, thank you so much for your useful information sharing ! Understood. Actually I am using MaxImdl for shooting subframes but I will try to use the Sequence with "relax-slew" activated and check whether my problem can be impreved ! Thanks in advance and Best Regards, Kazuo Horiuchi

Hello Robert-san, Thank you so much for your kind hint ! I performed "Tracking" and confirmed the "trying to correct OverCurrent Error" in Axis 1 as below when the Current reaches "5.0A". This Error was observed 3 times within approx. 65 min. today in the attached log-file. 16:54:10.589: Axis 1 slewing to -170.96 16:54:10.599: Axis 2 slewing to -97.42 16:54:14.037: Axis 2 Pos:-097.42° Curr:+00.5A MagAng:+264° PosErr:-05.65arcsec 16:54:14.224: Axis 1 Pos:-167.46° Curr:+00.8A MagAng:+115° PosErr:+00.40arcsec 16:54:20.344: Axis 2 Pos:-097.42° Curr:+00.7A MagAng:+264° PosErr:-00.02arcsec 16:54:20.458: Axis 1 Pos:-170.94° Curr:+01.5A MagAng:+083° PosErr:+00.02arcsec 17:20:50.270: Axis 1 Pos:-164.30° Curr:+04.3A MagAng:+156° PosErr:+00.66arcsec 17:20:50.273: Axis 2 Pos:-097.42° Curr:+01.0A MagAng:+264° PosErr:+00.00arcsec 17:20:56.658: Axis 1 Pos:-164.28° Curr:+04.9A MagAng:+156° PosErr:+09.45arcsec 17:20:56.673: Axis 2 Pos:-097.42° Curr:+01.0A MagAng:+264° PosErr:+00.00arcsec 17:21:03.036: Axis 1 Pos:-164.25° Curr:+04.9A MagAng:+156° PosErr:+64.29arcsec 17:21:03.052: Axis 2 Pos:-097.42° Curr:+01.0A MagAng:+264° PosErr:+00.00arcsec 17:21:05.173: Axis 1 trying to correct OverCurrent Error 17:21:05.192: Axis 1 slewing to -166.25 17:21:08.290: Axis 1 slewing to -162.25 17:21:11.251: Axis 1 slewing to -164.25 17:21:13.669: Axis 2 Pos:-097.42° Curr:+00.7A MagAng:+264° PosErr:-00.30arcsec 17:21:13.767: Axis 1 Error: Position Error 17:21:13.771: Axis 1 trying to autocorrect tracking error 17:21:15.014: Axis 1 Pos:-164.25° Curr:+00.0A MagAng:+156° PosErr:+00.02arcsec 17:21:19.244: Axis 2 Pos:-097.42° Curr:+01.0A MagAng:+264° PosErr:+00.04arcsec 17:21:21.428: Axis 1 Pos:-164.17° Curr:+02.3A MagAng:+157° PosErr:+00.00arcsec 17:21:25.540: Axis 2 Pos:-097.42° Curr:+00.9A MagAng:+264° PosErr:+00.00arcsec 17:21:27.702: Axis 1 Pos:-164.15° Curr:+02.4A MagAng:+158° PosErr:+00.00arcsec 17:39:22.485: Axis 1 Pos:-159.66° Curr:+03.8A MagAng:+207° PosErr:-00.40arcsec 17:39:26.589: Axis 2 Pos:-097.42° Curr:+01.0A MagAng:+264° PosErr:+00.00arcsec 17:39:28.849: Axis 1 Pos:-159.63° Curr:+04.9A MagAng:+207° PosErr:+02.51arcsec 17:39:32.970: Axis 2 Pos:-097.42° Curr:+01.0A MagAng:+264° PosErr:+00.00arcsec 17:39:35.165: Axis 1 Pos:-159.61° Curr:+05.0A MagAng:+208° PosErr:+31.57arcsec 17:39:38.377: Axis 1 trying to correct OverCurrent Error 17:39:38.390: Axis 1 slewing to -161.60 17:39:40.932: Axis 1 slewing to -157.60 17:39:44.008: Axis 1 slewing to -159.60 17:39:46.649: Axis 2 Pos:-097.42° Curr:+00.8A MagAng:+264° PosErr:-00.36arcsec 17:39:46.744: Axis 1 Pos:-159.60° Curr:+01.8A MagAng:+208° PosErr:+02.51arcsec 17:39:53.093: Axis 2 Pos:-097.42° Curr:+01.0A MagAng:+264° PosErr:+00.00arcsec 17:39:53.196: Axis 1 Pos:-159.53° Curr:+02.1A MagAng:+208° PosErr:+00.02arcsec 17:39:59.399: Axis 2 Pos:-097.42° Curr:+01.0A MagAng:+264° PosErr:+00.00arcsec According to your advice, I would like to contact ASA Service with this topic in this ASA COMMUNITY. If you do not mind, woulr you please kindly share the email address of the ASA Service which you had conntacted in your problem case ? Thanks in avance and Best Regards, Kazuo Horiuchi 2022_2_10_16h50m.txt

Hello Robert-san, Thank you so much for your detail explanation ! I will check my log-file according to your advice. But as it is cloudy today here in Japan I will perform above as soon as possible. Best Regards, Kazuo Horiuchi

Dear Robert-san, Thank you so much for sharing your experience ! I have checked my CIServo-log under the following folder. C:\ProgramData\ASA\Autoslew\ClServoLogs Unfortunately I did not enable the "Record Log File" setting as below. Therfore I have enabled it and "Log Magnetic Angle" as well and checked the CIServo-log can be stored as below. I will check this log-file during my next shooting based on your info., hopefully tonight. Just in case, would you please kindly give me your opinion on the following ? - Is it OK to set "Logging Interval (sec) : 5.5 (maybe this is default value) to check the "over-current-error" in the Log-file? - Can I see the "over-current-error" message in this log-file once the RA-axis current reaches the limit ? (ex.) In the log-file I can see the following descriptions. Latency Time for USB FTDI communication (default is 1)=1 USB Buffer Size for USB FTDI communication (default is 10)=10 Current Limit (A)=5 Current Peak Limit (A)=12 Current Peak Time (s)=2 [Controller Error Settings] Error Threshold for Phase Current (A)=13 If Voltage > 48V then Ignore=True If Voltage > 48V then Report=False If Voltage > 48V then shut down Controller=False If Voltage < 12V then Ignore=True If Voltage < 12V then Report=False If Voltage < 12V then shut down Controller=False Thanks in adavnce and Best Regards, Kazuo Horiuchi 2022_2_9_13h10m.txt

Hello Luis-san, Again, thank you so much for your advice. I will do following parallelly based on your advice. 1. Now I am using one "100V AC" for all devices in my DOME. In order to split the AC power of the DDM80X-SL out from other devices in my DOME, I will use following external Power Batttery for my DDM85X-SL only. 2. I will send email on this phenomena to ASA Service as well to get any advice. Just in case, do you know which email address of ASA Service I should use to send this topics ? Because in ASA Web site, it seems not so clear for me which email address of the ASA Service has to be used to send this topics. Thanks in avance and Best Regards, Kazuo Horiuchi

Hello Luis-san, Thank you so much for your feedback ! Actually I am using following "Switching Power Supply" but I will do that accordingly. Best Regards, Kazuo Horiuchi

Hi all, I have a serious problem of the Tracking Error in my DDM85X-SL. The DDM85 sometimes moves "Back and Forth", not periodically, while tracking. I have attached the URL of the video of the "Back and Forth" movement error below. https://drive.google.com/file/d/16Z7n-F3pNYCwQyXK25R1WuFpl38AZ4D7/view?usp=sharing This "Back and Force" movement always happens more than 10 times while approx. 4 hours tracking. Therfore I need your kind advice and helps for the following: 1. Does anyone have experiences like this "Back and Forth" tracking error ? 2. Shoul this DDM85X-SL be sent to ASA Service for repair or detail investigation ? 3. Any advice ? <Details> - This happens "RA" axis only, therefore subframes always have "tails" in RA direction. (see attached "Stars with tail.png") - This happens "not periodically" and you can see how this happens while tracking. (see attached "Telescope_WEST_Tracking_Error_Rate_21%.PNG" and "Telescope_EAST_tracking_Error_Rate_28%.PNG") In the attached both .PNG, the subframes highlighted in BLUE have this "Back and Forth" movement. - This happens in all conditions below. - "tracking" only (no "MLPT" nor "pointing model") - "MLPT" + tracking - "MLPT" + "Pointing model" + tracking - This happens wherever Telescope is pointing. (Zenith, close to Horize, both Telescope-East and Telescope-West) - As a result, during 4-hours tracking more than 10 subframes typically have this error. Therefore I always lose more than 20% subframes while 4-hours shooting and sometimes more than 30%. I always shooting each subframe for 5 min. exposure. <My configuration> -Windows 10 (x64bit) -Autoslew: 5.2.4.1 -Sequence: 0.2.1.1 -ASCOM: 6.5 SP1 -On the Balance in RA and DEC, I have attached "RA-Balance.png" and "DEC-Balance.png". -I have attached my "MLPT" result as an example. (200 min. & 10 points) <History> I purchased this DDM85X-SL in Feb.2012 and I am very proud having this one due to very precise tracking. Since 2 years ago, this error is becoming obvious but error subframe rate was less than 5% (in case of 5 min. exposures). Nowdays getting worse and currently more than 20%, sometimes approx. 30%, error subframes. Thanks in advance and Best Regards, Kazuo Horiuchi

Dear Mr. Antonio and Mr. P.Keller, Thank you so much for both your comments. Yes, I believe ASA DDM mount , AutoSlew and Sequence combination is very excellent for astronomy photo. I am really looking forward to have next official AutoSlew and Sequence software release !! Best Regards, Kazuo Horiuchi

Dear Sir, Does anyone know the way how to execute MLPT in Sequence by Script like VBScript ? Background is I would like to use ACP and MLPT together, but I am not sure if there are any ways how to make MLPT automated, like by Script. I am very sorry this is a right question to get help/advice in this Form. Best Regards, Kazuo Horiuchi from Japan

Dear Mr. Robert and Mr. P.Keller, Thank you so much for both your comments !! I understood current situation and looking forward to try new Version once it is available. Regarding volunteer as a beta tester, I am happy to be a beta tester even I'm not sure how much I can contribute. I will check new update in this forum frequently. Now I'm very happy because I am one of DDM85 users because I can get very valuable supports in this forum. Best Regards from Japan. Kazuo Horiuchi

Dear Sir, Are there any one who can conduct the MLPT in Sequence correctly over meridian without flip, with keeping "Telescope is East" ? I am living in Japan, which is north hemisphere as you know and using DDM85 Standard(DDM85X-SL). Please give me any advice so that I can conduct the "MLPT" correctly over meridian without flip. I am very satisfied with "MLPT" and Pointing file(16-Stars in East and 16-Stars in west), which I can get very "round stars" more than 40 minutes with 1880mm focal length in both East and West. But in case I conduct "MLPT" from East to West, over meridian but no flip due to my settings are below. In this "over meridian but no flip", I can not get "dot" results in MLPT after over meridian. Please see the screen shot: (or attached MLPT#1.PNG) http://i829.photobucket.com/albums/zz218/horiuchikazuo/MLPT1_zpsfa39bf73.png In this screenshot, I can not see last "2 dots" after over meridian. In addition, in case I execute "Load and Draw LPT File" function in More Tools section, the result is as below: (or attached MLPT_load&Draw.PNG) http://i829.photobucket.com/albums/zz218/horiuchikazuo/MLPT_loadampDraw_zpsff458ea0.png In this screenshot, Total Exposure time(min) is quite strange, which is -1387.8 and result dots are also strange !! I checked inside the 5Sarts.lpt with Windows "Notepad", there seems to be strange values inside which are highlighted in "Red" in the screenshot below: (or attached MLPT_test.PNG) http://i829.photobucket.com/albums/zz218/horiuchikazuo/MLPT_text_zps52d569d4.png I am using the following versions. -Autoslew: Version 5.1.1.2 -Sequence: Version 0.0.0.9 Settings in Autoslew are below: - Mount --> Type, Limits --> How far can you go through the Meridian with your German Mount ? : 30.0 - Mount --> Flip Options : stay on side I have looked inside old "Yahoo Group" and found similar issue which were raised by Mr. robert.pudlo dated Dec 2, 2011 6:44 pm. But I can not see any final solution nor answer for this issue. Thanks in advance and Best Regards, Kazuo Horiuchi