ESP8266 Developer Zone

Re: ESP8266 reports "topo option format is illegal"

2016-07-04T16:08:32+08:00

freebeans wrote:
Thank you Alen.
Now the ESP won't complain about the message format being illegal. I know it reaches mesh_none_proto_parser by the serial log.
However, I would expect a M_O_TOPO_RESP from the root node, but it only sends the regular json string at timed intervals.

How does this topology request/response system work?
Do I need to work anything on the application layer for that request to be answered?

Thank you.

Root may response two packets, one for flow response, and the other one is topology response.

Statistics: Posted by Guest — Mon Jul 04, 2016 4:08 pm

Re: ESP8266 reports "topo option format is illegal"

2016-07-04T16:06:41+08:00

freebeans wrote:
Alen, correct me if I'm wrong.
Can server/mobile send topology requests to the mesh router?

The topology request feature on the demo works well between devices.
I wonder if the protocol allows me to ask about topology from outside the mesh network.

mesh supports mobile or server to get topology from root node

Statistics: Posted by Guest — Mon Jul 04, 2016 4:06 pm

Re: ESP8266 reports "topo option format is illegal"

2016-07-01T02:37:00+08:00

Alen, correct me if I'm wrong.
Can server/mobile send topology requests to the mesh router?

The topology request feature on the demo works well between devices.
I wonder if the protocol allows me to ask about topology from outside the mesh network.

Statistics: Posted by freebeans — Fri Jul 01, 2016 2:37 am

Re: ESP8266 reports "topo option format is illegal"

2016-06-29T22:48:29+08:00

Thank you Alen.
Now the ESP won't complain about the message format being illegal. I know it reaches mesh_none_proto_parser by the serial log.
However, I would expect a M_O_TOPO_RESP from the root node, but it only sends the regular json string at timed intervals.

How does this topology request/response system work?
Do I need to work anything on the application layer for that request to be answered?

Thank you.

Statistics: Posted by freebeans — Wed Jun 29, 2016 10:48 pm

Re: ESP8266 reports "topo option format is illegal"

2016-06-29T18:23:01+08:00

freebeans wrote:
I'm using the default ESP8266_MESH_DEMO from GitHub and a slightly modified version of the demo_server.py.

I modded the python server so it will send M_O_TOPO_REQ packets and they look fine on Wireshark.

Pic from Wireshark. Shows the packet the server sends to the root node asking for topology.

However, the root node reports over the serial "topo option format is illegal".
Why is it illegal? It seems to be okay.

Also, as a secondary question, what are piggyback flow permit and piggyback flow request flags for?

Thank you for your attention.

1. please set option length = 8
2. and set piggyback flow request.

Statistics: Posted by Guest — Wed Jun 29, 2016 6:23 pm

ESP8266 reports "topo option format is illegal"

2016-06-29T06:23:30+08:00

I'm using the default ESP8266_MESH_DEMO from GitHub and a slightly modified version of the demo_server.py.

I modded the python server so it will send M_O_TOPO_REQ packets and they look fine on Wireshark.

Pic from Wireshark. Shows the packet the server sends to the root node asking for topology.

However, the root node reports over the serial "topo option format is illegal".
Why is it illegal? It seems to be okay.

Also, as a secondary question, what are piggyback flow permit and piggyback flow request flags for?

Thank you for your attention.

Statistics: Posted by freebeans — Wed Jun 29, 2016 6:23 am