Hi! I often write code using sockets, and when I need to upload an updated program to the robot, I check the "Kill background process", and due to the presence of timeouts in the program, KIDE does not have time to wait for the PCABORT command to act and returns an error. It would be more convenient if you could set your own timeout for waiting for the PCABORT command before sending the PCKILL command.
What do yo think about that?

Hi!

Zitat von dm.bogachev im Beitrag #1

---

Hi! I often write code using sockets, and when I need to upload an updated program to the robot, I check the "Kill background process", and due to the presence of timeouts in the program, KIDE does not have time to wait for the PCABORT command to act and returns an error. It would be more convenient if you could set your own timeout for waiting for the PCABORT command before sending the PCKILL command.
What do yo think about that?

---

        if (cycl > 4 && sw.ElapsedMilliseconds > 2000)
          break;
 

Of cause the "2000" can also be a variable in config.xml.

I added a new configuration value in "config.xml" called "AbortKillTimeoutMs".