MESH_DEMO from github

ESP_Alen

Re: MESH_DEMO from github

Postby ESP_Alen » Fri May 20, 2016 5:31 pm

Nikita Belyaev wrote:Hi everyone!

Can someone ask for this questions:
1) On which OSI layer does mesh protocols works?
2) How to create root node?
3) When I burned my esp8266 with mesh_demo from git, which kind of node I did? And how can I change user data?
4) Why I'm not able to change server IP? Be default its 0.0.0.0 7000. And when it started I cant see anything except "mesh server works"

There are more questions, but I cant go further without understanding of that things))

Thanks for your cooperation!

BR, Nik


1. ESP-Mesh works on application layer based on TCP layer. please refer to document for detail information;
https://github.com/espressif/ESP8266_ME ... ecture.pdf
2. All the node with the same image bin.
3. Mesh support HTTP/JSON/MQTT/BIN data, please refer to demo with json format in mesh_json.c
4. You can set ip address according to factual ip address of your server. And you can add some print to display more detail information.

Nikita Belyaev
Posts: 15
Joined: Wed May 18, 2016 11:09 pm

Re: MESH_DEMO from github

Postby Nikita Belyaev » Fri May 20, 2016 5:59 pm

Alen wrote:
Nikita Belyaev wrote:Hi everyone!

Can someone ask for this questions:
1) On which OSI layer does mesh protocols works?
2) How to create root node?
3) When I burned my esp8266 with mesh_demo from git, which kind of node I did? And how can I change user data?
4) Why I'm not able to change server IP? Be default its 0.0.0.0 7000. And when it started I cant see anything except "mesh server works"

There are more questions, but I cant go further without understanding of that things))

Thanks for your cooperation!

BR, Nik


1. ESP-Mesh works on application layer based on TCP layer. please refer to document for detail information;
https://github.com/espressif/ESP8266_ME ... ecture.pdf
2. All the node with the same image bin.
3. Mesh support HTTP/JSON/MQTT/BIN data, please refer to demo with json format in mesh_json.c
4. You can set ip address according to factual ip address of your server. And you can add some print to display more detail information.


Thanks a lot for answers!

here so more:
1) How does routing procedure works? I mean does each node know about all network's nodes? does routing static or dynamic?
2) What should i see, when local server works?
3) And where can I see all prints like this

Code: Select all

MESH_DEMO_PRINT("bcast mesh is busy\n");


I'm really glad for your help. I have read a lot pdfs, but cant find out all this questions(

CipiCips
Posts: 13
Joined: Sun Apr 24, 2016 10:26 pm

Re: MESH_DEMO from github

Postby CipiCips » Sat May 21, 2016 4:39 am

1. Please use following statement to set serial baut ratio, we have merge the statements and push it on github.
uart_div_modify(0, UART_CLK_FREQ / 9600);
uart_div_modify(1, UART_CLK_FREQ / 9600);
2. The maximum length of mesh packet is 1300.
3. When node receive packet, it's feasible to send packet to MCU with USART.



Dear Alen,

1. We have download from github in what file do we have to put:

uart_div_modify(0, UART_CLK_FREQ / 9600);
uart_div_modify(1, UART_CLK_FREQ / 9600);

2. since uart now only display information about connection with server. Can you guide us where should we change output of UART to just send received packet.


Thx
Regards
Ivan

ESP_Alen

Re: MESH_DEMO from github

Postby ESP_Alen » Sat May 21, 2016 12:52 pm

Nikita Belyaev wrote:
Alen wrote:
Nikita Belyaev wrote:Hi everyone!

Can someone ask for this questions:
1) On which OSI layer does mesh protocols works?
2) How to create root node?
3) When I burned my esp8266 with mesh_demo from git, which kind of node I did? And how can I change user data?
4) Why I'm not able to change server IP? Be default its 0.0.0.0 7000. And when it started I cant see anything except "mesh server works"

There are more questions, but I cant go further without understanding of that things))

Thanks for your cooperation!

BR, Nik


1. ESP-Mesh works on application layer based on TCP layer. please refer to document for detail information;
https://github.com/espressif/ESP8266_ME ... ecture.pdf
2. All the node with the same image bin.
3. Mesh support HTTP/JSON/MQTT/BIN data, please refer to demo with json format in mesh_json.c
4. You can set ip address according to factual ip address of your server. And you can add some print to display more detail information.


Thanks a lot for answers!

here so more:
1) How does routing procedure works? I mean does each node know about all network's nodes? does routing static or dynamic?
2) What should i see, when local server works?
3) And where can I see all prints like this

Code: Select all

MESH_DEMO_PRINT("bcast mesh is busy\n");


I'm really glad for your help. I have read a lot pdfs, but cant find out all this questions(


1. Node just knows all the sub-nodes, and routing dynamic.
2. Server will print "mesh server works" as soon as it is available.
3. Mesh just holds one packet from user, before it sends out the packet, it would not hold packet for user.
Before mesh send out data from user, user try to send another packet using mesh, mesh will print "**** mesh is busy"

ESP_Alen

Re: MESH_DEMO from github

Postby ESP_Alen » Sat May 21, 2016 12:59 pm

CipiCips wrote:
1. Please use following statement to set serial baut ratio, we have merge the statements and push it on github.
uart_div_modify(0, UART_CLK_FREQ / 9600);
uart_div_modify(1, UART_CLK_FREQ / 9600);
2. The maximum length of mesh packet is 1300.
3. When node receive packet, it's feasible to send packet to MCU with USART.



Dear Alen,

1. We have download from github in what file do we have to put:

uart_div_modify(0, UART_CLK_FREQ / 9600);
uart_div_modify(1, UART_CLK_FREQ / 9600);

2. since uart now only display information about connection with server. Can you guide us where should we change output of UART to just send received packet.


Thx
Regards
Ivan


Sorry, I'm confused about what you said, "where should we change output of UART to just send received packet"
I can't get what you mean.

Nikita Belyaev
Posts: 15
Joined: Wed May 18, 2016 11:09 pm

Re: MESH_DEMO from github

Postby Nikita Belyaev » Sat May 21, 2016 7:18 pm


Thanks a lot for answers!

here so more:
1) How does routing procedure works? I mean does each node know about all network's nodes? does routing static or dynamic?
2) What should i see, when local server works?
3) And where can I see all prints like this

Code: Select all

MESH_DEMO_PRINT("bcast mesh is busy\n");


I'm really glad for your help. I have read a lot pdfs, but cant find out all this questions(


1. Node just knows all the sub-nodes, and routing dynamic.
2. Server will print "mesh server works" as soon as it is available.
3. Mesh just holds one packet from user, before it sends out the packet, it would not hold packet for user.
Before mesh send out data from user, user try to send another packet using mesh, mesh will print "**** mesh is busy"



thanks!
1) what is the method of dynamic routing? which criterias nodes are uses to find best route?
2) Server just print that he is available and thats all? So how can I monitor the proses of mesh working? Where and how can I investigate bits in packets as you do it in ESP8266 Mesh User Guide?
3) I still cant understand where to look for such prints))
mesh will print "**** mesh is busy"

4) where in code should I look for description of events that are wreaten in README file such as

Code: Select all

2. Every node sends one packet to server per 7 seconds after it joins mesh network.
3. Every node gets mac address of all devices working in mesh per 14 seconds after it joins mesh?

5) Finally what is the procedure of election root and non root node?

CipiCips
Posts: 13
Joined: Sun Apr 24, 2016 10:26 pm

Re: MESH_DEMO from github

Postby CipiCips » Sun May 22, 2016 2:20 am

Dear Alen,


Sorry, I'm confused about what you said, "where should we change output of UART to just send received packet"
I can't get what you mean.


1.
Now when we flash esp with mesh demo bin files. Then when we connect serial monitor to esp we can see that esp is sending some date over UART. I suppose that is for debugging purpose. When I send packet from server to esp I wanna send that packet also over UART to mcu. So I must disable already existing debugging information and only send packet over UART.

For example I will send from server some data like "1111111111" and I wanna only this information to be send over UART. Where do we change this ?

2.
We are still unable to locate file where we have to put this two command line:
uart_div_modify(0, UART_CLK_FREQ / 9600);
uart_div_modify(1, UART_CLK_FREQ / 9600);

I hope we got this working then we will post our project here as example for others. This will be first project using esp mesh connected with some MCU.

Regards
Ivan

ESP_Alen

Re: MESH_DEMO from github

Postby ESP_Alen » Mon May 23, 2016 1:55 pm

Nikita Belyaev wrote:Hi everyone!

Can someone ask for this questions:
1) On which OSI layer does mesh protocols works?
2) How to create root node?
3) When I burned my esp8266 with mesh_demo from git, which kind of node I did? And how can I change user data?
4) Why I'm not able to change server IP? Be default its 0.0.0.0 7000. And when it started I cant see anything except "mesh server works"

There are more questions, but I cant go further without understanding of that things))

Thanks for your cooperation!

BR, Nik


1. ESP-Mesh works on TCP
2. root and non-root use the same image bin.
3. please refer to mesh_json.c for demo to set user data.
4. You can modify the IP address of server, please make sure the address is visible for root device.

Nikita Belyaev
Posts: 15
Joined: Wed May 18, 2016 11:09 pm

Re: MESH_DEMO from github

Postby Nikita Belyaev » Mon May 23, 2016 5:16 pm

Hi, Alen!
U have already answer for that questions))
Pleas take a look at my new questions above.

Alen wrote:
Nikita Belyaev wrote:Hi everyone!

Can someone ask for this questions:
1) On which OSI layer does mesh protocols works?
2) How to create root node?
3) When I burned my esp8266 with mesh_demo from git, which kind of node I did? And how can I change user data?
4) Why I'm not able to change server IP? Be default its 0.0.0.0 7000. And when it started I cant see anything except "mesh server works"

There are more questions, but I cant go further without understanding of that things))

Thanks for your cooperation!

BR, Nik


1. ESP-Mesh works on TCP
2. root and non-root use the same image bin.
3. please refer to mesh_json.c for demo to set user data.
4. You can modify the IP address of server, please make sure the address is visible for root device.

ESP_Alen

Re: MESH_DEMO from github

Postby ESP_Alen » Tue May 24, 2016 5:08 pm

Nikita Belyaev wrote:Hi everyone!

Can someone ask for this questions:
1) On which OSI layer does mesh protocols works?
2) How to create root node?
3) When I burned my esp8266 with mesh_demo from git, which kind of node I did? And how can I change user data?
4) Why I'm not able to change server IP? Be default its 0.0.0.0 7000. And when it started I cant see anything except "mesh server works"

There are more questions, but I cant go further without understanding of that things))

Thanks for your cooperation!

BR, Nik


1. Mesh woks on TCP.
2. All the node use the same image
3. Please refer to the mesh_json.c for detail information about user data.
4. You can change the server IP, please make sure the ip address is right.

Who is online

Users browsing this forum: No registered users and 13 guests