-
Notifications
You must be signed in to change notification settings - Fork 64
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
Encoding large (Type 5) messages causes NMEA max message length to exceed 82 characters. #81
Comments
@bgercken Thank you for bringing this up. I will look at this but as soon as time allows. But it might take a couple of days. |
No hurry on my part. Thank you very much. |
Could you provide me some example that led to this issue? I am not able to reproduce the described behavior. |
Below is output for encoding the following data.
UPDATE: actually 81 is too long. When you append the NMEA terminator it exceeds the max sentence length. |
I had closed this but it still appears to be an issue. Updated test fails:
|
Thank you. I am pretty sure that I forgot to include the final |
You were right. The max payload length should be set to 60 and not 61. The docstring of the relevant method actually mentions this: This method takes care of splitting large payloads (larger than 60 characters)
into multiple sentences. With a total of 80 maximum chars excluding end of line
per sentence, and 20 chars head + tail in the nmea 0183 carrier protocol, 60
chars remain for the actual payload. But then the implementation sets |
Should be fixed with version 2.2.1 |
Was running into an issue in encode.py ais_to_nmea_0183 where it was causing messages to exceed the NMEA max size.
On line 54 (in encode.py) I changed max_len to 60, which seems to have resolved it.
Thanks.
The text was updated successfully, but these errors were encountered: