- Messages : 15
- Remerciements reçus 0
HELP!! AWS vs GWS vs TWS
- MattiMelte
- Auteur du sujet
- Hors Ligne
- Nouveau membre
-
Moins
Plus d'informations
il y a 2 jours 7 heures - il y a 2 jours 7 heures #3728
par MattiMelte
Réponse de MattiMelte sur le sujet HELP!! AWS vs GWS vs TWS
thanks again for your support. AWA is present (bottom part of the image, sorry not the best image quality) and looks good. Attached you find the requested log. thanks
Dernière édition: il y a 2 jours 7 heures par MattiMelte.
Connexion ou Créer un compte pour participer à la conversation.
- maitai
- Hors Ligne
- Administrateur
-
Moins
Plus d'informations
- Messages : 1152
- Remerciements reçus 15
il y a 2 jours 5 heures #3729
par maitai
Réponse de maitai sur le sujet HELP!! AWS vs GWS vs TWS
The problem from your log is clear:
Your system sends a very bad MWD message, with TWA/TWD empty and TWS set at the same value as AWS received in MWV message.
I would either investigate why your system sends a faulty MWD message or filter out MWD message in NMEA settings in order to let qtVlm do the normal calculations in that case.
Your system sends a very bad MWD message, with TWA/TWD empty and TWS set at the same value as AWS received in MWV message.
I would either investigate why your system sends a faulty MWD message or filter out MWD message in NMEA settings in order to let qtVlm do the normal calculations in that case.
Connexion ou Créer un compte pour participer à la conversation.
- MattiMelte
- Auteur du sujet
- Hors Ligne
- Nouveau membre
-
Moins
Plus d'informations
- Messages : 15
- Remerciements reçus 0
il y a 1 jour 13 heures #3730
par MattiMelte
Réponse de MattiMelte sur le sujet HELP!! AWS vs GWS vs TWS
Connexion ou Créer un compte pour participer à la conversation.
- maitai
- Hors Ligne
- Administrateur
-
Moins
Plus d'informations
- Messages : 1152
- Remerciements reçus 15
il y a 1 jour 13 heures #3731
par maitai
Réponse de maitai sur le sujet HELP!! AWS vs GWS vs TWS
No this is not related. According to the NMEA specification MWD should contain GWS/GWD but in practice this is almost never the case and it contains TWS/TWD.
Your problem is that your MWD is broken. It contains only TWS and it should also contain TWD or TWA, plus the TWS it sends is wrong:
$TIMWD,,T,,M,10.34,N,5.32,M*6B
Your problem is that your MWD is broken. It contains only TWS and it should also contain TWD or TWA, plus the TWS it sends is wrong:
$TIMWD,,T,,M,10.34,N,5.32,M*6B
Connexion ou Créer un compte pour participer à la conversation.
- MattiMelte
- Auteur du sujet
- Hors Ligne
- Nouveau membre
-
Moins
Plus d'informations
- Messages : 15
- Remerciements reçus 0
il y a 1 jour 13 heures #3732
par MattiMelte
Réponse de MattiMelte sur le sujet HELP!! AWS vs GWS vs TWS
But as long as the SW uses the boat speed (the stuck log) to calculate the true wind values of course the values are broken. I need the SW to use the GPS speed to calculate ground wind ones. Sure that that button does not do exactly this? If not, what is it for? Thank you for your patience:)
Connexion ou Créer un compte pour participer à la conversation.
- maitai
- Hors Ligne
- Administrateur
-
Moins
Plus d'informations
- Messages : 1152
- Remerciements reçus 15
il y a 1 jour 13 heures #3733
par maitai
Réponse de maitai sur le sujet HELP!! AWS vs GWS vs TWS
As I said it is completely unrelated to your problem. Your problem is that your receive bad MWD message, whether it is supposed to contain GW or TW data is another story.
Because qtVlm "thinks" it has a correct TWS in MWD message it does not recalculate it and uses what is given.
Filter out MWD message in NMEA settings and qVlm will calculate TWS/TWD/TWA based on COG/SOG, which is of course a fallback when no HDG/STW is known.
Because qtVlm "thinks" it has a correct TWS in MWD message it does not recalculate it and uses what is given.
Filter out MWD message in NMEA settings and qVlm will calculate TWS/TWD/TWA based on COG/SOG, which is of course a fallback when no HDG/STW is known.
Connexion ou Créer un compte pour participer à la conversation.
Temps de génération de la page : 0.120 secondes

