3 ms·
Essentially my entire software career has been on embedded systems and this problem is something I've given a lot of thought to, in terms of how much work we ca
by HeyLaughingBoy 13y ago
Essentially my entire software career has been on embedded systems and this problem is something I've given a lot of thought to, in terms of how much work we can without needing to be in the office.
The machines we build are big. As in $100,000 build cost and almost half a ton of aluminum and plastic big. Obviously not something each employee can take home to work with remotely.
Since our control system hardware is pretty high level (Pentium-processor SBC scale), we have a lot of leeway in terms of footprint. So we simulate as much of the I/O as we can. This lets us do a lot of development without each developer needing the actual hardware for most testing. By abstracting the hardware away in this manner, the development becomes similar to server-type software dev that can be done on a desktop.
It doesn't solve all the problems, but we can do probably 80% of our development work on our laptops and only need to do some critical testing on the actual machine itself.
Where the need to be in the office really hits is the interactions with electrical and mechanical engineers. While they have drawing and specs in electronic format, the discussions usually rely on everyone being colocated. I've found it is very difficult to explain designs even over good video conference systems.