|
I can really use help from fellow members of this forum to hopefully solve a vexing problem I have been having trying to connect my Gen 3 SC with Peter’s original ASCOM driver and George’s new beta ASCOM driver.?
I have flashed (several times) my SC with the version 7.0C firmware obtained from Gary.? The “V” command in Peter’s SCU utility returns 7.0C.? I use a Nexus DSC (the original, not the Pro, version).? The serial port on the Nexus is connected to the DSC port on the SC.? A USB cord directly connects the USB/PC port on the SC to a USB port on my computer (and over the many tests I have run, I have used different USB ports and different PCs).? Before attempting to connect to an ASCOM driver, I align the SC/DSC and the red DSC LED on the SC goes from blinking to solid on.? (In addition, gotos initiated from the Nexus place the object in my eyepiece.)? I set the “Find” parameter on the DSC to “From Planetarium.”
I can connect my scope to Peter’s ASCOM driver (through the ASCOM Device Hub) but with only limited functionality.? Peter and I have looked at the Capabilities tab in the ASCOM Device Hub and Peter tells me that my capabilities report is the one he would expect if his driver was connected to an SC with pre-7.0 (legacy) firmware.? In particular, “Can Move Primary Axis” and “Can Move Secondary Axis” both report “False,” when they should both report “True” if connected to an SC with 7.0 firmware.
When I connect my scope to Peter’s SCU utility, I get the initial “status” report that Peter describes in his readme file.? While this report indicates that the firmware version is 7.0C, it incorrectly reports that the scope is NOT aligned and NOT tracking when I believe both are true.? Also, S (status) commands receive a “status update is not available” response.
I cannot connect to George’s ASCOM driver at all. I get an “operation timed out” error message.? After reviewing the logs of my attempts, George has informed me that his driver is sending my scope commands to obtain certain data from the scope but only gets back some of the data requested (the firmware version) and thus can’t proceed.
I have been working with Gary, Peter and George on this problem over the last few weeks with no solution.? We have not yet determined where the problem is originating – my particular SC, the coding for the drivers/SCU utility or something else entirely.
So, I am reaching out to forum members who have already tried to control their SC through ASCOM to ask for your experiences in connecting with either or both of the ASCOM drivers.? Additionally, if you have not yet tried to use an ASCOM driver but have an SC with the latest firmware and are willing to try in order to help out, I would be very grateful.? In particular, we would be interested in the answers to the following questions.
1.? Have any of you experienced the same issues as described above and were you able to resolve them?
2.? Have you successfully connected with/utilized George’s driver??
[I used version 0.6.0.0 of George’s driver in all my tests.? I know that George is working on a new version, which will close some open ASCOM conformance issues, but due to my personal time constraints I needed to post this message now.? I don’t think the expected new version will have any impact on my issues.]
?
3.? Can you connect to Peter’s driver through the ASCOM Device Hub?? If so, what are the values of “Can Move Primary Axis” and “Can Move Secondary Axis” on the Capabilities tab?
4.? Does the initial “status” report when you connect to Peter’s SCU utility correctly report the current state of your scope (e.g., alignment and tracking)?? Do you get subsequent status reports when you issue “S” commands?
I am going bald with all of the hair I am pulling out over this problem.? Any help anyone can provide would be greatly appreciated!!!
Paul
|
I just released v0.7.0.0 which addresses the remaining ASCOM Conformance issues. Please don't hesitate to reach out if you run into issues.
|
Unfortunately, I have yet to try the new Ascom driver with my 20" and Gen2 Servocat, but I hope to over the next few months, which I know doesn't help you now. With that said have you tried the Ascom Poth Hub rather than the Device Hub? The Poth hub is older,
but contains more configuration options generally. I find it works better with some of my equipment. At least it is something to try.
Alex Z.
toggle quoted message
Show quoted text
I can really use help from fellow members of this forum to hopefully solve a vexing problem I have been having trying to connect my Gen 3 SC with Peter’s original ASCOM driver and George’s new beta ASCOM driver.?
I have flashed (several times) my SC with the version 7.0C firmware obtained from Gary.?
The “V” command in Peter’s SCU utility returns 7.0C.?
I use a Nexus DSC (the original, not the Pro, version).? The serial port on the Nexus is connected to the DSC port on the SC.?
A USB cord directly connects the USB/PC port on the SC to a USB port on my computer (and over the many tests I have run, I have used different USB ports and different PCs).?
Before attempting to connect to an ASCOM driver, I align the SC/DSC and the red DSC LED on the SC goes from blinking to solid on.?
(In addition, gotos initiated from the Nexus place the object in my eyepiece.)?
I set the “Find” parameter on the DSC to “From Planetarium.”
I can connect my scope to Peter’s ASCOM driver (through the ASCOM Device Hub) but with only limited functionality.?
Peter and I have looked at the Capabilities tab in the ASCOM Device Hub and Peter tells me that my capabilities report is the one he would expect if his driver was connected to an SC with
pre-7.0 (legacy) firmware.? In particular, “Can Move Primary Axis” and “Can Move Secondary Axis” both report “False,” when they should both report “True” if connected to an SC with 7.0 firmware.
When I connect my scope to Peter’s SCU utility, I get the initial “status” report that Peter describes in his readme file.?
While this report indicates that the firmware version is 7.0C, it incorrectly reports that the scope is NOT aligned and NOT tracking when I believe both are true.?
Also, S (status) commands receive a “status update is not available” response.
I cannot connect to George’s ASCOM driver at all. I get an “operation timed out” error message.?
After reviewing the logs of my attempts, George has informed me that his driver is sending my scope commands to obtain certain data from the scope but only gets back some of the data requested (the firmware version) and thus can’t proceed.
I have been working with Gary, Peter and George on this problem over the last few weeks with no solution.?
We have not yet determined where the problem is originating – my particular SC, the coding for the drivers/SCU utility or something else entirely.
So, I am reaching out to forum members who have already tried to control their SC through ASCOM to ask for your experiences in connecting with either or both of the ASCOM drivers.?
Additionally, if you have not yet tried to use an ASCOM driver but have an SC with the latest firmware and are willing to try in order to help out, I would be very grateful.?
In particular, we would be interested in the answers to the following questions.
1.? Have any of you experienced the same issues as described above and were you able to resolve them?
2.? Have you successfully connected with/utilized George’s driver??
[I used version 0.6.0.0 of George’s driver in all my tests.?
I know that George is working on a new version, which will close some open ASCOM conformance issues, but due to my personal time constraints I needed to post this message now.?
I don’t think the expected new version will have any impact on my issues.]
?
3.? Can you connect to Peter’s driver through the ASCOM Device Hub??
If so, what are the values of “Can Move Primary Axis” and “Can Move Secondary Axis” on the Capabilities tab?
4.? Does the initial “status” report when you connect to Peter’s SCU utility correctly report the current state of your scope (e.g., alignment and tracking)??
Do you get subsequent status reports when you issue “S” commands?
I am going bald with all of the hair I am pulling out over this problem.?
Any help anyone can provide would be greatly appreciated!!!
Paul
|
George,
Please summarize the features of your new ascom driver.
I currently use the old driver and enjoy remote observing with Stellarium and my dob and ServoCAT—after I do the two star alignment on Argo Navis.
I built a stepper motorized filter slide changer and VB.NET program to remotely change filters. ?Planning to write an ASCOM driver in VB.NET.
Richard Miller
|
This ServoCAT ASCOM driver is fully featured, and makes do with the limitations inherent in the SC as much as possible. The features include:
- Runs as a server, so connections from multiple applications, as well as 32-bit and 64-bit, are supported without using a hub (such as Device Hub or POTH)
- Slew to RA/Dec coordinates, including the Async versions of the methods
- Slew to Alt/Az. This works by converting to RA/Dec and then stopping tracking afterwards
- Sync to Coordinates. This enables use of a plate solver to establish a local offset. This does not use the LocalSync functionality on the SC
- MoveAxis. This enables the equivalent of a virtual hand controller. It also reads the SC firmware configuration to determine the speeds, and exposes them over the ASCOM interface in the standard degrees per second units.
- PulseGuiding. This uses MoveAxis with the "Slow Guiding" rate, with internal timers to stop after a period of time. I haven't really tested this in the field, as I don't have a guider on my SC-mounted Dobsonian. Future versions of this could use the ST-4 port on the SC instead, as it may have more fine-grained control over start and stop responsiveness
- Parking. This uses the Park function built into the SC
In order for the ASCOM driver to work though, you need to have aligned the SC with its DSC ahead of time. I wanted to automate this process with platesolving, but unfortunately the functions aren't there to pull this off. For example, you can't issue a slew through the ArgoNavis DSC, nor can you programmatically set the alignment points.
|
George,
This sounds great. ?Plate solving would be a huge upgrade for me. ?
Is there a link to download your driver?
Thank-you for producing this driver.
Richard Miller
|
Paul, The topography you have implemented is the same as what you would use on the Argo Navis and it looks like what is described in the Nexus manual in the Motor driven telescopes section. However in the setup portion of the Nexus manual, page 12 it looks like they have a different topography for Gen3 Servo Cat.. The Nexus is hooked to the USB port on ServoCat and the PC communicated via the “From Planetarium” menu. Which I interpret to mean via the Nexus serial port or Nexus Wi-Fi. ?You might want to try that. I don’t currently have a ServoCat system as I sold that scope about 10 years ago. I am one of the club operator for the 40 which has the Nexus and Servocat gen 3. I will look at it next time out to the site. I do know tat there is something plugged into both the USB port and the serial port and occasionally a PC is hooked to it. It does communicate with Sky Safari via Wi-Fi. I feel certain that the Nexus communicates with the Servo Cat via USB on the 40. Bob Rose ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Paul Abel Sent: Friday, April 15, 2022 4:54 PM To: [email protected]Subject: [ServoCAT] Has Anyone Successfully Connected to/Used a ServoCAT ASCOM Driver? ? I can really use help from fellow members of this forum to hopefully solve a vexing problem I have been having trying to connect my Gen 3 SC with Peter’s original ASCOM driver and George’s new beta ASCOM driver.? I have flashed (several times) my SC with the version 7.0C firmware obtained from Gary.? The “V” command in Peter’s SCU utility returns 7.0C. ?I use a Nexus DSC (the original, not the Pro, version).? The serial port on the Nexus is connected to the DSC port on the SC.? A USB cord directly connects the USB/PC port on the SC to a USB port on my computer (and over the many tests I have run, I have used different USB ports and different PCs).? Before attempting to connect to an ASCOM driver, I align the SC/DSC and the red DSC LED on the SC goes from blinking to solid on.? (In addition, gotos initiated from the Nexus place the object in my eyepiece.) ?I set the “Find” parameter on the DSC to “From Planetarium.” I can connect my scope to Peter’s ASCOM driver (through the ASCOM Device Hub) but with only limited functionality.? Peter and I have looked at the Capabilities tab in the ASCOM Device Hub and Peter tells me that my capabilities report is the one he would expect if his driver was connected to an SC with pre-7.0 (legacy) firmware.? In particular, “Can Move Primary Axis” and “Can Move Secondary Axis” both report “False,” when they should both report “True” if connected to an SC with 7.0 firmware. When I connect my scope to Peter’s SCU utility, I get the initial “status” report that Peter describes in his readme file.? While this report indicates that the firmware version is 7.0C, it incorrectly reports that the scope is NOT aligned and NOT tracking when I believe both are true.? Also, S (status) commands receive a “status update is not available” response. I cannot connect to George’s ASCOM driver at all. I get an “operation timed out” error message.? After reviewing the logs of my attempts, George has informed me that his driver is sending my scope commands to obtain certain data from the scope but only gets back some of the data requested (the firmware version) and thus can’t proceed. I have been working with Gary, Peter and George on this problem over the last few weeks with no solution.? We have not yet determined where the problem is originating – my particular SC, the coding for the drivers/SCU utility or something else entirely. So, I am reaching out to forum members who have already tried to control their SC through ASCOM to ask for your experiences in connecting with either or both of the ASCOM drivers.? Additionally, if you have not yet tried to use an ASCOM driver but have an SC with the latest firmware and are willing to try in order to help out, I would be very grateful.? In particular, we would be interested in the answers to the following questions. 1.? Have any of you experienced the same issues as described above and were you able to resolve them? 2.? Have you successfully connected with/utilized George’s driver?? [I used version 0.6.0.0 of George’s driver in all my tests.? I know that George is working on a new version, which will close some open ASCOM conformance issues, but due to my personal time constraints I needed to post this message now.? I don’t think the expected new version will have any impact on my issues.] ? 3.? Can you connect to Peter’s driver through the ASCOM Device Hub?? If so, what are the values of “Can Move Primary Axis” and “Can Move Secondary Axis” on the Capabilities tab? 4.? Does the initial “status” report when you connect to Peter’s SCU utility correctly report the current state of your scope (e.g., alignment and tracking)?? Do you get subsequent status reports when you issue “S” commands? I am going bald with all of the hair I am pulling out over this problem.? Any help anyone can provide would be greatly appreciated!!! Paul
|
Richard, here is the link to v0.7.0.0 of George's ASCOM driver.? https://github.com/ghilios/ASCOM.ghilios.ServoCAT/releases
As noted in my original posting, I would be very interested to learn if you can successfully use it.
Paul
|
Hi Bob.? Thanks for your suggestions.? What I did not disclose in my original post, because it would add unwanted complications, is that what you described was how I initially attempted to connect my scope to my PC -- USB cable from the SC to the USB port on the Nexus and Serial cable between the serial port on the Nexus and the DSC port on the SC.? The Nexus was then connected to the PC by the Nexus Wifi.? All pursuant to the Nexus manual.
The problem with this approach was that both Peter's SCU utility and George's driver reported my ServoCAT firmware version as 6.2S (not 7.0C)!!!? Nobody knew why this was and my email to Serge at Astro Devices requesting guidance was never answered.
Serge has previously provided guidance that an alternate way of connecting a Gen 3 SC to a PC is to run a USB cord between the USB port on the SC and a USB port on the PC.? However, the Serial port on the Nexus must remain connected to the DSC port on the SC so that the system can be aligned and the SC will know where it is pointing.
All the best!
Paul
|
Paul are you saying that the Nexus has two connection to the SC?. Bob ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Paul Abel Sent: Saturday, April 16, 2022 1:20 PM To: [email protected]Subject: Re: [ServoCAT] Has Anyone Successfully Connected to/Used a ServoCAT ASCOM Driver? ? Hi Bob.? Thanks for your suggestions.? What I did not disclose in my original post, because it would add unwanted complications, is that what you described was how I initially attempted to connect my scope to my PC -- USB cable from the SC to the USB port on the Nexus and Serial cable between the serial port on the Nexus and the DSC port on the SC.? The Nexus was then connected to the PC by the Nexus Wifi.? All pursuant to the Nexus manual.
The problem with this approach was that both Peter's SCU utility and George's driver reported my ServoCAT firmware version as 6.2S (not 7.0C)!!!? Nobody knew why this was and my email to Serge at Astro Devices requesting guidance was never answered.
Serge has previously provided guidance that an alternate way of connecting a Gen 3 SC to a PC is to run a USB cord between the USB port on the SC and a USB port on the PC.? However, the Serial port on the Nexus must remain connected to the DSC port on the SC so that the system can be aligned and the SC will know where it is pointing.
All the best!
Paul
|
Bob:
When I am not connected to the PC and am just using the Nexus DSC to control the SC, there are two wired connections between the Nexus and SC:
1.? Nexus USB port to SC USB port
2.? Nexus Serial port to SC DSC port
I have never had any issues in this mode.
These 2 wired connections stay in place when a user tries to connect this Nexus/SC system to a PC using the Nexus wifi capability.? This is the method that Serge contemplated but in my case it produced the weird firmware version.
The back up method for connecting the Nexus/SC system to a PC is to retain the Nexus Serial port to SC DSC port wired connection, but connect the SC USB port to a USB port on the PC.? This means the Nexus USB port remains empty.? This is the method used in the attempts described in my original post.
Regards
Paul
|
Paul, very strange to have two connections sharing the same protocol. Seems like a recipe for disaster. Many moons ago when I had the Gen1 SC I was testing? some beta software that allowed a Windows CE to control the SC. The topography? used was to connect the Win CE device to the PC port on the SC via Bluetooth dongle. The Argo Navis has two serial ports One connected to the SC DSC port using SC protocol. The other to AN serial port was connected toa PC using LX200 protocol. It worked great except the SC would not recognize the GOTO from the PC. It did know the position from the PC and pressing the GOTO on the hand pad would send it there. This method drew the ire of both Garys. Eventually full GOTO was implemented on the Win CE device and even had it forcing the SC tracking satellites… Sort of. Then LG or somebody invented the smartphone and Win CE went away for consumers. If you had a Keyspan USB to serial dongle plugged into the USB on the Nexus how it would react trying the SC protocol first then the LX200 second. I say Keyspan because they are a lot less hassle in the long run. I am running out of ideas to try and just kind throwing thing at the wall. In a week or so I will examine the 40 and give you the topology of it. There have been no issues with it. But it is running probably old firmware on the SC. Bob ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Paul Abel Sent: Saturday, April 16, 2022 4:39 PM To: [email protected]Subject: Re: [ServoCAT] Has Anyone Successfully Connected to/Used a ServoCAT ASCOM Driver? ? Bob:
When I am not connected to the PC and am just using the Nexus DSC to control the SC, there are two wired connections between the Nexus and SC:
1.? Nexus USB port to SC USB port
2.? Nexus Serial port to SC DSC port
I have never had any issues in this mode.
These 2 wired connections stay in place when a user tries to connect this Nexus/SC system to a PC using the Nexus wifi capability.? This is the method that Serge contemplated but in my case it produced the weird firmware version.
The back up method for connecting the Nexus/SC system to a PC is to retain the Nexus Serial port to SC DSC port wired connection, but connect the SC USB port to a USB port on the PC.? This means the Nexus USB port remains empty.? This is the method used in the attempts described in my original post.
Regards
Paul
|
Bob,
Good to hear from you - long time no hear, I hope you are doing well.?
So there are 2 ports on the ServoCAT but they are not the same protocol - they are not even the same purpose. One is for the connection to a DSC which is required to achieve tracking and GOTO capability. The other is a means to allow a PC planetarium program to gather information on where the scope is and to allow a GOTO from that program as well. There's no issues with this - its been in place and increased greatly in functionality and precision ever since I introduced it around 2004 for use with Megastar (thanks to Emil Bonano).?
The latest version of the firmware in the ServoCAT (for Gen2/3 ServoCAT's) when used with the Argo Navis will allow even higher precision tracking including a feature called AutoLOCK that will lock on a point in space with zero accumulated error all-night-long. And a feature that allows tracking of man made satellites. That is all built in to the system now and has been there since it was introduced, this version set, in Jan 2015.?
When Serge developed the improved Nexus he added the PC port connection, it is (mostly) a dumb connection in that it transfers data between the two end points - the ServoCAT (and through it the DSC) and the "PC". In this manner its main benefit was that it did this wirelessly. (He has I believe also intervened in that connection by allowing a GOTO from the Nexus).?
When I get time I'll set something up here to try to help out - currently I'm tied up getting production out the door.?
Gary Myers StellarCAT
------ Original Message ------
Sent: 4/16/2022 8:38:16 PM
Subject: Re: [ServoCAT] Has Anyone Successfully Connected to/Used a ServoCAT ASCOM Driver?
Paul, very strange to have two connections sharing the same protocol. Seems like a recipe for disaster. Many moons ago when I had the Gen1 SC I was testing? some beta software that allowed a Windows CE to control the SC. The topography? used was to connect the Win CE device to the PC port on the SC via Bluetooth dongle. The Argo Navis has two serial ports One connected to the SC DSC port using SC protocol. The other to AN serial port was connected toa PC using LX200 protocol. It worked great except the SC would not recognize the GOTO from the PC. It did know the position from the PC and pressing the GOTO on the hand pad would send it there. This method drew the ire of both Garys. Eventually full GOTO was implemented on the Win CE device and even had it forcing the SC tracking satellites… Sort of. Then LG or somebody invented the smartphone and Win CE went away for consumers. If you had a Keyspan USB to serial dongle plugged into the USB on the Nexus how it would react trying the SC protocol first then the LX200 second. I say Keyspan because they are a lot less hassle in the long run. I am running out of ideas to try and just kind throwing thing at the wall. In a week or so I will examine the 40 and give you the topology of it. There have been no issues with it. But it is running probably old firmware on the SC. Bob ? ? Bob:
When I am not connected to the PC and am just using the Nexus DSC to control the SC, there are two wired connections between the Nexus and SC:
1.? Nexus USB port to SC USB port
2.? Nexus Serial port to SC DSC port
I have never had any issues in this mode.
These 2 wired connections stay in place when a user tries to connect this Nexus/SC system to a PC using the Nexus wifi capability.? This is the method that Serge contemplated but in my case it produced the weird firmware version.
The back up method for connecting the Nexus/SC system to a PC is to retain the Nexus Serial port to SC DSC port wired connection, but connect the SC USB port to a USB port on the PC.? This means the Nexus USB port remains empty.? This is the method used in the attempts described in my original post.
Regards
Paul
|
Hi Gary, It has been a very long time since we have had conversation. Good to hear from you. Congratulation on your upcoming retirement. So, you think you are busy now, wait until you fully retire. I had a request for help out with something the other day and so I popped out my calendar. It came up in quarter year view and it looked like it had caught the measles. Just a head up. Anyway, I have swapped sides of the country and now live not to far from where you once lived. So if you ever want to come back and visit your old stomping round give me a buzz. I did sell the 20 with the SC/AN to a guy that does imaging to use as something to do while subs ran. He could not believe the tracking and accuracy of the SC/AN system. That scope worked flawlessly. I had thought about adding it to my current scope but I guess I waited too long. I now see the reason for the second Nexus connection. So, it is required if you want the Nexus to have GOTO from the Nexus. I think Paul is wanting to control his SC from the PC so he can do some imaging though that scope eventually. With the quantum efficiency of cameras now days, the exposure times are getting very short. He should be able to get some decent data even in Alt/Az. ? Bob Rose ? ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of K9RX - Gary Sent: Sunday, April 17, 2022 5:07 AM To: [email protected]; [email protected]Subject: Re: [ServoCAT] Has Anyone Successfully Connected to/Used a ServoCAT ASCOM Driver? ? Good to hear from you - long time no hear, I hope you are doing well.? So there are 2 ports on the ServoCAT but they are not the same protocol - they are not even the same purpose. One is for the connection to a DSC which is required to achieve tracking and GOTO capability. The other is a means to allow a PC planetarium program to gather information on where the scope is and to allow a GOTO from that program as well. There's no issues with this - its been in place and increased greatly in functionality and precision ever since I introduced it around 2004 for use with Megastar (thanks to Emil Bonano).? The latest version of the firmware in the ServoCAT (for Gen2/3 ServoCAT's) when used with the Argo Navis will allow even higher precision tracking including a feature called AutoLOCK that will lock on a point in space with zero accumulated error all-night-long. And a feature that allows tracking of man made satellites. That is all built in to the system now and has been there since it was introduced, this version set, in Jan 2015.? When Serge developed the improved Nexus he added the PC port connection, it is (mostly) a dumb connection in that it transfers data between the two end points - the ServoCAT (and through it the DSC) and the "PC". In this manner its main benefit was that it did this wirelessly. (He has I believe also intervened in that connection by allowing a GOTO from the Nexus).? When I get time I'll set something up here to try to help out - currently I'm tied up getting production out the door.?
|
Alex:
I am sorry for the delayed response to your post.? I initially tried POTH with Peter's driver, with the same (non-)results.? During our conversations, Peter suggested I try ASCOM Device Hub.
Paul
|
I finally had a night I could try out my own driver! I verified that move axis, syncing, and getting scope status + position worked. I couldn't get GOTO working, but Gary and Peter reminded me I need to have the AN DSC Catalogue set to "Planetarium". I'll try this again as soon as I can, but otherwise the driver worked pretty well. I'm sure there will be a short list of odd issues here and there as it sees real use (for example, I'm sure I may need to increase some timeouts) but if you all report them to me directly I will address them quickly.
|
That’s great George! I haven’t had my scope out in months due to a back injury. I am hoping to do so in a few weeks
toggle quoted message
Show quoted text
On May 1, 2022, at 4:37 PM, George Hilios <ghilios@...> wrote:
?I finally had a night I could try out my own driver! I verified that move axis, syncing, and getting scope status + position worked. I couldn't get GOTO working, but Gary and Peter reminded me I need to have the AN DSC Catalogue set to "Planetarium". I'll try this again as soon as I can, but otherwise the driver worked pretty well. I'm sure there will be a short list of odd issues here and there as it sees real use (for example, I'm sure I may need to increase some timeouts) but if you all report them to me directly I will address them quickly.
|
Here is the latest update on my issue.
I sent the unit back to Gary, who tested the unit while we were on the phone together.? My unit worked as designed, i.e..
1.? My unit connected fine to George's new driver.
2.? Gary connected Peter's driver to the ASCOM Device Hub.?? Under the Capabilities Tab, “Can Move Primary Axis” and “Can Move Secondary Axis” both reported “True” as they should if connected to an SC with 7.0 firmware.
So let me publicly thank Gary for his assistance on this matter.
If anybody has any ideas I will be happy to try them.? I have already tried this process using two different computers, perhaps I will try a third computer??
Paul
|
There is a happy ending to this story.? Several people suggested to me that I try the Argo Navis instead of the Nexus DSC and I did. That solved my problem.? I am now able to connect my scope to both George's and Peter's drivers.? My first night's test revealed a few minor software issues and I have reached out to George and Peter to see how they can be resolved.
Paul
|
bobrose500
Mike