Server Messages about packet_forwarder HOT 3 CLOSED

Hello,

I'm not sure I fully get your question.

The message format sent by the gateway are formatted as described in the PROTOCOL.txt file you can found in the lora-net/packet_forwarder root directory.

Typically there are few octets (4 to 12) describing the protocol version, the message type etc...
Then, after those few octets, you have the JSON string which contains the actual packet data.

SO the server has to parse the few bytes as a binary header, and then any JSON parser car handle the JSON string.

Regards

from packet_forwarder.

Hello,
Thank you for the quick response. This answers my question.

from packet_forwarder.

Hello,
One more thing. I receive the uplink messages, but it seems I do NOT
receive the PULL DOWN ack message on the server side. When I uncomment the
the line in the source of the beacon "//MSG("WARNING: [down] recv returned
%s\n", strerror(errno)); /* too verbose */" it is
shown continuously although I am sending messages down the UDP to the
Gateway on a 5 sec basis.

When I start the util_sync I see that the packets are received but still
the beacon program is not aware of them.

Any suggestions?

Regards.

On Mon, Apr 25, 2016 at 2:21 PM, Michael Coracin [email protected]
wrote:

Hello,

I'm not sure I fully get your question.

The message format sent by the gateway are formatted as described in the
PROTOCOL.txt file you can found in the lora-net/packet_forwarder root
directory.

Typically there are few octets (4 to 12) describing the protocol version,
the message type etc...
Then, after those few octets, you have the JSON string which contains the
actual packet data.

SO the server has to parse the few bytes as a binary header, and then any
JSON parser car handle the JSON string.

Regards

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#7 (comment)

from packet_forwarder.