Chat freely about anything...

User avatar
By picstart
#57167 [quote]his node: C2823 Received from 138CFE msg=49Hello from node 138cfe
This node: C2823 Received from 6A82F msg=49Hello from node 6a82f
This node: C2823 Received from 138CFE msg=50Hello from node 138cfe
This node: C2823 Received from 6A82F msg=50Hello from node 6a82f
This node: C2823 Received from 138CFE msg=51Hello from node 138cfe
This node: C2823 Received from 6A82F msg=51Hello from node 6a82f
This node: C2823 Received from 138CFE msg=52Hello from node 138cfe
This node: C2823 Received from 6A82F msg=52Hello from node 6a82f
This node: C2823 Received from 138CFE msg=53Hello from node 138cfe
This node: C2823 Received from 138CFE msg=54Hello from node 138cfe
This node: C2823 Received from 138CFE msg=55Hello from node 138cfe
This node: C2823 Received from 6A82F msg=53Hello from node 6a82f
[/quote]
3 esp's with no timing code from github and no dropped packets within the first 50 ..I'll run it overnight and see the results.
User avatar
By picstart
#57169 Which direction is this design heading?
The no timing code uses the original design where every esp is AP_STA with unique ssid's
The developer design was a single esp got the AP+STA the rest got the STA
User avatar
By sfranzyshen
#57170
picstart wrote:Which direction is this design heading?
The no timing code uses the original design where every esp is AP_STA with unique ssid's
The developer design was a single esp got the AP+STA the rest got the STA


I took a step back from development on my devel branch to workout some of these timeout and wdt reset issues ... I am continuing to update my devel branch with the lessons learned from the no-timing experiments ... I choose to use the original code (plus know fixes) to build no-timing so that I was not introducing any new problems by using any of the changes (expanding on stuff) from the devel branch ... but I plan to drop working on no-timing once all bugs have been eliminated from the core ... and return to the devel branch for future development ...