No more SC-2040 in DAQMX 8. 1 ??

hello all,
I'm currently in a process to port my daq software (lw-cvi) to DAQMX
(formerly: traditional NI-DAQ) and had already finished some parts,
but still problems.
so I decided to upgrade to DAQMX 8.1, but now, I noticed, that the
SC-2040 S/H amplifier which I used for simultaneous scanning with
E-series boards, seems no longer available in MAX 4.0.3 (from DAQMX 8.1) as an accessory for my new M-series board (PCI-6250).
anyone knows what's going on here ?
thanks.
Once the game is over, the king and the pawn go back into the same box.

The SC-2040 didn't work properly in NI-DAQmx 8.0 when only configured in MAX. The PCI-6143 simultaneously sampling DAQ board is a much better choice than a combination of an M-Series board and a SC-2040 so the decision was made to remove it from the list of  accessories in NI-DAQmx 8.1
Still it's possible to work with the SC-2040 and an M-Series board with NI-DAQmx 8.1. Instead of configuring the SC-2040 as an accessory you can add some function calls to your code to export and configure the necessary timing signals for the board. Please refer to this document in the NI knowledge base for a detailed description.
Best regards,
Jochen Klier
National Instruments Germany

Similar Messages

  • PXI-6255 not identified in MAX as DAQmx

    We recently purchased a PXI-8108 controller for use as a spare and I'm having difficulty getting it to play well with our existing hardware and software. The controller we have been using is an older PXI-8106.
    The new controller has Windows 7 where the old had XP, so I had to use more recent versions of PXI Platform Services and MAX, as well as DAQmx. The versions I've installed are: PXI Platform Services 3.0.4, MAX 5.3.1, DAQmx 9.2.2. I can't use more recent version of DAQmx because our we are using LabVIEW 8.5.1 and anything more recent doesn't support that.
    The 6255 is showing up in the device manager under Windows, and the properties show that it is using the same hardware driver (nixsrkw.sys, rev. 1.13.0f4) as we use on the old controller. The 6255 also shows up in MAX, with a device identifier of PXI13::15:INSTR, but not listed as a DAQmx device. So, when I import the MAX settings file, the defined tasks won't run.
    I haven't found any postings in the forum that quite match this scenario. Anyone have any ideas?
    Thanks,
    Mike

    Mike,
    Firstly, I want to let you know that you will have problems using LabVIEW 8.5 with Windows 7.  The oldest version of LabVIEW supported in Win 7 is LabVIEW 2009 SP1:
    http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB
    About seeing your device in MAX, can you post a screenshot of what it looks like?
    Jon F.
    Applications Engineer
    National Instruments

  • Why can't I modify the property of a DAQmx timing node?

    I have right click the property and click "select property> browse>search property> more:reference clock:source". But the property list didn't update and I can't modify the property to "reference clock:source".
    Help me on this!
    Thanks!

    I think this article might be helpful, even if you are in a more recent version of DAQmx.  Otherwise, we might be looking at reinstalling the drivers.
    Kyle B  |  Product Support Engineer  |  ni.com/support

  • DAQmx input terminal configuration and sample mode choice

    Hi,
    I am studying "Timing and Synchronization Features of NI-DAQmx" from the following link,
     http://zone.ni.com/devzone/cda/tut/p/id/4322 
    Could
    anyone tell me in Figure 2, how to do input terminal configuration in
    the "DAQmx creat virtual channel" part? Shoud I just double click on
    the icon to change it? Or there is some way that I can show it in the
    block diagram like the sample mode in the DAQmx part?
    One
    more question, in the DAQmx timing part, how can I put "Continous
    Samples" there? Is it from the function pallette? Thank you.
    Solved!
    Go to Solution.

    You just right click on the terminal and select Create constant. You will get an constant on your BD with the appropiat type. Guess this covers 90% of yopur question. But, keep comin'.
    Felix
    www.aescusoft.de
    My latest community nugget on producer/consumer design
    My current blog: A journey through uml

  • 100% CPU usage after starting/joining a call

    This problem has been persisting for a few months now, and I haven't found a fix. Sometimes when I would start or join a call, the first thread of my i7 would shoot up to 100% usage (Monitored with MSI Afterburner). I originally thought it was because I had an older version of Skype, but I updated to the latest version and still had the issue. To get the usage to go down, I either have to restart the laptop or put it into sleep mode. When I checked the task manager, Skype was only using 0%-2% of my CPU, but System and System Interrupts run at higher usage (6%-7% each). I am running Windows 8.1 on a laptop with the desktop version of Skype. Please note that this also does not happen every time, just on some occasions.
    EDIT: It eventually happens, but not always right away.

    Yes, you can use NI-DAQmx with Visual C++ and with Mesurement Studio 7 or later you also have Microsoft Visual C++ class libraries for NI-DAQmx.
    If you are now developing a application I would advice to move to DAQmx since this the Traditional libraries are nolonger activly developed, we will only be adding new features and hardware to NI-DAQmx, thus for future support of the application it's better to use NI-DAQmx then Traditional NI-DAQ.
    For more information on NI-DAQmx see:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/ee47b125bb9e053686256fbc0014c384?OpenDocument
    Met vriendelijke groet / Kind regards,
    Karsten
    Applications Engineer
    National Instruments

  • Problem in bodi

    I have coded like this
    $TEXT_LINE_VALUE = sql( 'ds_stage','SELECT text_line FROM MANAGEMENT_LONGTEXT where ROOT = 43004003');
    in sql the value is having 1500 characters ,but in bodi it is returning 1020 characters only..
    the length of $text_line_value is 8000 which I have declared (This may not be the problem),
    I tried printing it like this too
    print(   sql( 'ds_stage','SELECT text_line FROM MANAGEMENT_LONGTEXT where ROOT = 43004003') );(here is the real problem)
    In the trace also I can see only 1020 characters...
    what is the maximum limit a sql transform can return in bodi??

    Try the same SELECT statement in SQL SERVER. (if that is your database). Copy and paste the retreived string into a notepad. It shows only 1020 characters.
    Cannot blame BODI for this
    What if the string length is more that 2040? How about this?
    $G_String_Start = 1;
    $G_String_Limit = 1020;
    $G_String = '';
    while($G_String_Limit <= 8000)
    begin
    $G_String = $G_String||sql('DATASTORE','SELECT substring(STRING, [$G_String_Start],[$G_String_Limit]) FROM STRING_TABLE');
    $G_String_Start = $G_String_Start + 1020;
    $G_String_Limit = $G_String_Limit + 1020;
    end
    print($G_String);
    Regards,
    Suneer.

  • Managing Tasks on Ethernet cDAQ - Best Practice

    Hi all,
    I'm currently working on a multi-station machine to perform functional product tests using an NI cDAQ 9188. Each station in the machine performs the same function but is intended to run independently. Basically a given station is loaded with a part, tested, sorted, a new part is installed and repeats. During this process other stations are undergoing the same procedure and sharing the same cDAQ. 
    During this testing digital signals (48) are turned on/off and analog signals (24) are being read between all stations. I've found that in contrary to a PCI task, the ethernet cDAQ tasks have quite a delay (~750 ms) when starting / stopping. Prior to this project I've only had experience using PCI tasks where I could read N Samples when needed without much start-up delay. Same goes for writing digital samples.
    The solution I've implemented for this is to create a continuous analog read VI that reads all analog signals and loops in the background continuously writing to a global variable. When a given station gets to a point where it needs to read signals, it pulls the desired index from the global array at that point in time. I also have a similar solution set up for the digital task, except it is reading a global variable for digital states and applies that to the task on each loop iteration. Normally I try to avoid continous loop senarios but the PC I'm using lets me get away with it. 
    Basically what I really need is subVI that starts the analog or digital task, but is idle until called by any module and returns N samples. This VI needs to act as a gate for analog read requests to avoid any reserved resource issue. I can't really think of how to accomplish this. 
    Any ideas?

    If you're looking for more control over the DAQmx task, perhaps you could utilize the DAQmx Control Task VI to control which state the task is in?
    http://digital.ni.com/public.nsf/allkb/3D9CF4F4A0549F40862574420029ECCD
    http://zone.ni.com/reference/en-XX/help/370466V-01/mxcncpts/taskstatemodel/
    Michael K.

  • Multiple scxi 1127 switches scanning, dmm 4070

    Hi,
    I am using 2 switches SCXI-1127 in a PXI/SCXI combination chassis. The readings are done through a dmm 4070.
    I need to scan 60 thermocouple channels, i.e. 32 on the first one and 28 on the second switch. Now, I found http://zone.ni.com/devzone/cda/tut/p/id/3658 stating that a scanning multiple SCXI switches is using legacy DAQ functions in niSwitch for these specific siwtch cards (1127).
    What version of niSwitch was it? Is it still true now? Why is that? Or should I use the new way using DAQmx?
    thank you
    alex 

    Hi Alex,
    This is still the case with NI-Switch 3.3.1.  Due to hardware limitations, scanning multiple SCXI-1127 modules is not a simple task with the NI-Switch driver.  I would recommend using the DAQmx example "DAQmx Multi Switch Synch.vi" if you are performing synchronous scanning.  I have taken a screen shot of the front panel of a working VI to help get you started.
    In general, it is more efficient to use DAQmx when scanning multiple switches.  When using NI-Switch to scan multiple switches, it is necessary to maintain a session for each switch module.  When using DAQmx Switch, you need only open one task.  Using DAQmx Switch increases programming efficiency, keeping your code neat and maintainable.
    If you need further explanation or if you have further questions, please let me know!
    Chad Erickson
    Switch Product Support Engineer
    NI - USA
    Attachments:
    synchronous scanning.JPG ‏136 KB

  • Configure PXI-2567 to Trigger on Rising Edge using LabWindows​/CVI

    I need some help configuring the trigger edge for a PXI-2567 using Labwindows/CVI.  I have been able to successfully create and execute a scan list using both the ni-switch and daqmx APIs.  However, currently the PXI-2567 triggers on the falling edge of an input trigger.  I need to configure it to trigger on the rising edge of an input trigger.  Every function I could find in the daqmx API for configuring the trigger edge gave a non-fatal runtime error, and I could find no such functions in the ni-switch API.
    Any help configuring the input trigger edge on the PXI-2567 using Labwindows/CVI would be appreciated.
    Thanks

    Hi JonRice,
    You can configure the scan list to execute on the rising edge of an input trigger.  Here are the Labwindows/CVI and LabVIEW functions you would want to use to retrieve, specify or verify the edge of a digital signal that advances to the next entry in a scan list.
    NI-DAQmx C Property: More >> Advance >> Digital Edge >> Edge
    You can get/set/reset this property using:
    DAQmxGetDigEdgeAdvTrigEdge
    DAQmxSetDigEdgeAdvTrigEdge
    DAQmxResetDigEdgeAdvTrigEdge
    NI-SWITCH C Attribute: NISWITCH_ATTR_TRIGGER_INPUT_POLARITY
    You can get/set/check this attribute using:
    niSwitch_GetAttributeViInt32
    niSwitch_SetAttributeViInt32
    niSwitch_CheckAttributeViInt32
    NI-DAQmx LabVIEW Property: More:Advanceigital Edge:Edge
    DAQmx Trigger Property Node
    Short Name: Adv.DigEdge.Edge
    NI-SWITCH LabVIEW Property: Trigger Input Polarity
    niSwitch Property Node
    Short Name: Trigger Input Polarity
    Hope this helps!  Let me know if you have further questions.
    Chad Erickson
    Switch Product Support Engineer
    NI - USA

  • VPN server claims I have multiple local logins

    I have successfully been logging in from my home Linux box to the company VPN using AnyConnect with DuoPush for about a month. As of last night I can no longer log in. The AnyConnect client says somethng like, "AnyConnect profile settings mandate a single local user, but multiple local users are currently logged into your computer.  A VPN connection will not be established."
    I am the only one on this Linux system. I have rebooted. I have forcibly rotated wtmp and utmp logfiles in case AnyConnect was confused by my not logging out when the system had to be shut down in a hurry due to A/C failure. The "last" command shows only me logged in. The "who" command shows me at the console, and on various ptys connected to xterms; I even killed the xterms at one point just to be sure that wasn't confusing it (this should be unnecessary but I was trying everything I could thnik of).
    What is AnyConnect looking at that convinces it there are multiple local logins?
    Thanks.

    Hi,
    You cannot use Windows Server Backup to back up file and folders on volumes that require more than 2040 GB (or 2 TB). However, as long as the data size is less than 2 TB, you can perform a file or folder backup.
    If you configure windows server backup to backup this 4TB volume to 8TB every 1 hour for period of 12 hours every day, you will get 12 versions shadow copies. You can now use a single backup to back up both the system state and other data on your server. These
    system state backups are now faster and require less space for multiple versions because they use shadow copies for versioning, similar to volume based backups, and not individual folders for each version.
    Windows Server Backup does not require user intervention to periodically delete older backups to free up disk space for newer backups—older backups are deleted automatically.
    For more detailed information, please refer to the article below:
    Windows Server Backup Overview
    http://technet.microsoft.com/en-us/library/cc772523.aspx
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • PCI-6602 Initial Delay

    Hello,
    Currently I use the code below to run the counters at a fixed frequency/duty cycle.  After the first counter fires the rest of the counters take their turn firing using the inital delay terminal on the create channel vi.  It works good and keeps them all from firing at once.
    Now, I need to change the frequency/duty cycle once a second for 70 seconds (a table of 70 different points) and then repeat until I want to stop.  I am able to do that with no problems.
    My problem is setting my initial delay every second based on my frequency to keep a nice ripple effect.  In order to set the initial delay I have to stop the task.  Is there another way to keep the counters evenly spaced out (a nice ripple) dependent on frequency without stopping the task?
    Solved!
    Go to Solution.

    I'm supposing that your need to stagger the "firing" of the injectors means that you're concerned with the timing of the pulses' active edges.  Whether they are active rising or falling may not be particularly relevant if we can simply make them very short duration.
    1. I'd start by suggesting you figure out the max reasonable freq you'll ever need to accomodate, and then plan to stagger the firings across that same interval of time even when you operate at a slower freq.  This will simplify things considerably.
    2. Configure all your slave counters to be retriggerable (as you're already doing), but REMOVE the call to DAQmx Timing.vi   They will all then be retriggerable single pulse generators.  Continue to have them triggered by CTR0, the master clock.
    3. Program the slaves in terms of Low Time / High Time.  Assuming an idle state that's Low (the default if I recall correctly),  set each "initial delay" equal to that counters' unique "low time" and set the minimum "high time" your system can accomodate. 
       Note:  unless the behavior has changed in more recent versions of DAQmx, the "initial delay" value is used after the 1st trigger while the "low time" value is used for all subsequent triggers.  Don't ask *me* why, but NI folks have weighed in on this in prior threads, calling it "expected behavior".   Expected by exactly whom is what I wonder.  I've yet to see a single comment saying, "Yeah, great, that's just how I *wanted* it to behave."   ANYWAY...
    4. Start all your slave counters before starting the master.
    5. The freq of the master counter can be changed on-the-fly without stopping and reprogramming it.  All the slave counters will continue to fire one single pulse per active edge of the master.
    6.*  Speculative idea, I haven't verified this.  You can *probably* update the low time / high time pairs of the slave counters on-the-fly as well.  If so, this will let you spread the "ripple" across more of the available interval when operating at lower speeds.  It sounds like your app can live with the possibility that these slave timing updates may not occur within the same master pulse cycle.
    -Kevin P

  • Is there a way to replace vilogger.d​ll and loggerdata​.dll (from VI logger version 1.1.1)

    I have a Labview vi developed from Labview 7 running on Windows XP.  It uses VI logger dlls to acquire data from NI multifunction daq board.  Recently I need to upgrade the system from Windows XP to Windows 7(32bit) and also upgrading to Labview 2010 (32bit).  When I open the vi from Labview 2010, the Labview crashes.  After a while of troubleshoot the problem, I manage to find out the root cause.  It was the problem of the VI logger dlls (vilogger.dll and loggerdata.dll).  I was able to open the vi with labview 2010 running on Windows 7 by deleting these two dlls.  Of cause, it is open but can not run because the vi has broken subvi that is calling the dlls.
    If I put the dll files back to the system and reconnect (reconfigure) the subvi/s with these two dlls then I can run the vi but the Labview will crash immediately.
    Need help to correct or replace these problematic dlls.

    As you should know, VI Logger is an obsolete product that is no longer sold or supported. You could try the procedure here for LabVIEW 8.2.
    You could also skip the old VI Logger calls and acquire the data in a more direct manner with DAQmx calls.

  • Run DAQ 6009 in differents VIs at the same time

    Hi, I need to use the DAQ 6009 in two or more differents subVIs at te same time.
    I have a main VI that runs two subVIs in parallel. Both subVI reads two different channels. 
    The problem is when a subVI "open" or inizializes the DAQ before others and It just read two channels.
    Can I use the DAQ in subVIs at te same time?
    Solved!
    Go to Solution.
    Attachments:
    Ejecucion en paralelo.jpg ‏39 KB
    DAQ.jpg ‏49 KB

    Hello rvenge,
    As for your first question- you can look up errors via Help>>Explain error...  Some errors will have multiple listings, which means that different scenarios or toolkits may return the same error code for a different reason.  Refer to this KnowledgeBase for more information on common DAQmx errors:
    KnowledgeBase 2XQEAPQJ: Common NI-DAQmx Error Codes and Solutions: Codes -50103 and -200000 to -200299
    http://digital.ni.com/public.nsf/allkb/001DA4DB6A31CF8886256D33006FA857
    On to the queues- it's not clear what you're trying to do here- it looks like you're doing some operations on the two input channels and then enqueuing them as well as the output of the operation.  I think you should take a step back and look at why you need to operate on the data asynchronously to begin with- do you need to stream all of your data from each channel to separate VIs? Would it be possible to process the data and then send the final value on to its destination?  If you do need to do this sort of operation, then yes, you'll need one queue for each location you want to read in.  I would recommend creating an Action Engine Queue handler to isolate the data transfer mechanism from your acquisition code rather than wiring everything through as you have.
    Regards,
    Tom L.

  • Are there DASYLAB 6.00.07 hardware drivers for the NI USB-9215

    I'm working with Dasylab 6.00.07. Do you know whether there are allready any hardwaredrivers for the NI USB-9215 ?

    At this time, DASYLab only works with NI hardware via the traditional NI-DAQ interface. Any board that is not supported via NI-DAQ will not work with DASYLab V8.
    The data sheet for the USB-9215 says:
    USB-9211 and USB-9215 devices each come with a ready-to-run
    data logger application that acquires and logs up to four channels of
    analog data. For more functionality, the NI-DAQmx Base driver
    software is a multiplatform driver with a limited NI-DAQmx
    programming interface.
    This says that it is not supported via NI-DAQ, and is not currently supported by DASYLab.
    We are actively working to ensure DASYLab's support for the DAQmx interface - watch for updates of the software!
    Please note that new driver support, such as this,
    will require an upgrade to the released version of DASYLab. It is not possible to update V7 or earlier with the changes required to fully support DAQmx.
    - cj
    Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

  • About PXI-6220 PXI-6221

    We want to use PXI-6220 or PXI-6221 to design a system. And we will use the CVI or Labview, but we cannot find the PROGRAMMING MANUALS of PXI-6220 or PXI-6221.Where can I get them? Thanks!

    Hi wenyan,
    You can program both the PXI-6220 and the PXI-6221 using the NI-DAQmx driver. The following tutorial is a very helpful:
    Learn 10 Functions in NI-DAQmx and Solve 80% of Data Acquisition Applications
    Also, both LabVIEW and CVI come with various data acquisition shipping examples (Help >> Find Examples). I suggest using those as starting points.
    If you've installed the DAQmx driver, you should be able to find DAQmx Help from (assuming you're using WindowsXP) Start>>Programs>>National Instruments>>NI-DAQ
    More information on the DAQmx functions can be found:
    NI-DAQmx Help (User Manual)
    Hope this helps,
    Lesley Y.

Maybe you are looking for