Logiciel de navigation et de routage

AppStore PlayStore
Contact us for support or information: contact@meltemus.com

Connecting using WiFi

Plus d'informations
il y a 18 heures 6 minutes #3192 par SkipperDan
Connecting using WiFi a été créé par SkipperDan
Hello, I am using a Digital Yacht WLN30 multiplexer. I have it connected to a Clipper Marine wind instrument. I also have it connected to a Standard Horizon GX2410GPS with AIS. I get data with the Clipper Mrine but not the GPS from the radio. I cannot check the AIS as I am not near a marina at the moment. I am not sure if I need to use more than one port in the setup. In the setup box of the multiplexer I only get data from the Wind. Nothing from the radio. I have a request in to Standard Horizon and Digital yacht. I just wanted to make sure I have the port set correctly in QtVlm. see attached.

Thank you, Daniel 

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 1 heure 32 minutes #3194 par Synapse Navigation
Réponse de Synapse Navigation sur le sujet Connecting using WiFi
Hello,
The problem is probably on the VHF side. This gateway is just a multiplexer collecting the NMEA0183 data. But, your VHF seems not to be able to send the AIS data in NMEA0183. Check its doc ( www.standardhorizon.com/Files/7B72F1ED-1...7N260_2407G-AS-1.pdf ) in §8.5.1, the position data can be emitted, but nothing about the AIS. With the NMEA2000 protocol, the AIS can be emitted (§15.5), but this protocol cannot be used with the gateway (and not directly to qtVlm).
If you receive the info from the windvane on qtVlm, you are connected to the gateway, so your connection is ok, and you don't need another one.
So it seems that you cannot receive the info about the AIS, but you should receive the GPS infos. Check in the VHF menu, if you emit it correctly (doc §19.9) (hardware connection and baudrate).
Good Luck !
Formations sur qtVlm
Services sur logiciels et materiel de navigation...
=> synapsenavigation.fr

Connexion ou Créer un compte pour participer à la conversation.

Temps de génération de la page : 0.182 secondes