PXI module DLL Documentation

Hi,
    I was able to extract PXI module data that I ask before through this Link:
But the VIs that are available on my function palette was somehow not complete, so
I wanted to create a few VIs that will extract the data I wanted by using "call library function". 
(The most important data for me right now are the Last External Calibration Dates and the Recommended
Calibration Interval from the PXI Modules)
    This will be my first time to use "call library function" so need your help with some DLL documentation for below hardware.
    Really appreciate if someone could share me some documentation.
Btw, I'm currently working with the following hardware:
NI PXI-5922/5122  ------ niSCOPE
NI PXI-6552          ------ niHSDIO.dll
NI PXI-5406          ------ niFGEN
NI PXI-4110/4130  ------ niDCPOWER
Thanks in advance!

Hi Versil1,
Thanks for posting.  The functions that you are looking for are already available in the function palette for some of the devices that you are using, so using Call Library Function to access the DLLs should not be necessary.  Here are where these functions are located:
For NI-FGEN: Right-click, then go to Measurement I/O » NI-FGEN » Calibration » Utility » niFgen Get Ext Cal Last Date and Time.vi and niFgen Get Ext Cal Recommended Interval.  
For NI-DCPower: Right-click, then go to Measurement I/O » NI-DCPOWER » Calibration » Utility » niDCPower Get Ext Cal Last Date and Time.vi and niDCPower Get Ext Cal Recommended Interval.
For NI-Scope: Right-click, then go to Measurement I/O » NI-SCOPE » Calibration » External Calibration » niScope Cal Fetch Date.vi.  There currently is no function to retrieve the recommended interval.  This information can be found within Measurement & Automation Explorer.
For NI-HSDIO: There are currently no functions to retrieve the last external calibration date or the recommended interval.  This information can also be found within Measurement & Automation Explorer.
I will be filing some product suggestions for adding functions to NI-Scope and NI-HSDIO to return this information.  Our R&D department will take a look at the suggestion for future improvements.  For now, these are the functions that we have available to use.  Hope this helps!
Regards,
Joe S.

Similar Messages

  • Direct connect to my PXI module

    Hi,
    my problem is, that I don´t know how I can direct "speak" whit my PXI module.
    I need some information about revisions-number and so on...
    whit the DAQ I can find serial-number and device-type, but I need some specific informations.
    If I look to GPIB ther are the kommand "*IDN?". Is ther some way to connect my PXI module like GPIB? Or with VISA?
    My application (in CVI) must read some information about the actual PXI system. I can´t use drivers from a specific module, then I don´t know what modul are in the system.
    I hope someone can help me

    You will be able to the get this information using the VISA Driver Development Wizard. You can read more about this tool at the following link:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/ADF3152837E2B4A486256B5600642AC7?opendocument
    This document explains in detail the process required.

  • How to use the Keying of CompactPCI in my own designed PXI-module?

    as title.
    I've designed a own PXI-module.Since I havn't seen the CompactPCI Keying in J1 before, I don't know how to use it, or it is just necessary for special application field?

    Hello,
    Please refer to the link below, I think it will have all of the information that you need concerning keying of CompactPCI and PXI modules:
    http://digital.ni.com/public.nsf/websearch/98907157CE1428A286256BC900607485?OpenDocument
    Regards,
    Andrew Mierau
    Applications Engineer
    National Instruments

  • Why do multiple PXI modules in a chassis cause my PC to continuall​y reset?

    I have a PXI-1000 connected to my desktop PC via a MXI-3 interface. When I plug more than a couple of PXI modules into the chassis and switch on, my PC continually resets itself. Any idea what is wrong?

    Dear Darren,
    This sounds like there is a problem with your chassis supplying the power required for all of your PXI modules. This could indicate either a problem with the power supply on the chassis itself, a problem with the PXI backplane being shorted, or a problem with one or more of your modules. If possible, I recommend testing this system with a different PXI chassis.
    If a second chassis works, then we know the problem is with the first chassis. In this case, I recommend checking for bent pins on the backplane. You can also send it in for repair.
    If the second chassis does not work, then we know the problem probably is not with the chassis. I recommend testing each card. One of your modules could be shorting the backplane. I recommend testing the s
    ystem with each module one at a time. Place each module in each slot in the chassis to see if any combination of modules and slots makes a difference. Once you verify that each module works, you can then test to see if a certain combination of modules causes the problem. The goal here is to determine which module or modules is causing the problem. We need to find out which module is either shorting out the backplane or is drawing too much power.
    This could also be a problem with the MXI-3 connection or the PC. I recommend testing this system with a different PC. You may also consider upgrading your PC's BIOS.
    If you want to send in your chassis or PXI modules for repair, you will need to call in. In this case, go to http://www.ni.com/support and generate a phone support request.
    Regards,
    David Shatila
    Applications Engineer
    National Instruments

  • The Module DLL D:\Microsoft\Exchange Server\V14\Bin\kerbauth.dll failed to load. The data is the error.

    Hi,
    I keep receiving an error message in the Event Logs for Exchange 2010:
    The Module DLL D:\Microsoft\Exchange Server\V14\Bin\kerbauth.dll failed to load. The data is the error.
    Event ID: 2280 - IIS-W3SVC-WP
    OWA is working.
    In IIS- HTTP Redirect is Disabled On the Default Website.

    Hi
       According to your error, the path is incorrect or dll file is corrupted.
       You can modify file “\Windows\System32\inetsrv\config\applicationHost.config”
        please check this sentence
       <add name=”kerbauth” image=”D:\Exchange,Server\V14\Bin\kerbauth.dll” />
       Can you find kerbauth.dll in this path?
       If you can find this dll, please copy same dll from other exchange system and replace of it.
       If you can’t find it, please modify path.
    Terence Yu
    TechNet Community Support

  • Release date for PXIe Modules

    I had a couple of questions about PXIe:
    1) I see that a controller and chassis have been released, when will Digitizers and DAQ cards be released?
    2) It is my understanding that a PXI card that is plugged into the PXIe
    chassis will work, but NOT receive the 1GB/s bandwidth, is this
    true?  In other words, PXI cards do not get the bandwidth upgrade,
    just PXIe cards.
    3) I saw in the PXIe tutorial that PXI cards can be sent in and the J2
    pin port will be replaced to make it into a PXIe hybrid card. 
    Would this card gain the benefit of the 1GB/s bus speed?
    Thank you in advance,
    Austin McElroy

    I'll answer your last two questions:
    >>It is my understanding that a PXI card that is plugged into the PXIe
    chassis will work, but NOT receive the 1GB/s bandwidth, is this
    true?  In other words, PXI cards do not get the bandwidth upgrade,
    just PXIe cards.
    There are different types of slots in PXI Express chassis. A PXI card can be plugged into a hybrid slot or a PXI slot. A PXI slot can only accept a PXI card. A hybrid slot can accept a PXI card or a PXI Express card. In order to insert a PXI card into a hybrid slot, it must have the J2 connector replaced as you stated. Some PXI cards do not have a J2 connector and these need no modification.
    PXI and PXI Express cards use different types of busses to connect to the system. PXI cards use only the PXI (PCI) bus while PXI Express cards use a PCI Express link. Electrically, the two busses are not compatible or interchangeable. Hybrid slots support both busses, but a card only uses one or the other. The bandwidth available to a PXI card does not increase if it is plugged into a hybrid slot as the PXI card will only use the PXI bus, not the PXI Express bus.
    >>I saw in the PXIe tutorial that PXI cards can be sent in and the J2
    pin port will be replaced to make it into a PXIe hybrid card. 
    Would this card gain the benefit of the 1GB/s bus speed?
    No, this card still connects using the PXI (PCI) bus. The PXI Express bus in the hybrid slot will not be connected to the PXI card. The PXI card will not be able to access the bandwidth provided by the PXI Express bus.
    This is a subtle point, but a PXI card that has been modified to work in a PXI Express hybrid slot is known as a "hybrid slot-compatible PXI module". A "PXIe hybrid card" seems to imply a card that uses both the PXI Express and PXI busses. I doubt such a card would ever be designed.

  • Slot Detection of PXI Modules, More details

    I read the knowledge base titled: Slot Detection of PXI Modules but have a few questions about it. How often to I have to do this? When I insert or remove a board from the PXI chassis? When I insert or remove an additional chassis in daisy chain? With Multiple chassis in Daisy chain. How do I know which device number is which card? ie if I have 2 of the same model of cards both in slot 5 but in different chassis. If I remove a card, am I guarranted that other cards device numbers will not change?

    John,
    The Knowledge Base (KB) "Slot Detection of PXI Modules" says that the PXI Initialization File (PXISYS.INI) file must be saved in the systems directory in order for the system to be able to identify the slot where a board is located. This is because every slot in a PCI Bus (a PXI system uses a PCI bus) has a PCI Device Number and PCI Bus Number associated with it. The PXISYS.INI file describes the architecture of the chassis and the controller, and has the appropiate PCI Device Number and PCI Bus Number for every slot. There is a unique PXISYS.INI file for every combination of PXI chassis and PXI controller.
    How often to I have to do this? When I insert or remove a board from the PXI chassis?
    Currently you do not need to edit the PXISYS.INI file. You can download the PXISYS.INI file from our website and use it as it is (see link in the KB you were reading). So you only need to save once the appropiate PXISYS.INI file to the Windows Systems directory, regardless of whether you change the PXI board in your system.
    When I insert or remove an additional chassis in daisy chain? With Multiple chassis in Daisy chain?
    If you are daysi-chaining chassis, keep in mind that the current PXI Standard DOES NOT support daysi-chaining. However, in previous PXI configurations, I have successfully edited a PXISYS.INI file so I can do Slot Identification in daysi-chained chassis (not in star configuration, though). The steps I followed are in the text file attach to this e-mail.
    How do I know which device number is which card? ie if I have 2 of the same model of cards both in slot 5 but in different chassis. If I remove a card, am I guarranted that other cards device numbers will not change?
    Finally, if you are using NI DAQ boards, NI-DAQ driver will assign a Device Number to the boards that correspond to the Slot Number, and the Slot Number is described in the PXISYS.INI file that you edited following the instructions in the text file attached below.
    If your boards do not use the NI-DAQ driver, but support NI-VISA, you can use the PXI VISA Instrument Descriptor to find out the Slot they are installed in. See the KB "Programmatic Slot ID" linked below for more information. It has an Example Program linked to it too:
    KnowledgeBase 2MDFG2WD - Programmatic PXI Slot Detection
    Let me know if I can be of further assistance,
    Claudia Lorente
    Applications Engineer
    National Instruments
    http://www.ni.com/
    Attachments:
    PXISYS_for_Daysi_Chain.txt ‏4 KB

  • PXI Module Informatio​n Scan

    Hi,
           I'm planning to develop a labview program thats scans information from all PXI module present in the chassis(like calibration dates, module description, etc..). Need some advice which Labview VI is capable of scanning above mentioned information wherein output is in "string" so that I could
    manipulate it in the labview program itself.  As I scan for VI, one option I see is the "MAX Generate Report", but results are in html or xml(plus my PXI
    hangs when I use this function).
           Appreciate any inputs on this.
    Thanks,
    Versil1
    Solved!
    Go to Solution.

    Hi Versil1,
    I would recommend using niModInst, DAQmx device node, and DAQmx system node. Examples for how to use those functions can be found here:
    niModInst: Programmatically Query Device Name or Other Information Using NI-ModInst API http://decibel.ni.com/content/docs/DOC-7454
    DAQmx device and system node: Programmatically Get DAQ Device Product Names http://decibel.ni.com/content/docs/DOC-3716
    For outputs that are not in string format (i.e. DevNames), you can use the flatten to string function to convert them to strings.
    Regards,
    Andrew M.
    Applications Engineer
    National Instruments

  • Function module CS_BOM_EXPL_MAT_V2 Documentation

    I cannot find any documentation for function module CS_BOM_EXPL_MAT_V2.  It is a very powerful function module, however, it is not useful without documentation.  I know that it can do single level boms as well as multi level and a host of other things, but I can only guess without documentation.  Do you know where I can get documentation for this function module. 
                        thank you in advance, Leonard Getz, Dy4 Systems Inc. Ottawa, Ontario, Canada.

    This is what I found:
    CALL FUNCTION 'CS_BOM_EXPL_MAT_V2' "BOM explosion for material
    EXPORTING
      ftrel = SPACE               " csdata-xfeld  Limited multi-level - stop explosion at items not relevant to production
      aufsw = SPACE               " csdata-xfeld  Determine and enter order level and channel
      aumgb = SPACE               " csdata-xfeld  Calculate scrap quantity
      aumng = 0                   " stko-bmeng    Scrap quantity
      auskz = SPACE               " csdata-xfeld  Scrap
      bagrp = SPACE               " mara-matnr    Assembly restriction
      beikz = SPACE               " stpo-beikz    Material provision indicator
      bessl = SPACE               " csdata-xfeld  Material provision selection indicator
      bgixo = SPACE               " csdata-xfeld  Load assembly information for exploded assemblies only
      brems = SPACE               " csdata-xfeld  Limited explosion
      capid = 'STD1'              " tc04-capid    Application ID
      cospr = SPACE               " csdata-xfeld  Internal: (CO) order-spec. MatPreRead
      cuobj = 000000000000000     " marc-cuobj    Configuration
      datuv = 00000000            " stko-datuv    Validity date
      delnl = SPACE               " csdata-xfeld  Delete items not kept in stock from list
      emeng = 0                   " stko-bmeng    Required quantity
      erskz = SPACE               " stpo-erskz    Spare part indicator
      erssl = SPACE               " csdata-xfeld  Spare part selection indicator
      fbstp = SPACE               " csdata-xfeld  Limited multi-level - stop explosion at externally procured item
      mbwls = SPACE               " csdata-xfeld  Read material valuation
      mdmps = SPACE               " csdata-xfeld  Limited multi-level - explode phantom assemblies at least
      mehrs = SPACE               " csdata-xfeld  Multi-level explosion
      mkmat = SPACE               " csdata-xfeld  Limited multi-level; explode KMAT
      mmaps = SPACE               " csdata-xfeld  Limited multi-level - explode at least M assembly (M order)
      mmory = SPACE               " csdata-xfeld  Memory use ('1'=on;'0'=off;' '=no reaction)
      mtnrv = SPACE               " mara-matnr    Material
      postp = SPACE               " stpo-postp    Item category
      rndkz = SPACE               " csdata-xfeld  Round off: ' '=always, '1'=never, '2'=only levels > 1
      rvrel = SPACE               " stpo-rvrel    Relevant to sales
      sanfr = SPACE               " stpo-sanfe    Production
      sanin = SPACE               " stpo-sanin    Maintenance
      sanka = SPACE               " stpo-sanka    Costing
      sanko = SPACE               " stpo-sanko    Engineering/design
      sanvs = SPACE               " stpo-sanvs    Shipping
      schgt = SPACE               " stpo-schgt    Bulk material
      stkkz = SPACE               " stpo-stkkz    PM assembly
      stlal = SPACE               " stko-stlal    Alternative BOM
      stlan = SPACE               " stzu-stlan    BOM usage
      werks = SPACE               " marc-werks    Plant
      mdnot = SPACE               " csdata-xfeld  Restriction on MDMPS: do not explode M phantom
      panot = SPACE               " csdata-xfeld  Restriction on MDMPS: no parallel discontinue
      IMPORTING
        topmat =                    " cstmat        Data for start material
        dstst =                     " csdata-xfeld  Structure destroyed by filter
      TABLES
        stb =                       " stpox         Collective item data table
      matcat =                    " cscmat        Material catalog (sub-assemblies)
      EXCEPTIONS
        ALT_NOT_FOUND = 1           "               Alternative not found
        CALL_INVALID = 2            "               Incorrect parameter combination
        MATERIAL_NOT_FOUND = 3      "               Material not found
        MISSING_AUTHORIZATION = 4   "               No authorization (bill of material)
        NO_BOM_FOUND = 5            "               No BOM for this material
        NO_PLANT_DATA = 6           "               Material not maintained in plant
        NO_SUITABLE_BOM_FOUND = 7   "               BOM does not exist
        .  "  CS_BOM_EXPL_MAT_V2

  • Automatic/Programmatic Detection of Device ID (Device Number) of PXI modules

    Hi All,
    I'm currently working on a project in RF (RFSG & RFSA) using,
    PXI-1042 Chassis
    PXI-8331 (MXI-4) module
    PXI 5610
    PXI 5421
    PXI 5600
    PXI 5620
    My project is going to be integrated as a sub-module into another project developed in VC++.
    It'll be called as an external component into that.
    I want the RF module to get auto detected when it is called from VC++ with the correct Device ID (Device Number) shown in MAX.
    This is because, for the same slot configuration of the RF modules into the PXI-1042 Chassis,
    it shows different Device ID (Device Number) when connected to different PCs.
    So, I dont want the user to launch the NI-MAX & then key in the correct Device ID (Device Number) shown there.
    It'll also become tedious & messy since this RF module is called by VC++.
    How can this be achieved?
    Is there any way to autodetect the Device ID (Device Number) or the Resource Name, in some cases, without the help of MAX?
    I do not mean the slot ID for which some material is already available in the NI website.
    Thanks & Regards,
    Partha.
    - Partha
    LabVIEW - Wires that catch bugs!

    Hi Partha,
    There is a VI named 'Get DAQ Device Information' which can be obtained
    through Traditional DAQ>> Calibration and Configuration pallete.
    You can iterate this VI in a for loop, and check whether the device
    name matches with the one that you require (see attached image). I have
    not worked with RF, so don't know exactly whether this VI will work
    with RF cards.
    Hope this helps!
    Kallis
    Have a nice day!!!
    LabVIEW | LabWindows/CVI | TestStand
    Certified LabVIEW Architect
    Attachments:
    Device Name.png ‏6 KB

  • How to read the serial number of PXI Module in my C/C++ program.

    I am using PXI NI-FGEN controlling it by my C/C++ program. I would like to read the serial number of the hardware. Are there any methods to do it ?
    Actually I could not find any functions and attributes in the programming manual. So I am posting this as the last chance. For example, it looks possible to me if we can access NI-MAX in my C/C++ program. Because NI-MAX displays the serial number.
    Any information would be appreciated.

    It looks like your answer is in the NI-FGEN help file. Go to NI-FGEN -> Documentation -> NI Signal Generators Help
    From that help the inforamtion you are looking for is under the following heading:
    NI Signal Generators Help
    +Programming
    +NI-FGEN Help
    +C Reference
    +Attributes
    +Instrument-Specific Attributes
    ?NIFGEN_ATTR_SERIAL_NUMBER
    I hope this is what you're looking for,
    Ross Mau
    NI Applications Engineer

  • Virtual InfoCube with Services - function module parameters documentation ?

    Hello,
    I have been trying to use a Virtual Infocube with Services.
    I have seen most of the posts in SDN, and read the documentation in http://help.sap.com/saphelp_nw04/helpdata/en/8d/2b4e3cb7f4d83ee10000000a114084/frameset.htm
    I did not manage to find a precise description of the import 
    parameters of the Variant 2.
    In particular, what is the meaning of the
    i_tx_rangetab TYPE rsdri_tx_rangetab parameter. I read in the code of RS_BCT_FIGL_DATA_GET that it has to do with query columns. In the tests I did this table is alway empty.
    Also, i_th_sfc gives you the list of characteristics used in the query. But it does not inform you on wether these are in the 'rows' 'free characteristics' or 'filter'. Is there a way of knowing that?
    Claudio Ciardelli

    Hi Claudio,
    I never implemented Virtual InfoCube with services with a FM, but I know there is a couple of How To Documents about named:
    - How to Reporting from External Data via Virtual InfoProvider
    -How to Implement a Virtual InfoCube with Services
    both with some code samples: did you read it?
    Hope it helps
    GFV

  • Only 2 of my PXI modules are found by Visa Interactive Control

    I can see 14 PXI devices in NI-MAX but only two are found by VISA Interactive Control.
    Solved!
    Go to Solution.

    I found the solution on ni.com.  See “Setting VISA to Recognize All of the PXI Devices in a PXI System”.
    http://digital.ni.com/public.nsf/allkb/B9BEB4A3C383BF4486256FCE0008EA72

  • In begining PXI session run program like RESMAN in VXI session or the open must bw a part of DLL?

    I am wriitng a DLL for a new PCI device and it was possible that in on e chassis will be more that one device hoe the user will pass to DLL in wirch device the command it?( this is my first expereince with PXI and PCI programming) the device is a passive device (no CPU in the device)

    FP:
    I think you are asking one of 2 possible questions and I'll try to answer them both.
    The first is how to find any existing board of a given model. Each PCI or PXI module will have its own model code, just as in VXI. You can do a search with viFindRsrc with "PXI?*INSTR{VI_ATTR_MANF_ID == 0x1234 && VI_ATTR_MODEL_CODE == 0x5678}". If there is only 1 in the system, the output string is what you want.
    If there are more than 1 of the exact same type of device in the system, that query will not suffice because it will return all of them. The way to distinguish them then is to use the device number, which is similar perhaps to the VXI logical address. 2 devices next to each other might have addresses like "PXI0::15::INSTR" and "PXI0::14::INSTR". These numbers
    are related to the slot but are not quite the same as the slot. The 3 unique numbers in PXI are bus (often 0 for a small PXI chassis), device, and function (0 for most devices, required only for multifunction devices). The resource string uses them as "PXI::::::INSTR".
    Dan Mondrik
    Senior Software Engineer, VISA
    National Instruments

  • Pulse Generation application with DAQmx and a PXI-6624 module?

    What is the best implementation method for the following pulse generation application
    using LabVIEW, DAQmx and a PXI-6624 counter\timer module?
    I have two rising edge trigger signals (Trigger-1 and Trigger-2).
    There is ample spacing between each trigger. They never occur at the same time.
    I need to generate a single pulse (fixed width, variable delay) whenever Trigger-1 occurs and
    a finite pulse train (fixed width, variable delay, N-pulses) whenever Trigger-2 occurs.
    However, the output must appear on one counter output because this composite signal
    will be used as a trigger source for another PXI module in the rack.
    With DAQmx and a TIO counter\timer can I use both the GATE (for Trigger-1) and
    AUX (for Trigger-2) at the same time on the same counter to gate out the desired pulses?
    Trigger-1 would be wired to the GATE of CTR0. One Trigger-1 event would generate one pulse on the output of CTR0.
    Trigger-2 would be wired to the GATE of CTR1 and the output of CTR1 would be routed to the AUX input of CTR0.
    One Trigger-2 event at the GATE of CTR1 would generate multiple pulses on output of CTR0.
    Would DAQmx and the PXI-6624 TIO support this implementation?
    What is the best way to accomplish the task at hand.
    Thank You.
    Best Regards,
    Scooby

    Hi Scooby,
    I have looked into the application you have described and I see a potential problem with what you describe.  In DAQmx, it is not possible to call the counters of the same DAQ device in the same task, so you cannot have the finite pulse train generation and the single pulse generation tasks running at the same time.  What you can do, since you mention the triggers will not occur at the same time, is to stop one counter task while you are triggering another.  The way I would suggest you merge the outputs is with a two input Or logic gate to avoid damaging your counters.  Your signals will effectively be added together by this logic gate.   I do not see any way to merge the outputs internal to the DAQ device. 
    Please let me know if I can be of additional assistance.
    Laura

Maybe you are looking for