... using two Gateways
-
@zzz-teo - check this out: https://forum.mysensors.org/topic/5455/bridge-between-rf24-and-rs485
-
Hello,
no bridge yet as far as i know. Mysensors allows one transport layer per gw for the moment.
It would need some software work though, like handling well both transport without missing packets, queue, more ram and also flash for fw. All of this for one mcu. Better use a good mcu for this.
Or it's very simple to use a cheap rpi like and use node-red for routing imho -
Hello,
no bridge yet as far as i know. Mysensors allows one transport layer per gw for the moment.
It would need some software work though, like handling well both transport without missing packets, queue, more ram and also flash for fw. All of this for one mcu. Better use a good mcu for this.
Or it's very simple to use a cheap rpi like and use node-red for routing imho -
@gohan
hehe. It depends on the angle of view. Simple for end user, but not for the dev :)I explained it above, but actually the lib works like this, 1x transport.
- This needs a few more coding abstraction layers to get that. Taking in account current todolist priorities, dev, testing, and time ;)
- better with an rtos too, as most common mcu are one core, it needs to handle well all the tasks involved..and the lib is not completely ready for this too.
- Lot of things to think for doing this (the message routing and so on) ..or no reliable comm.
That's why, i said, for the moment it may be easier to use an rpi for this even if i understood the point ;)
-
@gohan not without some sort of filtering
The two gateways would have the same id (0) and forwarding messages with destination 0 would probably confuse the other gateway.
There would probably also be some extra routing mechanism, to be able to handle routing between the two networks. To nodes on "network 1", it would have to look like gateway 2 is a repeater which is routing messages for all nodes in "network 2", and the other way around. -
@gohan not without some sort of filtering
The two gateways would have the same id (0) and forwarding messages with destination 0 would probably confuse the other gateway.
There would probably also be some extra routing mechanism, to be able to handle routing between the two networks. To nodes on "network 1", it would have to look like gateway 2 is a repeater which is routing messages for all nodes in "network 2", and the other way around. -
@gohan not without some sort of filtering
The two gateways would have the same id (0) and forwarding messages with destination 0 would probably confuse the other gateway.
There would probably also be some extra routing mechanism, to be able to handle routing between the two networks. To nodes on "network 1", it would have to look like gateway 2 is a repeater which is routing messages for all nodes in "network 2", and the other way around.@mfalkvidd
hmm... that is more complicated than i thought!
seems that need a repeater NRF to RS485 to handle the "INTERNAL" trafic also and not two Gateways ...:confused: :dizzy_face: -
@mfalkvidd
hmm... that is more complicated than i thought!
seems that need a repeater NRF to RS485 to handle the "INTERNAL" trafic also and not two Gateways ...:confused: :dizzy_face: -
@mfalkvidd
... sure! and since i'm not qualified for such task, hope this topic to alert someone and build it! -
@mfalkvidd
hmm... that is more complicated than i thought!
seems that need a repeater NRF to RS485 to handle the "INTERNAL" trafic also and not two Gateways ...:confused: :dizzy_face: -
@gohan
... yes this is the only solution ... but using long range modules the network is exposed to neighborhoods and may someone be motivated to play with it!
By using RS485 backbone the exposed level is reduced. (as well as EMI exposure).
... and by using repeaters may not be stable due to area division by Slabs.