[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] telemetry broadcast

From: Kadir ÇİMENCİ
Subject: Re: [Paparazzi-devel] telemetry broadcast
Date: Mon, 7 Jul 2014 13:28:36 +0300

Stephen,just for the records,  my java app was working fine in the same machine with server,  i could't run a different agent on the remote machine just like the java app. But a strange thing,running ivyprobe app on the remote machine, i can list clients and watch their status, cannot bind/receive any messages. (16 bit subnet mask case)

2014-07-07 13:21 GMT+03:00 Kadir ÇİMENCİ <address@hidden>:

Thanks for the answers. Today i find a solution for the problem. I had already tried with LAN broadcast ip with 16 bits subnet mask but it didn't worked, i have changed the mask with 24 bits and it is working now. I don't know why there is a problem with 16 bits or is it a specific problem with my environment, but anyway thanks again :)


2014-07-04 18:29 GMT+03:00 Stephen Dwyer <address@hidden>:


Yes, the bus should be on the broadcast IP, as Alexandre said. At least that has worked for me in the past. The local loopback doesn't work on OS X for normal operation; it uses instead.

Does your java app work when run on the same local machine as the server? Also, can you try running a different agent/app on the remote machine, other than your java app? You might also want to try ivyprobe to see if you are getting any messages.

-Stephen Dwyer

On Fri, Jul 4, 2014 at 6:52 AM, Alexandre Bustico <address@hidden> wrote:
Le 03/07/2014 15:19, Kadir ÇİMENCİ a écrit :

The options i have tried;
1) path_to_server/server -n -b "ip:port" (local ip of the machine on which the server is running, broadcast ip of the LAN, local ip of the remote computer are all tried)

2) On the remote side in a Java app.,

bus.start(Ivy.getDomainArgs("IvyHvl",new String[] {"ip:port"})); (ip of remote computer, broadcast ip of LAN, ip of the machine on which server is running are all tried)

the ip part is the broadcast ip of the LAN (example : for a 192.168.1.x network with netmask

i remember that we meet problems with broadcast address on macosx few years ago, i think it was loopback
broadcast addresses (127. ...) that was not handled, but it's old, i could be wrong.


Paparazzi-devel mailing list

Paparazzi-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]