X series device synchronization

Hello,
I have a simple problem and cannot find any solution:
I have two PCIe-6320 devices connected with RTSI cable. The cable is registered and works correctely.
I create two analog input tasks and synchronize them with OnBoard Clock- it wirks correctly.
Now when I try to add counter output task (to generate 12 pulses for SSI encoder) I get error -89137.
What clock should I use to run analog and digital task in the same time?
Attachments:
CreateDAQChannels.vi ‏54 KB

Dear vcb,
First of all, let me welcome you to the NI forums. I am looking forward to work with you on solving the issue.
For the first step I recommend you to read this KB about the specific error code, it may help: 
Why Do I Get Error 89137 "Specified route cannot be satisfied..." When Routing PFI Lines Over RTSI?
http://digital.ni.com/public.nsf/allkb/A7A4024278353BF7862570230072C6E1
It is also important to note that the routing in your case is 10MhzRefClock to RTSI0, (it is not wired to Sample Clock in your VI). 
You could also check the DAQmx Device Configuration palette, where you can use an API to route within the device. It is generally adviced to do RTSI signal sharing in the following way:
Use DAQmx Export Signal.vi and/or DAQmx Export Signal Property Node
There you have a property for TimeBase sharing. In the other device, if you wire a constant to you TimeBaseSrc, you can right click the constant -> I/O Name Filtering.. --> Include Advanced Terminals
This way you get access to more options. From there you can specify RTSI0 as TimeBase.
Please let me know if you found these information useful, and/or if you need more help with the issue.
Best regards,
Peter
Peter L.
National Instruments Hungary
Applications Engineer

Similar Messages

  • Synchroniz​ing AI and Counter Tasks in DSA and M Series devices

    Hello DAQ fellows, I am new in the Counter field, so it would be really helpful to have your comments and advices about my application.
    I need to acquire simultaneouslythe following signals:
    - AI Voltage signal with a DSA device (PXI 4461).
    - AI voltage signal with a M Series device (PXI 6250).
    - Periods between TTL pulses signal with one counter of the same M Series device. I want to use the counter as it is shown in the figure 7-8 attached below.
    You can see my approach in the vi attached below (4461-6250ai-6250Ctr.vi). The 4461 is the master device.
    For the synchronization between both AI tasks I am using the "SampleClockTimebase" of the master device as a source for the 6250. I am also using the "StartTrigger" signal from the master device to trigger the start of the AI acquisition in the 6250. As I understand, this configuration is OK.
    Now come the second stage, which is to include the Ctr task to the acquisition process. I am creating the 3 tasks previously with another vi, the vi which creates the counter task (CreateTask6250Ctr.vi) is also attached. Now in the measurement vi (4461-6250ai-6250Ctr.vi), I use the "SampleClock" of the 6250-AI task in order to synchronize the AI with the Ctr task (I am not sure that this is the proper way to do this). Then I ask the "CounterTimebase.Source" in order to know which one is been used as SOURCE signal for the tick counting between the TTL pulses. Finally, I use the same "StartTrigger" signal from the master device to trigger the start of the Ctr task. In this way, when the AI task from the 4461 is started, it give the "StartTrigger" signal to the AI and Ctr tasks from the 6250 and the 3 start at the same time.
    What do you think. am I right with my approach?
    Is the Ctr task properly created to use the counter as in figure 7-8?
    Are the three tasks properly synchronized?
    Which other options do I have in order to synchronize the Ctr task with the other 2?
    Thanking in advance,
    Cristián
    Attachments:
    4461-6250ai-6250Ctr.vi ‏1561 KB
    Fig 7-8 from M SeriesUserManual.jpg ‏16 KB
    CreateTask6250Ctr.vi ‏35 KB

    Could I also use the PXI_Clk10 as a "ReferenceClock.Source" for the three tasks in order to synchronize them? I mean, instead of using the "SampleClock" of the AI task of the 6250 and the Ctr tasks of the same device. See the attachment to see what I mean.
    Greetings,
    Cristián
    Attachments:
    4461-6250ai-6250Ctr - PXI_Clk10.vi ‏1558 KB

  • IPS SSP module vs standalone 4200 series devices

    Looking at price to performance ratio it seems that the IPS SSP modules are the winner.
    The 4200 series devices however has hardware bypass which can ensure traffic flow is not interrupted even if the power to the IPS goes down. How likely is it that a malfunction of the IPS SSP affects the work of the ASA?
    We are looking at ASA5585X S20 with IPS SSP S20 or same ASA with IPS 4260.
    Any and all input in terms of pros and cons you are aware of will be appreciated.

    Yes, you can have the IDSM2 module in your CAT 6K. However, please check how much traffic will be traversing the IDSM2 module since you mention internal as well as traffic towards the internet. Please ensure that the performance of the internal traffic is not impacted. Also depends on whether you will be configuring the IPS in promiscuous or inline mode.
    Here is the datasheet for IDSM2:
    http://www.cisco.com/en/US/products/hw/modules/ps2706/products_data_sheet09186a00801e55dd.html
    You might even want to bundle a few IDSM2:
    http://www.cisco.com/en/US/prod/collateral/modules/ps2706/ps5058/product_data_sheet0900aecd804b91d7.html
    Hope that helps.

  • I am a beginner in Labview and need help with multi-device synchronization.

    I am using a VI I found in order to continuously acquire and write voltage.  The next phase is to somehow synchronize this with a linear platform and am wondering if there are any tutorials on how to do this out there, or if anyone could give just general advice.  I'm not necessarily asking for explicit details on the code but rather where I would be able to improve my skills in a way that would help with this project.  Thank you in advance.

    Hi riraheta,
    Are you using daq? Can you tell me more about this linear platform which you want to synchronize? What operation do you plan to synchronize?
    There are some examples online which has to do in synchronizing devices, depends on what you're planning to synchronize. The following are the few I have found.
    Links (Presuming that you're using DAQ devices):
    Synchronize Continuous Acquisition of Multiple Analog Devices (login required)
    https://decibel.ni.com/content/docs/DOC-12182
    Easily Synchronize Your Measurements in LabVIEW 2010
    http://www.ni.com/white-paper/11549/en/
    Application Design Patterns: Producer/Consumer
    http://www.ni.com/white-paper/3023/en/
    Application Design Patterns: Master/Slave
    http://www.ni.com/white-paper/3022/en/
    Timing and Synchronization Features of NI-DAQmx
    http://www.ni.com/white-paper/4322/en/
    Or you can search it from your NI Example Finder (Open LabVIEW >> Help >> Find Examples... >> Type in the keyword of your interests)
    Hope it helps
    Warmest regards,
    Lennard.C
    Learning new things everyday...

  • Can any one suggest me how to use drawPixels method for 40 series devices

    Hello!
    I am using drawPixels method of DirectGraphics class the code I have written is :-
    Image offscreen=DirectUtils.createImage(width,height,0x00000000);// width and heights are integer value
    public final int MODEL=DirectGraphics.TYPE_INT_8888_ARGB ;
    Graphics offgra = offscreen.getGraphics();
    DirectGraphics directgraphics = DirectUtils.getDirectGraphics(offgra);
    directgraphics.drawPixels(imgData,false,0,width,0,0,width,height,0,MODEL); // imgData is a int array(int imgData[]) which contains required pixels of image.
    The above code is working fine with NOKIA 60 series device but when i use it with NOKIA 40 series device it gives java.lang.IllegalArgumentException.
    same time if i use :-
    directgraphics.drawPixels(imgData,false,0,width,0,0,width,height,0,DirectGraphics .TYPE_USHORT_4444_ARGB ) ;
    // imgData is a short array(short imgData[]) which contains required pixels of image. i have used different formet here.
    it works fine with 40 series device,
    can any one suggest me how to use drawPixels method for 40 series devices with format
    DirectGraphics .TYPE_INT_8888_ARGB .

    If Remote wipe is activated it can't be undone. And Once the Wipe is done, the device can nö longer be tracked.
    Sorry.

  • Is the AT-MIO-16DE-10 an E series device?

    I'm trying to reinstall labview and I'm not sure which option to select. The choices are the recommended one, the one for all non-E series devices, and neither, and there's a note at the bottom for which devices should use neither.

    The AT-MIO-16DE-10 is an E Series device. Thus, I would pick the "recommended one" because that seems to apply to the E Series boards which are the regular boards produced by NI.
    If you still have troubles, let me know what version of LV you are trying to reinstall.
    L Aguila
    Applications Engineer
    National Instruments

  • SCB-68 Reference Label for M series devices

    What's the difference between the SCB-68 Reference Label M series devices connector 0 and connector 1? I'm installing a NI PCI-6221-M series Multifunction DAQ and the SCB-68 connector block, and I don't know how to make the physical connections. With the SCB-68 kit, I received the Reference Label for the E-series devices. In the NI site, there is info about the connector 0, but what is the connector 0 and connector 1?
    Thanks,
    ZeK

    Good question Zek. The M series family uses a smaller version of the 68-pin connector used on E series so that two connectors can be located on the same board. The second connector is available on certain M seriies boards in order to provide connectivity to additional channels. In the case of the 6221, there is only one connector.
    The 6221 is fully compatible with the SCB-68. The following link provides a revised version of the SCB-68 label adapted for M Series devices:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/61ed77983ad7cca386256f66008215f1/$FILE/SCB68%20M%20Series%20Connector%200.pdf
    For pinout specific to a particular M Series device, you can refer to the M series help available at either one of the following locations:
    http://digital.ni.com/manuals.nsf/websearch/9477D6DF1FE5A72986256FAB00633DE4?OpenDocument&node=132100_US
    http://digital.ni.com/manuals.nsf/websearch/3AE9D4533E03A6EF86256FE300809FE6 (HTML format)

  • Qualified Disks for px-Series Devices

    Note: The following information pertains only to px-Series network devices. If you have any other StorCenter network device, including ix-Series devices, this does not apply to you. 
    Before adding new hard drives to your StorCenter px-Series network device, please be sure to familiarize yourself with the following information. If you still have any additional questions about this topic, feel free to post them below. 
    Supported Drives: 
    For the current list of drive brands and models that have been tested with the StorCenter px devices and are supported for use, please visit https://iomega-na-en.custhelp.com/app/answers/detail/a_id/26012. Our approved hard drive list is still growing! Please check back with the list often or subscribe for updates by clicking on the "Notify Me" button on the above link. 
    Important: All disks within a single storage pool must meet the following requirements: 
    Same manufacturer 
    Same rotational speed 
    Same capacity
    Failure to meet these requirements may result in unpredictable device behavior and will not be supported by Iomega. If you need technical assistance, please be prepared to backup your data and remove any unsupported drives or configurations. 
    Pre-Installed Drives: 
    If you purchased your px device either fully or partially populated with drives, the device’s operating system resides partially on the drives. To replace all of the drives from the original configuration, follow the steps here: https://iomega-na-en.custhelp.com/app/answers/detail/a_id/27190

    What model px4 do you have? Version 4.0.8.23976 is the latest LifeLine firmware release for the px2-300d and px4-300d network storage devices while Version 4.1.4.24001 is the latest for the px4-400d.
    There is not any supported way to disable or restrict the services you are referring to. Debian is the operating system of the device so it would not be able to disable that unless by turning the device off.
    Apache is the web interface of our devices so if you disable Apache you will not be able to access the web management console and would have to do any configuration by SSH at that point. It might be able to disable Apache if you really wanted to, but the device may just restart the service after disabling it as it is a main function of the device.
    I'm not sure about OpenSSL and PHP, but if you are concerned about the Heartbleed bug, it only affects the px4-400d and px4-400r. Please see the following release from Lenovo: OpenSSL Heartbleed security vulnerability
    Have questions and need answers?
    Search the database for answers to FAQ's, software/driver downloads, tutorials, news, features and more!
    LenovoEMC Support & Downloads
    LenovoEMC North America Support Contact Page

  • Preventing false trigger in S series Device

    I have a PXI 6133 and currently have a task set up to begin with an analog edge trigger, however the line experiences a fair bit of noise due to solenoid power lines. I know that some other devices are able to use the minimum pulse width option in the daqmx triggering property nodes, but as far as i can tell S series devices don't. Does anyone know of a work around for this.

    Hi fchacon,
    One approach may be to reduce the environment-induced noise in your system. The Field Wiring and Noise Guide and these Five Tips could be a good starting point for you. 
    Another possible option is using an Analog Edge Reference Trigger that accounts for the noise in your system. This may allow you to set a trigger higher than the desired level, but incorporates the noise from our environment.
    Briana C.
    Applications Engineer
    National Instruments
    ni.com/support

  • Will ni-daq drivers for an E-series device work under WinXP?

    I now use them to program the device using Visual C++ under win 98.

    Hello
    NI-DAQ 6.9.3 does provide support for XP and 98, so you most certainly can use it in XP with an E-series device.
    Thanks
    Bilal Durrani
    NI
    Bilal Durrani
    NI

  • Maemo / MeeGo for N series devices?

    Hi,
    is there a chance Nokia offers an update of N series devices like the N97 to Maemo / MeeGo? I think this would offer a whole new world of software to these devices. I am pretty sure one or the other engineer has already played with this idea in his lab

    It's not possible and it won't happen ! I would think there is a good chance we may get a tiny overspill from Symbian^3, but that's the best you can hope for, the N97  has neither the memory or the processor speed to perform much better. More likely that memory management may be improved in later updates and would think there will be at least another 12 months support from Nokia, but that's about it. That said, it's only my opinion , but I wouldn't hold your breath !
    If I have helped at all, a click on the White Star is always appreciated :
    you can also help others by marking 'accept as solution' 

  • 2 Devices Synchronize

    Hello,
    i have the problem in Sychronize. i found an example in NI Tutorial.
    Who knows what is the Name of the Element in the black Circle?
    And where can i find it out in the library?
    Attachments:
    vi.jpg ‏76 KB

    that is "Get Terminal Name with Device Prefix VI" under Help»Find Examples, then click the first example under Hardware Input and Output» DAQmx» Synchronization» Multi Device.

  • ASR9K Series devices inventory is not working.

    Hi all.  Inventory in CiscoWorks with new devices ASR9K Series is not working. CW version: LMS3.2.1. Device: ASR-9006 AC Chassis. Credentials correct. Can any help me?
    Screenshot1: inventory request fail.
    Screenshot2: RME knows Cisco ASR9006 Router.

    Hello again and thx for advice,
    I've tried the solution from Cisco for this bug (CSCte95623 ), by manipulating delays values in cmdsvc.properties file and restarting cfgmngmt process. I've changed delay values in very different manner (delay after connect, tunesleepmills, login, e.t.c). Unfortunately this solution didn't help. A CDA work for  SSH fails all the time. Also i've manipulated
    ssh rate-limit and ssh session-limit values on device. It's a pity that opportunity to set on only sshv1 on device doesn't exist, so CW tries to connect only with sshv2 and there is no chance to check how it work with sshv1.
    I'm becoming a bit desperate about that issue. Any ideas?!
    There is some output from ssh debugs on device:
    debug ssh server
    RP/0/RSP1/CPU0:May 31 12:02:14.068 : SSHD_[1114]: Spawned new child process 5869901
    RP/0/RSP1/CPU0:May 31 12:02:14.149 : SSHD_[65869]: Client sockfd 3
    RP/0/RSP1/CPU0:May 31 12:02:14.151 : SSHD_[65869]: Setting IP_TOS value:192
    RP/0/RSP1/CPU0:May 31 12:02:14.152 : SSHD_[65869]: After setting socket options, sndbuf33792, rcvbuf - 33792
    RP/0/RSP1/CPU0:May 31 12:02:14.153 : SSHD_[65869]: Connection from ------------ port ---------
    RP/0/RSP1/CPU0:May 31 12:02:14.158 : SSHD_[65869]: (addrem_ssh_info_tuple) user:()
    RP/0/RSP1/CPU0:May 31 12:02:14.162 : SSHD_[65869]: Session id 0
    RP/0/RSP1/CPU0:May 31 12:02:14.162 : SSHD_[65869]: Exchanging versions
    RP/0/RSP1/CPU0:May 31 12:02:14.164 : SSHD_[65869]: %SECURITY-SSHD-6-INFO_GENERAL : Client ------ closes socket connection
    RP/0/RSP1/CPU0:May 31 12:02:14.164 : SSHD_[65869]: %SECURITY-SSHD-3-ERR_GENERAL : Failed in version exchange
    RP/0/RSP1/CPU0:May 31 12:02:14.164 : SSHD_[65869]: In cleanup code, pid:5869901, sig rcvd:0, state:1
    RP/0/RSP1/CPU0:May 31 12:02:14.166 : SSHD_[65869]: Cleanup sshd process 5869901, session id 0
    RP/0/RSP1/CPU0:May 31 12:02:14.171 : SSHD_[65869]: Closing connection to --------
    RP/0/RSP1/CPU0:May 31 12:02:14.171 : SSHD_[65869]: Sending Disconnect msg
    RP/0/RSP1/CPU0:May 31 12:02:14.172 : SSHD_[65869]: sshd_shm_acquire_lock: SHM Lock is NULL
    RP/0/RSP1/CPU0:May 31 12:02:14.172 : SSHD_[65869]: sshd_shm_unlock: SHM Lock is NULL
    RP/0/RSP1/CPU0:May 31 12:02:14.184 : SSHD_[1114]: Signal 18 received in handler: pid 5869901
    RP/0/RSP1/CPU0:May 31 12:02:14.207 : SSHD_[1114]: ratelimit_msecs:1000.000000, ratelimit_count:1
    RP/0/RSP1/CPU0:May 31 12:02:14.207 : SSHD_[1114]: elapsed:145.976000, ratelimit_msecs:1000.000000, count:1
    RP/0/RSP1/CPU0:May 31 12:02:14.207 : SSHD_[1114]: %SECURITY-SSHD-6-INFO_GENERAL : Incoming SSH session rate limit exceeded
    And CDA ssh work log from CW:
    Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1571,Iam inside ssh ....
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1573,Initial time_out : 0
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1583,Computed time_out : 30
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,1599,After computing time_out : 30
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,1637,inside getSshCmdSvc with timeout : 30000
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshProtocols,1743,Inside getsshprotocols with time out : 30000
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,1651,SSH2 is running
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler,verify,136,Got CmdSvc for SSH
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler,verify,141,Before Resetting the counters i.e before invoking counters for CredType :: SSH
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler,verify,151,After Resetting the counters i.e before invoking counters for CredType :: SSH
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler,verify,156,Getting Primary credentails to reset again to Primary only..
    [ Thu May 31  12:10:17 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler,verify,201,trying to connect for SSH
    [ Thu May 31  12:10:18 MSD 2012 ],ERROR,[Thread-1],com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler,verify,272,Got CmdSvcException com.cisco.nm.lib.cmdsvc.CmdSvcException: java.net.SocketException: Connection reset
        at com.cisco.nm.lib.cmdsvc.OpConnect.invoke(OpConnect.java:57)
        at com.cisco.nm.lib.cmdsvc.SessionContext.invoke(SessionContext.java:299)
        at com.cisco.nm.lib.cmdsvc.Engine.process(Engine.java:57)
        at com.cisco.nm.lib.cmdsvc.LocalProxy.process(LocalProxy.java:22)
        at com.cisco.nm.lib.cmdsvc.CmdSvc.connect(CmdSvc.java:190)
        at com.cisco.nm.lib.cmdsvc.CmdSvc.connect(CmdSvc.java:166)
        at com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler.verify(CmdSvc_CDACredTypeHandler.java:202)
        at com.cisco.nm.xms.xdi.pkgs.LibCda.GenericCdaHandler.checkSanity(GenericCdaHandler.java:37)
        at com.cisco.nm.rmeng.inventory.cda.job.DoCDAonDevice.checkSanity(CdaJobEngine.java:1565)
        at com.cisco.nm.rmeng.inventory.cda.job.DoCDAonDevice.run(CdaJobEngine.java:1429)
        at com.cisco.nm.rmeng.inventory.cda.job.CdaJobMonitor$ExecutorThread.run(CdaJobMonitor.java:244)
    [ Thu May 31  12:10:18 MSD 2012 ],ERROR,[Thread-1],com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler,verify,308,exception occured at the time of closing cmdsvccom.cisco.nm.lib.cmdsvc.CmdSvcException: java.net.SocketException: Connection reset
        at com.cisco.nm.lib.cmdsvc.OpConnect.invoke(OpConnect.java:57)
        at com.cisco.nm.lib.cmdsvc.SessionContext.invoke(SessionContext.java:299)
        at com.cisco.nm.lib.cmdsvc.Engine.process(Engine.java:57)
        at com.cisco.nm.lib.cmdsvc.LocalProxy.process(LocalProxy.java:22)
        at com.cisco.nm.lib.cmdsvc.CmdSvc.connect(CmdSvc.java:190)
        at com.cisco.nm.lib.cmdsvc.CmdSvc.connect(CmdSvc.java:166)
        at com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler.verify(CmdSvc_CDACredTypeHandler.java:202)
        at com.cisco.nm.xms.xdi.pkgs.LibCda.GenericCdaHandler.checkSanity(GenericCdaHandler.java:37)
        at com.cisco.nm.rmeng.inventory.cda.job.DoCDAonDevice.checkSanity(CdaJobEngine.java:1565)
        at com.cisco.nm.rmeng.inventory.cda.job.DoCDAonDevice.run(CdaJobEngine.java:1429)
        at com.cisco.nm.rmeng.inventory.cda.job.CdaJobMonitor$ExecutorThread.run(CdaJobMonitor.java:244)
    [ Thu May 31  12:10:18 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler,verify,310,Some exception not handled....
    [ Thu May 31  12:10:18 MSD 2012 ],INFO ,[Thread-1],com.cisco.nm.xms.xdi.pkgs.LibCda.CmdSvc_CDACredTypeHandler,verify,312,Not for enable test

  • Can Anyone help me with an AI Multi Device Synchronization in Continous mode ?

    Hi,
    I am new to this forum and relatively new to Measurement Studio.
    I have started using Measurement Studio for ANSI C a few month ago and it work perfectly but as the program grew so did the need for C++.
    In ANSI C everything was relatively simple but in C++ I need a working example to work on.
    I started by looking at the example in : C:\Program Files\National Instruments\MeasurementStudioVS2003\VCNET\Examples\DAQmx\Synchronization\Multi-Device\AIFiniteAcquisition
    but the problem is that this one is in finite mode and I need continuous.
    I have tried combining with another example for acquisitioning in continuous
    work but I cannot make it work.
    Please can anyone here help me !! Your help is much appreciated.
    Thank you.
    What shoud I do ?
    Julian
    Message Edited by The_Mind_Traveller on 09-25-2008 03:32 AM

    Hi Julian,
    How are you doing today and welcome to the forum. 
    I see that you are looking into one of the examples of finite acquisition for synchronized I/O across several channels or devices. Are you trying to do synchronization in your own application at the moment?
    If you meant you couldn't get the continuous acquisition working alone without thinking about the synchronization part at this stage, I would suggest you to start looking into the examples of continuous acquisition for single channel first, and then when you feel more comfortable with it, move on to integrate the synchronization part for multiple devices, which the code would be very similar to the finite acquisition example you've already found.
    Examples for single channel continuous acquisitions are located at,
     C:\Program Files\National Instruments\MeasurementStudioVS2003\VCNET\Examples\DAQmx\Analog In\Measure Voltage
    I will continue to look into your issues while I hope you can tell us more details about what exactly you are trying to do?
    Thanks, 
    Best regards,
    Mark M.
    Applications Engineer
    National Instruments UK & Ireland

  • Q: Re: Q: Acquiring data using two E series devices connected by RTSI and streaming data to disk

    << (My first posting)
    I use two E series PCI Cards, connected by RTSI. I'd like to stream the data
    from both cards to a binary file and to add a header to it.
    I also need to somehow read (plot) the stored data, this with another VI.
    The whole should be then integrated into an existing program, that used just
    one acquisition card.
    Till now I have tried to combine "Two E-series Shared ScanClk.vi" and "High
    Speed Data Logger.vi" into another VI, and I have tried to read the stored
    data with the "High Speed Data Reader.vi". The problem is that I fight with
    one error after another, what prevents me from going further.
    I use LabView 6.1, under Windows 2K.
    Has somebody by chance already done something similar and would agree to
    share with me their experience? TIA for any suggestion.
    Regards,
    Victor Manta
    >>
    "Ben" wrote in message
    news:[email protected]...
    > Hi Victor,
    >
    > I have done a lot of similar work.
    >
    > Exactly what did you try and what specific errors did you encounter?
    >
    > What you are trying is do-able provided the hardware you have suuports
    > it.
    >
    > Please post (both here and to the DAQ group)
    > the details of the hardware you are using,
    > versions of software being used,
    > Examples that you are using,
    > error codes that occured,
    > posibly post example code showing the problem.
    >
    > Ben
    Hi Ben,
    I use two PCI-MIO-16E-1 cards, connected by RTSI. I'd like to stream the
    data from both cards in real time to a binary file, after having added a
    header to it.
    For tests, on the channel 0 of each card is applied the same square wave,
    100 Hz.
    Yes, the hardware support RTSI. I use LabView 6.1.
    Till now I have:
    1. Combined the "Two E-series Shared ScanClk.vi" and the "High
    Speed Data Logger.vi" into a DAQ VI. To do this, I have "doubled" and
    adapted the "High Speed Data Logger.vi". For testing purposes the data are
    stored in two files, always the same ones (the old ones being overwritten
    after each acquisition).
    2. "Doubled" and adapted "High Speed Data Reader.vi" into another VI, for
    reading from both files, mentioned earlier.
    What already works:
    - The headers for both files are correctly stored (VI point 1.)
    - The acquired data from the first card (device 1) are correctly stored (VI
    point 1.)
    - The VI (point 2.) that reads both files and displays the results works
    What doesn't work:
    - The acquired data from the second card aren't stored at all (VI point 1.)
    - An error message says: "Error -10608 occurred at AI Buffer Read. Possible
    reason: NI-DAQ LV: No transfer is in progress for the specified resource."
    I think that I understand this message, but I don't know how to continue.
    The DAQ VI can be downloaded from (please click the link, then the link on
    that page; about 100K, zipped):
    http://www.swissheartnet.unibe.ch/labview.htm
    Thanks a lot in advance.
    Regards,
    Victor Manta
    PS. I don't know which DAQ group you mean.

    "Filipe A." wrote in message
    news:[email protected]...
    > Victor;
    >
    > You can definitely accomplish that task with the DAQ boards you have
    > and Labview.
    >
    > It would be good if you could be more specific as far as what type of
    > errors you are seeing and how you are integrating both VIs.
    >
    > Regards
    > Filipe A.
    > Applications Engineer
    > National Instruments
    Maybe Mr. Filipe A. could help me? Please see below, and TIA.
    Regards,
    Victor Manta
    "Victor Manta" wrote in message
    news:[email protected]...
    > << (My first posting)
    > I use two E series PCI Cards, connected by RTSI. I'd like to stream the
    data
    > from both cards to a binary file and to add a header to it.
    >
    > I also need to somehow read (plot) the stored data, this with another VI.
    >
    > The whole should be then integrated into an existing program, that used
    just
    > one acquisition card.
    >
    > Till now I have tried to combine "Two E-series Shared ScanClk.vi" and
    "High
    > Speed Data Logger.vi" into another VI, and I have tried to read the stored
    > data with the "High Speed Data Reader.vi". The problem is that I fight
    with
    > one error after another, what prevents me from going further.
    >
    > I use LabView 6.1, under Windows 2K.
    >
    > Has somebody by chance already done something similar and would agree to
    > share with me their experience? TIA for any suggestion.
    >
    > Regards,
    > Victor Manta
    > >>
    >
    > "Ben" wrote in message
    > news:[email protected]...
    > > Hi Victor,
    > >
    > > I have done a lot of similar work.
    > >
    > > Exactly what did you try and what specific errors did you encounter?
    > >
    > > What you are trying is do-able provided the hardware you have suuports
    > > it.
    > >
    > > Please post (both here and to the DAQ group)
    > > the details of the hardware you are using,
    > > versions of software being used,
    > > Examples that you are using,
    > > error codes that occured,
    > > posibly post example code showing the problem.
    > >
    > > Ben
    >
    > Hi Ben,
    >
    > I use two PCI-MIO-16E-1 cards, connected by RTSI. I'd like to stream the
    > data from both cards in real time to a binary file, after having added a
    > header to it.
    >
    > For tests, on the channel 0 of each card is applied the same square wave,
    > 100 Hz.
    >
    > Yes, the hardware support RTSI. I use LabView 6.1.
    >
    > Till now I have:
    >
    > 1. Combined the "Two E-series Shared ScanClk.vi" and the "High
    > Speed Data Logger.vi" into a DAQ VI. To do this, I have "doubled" and
    > adapted the "High Speed Data Logger.vi". For testing purposes the data are
    > stored in two files, always the same ones (the old ones being overwritten
    > after each acquisition).
    >
    > 2. "Doubled" and adapted "High Speed Data Reader.vi" into another VI, for
    > reading from both files, mentioned earlier.
    >
    > What already works:
    >
    > - The headers for both files are correctly stored (VI point 1.)
    > - The acquired data from the first card (device 1) are correctly stored
    (VI
    > point 1.)
    > - The VI (point 2.) that reads both files and displays the results works
    >
    > What doesn't work:
    >
    > - The acquired data from the second card aren't stored at all (VI point
    1.)
    > - An error message says: "Error -10608 occurred at AI Buffer Read.
    Possible
    > reason: NI-DAQ LV: No transfer is in progress for the specified resource."
    >
    > I think that I understand this message, but I don't know how to continue.
    >
    > The DAQ VI can be downloaded from (please click the link, then the link on
    > that page; about 100K, zipped):
    >
    > http://www.swissheartnet.unibe.ch/labview.htm
    >
    > Thanks a lot in advance.
    >
    > Regards,
    >
    > Victor Manta
    >
    > PS. I don't know which DAQ group you mean.

Maybe you are looking for