@paweld Hi, I was just reading the "Limitations" section on the official page: https://www.arduino.cc/en/Reference/softwareSerial
You are using a "Mega" board so it seems that with the SoftwareSerial library you can only use a subset of the available pins (actually the limitation is for the RX pin).

Just to confirm, could you try to use different pins as described in the "Limitations"?

Max

Hi,
did you check if those channels are already busy? maybe there are WiFi Access Points that use the same frequencies.

Max

@parachutesj
Hi,
nrf24 radios share the same frequencies of wifi spot.
Did you check the presence of any WiFi spot, repeater or any other source of signal that could interfer with nrf24 modules?
You could check the Wifi spectrum with your smartphone. There are a lot of apps that analyze the frequencies.
Just an example: https://play.google.com/store/apps/details?id=cz.webprovider.wifianalyzer

Hi,
I haven't found any specific documentation but looking in the MYSBootloader's code I found this two checks in HW.h (https://github.com/mysensors/MySensorsBootloaderRF24/blob/development/HW.h)

#if defined(SPI_PINS_CE9_CSN10)
..
#elif defined(SPI_PINS_CSN7_CE8)
..
#endif

does it mean that those PINs (9+10 or 7+8) are the only options to have MYSBootloader on Arduino boards? (obviously without modifying the code and recompiling..)

thanks
Max

Hi all,
I'm planning to use MYSBootloader with a network of nrf24 modules. I have just ordered an USBasp, but I have a doubt..

I was changing my sketches to free a PWM pin and I choose to assign MY_RF24_CE_PIN to pin 14 (instead of pin 9).
I think that this could cause some problem with MYSBootloader configuration.
Isn't it?

What are the requirements to install MYSBootloader?

Thanks
Max

Hi all,
this is my first post and I would like to congratulate you for this wonderful site
I am also interested in a wired network and I know that rs485 bus has some limitations.. but rs485 modules are also really cheap (and I have already bought a lot of them ).

Just an idea to handling the bus.. why don't you use a different size for the first message that Leo propose to check the collision? The size should follow a priority: maximum priority for Controller/Gateway, less priority for Repeater, lower priority for Sensor nodes.
For example
3 start bytes - Controller/Gateway
2 start bytes - Repeater
1 start byte - Sensor Node
In this way if a sensor and the Gateway start sending the byte in the same time, the gateway wins.

This could help also with sensors that need high priority, for example alarms. In this case we only need to change the priority of the sensor that send the message (maybe with a new option on the send() command .. like the ack option).

Max