Date   

Re: Voyager and APCC

Dale Ghent
 

As a data point, I use the 3D view every session and over RDP (over wifi which then ends up going over my home's internal 1Gb ethernet or wifi network) as well. The mini-PC that runs my stuff is a Whiskey Lake i5-8265U based system and the RDP clients are anything from Windows PCs and Macs to iPhones and iPads - it works fine on all. The Whiskey Lake i5 system (OnLogic ML100G-51) has only the integrated Intel UHD 620 GPU.

NINA, PHD2, and SharpCap are all clients to APCC and the ASCOM driver while the 3D view is running and nothing bad happens in either app when the view is opened while they are connected.

Perhaps Voyager polls its connected drivers at a more aggressive rate and is sensitive to even a momentary unresponsiveness caused by the 3D view being opened and loaded?

On Jan 4, 2021, at 12:24, ejr@robau-designs.com wrote:

Latest version of Windows.
Using Windows 10 pro, so I RDP to it via Windows RDP.
Latest version of APCC pro.
Cat 6 ethernet to the observatory from my office upstairs in my home to the observatory in the back yard.
Leodardo the developer of Voyager indicated that he experiences the same thing.
My next move would be the upgraded graphics card or attempt a more detailed analysis without RDP.


Re: Voyager and APCC

Ray Gralak
 

The 3D view should not require too much 3D resource. I doubt a higher-performance graphics card would make a difference.

What kind of desktop resolution are you using when you remote? If it is something like 4K you could try something less taxing, like 1920x1080.

Also, you could run Windows Task Manager to see the utilization of each resource type on the "Performance" tab.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ejr@robau-designs.com
Sent: Monday, January 4, 2021 9:24 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Voyager and APCC

Latest version of Windows.
Using Windows 10 pro, so I RDP to it via Windows RDP.
Latest version of APCC pro.
Cat 6 ethernet to the observatory from my office upstairs in my home to the observatory in the back yard.
Leodardo the developer of Voyager indicated that he experiences the same thing.
My next move would be the upgraded graphics card or attempt a more detailed analysis without RDP.


Re: Voyager and APCC

Emilio J. Robau, P.E.
 

Latest version of Windows. 
Using Windows 10 pro, so I RDP to it via Windows RDP. 
Latest version of APCC pro. 
Cat 6 ethernet to the observatory from my office upstairs in my home to the observatory in the back yard.   
Leodardo the developer of Voyager indicated that he experiences the same thing.
My next move would be the upgraded graphics card or attempt a more detailed analysis without RDP.


Re: Voyager and APCC

Ray Gralak
 

I think you may have pegged it. Yes, I am using remote desktop. I will test it out locally, but I could swear that it
happens locally and yes, I have a separate card. Maybe I invest in another separate card. Is it okay to go to the
next level of ASCOM? Last time I installed APCC Pro, I think I recall a warning to stay on 6.4 SP1.
It is now okay to update to ASCOM 6.5 SP1.

Are you using Windows' built-in Remote Desktop? Or some 3rd-party application, like TeamViewer?

Windows Remote Desktop is usually more efficient than 3rd-party applications, so if you are using it, are you remoted to the other system via hardwire Ethernet, or WiFi? If you are using WiFi, that can cause graphics update delays if there is congestion or interference.

By the way, I assume you are using APCC Pro/Standard 1.8.8.x, correct? Some of the earlier versions of APCC could get more easily "stalled" waiting for display output to finish over a remote connection.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ejr@robau-designs.com
Sent: Monday, January 4, 2021 8:58 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Voyager and APCC

I think you may have pegged it. Yes, I am using remote desktop. I will test it out locally, but I could swear that it
happens locally and yes, I have a separate card. Maybe I invest in another separate card. Is it okay to go to the
next level of ASCOM? Last time I installed APCC Pro, I think I recall a warning to stay on 6.4 SP1.


Re: Voyager and APCC

Emilio J. Robau, P.E.
 

I think you may have pegged it.  Yes, I am using remote desktop.  I will test it out locally, but I could swear that it happens locally and yes, I have a separate card.  Maybe I invest in another separate card.  Is it okay to go to the next level of ASCOM?   Last time I installed APCC Pro, I think I recall a warning to stay on 6.4 SP1.


Re: Windows 10? (Was: Lost communications with mount)

 

One thing you can try is downloading updates to a thumb drive when you have access to internet that isn't metered, and installing them to your computer when you want to do updating. This would allow you to keep your computer current, while having the automatic updates disabled and preventing the dreaded mid-run update. 


Liam




From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of deonb <deonb@...>
Sent: Thursday, December 31, 2020 12:58 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Windows 10? (Was: Lost communications with mount)
 
On Thu, Dec 31, 2020 at 10:39 AM, Mike Dodd wrote:
That's a real shame. I really don't like software vendors assuming everyone has unlimited Internet speed and data. I live in a rural Virginia county, and get Internet via a 4G cell tower. We don't stream anything, and can't join a Zoom call because of the limited speed and data. But I have fairly dark skies. :-)
Microsoft for so many years have been the brunt of jokes about Windows being insecure that they'll rather loose users than not have them update regularly. I can't say I blame them.

However, in your case, definitely use Pro - it helps a lot, Home will give you no control. Set all your connections to metered, and disable updates in Group Policy.

And maybe <ducks> ... Starlink.


Re: Voyager and APCC

Ray Gralak
 

I run Voyager on my computer to run my scopes, cameras, mount and so on and so forth. Whenever I launch
the three dimensional view of my scope in APCC to see the scope and mount in operation, the mount gets
disconnected from Voyager and it is a pain to get reconnected.
That is a sign of a 3D graphics resource or performance issue.

Are you using a remote desktop application of some sort? Some remote desktop apps are inefficient at displaying 3D.

If not using remote desktop, does the computer have a discrete video card, or are you using the built in video output of the CPU?

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ejr@robau-designs.com
Sent: Sunday, January 3, 2021 8:54 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] Voyager and APCC

Hello,

I run Voyager on my computer to run my scopes, cameras, mount and so on and so forth. Whenever I launch
the three dimensional view of my scope in APCC to see the scope and mount in operation, the mount gets
disconnected from Voyager and it is a pain to get reconnected. I have to shut everything down and then start up
again. I posted this issue with the developer and he indicated that it was on the APCC side of the equation and
to post a ticket. Not looking to blame everyone, but I am looking to see if somehow this can be resolved since it
is a known issue. Voyager really is a spectacular piece of software and it would be good to be able to toggle to
APCC to see where the scope is from time to time. This is especially true when doing those weight side up slews
so you can see the crash in action when it actually happens. Gives you a second or two to actually fret or even
chicken out and stop it. I would rather see it happen then not. It is like if you are going to have an accident, you
might as well see it coming. If you are going to have a heart attack you might as well fell the angina first,
because you may be able to get a triple bypass to delay it for some time. You know what I mean?

Another quick question. I notice that APCC recommends not installing the latest version of ASCOM. Is there any
reason for this? I am pretty sure that a thread exists out there so if you can send me in that direction I appreciate
the lead.



Finally, thanks to Ray for providing a license for Pempro Version 3 after I had to rebuild my computer after the
last tropical storm here in S. Florida rained on it in my observatory. Funny thing is that it survived a direct hit from
cat 3 or 4 Irma, but a weak tropical storm did it in.


Re: Voyager and APCC

R Botero
 

Are you running Voyager as Admin and letting it open APCC?

I don't have APCC-Pro but it should make no difference.  I suspect the above.  Hopefully Ray can help but if he cannot replicate the issue (unless he is a user of Voyager) it will be difficult to pinpoint where it arises.  Have your APCC logs ready...

Roberto


Re: Voyager and APCC

Emilio J. Robau, P.E.
 

I use APCC pro.

I don't leave my 3D view on.  I have launched it from time to time to understand that it disconnects from Voyager and causes a problem when it is launched even before I start to slew and am doing nothing else but have the equipment connected.  I don't necessarily want to leave it on all the time.   I just want to be able to launch it from time to time, especially when I do slews of interest.

I don't think Voyager gives you any opportunity to recover and close the 3D view.  If that is an option, that is preferred for sure, and I am going to check it, but the functionality of being able to see the 3d view in APCC pro is desirable any time I want to access it. 

I discussed the issue with Leonardo via an email and he pointed me to Ray.  The issue is a known issue. He indicated that I needed to open a ticket with APCC.

I am glad you don't experience it.   My computer resources are excellent.  I am not doing anything in the background but imaging, so I really doubt it is a resource issue, but I may be incorrect.  

In fact, this issue has arisen on two different machines and the current machine that runs the setup is a relatively strong machine and is a brand new.  I can't remember the card, but I have 16 GB on the motherboard and am running Win 10 with the latest service packs.

In order to eliminate any issues, I am migrating to the latest issuance of ASCOM, unless someone chimes in and says not to at this point in time.


Re: Voyager and APCC

R Botero
 

Hi (what's your name?)

I am a user of Voyager and APCC also.  I don't leave the 3D view on (I have an IPCam in my RoR shed in case I want to check where the mount/scope are) but I don't encounter the issue you have.  What graphic card and RAM do you have on your PC?   The reported disconnection of the mount by Voyager happens when the latter cannot poll the mount as often as required.  This usually happens when your software environment doesn't have enough resources.  I get this sometimes when I am running image processing software (PixInsight) at the same time as all my imaging applications - not recommended!  Voyager eventually recovers as (memory) resources become available.  You could check this by closing the 3D view when you see the error message in the Monitor tab of Voyager.

Ray will confirm if any of the above if of use in your case. 

As for ASCOM, I use the latest version of the platform (6.5 SP1) and have no issues with APCC.  There were some problems for APCC-Pro users, not of APCC, but those have supposedly been resolved with SP1.

Good luck!

Roberto


Voyager and APCC

Emilio J. Robau, P.E.
 

Hello,

I run Voyager on my computer to run my scopes, cameras, mount and so on and so forth.   Whenever I launch the three dimensional view of my scope in APCC to see the scope and mount in operation, the mount gets disconnected from Voyager and it is a pain to get reconnected.  I have to shut everything down and then start up again.  I posted this issue with the developer and he indicated that it was on the APCC side of the equation and to post a ticket.   Not looking to blame everyone, but I am looking to see if somehow this can be resolved since it is a known issue.  Voyager really is a spectacular piece of software and it would be good to be able to toggle to APCC to see where the scope is from time to time.  This is especially true when doing those weight side up slews so you can see the crash in action when it actually happens.  Gives you a second or two to actually fret or even chicken out and stop it.  I would rather see it happen then not.  It is like if you are going to have an accident, you might as well see it coming.  If you are going to have a heart attack you might as well fell the angina first, because you may be able to get a triple bypass to delay it for some time.  You know what I mean?

Another quick question.  I notice that APCC recommends not installing the latest version of ASCOM.  Is there any reason for this?  I am pretty sure that a thread exists out there so if you can send me in that direction I appreciate the lead.

Finally, thanks to Ray for providing a license for Pempro Version 3 after I had to rebuild my computer after the last tropical storm here in S. Florida rained on it in my observatory.  Funny thing is that it survived a direct hit from cat 3 or 4 Irma, but a weak tropical storm did it in. 


Re: APCC GPS Error

Dale Ghent
 


The standard MNEA bit rate is 4800. My own ublox7 works fine at that. 

/dale 

On Jan 4, 2021, at 5:15 AM, David Fabrizio via groups.io <DavFab@...> wrote:

Ray,

 Thank you. I’ll try a few different baud rates and see what happens.


On Jan 3, 2021, at 6:26 PM, David Fabrizio via groups.io <DavFab@...> wrote:



All,

 I am trying to connect a U-Blox7 GPS to v1.8.8.0 of APCC and I get this error message:

UpdateLocation. Index and length must refer to a location within the string. Parameter name: Length.

 The gps is on com7. Any ideas?

Thank you

Dave Fabrizio


Re: Additional Options for storing the RAPAS,CP and Counterweights

Harley Davidson
 

John

HELLO, yes those Silver Metallic Sharpie's work great on dark colored surfaces. Like you said it will take a couple coats to see well. And if you need to change the name I have used lacquer thinner on a rag to clean the old text off. Then I'll use a fan to help dry the cloth surface and get rid of the lacquer smell.

So glad to hear the tree didn't destroy the mount inside your SKB case. That is truly amazing!

tony

On 1/3/2021 11:34 PM, John A. Sillasen wrote:
I also purchased the BUBM series of soft sided cases from Amazon after Tony's (Harley Davidson- aka starastronomer on YouTube) review video. What came to be hard was labeling the cases as there's no name tag sleeve anywhere. One reviewer suggests the clear top version and a label maker for that one.

My wife solved my problem with the black BUBM cases, Sharpie's Silver Metallic Permanent marker.  It shows up well - especially after a second coat after the first completely dried.  Photo attached so you can see the results. 

I picked up two packs of these 3 packs. Two for Keypads (1100 & Mach 1), one for CP4 for 1100, the CP4 for the Mach 1 stays on the Eagle Pier all the time so I don't need it for that.  I use the other 2 small ones for cable sets.  One complete CABPP6 & the other for a 12v cable for CP4. The spare middle one holds USB, Ethernet and Straight Thru Serial cable. 

All Silver Metallic Sharpie labeled accordingly. 

As for the Rigid cases. As someone who's Telescope Shed was destroyed by a felled tree, my one Rigid case that used to hold a spare Feathertouch focuser for scopes to swap as needed. And a few other things in the past.

It was completely destroyed. 

I'm the guy who ordered the huge SKB case from MyCaseBuilder.com for the 1100 with 16" DOVELM162,  the CP4-GTO, Keypad & Counterweight shaft.  It had its handle snapped off and one corner bent with the side case snap bent out of shape.  That corner held the CP4 and it tests and upgrades well.

I don't wish to replace the exact SKB case but man is it tough. I'll go with a smaller case that holds only  the 1100 with a  DOVEDV10 but without the CP4,  shaft or Keypad. Sure the Rigid cases are built well but they are not SKB or Pelican quality. That monster case is a two person carry to lift into a van.  



John A. Sillasen




Re: APCC GPS Error

David Fabrizio
 

Ray,

 Thank you. I’ll try a few different baud rates and see what happens.


On Jan 3, 2021, at 6:26 PM, David Fabrizio via groups.io <DavFab@...> wrote:



All,

 I am trying to connect a U-Blox7 GPS to v1.8.8.0 of APCC and I get this error message:

UpdateLocation. Index and length must refer to a location within the string. Parameter name: Length.

 The gps is on com7. Any ideas?

Thank you

Dave Fabrizio


Re: Lost communications with mount

weihaowang
 

Ouch!  That's the power adapter that came with the mount.  I will see if I can find another one.

--

Homepage:

http://www.asiaa.sinica.edu.tw/~whwang/

Astrobin gallery:
http://www.astrobin.com/users/whwang/


Re: Additional Options for storing the RAPAS,CP and Counterweights

John A. Sillasen
 

I also purchased the BUBM series of soft sided cases from Amazon after Tony's (Harley Davidson- aka starastronomer on YouTube) review video. What came to be hard was labeling the cases as there's no name tag sleeve anywhere. One reviewer suggests the clear top version and a label maker for that one.

My wife solved my problem with the black BUBM cases, Sharpie's Silver Metallic Permanent marker.  It shows up well - especially after a second coat after the first completely dried.  Photo attached so you can see the results. 

I picked up two packs of these 3 packs. Two for Keypads (1100 & Mach 1), one for CP4 for 1100, the CP4 for the Mach 1 stays on the Eagle Pier all the time so I don't need it for that.  I use the other 2 small ones for cable sets.  One complete CABPP6 & the other for a 12v cable for CP4. The spare middle one holds USB, Ethernet and Straight Thru Serial cable. 

All Silver Metallic Sharpie labeled accordingly. 

As for the Rigid cases. As someone who's Telescope Shed was destroyed by a felled tree, my one Rigid case that used to hold a spare Feathertouch focuser for scopes to swap as needed. And a few other things in the past.

It was completely destroyed. 

I'm the guy who ordered the huge SKB case from MyCaseBuilder.com for the 1100 with 16" DOVELM162,  the CP4-GTO, Keypad & Counterweight shaft.  It had its handle snapped off and one corner bent with the side case snap bent out of shape.  That corner held the CP4 and it tests and upgrades well.

I don't wish to replace the exact SKB case but man is it tough. I'll go with a smaller case that holds only  the 1100 with a  DOVEDV10 but without the CP4,  shaft or Keypad. Sure the Rigid cases are built well but they are not SKB or Pelican quality. That monster case is a two person carry to lift into a van.  



John A. Sillasen



Re: Lost communications with mount

Ray Gralak
 

Hi Wei-Hao,

The mount is seeing many intermittent "Low Power" issues. I counted 17 in the logs you sent me.

C:\Users\Ray\Downloads\ApccZip-Academia_Sinica-2021-01-04-104109\APCC-2020-12-30-143202.txt (2 hits)
Line 2437: 0002437 2020-12-30 14:33:51.961: Error, Command Thread, Low Power Detected
Line 29056: 0029056 2020-12-30 14:41:00.318: Error, Command Thread, Low Power Detected
C:\Users\Ray\Downloads\ApccZip-Academia_Sinica-2021-01-04-104109\APCC-2020-12-31-111617.txt (2 hits)
Line 255: 0000255 2020-12-31 11:16:27.870: Error, Command Thread, Low Power Detected
Line 785: 0000785 2020-12-31 11:16:36.918: Error, Command Thread, Low Power Detected
C:\Users\Ray\Downloads\ApccZip-Academia_Sinica-2021-01-04-104109\APCC-2020-12-31-123552.txt (1 hit)
Line 17186: 0017186 2020-12-31 12:41:59.422: Error, Command Thread, Low Power Detected
C:\Users\Ray\Downloads\ApccZip-Academia_Sinica-2021-01-04-104109\APCC-2021-01-01-132357.txt (1 hit)
Line 14369: 0014369 2021-01-01 13:29:08.788: Error, Command Thread, Low Power Detected
C:\Users\Ray\Downloads\ApccZip-Academia_Sinica-2021-01-04-104109\APCC-2021-01-01-133412.txt (1 hit)
Line 125411: 0125411 2021-01-01 14:18:05.031: Error, Command Thread, Low Power Detected
C:\Users\Ray\Downloads\ApccZip-Academia_Sinica-2021-01-04-104109\APCC-2021-01-01-144212.txt (1 hit)
Line 177: 0000177 2021-01-01 14:42:30.441: Error, Command Thread, Low Power Detected
C:\Users\Ray\Downloads\ApccZip-Academia_Sinica-2021-01-04-104109\APCC-2021-01-01-144500.txt (2 hits)
Line 12710: 0012710 2021-01-01 14:49:36.618: Error, Command Thread, Low Power Detected
Line 71121: 0071121 2021-01-01 15:09:58.207: Error, Command Thread, Low Power Detected
C:\Users\Ray\Downloads\ApccZip-Academia_Sinica-2021-01-04-104109\APCC-2021-01-01-151729.txt (3 hits)
Line 2123: 0002123 2021-01-01 15:18:19.377: Error, Command Thread, Low Power Detected
Line 2189: 0002189 2021-01-01 15:18:21.118: Error, Command Thread, Low Power Detected
Line 5289: 0005289 2021-01-01 15:19:22.102: Error, Command Thread, Low Power Detected
C:\Users\Ray\Downloads\ApccZip-Academia_Sinica-2021-01-04-104109\APCC-2021-01-01-152631.txt (4 hits)
Line 9820: 0009820 2021-01-01 15:30:02.093: Error, Command Thread, Low Power Detected
Line 14802: 0014802 2021-01-01 15:31:46.256: Error, Command Thread, Low Power Detected
Line 24381: 0024381 2021-01-01 15:35:06.401: Error, Command Thread, Low Power Detected
Line 25570: 0025570 2021-01-01 15:35:31.440: Error, Command Thread, Low Power Detected

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of weihaowang
Sent: Sunday, January 3, 2021 8:07 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Lost communications with mount

Hi Ray,

This is the link to the zipped APCC log:
https://www.dropbox.com/s/nj83ukryf49r9a8/ApccZip-Academia_Sinica-2021-01-04-104109.zip?dl=0

I had updated the timeout and crosshair update rate according to your suggestions. Nothing changed.
The disconnection persists.

Regarding ASCOM driver, I do find that the mount continues to track after the disconnection message
from TheSky. This is based on the observation of the location of the RA park marks. It continues to
move (very slowly, of course). However, I can identify two click sounds in my last trial. The first one
comes a few seconds before the TheSky error message. So I believe it signals the parking. Then after
a while, perhaps half minute, a second click sound shows up (without my clicking off the TheSky
warning window and without any attempts to reconnect in TheSky). I believe this signals unparking
and the start of tracking. Then quite many minutes later, I saw that the RA park marks have moved a bit.
So, I think what happened is that the mount parked itself for about half minutes. Although it started to
track again, this short period of parking is enough to interrupt the imaging or observations. This is
found when the mount was connected via USB.

I found another interesting thing when I connected to Mach2 with wifi. Perhaps because of the slower
response of wifi, sometimes TheSky doesn't show an error message at all, even though the mount had
parked and re-unparked. Maybe it is too fast from park to unpark, TheSky did not have time to
realize the disconnection under wifi.

Cheers,
Wei-Hao


--


Homepage:

http://www.asiaa.sinica.edu.tw/~whwang/

Astrobin gallery:
http://www.astrobin.com/users/whwang/


Re: Lost communications with mount

weihaowang
 

Hi Ray,

This is the link to the zipped APCC log:
https://www.dropbox.com/s/nj83ukryf49r9a8/ApccZip-Academia_Sinica-2021-01-04-104109.zip?dl=0

I had updated the timeout and crosshair update rate according to your suggestions.  Nothing changed.
The disconnection persists.

Regarding ASCOM driver, I do find that the mount continues to track after the disconnection message
from TheSky.  This is based on the observation of the location of the RA park marks.  It continues to
move (very slowly, of course).  However, I can identify two click sounds in my last trial.  The first one
comes a few seconds before the TheSky error message.  So I believe it signals the parking.  Then after
a while, perhaps half minute, a second click sound shows up (without my clicking off the TheSky 
warning window and without any attempts to reconnect in TheSky).  I believe this signals unparking
and the start of tracking.  Then quite many minutes later, I saw that the RA park marks have moved a bit.
So, I think what happened is that the mount parked itself for about half minutes.  Although it started to
track again, this short period of parking is enough to interrupt the imaging or observations.  This is 
found when the mount was connected via USB.

I found another interesting thing when I connected to Mach2 with wifi. Perhaps because of the slower
response of wifi, sometimes TheSky doesn't show an error message at all, even though the mount had
parked and re-unparked.  Maybe it is too fast from park to unpark, TheSky did not have time to 
realize the disconnection under wifi.

Cheers,
Wei-Hao


--

Homepage:

http://www.asiaa.sinica.edu.tw/~whwang/

Astrobin gallery:
http://www.astrobin.com/users/whwang/


Re: APCC GPS Error

Ray Gralak
 

Hi David,

UpdateLocation. Index and length must refer to a location within the string. Parameter name: Length.
That means there was an error parsing the response from the device. It could be that the data received was corrupted, or in an unrecognized format. If the error persists, it could be device's response is not in a standard format, or maybe the wrong baud rate is selected.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Fabrizio via groups.io
Sent: Sunday, January 3, 2021 5:26 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC GPS Error

All,

I am trying to connect a U-Blox7 GPS to v1.8.8.0 of APCC and I get this error message:

UpdateLocation. Index and length must refer to a location within the string. Parameter name: Length.

The gps is on com7. Any ideas?



Thank you

Dave Fabrizio


Re: Hanging case for GTOCP4?

Don Anderson
 

I like the gearbox noise!

Don Anderson


On Sunday, January 3, 2021, 12:04:45 p.m. MST, Roland Christen via groups.io <chris1011@...> wrote:



Kinda sounds like true class A power amplifier operation in my Hi-Fi hobby.  The output devices are always "on", at full current.  They run at their hottest with no signal and need a ton of heat sinks and you never enclose them.
I think you are mixing apples and oranges. Massive heatsinks are not required on our CP controllers.

Microstepper servos need current to hold position, otherwise the rotor falls back to one of the magnetic positions. All AC servo motors have this requirement. DC servos do not need to hold position and current falls to zero when not moving. Dc servos also have large gear reductions so they can operate at very low current levels and still produce plenty of torque at the worm shaft. Typical gear reduction of a Dc servo is around 60:1, whereas AC servos such as used on the Mach2 have reduction ratio of 2:1 or thereabouts.

Dc servos require very expensive gearboxes and expensive DC servomotors, otherwise the periodic error gets ragged and massive. They also make audible noise that people don't like. For the Mach2 we decided to use AC servos with belt drive so that we could apply the savings to add the very expensive Renishaw absolute encoders. With DC, the cost would have put us out of contention with competitive mounts. Plus people would have ragged about the slewing noise.

Rolando


-----Original Message-----
From: Jeff B <mnebula946@...>
To: main@ap-gto.groups.io
Sent: Sun, Jan 3, 2021 12:04 pm
Subject: Re: [ap-gto] Hanging case for GTOCP4?

Kinda sounds like true class A power amplifier operation in my Hi-Fi hobby.  The output devices are always "on", at full current.  They run at their hottest with no signal and need a ton of heat sinks and you never enclose them.

Ignorant but curious, since absolute encoders know where they are all the time, can a model be built by manually pointing the scope, without any goto commands?

Jeff

On Sun, Jan 3, 2021 at 12:23 PM Roland Christen via groups.io <chris1011=aol.com@groups.io> wrote:
On the CP5 controllers I would advise against putting them inside a cloth bag. The CP3 and CP4 are ok because they do not produce very much current for the two servo motors under normal tracking conditions. The CP5 sends full current to both stepper servos all the time, even when they are not moving, so the drivers are at full power and produce more heat. The case dissipates the heat to the surrounding air just fine, but if they are inside a cloth bag, they will not have any air circulation.

Roland Christen
Astro-Physics Inc.


-----Original Message-----
From: Dale Ghent <daleg@...>
To: main@ap-gto.groups.io
Sent: Sun, Jan 3, 2021 10:58 am
Subject: Re: [ap-gto] Hanging case for GTOCP4?

With the mounting bracket, you only have to losen two thumb screws and tip the unit forward to remove it, and the opposite to install it into the bracket. It’s quite quick to do and doesn’t require any tools. The thumb screws are similar to if not the same as the ones which secure the sliding access panels on your Mach1. 

/dale

On Jan 3, 2021, at 10:46, Patrick Spencer <patrick.spencer2@...> wrote:

Hi everyone,

I recently upgraded from a CP3 to a CP4 for my Mach1. The only thing I miss about the CP3 is the neat hanging case, which made it easy to "grab and go" and allowed me to hang the controller from a knob at the base of the mount. Unfortunately, the CP4 is too large to fit in the CP3 case. I know there's a mounting bracket option, but I like being able to quickly disconnect the control box and take it inside when I'm finished imaging.

There are a lot of clever folks in this group, so I was wondering if anyone has come up with a similar hanging pouch/bag solution for the CP4?

Thanks,

Patrick Spencer

--
Roland Christen
Astro-Physics

--
Roland Christen
Astro-Physics

3721 - 3740 of 79096