Incredible - I wasn’t aware of Eagle 4 being supported by Viking. The more I read on Voyager, the more I like it ! Thank you Leonardo and teams for this great automation software.
Allow me one question, if I may : I am about to have my roll-off observatory from Dome Parts installed very soon https://www.astrogfk.com/roll-off/, which comes with as so-called “semi automatic drive system / USB version”.
I was told by Dome Parts : “your control PC (Eagle) for your mount will have the relay control app (or your own: there is a free SDK)”. If I am not wrong, I could then remotely control the observatory via Eagle. What about Vikings ? I think I would need it, right ?
Thank you for your kind support. Wish you a “sunny day”.
seems your dome system must be used with relay so you can use Viking that manage a dedicated I/O cards or Eagle realy out. If you dont use Viking you must use self made script from you.
Hopefully a simple question or a configuration issue. I have been using the Eagle ascom driver to report sky quality in the observing conditions widget. It updates without issue. I recently added a ECCO 2 and configured the primalucelab ascom.pll observing conditions driver so that the other enviormental conditions (temp, hum, dewpoint, etc) show within the widget. When I connect to my setup these values show in the widget, however the temp, hum, dewpoint do not seem to update during the night. I can see the current values on the Eagle Manager screen but the widget has old values. I am using Voyager 2.3.2b. Any ideas?
If you use VIking, VIking send directly to voyager all the data.
If you using ASCOM driver for Observing Conditions, Voyager use the same code shared for all the drivers of this type so … if you dont see updating the data you must check the driver settings and connections , if you have the right version and if not solve please ask support to PrimaLuceLab about the driver.
Thanks for the reply Leo,
I checked the driver many times. When I configure the driver in voyager configuration settings the driver opens with the correct values from ECCO and updates values as I watch it. When I connect to my equipment in Voyager the values load in the observing conditions widget but the only value that updates is the Sky Quality. The other values like temp, hum, and dew point remain static.
I have the latest from PrimaluceLab but will ask them too.
I have also dome part RoR operational. I have the semi it has two buttons switches one for opening and one for closing the roof. I use two relays which i connected parallel on this switches. If you are able to do that via viking and one of the supported boxes then you are done. I use PI with 4 relay head. in have a alpace driver to control the roof. dont hasitate to drop me PM
what is in this thread is related to VIking. You are using ASCOM observing conditions driver developed from PrimaLuceLab so if you want to check if the code for all ASCOM observing conditions driver work fine in Voyager use the simulator. If you will not see changing to data please open a support ticket to Voyager otherwise the only solution is to ask support to PrimaLuceLab
For what about Eagle LE, I dont have tested with Viking (i received for development the Eagle 3/4 on all versions) so I cannot say if its real compatible, on the paper yes. Something to ask directly to PrimaLuceLab, depends on Eagle Manager version is installed inside.
Eagle Manager 4.2 is installed on the Eagle LE. This latter is exactly the same as the Eagle 4 except it doesn’t have the eye sensor as well the GPS - other than than “copy-pasted” product.
I presume it should work. I am probably doing something wrong. For the IP address, I am using the IPV4 address - not the official 192.168.137.1 (I have tried both with port 3389). Any suggestions / ideas ?
You must know the IP of your Eagle if you use viking in LAN , otherwise if is local the IP is 127.0.0.1 or localhost. Be sure you have the Firewall opened and the manager running.
When using the Eagle’s own wifi (Access point), the generic IP address is 192.168.0.1. I am not using it.
To remotely control it, I have decided to use my existing wifi network - as a result the IP address to be used in order to remotely control the Eagle is different than the generic one mentioned above.
In addition, my Eagle is also wired via an Ethernet cable. That’s where I am a bit confused. I have IPV4 address for the ethernet connexion as well as for the wifi. Which one should I use ?
As for the default port, the manual recommends 3389. Whenever I am trying to connect viking, I am getting a error “cannot receive data from”… etc.
Only you can know where is Viking and where is Eagle, use the IP of network that connect the 2 PCs.
If you start Application Server on Voyager you have in Application Server monitor all the IP in the PC (WEB Dashboard Setup - Voyager Wiki) , this can help to understand and match it to the IP in VIking PC.
Please, use official support channel if you want help…
