Jump to content

look for MKS pressure transducer readout PDR 2000 driver


fanyf06

Recommended Posts

I've used MKS transducers before and have tied directly into the sensor, saving a fair amount of money since the DAQ device they sell is fairly expensive. It is pretty straightforward to do the DAQ yourself. Otherwise, their device responds to rs-232 commands that should be straightforward to implement with Visa calls. You probably won't find a driver since it's fairly straightforward serial communication, though this post from the darkside suggests that they may provide something upon request.

Link to comment
  • 4 months later...
  • 8 years later...

Hi Jordan and Colin,

 

Thanks for your support. I'm new to MKS PDR 2000 Dual capacitance Manometer. I am familiar with serial communication and have used it often when communicating with a DB9 serial port on a computer. However, this controller has a DB15 female connector, so I'm confused on what exactly I should be doing to interface it with the laptop (as laptop doesn't have a DB15 serial connector port)?

I have a USB to DB9 (male) serial converter, which I then to a small box which connects three wires (Rx, Tx and Gnd) of DB9 connector to the DB15 connector. And then this connector goes to the female DB15 connector of the controller. I'm reading the manual and connecting the pin 7,8 and 9 (of DB15) to pin 3,2 and 5 (of DB9 connector). But, this doesn't seem to be working as I can't get the controller detected in the computer. I can only detect the USB to serial converter. 

Do you suggest to connect the controller directly to a PC with DB15 port (without USB to DB9 and DB9 to DB15 conversion)? 

Once I have the controller's connection established, then I think it is straightforward as I can use HyperTerminal for serial communication. 

It would be great if you could have some inputs for this problem. Please let me know your inputs.

 

Thanks in advance.

Link to comment
11 hours ago, Jaykumar Vaidya said:

I have a USB to DB9 (male) serial converter, which I then to a small box which connects three wires (Rx, Tx and Gnd) of DB9 connector to the DB15 connector. And then this connector goes to the female DB15 connector of the controller. I'm reading the manual and connecting the pin 7,8 and 9 (of DB15) to pin 3,2 and 5 (of DB9 connector). But, this doesn't seem to be working as I can't get the controller detected in the computer. I can only detect the USB to serial converter. 

According to this link mentioned in the post before yours, you got that wrong. pin 7, 8, 9 are the serial port signals on the DB9 connector. The DB15 connector has them on pin  1, 2, 4!

Link to comment

Thank you for your reply. The link that you are referring to is for MKS 900 series transducer but I am working with PDR 2000 controller. But I got it working by swapping the Rx and Tx terminals. So now, pin 7,8 and 9 (of DB15) to pin 2,3 and 5 (of DB9 connector) works

Link to comment
6 hours ago, Jaykumar Vaidya said:

Thank you for your reply. The link that you are referring to is for MKS 900 series transducer but I am working with PDR 2000 controller. But I got it working by swapping the Rx and Tx terminals. So now, pin 7,8 and 9 (of DB15) to pin 2,3 and 5 (of DB9 connector) works

Sounds like a masterpiece of engineering. Use a non-standard connector, resp. if they use the DB9 on the other device, connect its pins in a different way than standard, and then use for every new device again a different pinout. Someone must think selling custom cables is the way to earn lots of money! 😀

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By Porter
      View File Plasmionique Modbus Master
      This package contains the Plasmionique Modbus Master library for LabVIEW.
      It supports RTU, ASCII and TCP modes with the following function codes:
      0x01 - Read Coils
      0x02 - Read Discrete Inputs
      0x03 - Read Holding Registers
      0x04 - Read Input Registers
      0x05 - Write Single Coil
      0x06 - Write Single Register
      0x07 - Read Exception Status
      0x0F - Write Multiple Coils
      0x10 - Write Multiple Registers
      0x16 - Mask Write Register
      0x17 - Read/Write Multiple Registers
      0x2B/0x0E - Read Device Identification
      Other features include:
      - Sharing a COM port across multiple Modbus sessions using VISA locks (10 second timeout).
      - Sharing a Modbus session across multiple communication loops.
      - TCP transaction ID handling to ensure that requests and responses are matched up correctly in case responses are received out of order.
      - Modbus Comm Tester, available through the "Tools->Plasmionique" menu, for testing communication with a slave device without writing any code. 
      - Detailed help document available through the "Help->Plasmionique" menu.
      Examples are included in "<LabVIEW>\examples\Plasmionique\MB Master\":
      MB_Master Comm Tester.vi: Demonstrates usage of API to open/close connection and communicate with a Modbus slave device. MB_Master Multiple Sessions.vi: Demonstrates usage of API to open concurrent Modbus sessions. MB_Master Simple Serial.vi: Demonstrates polling of a single input register over serial line. Download a copy of the user guide here: MB_Master - User Guide.pdf
      Note that Version 1.3.4 of this library has been certified compatible with LabVIEW and has been released on the LabVIEW Tools Network: http://sine.ni.com/nips/cds/view/p/lang/en/nid/214230
      The most recent version of this library will always be released on LAVA first before going through NI's certification process.
      ***This project is now available on GitHub: https://github.com/rfporter/Modbus-Master
      Submitter Porter Submitted 04/01/2016 Category LabVIEW Tools Network Certified LabVIEW Version 2012 License Type BSD (Most common)  
    • By Porter
      This package contains the Plasmionique Modbus Master library for LabVIEW.
      It supports RTU, ASCII and TCP modes with the following function codes:
      0x01 - Read Coils
      0x02 - Read Discrete Inputs
      0x03 - Read Holding Registers
      0x04 - Read Input Registers
      0x05 - Write Single Coil
      0x06 - Write Single Register
      0x07 - Read Exception Status
      0x0F - Write Multiple Coils
      0x10 - Write Multiple Registers
      0x16 - Mask Write Register
      0x17 - Read/Write Multiple Registers
      0x2B/0x0E - Read Device Identification
      Other features include:
      - Sharing a COM port across multiple Modbus sessions using VISA locks (10 second timeout).
      - Sharing a Modbus session across multiple communication loops.
      - TCP transaction ID handling to ensure that requests and responses are matched up correctly in case responses are received out of order.
      - Modbus Comm Tester, available through the "Tools->Plasmionique" menu, for testing communication with a slave device without writing any code. 
      - Detailed help document available through the "Help->Plasmionique" menu.
      Examples are included in "<LabVIEW>\examples\Plasmionique\MB Master\":
      MB_Master Comm Tester.vi: Demonstrates usage of API to open/close connection and communicate with a Modbus slave device. MB_Master Multiple Sessions.vi: Demonstrates usage of API to open concurrent Modbus sessions. MB_Master Simple Serial.vi: Demonstrates polling of a single input register over serial line. Download a copy of the user guide here: MB_Master - User Guide.pdf
      Note that Version 1.3.4 of this library has been certified compatible with LabVIEW and has been released on the LabVIEW Tools Network: http://sine.ni.com/nips/cds/view/p/lang/en/nid/214230
      The most recent version of this library will always be released on LAVA first before going through NI's certification process.
      ***This project is now available on GitHub: https://github.com/rfporter/Modbus-Master
    • By szewczak
      I wanted to cross post metux's discovery here asap, and have a separate discussion.
      Metux's original post:
      The recent Linux driver package introduces a CRITICAL security vulnerability:
       
      http://www.ni.com/download/ni-linux-device-drivers-2018/7664/en/
       
      It adds additional yum/zypper repos, but explicitly disabling package signing and using unencrypted HTTP transport. That way, it's pretty trivial to completely takeover the affected systems, by injecting malicious packages.
       
       
      DO NOT INSTALL THIS BROKEN SOFTWARE - IT IS DANGEROUS !
       
      CERT and BSI are already notified.
       
       
       
       
       
    • By Benoit
      View File 1-Wire.zip
      This tool-set gives access to all the 1-wire TMEX functionality.
      I was able to access 1-wire memory with this library.
      It has all the basic VI to allow communication with any 1-wire device on the market.
      It needs to be used in a project so the selection of the .dll 64 bit or 32 bit is done automatically.
      It works with the usb and the serial 1-wire adapter.
      Submitter Benoit Submitted 06/01/2018 Category Hardware LabVIEW Version  
    • By Benoit
      This tool-set gives access to all the 1-wire TMEX functionality.
      I was able to access 1-wire memory with this library.
      It has all the basic VI to allow communication with any 1-wire device on the market.
      It needs to be used in a project so the selection of the .dll 64 bit or 32 bit is done automatically.
      It works with the usb and the serial 1-wire adapter.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.