I have a system like the image shows. Now instead of it being connected with an Ethernet cable, it is going to be wireless.
SBC's represent Raspberry Pi's.
SBC0 reads the data all the time and is supposed to send it to the other
SBC1. My options are to implement a time/event or mix both functions in the
SBC0. If it is a time trigger, then based on the interval chosen, the data from the sensor will be sent constantly even if the temp is
0c. With event trigger, it will only send the data when it meets the right condition. Lastly, a mix uses both, so data will only be sent if the condition is met for the duration of that condition, and the data would be sent based on the time interval that is chosen.
This is all done in packet tracer and using
I have concluded that a time trigger would cost a lot on the network traffic and instead use a triggered system, but then the issue was that when the desired condition for the triggered system was met, the system would spam constantly. I figured out that maybe it is best to use a mix of both where the data won't send to the primary system if it is not above
24 C, and if that is maintained, it will send the sensor's data every
I would love it if anyone could give me feedback on this, is my reasoning completely wrong or have I messed something up, and if it should be triggered or timed instead of a mix of both. For a system like this, what is the best interval
2s or more?
SBC0reads the data from the temp sensor all the time. That data is then sent to the other
SBC1. I am conflicted with how that data should be sent, in the question above I determined that a timed trigger was expensive on the network and pointless because the data would send temp data that we are not interested in, that why I think it it either event or an mix of both. The alarm/fan are just examples in Packet tracer