Logiciel de navigation et de routage

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

TWS & PPC Errors

Plus d'informations
il y a 1 jour 1 heure #3285 par MattiMelte
TWS & PPC Errors a été créé par MattiMelte
hello together,
i have an issue with some instruments on my qtvlm. As you can see from the image attached the TWS and AWS are almost the same but, in reality they are not by far (as it is calculated and displayed  on my garmin Wind Bundle 52). To calculate the "true" data, the AIS - which is trasmitting data via UDP to the pc with qtvlm - has both GPS data and the log data (Garmin).
Can someone tell me why?
In addition, why is the PPC data completely dead?
I also attached a log of the NMEA data.
thank you in advance for the support
Best
Matteo

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

Plus d'informations
il y a 15 heures 56 minutes - il y a 14 heures 22 minutes #3286 par Synapse Navigation
Réponse de Synapse Navigation sur le sujet TWS & PPC Errors
Hello,
Your STW (Speed Through Water) is wrong (or you are sailing a rocket). On the screenshot it is 73 Knots. There is something wrong that can impact the calculation of the TWS, TWA, and to compare to the polar (PPC ...). You should have a look at your sensor ...

Formations sur qtVlm
Services sur logiciels et materiel de navigation...
=> synapsenavigation.fr
Dernière édition: il y a 14 heures 22 minutes par Synapse Navigation.

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

Plus d'informations
il y a 14 heures 10 minutes - il y a 14 heures 9 minutes #3287 par maitai
Réponse de maitai sur le sujet TWS & PPC Errors
Hello,
First thing I see is that you have a really big issue with STW (Speed on Water), and actually you are receiving that:
$TIVHW,,T,,M,1273.90,N,2359.26,K*4F

1273.90 kts on water that is really fast :)

STW instruments shows only the last digits since such a huge number is not at all expected.

Concerning wind we receive
$TIMWV,293.61,R,4.81,M,A*21
which is AWD/AWS (4.81) since it is with "R"

and

$TIMWD,,T,,M,9.31,N,4.79,M*58
which is TWS (4.79 kts). Note that there is no TWD value, and therefore qtVlm is not able to calculate TWA

PPC does not show anything because 1) qtVlm was unable to read or calculate TWA and 2) that would give a too big number anyway.

So the conclusion is that your system sends both AWS and TWS but with the same value, and qtVlm just shows that. There is a big issue with VHW message, and it is also not normal to never receive TWD or TWA
What kind of navigation central is it ?
Dernière édition: il y a 14 heures 9 minutes par maitai.

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

Plus d'informations
il y a 13 heures 25 minutes #3288 par maitai
Réponse de maitai sur le sujet TWS & PPC Errors
To be more precise, it is not normal to receive TWS and not TWD or TWA. If TWS/TWA/TWD are all not received, qtVlm will calculate them based on AWA/AWS, but the case where only TWS is present is not covered because that would ignore the TWS received.

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

Plus d'informations
il y a 12 heures 57 minutes #3289 par MattiMelte
Réponse de MattiMelte sur le sujet TWS & PPC Errors
Hello and thanks for the analysis. The wind and log values are provided by a Garmin wind bundle 52 which apparently works well since the data on it dedicated displays make sense. Such data are transferred via nmea2000 to a em-trak AIS which is then sending them via high speed nmea0183 to a wifi antenna (yakker) which is in turn sending them via UDP to my pc with Qtvlm.
I don't know what is going wrong. I could understand if all data from the Garmin are somehow not received by qtvlm, but that part of them are wrong....

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

Plus d'informations
il y a 12 heures 55 minutes #3290 par maitai
Réponse de maitai sur le sujet TWS & PPC Errors
I would suspect the conversion between NMEA2000 and NMEA0183
Les utilisateur(s) suivant ont remercié: MattiMelte

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

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