So I have thought a bit about how I want the Ethernet Tester program to work and here are a few insights into what’s to come.
For starters, I’m breaking up the program into different server “Threads”. This will allow for more modular operations. Said threads would include Display, Interactions, HTTP config + access and iperf3.
Secondly, I’m creating an HTTP server for configuration and remote results access. This combined with the ability to configure the wireless through HTTP will allow the use of devices without an actual hardware display!
The HTTP configuration pages will eventually have options to do things like customize iperf3 settings, configure unit between display & secondary server, swap between supported displays, etc.
Right now I’m working on Refactoring and creating the new foundation to support these new features. This program is MUCH smaller than my Sensor program, so I don’t expect it to take too long. That being said, I will be playing around with things to see both my options and what works best. For instance, I’m going to be including all the required python files for the supported displays so you don’t need to use pip to get them (and should remain compatible regardless of how they change things upstream).
Once I get things working, I’ll post on the Raspberry Forums.
0 Comments.