Hi Robert,
got a problem with the Ascom OC driver with Voyager and NINA and firmware 139-03, you can find the log attached.
The SM driver looks good.
I also tryed the OCH driver and have all the value to zero.
the Voyager and OC hub has NOT been tested or supported, and you will find that it really appears nowhere in the documentation etc.
The native ASCOM OC driver that is provided works with NINA, but I am not sure where to start with your issue. Never used Voyager (and know nothing about it) and its safe to say I never will, That is not any opinion re Voyager rather my personal situation,
I just cannot deal with all other sorts of complexities. Thanks for posting the logs and I will go throught them to see if anthing stands out, Isuspect that I will not get the infor I need though, perhaps the NINA logs would prove helpful
Regards
Robert
Last edit: brownrb 2024-10-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can only talk about the latest version of mySQM+ 139-03
Some revisons ago the tcpip server moved from port 2121 to 2020 which is now the default
The logs reveal that a connection cannot be made at that address and that port number,
16:02:24.734 Connected 192.168.1.60
16:02:24.734 Connected Port
16:02:24.734 Connected 2121 <<<< should be 2020
Is 192.168.1.60 the address of the controller?
Open a web broswer and enter the ip address and the port of the Management Server
On the Servers page, check the TCPIP Server.
It should be running
It should be port 2020 (if you are running the latest firmware)
IP has to be the same
Port has to be the same
So 2121 does match 2020. Has to be the same.
Somehow you have to resolve this.
If the Management Server says it is running on 2020
then
stop the tcpip server, change port to 2121 then restart the tcpip server
no need to change any of the ascom driver details
OR
leave the tcpip server port at 2020 and make sure its running
change the port in the ascom driver properties to use 2020 instead of 2121
Regards
Robert
Last edit: brownrb 2024-09-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert,
There seems to be some problem with the Ascom dirvers, after some time both Voyager and NINA lose the connection, I attach the OCH and NINA logs.
Please let me know if it's some confguration error or something else.
The problem occurs both when using the mysqm+ and OCH drivers
Hi Marco
I dont think it would be a problem with the configuration or drivers.
Are you running this through a hub? It has never been tested by me as I dont use them. It appears that the hub does not work (the NINA log is full of OSC Hub error messages.
Is there a reason why you are using a hub?
The logs were not that helpful, An error occurred after about 10m, during that time little if anything was written to the Nina log. Before that and after that there are heaps of errors. But there is no obvious reason why.
The ASCOM OCH log must be from the Hub? The mySQM+ OC driver writes to its own logfile but you did not post that?
In general, dropped connections are more about quality of cables etc,
Please let me know the following
How long is the USB cable between computer and hub?
How long is the USB cable between hub and mySQM+ Controller?
Is the hub and mySQM+ controller powered from the same power supply.
Are you using 12V power to the controller?
Are you using bluetooth?
A USB cable extension?
A powered USB cable?
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert,
I have to use the hub because NINA and Voyager get stuck if I use Enviromental Safety Monitor and MySQM OSC drivers directly.
Anyway i found the problem.
I use Remote Desktop to operate on my Astronomy PC and, if I close the connection, both NINA and Voyager, and also the mysqm's windows app lost the connection with the device.
If I use other programs like teamviewer or anydesk there's no connection problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert,
got a problem with the Ascom OC driver with Voyager and NINA and firmware 139-03, you can find the log attached.
The SM driver looks good.
I also tryed the OCH driver and have all the value to zero.
Last edit: Marco Formenton 2024-09-25
Hi
the Voyager and OC hub has NOT been tested or supported, and you will find that it really appears nowhere in the documentation etc.
The native ASCOM OC driver that is provided works with NINA, but I am not sure where to start with your issue. Never used Voyager (and know nothing about it) and its safe to say I never will, That is not any opinion re Voyager rather my personal situation,
I just cannot deal with all other sorts of complexities. Thanks for posting the logs and I will go throught them to see if anthing stands out, Isuspect that I will not get the infor I need though, perhaps the NINA logs would prove helpful
Regards
Robert
Last edit: brownrb 2024-10-02
Ok, had a look at the logs
I can only talk about the latest version of mySQM+ 139-03
Some revisons ago the tcpip server moved from port 2121 to 2020 which is now the default
The logs reveal that a connection cannot be made at that address and that port number,
16:02:24.734 Connected 192.168.1.60
16:02:24.734 Connected Port
16:02:24.734 Connected 2121 <<<< should be 2020
Is 192.168.1.60 the address of the controller?
Open a web broswer and enter the ip address and the port of the Management Server
On the Servers page, check the TCPIP Server.
It should be running
It should be port 2020 (if you are running the latest firmware)
IP has to be the same
Port has to be the same
So 2121 does match 2020. Has to be the same.
Somehow you have to resolve this.
If the Management Server says it is running on 2020
then
stop the tcpip server, change port to 2121 then restart the tcpip server
no need to change any of the ascom driver details
OR
leave the tcpip server port at 2020 and make sure its running
change the port in the ascom driver properties to use 2020 instead of 2121
Regards
Robert
Last edit: brownrb 2024-09-28
Hello Robert,
you are right, the problem was the wrong port.
With 2020 port all works fine.
Sorry for my mistake
here some screenshots
Thank you for the help
i use the driver directly not the hub
The OC driver was tested against Conform U and I posted the Conform test logs,
https://sourceforge.net/projects/mysqmproesp32/files/APPLICATIONS/ASCOM%20Observing%20Conditions/Conform%201745.41839.txt/download
Regards
Robert
Hello Robert,
There seems to be some problem with the Ascom dirvers, after some time both Voyager and NINA lose the connection, I attach the OCH and NINA logs.
Please let me know if it's some confguration error or something else.
The problem occurs both when using the mysqm+ and OCH drivers
Regards
Marco
Hi Marco
I dont think it would be a problem with the configuration or drivers.
Are you running this through a hub? It has never been tested by me as I dont use them. It appears that the hub does not work (the NINA log is full of OSC Hub error messages.
Is there a reason why you are using a hub?
The logs were not that helpful, An error occurred after about 10m, during that time little if anything was written to the Nina log. Before that and after that there are heaps of errors. But there is no obvious reason why.
The ASCOM OCH log must be from the Hub? The mySQM+ OC driver writes to its own logfile but you did not post that?
In general, dropped connections are more about quality of cables etc,
Please let me know the following
How long is the USB cable between computer and hub?
How long is the USB cable between hub and mySQM+ Controller?
Is the hub and mySQM+ controller powered from the same power supply.
Are you using 12V power to the controller?
Are you using bluetooth?
A USB cable extension?
A powered USB cable?
Regards
Robert
Hi Robert,
I have to use the hub because NINA and Voyager get stuck if I use Enviromental Safety Monitor and MySQM OSC drivers directly.
Anyway i found the problem.
I use Remote Desktop to operate on my Astronomy PC and, if I close the connection, both NINA and Voyager, and also the mysqm's windows app lost the connection with the device.
If I use other programs like teamviewer or anydesk there's no connection problem.