Date   

APPM model how many points portable?

Roger Howard
 

Hello, looking for opinions and guidance for how many points to model.  There are a lot of topics on this but none of them seem to answer my questions.  I set up each time in my backyard in the same place on an ATS portable pier.  I'm using APCC Pro, 1100GTO, Edge 9.25 with OAG and SGP.  My pier is within I would estimate the same few inch square each time its set up. I did a 93 point model last time because I knew I would have several nights to image and it worked great.  The problem is that with a couple failed points that went to all sky solve it took well over an hour and a half using SGP and platesolve 2 as my plate solver.

My question is:  Just use the 93 point model since its almost in the same spot?  If not, how many points to model when I will be guiding?  My problem is that summertime dark isn't until about 8pm, and I get up for work at an early 0345 every day, so if I want to just do a night or two when the sky is clear for just a night or two, what should I do?  Is there a minimum number of points?  Can't dedicate a couple hours to get a pointing model because I have to hit the sack early (ish).  I know an observatory would be the answer, but in my yard that isn't happening.  Thanks for your experience.

Roger


Re: Initiation Parameters - APCC vs Driver

Ray Gralak
 

First, what Wade wrote here is true:

The ASCOM V2 driver connects to the mount through APCC.
Assuming that you are not initializing the mount with
the keypad (or some other device, like a smart phone),
APCC will initialize time/date/location. By the time the
ASCOM driver loads, the mount is already initialized by APCC.
So if the ASCOM driver and APCC have different
initialization settings, the APCC settings will be the
ones that are applied.
APCC has a “NOW” button that can be used to auto-configure the driver, but it isn’t clear to me whether this
configures only information like the port, time-out parameters and so forth, or does it communication that
The "Now" button only configures the AP V2 driver so that it can use APCC's virtual port. Leaving the "Auto-config" checkbox enabled does the same thing automatically every time APCC runs, and without the AP V2 driver acknowledgement popup's. The "Now" button allows you to reconfigure the ASCOM driver after changing the virtual ports in APCC while APCC is running.

Note that the location, mount type, park and initialization settings in the ASCOM V2 driver are independent of the
settings in APCC. You will create and adjust these settings within APCC.
Refer to the ASCOM manual for additional settings that are useful when using APCC.

This seems to imply that I don’t need to make any of these settings in the driver itself. Is this true even if I tick the
auto-config and auto-connect boxes in the Driver section of APCC?
Yes, this is still true. There are ASCOM settings that are only relevant for ASCOM client applications. APCC is ASCOM-agnostic at this time.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Craig Smith via groups.io
Sent: Sunday, April 11, 2021 6:42 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] Initiation Parameters - APCC vs Driver

I have a question/clarification of the relationship between APCC and the ASCOM V2 driver for Ray or anybody who
knows the answer for sure…

My question has to do specifically with the initialization phase and whether anything needs to be initialized in the
Driver separately if auto-connecting and starting the driver from APCC.

APCC has a “NOW” button that can be used to auto-configure the driver, but it isn’t clear to me whether this
configures only information like the port, time-out parameters and so forth, or does it communication that information
plus information about local time-zone, latitude and longitude information, park information and so forth? Or, I guess
the third option is whether the driver needs to know site information as long as APCC knows this information?

I found this statement in the APCC manual:

Note that the location, mount type, park and initialization settings in the ASCOM V2 driver are independent of the
settings in APCC. You will create and adjust these settings within APCC. Refer to the ASCOM manual for additional
settings that are useful when using APCC.


This seems to imply that I don’t need to make any of these settings in the driver itself. Is this true even if I tick the
auto-config and auto-connect boxes in the Driver section of APCC?

To further clarify (only if necessary), my workflow in the past for a portable setup has been to setup the site
information in the Driver and in APCC, then I ticked the auto-connect box anyhow and this seemed to work. (But I
never understood whether I really needed to configure the site information in the driver ahead of time.) After a year-
long hiatus, my workflow this year has been to start APCC with the auto-configure and auto-connect buttons
unticked, and to use the “NOW” button and “CONNECT” buttons to initiate the driver. In this work flow, I have not
been setting the driver site (and other) information independently, and that also works.

I realize that I could experimentally determine what I need to configure independently in the driver, but I wish I
understood enough about the relationship between APCC and the Driver to be able to have that answer in my
mental picture of the system.

Thanks and regards,
Craig


Re: Cable talk (with Linda Richman)

Astronut
 

Hi Dale,
A big thanks for the ZWO cable insights !

I too run mine with the USB throughput at the minimum 40% level and been lucky so far (knock on wood), but do appreciate the understanding that electrically they are nothing to write home about, to say the least...
I do run 3 ZWO cameras concurrently that way, but I only run mine outdoors, away from most other devices. Eventualy, when one fails, I will cut it apart to better 'appreciate' the quality of construction as well ;)
I had previously found some high end flat flex cables out there, that did have either coaxial or twisted pairs, as well as an overall braided shield, but they looked fairly thick (compared to the ZWO cables) and were hundreds of dollars each. IIRC they were marketed for robotics and industrial automation hi flex applications as well.
Thanks for the L-com info everyone !
Tim







Re: Initiation Parameters - APCC vs Driver

W Hilmo
 

The ASCOM V2 driver connects to the mount through APCC.  Assuming that you are not initializing the mount with the keypad (or some other device, like a smart phone), APCC will initialize time/date/location.  By the time the ASCOM driver loads, the mount is already initialized by APCC.  So if the ASCOM driver and APCC have different initialization settings, the APCC settings will be the ones that are applied.

 

I image at many different field locations each year, and I have all of the sites set up in APCC only.

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of DFisch
Sent: Sunday, April 11, 2021 8:59 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Initiation Parameters - APCC vs Driver

 

Craig, you said it thoroughly, inquiring minds want to know 

 

On Sun, Apr 11, 2021, 9:42 AM Craig Smith via groups.io <cgsathome=yahoo.com@groups.io> wrote:

I have a question/clarification of the relationship between APCC and the ASCOM V2 driver for Ray or anybody who knows the answer for sure…

 

My question has to do specifically with the initialization phase and whether anything needs to be initialized in the Driver separately if auto-connecting and starting the driver from APCC.

 

APCC has a “NOW” button that can be used to auto-configure the driver, but it isn’t clear to me whether this configures only information like the port, time-out parameters and so forth, or does it communication that information plus information about local time-zone, latitude and longitude information, park information and so forth? Or, I guess the third option is whether the driver needs to know site information as long as APCC knows this information?

 

I found this statement in the APCC manual:

 

Note that the location, mount type, park and initialization settings in the ASCOM V2 driver are independent of the settings in APCC. You will create and adjust these settings within APCC. Refer to the ASCOM manual for additional settings that are useful when using APCC.

 

This seems to imply that I don’t need to make any of these settings in the driver itself.  Is this true even if I tick the auto-config and auto-connect boxes in the Driver section of APCC?

 

To further clarify (only if necessary), my workflow in the past for a portable setup has been to setup the site information in the Driver and in APCC, then I ticked the auto-connect box anyhow and this seemed to work.  (But I never understood whether I really needed to configure the site information in the driver ahead of time.)  After a year-long hiatus, my workflow this year has been to start APCC with the auto-configure and auto-connect buttons unticked, and to use the “NOW” button and “CONNECT” buttons to initiate the driver.  In this work flow, I have not been setting the driver site (and other) information independently, and that also works.

 

I realize that I could experimentally determine what I need to configure independently in the driver, but I wish I understood enough about the relationship between APCC and the Driver to be able to have that answer in my mental picture of the system.

 

Thanks and regards,

Craig


Re: Initiation Parameters - APCC vs Driver

DFisch
 

Craig, you said it thoroughly, inquiring minds want to know 


On Sun, Apr 11, 2021, 9:42 AM Craig Smith via groups.io <cgsathome=yahoo.com@groups.io> wrote:
I have a question/clarification of the relationship between APCC and the ASCOM V2 driver for Ray or anybody who knows the answer for sure…

My question has to do specifically with the initialization phase and whether anything needs to be initialized in the Driver separately if auto-connecting and starting the driver from APCC.

APCC has a “NOW” button that can be used to auto-configure the driver, but it isn’t clear to me whether this configures only information like the port, time-out parameters and so forth, or does it communication that information plus information about local time-zone, latitude and longitude information, park information and so forth? Or, I guess the third option is whether the driver needs to know site information as long as APCC knows this information?

I found this statement in the APCC manual:

Note that the location, mount type, park and initialization settings in the ASCOM V2 driver are independent of the settings in APCC. You will create and adjust these settings within APCC. Refer to the ASCOM manual for additional settings that are useful when using APCC.

This seems to imply that I don’t need to make any of these settings in the driver itself.  Is this true even if I tick the auto-config and auto-connect boxes in the Driver section of APCC?

To further clarify (only if necessary), my workflow in the past for a portable setup has been to setup the site information in the Driver and in APCC, then I ticked the auto-connect box anyhow and this seemed to work.  (But I never understood whether I really needed to configure the site information in the driver ahead of time.)  After a year-long hiatus, my workflow this year has been to start APCC with the auto-configure and auto-connect buttons unticked, and to use the “NOW” button and “CONNECT” buttons to initiate the driver.  In this work flow, I have not been setting the driver site (and other) information independently, and that also works.

I realize that I could experimentally determine what I need to configure independently in the driver, but I wish I understood enough about the relationship between APCC and the Driver to be able to have that answer in my mental picture of the system.

Thanks and regards,
Craig


Re: Mach2 thru-mount USB when using USB 3.0 ? (and an M51)

Dominique
 

Hi Jeffc,
I have a complex installation (see the diagram in PJ) and I have no problem with my QHY294C and QHY294M-Pro, even for the 47M mode flats of the QHY294M-pro. It is useful to put a Hub-USB3 powered at the output of the Mach2 before an active extension cable. I only have a bit rate problem with a QHY5III224c because with the Altair GPCAM3 224C at 154fps no problem either.
I think that the duration of the exposures should be limited to 180s with this type of camera and in particular without Ha filter.
Dominique


Re: Mach2 thru-mount USB when using USB 3.0 ? (and an M51)

Keith Olsen
 

I have found that JSAUX produces a great quality USB cable.   I would occasionally have issues related to usb cables and after I switched to all JSAUX I have not had any cable issues.  This includes a 16' cable from my usb hub to my computer.  I've also noticed that the connections are tighter with these cables that others that i've used.  


Re: Mach2 thru-mount USB when using USB 3.0 ? (and an M51)

Eric Weiner
 

Jeff,

I have the same camera and mount as you and have not had any problems. Could it be USB 3 overall cable length? Keep the total USB 3 length under 10 feet. One difference is I use a Pegasus Ultimate Power Box v2 on the OTA, then run the shortest USB 3 cables possible between my accessories and the UPBv2. Keep in mind the output USB 3 cable from the mount to your PC must also be included in that 10 foot overall length limit, unless you use a USB 3 extender which are quite expensive.

Eric


Re: Mach2 thru-mount USB when using USB 3.0 ? (and an M51)

Dale Ghent
 

On Apr 11, 2021, at 02:27, Jeffc <jeffcrilly@gmail.com> wrote:

i've been troubleshooting an issue with a new camera (QHY268M) (and of course new-to-me drivers).

This is the second night I've had the QHY268M up and running.
The reliability of getting images out of it has been very hit and miss for me.
I'm using the Ascom QHY drivers, but also noted issues with "native driver" capture apps.

The reliability issue seems to be cable related:

-- It turns out if I run the USB 3 cable direct from the camera to the computer then it seems reliable. (I'm still testing this configuration for "longevity".)
-- However if I run the cable "through the Mach2 mount", then the connectivity is kind of flakey. Sometimes the downloads just don't happen. Sometimes the camera disappears from the win10 Device Manager.

Works: Camera --> USB-3-B--cable--USB-3-A --> Computer
Is flakey: Camera --> USB3-B--cable--USB-A --> Mach2 --> USB-A--cable--USB-A --> Computer

Two rules with USB3:

1. Keep cables runs between powered equipment short. I don't do runs more than 2m.

2. Use quality cables. "Amazon's Choice" cables are a dice roll, so just source cables directly from a decent manufacturer. L-Com, for one, but StarTech and Tripp Lite seem to source their cables from some place decent, too.

USB3 far less tolerant of distance and interference than USB2 is. You have to plan to these aspects. USB3 unpowered USB3 extension cables are unreliable in my experience. They add too much length to the total run in a lot of cases, their own construction quality might not be great, and of course there's the extra issue of just having two more physical connections in the line.

For my two QHY-based rigs (Mach1/130GTX/QHY600M and RST135/CFF92/QHY268M) I put a USB hub on the top of the telescope and run all on-scope equipment to that. In my case, the USB hub is a Pegasus Ultimate Power Box v2 or Pegasus Pocket Powerbox Advanced, respectively. A 2m USB cable comes off that and, on my Mach1, goes through the mount and directly into my imaging mini PC. My one PC drives both rigs at the same time, so I can't really keep it mounted on the telescope like many do now.


Re: Cable talk (with Linda Richman)

Dale Ghent
 

On Apr 11, 2021, at 08:11, Astronut <hg2u@hotmail.com> wrote:

Great Info !
About the L-com cables...
When they say ultra flexible, does that mean that they are ultra durable, to withstand many repeated movements, - OR - do they offer ultra low physical resistance to movement (like the ZWO USB3 flat cables that they use wth their cameras), OR BOTH ?
Both. Their high-flex USB cables are rated for 10,000 flex cycles. They use a TPE jacket instead of the more typical PVC one, so they remain flexible in colder temperatures where vinyl will start to stiffen up and, in some cases, crack.

So far, the ZWO flat cables seem to have very low resistance to movement, but only in the flat side orientation, of course.
I too am looking for some versatile USB3 cables that are reasonably durable, but with extremely low physical resistance to movement.
ZWO's flat cables are verified trash. I cut one open not too long ago to find two major faults:

1. The pairs are not twisted around each other, which is the only way you can get a flat cable obviously. The lack of this group twist reduces the cable's ability to reject interference

2. There is no encompassing grounded braid under the jacket, so noise rejection is further limited. The individual conductors are molded into the flat cable jacket.

If these cables work for anyone, it's by luck more than anything else. Low noise environment, probably. I had this same issue back when I got my first ZWO camera. The thing couldn't keep a connection in my office, surrounded by a lot of computing equipment, but seemed fine outside, with the ZWO driver's USB Limit setting also set to its lowest value of 40.


Initiation Parameters - APCC vs Driver

Craig Smith
 

I have a question/clarification of the relationship between APCC and the ASCOM V2 driver for Ray or anybody who knows the answer for sure…

My question has to do specifically with the initialization phase and whether anything needs to be initialized in the Driver separately if auto-connecting and starting the driver from APCC.

APCC has a “NOW” button that can be used to auto-configure the driver, but it isn’t clear to me whether this configures only information like the port, time-out parameters and so forth, or does it communication that information plus information about local time-zone, latitude and longitude information, park information and so forth? Or, I guess the third option is whether the driver needs to know site information as long as APCC knows this information?

I found this statement in the APCC manual:

Note that the location, mount type, park and initialization settings in the ASCOM V2 driver are independent of the settings in APCC. You will create and adjust these settings within APCC. Refer to the ASCOM manual for additional settings that are useful when using APCC.

This seems to imply that I don’t need to make any of these settings in the driver itself.  Is this true even if I tick the auto-config and auto-connect boxes in the Driver section of APCC?

To further clarify (only if necessary), my workflow in the past for a portable setup has been to setup the site information in the Driver and in APCC, then I ticked the auto-connect box anyhow and this seemed to work.  (But I never understood whether I really needed to configure the site information in the driver ahead of time.)  After a year-long hiatus, my workflow this year has been to start APCC with the auto-configure and auto-connect buttons unticked, and to use the “NOW” button and “CONNECT” buttons to initiate the driver.  In this work flow, I have not been setting the driver site (and other) information independently, and that also works.

I realize that I could experimentally determine what I need to configure independently in the driver, but I wish I understood enough about the relationship between APCC and the Driver to be able to have that answer in my mental picture of the system.

Thanks and regards,
Craig


Re: Cable talk (with Linda Richman)

M Hambrick
 

I have had really good luck with the USB cables I have gotten from L-Com. McMaster is also a good source of cables.

There is also a category of cable called continuous flex. These cables are not necessarily more flexible than a regular cable, but they are designed to withstand repeated movements without failing. I ordered one of these continuous flex Cat 5 ethernet cables to use with my Focuser Boss, and it was actually quite stiff. The continuous flex USB cables seem to be OK though.

Mike


Re: Cable talk (with Linda Richman)

Astronut
 

Great Info !
About the L-com cables...
When they say ultra flexible, does that mean that they are ultra durable, to withstand many repeated movements, - OR - do they offer ultra low physical resistance to movement (like the ZWO USB3 flat cables that they use wth their cameras), OR BOTH ?
So far, the ZWO flat cables seem to have very low resistance to movement, but only in the flat side orientation, of course.
I too am looking for some versatile USB3 cables that are reasonably durable, but with extremely low physical resistance to movement.
Thanks,
Tim


Re: Mach2 thru-mount USB when using USB 3.0 ? (and an M51)

Terri Zittritsch
 

Use a usb repeater just before the mach2, will clean things up once and for all.    You’re cables are not the issue, and doubtful it’s the hub.   I use a $15 hub throughout the Vermont winter.    I have an 8” usb a to a cable on the mount and then a usb repeater cable which is spec’d to drive another 15’ thought the mount side (better than std usb3 which is only 3M) but it’s not the length but the added connections which cause issue here.  I did a bunch of testing early on with lots of configurations and cables.  The run through the mount was the issue on mount 14. 


Re: Mach2 thru-mount USB when using USB 3.0 ? (and an M51)

annaski
 

I've also had problems with running the camera 'thru-mount', even with a powered hub on top. Sometimes the camera didn't show up at all, though other devices (slower devices) worked fine.
I've switched to an Eagle4 on top so the only thing I run through the mount now is the CP5 'backwards' up to the Eagle. This works reliably, probably due to the lower speed.


Re: Mach2 thru-mount USB when using USB 3.0 ? (and an M51)

Jeffc
 

ok.. I read the Mach2 manual.   It seems this might be a reasonable option:

Presumably the cabling with the hub would be ...

Computer --> USB-3-A--cable--USB-3-B --> Geamo hub --> USB-3-A--cable--USB-3-A. --> Mount --> USB-3-A--cable--USB-3-B --> camera

-jeff


On Sat, Apr 10, 2021 at 11:27 PM Jeffc via groups.io <jeffcrilly=gmail.com@groups.io> wrote:
i've been troubleshooting an issue with a new camera (QHY268M) (and of course new-to-me drivers).

This is the second night I've had the QHY268M up and running.   
The reliability of getting images out of it has been very hit and miss for me.   
I'm using the Ascom QHY drivers, but also noted issues with "native driver" capture apps.

The reliability issue seems to be cable related:

-- It turns out if I run the USB 3 cable direct from the camera to the computer then it seems reliable.   (I'm still testing this configuration for "longevity".)
-- However if I run the cable "through the Mach2 mount", then the connectivity is kind of flakey.  Sometimes the downloads just don't happen.  Sometimes the camera disappears from the win10 Device Manager.

Works:   Camera --> USB-3-B--cable--USB-3-A --> Computer
Is flakey:  Camera --> USB3-B--cable--USB-A --> Mach2 --> USB-A--cable--USB-A --> Computer

Anyone else run into USB-3 issues with the "mach2 USB pass-thru"?
Any suggested solutions?    

For example, I'm wondering if adding a USB extender somewhere along the data path would help.

(I will note the USB-2 ST-8300M worked fine with the Mach2 "thru the mount USB".)

A workaround would be to move the computer to the OTA.  To be honest, I think this is the best solution as the focuser and other devices can then connect directly to the computer without the need for a USB hub.  I would just need a smaller computer - Like an Eagle or a NUC.   (I'm currently using a late 2012 Intel-i5 Mac-Mini (running win10) which requires AC power, tho a 12volt input mod is possible.   The Mac-Mini seems rather lightweight, but it is still a bit large for "on-top of the OTA".)

Here's my QHY268M first light, 300 seconds Luminance only under light polluted skies with the AP 130 GT & Mach2 unguided.
image.png


Mach2 thru-mount USB when using USB 3.0 ? (and an M51)

Jeffc
 

i've been troubleshooting an issue with a new camera (QHY268M) (and of course new-to-me drivers).

This is the second night I've had the QHY268M up and running.   
The reliability of getting images out of it has been very hit and miss for me.   
I'm using the Ascom QHY drivers, but also noted issues with "native driver" capture apps.

The reliability issue seems to be cable related:

-- It turns out if I run the USB 3 cable direct from the camera to the computer then it seems reliable.   (I'm still testing this configuration for "longevity".)
-- However if I run the cable "through the Mach2 mount", then the connectivity is kind of flakey.  Sometimes the downloads just don't happen.  Sometimes the camera disappears from the win10 Device Manager.

Works:   Camera --> USB-3-B--cable--USB-3-A --> Computer
Is flakey:  Camera --> USB3-B--cable--USB-A --> Mach2 --> USB-A--cable--USB-A --> Computer

Anyone else run into USB-3 issues with the "mach2 USB pass-thru"?
Any suggested solutions?    

For example, I'm wondering if adding a USB extender somewhere along the data path would help.

(I will note the USB-2 ST-8300M worked fine with the Mach2 "thru the mount USB".)

A workaround would be to move the computer to the OTA.  To be honest, I think this is the best solution as the focuser and other devices can then connect directly to the computer without the need for a USB hub.  I would just need a smaller computer - Like an Eagle or a NUC.   (I'm currently using a late 2012 Intel-i5 Mac-Mini (running win10) which requires AC power, tho a 12volt input mod is possible.   The Mac-Mini seems rather lightweight, but it is still a bit large for "on-top of the OTA".)

Here's my QHY268M first light, 300 seconds Luminance only under light polluted skies with the AP 130 GT & Mach2 unguided.
image.png


Re: Cable talk (with Linda Richman)

Eric Dreher
 

Agreed on all counts, with Anderson Powerpoles used everywhere possible.  This extends to my ham radio equipment as well.

I recently purchased a new Yaesu 2m transceiver that came with the most ridiculous harness power connector I've ever seen.  The radio now sports 30A Anderson's.


Re: Cable talk (with Linda Richman)

Kenneth Tan
 

Thanks for the recommendations! Always good to know where to get good stuff.

On Sun, 11 Apr 2021 at 08:49, Dale Ghent <daleg@...> wrote:

> On Apr 10, 2021, at 12:47, Bryan R. <bross138@...> wrote:
>
> I am a fan of Switchcraft DC jacks.  They seem to be of much better quality than run-of-the-mill amazon stuff, bit easier to solder, and made in USA.  Would like to hear that others have used for ethernet RJ45 connectors if fabricating their own patch cables as I do.

I personally prefer not to solder things anymore. While I'm pretty comfortable with my soldering skills, I prefer to skip that with cables because it makes fixes in the field more of an ordeal and I never have that 3rd hand when I need it. So, for power, I do crimped powerpole with an array of adapters that I make myself.

For the typical 5.5/2.1mm or 5.5/2.5mm coaxial power plugs, I buy bags of premade connectors that have pigtails, and they're readily available with 18 awg wiring. Example:

https://www.amazon.com/gp/product/B079CKL6P9/

I take these, trim them down a little and crimp 15A powerpole ends on to them. Since I run a Pegasus UPBv2 with 5.5/2.1mm power sockets instead of a powerpole hub, I just have these at both ends and run a powerpole extension cable between them of appropriate length. I also make these out of a roll of 18 awg silcone jacketed zip wire. Pretty flexible and more than sufficient in the winter in my mid-Atlantic US temperate clime.

All my powerpile/cabling stuff fits in a small fishing tackle box and I don't need a soldering iron (and power for it) to make anything I need when it comes to 12V DC. Crimper, stripper, knife, side cutters, and all my supplies fit nicely on a box that's easy to pack and doesn't take up much space:

https://i.imgur.com/Gt68XsO.jpg

For USB, I exclusively use L-com (l-com.com) cables now. They have a line of high-flex USB2/3 cables in various lengths that are really super nice to use, especially for through-mount cabling:

https://www.l-com.com/usb-high-flex-usb-cable-assemblies

They also have high-flex versions cat 5e/6/6a ethernet and HDMI.

For ethernet and RS232 over 8p8c/twisted pair, I just crimp my own using wire and connectors sourced from wherever is handy at the moment; usually Monoprice. I use some leftover solid-core cat6 I have on a spool from wiring my house if the wiring isn't going to move much, otherwise I have some stranded-core cat5e. The only use of such cable I have is on my main rig where I made a cable to connect the focuser controller on my UPBv2 to the HSM35 that drives my 130GTX's focuser. This will go away soon, though, as it's all getting replaced with a Nitecrawler and that's just another 12V+USB2 wiring job.

/dale





Re: APCC PRO and Virtual Ports

Ray Gralak
 

Hi Jack,

My only suggestion is that you can try increasing the timeout in the AP V2 driver. APCC uses a third-party component for the virtual ports in APCC. The component is exactly the same for both APCC Standard and Pro, and there should be no reason that higher virtual COM port numbers would act differently than lower port numbers.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Jack Huerkamp
Sent: Saturday, April 10, 2021 11:28 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC PRO and Virtual Ports

Ray,

I modified the sample horizon file you sent to me and now have the horizon for my location input into APCC PRO.
But now I have a new issue.

I have been using APCC Standard for years to control my AP1600 using SkyTools PRO V3 and now SkyTools V4
Imaging. I have the mount connected to the computer using the Serial/USB connection on COM3.
I have two Virtual Ports created - COM6 and COM 12. I have been connecting SkyTools to the mount using
ASCOM V2 Telescope Driver - v5.30.10 on COM12 and occasionally I get a lost communication error message,
SkyTools shuts down, and I then have to restart SkyTools and reconnect it. I thought that maybe since I was on
COM12, that was the problem. So I created COM31, went into the ACSOM V2 Telescope Driver setup for
SkyTools, changed the COM port from 12 to 31, checked the port and it was found. But when I went to connect
SkyTools to the mount, a connection could not be established.
I eventually went back to COM12 and it connected right away.

Any idea what the problem could be? I would like to use the higher COM numbers if possible.

Yours truly,

Jack

Jack Huerkamp
Jack's Astro Accessories, LLC
38388 Pine Street
Pearl River, LA 70452-5192
985-445-5063
mallincamusa@gmail.com
www.mallincamusa.com
30.37N 89.76W

All of us get lost in the darkness.
Dreamers learn to steer by the stars.
………………………………….Neil Peart




--
This email has been checked for viruses by AVG.
https://www.avg.com



4661 - 4680 of 82382