Date   

Re: APCC PRO and Virtual Ports

Ray Gralak
 

Hi Jack,

Also, if I connect a CAT cable from the CP4 to the computer in addition to the Serial/USB cable that I currently have,
which connection mode will take APCC default to. And if there is an issue with the one in use, will APCC flip over to
the second connection mode automatically to keep from losing mount connectivity?
Yes, that is correct.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Jack Huerkamp
Sent: Sunday, April 11, 2021 5:29 PM
To: main@ap-gto.groups.io
Cc: mallincamusa@gmail.com
Subject: Re: [ap-gto] APCC PRO and Virtual Ports

Ray,

Thanks for the suggestion. As soon as I get my 16" RC back up on the mount and I balance the system, I will try
doing what you suggest.

Also, if I connect a CAT cable from the CP4 to the computer in addition to the Serial/USB cable that I currently have,
which connection mode will take APCC default to. And if there is an issue with the one in use, will APCC flip over to
the second connection mode automatically to keep from losing mount connectivity?

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



-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Saturday, April 10, 2021 8:26 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC PRO and Virtual Ports

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











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




Re: APCC PRO and Virtual Ports

Jack Huerkamp
 

Ray,

Thanks for the suggestion. As soon as I get my 16" RC back up on the mount and I balance the system, I will try doing what you suggest.

Also, if I connect a CAT cable from the CP4 to the computer in addition to the Serial/USB cable that I currently have, which connection mode will take APCC default to. And if there is an issue with the one in use, will APCC flip over to the second connection mode automatically to keep from losing mount connectivity?

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

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Saturday, April 10, 2021 8:26 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC PRO and Virtual Ports

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











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


Re: APPM model how many points portable?

Roger Howard
 
Edited

My mirror is locked in place and I am using a moonlite focuser. I’ll reduce the failed solve time allowable and run another set tonight. I just don’t want to use my limited time on extra points I won’t really need. I’m not sure how to only do points around my intended target. Once again my goal is a little more speed as with my schedule I need to be in bed by 8, which is sunset.  The good thing is that I put a telefgizmo cover on  and leave the scope in place over multiple days if the weather permits.  This is just for when I’m only going to do a night, or two.


Re: APPM model how many points portable?

Jeffc
 


> I use SGP and ASTAP. A 90 point model takes about a half hour

>> I didn’t think astap was supported in the AP software; or is this coming ASTAP -> SGP -> AP?


I have also been thinking about using SGP and ASTAP.

Fwiw: I have been assuming APPM (?) uses SGP to capture and plate solve, and SGP in turn uses ASTAP to do the plate solve.   

... but I'm far from knowledgeable on this, tho I would like to confirm this works or not without burning too many cycles ... But I'll probably just try it sometime soon.


Also fwiw I'm still on the SGP learning curve, along with a new camera.  Was using maxim-dl, but I don't have full pinpoint.   (And I've been avoiding TSX from a bad experience with it in the past, which is likely resolved.)  I am almost 100% open at this point for image acquisition apps as long as they don't break the bank or my brain.   e.g. Voyager has been noted in other forums, however it seems to me SGP is more intuitive, and maybe is more supported... and afaik APPM does not work with Voyager.


Point is:  there seems to be many variations/options for software these days, which might have varying performance and capability levels.   It would be good to know what works well (at this point in time).

I also am realizing "what works well" may depend on the imaging hardware one is using - whether ascom-only or natively supported.

E.g. I'm currently moving to an Ascom-only camera (at least I believe there isn't native QHY driver integration with with Maxim or SGP).

The upside is the new camera seems to have blazing download speed compared to the ST-8300M I was previously using.


thx .. this is a timely thread for me, btw.


-jeff


Re: APPM model how many points portable?

Worsel
 

My experience is that points that fail are near the edge of my horizon limits anyway...where I am unlikely to image.  I reduced the time limit on plate solves to about 20% greater than the solve time for most points.  This results in less time lost for points that may fail anyway and still produces an overall robust model with 200 points in about one hour.

A variation would be to reduce the the horizons for platesolving in APPM.

Finally, build a model ONLY for that portion of the sky you plan to image.  This has been discussed before.  Ray has improvements for this approach in the future.

Bryan


Re: APPM model how many points portable?

Ray Gralak
 

Hi Roger,

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.
One point per minute seems very slow, even with a few missed all-sky plate solves. You should be able to get 2-3 points per minute.

To answer your question though, your results will depend on your individual setup. If your mirror is not locked down sufficiently you might be wating your time doing too many points.

-Ray



-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Roger Howard
Sent: Sunday, April 11, 2021 2:59 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APPM model how many points portable?

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: APPM model how many points portable?

ap@CaptivePhotons.com
 

I didn’t think astap was supported in the AP software; or is this coming ASTAP -> SGP -> AP?

 

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of KHursh via groups.io
Sent: Sunday, April 11, 2021 7:24 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM model how many points portable?

 

I use SGP and ASTAP. A 90 point model takes about a half hour


Re: APPM model how many points portable?

KHursh
 

I use SGP and ASTAP. A 90 point model takes about a half hour


Re: APPM model how many points portable?

Roger Howard
 

That was only my second time using the mount. I had 3 fails which went to blind solve with a 5 minute limit on those solves, so that is 15 minutes right there. I’ll probably reduce the blind solve fail time limit and just drop a few points if they fail. So don’t judge anything by me, I’m just starting out. 


Re: APPM model how many points portable?

ap@CaptivePhotons.com
 

My 1100 is due this summer so very curious also, as I will set up each night and tear down, often with a C11, sometimes a 4” refractor.

 

Right now with a MyT I do one large model, then a recalibration each night which takes 10 minutes.  I understand that’s not exactly possible with the AP mount.


One thing from the MyT experience and an SCT – unless you have the mirror locked, the point of diminishing returns gets reached fairly quickly in terms of number of model points and increasing accuracy, as with mirror movement there is an inherent lack of repeatability of getting back to any area of the sky.  Getting a model that gets fractional arc second precision with a scope that’s not repeatable except maybe to 5” or more is not very useful.   One day I may get a different focuser and lock my mirror but in the meantime I accept that lack of precision.

 

But spending 90 minutes a night building a model will be a real bummer.   Is it a plate solve issue?   TSX only takes a second per image to solve.  I really do not like TSX in general, and glad to be getting away, but… 90 minutes?  

 

Say it ain’t so!

 

Linwood

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Roger Howard via groups.io
Sent: Sunday, April 11, 2021 5:59 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APPM model how many points portable?

 

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


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.

4701 - 4720 of 82432