RE: pfeiffer TPG 366 Maxiguage Epics support

["Oram, Dominic \(STFC,RAL,ISIS\) via Tech-talk" <tech-talk at aps.anl.gov>]

Hi Vishnu, Florian,

 

We also have a number of TPGs, of various models.

 

The code is very similar to Florian’s but also does some logic for reading the units from the device.

 

The code can be found at https://github.com/ISISComputingGroup/EPICS-TPG/tree/master/TPGSup, for the unit setting part it also depends on https://github.com/ISISComputingGroup/EPICS-utilities/blob/master/utilitiesApp/Db/unit_setter.template but this is optional.

 

Feel free to get in touch if you need help setting it up.

 

Thanks,

Dom

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Florian Feldbauer via Tech-talk
Sent: 24 February 2021 09:44
To: tech-talk at aps.anl.gov
Subject: Re: pfeiffer TPG 366 Maxiguage Epics support

 

Hey Vishnu,

 

we use a lot of Pfeiffer equipment and usually use StreamDevice + Asyn for it.
Attached are examples for the TPG 256.

 

HTH,
Florian

 

On 2/24/21 10:40 AM, Vishnu Patel via Tech-talk wrote:

Dear All,

     I have Pfeiffer Vacuum gauge  controller TPG366. I would like to read data on serial port(RS-232). 

 

Any one using TPG 366 epics driver and can share with me, I will be very thankful.

 

Thank you

Vishnu

-- 

Ruhr-Universität Bochum

AG der Experimentalphysik I

Dr. Florian Feldbauer

NB 2/131 / Fach 125

Universitätsstr. 150

D-44801 Bochum

Office: NB 2/134

Phone:  (+49)234 / 32-23563

Fax:    (+49)234 / 32-14170

https://paluma.ruhr-uni-bochum.de

This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.