Linux Raspberry UDP network and serial communication component
Budget: $250 – $750 USD
*Please include descriptions of 1-2 most relevant projects delivered.
*Also as part of the offer please provide comments to the 2 questions at the end of this description
Linux Raspberry UDP network and serial communication component
1. Product to be done: a basic communication component handling low-volume, ca. 20-100-byte command messages with rather relaxed performance requirements. The messages will be coming on a non-regular basis from a few clients over a Wi-Fi local network, typically say 2 clients. There is no need to confirm the messages in either way. Consequently it seems that UDP is the right protocol to be used (to be confirmed by the contractor).
2. The server should also support its part of a detection mechanism that should allow the clients to automatically detect the address IP of the server (both clients and server on the same router), like UPnP or even better a custom method, possibly simple but reliable.
3. All the clients that have sent a message to the server should be registered in a simple IP list. Then every message from one client should be automatically re-sent over Wi-Fi/UDP to all registered IP-s.
4. Additionally the component should handle low-level basic RX and TX interfacing over one UART and one I2C port.
5. The target HW environment will be Raspberry Pi Zero 2W with Linux. The sending and receiving code should execute possibly in the background in order to allow to use the host Linux platform to perform other processing in parallel.
6. The component should be 2-way and use simple circular queues to buffer RX and TX messages. I have attached a draft, base class Qued with a very simple own implementation of such a circular message queue. The class needs to be supplemented with missing code for the UDP interface handling
The contractor can freely propose changes or a different implementation of this queue mechanism.
I also attached a separate .docx with more detailed description of server functions including server UDP RX queue handling that includes use of UART TX and I2C RX/TX interfacing.
As part of the offer I would like to ask for your proposition of the approach to the component development, in particular:
1) What Wi-Fi network mechanism do you recommend to use for IP server address detection at the clients ?
2) The preferred project delivery language is C/C++. Please describe your proposed approach to development - what dev environment tools you propose to use for the project work and how to do testing ?
What tools and knowledge I myself would need to possess in order to be able to maintain and modify the project on my own after it is completed (at the moment I have pretty good knowledge of C/C++).
*Also as part of the offer please provide comments to the 2 questions at the end of this description
Linux Raspberry UDP network and serial communication component
1. Product to be done: a basic communication component handling low-volume, ca. 20-100-byte command messages with rather relaxed performance requirements. The messages will be coming on a non-regular basis from a few clients over a Wi-Fi local network, typically say 2 clients. There is no need to confirm the messages in either way. Consequently it seems that UDP is the right protocol to be used (to be confirmed by the contractor).
2. The server should also support its part of a detection mechanism that should allow the clients to automatically detect the address IP of the server (both clients and server on the same router), like UPnP or even better a custom method, possibly simple but reliable.
3. All the clients that have sent a message to the server should be registered in a simple IP list. Then every message from one client should be automatically re-sent over Wi-Fi/UDP to all registered IP-s.
4. Additionally the component should handle low-level basic RX and TX interfacing over one UART and one I2C port.
5. The target HW environment will be Raspberry Pi Zero 2W with Linux. The sending and receiving code should execute possibly in the background in order to allow to use the host Linux platform to perform other processing in parallel.
6. The component should be 2-way and use simple circular queues to buffer RX and TX messages. I have attached a draft, base class Qued with a very simple own implementation of such a circular message queue. The class needs to be supplemented with missing code for the UDP interface handling
The contractor can freely propose changes or a different implementation of this queue mechanism.
I also attached a separate .docx with more detailed description of server functions including server UDP RX queue handling that includes use of UART TX and I2C RX/TX interfacing.
As part of the offer I would like to ask for your proposition of the approach to the component development, in particular:
1) What Wi-Fi network mechanism do you recommend to use for IP server address detection at the clients ?
2) The preferred project delivery language is C/C++. Please describe your proposed approach to development - what dev environment tools you propose to use for the project work and how to do testing ?
What tools and knowledge I myself would need to possess in order to be able to maintain and modify the project on my own after it is completed (at the moment I have pretty good knowledge of C/C++).