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).

#define MY_RS485_HWSERIAL Serial2 doesnt work, softserial still used

Redguy 6 Feb 2017, 16:46 last edited by

I amusing an Arduino mega as serial <-> RS485 gateway node..

I first tested using the default softserial solutionfrom the examples,and this works fine..

Then i added :
#define MY_RS485_HWSERIAL Serial2

So i could use serial2 as hardware serial for RS485. Which did not work. There was no activity on the tx of serial 2at all.

After some switching between hard and softserial during testing it worked all of a sudden.. I thought.. Turned out i left the max485 to the softserial pins.

So even when the hwserial is defined, the softserial is still used!?!?

Is this something anybody else noticed as well?
Reply Quote 0
1 Reply Last reply

1
Posts

814
Views

1 out of 1

Suggested Topics

Code for beta-testing?
Controllers • 24 Mar 2014, 20:48 • andriej 9 Aug 2014, 10:44

33

0
Votes

33
Posts

15.1k
Views

9 Aug 2014, 10:44

@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...
ACK -aka ECHO beeing missed by Serial Gateway with RF24 radios. V2.3.2
Bug Reports • 15 Apr 2023, 06:27 • GaryStofer 21 Apr 2023, 17:34

8

0
Votes

8
Posts

56
Views

21 Apr 2023, 17:34

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
Sensor presentation failure
Bug Reports • presentation • 31 Jul 2016, 19:23 • Sergio Rius 3 Mar 2021, 18:48

11

0
Votes

11
Posts

4.1k
Views

3 Mar 2021, 18:48

@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
Making WiFiManager compatible with MySensors 2.3.2
Bug Reports • 12 Feb 2020, 21:43 • pihome 1 Jun 2022, 16:02

2

1
Votes

2
Posts

50
Views

1 Jun 2022, 16:02

Thank you.
ESP32 + Signing fails after xxx msg as result of memory leak
Bug Reports • esp32 signing crypto esp32 signing fault mbedtls sha256 sha256hmac • 6 Apr 2020, 18:43 • Technovation 7 Mar 2022, 10:37

6

2
Votes

6
Posts

71
Views

7 Mar 2022, 10:37

actually it is thanks a lot
Boards esp8266 v3.1.0 or Newer Doesn't Work with MySensors
Bug Reports • 21 Feb 2023, 01:55 • d-smes 25 Feb 2023, 19:37

9

0
Votes

9
Posts

58
Views

25 Feb 2023, 19:37

@monte said in Boards esp8266 v3.1.0 or Newer Doesn't Work with MySensors: il existe tellement de solutions bon marché et faciles pour ce que font mysensors as rich in possibilities as this does not exist

#define MY_RS485_HWSERIAL Serial2 doesnt work, softserial still used

Suggested Topics

Code for beta-testing?
Controllers • 24 Mar 2014, 20:48 • andriej 9 Aug 2014, 10:44

ACK -aka ECHO beeing missed by Serial Gateway with RF24 radios. V2.3.2
Bug Reports • 15 Apr 2023, 06:27 • GaryStofer 21 Apr 2023, 17:34

Sensor presentation failure
Bug Reports • presentation • 31 Jul 2016, 19:23 • Sergio Rius 3 Mar 2021, 18:48

Making WiFiManager compatible with MySensors 2.3.2
Bug Reports • 12 Feb 2020, 21:43 • pihome 1 Jun 2022, 16:02

ESP32 + Signing fails after xxx msg as result of memory leak
Bug Reports • esp32 signing crypto esp32 signing fault mbedtls sha256 sha256hmac • 6 Apr 2020, 18:43 • Technovation 7 Mar 2022, 10:37

Boards esp8266 v3.1.0 or Newer Doesn't Work with MySensors
Bug Reports • 21 Feb 2023, 01:55 • d-smes 25 Feb 2023, 19:37

14
Online

11.5k
Users

11.1k
Topics

112.8k
Posts

#define MY_RS485_HWSERIAL Serial2 doesnt work, softserial still used

Suggested Topics

Code for beta-testing? Controllers • 24 Mar 2014, 20:48 • andriej 9 Aug 2014, 10:44

ACK -aka ECHO beeing missed by Serial Gateway with RF24 radios. V2.3.2 Bug Reports • 15 Apr 2023, 06:27 • GaryStofer 21 Apr 2023, 17:34

Sensor presentation failure Bug Reports • presentation • 31 Jul 2016, 19:23 • Sergio Rius 3 Mar 2021, 18:48

Making WiFiManager compatible with MySensors 2.3.2 Bug Reports • 12 Feb 2020, 21:43 • pihome 1 Jun 2022, 16:02

ESP32 + Signing fails after xxx msg as result of memory leak Bug Reports • esp32 signing crypto esp32 signing fault mbedtls sha256 sha256hmac • 6 Apr 2020, 18:43 • Technovation 7 Mar 2022, 10:37

Boards esp8266 v3.1.0 or Newer Doesn't Work with MySensors Bug Reports • 21 Feb 2023, 01:55 • d-smes 25 Feb 2023, 19:37

14Online

11.5kUsers

11.1kTopics

112.8kPosts

Code for beta-testing?
Controllers • 24 Mar 2014, 20:48 • andriej 9 Aug 2014, 10:44

ACK -aka ECHO beeing missed by Serial Gateway with RF24 radios. V2.3.2
Bug Reports • 15 Apr 2023, 06:27 • GaryStofer 21 Apr 2023, 17:34

Sensor presentation failure
Bug Reports • presentation • 31 Jul 2016, 19:23 • Sergio Rius 3 Mar 2021, 18:48

Making WiFiManager compatible with MySensors 2.3.2
Bug Reports • 12 Feb 2020, 21:43 • pihome 1 Jun 2022, 16:02

ESP32 + Signing fails after xxx msg as result of memory leak
Bug Reports • esp32 signing crypto esp32 signing fault mbedtls sha256 sha256hmac • 6 Apr 2020, 18:43 • Technovation 7 Mar 2022, 10:37

Boards esp8266 v3.1.0 or Newer Doesn't Work with MySensors
Bug Reports • 21 Feb 2023, 01:55 • d-smes 25 Feb 2023, 19:37

14
Online

11.5k
Users

11.1k
Topics

112.8k
Posts