Views:

Setting up COMPASS for Pressure to read a Heise PTE-1 calibrator (works with PTE-2) also

Set up a basic DUT with remote interface

This setup was created for a PTE-1 with 100 psi and 15 inH2O modules in the module1 and module2 ports respectively. This setup is for the 100 psi module in the module1 port. These same instructions apply to any module in the module1 port. Just change the labels and range information for other range modules.

Instructions are at the end to setup the 15 inH2O module. These would apply to any module in the module2 port.

 

Calibration tab settings are optional but you can specify the test to run if you like

 

The communications tab can be setup like this.  Make sure you set up the COM port assignment to match your computer (COM1 in this example). See the PTE-1 Operating Manual, Section 19.0 RS232 Interface General Information, for instructions on how to setup the RS232 interface. See the PTE-2 manual and the Heise website to setup the USB COM port and driver for it.

mceclip0.png

The remote commands to read the output of the PTE-1 are setup under the <Edit Commands> button located in the lower right hand corner of the above window. In this example the command that has been setup in the PTE-1 so that it will reply is “P” (ASCII character 80). See the PTE-1 Operating Manual, Section 19.4 “Setup of the RS232 Interface in the Inquiry Mode”, for instructions on how to setup the PTE-1 in Inquiry Mode to reply to a specified character. See Section 19.4 for details on Inquiry Mode.

The default command for the PTE-2 is the carriage return (Enter key on a keyboard). It is suggested to change this to a character like P in the PTE-2 setup menus. See Section 15 m.iv in the PTE-2 manual.

Note that the reply will include the measurements from both module ports, regardless if modules are installed in them or not. COMPASS for Pressure will only use the first reading (module1) unless directed otherwise (see instructions for module2 port at the end of this document).

The Global Settings tab is optional but can be used to add a delay in milliseconds if desired (or necessary)

 

The Output tab should look like this. Edit as necessary.

The Comment tab is optional

 

Verify communications

It’s a good idea to use the Remote Communications tool (access by the [Tools, Remote Communications menu) to first check your COM port setups before running a test.  This allows you to make sure that communication exists between your Heise PTE-1 and your computer. In the below example are replies on successive lines;

when both modules are installed
when only module2 is installed
when only module1 is installed

See more communications troubleshooting information below the module2 setup info below

Setup module2

If you have already setup module1 then copy that DUT setup by pressing the copy button when the module1 setup screen is open in COMPASS for Pressure,

For advanced COMPASS for Pressure users you can make an Advanced DUT and have each module be a different output.

These instructions apply to any module in the module2 port. Just change the labels and range information for other range modules.

The reply from the PTE-1 will include the measurements from both module ports, regardless if modules are installed in them or not. If you want to use the reply from the second module enter 15 in the “Manipulate Response” entry box. This will cause COMPASS for Pressure to skip the first 15 characters in the reply (the pressure reading from the first module.) Depending whether one or two modules are installed; the resolution, range and units of the modules; you may have to use a number other than 15.

Use the remote communications tool to try and determine how many characters to strip (but you can’t strip characters or “Manipulate reply” in the Remote Communications tool). Run a test to determine if it works. Activate the Interface Spy to see what command is being sent and what the reply is. Search for “Device Output Run Screen” in the COMPASS Help File and then view the “Spy Windows” section on that page. Here’s an example with the Device Output Run Screen and the Spy Window while running a Manual Test.