Closed benedekh closed 8 years ago
Previously we have agreed with @hegyibalint that the implementation remains on the Arduino platform, but we should attach the device to a raspberry pi over uart instead having an individual ethernet connection. Therefore everything remains the same (programming language, device, even the algorithm) except the communication form, which will be implemented on the raspberry pi.
On Tue, 13 Sep 2016, 10:07 Benedek Horvath, notifications@github.com wrote:
Assigned #42 https://github.com/FTSRG/BME-MODES3/issues/42 to @zsoltmazlo https://github.com/zsoltmazlo.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/FTSRG/BME-MODES3/issues/42#event-787180988, or mute the thread https://github.com/notifications/unsubscribe-auth/AF0bSC0IIOO6ID6xoFUdbRSsGzZDLt3nks5qplmzgaJpZM4J7Zdq .
Üdvözlettel, Mázló Zsolt
As I see the ticket cannot be closed yet, because:
So far this component was deployed on Arduino as a C++ code. It communicated with the network through MQTT. The objective was to query the section occupancies through RJ45 ('telephone cable') using S88 protocol and transfer this information (sections occupancy vector) through the network.
Main questions regarding this issue: