Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

ESP8266 Gateway logic conflict MY_GATEWAY_CLIENT_MODE & MY_USE_UDP

rb3rg

Scenario: GatewayESP8266 with UDP

If you clone the development version from github and try to compile the GatewayESP8266 with MY_USE_UDP it will fall over a bunch of compilation errors.
The reason is found in the MySensors.h around line 153, GATEWAY - TRANSPORT

#if (defined(MY_CONTROLLER_IP_ADDRESS) || defined(MY_CONTROLLER_URL_ADDRESS))
	#define MY_GATEWAY_CLIENT_MODE
#endif
#if defined(MY_USE_UDP) && !defined(MY_GATEWAY_CLIENT_MODE)
	#error You must specify MY_CONTROLLER_IP_ADDRESS or MY_CONTROLLER_URL_ADDRESS for UDP
#endif

Once you define MY_USE_UDP you will also want to define MY_CONTROLLER_IP_ADDRESS to send the packages to your controller,
However as you see in the first line if MY_CONTROLLER_IP_ADDRESS is defined then MY_GATEWAY_CLIENT_MODE will be auto defined and this
will conflict with UDP use.

I've fixed it changing to:

#if (defined(MY_CONTROLLER_IP_ADDRESS) || defined(MY_CONTROLLER_URL_ADDRESS)) && !defined(MY_USE_UDP)
	#define MY_GATEWAY_CLIENT_MODE
#endif
#if defined(MY_USE_UDP) && (!defined(MY_CONTROLLER_IP_ADDRESS) && !defined(MY_CONTROLLER_URL_ADDRESS))
	#error You must specify MY_CONTROLLER_IP_ADDRESS or MY_CONTROLLER_URL_ADDRESS for UDP
#endif

1
Posts

932
Views

Suggested Topics

Code for beta-testing?
Controllers • • andriej

33

0
Votes

33
Posts

15138
Views

@donnib - I didn't continue this way but instead started using node-js based controller code that connects to a standard Ethernet gateway. @hek merged the code about two weeks ago. I will provide a tutorial on how to set it up from scratch shortly...
NRF51-52 PA not support ???
Bug Reports • • berkseo

17

0
Votes

17
Posts

1342
Views

@berkseo said in NRF51-52 PA not support ???: The network is simple, this node is nrf52 with an amplifier and a gateway with the nrf24 radio module with an amplifier. It would be strange if a gateway with an amplifier could not deliver ACK. Two moments, or I did a very bad control of the amplifier on the node nRF52 or in the radio driver itself, something is not working well, and may need some delay settings. If i send messages with an ECHO (soft ack) request, this works fine over very long distances. Hw ack does not work properly. Someone was able to do this for mysensors? Gateways and repeaters on nrf5 with amplifier is a very, very cool topic.
ACK -aka ECHO beeing missed by Serial Gateway with RF24 radios. V2.3.2
Bug Reports • • GaryStofer

8

0
Votes

8
Posts

56
Views

First let me say that the test "network" consists of a single node and a Serial GW with a Domoticz controller only. No repeater nodes are present and it operates at 250Kbd on a frequency outside of the WiFi spectrum verified to have no traffic. The test subjects are within 10 feet of each other and the protocol sniffer receiver is placed roughly midway between the two communicating nodes. The test node has a plugable connector for the RF modules so that I can switch them out separately. The GW has the LNA/PA module and the node is using the standard mudules. Both GW and node are set to "High" power. Looking at the problem with the promiscuous protocol sniffer and wireshark I can clearly see that packets collide mid air when both the node and the GW transmitting at the same time. This happens when the controller/GW talks to the node while having the protocol ACK request enabled and the node does not have the extra wait/delay programmed. Going through 12 RF modules node side, I can see that about 1/3 shows the problem consistently to the extent that all 16 retransmissions are used up , 1/3 to various degrees and the rest shows no problems at all. Before you say "ohh fake chips etc." these modules all came from the same batch, so more than likely not fake and non fake, but rather some parameter that the lib assumes to tight of a margin for. When turning off the protocol level ACK via the controller/GW, the package goes out without an request for the node to send back the package, only the HW ack remains in the picture. Setup like this I can see that the third of the modules that cause the persistent collisions evoke a re-send of the package by the GW after ~2 to 2.5ms , while the group that shows no problem shows one single transmission from the GW only. Since the sniffer is not fast enough to capture the quick turn around ( spec says 130us) for the short HW ack to go out I can not get say whether the node is simply not sending it or just not sending it in quick enough. All I can say is that the GW code did not see a HW ack and therefore sends out the package a second time. Meanwhile on the node side all is well, it just might get the same package twice and since no status changed there is no harm done. However when you now turn on the protocol level ACK request in the controller ( as you should) the node has to turn around and send out the echo package which then collides with the resend of the original package from the GW. The node also doesn't get an HW-ACK becasue of this and tries to resend the echo package over again until it runs out of tries. When I then introduce the wait/delay in the code above to wait out the 2.5Ms for the GW to resend the initial package this ACK/resend storm goes away because the air is clear when the node sends it's echo package. If I wait/delay for 2 ms the problem is greatly reduced and if I wait 3 ms I see no more evidence of collisions. Either wait or delay works however, I choose delay() to be positively sure that no other communication is started during that time by the node. I conclude that as a work around this solves the issue we are having with the RF24 transport, but without further investing into faster RF sniffing equipment I can't say for sure if this could be solved better on the TX side by waiting longer for the HW ack to arrive from the receiving node, however I think there would be a good chance for that. There is also a chance that the PA/LNA module used on the GW could be part of the problem by not being able to switch quickly enough back to RX mode and therefore loose the HW-ACK for nodes that respond quicker than others. Edited: Checked with a non PA/LNA module on the GW and no change could be observed, so this theory can be discounted. BTW: All of this is very reminiscent of an email communication in 2015 I had with Ekblad !! GS
ESP32 + Signing fails after xxx msg as result of memory leak
Bug Reports • esp32 signing crypto esp32 signing fault mbedtls sha256 sha256hmac • • Technovation

6

2
Votes

6
Posts

71
Views

actually it is thanks a lot
Sensor presentation failure
Bug Reports • presentation • • Sergio Rius

11

0
Votes

11
Posts

4137
Views

@Yveaux I also add the delay to not ddos the gateway. When I did the MySensors workshop, 20 people started to connect to the gateway almost at the same time. And they got Funky messages. Since then I do a delay. But it would probably be better to add a random time to the delay. Something like 20ms + random( 0 - 30 ) ms. That way you don't get the ddos effect. Sonoff had the same problems with their solution a couple of years ago, when the servers went down. All Sonoff devices tried to reconnect almost the at the same time. Which caused a ddos xd
sleep(0) in V2.1 doesn't sleep indefinitely anymore. Used to powerdown and sleep in V1.5
Bug Reports • • GaryStofer

3

0
Votes

3
Posts

149
Views

@mfalkvidd No, the issue with sleep(0) still exists in V2.3.2. That is the version that the ArDuino Library installer installs currently . -- Work around is to call hwPowerDown(WDTO_SLEEP_FOEREVER) as in above code if you want the battery to last more than a day. GS

ESP8266 Gateway logic conflict MY_GATEWAY_CLIENT_MODE & MY_USE_UDP

Suggested Topics

Code for beta-testing?
Controllers • • andriej

NRF51-52 PA not support ???
Bug Reports • • berkseo

ACK -aka ECHO beeing missed by Serial Gateway with RF24 radios. V2.3.2
Bug Reports • • GaryStofer

ESP32 + Signing fails after xxx msg as result of memory leak
Bug Reports • esp32 signing crypto esp32 signing fault mbedtls sha256 sha256hmac • • Technovation

Sensor presentation failure
Bug Reports • presentation • • Sergio Rius

sleep(0) in V2.1 doesn't sleep indefinitely anymore. Used to powerdown and sleep in V1.5
Bug Reports • • GaryStofer

36
Online

11.4k
Users

11.1k
Topics

112.7k
Posts

ESP8266 Gateway logic conflict MY_GATEWAY_CLIENT_MODE & MY_USE_UDP

Suggested Topics

Code for beta-testing? Controllers • • andriej

NRF51-52 PA not support ??? Bug Reports • • berkseo

ACK -aka ECHO beeing missed by Serial Gateway with RF24 radios. V2.3.2 Bug Reports • • GaryStofer

ESP32 + Signing fails after xxx msg as result of memory leak Bug Reports • esp32 signing crypto esp32 signing fault mbedtls sha256 sha256hmac • • Technovation

Sensor presentation failure Bug Reports • presentation • • Sergio Rius

sleep(0) in V2.1 doesn't sleep indefinitely anymore. Used to powerdown and sleep in V1.5 Bug Reports • • GaryStofer

36Online

11.4kUsers

11.1kTopics

112.7kPosts

Code for beta-testing?
Controllers • • andriej

NRF51-52 PA not support ???
Bug Reports • • berkseo

ACK -aka ECHO beeing missed by Serial Gateway with RF24 radios. V2.3.2
Bug Reports • • GaryStofer

ESP32 + Signing fails after xxx msg as result of memory leak
Bug Reports • esp32 signing crypto esp32 signing fault mbedtls sha256 sha256hmac • • Technovation

Sensor presentation failure
Bug Reports • presentation • • Sergio Rius

sleep(0) in V2.1 doesn't sleep indefinitely anymore. Used to powerdown and sleep in V1.5
Bug Reports • • GaryStofer

36
Online

11.4k
Users

11.1k
Topics

112.7k
Posts