-
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
failed parse some MessageType5 data , it throw 'MissingMultipartMessageException' #85
Comments
Like the message indicates, it misses the second part of the multipart message. |
I use other way then no error report, the code below:
|
@mihermans is totally right. The error is pretty clear: You are trying to decode a multi fragment message. Such messages are too big to fit into the 82 character maximum of NMEA 0183 messages. Therefore, long messages are fragmented into multiple fragments. In order to decode a fragmented message, all fragments need to be assembled before the message is decoded. Imagine that you want to send a very big package to someone. Your package is too big to fit into a single parcel. Therefore, you split the package into multiple smaller packages. Each package can then be shipped in its own parcel. The receiver of the packages then needs to receive all packages before he can reassemble the original package. Otherwise the package would be incomplete. In your case the message
This may not raise an exception. But it is still wrong. The decoded message is invalid, because half of it is missing. |
so then, how to solve this issue ? sorry maybe my question is stupid :-| |
This is not an issue. This is expected behavior. You need to pass both parts the decode function - not just the first |
got it... thanks all |
face this problem, the decode.py code logic bellow:
while parse string :
!AIVDM,2,1,6,A,55MwgS`00001L@?;OK80b022220l1@:44vT4,0*6B
it throw exception:
what is the reason ?
if I comment the check logic , then all things works fine , anyone can give tip for this case ?
The text was updated successfully, but these errors were encountered: