-
Notifications
You must be signed in to change notification settings - Fork 102
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
Additional UDP output #513
Comments
Update: I have looked into this and am working on it. Will create a PR once completed |
You can also connect to TCP port 14570 where the JSON data will be pushed out periodically (once per second for sonde data), maybe this is an option instead of adding yet another way of communicating data? (This is also the port I am using for the Android app) |
I did look at the TCP option with iOS and thought it might be a bridge too far in terms of the connection that has to be maintained. Anyway, I do have it sending the sonde2json data out on a UDP multicast address. One of the reasons I looked to UDP is that I do not explicitly have to specify the host address, or maintain a TCP connection and can resort to multicast. I have created a PR. |
I am toying with the development of an iOS 'SondeSeeker' app for the rdz_ttgo_sonde and wondering how much work would be involved to essentially clone the ChaseMapper UDP feature and have rdz send out a UDP packet with the same format as live.json?
I am currently polling the device via http to get the data and feel it might be better to have the data pushed out. Asking as the ChaseMapper format doesn't give all the data that's available via json, and it would be nice to have.
73,
Sean
VK6DI
The text was updated successfully, but these errors were encountered: