-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Furuno messages incomplete #171
Comments
It appears there may be differences in the versioning of NMEA messages. I am not certain how to tackle that.. Also, I have been unable to find documentation for the Based on these implementations, the
This might help with reverse engineering the |
Thanks,
I'll see if I can reach-out to a contact that may have this information. If so I'll see If I can make a pull request. |
@JoepdeJong
I assume your changes have made it into version 1.19.0?
If so it seems that your addition of the furuno messages isn't all encompassing. The fields don't seem to be fully defined. Based on my webcrawling the values and limits are based on:
manual
Attitude message:
ATT (Proprietary): incl. yaw, pitch roll data [0, 359.9], [-90, 90], [-90, 90]
$PFEC,GPatt,xxx.x,+xx.x,+xx.xhh (Ver. 2.0)
sample: "$PFEC,GPatt,194.483,-0.963,17.17258"
Heave message:
HVE (Proprietary): incl. heave data unit in m [-99.999, 99.999], A/V
$PFEC,GPhve,xxx.x,Ahh (Ver. 2.1)
"$PFEC,GPhve,-0.114,A16",
Additionally I'm still looking for a description of the IMU message GPimu
"$PFEC,GPimu,0.210,0.056,-0.023,0,-0.654,0.448,0.486,0,0*42",
I'm planning on 'reverse engineering' GPimu, but that will require some vessel data analysis and might take some time.
The text was updated successfully, but these errors were encountered: