Skip to content
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

Incorrect/rogue parsing in StaticDataReportPartAMessage #28

Closed
chelliwell opened this issue Jan 28, 2020 · 2 comments
Closed

Incorrect/rogue parsing in StaticDataReportPartAMessage #28

chelliwell opened this issue Jan 28, 2020 · 2 comments

Comments

@chelliwell
Copy link
Contributor

Part A shouldn't be looking for 'Spare' - the Part A message ends with ShipName @ 160 bits.
[Apologies for not submitting a pull request, but I'm no expert on Git, so you might not thank me for trying lol. I think in this case it's just a one-line deletion]

@chelliwell
Copy link
Contributor Author

Suitable test case:
!AIVDM,1,1,,B,H3`u5VA=VliDp@D000000000000,2*35

@chelliwell
Copy link
Contributor Author

Pull request submitted: #32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants