Poor performance while editing and sending

[MauriceDuteau]

Brian also reports that he spends a lot of time waiting for the program to be sent, getting errors and waiting a long time for retries.
This needs to be improved. Dont wait so long for a retry. Don't lock the user interface while retrying.
Anything we can do to improve the performance over slow/poor connections, we must do it.

[Fance]

The root cause of the issue may lie in delayed device responses or the network environment. It is difficult to handle this in a background thread, as background threads are mostly used for processing large batches of read/write data. There is no significant way to improve the operation of reading from or writing to a single device.
communication quality is very poor here, users must wait for a period of time to receive the result before proceeding with the next read/write operation.
https://github.com/user-attachments/assets/787a37b2-5ab9-40bc-9257-cab838797a8b

[MauriceDuteau]

The response looks great in your test, Brian mentioned his environment had 90% communications health. We need to simulate that and see what we can do to improve responsiveness. Try programming on a subnet device for example. I know you give devices a lot of time to respond, you can reduce that. Also you can do a resume rather than start again from the beginning.