i tried to test it, but the app cant connect, after it fails to connect, it tells me to connect to 192.168.1.200 all the time, but ive put 192.168.1.50 in config..?!
is this ip hardcoded?
ludomotico wrote:In my experience, I found that using telnet to stream data from fgfs to the remote application was too slow to be usable. Using telnet, you can read or write data about twice a second, just as the documentation says, and trying a shorter update period blocks the client. 2Hz may be suitable for showing the position of the plane on a map or change switches, but it is clearly not enough for instruments. Figuring out a way to solve this limitation was the main reason for the long delay in the last update of my application.
Thus, I'm using UDP for fast downstream communication (instruments, position, engines...), and telnet for the slower upstream communication (instrument calibration and switches), that is something that is expected that the pilot does just once in a while. I was not able to push data into fgfs using UDP and a custom protocol: it is documented in README.IO and README.protocol, but I wasn't able to have that bit working.
Users browsing this forum: No registered users and 3 guests