How does one go about troubleshooting or debugging a problem when the mount becomes unresponsive for no apparent reason:
Here is an example. Commands are issued, and there is a response, then suddenly, no responses at all:
SCOPE 7000.078862 sec : CMD <:GR#>
SCOPE 7000.100635 sec : RES <18:19: 4.1>
SCOPE 7000.100714 sec : VAL [18.3178]
SCOPE 7000.100732 sec : CMD <:GD#>
SCOPE 7000.121625 sec : RES <-13*46:55>
SCOPE 7000.121703 sec : VAL [-13.7819]
DEBUG 7000.121721 sec : CMD: <:pS#>
DEBUG 7000.137620 sec : RES: <East>
SCOPE 7001.138734 sec : CMD <:GR#>
SCOPE 7001.160656 sec : RES <18:19: 4.1>
SCOPE 7001.160734 sec : VAL [18.3178]
SCOPE 7001.160753 sec : CMD <:GD#>
SCOPE 7001.181639 sec : RES <-13*46:55>
SCOPE 7001.181715 sec : VAL [-13.7819]
DEBUG 7001.181733 sec : CMD: <:pS#>
DEBUG 7001.197771 sec : RES: <East>
SCOPE 7002.198163 sec : CMD <:GR#>
SCOPE 7002.219656 sec : RES <18:19: 4.1>
SCOPE 7002.219732 sec : VAL [18.3178]
SCOPE 7002.219749 sec : CMD <:GD#>
SCOPE 7002.240649 sec : RES <-13*46:55>
SCOPE 7002.240724 sec : VAL [-13.7819]
DEBUG 7002.240742 sec : CMD: <:pS#>
DEBUG 7002.255794 sec : RES: <East>
SCOPE 7003.257038 sec : CMD <:GR#>
SCOPE 7004.258074 sec : CMD <:GR#>
SCOPE 7005.259371 sec : CMD <:GR#>
SCOPE 7006.260306 sec : CMD <:GR#>
SCOPE 7007.261391 sec : CMD <:GR#>
SCOPE 7008.262453 sec : CMD <:GR#>
SCOPE 7009.263522 sec : CMD <:GR#>
SCOPE 7010.264588 sec : CMD <:GR#>
...
The mount was tracking normally, and the hand controller responding as expected.
I stop KStars, and start it again, fire up INDI. The mount responds, then suddenly stops responding ...
SCOPE 25.484658 sec : CMD <:GR#>
SCOPE 25.506454 sec : RES <18: 4:57.0>
SCOPE 25.506532 sec : VAL [18.0825]
SCOPE 25.506549 sec : CMD <:GD#>
SCOPE 25.527434 sec : RES <-24*22: 0>
SCOPE 25.527497 sec : VAL [-24.3667]
DEBUG 25.527538 sec : CMD: <:pS#>
DEBUG 25.543438 sec : RES: <East>
SCOPE 26.544536 sec : CMD <:GR#>
SCOPE 26.567455 sec : RES <18: 4:57.1>
SCOPE 26.567522 sec : VAL [18.0825]
SCOPE 26.567535 sec : CMD <:GD#>
SCOPE 26.588432 sec : RES <-24*22: 0>
SCOPE 26.588454 sec : VAL [-24.3667]
DEBUG 26.588495 sec : CMD: <:pS#>
DEBUG 26.603454 sec : RES: <East>
SCOPE 27.604553 sec : CMD <:GR#>
SCOPE 28.605734 sec : CMD <:GR#>
SCOPE 29.606915 sec : CMD <:GR#>
SCOPE 30.608086 sec : CMD <:GR#>
SCOPE 31.609368 sec : CMD <:GR#>
SCOPE 32.611917 sec : CMD <:GR#>
SCOPE 33.613110 sec : CMD <:GR#>
SCOPE 34.614300 sec : CMD <:GR#>
SCOPE 35.615484 sec : CMD <:GR#>
SCOPE 36.257941 sec : <setObjectRA>
SCOPE 36.257980 sec : CMD <:Sr 18:37.4#>
SCOPE 36.616025 sec : CMD <:GR#>
SCOPE 37.617186 sec : CMD <:GR#>
SCOPE 38.617642 sec : CMD <:GR#>
SCOPE 39.618781 sec : CMD <:GR#>
SCOPE 40.620084 sec : CMD <:GR#>
SCOPE 41.621275 sec : CMD <:GR#>
...
The only thing I did was connect the laptop to an external booster battery pack after its internal battery was about to run out.
I was suspecting that the power cable and USB cable were overlapping and hence noise or interference. But Why does it work then not work? If it was a USB problem, there would be an error, right?
Any ideas appreciated.
