@rejoe2 said in RS485 nodes stop sending data after some hours or days:

So next step will be to apply @pjr's modified version of MyTransportRS485.cpp...

That should only help in case of collisions.

Wondering if you could check if those "dead" nodes are trying to send anything by attaching USB-RS485 adapter to the bus and check if there is any activity after pressing reset on "dead" node.

Other helpful thing could be a "datalogger" for testing nodes that will die eventually: https://forum.mysensors.org/topic/6340/debug-to-a-sd-card-module

Those 20K resistors are so small factor that removing them might not be necessary but removing extra termination is. I'm also using 600ohm pull-ups and pull-downs in the middle of the bus but I think 1k might also be ok and it needs little less juice from vcc.
This might be helpfull: http://alciro.org/tools/RS-485/RS485-resistor-termination-calculator.jsp

@gohan said in Serial RS485 Gateway stops receiving after some hours or days:

I remember there was a suggestion to modify the rs485 library to send 3 times the header message before sending the payload in order to avoid collisions.

For the library code i did this modification to MyTransportRS485.cpp

Added this to beginning of the lib file:

#if !defined(MY_RS485_SOH_COUNT)
  #define MY_RS485_SOH_COUNT 3
#endif

And in the sending code:

// Start of header by writing multiple SOH
for(byte w=0; w<1; w++) {
    _dev.write(SOH);
}

Changed to this:

// Start of header by writing multiple SOH
for(byte w=0; w<MY_RS485_SOH_COUNT; w++) {
    _dev.write(SOH);
}

I did the selector <> dimmer mapping in lua:

--
-- Heat pump mode selector <> dimmer mapping with lua
--

commandArray = {}

selectorName = 'Pumppu_Mode'
selectorId = '332' -- needed for UpdateDevice
dimmerName = 'Pumppu_ModeSW2'

-- selector -> dimmer
if(devicechanged[selectorName]) then
  iDimLevel = tonumber(otherdevices_svalues[selectorName])
  if(iDimLevel < 60) then -- not needed anymore?
    commandArray[dimmerName]='Set Level '..iDimLevel
  end
end

-- dimmer-> selector. UpdateDevice is not triggering this script again
if (devicechanged[dimmerName]) then
  if (devicechanged[dimmerName] == 'Off') then
    commandArray['UpdateDevice'] = selectorId..'|0|0'
  else
    iCurrentDimLevel = 0
    if(otherdevices[dimmerName] == 'On') then -- can be "On" or something else
      iCurrentDimLevel = tonumber(otherdevices_svalues[dimmerName])
    else
      iCurrentDimLevel = tonumber(string.match(otherdevices[dimmerName], "Set Level: (%d+) %%"))
    end
    
    commandArray['UpdateDevice'] = selectorId..'|'..iCurrentDimLevel..'|'..iCurrentDimLevel
  end
end

return commandArray```

@arduino_89_89 said in Problem with Domoticz:

Hi everyone, I wanted to know how ever whenever the PC reboots, I also change the com port. And why when I break the gateway, are the sensors no longer connected?

What environment? Could this help? https://www.domoticz.com/wiki/Assign_fixed_device_name_to_USB_port

@dbemowsk Yes thats true that domoticz doesnt handle the VARX the way the irrigation code expects. But about the error message written on topic I'm pretty sure it actually is his problem since I'm using domoticz and have faced the same error message..

He stated:
"[Error sending switch command](check device/hardware !)"
"The error comes up when turning on or off."

With default settings RF24_PA_HIGH or RF24_PA_MAX (have to check the default from MyConfig.h) is used and with this setting the radio needs good power source. Especially the clone radios..

So your node can get messages thru to gw but gw cant get them always to node..
Have you added capacitor to your gateway radio? For me this looks like power issue of the radio.
You could try this on your gateway: #define MY_RF24_PA_LEVEL RF24_PA_LOW (or RF24_PA_MIN) before mysensors include.

@kduino said in How to use SoftwareSerial Library?:

Hi PJR,
would you mind explaining me the reason for defining MY_RS485_HWSERIAL?
Thank you,
by kduino

Take a look at MySensors.h:

#elif defined(MY_RS485)
  #if !defined(MY_RS485_HWSERIAL)
    #if defined(__linux__)
      #error You must specify MY_RS485_HWSERIAL for RS485 transport
    #endif
    #include "drivers/AltSoftSerial/AltSoftSerial.cpp"
  #endif
  #include "hal/transport/MyTransportRS485.cpp"
..

If I read this correctly it loads also AltSoftSerial if you dont define MY_RS485_HWSERIAL
Of course I can read this wrong..

@user2684 wow, that was fast! Thanks!

@rakeshpai I can understand that. Not sure about the amount of rs485 users but one at least

Just an idea:
I would try adding:

#elif defined(MY_RS485_SWSERIAL)
SoftwareSerial& _dev = MY_RS485_SWSERIAL;

so it looks like this:

#if defined(__linux__)
SerialPort _dev = SerialPort(MY_RS485_HWSERIAL);
#elif defined(MY_RS485_SWSERIAL)
SoftwareSerial& _dev = MY_RS485_SWSERIAL;
#elif defined(MY_RS485_HWSERIAL)
HardwareSerial& _dev = MY_RS485_HWSERIAL;
#else
AltSoftSerial _dev;
#endif

and in your code define:

#define MY_RS485_HWSERIAL
#define MY_RS485_SWSERIAL mySerial

and see what happens

ps. the #define of MY_RS485_HWSERIAL is still there since I'm not sure what will be missing for serial communication if that is not defined.

Feature request: support for RS485 network!