Jump to content


Beta Tester
  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
    Ulm, Germany

Contact Methods

  • Website URL

Recent Profile Visitors

251 profile views

robertp's Achievements


Member (1/1)

  1. Hi Jeremy, any progress with your problem? Best regards, Robert
  2. Hi Jeremy, that's correct, these are the relevant logs. Within the log from one of the sessions where you experienced the problem there might be an error message that could help track down your problem. Best regards, Robert
  3. Hello Jeremy, have you tried to do an auto tune of the servos before trying to optimize the balance? You mentioned that with the additional weights the mount vibrates gently. I can imagine that as soon as the balance routine tries to move your RA axis, the maximum error of the axis will be reached and therefore the motor shuts off. So I would recommend that you either do an auto tune or if that fails do a manual tune making sure that you get no vibrations (neither in tracking mode nor when doing fast slews) and then try to balance the mount perfectly. Have you checked the servo-log whether it contains some hint what the problem might be? Hope you get your problem resolved, clear skies, Robert
  4. Hi Stephan, great to hear that you are back in business! Clear skies, Robert
  5. Hi Stephan, did you have a chance to test whether everything is working properly now? Best regards, Robert
  6. Hi Stephan, strange, usually when you install autoslew from scratch on win10, it creates the correct subdirectories under c:\ProgramData\Asa. Maybe you have to run it as adminstrator (but then you have to make sure that you run e.g. Sequence as adminstrator as well). We keep the fingers crossed that this resolves your problems, clear skies, Robert
  7. Hi Stephan, do you have one of the first DDM60 where the user had to find out the encoder settings or one of the second generation, where ASA provided the correct parameters? If you still have the *.ini-files from your last working configuration, you should be able to keep your new configuration with the latest versions of autoslew and sequence and just replace the cl-servos.ini with the one from your working configuration. Within the cl-servos.ini, you find the parameter "encoder resolution per revolution (in mm)" for both axis. Please check whether these are identical in the old and new ini-files. Good luck, Robert
  8. Hi Stephan, reminds me of a problem I once had and that caused me a lot of headaches ... When you sync on a star e.g. near the meridian and slew to different stars e.g. on the east side: does the pointing error gets bigger the further away you are from the synced star? I had that behaviour once until I realised, that my autoslew.ini file somehow got corrupted. There's one parameter that determines the ration between the axis and the encoders and somehow that parameter was wrong for one axis (I only realized that when I compared all settings to an older configuration that I had archived). So if you have a backup of a former configuration where everything worked properly, that might be worth a look. BTW: Which mount do you have? I have a DDM60Pro but with an RC10 (2000mm focal lenght) and a KAF8300 chip, pointing accuracy is good enough to platesolve all pointing files across the sky with Sequence. Clear skies, Robert
  9. Hi Stephan, when you do the platesolve directly within PinPoint: does PinPoint solve the pictures immediately or does it have to do several iterations using the spiral search? If the latter is the case, then Sequence probably fails to solve the pointing pics because of the expected position deviates too much from the real position (the expected position is not within the field of view). There are several options to mitigate that problem: * Do a small manual pointing file (5 stars or so) across the sky and use that to get a rough model of the sky that will ensure, that the pointing accuracy is good enough to get stars in all parts of the sky within the field of view of your camera. * Improve your polar alignment (e.g. using the great routine within SharpCap), make sure that the geo-coordinates within autoslew are correct as well as date and time are perfect. Then slew to a reference star, center it and sync autoslew. This should also ensure a sufficiently high pointing accuracy without a pointing model. * Center a star near the meridian, sync autoslew and start with a pointing file using stars not too far away (e.g. within 30 degrees from the meridian) to get a first pointing model that is good enough to add another one with stars spread all across the sky. Hope this helps. Btw: where are you located? Best regards, Robert
  10. Hi Stephan, that sounds like a very tedious way of creating pointing files. Can you describe the problems you are facing when trying to do the platesolving with Sequence? Best regards, Robert
  11. robertp

    C drive full

    Hi Dave, glad to hear that you managed to delete the huge log-file. I've just read through the sesto-senso documentation and did not find an option to control the amount of logging-data that is stored. I would suggest that you monitor the log-file size to get a feeling how much it grows during one night. If it grows very fast, then it might make sense to contact primaluce to see whether they have a recommendation to avoid the problem. You could also check whether you have turned logging on in the ascom chooser, I guess there is a checkbox where you can turn logging on or off for the ascom devices. Clear skies, Robert
  12. robertp

    C drive full

    Hi Dave, the huge file seems to be the log-file of your motor-focus, that connects to Sequence via Ascom. Have you tried to delete the file right after rebooting your computer before you start Sequence or any other astro-related programs? I would also suggest that you check the ascom driver to see whether you can define a different location for the log-file. Hope this helps, Robert
  13. Hi Daniel, I can't comment on the Astrodon filters. I use Baader filters and I also experience differences: The RGB-filters are basically parfocal but about 0,04mm off compared to the L-filter. The narrowband filters are about 0,33mm off compared to the L-filter, as the narrowband filters are 2mm thick whereas the LRGB filters are 3mm thick. The differences that you measure are substantial if the filters are claimed to be parfocal as expecially the difference between L and the narrowband filters is way bigger than your critical focus zone. To compensate for that, I put the differences into MaximDL - not in sequence. You can use negative values (my narrowband filters need negative values whereas the RGB filters are positive). In Maxim, I had to enter the differences in steps, so I entered e.g. -330 for h-alpha instead of 0,330mm (I use a ASA N8 with the OK3Z focuser). After I measured the differnces and stored them in MaximDL, I verified the correctness by doing an autofocus with the L filter, then put a bahtinov-mask on the telescope and started bahtinov-grabber (a tool that gives you very precise information whether your focus is perfect) and then steped through all other filters to check, whether the focus compensation worked correct. Hope this helps, clear skies, Robert
  14. Hi Bill, was it working before and suddenly stopped working? Did you change anything in your setup? Best regards, Robert
  15. Hello Mark, thanks for your feedback, your experience seems to support my recent tests. I did another test 2 days ago with the scope on the east side and pointing to the south-east. With a well-balanced configuration I got the over-current-error after about 65 minutes. Then I slightly moved one of the counterweights (much less than in the first test) to make the setup slightly west-heavy. After more than 3 hours, the current was still under 3.5 amps. As I have a bended pier and do not have to do a meridian-flip, in many cases I might get away with setting the slight unbalance at the beginning of the session for the whole night. I will try your more sophisticated approach in trying to find the sweet spot but will probably still stick to performing relax slews in sequence (which won't work if I e.g. do sequences of planetary images or the sun). Best regards, Robert
  • Create New...