rharter

Hi Mike, correct me if I am wrong, but I have in mind that with ver 5240 "super fit" is automatically applied. At the former versions it was necessary to apply it manually. Ralph

Hello Bernard, thanks for your hint! Yes it already installed a com port but unfortunately the original ASA GPS receiver is not found by GPSComplete although the ublox 6 driver is installed and the receiver is active in "sensors". Mayby I have to dive a bit deeper into the manual... ;-) Ralph

Hi all, have anyone of you an idea how I can allocate a com port to the gps receiver to install it in Autoslew? The gps receiver is automatically installed in Win 10 under "sensors" and not on a com port. Thanks! Ralph

Hi Daniel, in Win 10 Home you can deactivate updates: 1. press "Windows +R" 2. enter "services.msc" 3. look for "Windows update" doubleclick 4. choose "deaktivate" Ralph

Hi, for those of you who are interested in the anwser given by ASA regarding my above question after a direct request: Mr. Weinzinger wrote: Hallo Herr Harter, Hinsichtlich der Präzision wird es kaum Unterschiede geben, , das sind die inkrementellen auch bereits sehr gut. Bei der Software wird es vielleicht in der Zukunft mit den Absolute mehr Optionen geben. Beim Start der neuen Software wird es keine Unterschiede geben. Derzeit arbeiten unser Entwickler bei den Tests mit Montierungen mit inkrementellen Encodern. ASA – Discover Your Universe Sollten Sie weitere Fragen haben, zögern Sie bitte nicht uns zu kontaktieren. Should you have any further questions, please do not hesitate to contact us. Mit freundlichen Grüßen / Best regards Ing. Dietmar Weinzinger B.A. Verkauf und Business Development / Sales and Business Development ASA Astrosysteme GmbH Galgenau 19 A-4212 Neumarkt i. M. Tel.: +43 (0)7942 77811-53 Fax: +43 (0)7942 77811-60 Mob: +43 (0)676 66 44 623 E-mail: d.weinzinger@astrosysteme.at Web: www.astrosysteme.com Web: www.asa-telescopes.com Besuchen Sie uns auf Facebook / Follow us on Facebook Take a look inside ASA here! UID Nummer: ATU 54452907, FN 222906d FB-Gericht: Linz, Gerichtsstand Freistadt Geschäftsführer: Egon Döberl

Dear Dietmar, what does this mean for elderly mounts like mine DDM85 (about 2.5 years old)? How can I verify which encoders were built in? If incremental encoders were built in,is it necessay to upgrade them in terms of precision or new software? kind regards Ralph

Hi, I just wondering, because of the term new... Do anyone knew something about the DDM 85, are there any changes in the encoder type? greetings Ralph

Hi, I saw in an advertisment from ASA in the latest "Sterne und Weltraum" that they promote "Now new, all ASA mounts with absolute encoder". I already thought that the used Renishaw encoders in "elderly" mounts are absolut encoders as well? Are there any differences? kind regards Ralph

Hi all, the frustration about the not existing customer relationship in this forum from ASA is reproducible. Restrictively to this forum, the documentation and the update politics, because in a service case my experiences (2 times) were quite ok. I must admit that I can not understand this behaviour against customers, who are dependent on updates. Just for example: Since I use Sequence beta, suggested by Mr. Keller, most of my problems I had before are gone ( besides of my wobbling telescope ). But since months they are still offering Sequence 09... although several announcements of updates...??? So here my suggestion for really satisfied customers of a high price tool: Please ASA do change your update and information politics! It´s a pity! kind regards Ralph

@Lukas: I am using Sequence Version 0.2.0.5. I will try to install it new because on another computer it seems to work and I can choose your mentioned objects. Just have to find out where the failure message came from... @ Pelle: no problems with the internal hub. I additionally work with an etxternal hub with external power supply.

Hi Lukas, I am just trying to set it up ( dry run) but I am struggeling at the point "exposure settings/exposure details. When I set the checkbox MLPT does the program really run the MLPT process alone before the imaging? By the way when I open the box "SET Exposures" I get an error message "Invalid Argument" but I go further with -next- the window Exposure Details appears and then I want to Exit the exposure Details, with the checkbox MLPT on, nothing happens and there is no entry in the field "Exposure setings" ??? Any ideas? Ralph

Hi Lukas, This would be perfect if it works. Do you have a short workflow for the "Sequence run" howto for 1st. movement, start MLPT then imaging, 2nd movement, MLPT next image... unfortunatly only a dry run due to the bad weather Thanks in advance Ralph

Sequence should handle even more. In a complete automated system I want to imaging several objects at different coordinates in one night. Unfortunately I have to use MLPT before each object...Is there a possibility to realize this? Ralph

Hi all, what are your experiences concerning a complete automated imaging process with the various software applications on the market (e.g. ccd commander, autopilot, SGPro etc.) and Autoslew? As I noticed Sequence beta has an additional task „Sequence run“ which also goes in this direction. Is it possible, in an automated process, to start MLPT before the imaging session, because I get the best tracking results with it? Thanks for your help. Kind regards Ralph

Hello, The error sum of errors in azimuth and altitude results from different sources (e.g. telescope flex, etc.) and increases with a larger number of stars. If I for example do a polar alignment with about 4 stars on the east following the manual, I get an error in polar azimuth: 0.18 and polar altitude : -0.21 (fixed mount) so far so good. If I for example, make a larger pointing file with mouse grid of about 15 stars per east and west I get a resulting polar azimuth error of : +4.12 and a polar altitude error of : -2.34. What values do you gain from your pointing files? Are my error values exceptionally big compared to the polar alignment process with only 4 stars? Thanks for your input! kind regards Ralph

Hi again, during my extended search for time deviations I came across a very interesting point, which effects a lot of phenomena and of course tracking as well. The internal “Windows” clock and its time server is far from being precise. I notice a deviation on my laptop of around 8sec which is resulting in a deviation in RA especially when a planetarium program is synchronized with the internal pc clock! I guess I have found a good solution to fix this problem.: 1. The deviation of your internal pc timer to standard can be shown with: www.time.is 2. I have changed the Internet time server to pool.ntp.org (it is said that this time server is more precise) in date and time settings / internet time, 3. Change the time synchronization interval from 1 week (default) to daily or hourly with this mentioned tool: http://www.thewindowsclub.com/change-internet-time-update-interval-windows I hope this will help to minimize our multiple source of errors. Ralph

Hi, after a long search for the deviation I guess I have found the source. A time problem was the right path to the source. In the planetarium program The Sky X under Input/Location in the custom adjustment is an aditional field for time zone. Here should be the correct difference to UTC time. Unfortunatley I entered here the MEZ and not the right MESZ. With the correct difference now the deviation fade away. Ralph

Hi Robert, when I disable the checkbox of "synch query" in Time Settings the other checkbox "synch PC-Tim" seems to be linked and is disabled as well. Or do you mean something different? the other point: In the manual is said in "Mount/New Home Position":" never synchronize with the planetarium software again"after saving "set new homeposition"!.....? So this is why I do not want to sych again. I do not know what will happen when synchronizing again in contradiction to the instruction manual. Ralph

Hi, still on the search of my deviation, I have found a difference in time between Autoslew/time Settings from GPS ( in UTC) and The Sky time (from computer). see pic. All in all 2hours! Could this be the reason? How are your adjustments to avoid this? Ralph

Hi again, this weekend I had luck for 1 hour without clouds... and I could verify that it had no effect with the wrong epoch in MaximDL. The deviation of about 15 arcmin in west is still there after a new start. Itself after a new synchtonization and new home position with save and followed powercycle the deviation is present. I took an image with the position deviation of 300s and tracking is ok. Any ideas what can cause this ? Kind regards Ralph

Hi, at first I checked the epoch adjustments. In Maxcim DL I have found a J2000 instead JNOW. It could have an influence via the poth hub...? But I could not verify it, clouds, clouds, clouds, mayby next weekend.... to Robert: my telescope is an ODK 14" piggypacking with a APO 80. But shouldn´t be a collimation error of the main telescope calculated and therefore already considered? Ralph

Hallo Robert, the program should only "refresh" after a change... thats the way it works on my laptop. Did you use the correct version (32/64 bit)? Ralph

Hi Robert, I use: USBDeview v2.35 http://www.nirsoft.net/utils/usb_devices_view.html Ralph

Hi George, good point, I will check this comming weekend at the location. I have changed the local computer a view weeks ago... Did I forget a adjustment ? Autoslew: Main frame: Ep. ; real Control/ASCOM ACL: Used Epoch=0.0 Sky X: Navigate / Enter Coordinates, Apparent Equinox: Current Mount Setup: ASCOM Poth Hub, Setup advanced : Coordinate Management: Local Maxim DL: Setup/Telescope Poth Hub, Setup advanced: Coordinate Management: Local Observatory/Telescope: Target Coordinates: JNOW Ralph

Hi, oops, sorry wrong unit.The deviation is about 15 arcmin in RA ! Ralph