View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002114 | SkyChart | 1-Software | public | 19-04-08 09:46 | 19-04-08 17:16 |
| Reporter | Emchenko Boris | Assigned To | Patrick Chevalley | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | PC | OS | Windows | OS Version | 10 64bit |
| Product Version | 4.1 SVN | ||||
| Target Version | 4.2 | Fixed in Version | 4.1 SVN | ||
| Summary | 0002114: Closing (normally or abnormally) of ASCOM driver for Sitech mount will always leed to losing control of CdC | ||||
| Description | Closing (normally or abnormally) of ASCOM driver for Sitech mount will always leed to losing control of CdC. At first, CdC will displaying dialog "Error: An existing connection was forcibly closed by remote host" and after pressing OK infinitely will be displayed dialog: "Error: no connection could be made because the target machine actively refused it 127.0.0.1:8000" Clicking ok will lead to dispaling it again with no chance to use other interface elemement (even CdC closing) | ||||
| Steps To Reproduce | How to reproduce: 1) Closing ASCOM Sithech driver (any version) normally or abnormally 2) CdC will displaying dialog "Error: An existing connection was forcibly closed by remote host: 3) after pressing OK infinitely will be displayed dialog: "Error: no connection could be made because the target machine actively refused it 127.0.0.1:8000" 4( clicking ok will lead to dispaling it again with no chance to use other interface elemement (even CdC closing) | ||||
| Additional Information | Link to ASCOM Sitech driver (no need to have appropriate hardware to test, works without connection): http://siderealtechnology.com/SiTechSetup094N.exe | ||||
| Tags | Telescope control | ||||
|
|
All this error messages are from the SiTech ASCOM driver when it loss the connection with the control software. But the problem is because the SiTech ASCOM driver do not report the connection is closed. After closing the control program the ASCOM driver still report the Connected property is True, so CdC continue to try to read the telescope coordinates. I make a change that protect CdC from this bad behavior. Now it close the connection after the first failed attempt to read the telescope position. This can be annoying in case of temporary condition but better than this endless loop. https://github.com/pchev/skychart/commit/eb29c785824245bc68139abbc5651d2f6bcc2612 |
|
|
"After closing the control program the ASCOM driver still report the Connected property is True" If you want you can report this bug to SiTech. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 19-04-08 09:46 | Emchenko Boris | New Issue | |
| 19-04-08 09:46 | Emchenko Boris | Tag Attached: Telescope control | |
| 19-04-08 17:14 | Patrick Chevalley | Assigned To | => Patrick Chevalley |
| 19-04-08 17:14 | Patrick Chevalley | Status | new => resolved |
| 19-04-08 17:14 | Patrick Chevalley | Resolution | open => fixed |
| 19-04-08 17:14 | Patrick Chevalley | Fixed in Version | => 4.1 SVN |
| 19-04-08 17:14 | Patrick Chevalley | Target Version | => 4.2 |
| 19-04-08 17:14 | Patrick Chevalley | Note Added: 0005585 | |
| 19-04-08 17:16 | Patrick Chevalley | Note Added: 0005586 |
