Ascom Error

[Elisabeth Milne]

I had the same error on both my imaging rigs last night.  I was using 2.6.9dev2.  My sequence (SGP Pro) stopped because my guider failed to restart.  PHD2 reported this error:

ASCOM error – Cannot start exposure with given parameters: (ASCOM.sxCamera.BaseCamera) StartExposure called while in state cameraError

I use different guiding cameras on my rigs.  On one I have a Lodestar and on the other a QHY camera.  I got the same error on both rigs.  It occured twice on the Lodestar rig - once when doing a meridian flip and the second time when slewing to a new target.  On the QHY rig, it did it when slewing to new target. 

I noticed that 'use multi-star' had bcome unselected on both rigs.  I have installed dev 3.

Is there anything else I should be thinking about?

[Brian Valente]

Hi Elisabeth

Can you please upload your guide and debug logs https://openphdguiding.org/getting-help/

Also if you are using SGP please update to the latest dev3 release  https://openphdguiding.org/development-snapshots/

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/3fcb2a8f-82fb-4d66-ab43-bdeaa6e15650n%40googlegroups.com.

--

Brian 

Brian Valente

portfolio brianvalentephotography.com 

[Elisabeth Milne]

Of course.  I believe that this is the relevant log file.  I have today upgraded to dev 3 and will try it tonight, weather permitting.

[Brian Valente]

Hi Elisabeth

that is the debug log. 

it would be better if you used the automatic log uploader to send the relevant stuff (see previous response and link)

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/7ce85bed-ca83-47a8-a550-873021b65d54n%40googlegroups.com.

[Elisabeth Milne]

OK.  I think this is it.  Apologies for earlier error.

https://openphdguiding.org/logs/dl/PHD2_logs_Rqtx.zip

[Elisabeth Milne]

OK.  Now on dev3.  I just got the same error again after the mount did a meridian flip.  I should perhaps add that I've been runing this rig for at least two years now and have only had this problem since switching to the dev version (for multistar guiding).

Here's tonights log

https://openphdguiding.org/logs/dl/PHD2_logs_2WNg.zip

[Brian Valente]

Hi Elisabeth

I don't see any errors or problems in the logs you sent. Can you maybe tell me at what time of night there was a problem?

Also I see you are using a 10micron mount, I assume that mount has encoders on both axis, correct?

 

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/77193673-8bca-407b-a544-8362831062d6n%40googlegroups.com.

[bw_msgboard]

Hi Elisabeth.  You’ve sent us three sets of logs now and I’m having some trouble lining them up with what you’re reporting.  Here’s what I see:

 

1. 2.6.9dev2 log from 1/11/2021: none of these errors recorded
2. 2.6.9dev3 log from 1/12/2021: one message of this type recorded
3. 2.6.9dev2 log from 1/10/2020: none of these errors recorded

 

So the only thing I can look at is the second one.  In that case, the ASCOM driver for the LodeStar reported a failure while PHD2 was trying to poll for the completion of an exposure.  This is a very basic operation using a camera and a driver that are known to be very stable.  And it has nothing to do with changing versions of PHD2, this code hasn’t changed in a long time.  It points to a problem with the USB connection to the camera, either a cable or problems in the USB subsystem of the PC.  I don’t really doubt that you saw more messages than this – but the question is, did they all come from PHD2?  The message text is coming from the ASCOM driver, is your imaging app also using an ASCOM driver for the main camera?  Could the message have originated there?  Has something changed on your PC, perhaps an unwanted change in power management?  It’s also possible for a single failed USB cable to wreak havoc on the entire USB system, thus affecting other apps that are trying to communicate.  It could also be caused by a low power situation on one of the cameras, perhaps because of cold temps.   Are you running the two scopes from the same PC?  

 

I would tackle this in the same way as the more common “camera timeout” messages people sometimes get.  The trouble-shooting section in the PHD2 manual describes a set of diagnostic steps that can be taken to isolate the problem.  Fortunately, it can be done during the daytime.  You’ll see that it tries to address both bandwidth and power delivery aspects of these operations.

 

Hope you can track it down,

Bruce

 

 

 

---

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/c6cfc807-fe70-4172-982c-a651ade242d3n%40googlegroups.com.

[Elisabeth Milne]

Thanks for the replies.  I have been running both rigs for a while without issue.  They run from 2 separate PCs and are run remotely (PCs in Spain and me in UK looking in via TeamViewer).  The 10 Micron mounts are correctly set up (in as much as it is possible to set these things up correctly!).  I had a good run last night except for one error on Rig 2 (the one that I posted the correct log for (#2 on Bruce's list).  I was sat in front of the PC looking at the Rig 2 PC on TeamViewer when this happened.  It happened after the mount performed a meridian flip.  This would have been around 11pm -ish.  The message came up in PHD2 in a pale yellow box at the top of the image window.  See photo below.  SGP (my imaging App) is also using an Ascom driver for the camera (a QSI 690WSG).  There has been no change in the PC for 2 years (other that the usual pesky Windows updates).  It was around -4 degrees last night (according to teh focuser temperature readout).

Since this occurred during a meridian flip, I am leaning towards it being a cable issue.  Perhaps something is a little loose at the camera/cable connection.  I did have further meridian flips (on different targets) last night without issue, but a cable/connection issue could be random.

The only thing that makes me question this is that there is a little oddness still in PHD.  With dev 2, I was getting the issue whereby the 'use multiple stars' box was becoming 'unticked'.  Last night, using dev 3 for the first time, the box stayed ticked, but on-screen I wasn't seeing the 'big green square with a few little circles'.  I was just seeing the green square.  (Apologies for the technical language.)

 

[Elisabeth Milne]

I've read the Troubleshooting bit in the manual.  As I said, the PC is in Spain and I am in the UK.  Even if I wanted to, I cannot just pop over there due to Covid.  I have guys there that I can get to do small tasks (change cable, or whatever) but I cannot get detailed troubleshooting done.  The PCs are in a pierside cabinet - and I need a 3m cable to get from PC to Lodestar. 

One quick question, could this issue be caused by the USB Suspend 'feature' of Windows.  I see that I had this 'Enabled' on my Rig 2 PC, but 'Disabled' on Rig 1 (where I have only had one guiding issue over the last 2 nights.

[bw_msgboard]

 

 

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Elisabeth Milne
Sent: Wednesday, January 13, 2021 1:18 AM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] Ascom Error

 

Thanks for the replies.  I have been running both rigs for a while without issue.  They run from 2 separate PCs and are run remotely (PCs in Spain and me in UK looking in via TeamViewer).  The 10 Micron mounts are correctly set up (in as much as it is possible to set these things up correctly!).  I had a good run last night except for one error on Rig 2 (the one that I posted the correct log for (#2 on Bruce's list).  I was sat in front of the PC looking at the Rig 2 PC on TeamViewer when this happened.  It happened after the mount performed a meridian flip.  This would have been around 11pm -ish.  The message came up in PHD2 in a pale yellow box at the top of the image window.  See photo below.  SGP (my imaging App) is also using an Ascom driver for the camera (a QSI 690WSG).  There has been no change in the PC for 2 years (other that the usual pesky Windows updates).  It was around -4 degrees last night (according to teh focuser temperature readout).

 

Since this occurred during a meridian flip, I am leaning towards it being a cable issue.  Perhaps something is a little loose at the camera/cable connection.  I did have further meridian flips (on different targets) last night without issue, but a cable/connection issue could be random.

 

The only thing that makes me question this is that there is a little oddness still in PHD.  With dev 2, I was getting the issue whereby the 'use multiple stars' box was becoming 'unticked'.  Last night, using dev 3 for the first time, the box stayed ticked, but on-screen I wasn't seeing the 'big green square with a few little circles'.  I was just seeing the green square.  (Apologies for the technical language.)

 

The automatic disabling of the ‘use multiple stars’ function was a behavior of dev2 – it happens when the user manually selects a guide star.  In dev3, that checkbox will never be disabled behind your back, but it is still true that manually selecting a guide star will force single-star guiding.  That’s the way it has to be.  You need to use the auto-select-star feature despite what you think you’re seeing on the display.  Judging just from your screenshot, those are probably saturated or near-saturated stars you’re seeing. 

 

Bruce

 

 

 

 

On Wednesday, 13 January 2021 at 03:28:51 UTC bw_m...@earthlink.net wrote:

Hi Elisabeth.  You’ve sent us three sets of logs now and I’m having some trouble lining them up with what you’re reporting.  Here’s what I see:

 

1.      2.6.9dev2 log from 1/11/2021: none of these errors recorded

2.      2.6.9dev3 log from 1/12/2021: one message of this type recorded

3.      2.6.9dev2 log from 1/10/2020: none of these errors recorded

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/8d156b3b-13f3-4cea-b59f-deceb6b425a6n%40googlegroups.com.

[bw_msgboard]

 

 

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Elisabeth Milne
Sent: Wednesday, January 13, 2021 1:42 AM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] Ascom Error

 

I've read the Troubleshooting bit in the manual.  As I said, the PC is in Spain and I am in the UK.  Even if I wanted to, I cannot just pop over there due to Covid.  I have guys there that I can get to do small tasks (change cable, or whatever) but I cannot get detailed troubleshooting done.  The PCs are in a pierside cabinet - and I need a 3m cable to get from PC to Lodestar. 

 

One quick question, could this issue be caused by the USB Suspend 'feature' of Windows.  I see that I had this 'Enabled' on my Rig 2 PC, but 'Disabled' on Rig 1 (where I have only had one guiding issue over the last 2 nights.

 

That is a possibility – I would reset that immediately although I don’t see why it would correlate with meridian flips. Perhaps you can have one of your on-site guys replace the USB cable to the guide camera.  If you’re running Windows 10, I would recommend that you closely control when Windows updates are done and then sanity-check all these settings after one is completed.  This is especially true for the probably-unwanted feature updates which tend to big-foot a lot of things.

 

Bruce

 

 

On Wednesday, 13 January 2021 at 09:18:11 UTC Elisabeth Milne wrote:

Thanks for the replies.  I have been running both rigs for a while without issue.  They run from 2 separate PCs and are run remotely (PCs in Spain and me in UK looking in via TeamViewer).  The 10 Micron mounts are correctly set up (in as much as it is possible to set these things up correctly!).  I had a good run last night except for one error on Rig 2 (the one that I posted the correct log for (#2 on Bruce's list).  I was sat in front of the PC looking at the Rig 2 PC on TeamViewer when this happened.  It happened after the mount performed a meridian flip.  This would have been around 11pm -ish.  The message came up in PHD2 in a pale yellow box at the top of the image window.  See photo below.  SGP (my imaging App) is also using an Ascom driver for the camera (a QSI 690WSG).  There has been no change in the PC for 2 years (other that the usual pesky Windows updates).  It was around -4 degrees last night (according to teh focuser temperature readout).

 

Since this occurred during a meridian flip, I am leaning towards it being a cable issue.  Perhaps something is a little loose at the camera/cable connection.  I did have further meridian flips (on different targets) last night without issue, but a cable/connection issue could be random.

 

The only thing that makes me question this is that there is a little oddness still in PHD.  With dev 2, I was getting the issue whereby the 'use multiple stars' box was becoming 'unticked'.  Last night, using dev 3 for the first time, the box stayed ticked, but on-screen I wasn't seeing the 'big green square with a few little circles'.  I was just seeing the green square.  (Apologies for the technical language.)

 

 

 

 

On Wednesday, 13 January 2021 at 03:28:51 UTC bw_m...@earthlink.net wrote:

Hi Elisabeth.  You’ve sent us three sets of logs now and I’m having some trouble lining them up with what you’re reporting.  Here’s what I see:

 

1.      2.6.9dev2 log from 1/11/2021: none of these errors recorded

2.      2.6.9dev3 log from 1/12/2021: one message of this type recorded

3.      2.6.9dev2 log from 1/10/2020: none of these errors recorded

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/ab5712e4-b4c7-43ef-ab73-2add8dd786f9n%40googlegroups.com.

[Elisabeth Milne]

Thanks again.   

It is possible that I did manually select a star last night, when I was trying to get everything running again after the ‘crash’.  Normally it is autoselected as you recommend.

Windows updates should only happen during the day.  We did have an update download through the night, but it didn’t install until this morning.

I’ll try it tonight with the USB power thingymajig disabled.

I’m also an Ascom version or two out of date.

If none of that works, I’ll get the cable replaced.

[Brian Valente]

Hi Elisabeth

FYI i have a lodestar as well and i've run into the camera state = error problem before. It was around for a while and very intermittent for me. I just power cycled the USB port on which it was connected (pegasus astro powerbox) and got it working again. It hasn't happened for a while and I could never find the issue. so it's not just you :)

also FYI if you do upgrade ascom, make sure to go to the latest 6.5SP1 - 6.5 had an issue that caused plate solving to not work correctly

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/34c34771-acb7-4148-997d-d9636135ccf6n%40googlegroups.com.

[bw_msgboard]

I would advise against churning application software – like ASCOM – while you’re in the middle of trouble-shooting.  This isn’t a software problem, or at least not software above the hardware driver level.  Didn’t I read that Spain has been having exceptionally cold temperatures lately?  If that’s the case and since the problem happens on multiple systems, I would be taking a hard look at the power delivery to those cameras – especially if there are USB hubs involved.  Many of those devices don’t do well in very cold temps.

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/34c34771-acb7-4148-997d-d9636135ccf6n%40googlegroups.com.

[David Kerber]

I have also seen cold temperatures kill USB cables. Replacing them with
ones called "rugged" made a huge difference in their ability to handle
temperature extremes.

On 1/13/2021 1:59 PM, bw_msgboard wrote:
>
> I would advise against churning application software – like ASCOM –
> while you’re in the middle of trouble-shooting. This isn’t a software
> problem, or at least not software above the hardware driver level.
> Didn’t I read that Spain has been having exceptionally cold
> temperatures lately? If that’s the case and since the problem happens
> on multiple systems, I would be taking a hard look at the power
> delivery to those cameras – especially if there are USB hubs involved.
> Many of those devices don’t do well in very cold temps.
>
> Bruce
>

> ------------------------------------------------------------------------
>
> *From:*open-phd...@googlegroups.com
> [mailto:open-phd...@googlegroups.com] *On Behalf Of *Elisabeth Milne
> *Sent:* Wednesday, January 13, 2021 9:03 AM
> *To:* Open PHD Guiding
> *Subject:* Re: [open-phd-guiding] Ascom Error

>
> Thanks again.
>
> It is possible that I did manually select a star last night, when I
> was trying to get everything running again after the ‘crash’.
>  Normally it is autoselected as you recommend.
>
> Windows updates should only happen during the day.  We did have an
> update download through the night, but it didn’t install until this
> morning.
>
> I’ll try it tonight with the USB power thingymajig disabled.
>
> I’m also an Ascom version or two out of date.
>
> If none of that works, I’ll get the cable replaced.
>
> On Wednesday, 13 January 2021 at 16:14:59 UTC bw_m...@earthlink.net wrote:
>

> ------------------------------------------------------------------------
>
> *From:*open-phd...@googlegroups.com
> [mailto:open-phd...@googlegroups.com] *On Behalf Of *Elisabeth Milne
> *Sent:* Wednesday, January 13, 2021 1:42 AM
> *To:* Open PHD Guiding
> *Subject:* Re: [open-phd-guiding] Ascom Error

> Aascom_PHD.jpg
>
> On Wednesday, 13 January 2021 at 03:28:51 UTC
> bw_m...@earthlink.net wrote:
>
> Hi Elisabeth.  You’ve sent us three sets of logs now and
> I’m having some trouble lining them up with what you’re
> reporting.  Here’s what I see:
>

> 1.2.6.9dev2 log from 1/11/2021: none of these errors recorded
>
> 2.2.6.9dev3 log from 1/12/2021: one message of this type
> recorded
>
> 3.2.6.9dev2 log from 1/10/2020: none of these errors recorded

> ------------------------------------------------------------------------
>
> *From:*open-phd...@googlegroups.com
> [mailto:open-phd...@googlegroups.com] *On Behalf Of
> *Elisabeth Milne
> *Sent:* Tuesday, January 12, 2021 2:39 PM
> *To:* Open PHD Guiding
> *Subject:* Re: [open-phd-guiding] Ascom Error

> */ASCOM error – Cannot start exposure

> with given parameters:
> (ASCOM.sxCamera.BaseCamera)
> StartExposure called while in state

> cameraError/*

> <https://groups.google.com/d/msgid/open-phd-guiding/3fcb2a8f-82fb-4d66-ab43-bdeaa6e15650n%40googlegroups.com?utm_medium=email&utm_source=footer>.

>
>
> --
>
> Brian
>
> Brian Valente
>
> portfolio brianvalentephotography.com

> <http://brianvalentephotography.com>

>
> --
> You received this message because you are
> subscribed to the Google Groups "Open PHD
> Guiding" group.
> To unsubscribe from this group and stop
> receiving emails from it, send an email to
> open-phd-guidi...@googlegroups.com.
>
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/open-phd-guiding/7ce85bed-ca83-47a8-a550-873021b65d54n%40googlegroups.com
> <https://groups.google.com/d/msgid/open-phd-guiding/7ce85bed-ca83-47a8-a550-873021b65d54n%40googlegroups.com?utm_medium=email&utm_source=footer>.

>
>
> --
>
> Brian
>
> Brian Valente
>
> portfolio brianvalentephotography.com

> <http://brianvalentephotography.com>

>
> --
> You received this message because you are subscribed to
> the Google Groups "Open PHD Guiding" group.
> To unsubscribe from this group and stop receiving emails
> from it, send an email to open-phd-guidi...@googlegroups.com.
>
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/open-phd-guiding/c6cfc807-fe70-4172-982c-a651ade242d3n%40googlegroups.com
> <https://groups.google.com/d/msgid/open-phd-guiding/c6cfc807-fe70-4172-982c-a651ade242d3n%40googlegroups.com?utm_medium=email&utm_source=footer>.

>
> --
> You received this message because you are subscribed to the Google
> Groups "Open PHD Guiding" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to open-phd-guidi...@googlegroups.com.
>
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/open-phd-guiding/ab5712e4-b4c7-43ef-ab73-2add8dd786f9n%40googlegroups.com
> <https://groups.google.com/d/msgid/open-phd-guiding/ab5712e4-b4c7-43ef-ab73-2add8dd786f9n%40googlegroups.com?utm_medium=email&utm_source=footer>.

>
> --
> You received this message because you are subscribed to the Google
> Groups "Open PHD Guiding" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to open-phd-guidi...@googlegroups.com

> <mailto:open-phd-guidi...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/open-phd-guiding/34c34771-acb7-4148-997d-d9636135ccf6n%40googlegroups.com
> <https://groups.google.com/d/msgid/open-phd-guiding/34c34771-acb7-4148-997d-d9636135ccf6n%40googlegroups.com?utm_medium=email&utm_source=footer>.

>
> --
> You received this message because you are subscribed to the Google
> Groups "Open PHD Guiding" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to open-phd-guidi...@googlegroups.com

> <mailto:open-phd-guidi...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/open-phd-guiding/1FDC673DFA534FEAAAA416B017C289D7%40HomeDesktop
> <https://groups.google.com/d/msgid/open-phd-guiding/1FDC673DFA534FEAAAA416B017C289D7%40HomeDesktop?utm_medium=email&utm_source=footer>.

[Elisabeth Milne]

We don't use USB hubs - I've had too many fail.  It was around -4 in Spain last night (0 tonight).  My home observatory is in the UK where we regularly get down lower than that.  I can't cycle the hub, but I could reboot the PC.  But it came back after a disconnect/reconnect in the PHD interface. 

[Elisabeth Milne]

OK.  It just happened again.  During the meridian flip, I heard the Windows 'USB disconnect' sound.  Then when the guider tried to restart, I got the error.  It's looking increasingly like a cable issue - yes?

Here is the log.

https://openphdguiding.org/logs/dl/PHD2_logs_DCBq.zip

[Brian Valente]

>>>  I heard the Windows 'USB disconnect' sound.  Then when the guider tried to restart, I got the error.  It's looking increasingly like a cable issue - yes?

sure sounds like it!

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/381e2a03-1c94-4293-af5c-9cbbb6f080b0n%40googlegroups.com.

[George Shoup]

At what temperature do you all start seeing cable and connector issues?  I believe the G11 is rated for 0 F.  The coldest temp I have imaged is approx 10 F.  

Sent from my iPhone

On Jan 13, 2021, at 3:41 PM, Brian Valente <bval...@gmail.com> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i74Z-5k_tPfZqQb1S-ZfEuNcX%3D%2BF%3DtiXR6cOHzWzJPuYw%40mail.gmail.com.

[David Kerber]

Last winter I started having trouble when the temperatures started going
below about 30F. Since I got better cables, I've worked down into the
low 20s with no trouble. We haven't been colder than that yet this year,
but there is still lots of winter left to go...

>> <https://groups.google.com/d/msgid/open-phd-guiding/3fcb2a8f-82fb-4d66-ab43-bdeaa6e15650n%40googlegroups.com?utm_medium=email&utm_source=footer

>> <https://groups.google.com/d/msgid/open-phd-guiding/3fcb2a8f-82fb-4d66-ab43-bdeaa6e15650n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>>
>> >
>> >
>> > --
>> >
>> > Brian
>> >
>> > Brian Valente
>> >
>> > portfolio brianvalentephotography.com
>> <http://brianvalentephotography.com>

>> > <http://brianvalentephotography.com

>> <http://brianvalentephotography.com>>
>> >
>> > --
>> > You received this message because you are
>> > subscribed to the Google Groups "Open PHD
>> > Guiding" group.
>> > To unsubscribe from this group and stop
>> > receiving emails from it, send an email to
>> > open-phd-guidi...@googlegroups.com.
>> >
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/open-phd-guiding/7ce85bed-ca83-47a8-a550-873021b65d54n%40googlegroups.com
>> <https://groups.google.com/d/msgid/open-phd-guiding/7ce85bed-ca83-47a8-a550-873021b65d54n%40googlegroups.com>
>>
>> >

>> <https://groups.google.com/d/msgid/open-phd-guiding/7ce85bed-ca83-47a8-a550-873021b65d54n%40googlegroups.com?utm_medium=email&utm_source=footer

>> <https://groups.google.com/d/msgid/open-phd-guiding/7ce85bed-ca83-47a8-a550-873021b65d54n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>>
>> >
>> >
>> > --
>> >
>> > Brian
>> >
>> > Brian Valente
>> >
>> > portfolio brianvalentephotography.com
>> <http://brianvalentephotography.com>

>> > <http://brianvalentephotography.com

>> <http://brianvalentephotography.com>>
>> >
>> > --
>> > You received this message because you are subscribed to
>> > the Google Groups "Open PHD Guiding" group.
>> > To unsubscribe from this group and stop receiving emails
>> > from it, send an email to
>> open-phd-guidi...@googlegroups.com.
>> >
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/open-phd-guiding/c6cfc807-fe70-4172-982c-a651ade242d3n%40googlegroups.com
>> <https://groups.google.com/d/msgid/open-phd-guiding/c6cfc807-fe70-4172-982c-a651ade242d3n%40googlegroups.com>
>>
>> >

>> <https://groups.google.com/d/msgid/open-phd-guiding/c6cfc807-fe70-4172-982c-a651ade242d3n%40googlegroups.com?utm_medium=email&utm_source=footer

>> <https://groups.google.com/d/msgid/open-phd-guiding/c6cfc807-fe70-4172-982c-a651ade242d3n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>>
>> >
>> > --
>> > You received this message because you are subscribed to
>> the Google
>> > Groups "Open PHD Guiding" group.
>> > To unsubscribe from this group and stop receiving
>> emails from it,
>> > send an email to open-phd-guidi...@googlegroups.com.
>> >
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/open-phd-guiding/ab5712e4-b4c7-43ef-ab73-2add8dd786f9n%40googlegroups.com
>> <https://groups.google.com/d/msgid/open-phd-guiding/ab5712e4-b4c7-43ef-ab73-2add8dd786f9n%40googlegroups.com>
>>
>> >

>> <https://groups.google.com/d/msgid/open-phd-guiding/ab5712e4-b4c7-43ef-ab73-2add8dd786f9n%40googlegroups.com?utm_medium=email&utm_source=footer

>> <https://groups.google.com/d/msgid/open-phd-guiding/ab5712e4-b4c7-43ef-ab73-2add8dd786f9n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>>
>> >
>> > --
>> > You received this message because you are subscribed to
>> the Google
>> > Groups "Open PHD Guiding" group.
>> > To unsubscribe from this group and stop receiving
>> emails from it, send
>> > an email to open-phd-guidi...@googlegroups.com
>> > <mailto:open-phd-guidi...@googlegroups.com>.
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/open-phd-guiding/34c34771-acb7-4148-997d-d9636135ccf6n%40googlegroups.com
>> <https://groups.google.com/d/msgid/open-phd-guiding/34c34771-acb7-4148-997d-d9636135ccf6n%40googlegroups.com>
>>
>> >

>> <https://groups.google.com/d/msgid/open-phd-guiding/34c34771-acb7-4148-997d-d9636135ccf6n%40googlegroups.com?utm_medium=email&utm_source=footer

>> <https://groups.google.com/d/msgid/open-phd-guiding/34c34771-acb7-4148-997d-d9636135ccf6n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>>
>> >
>> > --
>> > You received this message because you are subscribed to
>> the Google
>> > Groups "Open PHD Guiding" group.
>> > To unsubscribe from this group and stop receiving
>> emails from it, send
>> > an email to open-phd-guidi...@googlegroups.com
>> > <mailto:open-phd-guidi...@googlegroups.com>.
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/open-phd-guiding/1FDC673DFA534FEAAAA416B017C289D7%40HomeDesktop
>> <https://groups.google.com/d/msgid/open-phd-guiding/1FDC673DFA534FEAAAA416B017C289D7%40HomeDesktop>
>>
>> >

>> <https://groups.google.com/d/msgid/open-phd-guiding/1FDC673DFA534FEAAAA416B017C289D7%40HomeDesktop?utm_medium=email&utm_source=footer

>> <https://groups.google.com/d/msgid/open-phd-guiding/1FDC673DFA534FEAAAA416B017C289D7%40HomeDesktop?utm_medium=email&utm_source=footer>>.
>>
>>
>> --
>> You received this message because you are subscribed to the
>> Google Groups "Open PHD Guiding" group.
>> To unsubscribe from this group and stop receiving emails from it,

>> send an email to open-phd-guidi...@googlegroups.com
>> <mailto:open-phd-guidi...@googlegroups.com>.
>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/open-phd-guiding/381e2a03-1c94-4293-af5c-9cbbb6f080b0n%40googlegroups.com
>> <https://groups.google.com/d/msgid/open-phd-guiding/381e2a03-1c94-4293-af5c-9cbbb6f080b0n%40googlegroups.com?utm_medium=email&utm_source=footer>.

>>
>>
>>
>> --
>> Brian
>>
>>
>>
>> Brian Valente
>> portfolio brianvalentephotography.com
>> <http://brianvalentephotography.com>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Open PHD Guiding" group.
>> To unsubscribe from this group and stop receiving emails from it,

>> send an email to open-phd-guidi...@googlegroups.com
>> <mailto:open-phd-guidi...@googlegroups.com>.
>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i74Z-5k_tPfZqQb1S-ZfEuNcX%3D%2BF%3DtiXR6cOHzWzJPuYw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i74Z-5k_tPfZqQb1S-ZfEuNcX%3D%2BF%3DtiXR6cOHzWzJPuYw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

> --
> You received this message because you are subscribed to the Google
> Groups "Open PHD Guiding" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to open-phd-guidi...@googlegroups.com
> <mailto:open-phd-guidi...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/open-phd-guiding/487612D8-3A09-4239-9B4F-A1BC077974BF%40gmail.com
> <https://groups.google.com/d/msgid/open-phd-guiding/487612D8-3A09-4239-9B4F-A1BC077974BF%40gmail.com?utm_medium=email&utm_source=footer>.

[George Shoup]

Thanks. I will search for low temp rated cables at Amazon

Sent from my iPhone

> On Jan 13, 2021, at 5:09 PM, David Kerber <rhody...@gmail.com> wrote:
>
> Last winter I started having trouble when the temperatures started going below about 30F. Since I got better cables, I've worked down into the low 20s with no trouble. We haven't been colder than that yet this year, but there is still lots of winter left to go...

> To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/d6302340-335f-222e-c757-542f024d3942%40gmail.com.