How to use the PCI-DIO-32HS counter

I have to create a SPI, I'd like to use counter, but the card doesn't answer, so Labview bug. Do you if there is programmable/configurable counter on this Card?

Hello,
The PCI-DIO-32HS does have a counter onboard. However the counter is only used for generating an internal clock in order to do pattern generation. You cannot program this counter in LabVIEW. If you need a counter, I would look at using an M Series Board, or a 660X board.
Best regards,
Justin T.

Similar Messages

  • How to use a PCI-DIO-32HS board with macintosh C++

    How can I run the PCI-DIO-32HS board with code from CodeWarrior for a Macintosh G3? The current drivers (V4.8) with Mac C++ support don't support this board.

    Here is a list of supported compilers with NI-DAQ 4.9.4 or earlier found on the www.ni.com/support website search
    Apple MPW 3.3.x
    Mainstay VIP-C 2.0.x
    Metrowerks CodeWarrior Pro 1
    Staz Software FutureBASIC 2.x.x
    Symantec THINK Pascal 4.0.x
    Symantec THINK Project Manager 7.0.x Symantec Project Manager 8.0.x
    Zedcor FutureBASIC 1.0.x
    If are programming in a different programming environment you will have to use Register Level Programming (RLP). For more information on RLP you can visit www.ni.com/support/daqsupp.htm and look under the Resources for register level programming link.

  • Can Group1 and Group2 of the PCI-DIO-32HS 6533 card be configured at the same time?

    Can the PClk1 and PClk2 run simultaneously when both groups 1 and 2 are configured?

    Tmax,
    Yes, both Group 1 and Group 2 of the PCI-DIO-32HS can be configured at the same time. Furthermore, both PCLK1 and PCLK2 can run simultaneously.
    Good luck with your application.
    Spencer S.

  • Who has had a PCI-DIO-32HS card fail, ever?

    I've looked through the forum somewhat and I've found little concerning the card itself failing.  For instance, I found something about the card failing due to driving it with a TTL high before it was powered, but that was about it as far as actual death of the card.  Hence, I'm wondering if others besides myself, and therefore my design using the PCI-DIO-32HS, have killed or had the death of a PCI-DIO-32HS DAQ card and what was determined to be the root cause in your case(s).
    Also, by chance, did your card's death also take down the PC such that it wouldn't POST (Power On Self Test) until the card was removed?
    Thank you all.

    First, the issue has not been resolved yet. I still have boards dying. At $1500 a pop, this issue needs to be resolved.
    I was mistaken about two things said earlier: 1) The G card has now failed; therefore, the recovery was a fluke, and 2) I thought 8.x was installed in the design's PC, but as it turns out it has been 9.x. (The version numbers are tough to remember. Sorry. I think it's 9.1.7.) Is there a known issue with that one also?
    What I really want to know is why the original board I returned to NI failed. I want to know specifically what slot contacts are holding up the PC, keeping it from performing its POST? I don't want to hear any more suggestions for installing version x.y.z. without also having a specific reason for why it should work. These cards are too expensive. There's something very wrong with this design such that I can't keep the DAQ card alive using Traditional DAQ software that has run for years. The system works until (it seems) you think the problem's been resolved, and then whammo! An esoteric error number in a window is thrown up. (It's not just one error. The error can change as you try in vain to avoid cycling power as the only way out of the now dead software.) You can't run the software past a button click due to the error window, but yet the PC itself works fine...unless you cycle the power: NO POST.
    What on earth in this design could be killing these cards? The PCI slot was tested via substitution with a video card and there was no issue found. I just can't keep the DAQ card alive. Help! Trying version x.y.z of the driver is not a good enough solution. Running software should not just out of the blue blow up a DAQ card and cripple the PC only at power-up. Rather, there should be an error, some incompatibility indication before the card is dead. Frying a $1.5K card...eventually...is not how you find the source of an incompatibility issue. Like I said, HELP!
    I'm suspecting the software is creating a bus contention somehow which doesn't end in an error but, rather, an internally shorted IC, where I'm guessing it's the large NI ASIC just above the card edge due to the considerably noticeable heat generated while the PC tries to POST, a short that is undetectable except that the software stops working, but nevertheless a short that won't let the PC continue its POST if power is removed and then reapplied to the PC. It's like the software has had a "sacrifice(PCI-DIO-32HS, legacy_sw);" function embedded into it that only gets called under certain circumstances, circumstances that involve the power-up sequence of a PC. Help!

  • Why ACK should be deasserted sometimes during the data acquisition with PCI-DIO-32HS burst mode handshaking?

    My peripheral device sends 32-bit data to the DIO board serially with PCLK 6MHz, about 300,000 times totally. The phenomenan like I mentioned in the summary above happens, and it causes some data missings.
    Though I know ACK is not always asserted as somewhere in the NI database says, I want to know why it happens. if I can. I wonder if it is just inevitable or not.
    Do I only have to add some buffer memories to my device and make it watch on the ACK changing? Or, is there any other good way to avoid this problem?

    Hi,
    Burst mode handshaking protocol needs to conditions to be meet before data can be transfered. The PCI-DIO-32HS need to be ready to transfer data and the external device needs to be ready to transfer data.
    The ACK line tells the external device when the PCI-DIO-32HS is ready and the REQ line tells the PCI-DIO-32HS when the external device is ready. When both are ready data should be transfered. This is the nature of Handshaking, guarenteed data transfer (when both devices are ready), but not at a guarenteed rate. Handshaking means that the two devices communicate with each other to determine when to transfer data.
    The PCI-DIO-32HS ACK line is toggling low because the PCI-DIO-32HS is busy catching up with the given transfer and is not ready to receive m
    ore data at this time. The ACK line is not something you can control, it is controlled by the PCI-DIO-32HS.
    Your application may be better suited for use with Pattern I/O if you are not using the handshaking lines, ACK and REQ, to control the flow of data. Pattern I/O does not use handshaking lines and clocks data in on every rising edge of the clock. You may receive an error if your system can not keep up with the transfer rate.

  • How do I create an interrupt on the PCI-DIO-96 from an external signal connected to the lines PC0 or PC3 of a port?

    Hi everybody,
    we are currently using the PCI-DIO-96 for data acquisition from an old AT-DIO-32F card. All PPIs and ports work in mode 0 (standard input/output). The manual mentions the possibility to create an interrupt from an external signal connected to the lines PC0 and PC3 of port C from a PPI. To get the interrupt I have connected my interrupt service routine to the PCI-DIO-96, enabled the master interrupt enable bit in the interrupt configuration register 2 and enabled interrupt enable bits of every PPI chip in the interrupt configuration register 1. The interrupt should be generated if a signal low-to-high transition occurs on th
    e lines PC0 or PC3 of a PPI. We've simulated the signal low-to-high transition with an external voltage source connected to the line PC0. We actually saw in the memory that the line toggled from state low to state high, but no interrupt was generated. I don't have a guess what I am doing wrong. Perhaps anybody knows the solution of this problems.
    Thanks and best regards.
    Sven Jungnickel

    You may want to try disabling your USB or IEEE-1394 host controller. It's possible that one of these devices could be on the same interrupt as you DIO-96 and causing the interrupt to not be serviced.
    Regards,
    Erin

  • PCI-DIO-32HS (PCI-6533) setup problem

    Hello
    I am in the process of setting up a Windows XP-based Labview 7.1 system and I am encountering a frustrating problem. Just to make sure I provide enough details, I'll describe what I've done so far, step-by-step (sorry if this gets tedious):
    First, I installed Labview and the NI-DAQ 7.3 drivers. I powered down the system and installed two PCI cards: a PCI-6031E and a PCI-DIO-32HS (PCI-6533) in PCI slots 1 and 2, respectively. I powered the system back up, went into MAX and configured the cards as follows:
    PCI-6031E: Device 1; AI: Polarity/Range=-10.0V - +10.0V, Referenced Single Ended; AO: Polarity=Bipolar; Accessory=SCB-100
    PCI-DIO-32HS: Device 2; Accessory=SCB-68
    I then started up Labview and ran my VI. This VI has been in use for 2 years now on the same NI hardware, so it's been well-tested and works great on other systems. However, when I run it on this system, the PCI-DIO-32HS spits out an error, with "Digital Buffer Write" as the source, and with a code of -10843 (buffer underflow).
    What's interesting is that I had this exact same problem when I was setting this system up in Mac OS 9. That time, I realized that the problem could have been due to the fact that I installed the hardware before I installed the software, so there may have been problems communicating with the device. By uninstalling everything and then re-installing it in the proper order, I solved the problem and was able to run the VI flawlessly. I'm assuming that these two problems are related in their nature, but this time around I was very careful to make sure that I did all of the setting up properly (I did it twice just to make sure. It did not work either time), so I'm not sure what could be the exact source of this one.
    Please let me know if you have any ideas as to what the source of this problem might be. Like I said before, I think there's probably a resource problem that's causing a communication failure which results in no data being sent to the DIO card (hence the buffer underflow error), but I can't figure out where to look for such a problem or how to fix it. Obviously, I'm rather new to Labview and everything about it, so the help is greatly appreciated.
    Thanks!

    Hi,
    Thanks for the reply. I have run the test panels, and I have not generated any errors in them. I've verified that I can definitely do output, because LEDs on my equipment turn on when turn on output on certain channels.
    So, I agree that the problem lies in the VI. I was not the author of the VI, however, so I'm not sure where to look. The author was also kind enough to have not provided any documentation. What would be a good example VI to run? I've never looked at any of them.
    As for how the program works, I don't believe there's any actual input coming back into the DIO-32HS. The system is used for electrophysiology. The DIO sends a signal to flash LEDs at given intervals. Electrodes then pick up an electrical signal from the retina of a mouse, which is sent to the DAQ card and written to a file. I have run complete tests, and proper data files were generated and contained expected voltage values. The only part that's not working right now is that the LEDs aren't flashing due to this error.
    I did some digging around in the program, but I couldn't come up with much. I verified that the program expects the DIO card to be Device 2, so there's no problem there. Aside from that, I couldn't find anything that seemed like it would apply.
    Thanks for your help! I have no experience with Labview, yet I've found myself placed in the "Labview expert" position over here, so I've kind of been forced into a sink-or-swim type crash course where I learn as I go.

  • PCI DIO 32HS

        Hi,
        I have a legacy VI that I am troubleshooting. It involves configuring input & output digital ports on our PCI-DIO-32HS.
    Two ports (Port B & C) are configured as outputs. I have a suspicion that Port C is not operating correctly (or at least some of the lines on Port C are not operational).
    Is there a way of verifying the output operation of Port C ? (I have checked out the Test Panels in MAX - maybe there is a more direct test ?)
    Earlier, our computer crashed when I tried to reboot. Immediately before that the VI & NI488.2 Communicator were running at the same time - perhaps there was a hardware conflict that caused the crash ? Besides this incident, the program has been running fine for several years...
    Finally, is the PCI-DIO-32HS available for sale ? If not, what is the closest substitute ?
      Any help would be greatly appreciated !
        Regards,
             ak

    Hello ak,
    What is it about port C that you believe is not working anymore? You could try generating on those lines, and then test the correct pins with a multimeter or scope.
    Please also do a device Reset from MAX and verify that the device passes a Self-Test.
    We no longer sell the PCI-DIO-32HS, but we do have a wealth of other cards that are HSDIO. I don't know what kind of specs you want, but this is a great starting spot: http://www.ni.com/highspeeddigitalio/
    Any card that starts with 65xx is a HSDIO card. I believe the PCIe-5635 will be the closest replacement spec-wise, but you will need DAQmx or NI HSDIO for the programming, I do not believe you can use Traditional DAQ.
    Thanks,
    Joel C
    National Instruments

  • Pci dio 32hs burst mode

    We would like to use simultaneous input output data acquisition using the
    burst mode protocol.
    The problem is that we notice that the operations are not simultaneous: first
    a group and after the second.
    We have try all tipe of pclk (internal and external) and we connect req1 and
    req2 to an external manual trigger to have the same handshaking signal to
    both the groups. We also try to differ the active high or low of both the
    groups parameters.
    In the vi attachment, you find the simple 2 groups acquisition chains and
    it's easy to see that if you use an external clock of 1 Khz with 3000 input-
    output samples, the total acquisition time would be 6 second instead of 3.
    For our application it's necessary to use this protocol
    (not the pattern
    generation that we have tested in continuos and it worked) so we would like
    to have a solution to this problem.
    Since the pci DIO 32HS's manual asserts that it's possible to have 2
    handshaking operation simultaneous we didn't aspect so many problems.
    Thank you for your time
    Pier

    Hi,
    Burst mode handshaking protocol needs to conditions to be meet before data can be transfered. The PCI-DIO-32HS need to be ready to transfer data and the external device needs to be ready to transfer data.
    The ACK line tells the external device when the PCI-DIO-32HS is ready and the REQ line tells the PCI-DIO-32HS when the external device is ready. When both are ready data should be transfered. This is the nature of Handshaking, guarenteed data transfer (when both devices are ready), but not at a guarenteed rate. Handshaking means that the two devices communicate with each other to determine when to transfer data.
    The PCI-DIO-32HS ACK line is toggling low because the PCI-DIO-32HS is busy catching up with the given transfer and is not ready to receive m
    ore data at this time. The ACK line is not something you can control, it is controlled by the PCI-DIO-32HS.
    Your application may be better suited for use with Pattern I/O if you are not using the handshaking lines, ACK and REQ, to control the flow of data. Pattern I/O does not use handshaking lines and clocks data in on every rising edge of the clock. You may receive an error if your system can not keep up with the transfer rate.

  • PCI DIO 32HS (6533) Suddenly giving "The device is not responding to the first IRQ level" error, and no longer functioning.

    Greetings NI folks,
      I'm an oceanographer, and have an sidescan sonar data aquasition computer running Windows XP SP2, and NiDAQ 7.0 (Legacy). For several years, this machine has worked flawlessly, but today, I booted it up to test the system for an upcoming job, and I got some strange errors in our sonar program. I tranced the problem to our NI-6533 PCI-DIO-32HS card. I launched NI Automation Explorer to test that the card was responsive, and when I click the "test panel", I get an error: "The device is not responding to the first IRQ level." Continue (yes/no). If I click yes, I can test the digital i/o's, but nothing happens, and all the tests fail (nonresponsive). I tried moving the card to another PCI slot, tried forcing it to have a specific IRQ that was unused by anything else, and finally tried moving it to another computer that had never been used with the DIO card. I'm still getting the error, and the card is nonresponsive. I'm at the limit of my abilities, and would like to know if there's anything else I can do, or should we send the card back to NI for repair/diagnosis.
    Thanks.

    Duplicate Post
    Best Regards
    Hani R.
    Applications Engineer
    National Instruments

  • Digital Handshaking with two PCI-DIO-32HS Cards

    Hardware: two PCI-DIO-32HS Cards
    Software: LabVIEW 5.1, NI DAQ 6.6
    Problem:
    I'd like to do burst digital handshaking with two PCI-DIO-32HS cards.
    One being used for sending bit stream while the other receive.
    Suppose I want to use burst handshake mode.
    How should I wire the connections?
    Where should I wire the REQ, and ACK line from the sending card?
    Should I wire REQ from card one to REQ of the other card?
    Also, how do I configure labVIEW VI to do burst handshaking mode.
    Can anyone send me a VI that can do this.
    Thanks a lot.

    Matt,
    I would recomend using the DIdoubleBufPatternGen.C examples that ships with NI-DAQ. You can find it in your \NI-DAQ\Examples\VisualC\Di folder. If you don't have this example on your machine, you can get it by running NI-DAQ Setup and selecting support for C/C++.
    This example does double buffering to allow you to continuously acquire data from your card. Data is transfered only when a full 1/2 buffer is ready. You can set how long to acquire data by setting the number of half buffers to read, or by modifying the read loop conditional parameters to fit you needs. See the NI-DAQ help on how to set you REQ pulse rate to 100kS/s.
    Nick W.
    www.ni.com/ask

  • Installing PCI DIO 32HS 6533 card

    I'm back to using DAQ after 5 years on other things...
    I can't find the CD that came with my PCI DIO 32HS 6533 card (my desk is a
    meter high mess of paper, disks, broken cards...)
    I installed NI-DAQ from the CVI 5.5 CD but upon reboot I still get the
    "Windows found some new hardware" without being able to point it to the
    correct driver, and in addition I get a "Missing NICFQ32.DLL" error.
    Any help ?
    Guillaume Dargaud
    CNR/IFA
    http://sung3.ifsi.rm.cnr.it/~dargaud/
    http://sung3.ifsi.rm.cnr.it/~domec/
    http://sodarserver.ifa.rm.cnr.it/
    "Q: How many software engineers does it take to change a lightbulb ?
    A: It can't be done; it's a hardware problem."

    Go to www.ni.com choose download software then drivers and updates then NI-DAQ
    then 6.8.1 for Windows (if you have windows)
    "Guillaume Dargaud" wrote:
    >I'm back to using DAQ after 5 years on other things...>>I can't find the
    CD that came with my PCI DIO 32HS 6533 card (my desk is a>meter high mess
    of paper, disks, broken cards...)>I installed NI-DAQ from the CVI 5.5 CD
    but upon reboot I still get the>"Windows found some new hardware" without
    being able to point it to the>correct driver, and in addition I get a "Missing
    NICFQ32.DLL" error.>>Any help ?>----------------->Guillaume Dargaud>CNR/IFA>http://sung3.ifsi.rm.cnr.it/~dargaud/>http://sung3.ifsi.rm.cnr.it/~domec/>http://sodarserver.ifa.rm.cnr.it/>"Q:
    How many software engineers does it ta
    ke to change a lightbulb ?>A: It can't
    be done; it's a hardware problem.">

  • I was trying to find out if the PCI-DIO-32​HS will take thermocoup​le readings?

    I have a PCI-DIO-32HS and a SCB-68 connector block. I am trying to figure out if the card will receive the input coming from a thermocouple.

    Dennis is right.
    however, if you feel like not spending more money on a analog input board, and have hands for a little electronics, here what you can do:
    1) use a 16bit D/A converter (eg DAC7744), connected to the card.
    2) connect the output to a comparator (LM311),  to compare with your own analog input. you might want to isolate the 2 inputs via INA105.
    3) connect the output via a pull up resistor directly to pin 1 of your parallel port.
    4) create a small Labview program for making a 16 (or 8 or 4) bit comparison process:
           - create an analog value of 0V (via 16 bit digital card)
           - check if response is true or false (higher or lower than your  analog in) from the parallel port
           - if true, send new analog value of -5V
    ....check again, 16 times.
    you got your analog value. of course this is a relatively slow process, as you have to read the parallel before each time you send the new analog value. yet, it is going to be much faster than a NI-USB 6008 for example. i expect a rate around the KHz at least.
    ... And here's where I keep assorted lengths of wires...

  • How to use the static lib of berkeleydb in VC6?

    I know there is a libdb45s.lib. But when I try to link my project to it, VC6 reports many errors. Even the getting start examples cannot link correctly. The documents coming with berkeley db do not tell me how to link project to the lib, no matter static or dynamic.
    Could anyone tell me how to use the static lib libdb45s.lib and how to link it properly?
    OS: Windows XP pro SP2
    IDE: Virsual C++ 6.0 sp6
    BDB: 4.5.20
    Here is what I have done to link the libdb45s.lib:
    1.Add BDB related diretorys to VC6 link/lib dirs
    2.Add #include <db.c> to my .cpp file, I use the C API
    3.Change Project Options
    Link-> Libs/Objects-> add "libdb45s.lib"
    C/C++-> code generation-> Use Run Time Library-> MutiThreaded
    Link-> Ignore Library-> MSVCRT
    4.Build, here is the output, hope it would be some help:
    --------------------Configuration: wordseg - Win32
    Release--------------------
    Linking...
    LINK : warning LNK4049: locally defined symbol
    "_fflush" imported
    LINK : warning LNK4049: locally defined symbol "__iob"
    imported
    LINK : warning LNK4049: locally defined symbol
    "__errno" imported
    LINK : warning LNK4049: locally defined symbol
    "_malloc" imported
    LINK : warning LNK4049: locally defined symbol
    "_realloc" imported
    LINK : warning LNK4049: locally defined symbol "_free"
    imported
    LINK : warning LNK4049: locally defined symbol
    "_fclose" imported
    LINK : warning LNK4049: locally defined symbol
    "_fopen" imported
    LINK : warning LNK4049: locally defined symbol
    "__pctype" imported
    LINK : warning LNK4049: locally defined symbol
    "___mb_cur_max" imported
    LINK : warning LNK4049: locally defined symbol
    "__isctype" imported
    LINK : warning LNK4049: locally defined symbol
    "_strchr" imported
    LINK : warning LNK4049: locally defined symbol
    "_printf" imported
    LINK : warning LNK4049: locally defined symbol
    "_strncmp" imported
    LINK : warning LNK4049: locally defined symbol
    "_strncpy" imported
    LINK : warning LNK4049: locally defined symbol "_atol"
    imported
    LINK : warning LNK4049: locally defined symbol
    "_getenv" imported
    LINK : warning LNK4049: locally defined symbol
    "__open" imported
    LINK : warning LNK4049: locally defined symbol
    "__close" imported
    LINK : warning LNK4049: locally defined symbol
    "_strftime" imported
    LINK : warning LNK4049: locally defined symbol
    "_memmove" imported
    LINK : warning LNK4049: locally defined symbol
    "_strtoul" imported
    LINK : warning LNK4049: locally defined symbol
    "_fwrite" imported
    LINK : warning LNK4049: locally defined symbol
    "_fgetc" imported
    LINK : warning LNK4049: locally defined symbol
    "_strtol" imported
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved
    external symbol __imp__strerror
    libdb45s.lib(db_getlong.obj) : error LNK2001:
    unresolved external symbol __imp__strerror
    libdb45s.lib(qam_verify.obj) : error LNK2001:
    unresolved external symbol __imp___snprintf
    libdb45s.lib(mp_mvcc.obj) : error LNK2001: unresolved
    external symbol __imp___snprintf
    libdb45s.lib(repmgr_util.obj) : error LNK2001:
    unresolved external symbol __imp___snprintf
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp___snprintf
    libdb45s.lib(env_region.obj) : error LNK2001:
    unresolved external symbol __imp___snprintf
    libdb45s.lib(log_put.obj) : error LNK2001: unresolved
    external symbol __imp___snprintf
    libdb45s.lib(qam_files.obj) : error LNK2001:
    unresolved external symbol __imp___snprintf
    libdb45s.lib(db.obj) : error LNK2001: unresolved
    external symbol __imp___snprintf
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved
    external symbol __imp___snprintf
    libdb45s.lib(db_pr.obj) : error LNK2001: unresolved
    external symbol __imp___snprintf
    libdb45s.lib(env_failchk.obj) : error LNK2001:
    unresolved external symbol __imp___snprintf
    libdb45s.lib(env_register.obj) : error LNK2001:
    unresolved external symbol __imp___snprintf
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved
    external symbol __imp___vsnprintf
    libdb45s.lib(log_debug.obj) : error LNK2001:
    unresolved external symbol __imp___vsnprintf
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved
    external symbol __imp__vfprintf
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved
    external symbol __imp__fprintf
    libdb45s.lib(db_pr.obj) : error LNK2001: unresolved
    external symbol __imp__fprintf
    libdb45s.lib(db_getlong.obj) : error LNK2001:
    unresolved external symbol __imp__fprintf
    libdb45s.lib(os_errno.obj) : error LNK2001: unresolved
    external symbol __imp__WSASetLastError@4
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__WSAGetLastError@0
    libdb45s.lib(os_errno.obj) : error LNK2001: unresolved
    external symbol __imp__WSAGetLastError@0
    libdb45s.lib(repmgr_method.obj) : error LNK2001:
    unresolved external symbol __imp__WSAGetLastError@0
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol __imp__WSAGetLastError@0
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__WSAGetLastError@0
    libdb45s.lib(env_open.obj) : error LNK2001: unresolved
    external symbol __imp__strncat
    libdb45s.lib(mut_win32.obj) : error LNK2001:
    unresolved external symbol __imp___getpid
    libdb45s.lib(os_pid.obj) : error LNK2001: unresolved
    external symbol __imp___getpid
    libdb45s.lib(txn_chkpt.obj) : error LNK2001:
    unresolved external symbol __imp__time
    libdb45s.lib(env_stat.obj) : error LNK2001: unresolved
    external symbol __imp__time
    libdb45s.lib(rep_record.obj) : error LNK2001:
    unresolved external symbol __imp__time
    libdb45s.lib(rep_backup.obj) : error LNK2001:
    unresolved external symbol __imp__time
    libdb45s.lib(env_recover.obj) : error LNK2001:
    unresolved external symbol __imp__time
    libdb45s.lib(txn_region.obj) : error LNK2001:
    unresolved external symbol __imp__time
    libdb45s.lib(log.obj) : error LNK2001: unresolved
    external symbol __imp__time
    libdb45s.lib(rep_region.obj) : error LNK2001:
    unresolved external symbol __imp__time
    libdb45s.lib(db_stati.obj) : error LNK2001: unresolved
    external symbol __imp__time
    libdb45s.lib(rep_util.obj) : error LNK2001: unresolved
    external symbol __imp__time
    libdb45s.lib(env_region.obj) : error LNK2001:
    unresolved external symbol __imp__time
    libdb45s.lib(txn.obj) : error LNK2001: unresolved
    external symbol __imp__time
    libdb45s.lib(db_idspace.obj) : error LNK2001:
    unresolved external symbol __imp__qsort
    libdb45s.lib(log_archive.obj) : error LNK2001:
    unresolved external symbol __imp__qsort
    libdb45s.lib(db_join.obj) : error LNK2001: unresolved
    external symbol __imp__qsort
    libdb45s.lib(mp_mvcc.obj) : error LNK2001: unresolved
    external symbol __imp__qsort
    libdb45s.lib(db_meta.obj) : error LNK2001: unresolved
    external symbol __imp__qsort
    libdb45s.lib(lock_list.obj) : error LNK2001:
    unresolved external symbol __imp__qsort
    libdb45s.lib(mp_sync.obj) : error LNK2001: unresolved
    external symbol __imp__qsort
    libdb45s.lib(txn_stat.obj) : error LNK2001: unresolved
    external symbol __imp__qsort
    libdb45s.lib(rep_record.obj) : error LNK2001:
    unresolved external symbol __imp__qsort
    libdb45s.lib(os_config.obj) : error LNK2001:
    unresolved external symbol __imp__wcscmp
    libdb45s.lib(env_config.obj) : error LNK2001:
    unresolved external symbol __imp__fgets
    libdb45s.lib(repmgr_method.obj) : error LNK2001:
    unresolved external symbol __imp__gethostname@8
    libdb45s.lib(os_open.obj) : error LNK2001: unresolved
    external symbol __imp___snwprintf
    libdb45s.lib(os_map.obj) : error LNK2001: unresolved
    external symbol __imp___snwprintf
    libdb45s.lib(os_unlink.obj) : error LNK2001:
    unresolved external symbol __imp___snwprintf
    libdb45s.lib(os_dir.obj) : error LNK2001: unresolved
    external symbol __imp___snwprintf
    libdb45s.lib(os_map.obj) : error LNK2001: unresolved
    external symbol __imp__wcsrchr
    libdb45s.lib(log_archive.obj) : error LNK2001:
    unresolved external symbol __imp___getcwd
    libdb45s.lib(lock_stat.obj) : error LNK2001:
    unresolved external symbol __imp__localtime
    libdb45s.lib(qam_files.obj) : error LNK2001:
    unresolved external symbol __imp__strrchr
    libdb45s.lib(ctime.obj) : error LNK2001: unresolved
    external symbol __imp__ctime
    libdb45s.lib(os_clock.obj) : error LNK2001: unresolved
    external symbol __imp___ftime
    libdb45s.lib(os_uid.obj) : error LNK2001: unresolved
    external symbol __imp__rand
    libdb45s.lib(os_uid.obj) : error LNK2001: unresolved
    external symbol __imp__srand
    libdb45s.lib(repmgr_msg.obj) : error LNK2001:
    unresolved external symbol __imp__ntohs@4
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol __imp__ioctlsocket@12
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol __imp__WSACleanup@0
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__WSACleanup@0
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol __imp__WSAStartup@8
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol __imp__WSASend@28
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol __imp__WSARecv@28
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol
    __imp__WSAEnumNetworkEvents@12
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol
    __imp__WSAWaitForMultipleEvents@20
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol __imp__WSAEventSelect@12
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__WSAEventSelect@12
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__WSAEventSelect@12
    libdb45s.lib(repmgr_windows.obj) : error LNK2001:
    unresolved external symbol __imp__WSACreateEvent@0
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__WSACreateEvent@0
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__WSACloseEvent@4
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__WSACloseEvent@4
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__closesocket@4
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__closesocket@4
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__accept@12
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__connect@12
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__socket@12
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__socket@12
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__htonl@4
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__htonl@4
    libdb45s.lib(getaddrinfo.obj) : error LNK2001:
    unresolved external symbol __imp__htonl@4
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__ntohl@4
    libdb45s.lib(repmgr_sel.obj) : error LNK2001:
    unresolved external symbol __imp__send@16
    libdb45s.lib(repmgr_util.obj) : error LNK2001:
    unresolved external symbol __imp__htons@4
    libdb45s.lib(getaddrinfo.obj) : error LNK2001:
    unresolved external symbol __imp__htons@4
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__listen@8
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__bind@12
    libdb45s.lib(repmgr_net.obj) : error LNK2001:
    unresolved external symbol __imp__setsockopt@20
    libdb45s.lib(getaddrinfo.obj) : error LNK2001:
    unresolved external symbol __imp__gethostbyname@4
    libdb45s.lib(getaddrinfo.obj) : error LNK2001:
    unresolved external symbol __imp__inet_addr@4
    Release/wordseg.exe : fatal error LNK1120: 47
    unresolved externals
    Error executing link.exe.
    wordseg.exe - 100 error(s), 25 warning(s)

    After adding MsWSock.Lib, WSock32.Lib, build returns following errors:
    (error count reduced from 100 to 71)
    --------------------Configuration: wordsegzjp - Win32 Release--------------------
    Compiling...
    main.cpp
    Linking...
    LINK : warning LNK4049: locally defined symbol "_fflush" imported
    LINK : warning LNK4049: locally defined symbol "__iob" imported
    LINK : warning LNK4049: locally defined symbol "_malloc" imported
    LINK : warning LNK4049: locally defined symbol "_realloc" imported
    LINK : warning LNK4049: locally defined symbol "_free" imported
    LINK : warning LNK4049: locally defined symbol "_fclose" imported
    LINK : warning LNK4049: locally defined symbol "_fopen" imported
    LINK : warning LNK4049: locally defined symbol "__pctype" imported
    LINK : warning LNK4049: locally defined symbol "___mb_cur_max" imported
    LINK : warning LNK4049: locally defined symbol "__isctype" imported
    LINK : warning LNK4049: locally defined symbol "_strchr" imported
    LINK : warning LNK4049: locally defined symbol "_printf" imported
    LINK : warning LNK4049: locally defined symbol "_strncmp" imported
    LINK : warning LNK4049: locally defined symbol "_strncpy" imported
    LINK : warning LNK4049: locally defined symbol "_atol" imported
    LINK : warning LNK4049: locally defined symbol "_getenv" imported
    LINK : warning LNK4049: locally defined symbol "__open" imported
    LINK : warning LNK4049: locally defined symbol "__close" imported
    LINK : warning LNK4049: locally defined symbol "_strftime" imported
    LINK : warning LNK4049: locally defined symbol "_memmove" imported
    LINK : warning LNK4049: locally defined symbol "_strtoul" imported
    LINK : warning LNK4049: locally defined symbol "_fwrite" imported
    LINK : warning LNK4049: locally defined symbol "_fgetc" imported
    LINK : warning LNK4049: locally defined symbol "_strtol" imported
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved external symbol __imp__strerror
    libdb45s.lib(db_getlong.obj) : error LNK2001: unresolved external symbol __imp__strerror
    libdb45s.lib(qam_verify.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(mp_mvcc.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(repmgr_util.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(repmgr_net.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(env_region.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(log_put.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(qam_files.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(db.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(db_pr.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(env_failchk.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(env_register.obj) : error LNK2001: unresolved external symbol __imp___snprintf
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved external symbol __imp___vsnprintf
    libdb45s.lib(log_debug.obj) : error LNK2001: unresolved external symbol __imp___vsnprintf
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved external symbol __imp__vfprintf
    libdb45s.lib(db_err.obj) : error LNK2001: unresolved external symbol __imp__fprintf
    libdb45s.lib(db_pr.obj) : error LNK2001: unresolved external symbol __imp__fprintf
    libdb45s.lib(db_getlong.obj) : error LNK2001: unresolved external symbol __imp__fprintf
    libdb45s.lib(os_errno.obj) : error LNK2001: unresolved external symbol __imp___errno
    libdb45s.lib(env_open.obj) : error LNK2001: unresolved external symbol __imp__strncat
    libdb45s.lib(mut_win32.obj) : error LNK2001: unresolved external symbol __imp___getpid
    libdb45s.lib(os_pid.obj) : error LNK2001: unresolved external symbol __imp___getpid
    libdb45s.lib(txn_chkpt.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(env_stat.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(rep_record.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(rep_backup.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(env_recover.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(txn_region.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(log.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(rep_region.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(db_stati.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(rep_util.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(env_region.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(txn.obj) : error LNK2001: unresolved external symbol __imp__time
    libdb45s.lib(db_idspace.obj) : error LNK2001: unresolved external symbol __imp__qsort
    libdb45s.lib(log_archive.obj) : error LNK2001: unresolved external symbol __imp__qsort
    libdb45s.lib(db_join.obj) : error LNK2001: unresolved external symbol __imp__qsort
    libdb45s.lib(mp_mvcc.obj) : error LNK2001: unresolved external symbol __imp__qsort
    libdb45s.lib(db_meta.obj) : error LNK2001: unresolved external symbol __imp__qsort
    libdb45s.lib(lock_list.obj) : error LNK2001: unresolved external symbol __imp__qsort
    libdb45s.lib(mp_sync.obj) : error LNK2001: unresolved external symbol __imp__qsort
    libdb45s.lib(txn_stat.obj) : error LNK2001: unresolved external symbol __imp__qsort
    libdb45s.lib(rep_record.obj) : error LNK2001: unresolved external symbol __imp__qsort
    libdb45s.lib(os_config.obj) : error LNK2001: unresolved external symbol __imp__wcscmp
    libdb45s.lib(env_config.obj) : error LNK2001: unresolved external symbol __imp__fgets
    libdb45s.lib(os_open.obj) : error LNK2001: unresolved external symbol __imp___snwprintf
    libdb45s.lib(os_map.obj) : error LNK2001: unresolved external symbol __imp___snwprintf
    libdb45s.lib(os_unlink.obj) : error LNK2001: unresolved external symbol __imp___snwprintf
    libdb45s.lib(os_dir.obj) : error LNK2001: unresolved external symbol __imp___snwprintf
    libdb45s.lib(os_map.obj) : error LNK2001: unresolved external symbol __imp__wcsrchr
    libdb45s.lib(log_archive.obj) : error LNK2001: unresolved external symbol __imp___getcwd
    libdb45s.lib(lock_stat.obj) : error LNK2001: unresolved external symbol __imp__localtime
    libdb45s.lib(qam_files.obj) : error LNK2001: unresolved external symbol __imp__strrchr
    libdb45s.lib(ctime.obj) : error LNK2001: unresolved external symbol __imp__ctime
    libdb45s.lib(os_clock.obj) : error LNK2001: unresolved external symbol __imp___ftime
    libdb45s.lib(os_uid.obj) : error LNK2001: unresolved external symbol __imp__rand
    libdb45s.lib(os_uid.obj) : error LNK2001: unresolved external symbol __imp__srand
    libdb45s.lib(repmgr_windows.obj) : error LNK2001: unresolved external symbol __imp__WSASend@28
    libdb45s.lib(repmgr_windows.obj) : error LNK2001: unresolved external symbol __imp__WSARecv@28
    libdb45s.lib(repmgr_windows.obj) : error LNK2001: unresolved external symbol __imp__WSAEnumNetworkEvents@12
    libdb45s.lib(repmgr_windows.obj) : error LNK2001: unresolved external symbol __imp__WSAWaitForMultipleEvents@20
    libdb45s.lib(repmgr_windows.obj) : error LNK2001: unresolved external symbol __imp__WSAEventSelect@12
    libdb45s.lib(repmgr_sel.obj) : error LNK2001: unresolved external symbol __imp__WSAEventSelect@12
    libdb45s.lib(repmgr_net.obj) : error LNK2001: unresolved external symbol __imp__WSAEventSelect@12
    libdb45s.lib(repmgr_windows.obj) : error LNK2001: unresolved external symbol __imp__WSACreateEvent@0
    libdb45s.lib(repmgr_sel.obj) : error LNK2001: unresolved external symbol __imp__WSACreateEvent@0
    libdb45s.lib(repmgr_sel.obj) : error LNK2001: unresolved external symbol __imp__WSACloseEvent@4
    libdb45s.lib(repmgr_net.obj) : error LNK2001: unresolved external symbol __imp__WSACloseEvent@4
    Release/wordsegzjp.exe : fatal error LNK1120: 28 unresolved externals
    Error executing link.exe.
    wordsegzjp.exe - 71 error(s), 24 warning(s)

  • Register Level programming of the AT-DIO-32HS

    I am working with a piece of software that was written using the AT-DIO-32F card. The original programmer did NOT use the National Instruments driver with that card, but rather used a software library that allowed him to access and manipulate the registers directly on that board. The name of the library is called NTPORT (http://www.zealsoft.com/ntport/index.html).  He did this because he was not able to meet the timing requirements using the NI driver.
    We have to replace the AT-DIO-32F card with the AT-DIO-32HS card, and I would like to know if I can continue to do register level programming with the 32HS card.  I have found that I also can not meet my timing requirements using the driver that comes along with the 32HS card.
    I checked this web page (http://digital.ni.com/public.nsf/allkb/B08F4125A9325B3F862565CC0073E68F?OpenDocument), and did not find the AT-DIO-32HS listed. Does this mean I can not program its' registers ?
    Any feedback would be appreciated !!
    Thanks !!

    Hi Raminta-
    The Measurement Hardware Driver Development Kit (MHDDK) provides examples and register documentation for the 653x devices (which includes the AT-DIO-32HS).  The DIO-32F and DIO-32HS devices are quite similar, so it is possible that your existing code will work.  The resources on the MHDDK page should help you fill in any differences.
    Thanks-
    Tom W
    National Instruments

Maybe you are looking for