Measure Error: UJO_READ_EXCEPTION_018

Hi All
I am facing an issue where when I select QTD measure, it gives me error
Bad request.
Server message:
code: UJO_READ_EXCEPTION_018
severity: error
description: MDX statement error: table config for index <TIME DIM TECH NAME> is not valid
log id: 051Md38L7jEgmRSwYcMD3G
DATAVALUE:table config for index <TIME DIM TECH NAME> is not valid
MDX:
V1:table config for index <TIME DIM TECH NAME> is not valid
V3:
V4:
There is no error in UJA_DATA_CHECKER but the same error comes when I try UJA_REFRESH_DIM_CACHE
table config for index <TIME DIM TECH NAME> is not valid.
I have checked in UJA_MAINTAIN_MEASURE_FORMULA and the Measure formulas for all measures are same as environmentshell.
Can you please suggest the possible cause and resolution of this.
we are on
SAPK-80103INCPMBPC
SAPK-10203INPOASBC
(Checked the recent thread about the similar issue, but measure formula for us is not changed from standard)
-SM

Here is the TIME dimension members for one year (couldnt post the screenshot image):
ID
Description
STORED_CALC
Base Period
Level
MONTHNUM
Period
PERIOD_END
STYLE
TIMEID
Year
PARENTH1
2013.TOTAL
2013.TOTAL
0
YEAR
12
TOTAL
20130005
2013
2013.Q1
2013.Q1
0
QUARTER
3
Q1
20130001
2013
2013.TOTAL
2013.P01
2013.JAN
0
MONTH
1
JAN
Jan26 2013
20130100
2013
2013.Q1
2013.P02
2013.FEB
0
MONTH
2
FEB
Feb23 2013
20130200
2013
2013.Q1
2013.P03
2013.MAR
0
MONTH
3
MAR
Mar30 2013
20130300
2013
2013.Q1
2013.Q2
2013.Q2
0
QUARTER
6
Q2
20130002
2013
2013.TOTAL
2013.P04
2013.APR
0
MONTH
4
APR
Apr27 2013
20130400
2013
2013.Q2
2013.P05
2013.MAY
0
MONTH
5
MAY
May25 2013
20130500
2013
2013.Q2
2013.P06
2013.JUN
0
MONTH
6
JUN
Jun29 2013
20130600
2013
2013.Q2
2013.Q3
2013.Q3
0
QUARTER
9
Q3
20130003
2013
2013.TOTAL
2013.P07
2013.JUL
0
MONTH
7
JUL
Jul27 2013
20130700
2013
2013.Q3
2013.P08
2013.AUG
0
MONTH
8
AUG
Aug24 2013
20130800
2013
2013.Q3
2013.P09
2013.SEP
0
MONTH
9
SEP
Sep28 2013
20130900
2013
2013.Q3
2013.Q4
2013.Q4
0
QUARTER
12
Q4
20130004
2013
2013.TOTAL
2013.P10
2013.OCT
0
MONTH
10
OCT
Oct26 2013
20131000
2013
2013.Q4
2013.P11
2013.NOV
0
MONTH
11
NOV
Nov23 2013
20131100
2013
2013.Q4
2013.P12
2013.DEC
0
MONTH
12
DEC
Dec28 2013
20131200
2013
2013.Q4
I am seeing one difference now with standard TIME dim, there we do not have any values in TIMEID for non-basemembers nodes, but in this case, we have 20xx00nn.

Similar Messages

Huey Pro calibrator- error message display measurement Error

i am using this huey pro calibration.. it had been a year without problem... but now i am trying to calibrate my apple cinema display LCD 30 inch it keep saying error message- display measurement error.. and huey support never answer my e-mail. any idea? how can i fix it.. i did re install software many times but same thing happen.. so right now i can;t calibrate my monitor.. any help please

>a nice NVidia card... Please help Adobe!
1a - what is the model nVidia card, and what is your driver version?
1b - for instance, I have a GTX 285 and driver 296.10
2a - aside from the occassional Adobe employee, this is a user to user forum, not Adobe suport
2b - how to contact Adobe...
Adobe contact information
http://www.adobe.com/support/contact
In the US - Adobe General support 800-833-6687 M-F 5am-7pm Pacific
In the US - Adobe Install Problems 800-642-3623
In the US - Adobe Activation 866-772-3623 Open 24/7

Huey Pro Calibration Error message- measurement error

i need using this huey pro calibration for year. but now i am trying to calibrate my apple cinema display LCD 30 inch it keep saying error message- display measurement error.. and huey support never answer my e-mail. any idea? how can i fix it.. i did re install software many times but same thing happen.. so right now i can;t calibrate my monitor.. any help please?

Hi,
Which Wireless-Card you used?
Best you use the Cisco CB21AG PCMCIA Card. I had similar problems with intel wireless chipsets
Sincerely,
Frederik

SE30 - Unable to end the measurement (error number 5, Time limit reached)

Hello there,
I wish to perform a complete ABAP trace using SE30 for a program running for 4 hours. The system is R/3 4.6C.
However I got the error message below once I clicked "Back" button or F3 when the program finished after 4 hours.
Please note that ST12 is not available in the system I logged on.
=============================================================
Error message:
"Unable to end the measurement (error number 5, Time limit reached)
Message no. S7 068"
Meas. type           Fully aggregated
Session type         In current session
Status               Time limit reached
Error message text   Time limit exceeded. LIMIT: 1800000000, ELAPSED TIME: 1800957266
File user            XXX
User                 XXX
File ID              ATRAFILE
Release              46C
Version              6
Operating system     HP-UX
Number of processors ???
=============================================================
The ABAP trace results only managed to capture the first 45 minutes of the ABAP calls (due to timeout i think). I would need the whole and complete ABAP trace result for 4 hours, NOT the first 45 minutes. Is there any setting in SE30 can be set for this purpose? Note that there is no ABAP error for the program I traced.
The following link didn't answer my question as well. Hope you can provide clue in this case.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm
Runtime analysis, SE30, ERROR
Thanks,
KP

Hi Kim,
The Limit is expliced on the Doc.
http://help.sap.com/saphelp_nw70/helpdata/en/4d/4e2f37d7e21274e10000009b38f839/frameset.htm
It's 4293 Actually and you set it on SE30 by change the Measurement Restrictions, tab Duration/Type.
regards.

System Measurement - Error while exporting to LAW file

Hi all,
We have the SAP ERP 6.0. We started the system measurement on our ECC landscape with the aim to consolidate the results with LAW in Solution Manager. We performed the measurement in our production server and we select System Measurement - Export to Law File and execute, we are having the following error:
Last measurement was not successfully performed (see USMM)
We are having the error despite doing the measurement afresh
Grateful if you could suggest what to do.
regds

Hi all
thanks for all your comments.
We have tested in other system with Basis 14 and it works there. So we are presuming that the error is due to Basis being level 13.
Still, we have informed SAP about the error.
thanks all.

Unit of measurement error

i
hi guys
crested po with unit of measure kg and also made migo,miro and RFQ but now when i change unit of measurement from kg to pc in material master there is error
the base unit of measure cannot be changed choose display errors
1 if there are no stock of the material in the current period and in the previous period if there are stock in the previous period you can clear them as follow
-post the stock in the previous period to the current period so that the stock for the previous period is the same as the stock for the current period
-clear the stock with the posting date in the previous period
-if no purchase order exist for the material
i have already made po migo,miro, RFQ , please can you guide me step by step how to change the unit of measurement
thanks in advance

Hi
Goods issue the particular material to some cost center. Then there will not be any stock for the particular material. Then change the UOM.
It will work out.
Then reverse the Goods Issue.
Regards,
Raman

Unit of measure error in BAPI_MATERIAL_SAVEDATA

Hi Guru's,
i am trying to upload the material master data using BAPI...while uploading ia m getting beloow error ..please guide me anyone you..where i am doing mistake.....
1st this error i am getting while executing:
internal unit HR ,language EN is not maintained.
and afetr execution in gs_return i am getting below error:
Unit of measure ****** is not defined; check your entry
error number :490
dont get tence for code and all the values ae moving properly into BAPI...and
here i am consider the unit of mesure as HR (hour)..
here i am caliculating like ex: for employe (material) generating bill in hour basis.that is per 1hour $100.
please let me know if my question is not clear..
thanks in advance and will full points to reply....
*& Report ZERP_MATERIAL_CREATE_UPLOAD
REPORT zerp_material_create_upload.
DATA:gs_bapimathead          TYPE bapimathead,
     gs_clientdata           TYPE bapi_mara,
     gs_clientdatax          TYPE bapi_marax,
     gs_plantdata            TYPE bapi_marc,
     gs_plantdatax           TYPE bapi_marcx,
     gs_forecastparameters   TYPE bapi_mpop,
     gs_forecastparametersx TYPE bapi_mpopx,
     gs_valuationdata        TYPE bapi_mbew,
     gs_valuationdatax       TYPE bapi_mbewx,
     gs_salesdata            TYPE bapi_mvke,
     gs_salesdatax           TYPE bapi_mvkex,
     gs_storagelocationdata TYPE bapi_mard,
     gs_storagelocationdatax TYPE bapi_mardx,
     gt_materialdescription TYPE STANDARD TABLE OF bapi_makt,
     gwa_materialdescription TYPE bapi_makt,
     gt_taxclassifications   TYPE STANDARD TABLE OF bapi_mlan,
     gwa_taxclassifications TYPE bapi_mlan,
     gt_prtdata              TYPE STANDARD TABLE OF bapi_mfhm,
     gwa_prtdata             TYPE bapi_mfhm,
     gt_prtdatax             TYPE STANDARD TABLE OF bapi_mfhmx,
     gwa_prtdatax            TYPE bapi_mfhmx,
     gt_unitsofmeasure       TYPE STANDARD TABLE OF bapi_marm,
     gwa_unitsofmeasure      TYPE bapi_marm,
     gt_unitsofmeasurex      TYPE STANDARD TABLE OF bapi_marmx,
     gwa_unitsofmeasurex     TYPE bapi_marmx,
     gs_return               TYPE bapiret2.
TYPES:BEGIN OF gty_itab1,
         matnr(18),   "material
         mbrsh(1),    "industry sector
         mtart(4),    "material type
         vkorg(4),    "sales org
         vtweg(2),    "distr chan
         kondm(2),    "mat prcing grp
         ktgrm(2),    "acc asgn grp
         dwerk(4),    "plant
         meins(3),    "base uom
         tragr(4),    "tarns grp
         matkl(9),    "mat grp
         spart(2),    "division
         ntgew(13),   "net weight
         gewei(3),    "weight unit
         werks(4),    "plant
         ladgr(4),    "loading grp
         dismm(2),    "mrp type
         mtvfp(2),    "available check
         disgr(4),    "mrp grp
         dispo(3),    "mrp controller
         beskz(1),    "procurement type
         prmod(1),    "forecasting mode
         bklas(4),    "valution class
         stprs(11),   "std price
         vprsv(1),    "price control
         peinh(5),    "price unit
         lgort(4),    "storage location
         maktx(40),   "mat description
         taxkm(1),    "tax class
         planv(3),    "task list usage
         brgew(13),   "gross weight
         mtpos(4),    "gen it gross grp
      END OF gty_itab1.
DATA:gt_itab1 TYPE STANDARD TABLE OF gty_itab1,
     gwa_itab1 TYPE gty_itab1.
TYPES:BEGIN OF gty_itab2,
      abc(178),
END OF gty_itab2.
DATA:gt_itab2 TYPE STANDARD TABLE OF gty_itab2,
     gwa_itab2 TYPE gty_itab2.
PARAMETERS:p_files TYPE string.
*START-OF-SELECTION.
START-OF-SELECTION.
*using call method uploading CSV file into internal table
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = p_files
      filetype                = 'ASC'
    TABLES
      data_tab                = gt_itab2
    EXCEPTIONS
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      OTHERS                  = 17.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT gt_itab2 INTO gwa_itab2.
    gwa_itab1 = gwa_itab2-abc(178).
    APPEND gwa_itab1 TO gt_itab1.
ENDLOOP.
LOOP AT gt_itab1 INTO gwa_itab1.
    SPLIT gwa_itab1 AT ',' INTO
          gwa_itab1-matnr
          gwa_itab1-mbrsh
          gwa_itab1-mtart
          gwa_itab1-vkorg
          gwa_itab1-vtweg
          gwa_itab1-kondm
          gwa_itab1-ktgrm
          gwa_itab1-dwerk
          gwa_itab1-meins
          gwa_itab1-tragr
          gwa_itab1-matkl
          gwa_itab1-spart
          gwa_itab1-ntgew
          gwa_itab1-gewei
          gwa_itab1-werks
          gwa_itab1-ladgr
          gwa_itab1-dismm
          gwa_itab1-mtvfp
          gwa_itab1-disgr
          gwa_itab1-dispo
          gwa_itab1-beskz
          gwa_itab1-prmod
          gwa_itab1-bklas
          gwa_itab1-stprs
          gwa_itab1-vprsv
          gwa_itab1-peinh
          gwa_itab1-lgort
          gwa_itab1-maktx
          gwa_itab1-taxkm
          gwa_itab1-planv
          gwa_itab1-brgew
          gwa_itab1-mtpos.
*header data
    gs_bapimathead-material                      = gwa_itab1-matnr.
    gs_bapimathead-ind_sector                    = gwa_itab1-mbrsh.
    gs_bapimathead-matl_type                     = gwa_itab1-mtart.
    gs_bapimathead-basic_view                      = 'X'.
    gs_bapimathead-sales_view                      = 'X'.
    gs_bapimathead-purchase_view                   = 'X'.
    gs_bapimathead-mrp_view                        = 'X'.
    gs_bapimathead-storage_view                    = 'X'.
    gs_bapimathead-account_view                    = 'X'.
    gs_bapimathead-cost_view                       = 'X'.
*sales data
    gs_salesdata-sales_org                       = gwa_itab1-vkorg.
    gs_salesdatax-sales_org                      = '8888'.   "'X'.
    gs_salesdata-distr_chan                      = gwa_itab1-vtweg.
    gs_salesdatax-distr_chan                     = '88'.   "'X'.
    gs_salesdata-mat_pr_grp                      = gwa_itab1-kondm.
    gs_salesdatax-mat_pr_grp                     = 'X'.
    gs_salesdata-acct_assgt                      = gwa_itab1-ktgrm.
    gs_salesdatax-acct_assgt                     = 'X'.
    gs_salesdata-delyg_plnt                      = gwa_itab1-dwerk.
    gs_salesdatax-delyg_plnt                     = 'X'.
*client data
    gs_clientdata-base_uom                       = 'HR '.   "gwa_itab1-meins.
    gs_clientdatax-base_uom                      = 'X'.
    gs_clientdata-trans_grp                      = gwa_itab1-tragr.
    gs_clientdatax-trans_grp                     = 'X'.
    gs_clientdata-matl_group                     = gwa_itab1-matkl.
    gs_clientdatax-matl_group                    = 'X'.
    gs_clientdata-division                       = gwa_itab1-spart.
    gs_clientdatax-division                      = 'X'.
    gs_clientdata-net_weight                     = gwa_itab1-ntgew.
    gs_clientdatax-net_weight                    = 'X'.
    gs_clientdata-unit_of_wt                     = gwa_itab1-gewei.
    gs_clientdatax-unit_of_wt                    = 'X'.
   gs_clientdata-item_cat                       = gwa_itab1-mtpos.
   gs_clientdatax-item_cat                      = 'X'.
*Plant data
    gs_plantdata-plant                           = '8888'. "gwa_itab1-werks.
    gs_plantdatax-plant                          = '8888'.   "'X'.
    gs_plantdata-loadinggrp                      = gwa_itab1-ladgr.
    gs_plantdatax-loadinggrp                     = 'X'.
    gs_plantdata-mrp_type                        = gwa_itab1-dismm.
    gs_plantdatax-mrp_type                       = 'X'.
    gs_plantdata-availcheck                      = gwa_itab1-mtvfp.
    gs_plantdatax-availcheck                     = 'X'.
    gs_plantdata-mrp_group                       = gwa_itab1-disgr.
    gs_plantdatax-mrp_group                      = 'X'.
    gs_plantdata-mrp_ctrler                      = gwa_itab1-dispo.
    gs_plantdatax-mrp_ctrler                     = 'X'.
    gs_plantdata-proc_type                       = gwa_itab1-beskz.
    gs_plantdatax-proc_type                      = 'X'.
    gs_plantdata-period_ind                      = 'M'.   "HARD CODED FOR PERKZ peroid indicator
    gs_plantdatax-period_ind                     = 'X'.
    gs_plantdata-inhseprodt                      = '0'.   "hard coded for DZEIT inhouse production
    gs_plantdatax-inhseprodt                     = 'X'.
*forecast parameeters
    gs_forecastparameters-plant                  = '8888'.   "gwa_itab1-prmod.
    gs_forecastparametersx-plant                 = '8888'.   "'X'.
    gs_forecastparameters-fore_model             = gwa_itab1-prmod.
    gs_forecastparametersx-fore_model            = 'X'.
*valution data
    gs_valuationdata-val_area                   = '8888'. "gwa_itab1-bklas.
    gs_valuationdatax-val_area                  = '8888'.   "'X'.
    gs_valuationdata-val_class                   = gwa_itab1-bklas.
    gs_valuationdatax-val_class                  = 'X'.
    gs_valuationdata-std_price                   = gwa_itab1-stprs.
    gs_valuationdatax-std_price                  = 'X'.
    gs_valuationdata-price_ctrl                  = gwa_itab1-vprsv.
    gs_valuationdatax-price_ctrl                 = 'X'.
    gs_valuationdata-price_unit                  = gwa_itab1-peinh.
    gs_valuationdatax-price_unit                 = 'X'.
*storage location dat
    gs_storagelocationdata-plant              = '8888'. "gwa_itab1-lgort.
    gs_storagelocationdatax-plant             = '8888'. "'X'.
    gs_storagelocationdata-stge_loc              = gwa_itab1-lgort.
    gs_storagelocationdatax-stge_loc             = '8888'.   "'X'.
*material discription
    gwa_materialdescription-langu                = 'E'.
    gwa_materialdescription-matl_desc            = gwa_itab1-maktx.
*tax classification
   gwa_taxclassifications-taxclass_1            = gwa_itab1-taxkm.
    gwa_taxclassifications-depcountry            = 'US '.         "HARD CODE FOR TAX
*prt data
    gwa_prtdata-plant                        = '8888'.   "gwa_itab1-planv.
    gwa_prtdatax-plant                       = '8888'.   "'X'.
    gwa_prtdata-prt_usage                        = gwa_itab1-planv.
    gwa_prtdatax-prt_usage                       = 'X'.
*unitsof measure
    gwa_unitsofmeasure-alt_unit                  = 'HR '.   "gwa_itab1-brgew.
    gwa_unitsofmeasurex-alt_unit                  = 'HR '. "'X'.
    gwa_unitsofmeasure-unit_of_wt                  = 'KG'.    "gwa_itab1-brgew.
    gwa_unitsofmeasurex-unit_of_wt                  = 'X'.
    gwa_unitsofmeasurex-sub_uom                  = 'X'.
    gwa_unitsofmeasure-gross_wt                  = gwa_itab1-brgew.
    gwa_unitsofmeasurex-gross_wt                  = 'X'.
*appending workarea to table's
    APPEND gwa_materialdescription    TO gt_materialdescription.
    APPEND gwa_taxclassifications     TO gt_taxclassifications.
    APPEND gwa_prtdata                TO gt_prtdata.
    APPEND gwa_prtdatax               TO gt_prtdatax.
    APPEND gwa_unitsofmeasure         TO gt_unitsofmeasure.
    APPEND gwa_unitsofmeasurex        TO gt_unitsofmeasurex.
*calling FM BAPI for uploading the Material master data
    CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
      EXPORTING
        headdata            = gs_bapimathead
        clientdata          = gs_clientdata
        clientdatax         = gs_clientdatax
        plantdata           = gs_plantdata
        plantdatax          = gs_plantdatax
        forecastparameters = gs_forecastparameters
        forecastparametersx = gs_forecastparametersx
        valuationdata       = gs_valuationdata
        valuationdatax      = gs_valuationdatax
        salesdata           = gs_salesdata
        salesdatax          = gs_salesdatax
      IMPORTING
        return              = gs_return
      TABLES
        materialdescription = gt_materialdescription
        unitsofmeasure      = gt_unitsofmeasure
        unitsofmeasurex     = gt_unitsofmeasurex
        taxclassifications = gt_taxclassifications
        prtdata             = gt_prtdata
        prtdatax            = gt_prtdatax.
Check the return table.
    IF sy-subrc NE 0.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      WRITE: / 'Error occured while creating material'.
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
      WRITE: / 'material',gwa_itab1-matnr,'created'.
    ENDIF.
ENDLOOP.

Hi Aparna..
even with HUR also i am getting same error.....
is there any changes required in the SPRO .......
i mean in BAPI had ..unitofmeasure we have around 21 fields( here extra fields is DEL FLAG)
                      but in unitofmeasurex has only 20 fields...
we need to anything in SPRO for avoiding DEL FLAG.....
sorry if i am confusing u.....
thanks for responce and send few more inputs for resolving the issuee....

Unit of Measure Error in Purchase order

Hi Gurus,
While saving the Purchase order i am getting the Error message
"Unit of measure KG not defined for language GB."
We are trying to place this PO outside the US .PR already created and released.But when i am converting the PO and saving it gives me this error .
Thanks a lot in Advance
Edited by: Metroid01 on Jul 23, 2009 12:55 AM

How do i create the UOM in CUNI for the specific language? I can see the below
Int meas unit---->KG
Display
Commercial--->KG
Technical----> Kg(in Po it is taking g is lower case)
in ALE/EDI--->ISO Code is EA.
Can you check this if it is the right set up in config.
Thanks a lot for the help.

Measurement error in reading Encoder Pulses

I am using PCI-6601 card to read a Linear Encoder which gives 2000 pulses per mm of distance.The accuracy of the Linear encoder is 2Microns.In my application I am measuring a distance of 7mm.But the card is reading with an error of 30 to 50 Microns error.We had checked up all the factors related to mechanical and Encoder.In fact the same application was earlier working with Advantech Encoder card which has provisons to connect the A,B,A Bar,B Bar inputs from Encoder.There was an accuracy of 0 to 5Microns.But the application was replaced with NI Card because of the continuous problem of the Digital I/O Card used from Advantech.
Mail me the possible causes and also the troubleshooting procedures for correcting the above problem

Hi,
What I think is happening is there might be some noise on your signal lines. The PCI-6601 counters are capable of detecting a pulse as small as 20ns. If the Advantech card can't detect pulses at that small a resolution, it might be ignoring "noisy" pulses that shouldn't be there. Are you reading more pulses than you should be or less?
There are a couple things I might be able to suggest to clean up your signal. The counters support several different encoder modes. Try using X4 Encoders. An X4 encoder counter increments or decrements on each edge of channels A and B. Whether the counter increments or decrements depends on which channel leads the other. Each cycle results in four increments or decrements. I believe this X4 mode is more noise resi
stant than the standard mode.
Another thing you might want to consider is applying a filter to the input signals (debounce or deglitch filters). Each PFI line coming from the I/O connector can be passed through a simple digital filter. The filter operates off a filter clock and a fast internal sampling clock. It samples the signal on the PFI line on each rising edge of the sampling clock. A change in the signal is propagated only if it maintains its new state for at least the duration between two consecutive rising edges of the filter clock (one filter clock period). The frequency of the filter clock determines whether a transition in the signal may propagate or not.
6601/6602 User Manual
http://digital.ni.com/manuals.nsf/webAdvsearch/DD0DBB6404BC139886256721007CF16D?OpenDocument&vid=niwc&node=132100_US
Hopefully one of these suggestions will do the trick. Have a good day.
Ron

Voltage measurement error

Hello,
I am using a PXI system (PXIe-1073 chassis, PXIe-6363 DAQ card, PXI-2567 relay driver card) connected to my custom PCB.
My PCB has a 2.5V output precision reference IC whose output is connected to an analog input of PXIe-6363 DAQ card through the 68-pin connector and DAQ cable (SHC68-68).
When I measure the 2.5V output at the 68-pin connector (Analog input pin of the connector) using an external DMM (with High Z input impedance), I measure exactly 2.5003V, which is what I expect. However, LabVIEW reports back 2.4987V with an error of 1.6mV.
So, I disconnect my PXI system from my PCB and connect the DAQ card cable to the SCB-68 connector block and supply 2.5V external supply to the analog input and GND through the connector block. Now, both external DMM and LabVIEW report exactly 2.5V. This suggests that the DAQ card and software (voltage measurement VI) are working fine.
Then why do I have an error of 1.6mV when the PXI system is connected to my PCB ? If the problem is in my PCB, then why does the external DMM measure accurately right at the DAQ 68-pin connector ? What could be going on ?
Thanks
Jeet

Hello,
Yes, the PXI chassis is still connected to the PCB when I measured with an external DMM.
Upon further investigation, I found that my switched mode power supply was injecting 240 mV-pp noise on the Ground. This Ground noise was getting filtered down to 60 mV-pp through a choke but it still wasn't good enough. So I used another RF bead (with 1K impedance @ 100 MHz) to further suppress the ground noise and that did the trick. Now my voltage measurements are right on.
Thanks
Jeet.

Period measurement Error 20308

I'm trying to measure the period of a very slow frequency (0.083 Hz) coming into my DAQ(6009).
However it comes with "Error -20309 occurred at "NI_MAPro.lvlibulse Measurements 1 chan.vi:2" when called from "NI_MAPro.lvlibulse Measurements N chan.vi:1" (waveform index 0 of 1)".
The DAQ is capturing method is set to "on demand" however I have also tried various (frequency + buffer) such as 10k by 2k.
but it still comes up with the error.
I know why it comes up with this error but don't know how to fix it.
I have attached the vi (the simulate signal is replicating my DAQ)
Solved!
Go to Solution.
Attachments:
untitled.PNG ‏17 KB
Period.vi ‏35 KB

The error is explaining that not the wave didn't cross the reference levels enough times to do the calculations. Check that your signal reaches both the high and the low levels and that you have enough data in your signal to do a couple of whole signal periods. (with a signal frequency of 0.8 it will take 12 seconds to do a whole cycle) In the simulated example, I got it to work just by increasing the number of samples to 100.
Ian S
Applications Engineer CLD
National Instruments UK&Ireland

TBX-68T temperature measurement errors

I am using a TBX-68T with a PXI 4351 card to measure the temperature of a steel plate while the plate is undergoing a TIG (electric arc) welding process. To my knowledge (and based on past experience), the device is connected properly in MAX, with the TBX-68T selected as the accessory. In MAX it also passes the tests. Using the built in CJC and specifying a K-type thermocouple at a range of +/-0.625v, MAX reports temperatures of -80C. The temperature remains nearly the same as the range is increased, but if I change the range to +/-3.75v, the temperature suddenly jumps to 100+C. I used the Measure Thermocouple (with accessory).vi that comes with the driver, and it gives me the same readings. Furthermore, when I initiate the TIG welder the card reads extremely negative (-10e9) temperatures.
What is odd, is that I have used these devices for the exact same process in the past and it generated believable results.
How can I fix the current temperature offset problem? Could I have possibly damaged the unit? Is it possible to use the TBX-68T to reliably detect temperature in arc welding process?
Thanks,
William

Hello,
Becasue TIG welding creates a large electrical discharge I am concerned that you may have shorted the card. What kind of isolation did you use to ensure a separation between the TIG process and the temperature measurement? Because the error is read by both your program and MAX it must be either the temperature configuration or the card. Could you try to conduct a simple Voltage measurement with the 4351, lets say a AA battery. You should be able to read 1.5-1.6V. If this works than the card should be fine, (make sure to test all channels that are failing).
If you cannot read the proper voltage on the card, then it is possible that the card will need to be repaired. Please update us so we can help you further.
Thank you
Regards,
CharlesD
Digital MultimetersSchedule a Free 1 Hour LabVIEW Tutorial with an NI Applications Engineer

How to measure error on peak detect?

Hello!
I'm using the vi Waveform Peak Detect to find peaks in some signals that we analyze at the lab where i work. However, i must know also what's the error on the measure. Anyone knows if there is a vi that measures peak AND the error on the values found? Or at least a mathematical way to find the error myself?
Thanks!

This is not an simple question to answer. When you search for the peak value of a signal you have to make some assumptions about that signal. For example if your signal looks like [1, 1, -1, -1, 1, 1, -1, -1, ...], it may be difficult to define its peak value.
The first approach is, that your signal is a square wave of amplitude 1.0 and normalized frequency = 0.25. It this case the peak value is also 1.0
But the same signal could be the result of the sampling of a pure sine tone of amplitude 1.4142 (SQRT(2)). if you sample your sine tone at 45, 135, 225 and 315 degrees of phase, you get the same sequence of samples. In this case you would like your peak result to be 1.4142.
So the error can be as big a 41% (3 dB). This is of course an extreme situation, and
in most case the error is much smaller.
In general, the higher the relative bandwidth of your signal is (the ratio between the signal bandwidth and the used sample rate), the most uncertain is your result. So if you want to "stay in control" you need to make sure your signal is sampled at a rate that is high enough to give a good representation of your original analog signal.
As an option, you may want to re-sample your signal (to a higher rate) using an appropriate algorithm. The new resampling VIs offer various interpolation algorithm that you can experiment with, depending on the nature of your signal. The peak detection VI will then do the work for you.

Frequency measurement error using DAQSTC

I have modfied the example listed to measure up to 9 frequencies continuosly in the vi as attached.
When I use the same approach combined with analogue & digital input/output I get a small error in frequency.
(Input line PF10 reads 6.8Hz for a 6.7Hz input.)
Attachments:
measure_9_frequencies.zip ‏50 KB
Rig_13-2_Monitor-1.llb ‏196 KB

Hello,
The code that you are using to take the frequency measurement could be done with lower level VIs that will more than likely resolve this issue. I modified one of the LabVIEW shipping examples: Measure Period (DAQ STC).vi Please take a look at the VI that I have attached.
Attachments:
Measure_Multiple_Freqs.vi ‏98 KB

Pulse measurement Error

I used the Pulse measurement 1 Chan VI in my project and could see that the VI pops up an error in few cases (Error -20308 occurred at "NI_MAPro.lvlib:ma_ptmFetch.vi:2" when called from "NI_MAPro.lvlibulse Measurements 1 chan.vi:1").
I have attached the data cluster of a failed case. Please let me know, wat is going wrong?
Attachments:
Pulse Measurement.vi ‏16 KB

HI
The data you are passing to pulse measurement vi is very small because of that it is giving the error.
Please find attached image for more detail. I have just appended the same siganl four times
Hope this helps
Regards
Santosh
Attachments:
data.JPG ‏232 KB

Measure Error: UJO_READ_EXCEPTION_018

Similar Messages

Maybe you are looking for