Date   

Re: Deep image of M86 area

Barry Megdal
 

PixInsight annotation.  Lots of galaxies.

 

https://www.dropbox.com/s/w5q37z16yxwa1ru/M86_image_Annotated.jpg?dl=0

 

-          Barry

 

 

Dr. Barry Megdal

 

Faculty

Dept. of Electrical Engineering

California Institute of Technology

Pasadena, CA

bmegdal@...

 

 


Portable powersupplys....

beckemd <beckemd@...>
 

Ok...need to get moving on this. From what I've read,  a dedicated PS for the Mach1 gto is required. I also need power for my laptop, powered USB hub (for orion SSAG/2 nikon to computer connections/and mount to laptop). That's it. I Noticed Kendricks imaging power panel which seems to have lots of connections.  Just add battery and u're good to go. Has anyone tried one of these?
Dbb in Chicago



Sent from my Verizon Wireless 4G LTE smartphone


Re: Deep image of M86 area

Roland Christen
 

Thanks for the annotation. Can you tell what the faintest galaxies are in this image?
 
Rolando
 
 

-----Original Message-----
From: Benoit Schillings benoit.schillings@... [ap-gto]
To: ap-gto
Sent: Fri, May 6, 2016 10:06 pm
Subject: Re: [ap-gto] Deep image of M86 area




On Thu, May 5, 2016 at 3:32 PM, chris1011@... [ap-gto] <ap-gto@...> wrote:
 
Hi All
 
I had a chance to add another 18 exposures last night. It was quite transparent, so it looks like I was able to capture faint galaxies beyond magnitude 20. I also did a bit of processing of the cores of the brighter galaxies to bring out more detail. Here is a full size JPEG (not the best resolution):
 
 
Rolando




Re: AP 1200 very old model QMD

Konstantin von Poschinger
 

No!


Konstantin v. Poschinger

Hammerichstr. 5
22605 Hamburg
040/8805747
0171 1983476

Am 07.05.2016 um 03:29 schrieb don123donxyz@... [ap-gto] <ap-gto@...>:


Can this model be updated to the newer goto models our are you simply stuck with stepper motors

and Navis to locate your various objects. I looked on AP's website under history and it looks like many parts can be upgraded..

I am in the process of upgrading my OTA from a Celestron C11 to a C14 and I'm sure my current Losmandy G11 Gemini II will not be capable of handling the larger C14.

Don Curry




Re: CP4 Documentation

Rob Hawley
 

Is the intent that the AE Utility use the second serial port or should it use a virtual port like the V2 driver?
Rob Hawley
www.robhawley.net


Re: Deep image of M86 area

Benoit Schillings
 

On Thu, May 5, 2016 at 3:32 PM, chris1011@... [ap-gto] <ap-gto@...> wrote:
 

Hi All
 
I had a chance to add another 18 exposures last night. It was quite transparent, so it looks like I was able to capture faint galaxies beyond magnitude 20. I also did a bit of processing of the cores of the brighter galaxies to bring out more detail. Here is a full size JPEG (not the best resolution):
 
 
Rolando



Re: Powermate or extender

r1300rs
 

That's good to know. I will work on the extension tubes and adapters and give it a try. Others are having great success with this. Conflicting information but I've seen the pictures and they look great with short exposures for DSOs...


AP 1200 very old model QMD

Don Curry
 

Can this model be updated to the newer goto models our are you simply stuck with stepper motors

and Navis to locate your various objects. I looked on AP's website under history and it looks like many parts can be upgraded..

I am in the process of upgrading my OTA from a Celestron C11 to a C14 and I'm sure my current Losmandy G11 Gemini II will not be capable of handling the larger C14.

Don Curry


Re: Question about AP900 CP2

C. G. Anderson
 

I just ordered a CP4 for my 1998 vintage AP900.  Now to get rid of my CP3.....  CG


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Joe Zeglinski
 

Lance, et al.
 
    The TeamViewer website also has old versions  10, 9 and 8 available for download. Just be sure to UNCHECK the option to download Updates, or your login will insist on giving you the current version, and not permit rejecting it.
So, that can get you going in circles, unless you disable the option in the EXTRAS tab , first.
 
Joe


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

kentdegroff@...
 

Hi Lance,

I happened to have the older version in my downloads folder, so uninstalled the newer version and reinstalled the older version.

Kent


Re: CP4 Documentation

George
 

Rob,

 

For now the AEUtility remains unchanged as a standalone and is used with the CP4 as it was with the CP3.   It will be integrated into APCC in a future iteration.     

 

Regards,

 

George

 

George Whitney

Astro-Physics, Inc.

Phone:  815-282-1513

Email:  george@...

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Friday, May 06, 2016 9:51 AM
To: ap-gto@...
Subject: [ap-gto] Re: CP4 Documentation

 

 

How are the functions of the existing AEUtility (setting home, turning the encoders off/on, setting mount limits) performed?  In the GOTOCP3 this was done by a special utility that used a separate serial line to talk to the controller for the Absolute Encoders.

 

My understanding is that this functionality is now incorporated in either the ASCOM V2 driver or APCC, but I did not see this documented.  This may be as simple as a typo since the APCC section contains a line

 

  • ●  home and limits for all non-Absolute encoder Ap Gto mounts 

 

 

Rob Hawley
www.robhawley.net

 


Re: AP 1100GTO weight capacity

Roland Christen
 

You can load the mount with 50kg scope weight. Then you can add as many counterweight as necessary to balance that weight.
 
Rolando
 
 

-----Original Message-----
From: carlos49gib@... [ap-gto]
To: ap-gto
Sent: Fri, May 6, 2016 6:35 am
Subject: [ap-gto] AP 1100GTO weight capacity



I am changing scope from a Tak106ed to a Tak cca250, the latter weight around 23kg, the image train another 4kg. Now the mount payload is around 50kgs so seem fine, but I am confuse with AP website reading, when it says 'not including counterweights' I suppose that the 50kgs is net weight, in other words that I can put a maximum (not that I going to) up to 50kg on top of the mount and the counterweights are included in this 50kgs.

Thanks



Re: CP4 Documentation

Rob Hawley
 

How are the functions of the existing AEUtility (setting home, turning the encoders off/on, setting mount limits) performed?  In the GOTOCP3 this was done by a special utility that used a separate serial line to talk to the controller for the Absolute Encoders.

My understanding is that this functionality is now incorporated in either the ASCOM V2 driver or APCC, but I did not see this documented.  This may be as simple as a typo since the APCC section contains a line

  • ●  home and limits for all non-Absolute encoder Ap Gto mounts 



Rob Hawley
www.robhawley.net




Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

kentdegroff@...
 

Joe, Stuart, et.al,

FYI: I have been running Win7 computers in both places for the last year or two. No timeouts with TV installed from download file version 10.0.47484.0. Before that, it was XP which I still have on a laptop, version 10.36897; works too.

Kent


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Joe Zeglinski
 

Steven,
 
    Fully agree – TeamViewer is a great deal, even with its one problem. Just wish the Win-7/10 wireless host disconnects weren’t so random. Otherwise, a 3-hour reconnect wouldn’t be a hassle.
 
    However, every astronomer uses his system differently. I start the night and run the scope, change targets, view images, etc – for hours, just staring at the screen. Sure beats sitting in a cold damp observatory, feeding the mosquitoes, or freezing to death in winter at the telescope. The convenience of doing everything from the kitchen table using TeamViewer, with the scope in the distant backyard, really makes doing this hobby enjoyable.
 
    Then again, if as you do,  I just programmed a script to run a predetermined set of targets and image sequences, I too would go to bed with the TV host connection logged out. However, I don’t trust “computer automation” with my magnificent AP mount, that much -  so I likely would not sleep very peacefully.
 
Joe


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Steve Reilly
 

I’ve followed most of this thread but really wonder why a constant connection is such a big deal. I’m guessing that you don’t need a constant connection but rather maybe checking from time to time on the progress of the session and making a connection with TV is fast and simple. For me I have my computers, near and far, listed under my sing-in account and it’s a matter of mouse clicking on the computer to make the connection. A few seconds later I’m there. If it times out in three hours so be it, just click again. For the cost, free, it’s a great deal. Most times I end the connection and come back later. All systems are set as easy access that at most require the password.

 

Just saying…..

 

 

Steve

 

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Friday, May 6, 2016 10:04 AM
To: ap-gto@...
Subject: Re: [ap-gto] Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

 

 

Stuart,

 

    Just as I suspected – XP on the telescope side, as host, will run as long as there is a decent signal, no Timeout.

 

    As a further test, try what I did. Reverse the TeamViewer roles – go to the observatory “Win-XP”  computer, and log into the Win-7 or 10  PC in the house which then becomes the TV host. I suspect your XP (or any other Win O/S as client), will timeout at the 3 hour mark, or sooner if the  IPv6 comms.  driver doesn’t like signal quality. The house Win-7/10 system will continue running, oblivious of the disconnect, other than a note in Connections_incoming.txt (on the host side’s TeamViewer) log file.

 

    Bottom line, it seems that only TeamViewer XP-based “hosts” will not time out.

Joe


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Joe Zeglinski
 

Stuart,
 
    Just as I suspected – XP on the telescope side, as host, will run as long as there is a decent signal, no Timeout.
 
    As a further test, try what I did. Reverse the TeamViewer roles – go to the observatory “Win-XP”  computer, and log into the Win-7 or 10  PC in the house which then becomes the TV host. I suspect your XP (or any other Win O/S as client), will timeout at the 3 hour mark, or sooner if the  IPv6 comms.  driver doesn’t like signal quality. The house Win-7/10 system will continue running, oblivious of the disconnect, other than a note in Connections_incoming.txt (on the host side’s TeamViewer) log file.
 
    Bottom line, it seems that only TeamViewer XP-based “hosts” will not time out.
Joe


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Joe Zeglinski
 

Thanks for that update, Kent.
 
    Reading through the forums you provided link to, it is surprising to see the range of (free) session timeouts experience 1, 2 or 3 hours. I suspect some of these are likely loss of WiFi or direct connect router/modem signal, since TeamViewer tech support FINALLY admitted to the 3 hour limit, if all else works. I wonder if the company will finally post that on their web, or in the next version update.
 
    By any chance is your observatory (host) PC running Win-XP?
 
    I found I can get pretty much undisrupted connection to my XP laptop (using any Windows client OS) – with the Session Timeout option, set to OFF -  compared to the random disconnects when talking to my two Win-10 and the Win-7 Pro systems as hosts, all PC’s in the very same room. That imbedded (non-disclosed) 3-hour limit kill switch doesn’t seem to trigger in XP hosted PC’s.  Win-XP wasn’t encumbered by all the later Microsoft security routines, so TV runs far simpler as a host at the telescope.
 
    Also, Win-XP only used IPv4 to handle communications. Win-7 (and later), automatically re-links all existing IPv4 calls (during boot),  to the new IPv6 module, which I suspect may account for some of the “premature” disconnects on weak WiFi and direct connect router signals. I have run a couple of XP hosted sessions, for well over 10 hours each, and  3 hours at most, on Win-7 and later host side TeamViewer systems. I wonder if IPv6 sensitivity to signal dips has been responsible for cases when it started and aborted a session lasting only a few seconds, in a string of a dozen sequential restarts, before it finally stayed connected for a while.
 
    As for your setting the option for option -  “Incoming LAN” ... Deactivate” – that is indeed odd, though from what I have seen, now in weeks of daylong  tests, it is not unexpected. TeamViewer (any version)  isn’t consistent and sometimes looks like it ignores its own User settings. Some settings, based on comments in the log,  can’t actually be activated, depending if it is running on Win-XP, versus the later Windows  systems with their security lockouts.
 
    Click on  the TV Log files option in EXTRAS, and read through the list of sessions in TeamViewer-11_log.txt (requires to be run only with Notepad). You will see lots of system calls, possibly to mostly its own command modules, which fail or produce errors. The date/time tag in that file is your “Local Time”.
 
    Also, have a look at the file “Connections_incoming.txt” – also on the host TeamViewer – to see the start and stop times recorded at the end of each session. Note that the date stamp is in Universal Time (not local time, as in the former log file), which makes comparing events to sessions confusing.
 
    Finally, I repeat, do NOT wait for TV to actually reconnect, after aborting a session – probably more so in Win-7 and later TV host-side, systems. I don’t think the security features in later Windows, permit it to do that, so it wastes time and your patience. Just click the red-X and close the session Window, even as TV is saying it is “Trying to reconnect” – that’s Bogus ... and it will take 8 minutes before it finally hangs. Closing the session window right away and clicking on the TV start icon, only takes a blink of the eye to resume without loss of the former host screen.
 
    From the troubles I have seen, it almost seems like TeamViewer is simply written as a huge JAVA Script, rather than a well programmed compiler or even assembler based program.
 
Joe


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Stuart Heggie <stuart.j.heggie@...>
 

Joe, Kent, ... I just wanted to report that as of now I have had a LAN connection of TV 11 running from a 32-bit W7 machine to a 32-bit XP Home machine for about 3 days without interruption. Weird.

Stuart

On Thu, May 5, 2016 at 2:46 AM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
 

Kent,
 
    Before posting this thread about the TC-11 timeout, I went back to TV –10 and TV-9, and all three (free) versions have the same “random” timeout. By any chance was your TV-10 a “paid” Commercial version, which of course, doesn’t have the timer set for 3 hours? Seems Stuart and I are seeing the same problem – as are very many others on the web, if you Google “TeamViewer disconnects”
 
    Yesterday, in pursuing this issue with TeamViewer’s Tech Support, they suggested trying to UNCHECK  the option in “Advanced Network Settings ... Use UDP (Recommended)” in the Extras-Options-Advanced. Well, the first run timed out in the first few minutes. But, the second session, continued to run for hours. After the 3-hour (free) time limit had passed, I decided to move the optional Timeout slider from 8 hours (max), back down to “OFF”  (No timeout) ... and the strange thing is that it was still running just fine after 10.5 hours – when I finally decided to stop the session, as it was then obvious that it was going to run forever. Somehow the “non-UDP network” option, seemed to confuse TV-11 to ignore the built-in kill switch , for Home users. That, at first, seemed like an enticing bonus for not using UDP, so I will continue with it, as it gives fewer random session disconnects. Hopefully TeamViewer will eventually discover the cause, after so many versions of their software.
 
    Then I switched to another host laptop, expecting this was perhaps a quirk using  Win-XP on the host laptop,  but the same thing happened on a Win-10 host laptop – Session aborted after a few minutes, and the rerun session bombed out after 1 hour 52 minutes, far short of the built-in 3-hour limit.
 
    My tests are currently indoors, with the option set to “Accept LAN” connections – so there is no chance of ISP modem blips or internet traffic jams. However, I suspect TV still uses its internet link – perhaps for monitoring, even as it is running a session with the in-house LAN, ... and the two laptops just 10 inches apart on the table !
 
    TeamViewer session – using any Home User version -  is unpredictable.
When it runs, its great, but when it randomly disconnects, its a royal pain. Still, it is useful, since you can login again. I find it takes 7 to 8 minutes before it accepts a re-login ... while it says it is “Trying to reconnect”. But, if you just CLOSE the session window, you can login again ...  in just a few seconds. I find I might as well do that, since it has “never” managed to reconnect on its own, no matter how hard it is trying. I thought it was a Windows Security issue – not allowing it to login – but XP didn’t have security, and as the host (scope system) PC, it too still failed the same way.
 
Joe