Re: Pfeiffer Vacuum TPG 366: No reply within 200 ms

[Abdalla Ahmad via Tech-talk <tech-talk at aps.anl.gov>]

Hi Lewis

We are controlling the TPG366 using stream device protocol. I looked into the device's protocol file, and we had set the timeout as follows

ReplyTimeout = 5000;
ReadTimeout  = 2500;

I think the 200 ms might be too fast for the controller, try increasing the timeout and check if the timeout persists.

Best Regards,

Abdalla.

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of J. Lewis Muir via Tech-talk <tech-talk at aps.anl.gov>
Sent: Thursday, July 9, 2026 2:06 AM
To: EPICS Tech-Talk <tech-talk at aps.anl.gov>
Subject: Pfeiffer Vacuum TPG 366: No reply within 200 ms

Hi, Tech-Talkers!

I'm using the driver at

  github.com/paulscherrerinstitute/TPG366

to control two Pfeiffer Vacuum TPG 366 devices connected via Ethernet,
and it mostly works, but I sometimes get errors on the IOC console like
the following for both devices, and I'm wondering, does anyone know what
might be going wrong and how to fix it?

----
2026/07/08 14:18:08.370669 PFEIFFER2 17ida:Igc2:READ-STATUS: No reply within 200 ms to "SEN<0d>"
2026/07/08 14:28:32.363384 PFEIFFER2 17ida:Igc2:READ-STATUS: No reply within 200 ms to "<05>"
2026/07/08 14:34:40.357193 PFEIFFER2 17ida:Igc2:READ-STATUS: No reply within 200 ms to "UNI,1<0d>"
----

Thanks!

Lewis