Draft: Allow pepu to configure tcp timeout
On id16a they are using the pepu to do long acquisitions. Everything was working fine at 300,000 points but at 600,000 points the device times out. Ricardo has provided a custom firmware with enough memory to store something like 6M points. It seems an increase in the default (5s) tcp timeout is needed to read back the larger scans. This adds the option to configure the tcp timeout from the pepu yml.
This is not my domain of expertise, i dont know what the effects on the icepap are of exposing this. I'd appreciate someone who knows what they are doing reviewing and testing this properly!
Edited by Stuart Fisher