You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting up 2 different Windows computers with AIS data connections ran into an issue where SignalK data connection worked on one computer but not the other computer
Computer 1: Server -> Data Connection setup w/ NEMA 0183 Source: TCP Client with Host and Port is showing AIS vessels. If I add SignalK Data Type with Source TCP and enter the host and port I get Server Log Messages
get these continual messages
Aug 17 23:50:28 Could not parse JSON:!AIVDM,1,1,,A,15Mw>PP000o>RJvK0DnWvoJl0H@c,0*4B
Computer 2: Server -> Data Connection setup is using SignalK w/ TCP, Host and Port and is working fine, not getting any unable to parse messages.
The text was updated successfully, but these errors were encountered:
As Scott said the error message means that you are expecting Signal K but receiving NMEA 0183.
But I have to say your description of your setup is really ambiguous: host and port may be obvious to you, but I have no idea whose host snd port they are. And where is your data coming from in the first place?
Describing explicitly what you have and what you are trying to achieve makes helping a lot easier and thus getting the problem solved much more probable.
Setting up 2 different Windows computers with AIS data connections ran into an issue where SignalK data connection worked on one computer but not the other computer
Computer 1: Server -> Data Connection setup w/ NEMA 0183 Source: TCP Client with Host and Port is showing AIS vessels. If I add SignalK Data Type with Source TCP and enter the host and port I get Server Log Messages
get these continual messages
Aug 17 23:50:28 Could not parse JSON:!AIVDM,1,1,,A,15Mw>PP000o>RJvK0DnWvoJl0H@c,0*4B
Computer 2: Server -> Data Connection setup is using SignalK w/ TCP, Host and Port and is working fine, not getting any unable to parse messages.
The text was updated successfully, but these errors were encountered: