0

Format for Fixed Quantity

How can I format the Fixed Quantity value since this value has a decimal number more than the value of the UUT. Example:
 
Fixed Quantity = 600.00V
UUT = 599.9V
ERROR = -0.12V
 
And I need the format of the Fixed Quantity value to be equal to the UUT and equal to the ERROR. Example
 
Fixed Quantity = 600.0V
UUT = 599.9V
ERROR = -0.1V
 
thanks for your help
 
Juan Pablo Gutierrez.

14 comments

Date Votes
0
Avatar
Michael Johnston

Are you talking about in your calibration report, with a reported result?

The order of precedence for resolution that MET/CAL looks for what to use is as follows:

  1. Instrument FSC with a value in the Nominal Field (Evaluation Test Type)
  2. MEMC/MEMCX FSC with a value in the Nominal Field
  3. ACC FSC with a vaue in the Nominal Field
  4. SETUP FSC with a value in the Nominal Field
  5. MEMC/MEMCX Tolerance Field which includes a U (units from the nominal field) component

Are you using MEM or MEM1 to fill your nominal field for your evaluations? If you are and you don't have any of the other options filled, MET/CAL tries to "infer" what it thinks it should be. Using TSET UUT_RES = xxxxx should override any of the 5 options I listed there, but the one thing to remember that might be an issue is that UUT_RES is expressed in base units, not reported units. So to get a resolution of 0.001 mV, you would need to use UUT_RES = 0.000001.

Basically, if you are wanting the result of your test to have a resolution of 0.1V, you can either just make sure your Nominal field has that resolution (MEMC 0.0V TOL) or use the TSET FSC to manually set it (TSET UUT_RES = 0.1).

 

0
Avatar
Juan Pablo Gutierrez

Thanks for answering. The verification I am performing is from a Fluke Insulation Tester 1507 and the example test I show in the attached image is a continuous voltage check. To do this test I use the standard 5520 and at its nominal value I put 3.0V for the first measurement point. So the resolution of the UUT would be 0.1V.

 

But in the attached image it is shown that the True Value column appears with a decimal more than in the Test result column. I need the True Value column and the Error Column to be the same as the UUT resolution. Example:

 

True Value = 3.0V

Test Result = 3.2V

Error = 0.2V

Attachment not imported: report.png
0
Avatar
Michael Johnston

That table is being generated by MET/CAL? Or are you trying to create a procedure and have it match that table and fix the resolution aspect?

Using the correct resolution in each field of the procedure code should ensure that it's correct in the results. For example:

         5520   3.0   V                                                 N  2W
#[Code to collect UUT reading.]
         MEMCX        3.0V           0.5U

I just used 0.5V as the spec, since I don't know what it is. But if both the Nominal fields and the tolerance field all have the same resolution, it should show up correctly on the report.

If you're using variables to fill out an external Excel sheet or something, you might have to format those string variables with the MATH FSC. There's a writeup in the Help file, but basically, to format those numbers, if for example your value was stored in MEM, you'd do:

         MATH         MEM = FMT(MEM,"%3.1f")

If the value of MEM were 3.11, for example, that line would format it to 3.1.

The syntax of the FMT code is "%w.df" where w is the total minimum width of the result you want, including decimal, and d id the number of decimal digits you want. The f at the end maked it fixed-point decimals instead of floating.

 

0
Avatar
Juan Pablo Gutierrez

The report is generated by METTEAM through Crystal report. The procedure for the UUT I am creating it. A fraction of the code is as follows:

 

    1.014  TARGET       -m

  1.015  MESS         INGRESE LA LECTURA DEL 1507

  1.016  5520         3.0V           0.3U                                  2W

 

  2.001  TARGET       -m

  2.002  MESS         INGRESE LA LECTURA DEL 1507

  2.003  5520         8.0V           0.5U                                  2W

 

Can the difference in decimals be produced by Crystal Report?

0
Avatar
Michael Johnston

Try this instead:

         TARGET       -m
         5520         3.0V                                              N  2W
         MEMI         INGRESE LA LECTURA DEL 1507
         MEMCX        3.0V           0.3U

And if that doesn't fix it, try:

         TARGET       -m
         5520         3.0V                                              N  2W
         MEMI         INGRESE LA LECTURA DEL 1507
         MATH         MEM = FMT(MEM,"%3.1f")
         MEMCX        3.0V           0.3U

Let me know if that fixes it.

 

 

0
Avatar
Juan Pablo Gutierrez

I tried the two solutions that you gave me but I did not change the values. Continues to the same decimal places.

 

In the attached image I show the values that are seen in metteam. The FIXQ column and ERROR_ VALUE same appear with two decimal places but the VARQ column is at the correct resolution.

Attachment not imported: results.png
0
Avatar
Michael Johnston

Ok, this should fix the trule value at least. Add the following line before the evaluation step:

         FMT          FIXQ = %.1f

Your report template is using the database field FIXQ as the true value. The part I'm not sure about is how it will affect the error. I'm not even sure how you're getting that error value, when you're entering 3.2 as the UUT reading and the true value is 3.00. Are you entering more digits in the reading than you're reporting?

 

0
Avatar
Juan Pablo Gutierrez

It works only for the FIXQ column but not for the ERROR_VALUE column.

The UUT values are 4 readings and are as follows:

 

For the point of 3.0V = 3.1V, 3.2V, 3.1V, 3.2V

For the point of 8.0V = 8.1V, 8.2V, 8.1V, 8.2V

 

Will work if I put in the code  FMT ERROR_VALUE =% .1f

Attachment not imported: results2.png
0
Avatar
Michael Johnston

Ah, you're using an average. Got it.

The help file doesn't list that variable as being allowed with the FMT FSC, so I wasn't sure.

Try "ERR" and "TOL_ERR" and see if either works.

0
Avatar
David Weir-Marshall

Just wanted to chime in and say thanks Michael!

This is something that's been bugging me, and this answer saves me the hassle of compensating in crystal reports.

0
Avatar
Michael Johnston

Glad it helped you out! I typically just let the nominal field be what it's going to be and only worry about the result itself being formatted correctly along with the tolerances, so I had to go to the help file for some of this.

0
Avatar
David Weir-Marshall

We were doing likewise, but our accreditation body decided that they didn't like it any more...

Thanks again.

0
Avatar
Juan Pablo Gutierrez
Thank you so much Michael. Resulted the ERR command.
 
Thank you very much for your help and your time
0
Avatar
Michael Johnston

No problem! Glad we were able to work through it. I learned something new as well.

Please sign in to leave a comment.