Closed aviateur17 closed 2 years ago
Do we want to start thinking about splitting those up into different files?
Absolutely. At the moment I have some work done on a two-way communication branch, but when that is finished or at a stopping point, let's plan on talking about and finalizing the division and organization of the files. I think that a file for each interface (serial, LoRa, MQTT, SD, will be much simpler, and easier to expand.
It would also be useful to somehow find out, if two gateways are in reach for each other. So you can see, if the chain of gateways to a remote location will work.
It would also be useful to somehow find out, if two gateways are in reach for each other. So you can see, if the chain of gateways to a remote location will work.
Yes, it is a good idea but I think this starts to approach a mesh network situation and I don't think that's the intent of this project.
Added code to allow LoRa sensor send ping to LoRa gateway and receive ping reply from LoRa gateway back to the LoRa sensor via SystemPacket cmd_ping.
For the cmd_ping SystemPacket I utilized param as follows: param = 0 is for ping request (Sensor -> Gateway for now) param = 1 is for ping reply (Gateway -> Sensor for now)
gateway output:
sensor output:
fdrs_sensor.h is now 500 lines. fdrs_functions.h is now 1055 lines. Do we want to start thinking about splitting those up into different files? Maybe LoRa stuff in it's own file for each the sensor and the gateway? As we add capabilities the two files above are starting to look more and more similar.