💬 Building a wired RS485 sensor network

[Bart]

@hek OK, thanks for the hint - thought the article is older. Anyway as I am already on it, I will try to prepare something.

BTW, Apart from the SerialGateway (where Serial is obviously not available for the debug), should the Serial work for the debug? Assuming I am using AltSoftSerial or Serial1 for the RS485 I guess it should be possible. However with DEBUG on I was not able to get it to work.

[hek]

Yes, for a regular node you should be able to print debug info.

[kimot]

Please, how many sensors on the bus you tested? I think, that this multimaster rs485 protocol is not very usefull for large number of nodes and heavy traffic..
I am working on protocol for CAN bus nodes connected to to the serial gateway, but documentation for mysensors code is very bad.
Its easier for me make it from scratch and use mysensors serial protocol between gateway and controller. only.

[pjr]

Would this help?
https://ci.mysensors.org/job/Verifiers/job/MySensorsArduino/job/development/Doxygen_HTML/

[rayven]

I would like to create a rs485 network that is 'local' to a specific device, (one that uses many arduinos to manage a process currently using a mega hardware serial ports as the intermediary and local interface ) and one mysensors note to relay sensor data from the rs485(local network) to the wireless mysensors network. Mostly I am wondering if I can use the wired network gateway and wireless network repeter features at the same time? any help is appreciated.

https://github.com/rayvenwalker/mysensors-distillation/

[wimd]

Hi, I build up the set up with serial gateway and the motion sensor but nothing happens (only nonsence is is seen in the serial monitor)
However if I run this small program using the AltSoftSerial library I can communicatie without any issue in both directions.
Have others the same issue, or what do I overlook?

#include <AltSoftSerial.h>

AltSoftSerial altSerial;
#define SSerialTxControl 2 //RS485 Direction control

#define RS485Transmit HIGH
#define RS485Receive LOW
bool ReceiveOrSend = RS485Transmit;

void setup() {

Serial.begin(9600);
Serial.println("AltSoftSerial Test Begin");
pinMode(SSerialTxControl, OUTPUT);
digitalWrite(SSerialTxControl, RS485Transmit); // Enable RS485 Transmit
altSerial.begin(9600);
if (ReceiveOrSend ){
Serial.println("send mode");
digitalWrite(SSerialTxControl, RS485Transmit); // Enable RS485 Transmit
} else
{
digitalWrite(SSerialTxControl, RS485Receive); // Enable RS485 Transmit
Serial.println("receive mode");
}
}

void loop() {
char receivedOnRS485;

if (ReceiveOrSend ){
altSerial.println(" Hello world");
delay(2000);
} else
{

if (altSerial.available()) {
receivedOnRS485 = altSerial.read();
Serial.print("ontvagen=");
Serial.println(receivedOnRS485);
}
}
}

[pjr]

2.1.0-beta tested and works between two nanos over altsoftserial
COM6:GW, COM9:Bus monitor and COM5:Node

[wimd]

Tried this but I get an errormessage when I complile sketch for the gateway.
The node presents itself but the messsage is not recognised/ answered by the gateway.

[mick]

Has anyone else got this working alright ? I've connected 5v, GND, pins 8 to RD. 9 to DI. DE + RE to 2 and connected the rs485 modules via A B. Not getting any replys. Does the rs485 link need a resistor across it? Cheers.

[wimd]

@MICK HI, please check this topic : https://forum.mysensors.org/topic/5495/rs485-on-nano

[mick]

@wimd Thanks mate! That topic was just what I was looking for. Works perfectly with defining a node ID!

Just added this to my sensor node:

#define MY_NODE_ID <X>

and everything came together. Thank you for your quick reply.

[kimot]

Yes. It is very bad for beginners, that examples in MySensors library are wrong.
Example "MotionSensorRS485" will never work and I think, that author not tested it.
MY_NODE_ID must be always defined for node in RS485 network, because is used for RS485 network addressing.
Obtaining NODE_ID from controller with currentRS485 network implementation is impossible and I think it should be clearly mentioned in the examples and documentation.

[hek]

Would be better if someone with a RS485 setup could analyse and fix the root cause of why automatic id assignment doesn't work than just change the example to use static ids.

Did the id request reach your controller or gateway? Did the id response get to your gateway?

[kimot]

@hek
I think it is simply. In radio network, each node has its unique "radio ID" , witch is used for delivering messages between nodes in radio network. So node can send message " Give me NODE_ID" and gateway or controller knows to witch radio ID send message with assigned NODE_ID in it.
But in RS485 network we had not unique network ID by default - we use directly NODE_ID for addressing messages between nodes.

[hek]

No, it follow exactly the same flow as in a radio network. The gateway (and nodes) should listen to "channel" 255 which is used for broadcast messages (picked up by anyone interested; I.e. repeaters and nodes waiting for new id).

When a id request is sent out from a node, the gateway will forward it to the controller.. the controller sends out the new id on 255 (which is forwarded by the gateway) and (hopefully) picked up by the new node.

So somewhere in stil flow the message is not sent along for some reason. Which controller do you use @kimot?

[kimot]

@hek
I am using Domoticz, but not using RS485, instead I am working on CAN protocol layer for MySensors or using only MySensors serial gateway protocol in my CAN-to-Domoticz gateway. For that reason I am studying source code of MYSensors a lot of. Its only useful documentation source, unfortunately.
Imagine, if you "switch on" entire your network with 10 nodes. Each node send request for NODE_ID to the gateway and gateway send broadcast with assigned NODE_ID. How RS485 nodes recognizes, that this NODE_ID is exactly for specific node?
Why in radio network is something like MY_RF24_NODE_ADDRESS?
( five bytes long, 4 are constant, fifth is radio ID )
I seems, that entire this "MySensors network DHCP" stuff is made in different level then MyTransportXXXXX.cpp level. Maybe radio drivers ?
If you know, how it works, pleas write here or send link, please.
I can imagine only mechanism, when only one new node is connected at time, or some random generated number in each node or unique serial number etc. Then gateway can send NODE_ID with this "mark" end receiving node knows, that this is for it.

[hek]

@kimot said:

Imagine, if you "switch on" entire your network with 10 nodes. Each node send request for NODE_ID to the gateway and gateway send broadcast with assigned NODE_ID. How RS485 nodes recognizes, that this NODE_ID is exactly for specific node?

This will not work (and the same applies for a radio network). All nodes will then pick the broadcasted id.

This is known limitation and has its technical background in how the radios work and that the new have problem generating a good unique random number when it starts blank.

I know we had some ideas of adding a payload (random number) on the id-request payload identifying the requesting node. The node then also check that this number is the same in the id-response. But would break backward compatibility with the serial protocol so it would only happen in a bigger (3.0?) release.

Edit: Added issue so we won't forget it.
https://github.com/mysensors/MySensors/issues/732

[kimot]

@hek
Thanks for your explanation.
Last question for you. I cannot find information about internal message strukture.
Only this discussion:
https://forum.mysensors.org/topic/305/mysensors-protocol-format
or
"hacking" libraries

Witch version is actual?

I need myself write translation between my network message format and MySensors message format to use
something like MyTransportRS485.cpp. But I have limited number of bytes for payload, so I need modify and test "data" array too.
Thanks.

[Reza]

is domoticz support this gateway ?

[wimd]

@Reza yes, select MySensors Gateway USB for type if you add hardware.

[Reza]

@wimd
i have problem with usb port in raspberry. everytime after power off/on , usb port lost for me. so now i use a raspberry gateway . rs485 can run on gpio ? with a virtual usb port

[wimd]

@Reza sory but I'm not able to help you with this.

[Reza]

@wimd
thank you

[Reza]

@wimd
i have problem with nrf24. and this is work bad for me in distance 10 or 20 meter. i have problem in wireless connection. this protocol have not this problem ? connection is good ? with out any disconnect ?

[wimd]

@Reza Check https://www.mysensors.org/build/raspberry. There is a comment for a serialgateway.

[Reza]

@wimd
i see this, but this is not for a arduino wiring. this is for a nrf24 . perhaps @marceloaqno can setup a rs485 gateway on raspberry. thank you

[wimd]

@Reza Struggling also with the radio network if the distance is more then 5m (and I'm using the ones with the antenna) I have troubles
Add #define MY_RF24_PA_LEVEL RF24_PA_HIGH to send on maximum power.
Added the capacitor give a bit extra power on the 3,3V?

I do not have a RS485 network installed yet but trails on a 10m ethernet cable did not give any issues. Still in program phase.

[wimd]

@Reza scroll down on the page down to the serial gateway chapter on that page.

[Reza]

@wimd
i use capacitor 4.7 , 100 , 470 uf.
i use 3 type of radio. (usual + 2chip + 2chip+pa+lna)
i use radio adapter. i use regolator 5 to 3.3 module.
but i have problem yet.
i dont test #define MY_RF24_PA_LEVEL RF24_PA_HIGH !
what is code ? and where i can add this ? for gateway or nodes?
this code can solve my problem ? in other means this code can increase power of radio ?

[wimd]

@Reza yes adding this code increases the power of the radio.
you add this code at the begin of your sketch (both gateway and nodes)

#define MY_RADIO_NRF24

#define MY_RF24_PA_LEVEL RF24_PA_HIGH

[Reza]

@wimd
thank you very much , i test this and i hope this is answer for me. because i am tired really
thank you my friend

[Reza]

@wimd
i test with "PA_HIGH" and "PA_MAX" (for nodes and gateway) but this is more bad.
(for example for 10-15 meter with 2 wall)
in default PA for 10 command i have 2 error
in PA_HIGH for 10 command i have 8 error
in PA_MAX my connection is disconnect completly
can you understand where is problem? i think this is related to power supply of radio (because when i want more power for more distance so radio can not have a good connection) but i providing enough power for radio. i use a adapter 5v 2A and connect this to a radio adapter(reglator 5 to 3.3) even use a 4.7u capacitor for radio. similar to photo:

[wimd]

@Reza You have exactly the same problem as I had when I first found MySensors in march last year.
I got a couple of radio and started to play with them. All worked fine as long as they were not more than 5m away from each other. I dropped the idea at that time.

2 months ago I saw the possibility on the website to build a wired network. I started again. With the order for the RS485 bricks I ordered also some radios but now with antenna and amplifier. The only improvement I got was now up to 7m.
I managed now to connect with my greenhouse that is 12m away but had to place a repeater in between but the connection is no reliable.

The discussion that is now ongoing is not related anymore to a RS485 network. I suggest you start an new topic specific for your radio issue. Or we both did do something wrong or the hardware that we buy does not meet the specification for transmitting distance.

Let me now if you started a new topic.

[wimd]

@Reza maybe read all on this one : https://forum.mysensors.org/topic/1142/nrf24l01-pa-lna/35

[gohan]

What are the main advantages of rs485 over I2C bus?

[kimot]

@gohan
I2C bus is designed for short distances, obviously between circuits on one PCB.
Max allowed capacitance i2c bus is 400pF. CAT5 cable has nominal 52pf/m.
Ideally you can communicate to distance 8m.
It is very short bus for home network, I think.
Or we need some "hacking" for i2c bus, for example at page 4 in this document:

http://www.nxp.com/documents/application_note/AN460.pdf

For each node we need one bus expander ( P82B96 ) and two CAN bus drivers ( PCA82C250 ).
7 + 2*0.5 US$ ( ebay )
Plus second pair of wires.
Or buy this: http://mayhewlabs.com/products/i2c-power-extender
You can read bus length, number of nodes and speed limit, there.

But, interesting idea.
With some smart "node addressing" and multi-master i2c bus I can imagine, that on some places you do not need processor.
For actuator simply use PCF8574 for example.

[gohan]

So basically for 10-15 meters distance it's better and cheaper to use cheap rs485 modules, right?

[kimot]

@gohan
Yes

[Reza]

@wimd thank you friend . i started several topic about this issue , but dont found any answer so i delete all topics. also i dont start new topic because friends are sad for my topics and admin told me dont start any topic
i have exactly this problem. now for 10 meter i must use a repeater ! for 10 meter ! ! ! ! this is strange ! i use 4.7u capacitor and more. i use radio adaptor. i use reglator module. use 3 type of radio . in sketch use PA_MAX and PA_HIGH ... but effectless. so you told me if i want change my network to wiring with RS485 , i will have same problem again ? i can not found any way for this problem .
now please let me for read this topic perhaps i can found any way for this problem . thank you

[wimd]

@Reza I have written earlier that I didn’t have any problem with RS485 on a cable of 10m but did not trail longer yet.
If you make trails with the wired network, make sure that you define your node id number

#define MY_NODE_ID <X>```

[wimd]

@hek I was wondering if it could be useful to have an extra sensor that a bridge between the wireless and wire network.
This bridge is made between the SPI dealing with the wireless network and the hardware serial that is dealing with the wire network.
It would allow you to connect a remote wired network.

IF the CE pin for the radio (9) could be user defined, a 2nd thought (based on the bridge idea).
Can’t something similar be done for the serial gateway and make that one suitable for wired and wireless network in the same gateway?

[gohan]

Cable will always be better that wireless, so if you can go with cable. I tried NRF24 but with those smd modules I can't get more than 6-7 meters. I have to try to add a longer antenna

[boozz]

@gohan
In some cases 'with cable' is the better option. In some cases wireless is the better option. I totally disagree with you on your statement that cable will be ALWAYS be better than wireless. that's nonsense!

There are good NRF24 modules out there and there are worse variants, maybe fake ones. I've bought from several ebay stores throughout time. I found out the hard way that some perform good with a 100uF capacitor attached (the simplest variants, costing no more than $0.85), and other perform better with a smaller size capacitor (4.7uF). I get distances with these modules over more than 25 mtrs. with all kinds of obstructions (even faraday alike) in between. All it takes is some (hobby) time to find out what works best (e.g. move a node 1 meter to the left or right or align the antenna somewhat...)
I never ever modified an antenna, never needed to do so. I once bought 2 nrf24L01+-PA-LNA antenna's for wider coverage as I thought I would need that for better/wider coverage, but now, 2 years later, they still are lying around in my workshop.

Maybe good to say that these distances can only be achieved with a speed set at 250 kBs and this is only possible using the nrf24L01+ modules!

If I can, I use wireless, as it is cheap, simple, and convenient, but the best reason for going wireless is that I don't need to use a cable! Simple as that.

For the sake of staying somewhat on topic ("Building a wired RS485 sensor network")...
There are occasions in which a wired (RS485) network would be the better choice. In my opinion one occasion is when you need instantly acknowledge that a command really was delivered to a node.

BR,

Boozz

[Reza]

@wimd
how long wiring can i use between a node and gateway with rs485 (without repeater)? how many node can support ? delay for send and receive for nrf24 is more or rs485 ? thank you

[Reza]

@boozz
how detect a fake radio with a original radio ?

[gohan]

@boozz

I said it's better because in terms of stability and reliability you can't beat cable and I also added that if he can use a cable to go with it otherwise wireless it's still an option, but as you said it takes time and trial and error to make good use of those nrf24 especially for the reason that there are lots of clones on the market that behave slightly differently from one another and thus adding more complexity to the project.
In addition once you have a cable you can also use it for power.
Of course cable is not the universal solution for all the problems, but if I had to choose between a wired or wireless security system I'd choose wired and if I would need to have a temperature sensor that reports data every now and then I'd go most likely wireless

[boozz]

@gohan
My reaction was only based on your last post in this tread , I totally agree with you on the wired security system where wireless is not an option.

[boozz]

@Reza
There are many options for detecting fake radio's. For me it works best to test them in a node that has a good working radio attached (preferrably far as far away from its parent node as possible) and exchange it with the suspected fake one.

There's also a thread in this forum that describes a method to test the quality of nrf24L01+ connections. It's a quality meter. I know for sure you can find this one using the search function.

By the way; about the wiring distance between a node and gateway: the fastest way to get an answer is to get multiple answers on such questions is using an universal search engine: www.google.com

[gohan]

@boozz
What are the codes on the NRF24 chip of the modules you consider being the best performing?

[hek]

@gohan

There is no easy way of telling by looking at it.

https://forum.mysensors.org/topic/1664/which-are-the-best-nrf24l01-modules

[Reza]

for wiring , is this true ?
rs485...............arduino
vcc......................5v
gnd....................gnd
DI.........................9
DE........................2
RE.......................10
R0........................8

[kimot]

@Reza

DI and DO depends on your board type.
Look at AltSoftSerial_Boards.h
DE and RE should be connected together and connected to pin,
which is defined in your program:
#define MY_RS485_DE_PIN 2

[kimot]

@Reza
http://cmss.pl/arduino/MySensor_RS485_test02_b.JPG

[Reza]

@kimot thank you friend

[Reza]

@kimot
for a raspberry pi gateway this wiring is true ?

[wimd]

@Reza No. You need to have your gateway inbetween. Your controller can't "talk" directly with you MySensors network. Wee the picture from kimot.

[gohan]

@wimd
actually RPI can act as gateway https://www.mysensors.org/build/raspberry , but I agree that's much easier to have an Arduino as a gateway

[Reza]

@wimd we can build a gateway with raspberrypi without arduino . @gohan saying true . but i have to use gpio for serial gateway because when i use a usb serial port after turn on/off or reboot raspberry can not detect my gateway... but with gpio i test and this is true, so i have to use gpio for gateway

[Reza]

if i use rs485 for my network , can solve problems about signaling and distance and wall? and solve problem about NACK ?

[kimot]

@Reza
Maybe your problem and its solution with "serial-through USB" connection on Raspberry is described here:

https://g0kao.wordpress.com/2013/08/08/usb-port-assignment-on-a-raspberry-pi/

[kimot]

@kimot
I am not sure, that Raspberry can work like RS485 gateway for MySensors RS485 network.
On a "quick" look through code, I do not find anything for RS485.

[gohan]

@Reza
Maybe it is worth a try and get a W5100 network shield and make an ethernet gateway. I have one now and so far I'm happy with it.

[Reza]

thank you friends

[Reza]

@kimot @gohan do you use a wired network with rs485 ? i have problem with rf24 and i want change my wireless network to a wiring network , but i want know with a rs485 all command are send? without error and NACK ? now for wireless network i have for example every 5 true commands 1 fail command(NACK)

[gohan]

@Reza
not yet, but I am getting the parts to make a wired rs485 network of 4 nodes + gateway. About the NACK error it should be handled by the library and retransmit the lost packet.

[pjr]

Currently there is no "hw" ack functionlity like the radio has.
You can check out the rs485 transmit code from here.

But you can of course use the ack functionality between controller software and node to make sure message will get to destination.

[Reza]

@gohan now my sensors lib how many send packet if first is lost ? how more this ?
i want after send command Turn on light Certainly

[Reza]

i am tired for test and trying to configure wiring network with RS485. this is strange
i build a gateway and a relay with rs485 . for test i now use 2raspberry pi and 1orangepi and a laptop ! every time disconnect gateway from one and connect to other one ( with out other change for example sketch and wiring and etc. just change controller) some time this is very good work on laptop. some time good work on orange and some time good on raspbrrey pis !! some time same first command has sent(LED on gateway and on node just one blink. some time LEDs 2 blink and turn on later)
i am using 15cm wire between 2nodes! when change to some meter so dont work never...
so there is not any one that understand what is reason this issue !!!

i am ready and i have devices and madules. so any body that think can solve this , told me so i test on my devices and feedback.

[pjr]

@Reza have you tried to use terminating resistors?

And perhaps it could be good to try 1k pull-up and pull-downs at the gateway end. The left diagram:

With these two tricks I got my setup stable.

And a little tweak to transport class could help also..

[Reza]

@pjr
i use 120 ohm in terminate before. but now i use 1k for pull-up and down.but this is effectless.
please wait until i read this topic (rs485 stress test) and do it and feedback here . thank you

[Reza]

@pjr thank you for help , i read that topic hardly because i am weak in english.
What I understand , this problem is about collision , command and ack ! and related to transport rs485 and other friends trying to solve this ! is this true ?now , a rs485 network is not complete and Ideal and stable in mysensors.
i think all problem is related to collision in short wire and long wire. in many short wire i have not problem(between two nodes). in short wire gateway detect node and connect but many command are failed . in long wire gateway can not detect node and can not connect never.

[kimot]

@Reza
Original RS485 library was written so, that multiple SOH characters is sended on start of package.
In Mysensors library it is only one times and it can be problem for synchronization and arbitration.

Try in MyTransportRS485.cpp in function "transportSend" change line 274 from

for(byte w=0; w<1; w++) {

to

for(byte w=0; w<3; w++) {

[Reza]

@kimot said in Building a wired RS485 sensor network:

for(byte w=0; w<1;

thank you i will test this and again feedback here

[Reza]

@kimot this is good. i am testing . in the first test ((just for 2 node: gateway and one relay)) i see this is work well with 15cm wire. other test with 1meter and 5 meter work well.for 30 meter (CAT6) with 120 ohm resistor (first and end bus) dont work without resistor work with 15-20% error ( dont receive or send command and ack)
but i think this is good for 2 nodes and short distance and for more nodes and distance increase % errors. is this true ?

[Reza]

@kimot also do you have idea for improve wireless transport(nrf24)?
because for wireless also i have 50% error for commands.

[pjr]

Will the result change if you add more sync(SOH) chars?

[Reza]

@pjr i dont know what is this "for(byte w=0; w<3; w++)" because i am beginner but i see after change this , my network work better. very better. but no perfect

[kimot]

@Reza
This code makes, that your node sends three SOH bytes on beginning of message instead of only one SOH.

[kimot]

@Reza
Sorry, I do not know.
I am not using radio now (but RS485 too not).
I only look to code and try some RS485 library things,
but only two nodes connected through serial lines.
I am trying understand like MySensors code works to write my own library for CAN bus.

https://forum.mysensors.org/topic/5327/can-bus-transport-implementation-for-mys/17

[Reza]

@kimot thank you for help

[kimot]

@Reza
Like someone writes here, your module maybe includes all needed resistors for the bus on PCB.

http://yourduino.com/sunshop//index.php?l=product_detail&p=323

For two nodes it ok and you must not connect any terminating resistors.
For three and more, you must remove this resistors from PCB exclude those nodes, which are on the ends of bus.
Maybe you can divide your "big" problem to several "small" problems.
RS485 is tested bus and MUST work even on long cables.
It must be problem with electricity circuit or software.
Maybe software switchs direction pin to receiving mode early and not all data are send on the bus.
In MyTransportRS485.cpp maybe it is wrong .
It is "hard coded" for crystal 20MHz and bus speed 9600 bd. Try put your values.
//
_dev.flush();
delayMicroseconds((20000000UL/9600)+1);
//

Try examples from AltSoftSerial library with different lengths of cables and do not forgot handle your DE pin.
https://github.com/PaulStoffregen/AltSoftSerial

Or connect your two nodes only through serial wires and check functionality of your code without rs485 converters.

[Reza]

@kimot how remove resistors from PCB ? there is resistor onboard? so for first and end dont need connect external resistor ? in other means i must for example for 10 nodes , any change in node 1 and 10 ! and remove resistor for node 2 - 9 with soldering?
i test with some hardware. for 30 meter cable i dont use sheild cable. this is without sheild? may be problem for 30 meter is related to this ! is this true ?
i dont change any things in mytransport rs485 just W<3. also sketch is from site
im my transport is:
_dev.flush();
delayMicroseconds((20000000UL/9600)+1);

your last experience how many nodes you use ? with how much wire? and how % error for send and receive you have?

[scalz]

@Reza

I agree regarding your rs485 network you may need to adjust resistors. But i've not this setup, even if i would like to try it!

about removing smd resistor..if you have a solder iron, a simple trick :
Let's assume you want to push and remove your resistor to the right..

1. Add a blob of solder to the right pad (take a magnifier if you're not confident or smd is too small)
2. Heat well this pad. Not like hell, lol, but enough so solder will still be melted, for,
3. Then quickly move to the left pad, heat it, and push the resistor to the right for removing it.

Be careful with others parts around of course

I hope it's clear

[Reza]

@scalz This is an exciting job
thank you
i hope it is clear too

[kimot]

@Reza
I recommend nothing solder or unsolder now.
Simply start with two Arduinos on two ends of cable.
When your communication will work for these two devices, then you can go further.
For one Arduino write simple sketch, which will periodically send something ("Hello World/n" )
to the bus. Other Arduino with sketch witch will receive characters and sends then through USB serial port to serial monitor on PC. Only with AltSoftSerial library, not with MySensors.
When this communication will work on any length of cable ( I suppose you have not cable longer then 1km at your home ), you can go further.
You do not need drive DE and RE pins by software, simply on transmitting Arduino set it for transmit ( to +5V ) and on receiving Arduino to ground.

[Reza]

@kimot this hard for me because i am beginner but thank you very thank you for help

[ranseyer]

Hi, i have a Gateway running and the motion-sensor. The Sensors talks with the Gateway. (Arduino Pins: D2,D8,D9)
Now i have to switch to another Hardware. On the Arduino-Pro Mini i have easy access to 0-RX, 1-TX, 2-D5, 3-D5, 4-D7, 10-13, A1-A3)
Which combination of this pins would be the best, and how can i define it in the sketch ?
Im happe for each hint.

[ArduiSens]

The 510 ohm pull up and pull down resistors are usually mounted on the master side. Theoretically it
would be best to install it in the middle of your bus line. The 120 ohm termination resistor must always
be used on distances greater than 1 meter and/or baud rates higher than 9600. It’s best to install it as a
norm as noise and reflections will cause havoc on your communication once implemented in the field.
The termination resistors should be mounted at both ends of the bus line. Please note that adding bias
resistors will load the driver IC output. With the indicated values the max number of units on the bus
line is limited to eight 12kΩ, sixteen 24kΩ, or thirty-two 48kΩ units.
For further protection transient suppressors can be installed across the differential lines, from the Vcc to
D+ and from GND to D-.!

[ArduiSens]

Google for simple Modbus Master dcouments (arduino forum)

The MAX485 is not the best RS485 chip because of it's own internal impedance.
The chip in the diagram can be change by MAX485, MAX...

https://datasheets.maximintegrated.com/en/ds/MAX1487-MAX491.pdf

[ArduiSens]

FYI

[nofox]

Hi, I'm building my home automation system and I have UTP cables cat5e in walls going to my wall switches. I have four cables, 5 nodes on one cable, 2 nodes on the second cable, and one node on 3rd and one 4th cable. 9 nodes. I know that the RS485 should be connected in parallel on single twisted pair but i cant change cables now cause my walls are painted etc.. So I have few problems, nodes stops working, i need to reset them few times, after few days the network stops to work and i start to search for an answers here. I changed numbers of SOH from 1 to 3 in 274 line of MyTransportRS485.cpp and now I think the network working better. I have 120ohm resistor in every node. You think that I should remove them ? Nodes are max 10 meters from the gateway so the cable lengths aren't so long.

[kimot]

@nofox
If you have got one free pair of wires in cat5e cable, it is easy to convert your "star" topology to pure 485 bus topology with terminal resistors on both ends only.

[gohan]

I think the 120Ohms resistor needs to go at the end of the cable, not on each node

[nofox]

@kimot I was thinking about that before I wrote here, and if nothing else can help I will convert star to bus.

[ArduiSens]

@nofox it's what gohan stated, the 120ohm resistors should only put on the first and last node of you network. And you can only use a "bus" network topology for RS485.You should use the other wires of you Ethernet cable to accomplish this like kimot wrote.

[nofox]

Ok, so i switched my RS485 network to "bus". I desolder all of 120ohm resistors and have them only on both ends of the bus. RS485 to Ethernet gateway is in the middle of the wire. There are still some problems.. When I switching on the power and reading debug from gate I see that only 4 from 9 nodes are presenting. I need to reset other nodes manually to get them properly presented to the gateway. What am I doing wrong ? I need help I think.. Maybe its caused by the fact that all nodes powering on at the same time and there are many collisions on the RS485 bus ?? Maybe I should add some different delay() to setup part of my sketches to give, a time for every single node to present to the gateway ? Someone have successful working rs485 mysensors network here ?

This is code for one of my nodes with buttons, relays and temperature sensor:

#define MY_NODE_ID 8

// Enable debug prints to serial monitor
#define MY_DEBUG 

// Enable RS485 transport layer
#define MY_RS485

// Define this to enables DE-pin management on defined pin
#define MY_RS485_DE_PIN 2

// Set RS485 baud rate to use
#define MY_RS485_BAUD_RATE 9600

#include <SPI.h>
#include <MySensors.h>
#include <Bounce2.h>
#include <DallasTemperature.h>
#include <OneWire.h>
#include <OneButton.h>

// define actions for OneButton function
typedef enum {
  ACTION_OFF_1,  // set relay "OFF".
  ACTION_ON_1,   // set relay "ON"
  ACTION_OFF_2, 
  ACTION_ON_2
}
MyActions;

MyActions nextAction_1 = ACTION_OFF_1;
MyActions nextAction_2 = ACTION_OFF_2;

// define Arduino I/O pins for relays
#define RELAY_1  3 // Arduino Digital I/O pin number for first relay
#define RELAY_2  5 // Arduino Digital I/O pin number for first relay
#define RELAY_ON 1  // GPIO value to write to turn on attached relay
#define RELAY_OFF 0 // GPIO value to write to turn off attached relay

// configure parameters for 1Wire temp sensor
#define COMPARE_TEMP 1
#define ONE_WIRE_BUS 6
#define MAX_ATTACHED_DS18B20 16

// define CHILD IDs for relays and virtual multiaction click/doubleclick/longpress buttons
#define CHILD_ID_11 11 // child id for first relay and first button single click 
#define CHILD_ID_12 12 // child id for second relay and second button single click
// #define CHILD_ID_13 13 // child id for first button single click (in this version not active because single click is attached directly to relay state)
#define CHILD_ID_14 14 // child id for first button double click
#define CHILD_ID_15 15 // child id for first button long press
// #define CHILD_ID_16 16 // child id for second button single click (in this version not active because single click is attached directly to relay state)
#define CHILD_ID_17 17 // child id for second button double click
#define CHILD_ID_18 18 // child id for second button long press

// define variables for temperature (and other) 1Wire Sensors
long previousMillis = 0;
long sensorInterval = 60000; // interval for temperature measurement 
long HI_interval = 1000;
OneWire oneWire(ONE_WIRE_BUS);
DallasTemperature sensors(&oneWire);

float lastTemperature[MAX_ATTACHED_DS18B20];
int numSensors=0;
bool recivedConfig = false;
bool metric = true;

// define Arduino Digital I/O pins for OneButton function
OneButton BUTTON_1(7, true); // Arduino Digital I/O pin number for first physical button
OneButton BUTTON_2(10, true); // Arduino Digital I/O pin number for second physical button

bool V1_BUTTON_1; // set variable for virtual one click button 1
bool V2_BUTTON_1; // set variable for virtual double click button 1
bool V3_BUTTON_1; // set variable for virtual long press button 1

bool V1_BUTTON_2; // set variable for virtual one click button 2
bool V2_BUTTON_2; // set variable for virtual one click button 2
bool V3_BUTTON_2; // set variable for virtual one click button 2


bool state1; // variable for RELAY_1 states 
bool state2; // variable for RELAY_2 states 

void before()
{    

 sensors.begin();

}

//define messages for diferent type of sensors CHILD_IDs used
MyMessage msg0(0,V_TEMP); // temperature sensor message
MyMessage msg11(CHILD_ID_11, V_LIGHT); // first relay & single click message
MyMessage msg12(CHILD_ID_12, V_LIGHT); // second relay & single click message

// MyMessage msg13(CHILD_ID_13, V_LIGHT); // button 1 Single click
MyMessage msg14(CHILD_ID_14, V_LIGHT); // button 1 Double click
MyMessage msg15(CHILD_ID_15, V_LIGHT); // button 1 Long press

// MyMessage msg16(CHILD_ID_16, V_LIGHT); // button 2 Single click
MyMessage msg17(CHILD_ID_17, V_LIGHT); // button 2 Dobule click
MyMessage msg18(CHILD_ID_18, V_LIGHT); // button 2 Long press

void setup()
{

digitalWrite(RELAY_1, RELAY_OFF); // Set first relay state and pin mode
 pinMode(RELAY_1, OUTPUT);

state1 = loadState(CHILD_ID_11);  // Set relay to last known state (using eeprom storage)
 digitalWrite(RELAY_1, state1?RELAY_ON:RELAY_OFF);

digitalWrite(RELAY_2, RELAY_OFF); // Set second relay state and pin mode 
 pinMode(RELAY_2, OUTPUT);

state2 = loadState(CHILD_ID_12);  // Set relay to last known state (using eeprom storage)
 digitalWrite(RELAY_2, state2?RELAY_ON:RELAY_OFF); 

 
// sending states of relays after node bootup
send(msg11.set(state1));
send(msg12.set(state2));

// attaching physical BUTTON_1 to OneButton function actions
BUTTON_1.attachClick(singleclick_BUTTON_1);
BUTTON_1.attachDoubleClick(doubleclick_BUTTON_1);
BUTTON_1.attachLongPressStop(longpress_BUTTON_1);
// attaching physical BUTTON_2 to OneButton function actions
BUTTON_2.attachClick(singleclick_BUTTON_2);
BUTTON_2.attachDoubleClick(doubleclick_BUTTON_2);
BUTTON_2.attachLongPressStop(longpress_BUTTON_2);
// setup for temperature sensor
sensors.setWaitForConversion(false);

}

void presentation()
{
    sendSketchInfo("pokoiczek_puszka_1", "1.0");

    numSensors = sensors.getDeviceCount();

  // Present all sensors to controller
  for (int i=0; i<numSensors && i<MAX_ATTACHED_DS18B20; i++) {   
     present(i, S_TEMP);
  }

    present(CHILD_ID_11, S_LIGHT);
    present(CHILD_ID_12, S_LIGHT);
    
    // present(CHILD_ID_13, S_LIGHT);
    present(CHILD_ID_14, S_LIGHT);
    present(CHILD_ID_15, S_LIGHT);
    
    // present(CHILD_ID_16, S_LIGHT);
    present(CHILD_ID_17, S_LIGHT);
    present(CHILD_ID_18, S_LIGHT);
    
}


void loop()
{

  temperatureCheck(); // tmperature check function

  // states for nextAction of OneButton function
  if(state1 == HIGH)
    {
      nextAction_1 = ACTION_OFF_1;
    }
    else 
    {
      nextAction_1 = ACTION_ON_1;
    }

  BUTTON_1.tick();  // reading state of first physical button 
  
  if(state2 == HIGH)
    {
      nextAction_2 = ACTION_OFF_2;
    }
    else 
    {
      nextAction_2 = ACTION_ON_2;
    }  
  
  BUTTON_2.tick(); // // reading state of second physical button 
  
}

void singleclick_BUTTON_1()
 {
  if (nextAction_1 == ACTION_OFF_1 )
    {
      nextAction_1 = ACTION_ON_1;
      send(msg11.set(HIGH?false:true), true);
    }
  else
    {
    nextAction_1 = ACTION_OFF_1;
    send(msg11.set(LOW?false:true), true);
    }
  // send(msg13.set(LOW ? 1 : 0));
  // send(msg13.set(HIGH ? 1 : 0));
 }

void doubleclick_BUTTON_1()
{
   send(msg14.set(LOW ? 1 : 0));
   send(msg14.set(HIGH ? 1 : 0));
}

void longpress_BUTTON_1()
{
   send(msg15.set(LOW ? 1 : 0));
   send(msg15.set(HIGH ? 1 : 0));
}

void singleclick_BUTTON_2()
{
   
   if (nextAction_2 == ACTION_OFF_2 )
    {
      nextAction_2 = ACTION_ON_2;
      send(msg12.set(HIGH?false:true), true);
    }
  else
    {
    nextAction_2 = ACTION_OFF_2;
    send(msg12.set(LOW?false:true), true);
    }
   
  // send(msg16.set(LOW ? 1 : 0));
  // send(msg16.set(HIGH ? 1 : 0));
}

void doubleclick_BUTTON_2()
{
   send(msg17.set(LOW ? 1 : 0));
   send(msg17.set(HIGH ? 1 : 0));
}

void longpress_BUTTON_2()
{
   send(msg18.set(LOW ? 1 : 0));
   send(msg18.set(HIGH ? 1 : 0));
}

void temperatureCheck()
{
 unsigned long currentMillis = millis();
 if(currentMillis - previousMillis > sensorInterval)
  {
    previousMillis = currentMillis;
    
  // Fetch temperatures from Dallas sensors
  sensors.requestTemperatures();
  // query conversion time and sleep until conversion completed
  int16_t conversionTime = sensors.millisToWaitForConversion(sensors.getResolution());
  // sleep() call can be replaced by wait() call if node need to process incoming messages (or if node is repeater)
  wait(conversionTime);
  // Read temperatures and send them to controller 
  for (int i=0; i<numSensors && i<MAX_ATTACHED_DS18B20; i++) {
    // Fetch and round temperature to one decimal
    float temperature = static_cast<float>(static_cast<int>((getControllerConfig().isMetric?sensors.getTempCByIndex(i):sensors.getTempFByIndex(i)) * 10.)) / 10.;
    // Only send data if temperature has changed and no error
    #if COMPARE_TEMP == 1
    if (lastTemperature[i] != temperature && temperature != -127.00 && temperature != 85.00) {
    #else
    if (temperature != -127.00 && temperature != 85.00) {
    #endif
      // Send in the new temperature
      send(msg0.setSensor(i).set(temperature,1));
      // Save new temperatures for next compare
      lastTemperature[i]=temperature;
    }
  }
  
}

}

void receive(const MyMessage &message)
{
  if (message.type == V_STATUS && message.sensor == 11) {
    // Change relay state
    state1 = message.getBool();
    digitalWrite(RELAY_1, state1?RELAY_ON:RELAY_OFF);
    // Store state in eeprom
    saveState(CHILD_ID_11, state1);
    
   // send(msg11.set(state1));

     // Write some debug info
    Serial.print("Incoming change for sensor:");
    Serial.print(message.sensor);
    Serial.print(", New status: ");
    Serial.println(message.getBool());
  }
  else if (message.type == V_STATUS && message.sensor == 12) {

    state2 = message.getBool();
    digitalWrite(RELAY_2, state2?RELAY_ON:RELAY_OFF);

    saveState(CHILD_ID_12, state2);

   // send(msg12.set(state2));
    
    // Write some debug info
    Serial.print("Incoming change for sensor:");
    Serial.print(message.sensor);
    Serial.print(", New status: ");
    Serial.println(message.getBool());
  }
}

I'm using OneButton library to get different actions when i'm clicking once, twice and holding buttons.

[ArduiSens]

Nofox,

1. The 510 ohm pull up and pull down resistors (between A (D+) and 5V / between B (D-) and ground) are usually mounted on the master side (which is your gateway). Theoretically it would be best to install it in the middle of your bus line.
2. check if your power supply has enough power to feed all your nodes
3. check that all the ground lines of your boards are connected with each other.

[nofox]

@ArduiSens Thanks for your reply! I have found few post here on MYS Forum about biasing rs485 line with pull up and pull down resistors and I will try to do this tomorrow. I'm using standard rs485 module from aliexpress on the gateway side. There are pullups and pulldowns there but they are two 10k resistors, I will change them to 510 as you mentioned.
All of my wired sensors, gateway and RPi are powered form 10A buffered power supply. I've checked voltage on every node. I have 5.25V on power supply pins in the middle of the line and 5.21 on both ends of line. I'm using one twisted pair for Vcc and one for GND. The bus is about 15 meter long form one end to another.
As I mentioned above all of nodes are supplied from one power supply so the grounds are all connected.

[nofox]

Hello again. I've soldered this two pull-ups resistors like @ArduiSens wrote before. Now I think the network works much much better but after 24 hours of using something hangs and i can't turn of the light with buttons and with OpenHab also. I think the gateway freezing because after I reset only gateway all starts to work normal when i'm pressing wall switches. I need to reboot controller because after gateway reset OpenHab won't communicate with the gateway... Please take a look at my gateway sketch:

// Enable debug prints to serial monitor
#define MY_DEBUG

// Enable and select radio type attached
// #define MY_RADIO_NRF24
// #define MY_RADIO_RFM69
#define MY_NODE_ID 0
// Enable RS485 transport layer
#define MY_RS485

// Define this to enables DE-pin management on defined pin
#define MY_RS485_DE_PIN 2

// Set RS485 baud rate to use
#define MY_RS485_BAUD_RATE 9600

// #define MY_GATEWAY_MQTT_CLIENT

// Enable gateway ethernet module type
#define MY_GATEWAY_W5100

// W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
// #define MY_W5100_SPI_EN 4

// Enable Soft SPI for NRF radio (note different radio wiring is required)
// The W5100 ethernet module seems to have a hard time co-operate with
// radio on the same spi bus.
#if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
#define MY_SOFTSPI
#define MY_SOFT_SPI_SCK_PIN 14
#define MY_SOFT_SPI_MISO_PIN 16
#define MY_SOFT_SPI_MOSI_PIN 15
#endif



// When W5100 is connected we have to move CE/CSN pins for NRF radio
// #ifndef MY_RF24_CE_PIN
// #define MY_RF24_CE_PIN 5
// #endif
// #ifndef MY_RF24_CS_PIN
// #define MY_RF24_CS_PIN 6
// #endif

// Enable to UDP
// #define MY_USE_UDP

#define MY_IP_ADDRESS 192,168,0,66   // If this is disabled, DHCP is used to retrieve address
// Renewal period if using DHCP
//#define MY_IP_RENEWAL_INTERVAL 60000
// The port to keep open on node server mode / or port to contact in client mode
#define MY_PORT 5003
// Controller ip address. Enables client mode (default is "server" mode).
// Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
//#define MY_CONTROLLER_IP_ADDRESS 192, 168, 0, 70

// The MAC address can be anything you want but should be unique on your network.
// Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
// Note that most of the Ardunio examples use  "DEAD BEEF FEED" for the MAC address.
#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED

// Set this node's subscribe and publish topic prefix
// #define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway1-out"
// #define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway1-in"

// Set MQTT client id
// #define MY_MQTT_CLIENT_ID "mysensors-1"

// Enable these if your MQTT broker requires usenrame/password
//#define MY_MQTT_USER "username"
//#define MY_MQTT_PASSWORD "password"

// Enable inclusion mode
// #define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
//#define MY_INCLUSION_BUTTON_FEATURE
// Set inclusion mode duration (in seconds)
// #define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN  3

// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300

// Flash leds on rx/tx/err
// Uncomment to override default HW configurations
//#define MY_DEFAULT_ERR_LED_PIN 7  // Error led pin
//#define MY_DEFAULT_RX_LED_PIN  8  // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN  9  // Transmit led pin


#if defined(MY_USE_UDP)
#include <EthernetUdp.h>
#endif
#include <Ethernet.h>
#include <MySensors.h>


void setup()
{
}

void loop()
{
}

[gohan]

@nofox why are you using soft SPI? You don't have a nrf24 radio