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
I am trying to decode the ws://192.168.10.1/gdl90 WebSocket messages from Javascript App in iOS safari (ours is a PWA). It seems Stratux does not set message type to Binary so they end up as "String" in iOS Safari client. After that its difficult to figure just how to decode this string - I have tried various ways including TextEncoder but data does not come out correct.
It would have been nice if message type was binary because browsers can then receive it as binary. I am not asking to change this at this point, but just want to know how to decode a byte[] sent via Go Websocket that ends up as string in javascript WebSocket client! To me it seems incompatible
Any ideas ?
The text was updated successfully, but these errors were encountered:
femski
changed the title
Help. What is encoding for GDL90 messages over WebSocket
Help. What is the encoding for GDL90 messages over WebSocket
Aug 7, 2019
Hi, Did you resolve this GDL90 decoding problem? If I do a base64 decode the data doesn't match the message description for a GDL90 heartbeat message lets say.
Thanks,
Steve
Stratux version:
Stratux config:
SDR
GPS
type:
AHRS
power source:
usb cable:
EFB app and version: (e.g., WingX Pro7 8.6.2)
I am the developer of AvNav so its about AvNav
EFB platform: (e.g., iOS 9.2) iOS and Android
EFB hardware: (e.g., iPad Mini 2) Mini, iPAD etc
Description of your issue:
I am trying to decode the ws://192.168.10.1/gdl90 WebSocket messages from Javascript App in iOS safari (ours is a PWA). It seems Stratux does not set message type to Binary so they end up as "String" in iOS Safari client. After that its difficult to figure just how to decode this string - I have tried various ways including TextEncoder but data does not come out correct.
It would have been nice if message type was binary because browsers can then receive it as binary. I am not asking to change this at this point, but just want to know how to decode a byte[] sent via Go Websocket that ends up as string in javascript WebSocket client! To me it seems incompatible
Any ideas ?
The text was updated successfully, but these errors were encountered: