SPI bus timing, 1ms repeat acquisition

I plan to use digital I/O to create a SPI bus to read the output from a sensor.   I need to repeat a 2 byte read at a 1ms interval.  I was hoping to use a USB-8451 for this but I am unaware how I can control the 1ms repeat timing using LabVIEW.  If I only need 100ms of data perhaps I can use the NI845x SPI Write Read.vi to read an array of 200 bytes and then divide the array up into 100 2-byte pieces.  Depending on my sensor, I may need to deselect the Chip Select between the 100 reads to permit the DUT to update its data.
Alternatively, I have considered the USB-6221,6225,6229,6251,6259,6281 or 6289.  These seem to have better hardware timing features but may be limited to 2047 samples.  I assume that this means 256 bytes which could give me 128 samples from the sensor.
Thanks for any suggestions you can provide.

Hey Ryan, 
A picture of the behavior you are seeing would be helpful. The NI 9411 should only be reading 50 bits every 1 ms.  
It may not be possible to read 25 bits (do you mean 50 bits? 25 high 25 low) and push it to a queue without encountering an overflow error. If you take a look at the above code the digital input will receive 50 sample clocks every 1 ms. This is equivalent to acquiring 50 points every 1 ms which is an acquisition speed of 50 samples/1 ms=50 kHz. The read loop must keep up with the 50 kHz rate otherwise the buffer will overflow. In the above example I’ve set the read to pull 5000 samples (x) with the assumption that the loop will take less than or equal to .1 seconds (y). This yields a software acquisition speed of 50 kHz (5000 samples/100 ms). If the loop speed is faster than 100ms then the 10 seconds timeout on the DAQmx read will allow for the read to block so the FIFO may be filled.
The options available for question 2 are below. They may be used separately or in conjunction.
Move the DAQmx Read for the NI 9411 to its own independent while loop, set the DAQmx Read to acquire 50 samples, do not graph the data, and pass the data to a Queue for processing in a consumer loop. This will increase the loop speed which may allow you to keep up with the 50 kHz acquisition speed. This may not work because the loop speed will need to be 1 ms or less.
Increase the value of the Samples per Channel control that goes into the DAQmx Timing VI. This will increase the DAQmx Software Buffer size. This buys time until you receive an overflow error because the DAQmx Software Buffer is being filled faster than samples are removed.
Read in 5000 sample chunks (producer loop), push this to the queue, and perform the analysis in 50 bit chunks (consumer loop). The additional queue created should allow for the acquisition loop to keep up.
Regards,
Izzy O.
Product Support Engineer
ni.com/support

Similar Messages

  • Is the VXI bus timing on an 870 using VIC the same as I will get from my application program ?

    I have a 3rd party instrument that interferes with interrupts on modules in higher numbered slots. This instrument just passes the daisy chain along, but I suspect it is responding when it should not during an interrupt ack cycle. VIC interrupt ACK worked fine. Is the VXI bus timing fixed by the controller ? Is what I see on the bus with VIC what I will get using VISA calls?

    In VISA, you use VISA Enable Event to configure VISA with what type of event to watch for (such as interrupts). Then use VISA Wait on Event to actually wait for the interrupt to be generated and then acknowledged. Finally, you use VISA Disable Event before ending the VISA session.
    You will find tabs that correspond with these names in VISA Interactive Control. First use the Enable Event, select the event type and whether you want a queue or handler mechanism (I would suggest queue), and press Execute. Then go to the Wait on Event tab, set your timeout, and press Execute. As long as the interrupt occurs before the timeout period has elapsed, you will see the interrupt information returned. You can Execute Wait on Event numerous time
    s and it will return the next interrupt in queue. Before closing the VISA window, Execute Disable Event.

  • Precisely control timing of multiple acquisitions?

    What is the best way to acquire repetitive sets of data at precisely spaced time intervals? I'm running LabVIEW 6i on Windows NT.
    For example, I want to acquire say 500 scans at my top scan rate, process them, and then repeat this process every 10 msec. (I have to make configuration changes to my system during the dead time.) I need these data points taken at well controlled time intervals so I can make a meaningful waveform out of the data later.
    Here's what I've tried:
    1. Using a pulse train to trigger the AI Start function. When a triggered AI Start is included inside a While loop it uses all of the system resources watching for the trigger. No good. If I put in any kind of delay inside
    the loop, then NT can take away priority and not give it back until the trigger event has passed.
    2. Using a pulse train to gate the DAQ scan clock. Here I set the data acquisition for continuous acquire, but then turn the scan clock off during the dead time. So the system should only be taking data when the gate signal is high. My problem here is I don't know how to configure the AI Read function properly. Specifically, I don't know how to set the number of scans to read. If I calculate how many data points should be available and use that number, I'll often leave a data point or two in the buffer due to timing/rounding errors. If I set the number of points to read higher than the number I should have acquired, I get unpredictable behavior. Sometimes I read exactly the number of points I expect, sometimes 10 more, sometimes thousands more as it waits through multiple cycles to acquire more points.
    I'm sure there is a better way. Any suggestions?
    Thanks!
    Craig

    How about...
    If you have precise control of the DAQ scan clock, then reading n points would be the way to go. You can request 0 points to read and look at the scan backlog to detect when the next n points are available without getting locked into an AIRead call.
    Or...
    read data all the time and just throw out the rest of the data. Set your acquisition buffer for several seconds worth of data collection and keep track of read vs skip data.
    Stu

  • Timing for Data Acquisition Using Notifiers

    I'm trying to use notifiers to transfer data from an acquisition (master) loop to the slave loop. I want data to be transferred for analysis only when the VI is in a certain state - not in all states. That's why I'm preferring to use notifiers instead of queues (I want all data collected during the other states to be disregarded). I have attached a simplified version of what I'm trying.
    The master loop generates a data point every second. The slave loop is in a "delay" state for 5 seconds and then in "acquire" state for 3 seconds. Given this architecture I would expect no data for 5 seconds and then 3 data points to be plotted during "acquire" state because only one data point is generated per second. But for some reason I get 5 or 6 data points during every acquire cycle. I haven't figured out why I get 5-6 data points instead of 3. It probably has to do with the timing functions I'm using.  
    Thanks!
    -Arnie 
    Attachments:
    Notifier Data Transfer Template.vi ‏62 KB

    Here is an example of a race condition without the use of local or global variables.  What is happening is that the notifier is already queued up with a value even before the Elapsed Timer has even started.  So one extra value will be in the output array.  Also, depending on how the parallel loops perform (which goes first), there may be an extra value queued up before the Time Elapsed event could fire.  Typically, when I ran it, I got an array size of 6 at first, and then it went down to 5.  Clearly the architecture is not right for what you want to do.  Instead of depending on timers and parallel loop timing, you could receive all the values queued and just discard the ones you don't want.
    - tbob
    Inventor of the WORM Global

  • Timing of DAQmx Acquisition Vi and data write

    I am acquiring data from a DAQ rack, using a 6251 PCI card. after acquiring a data set, i write it to a binary file. afterwards, i do a small calculation on one channel value and apply a condition on this value. the outcome of which is connected to the while loop surrounding the acquisition. So i (1.)grab 100 points, (2.) write, calc. and cond., and (3.) start over again. I stuck millisecond timers in between steps 1, 2, and 3 to determine if i was incurring much delay. So, if i have no delay, and i'm sampling at 100 Hz, the differences between the millisecond timing values (stuck into an array) should be
    1000
    0
    0
    1000
    0
    0
    1000
    0
    0
    etc.
    This is usually the case. However, sometimes i get something like this
    900
    100
    0
    900
    100
    0
    or
    980
    20
    0
    980
    20
    0
    So if i measure a delay as a result of the writing/calculations/conditing, this time is subtracted from the acquisition time interval. I don't really understand this at all. Why a delay after the acquisition would speed up the acquisition, i have no idea. My only guess is that i start writing/calculating/conditioning before acquision has finished, but why would it do that? I've attached basically the setup. Any help would be great.
    Attachments:
    Concept.vi ‏61 KB

    ...what is the "hw?"
    That's short for "hardware." Specificially, in a buffered acquisition the data is sent into your memory buffer at regular times regulated by a hardware clock found in your data acq board. Your software interacts with this memory buffer via 'Read' calls.
    ...worry about delay?
    That'll depend on your app. As you've described it, you Read 1 second worth of data all at once then do some processing and storage. As long as you can do that processing and get back around the loop in less than one second, then the processing is not a bottleneck. The speed is being regulated by the amount of data you request and the time it takes to acquire it.
    If this behavior is sufficient for you, then no, you don't have to worry about the delay.
    Other apps may need to read smaller amounts of data and make decisions more quickly than once per second. Or they may need to instantly read the most recent data without waiting for any and then quickly make a decision. These sorts of apps might cause you to worry about the processing time.
    -Kevin P.

  • Timed out repeatedly

    I've been getting the 'the network connection timed out' message repeatedly for the last day.
    I recently downloaded and made firefox my default browser . At ~ the same time I upgraded itunes from 7.3 to 7.3.1.
    Is itunes down?
    Is it firefox?
    Is it firefox + 7.3.1
    Any other ideas?
    Thanks much,
    Ian

    The first thing to think about if you can't connect to the store after an ugrade is your firewall.
    Try briefly disabling your security software, which is not too dangerous is you connect to the internet via a router.
    If you can connect with the firewall disabled, then this tells you you need to configure your firewall to allow the new version of iTunes access to the internt.
    There are many different firewalls so I can't give exact instructions. If this is a problem post the name of your firewall and someone will probably be able to help. I have Norton 2005.

  • NICard 6031E Acquisition too slow when synchronisation with ATMEGA128

    Hello:
    I have an NI Card 6031E acquiring in HARDWARE SAMPLE CLOCK timing mode which means I supply a clock from an ATMEGA128 and the card acquires a value after each CLOCK high from another ASIC (Multiplexer chip).
    The clock comes from a microcontroller ATMEGA128.
    PROBLEM: I send an ' r ' character to the ATMEGA128 and subsequently I call the SAMPLE CLOCK timing read function in my user interface Visual C++ 6.0 on the PC. I am trying to synchronise PC with ATMEGA and NICARD data read, BUT I CANT DO IT.
    The thing is when the ' r ' char is received at the ATMEGA128 this one does what it has to do just ONCE and may be does it too fast for the NICARD to read the values supplied by the CLOCK from the ATMEGA128.
    The ATMEGA128 supplies a few digital binary signals (0 or 1) to the ASIC and the ASIC having received that particular sequence or digital waveform it sends the data (128 values one after each CLOCK high) to the NICARD.
    Therefore, each CLOCK high delivers a value to the NICARD from the ASIC. The problem is that it seems I loose the data on the NICARD because the sequence is done very fast at the ATMEGA128 and the NICARD takes 480us I think to perform an instruction. I tried placing the READ function before sending the r char but it blocks.
    I need SYNCHRONISATION between the NICARD acquiring values and the ATMEGA128 sending the clock and the ASIC sending data. Can I use other CHARS. I am lost! HELP! -)
    Thanks,
    Javi

    The ATMEGA128 code structure and CLOCK signal is as such:
    1 - FOR loop, therefore repeats itself always until you come out of the program execution.
    INSIDE FOR LOOP:
    2 - wait 1 microsecond, CLOCK HIGH, wait 1 micro second and CLOCK LOW
    3 - wait 26.4 microseconds, another FOR loop and inside it, (128 times CLOCK HIGH, wait 1 micro second and CLOCK LOW, and wait 26.4 micro seconds).
    4 - Once finished program goes back to 1
    So therefore the frequency of the CLOCK is of 37878.78 Hz or 37878.78 HIGH CLOCKS or samples per second which comes from 1/26.4microseconds.
    However, the initial first CLOCK on the FOR loop starting in section 1 is HIGH after 1 microsecond as described in section 2.
    The sampling frequency is set at 50000 samples per second on the NICARD, so therefore it is a sufficient setting for a 37878.78 Hz CLOCK.
    I acquire the data via an NICARD and my code sends an "r" character from the VISUAL C++ user interface to the ATMEGA128 and when the ATMEGA128 receives the "r" char it SENDS the CLOCK (and relevant waveform) to an ASIC. Then when the NICARD receives the CLOCK it acquires 1 sample on every CLOCK HIGH.
    I noticed a few days ago that when I start the CLOCK from the ATMEGA (same as sending an "r" char to the ATMEGA) on another Visual C++ application without the NICARD acquisition software functions and at the same time I start the Visual c++ application with the NICARD functions, I get almost the correct data.
    It seems that separating both Visual C++ applications PARTIALLY works but it does not make much sense.
    The difference between both is just having the NICARD functions present or not present, it seems, although it could be something else too.
    As you can see the synchronisation between the NICARD (HARDWARE TIMING CLOCK) data acquisition and the ATMEGA128 or ASIC sending data is performed via the sending of the "r" char to the ATMEGA128.
    Thanks.
    Javi.

  • NI8451 SPI data transfer speed and SCLK setup time adjustment

    I'm using NI USB-8451 SPI bus to do communication. I can not reach the speed of communication 4MHz (NI USB-8451 module advertises speeds up to 12MHz). Actrually the data transfer speed is much slower than 4/8 Mb/s. The 16k*16bit data cost around 800ms while it should be 128ms if the data transfer achieves 4Mhz speed. In the manual there is a SPI timing clock figure like this:
     In the 4Mhz communication case,  the t2 should be 0.25us. I wonder whether the low data transfer speed is due to t1,t3 and t4 since they occupy too much "dead time". If my guess is right, is there any method to reduce the t1,t3 or t4, espetially t3? I know that in the advanced API there is a way to add delay while I did not figure out how to reduce delay(t3).  If my guess is wrong, what is the exactly maximum data transfer speed NI8451 can support? (not the clock rate)
     Thanks for help.

    Hi everyone. Im using the SPI communication with 8451 and Im having the same situation., since the serial flash memory I need to program is big enough, t3 (SCLK Setup time) and other "dead time" which I think is the time when buffer on the 8451 needs to be re-filled those are killing my expectation on the final results. I can't see a way to decrease t3 (~10uSec) and in the same way Im seeing something like buffering up to 100~110 bytes then, a ~1.5mSec delay appears on the signal waveforms. Did somebody have good results trying to avoid this?
    Thank you.
    Javier
    Attachments:
    t3 - SCLK setup time.jpg ‏156 KB
    Data byte Transfer_109.jpg ‏137 KB

  • PCI-7833R RTSI Bus

    I'm in the process of integrating a second PCI-7833R into my project (a towable wideband echo repeater for submarine target emulation).
    The first board does the actual echo repeating (acquisition, trigger filtering, and detection, etc.)
    The second board will do optional signal generation and transmit equalization.
    Could I use the RTSI Bus as a data bus between the two boards? The project manager seems to treat them as general purpose IO.
    Where do I find the pinout and function description for the RTSI Bus Connector as this info is not in the PCI-7833R documentation.
    Thanks

    Hi,
    Yes, you can use the RTSI Line. However, you will need to connect the two 7833R board together through the RTSI connector using RTSI cable.
    The user manual for 78XX describes how to access and use the RTSI line on Page 36 (RTSI Trigger Bus). This knowledge base entry also provides the RTSI connector pinout for National Instruments PCI boards.
    Tunde

  • What is the pin map for chip select on LM3S8962 for "ARM SPI Create Configuration Reference.vi" ? (0 through n)

    Hello All,
    When the LM3S8962 is the master, what pin is used when chip
    select is the default (0), or another value ?
    Despite this question being asked a few ways in the forums,
    NI's "ARM SPI Create Configuration Reference.vi" documentation
    for chip select is unclear.
    TI's manual is no help for NI's implementation of chip select.
    NI's help for the above subvi seems not only too generic (perhaps
    written for the SDK ?),  but erroneous in that it reads:
    "chip select specifies the chip select line to assert during the
    SPI transfer. The chip select line must connect to the EEPROM
    on the
    microcontroller. Refer to the documentation for the SPI
    device for information
    about chip select lines."
    This is useless as the ARM microcontroller has no EEPROM and 
    the SPI slave device documentation only covers its own pins.
    The hope is to have more than one slave on the LM3S8962's single SPI bus,
    without chewing up a additional pin using elemental I/O like the splendid forum
    examples for ADC's and DAC's.  This would save diagram real estate compared
    with two sequence frames that are typically shown toggling a elemental I/O digital
    output before and after writing and/or reading from the slave.   It also would clarify
    what on chip resource trade offs there are for each chip select number chosen.
    (as most pins have multiple possible functions)
    Thanks in advance for any light on this.   Please don't post info on other processors
    to this thread as this taints future searches on this issue with this tier 1 target.
    Best,
    Davy

    Hi Davy,
    While doing research on this question, I was informed that you have been working with a colleague of mine, Joel, via email for this same question. So that we do not have multiple engineers working on the same issue, Joel will be your point of contact for this issue. I ask that when you have come to a resolution, that you post that resolution here so that other customers can reference this information.
    Thanks!
    Aaron P
    National Instruments
    Applications Engineer
    http://www.ni.com/support

  • SPI Converter Selection

    Hi All,
    We are developing an application in LabVIEW to test the DUT through the SPI interface.
    The DUT has the two SPI interface.
    One SPI interface is used for sending the request command from LabVIEW application (PC COM port or USB) to DUT (SPI BUS). By this time LabVIEW act as Master and DUT act as a Slave. For the request communication clock is generated from the Master. Slave use that clock for data transmission to DUT.
      Another SPI interface is used for sending the response command from DUT (SPI Bus) to LabVIEW application (PC COM or USB). By this time DUT act as Master and LabVIEW application act as a Slave. For the response communication clock is generated from the Master (Clock rate is 18 MHz). Slave use that clock for data reception.
    Here I need a converter for converting the COM or USB signals to SPI signals. Please let me know which converter is best suitable for this application.
    Thanks and Regards,
    Bharathi Thiruppathi
    Attachments:
    Test Setup.JPG ‏20 KB

    talk to sukesh once...
    Regards
    Guru (CLA)

  • 'systemctl --user status' returns 'Failed to get D-Bus connection'

    Basically I am trying to run a user session of systemd. Up to now, this worked without doing the additional parts from the systemd/User wiki-page. Now it returns 'Failed to get D-Bus connection: No such file or directory' or 'Failed to read server status: Input/output error' (the first one when I try it from the TTY, the second one from within xfce / urxvtc). Even after doing the wiki-page, it still returns the two error messages.
    My current 'systemctl status':
    ● SHODAN
    State: running
    Jobs: 0 queued
    Failed: 0 units
    Since: Fr 2014-04-25 18:33:55 CEST; 6min ago
    CGroup: /
    ├─1 /sbin/init
    ├─system.slice
    │ ├─rtkit-daemon.service
    │ │ └─466 /usr/lib/rtkit/rtkit-daemon
    │ ├─polkit.service
    │ │ └─376 /usr/lib/polkit-1/polkitd --no-debug
    │ ├─lightdm.service
    │ │ ├─279 /usr/bin/lightdm
    │ │ └─283 /usr/sbin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
    │ ├─systemd-logind.service
    │ │ └─276 /usr/lib/systemd/systemd-logind
    │ ├─dbus.service
    │ │ └─274 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    │ ├─wicd.service
    │ │ ├─273 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-daemon.py --no-daemon
    │ │ ├─289 /usr/bin/python2 -O /usr/share/wicd/daemon/monitor.py
    │ │ └─365 wpa_supplicant -B -i wlp4s0 -c /var/lib/wicd/configurations/00184db47218 -Dwext
    │ ├─systemd-udevd.service
    │ │ └─143 /usr/lib/systemd/systemd-udevd
    │ └─systemd-journald.service
    │ └─119 /usr/lib/systemd/systemd-journald
    └─user.slice
    └─user-1000.slice
    └─session-c2.scope
    ├─ 314 lightdm --session-child 13 20
    ├─ 352 /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc
    ├─ 359 dbus-launch --sh-syntax --exit-with-session
    ├─ 362 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
    ├─ 374 xfce4-session
    ├─ 384 /usr/lib/xfce4/xfconf/xfconfd
    ├─ 395 /usr/bin/gpg-agent --sh --daemon --enable-ssh-support --write-env-file /home/dustball/.cache/gpg-agent-info
    ├─ 411 xfwm4
    ├─ 419 xfce4-panel
    ├─ 421 Thunar --daemon
    ├─ 423 xfdesktop
    ├─ 425 urxvtd
    ├─ 448 python2 /usr/bin/quicktile -d
    ├─ 465 /usr/bin/pulseaudio --start --log-target=syslog
    ├─ 480 /usr/bin/python2 -O /usr/share/wicd/gtk/wicd-client.py --tray
    ├─ 481 grep -v Unhandled action type _OB_WM
    ├─ 482 xfsettingsd
    ├─ 483 xfce4-volumed
    ├─ 488 mpd
    ├─ 504 /usr/lib/pulse/gconf-helper
    ├─ 506 /usr/lib/GConf/gconfd-2
    ├─ 525 /usr/lib/xfce4/notifyd/xfce4-notifyd
    ├─ 529 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libsystray.so 6 12583017 systray Benachrichtigungsfl che Fl che, in der Symbole f r Benachrichtigungen erscheinen
    ├─ 531 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libactions.so 2 12583018 actions Aktionskn pfe Abmelden, sperren oder andere Systemaktionen
    ├─ 532 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libmixer.so 16 12583019 mixer Lautst rkeregler Lautst rke einstellen
    ├─ 548 xfce4-appfinder --collapsed
    ├─ 555 /usr/bin/python2 /usr/bin/sonata
    ├─1131 /usr/lib/chromium/chromium --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-print-preview
    ├─1132 liferea
    ├─1133 claws-mail
    ├─1134 kvirc -m
    ├─1135 /usr/lib32/skype/skype
    ├─1176 /usr/lib/chromium/chromium --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-print-preview
    ├─1177 /usr/lib/chromium/chrome-sandbox /usr/lib/chromium/chromium --type=zygote --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206
    ├─1178 /usr/lib/chromium/chromium --type=zygote --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206
    ├─1181 tmux new-session
    ├─1184 tmux new-session
    ├─1185 -zsh
    ├─1268 /usr/lib/at-spi2-core/at-spi-bus-launcher
    ├─1567 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
    ├─1588 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
    ├─1600 /usr/lib/chromium/nacl_helper
    ├─1755 /usr/lib/chromium/chromium --type=zygote --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206
    ├─1824 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.1.59959206
    ├─1847 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.2.164356213
    ├─1857 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.3.96609819
    ├─1871 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.4.134029888
    ├─1880 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.6.5115895
    ├─1886 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.7.176936345
    ├─1891 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.8.160718626
    ├─1896 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.9.165553601
    ├─1940 /usr/lib/dconf/dconf-service
    ├─2013 /usr/lib/chromium/chromium --type=gpu-process --channel=1131.12.1289180957 --supports-dual-gpus=false --gpu-driver-bug-workarounds=0,1,17,28,34 --disable-accelerated-video-decode --gpu-vendor-id=0x10de --gpu-device-id=0x0425 --gpu-driver-vendor=NVIDIA --gpu-driver-version=337.1
    ├─2025 /usr/lib/chromium/chromium --type=gpu-process --channel=1131.12.1289180957 --supports-dual-gpus=false --gpu-driver-bug-workarounds=0,1,17,28,34 --disable-accelerated-video-decode --gpu-vendor-id=0x10de --gpu-device-id=0x0425 --gpu-driver-vendor=NVIDIA --gpu-driver-version=337.1
    ├─2105 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.16.111786888
    ├─2121 bash /usr/bin/steam
    ├─2131 bash /home/dustball/.local/share/Steam/steam.sh
    ├─2132 tee /tmp/dumps/dustball_stdout.txt
    ├─2226 /home/dustball/.local/share/Steam/ubuntu12_32/steam
    ├─2415 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.18.32337900
    ├─2423 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.19.132593708
    ├─2432 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.20.6353944
    ├─2452 /usr/lib/chromium/chromium --type=renderer --lang=de --force-fieldtrials=Prerender/PrerenderControl/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_09/UMA-Uniformity-Trial-1-Percent/group_21/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_01/UMA-Uniformity-Trial-5-Percent/group_11/UMA-Uniformity-Trial-50-Percent/default/ --renderer-print-preview --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=13.0.0.206 --enable-deadline-scheduling --disable-accelerated-video-decode --channel=1131.22.126548679
    ├─2465 /usr/lib/chromium/chromium --type=ppapi --channel=1131.23.955061051 --ppapi-flash-args --lang=de
    └─2685 systemctl status

    I did the dbus-setup according to the systemd/User part in the wiki.
    $ cd $XDG_RUNTIME_DIR/systemd/ && ls -lah |grep private && pwd
    srwxr-xr-x 1 dustball dustball 0 25. Apr 22:13 private
    /run/user/1000/systemd
    Do I need to enable the dbus somehow else than via
    sudo systemctl --global enable dbus.socket

  • Can anyone help me with Labview/GPIB timing problems?

    I am trying to use a very simple VI (downloaded from the NI site) to control a Newport 1830C optical power meter.
    I have been spending most of my time trying to use the VI issue a command to read the current displayed power. When I run the VI normally, I get no response from the meter, and the VI simply terminates without any error message. (The "remote" indicator does light on the meter, though, so it seems to be receieving the command.)
    However, when I run the VI in the "highlight exectution" mode, everything seems to work just fine, and I receive a correct reading from the meter! Needles to say, this makes it really hard to debug the problem.
    My guess is that I have some kind of timing problem, and t
    he "highlight execution" feature fixes it by introducing delays. Is this correct? If so, how can I achieve the same thing by putting in delays by hand?
    thanks, Whitney White

    Whitney,
    I agree that this is very likely to be a timing issue. VIs run much slower in highlight execution mode, therefore your instrument may need more time to prepare the data you have requested. Try wiring a delay inline prior to the GPIB reads and/or writes, or try using Service Requests (SRQs) to give the instrument enough time to generate the data it needs to send back to the computer.
    Another possibility is that your instrument may not be IEEE 488 compliant. Some older instruments indicate that they are ready to receive data before they really are. Try changing the GPIB bus timing to the slowest setting (in the GPIB Configuration Utility). This only affects the time that the GPIB controller waits before valid data is on the bus and the DAV line i
    s asserted (a step in the GPIB handshaking that occurs each time a byte of information is sent to the device) so this may not be effective.
    Lastly, you may wish to try the instrument driver for your instrument. There is a contributed driver at this location: LabVIEW Traditional Instrument Driver: Newport Optical Power Meter 1830C. A 'contributed driver' means that someone outside of National Instruments wrote the driver and then submitted it for posting. This driver also contains a good example of adding a time out.
    Regards,
    Heather S.
    Applications Engineer
    National Instruments

  • Is bus branching supported?

    I found I could construct a bus tree by dragging bus segment endpoints into other existing buses.  For example, starting with two seperate buses arranged as an unconnected "T", the endpoint that forms the gap can be dragged into the neighboring bus to form a single bus.  The process of dragging the enpoint to form a single bus can be repeated to form a larger bus mesh.  The file can be saved and loaded without a problem.
    Is this feature supported?  Officially?  Unofficially?

    This still isn't the proper and intuative way to create busses. Nester I see your point regarding the after the bus entries are added dialog merge.......thats fine.
    The way it "should" work is that you should be able to T "JUNCTION" a bus just as you do with wire junctions or be able to ADD a junction point in the bus body and then allow connection to that junction. The merging is fine if things are already established but if your starting a micro design or multiplexed display from scratch, your mostly like just laying out parts and its a real PITA to try to get a "singular" bus running around the schematic. Ususally a bus will be run above or below a row of bus devices and the entries go to an intersecting bus that should T itself into the the bus running above and below the IC rows. The merge endpoint doesn't show a "junction" based on the attachement given here..........but at least it connects together "like" if there are no entry points.
    It still needs a major overhaul. I even sent pictures following Orcads model with is one of the most efficient ways to do junctions and its been ignored or "we'll get around to it"........this is ongoing since version 8 and hence why I have not been a very active v10 beta return.....I wish they would take our advise more seriously.......these are basic interface things that need attention.......the simulation stuff is secondary to functionality of basic circuit capture.....IMO.
    Best Regards,
    Chris Bertrand
    Signature: Looking for a footprint, component, model? Might be here > http://ni.kittmaster.com

  • My periodic tasks don't look so periodic on the bus monitor.

    My periodic tasks don't look so periodic on the bus monitor.  Is it possible the bus monitor is reporting incorrect rates or are my frames really not being sent very close to periodically?  Are there only certain multiples of a base rate than can be sent periodically?  The attachment shows my different rates.  I've written in the middle of the columns what they should be.  Some are fairly close, some are not.  Am I doing something wrong?  Thanks for any help/advice.
    Robert C. Mortensen
    Certified LabVIEW Architect
    Certified LabVIEW Embedded Systems Developer
    Endigit
    Attachments:
    CAN Bus Timing.PNG ‏44 KB

    Hi Chris,
    Thanks for responding.  I've attached an image of my LabVIEW code setting up and executing the periodic messages.  I'm doing a simple loopback to read what I'm sending out on the other port.  The code is executing without error; I was just wondering if it is normal for hardware-timed periodic messages to be so erratic.  I would have imagined that if the CAN transciever is sending out buffered data at intervals specified by the on-board clock the messages would appear more deterministically timed.
    I appreciate your efforts to keep these forums monitored.  I know these questions can be pretty random.
    Robert C. Mortensen
    Certified LabVIEW Architect
    Certified LabVIEW Embedded Systems Developer
    Endigit
    Attachments:
    Periodic CAN.PNG ‏16 KB

Maybe you are looking for

  • Why Can't I install Adobe Flash Player? Please Help!

    I have Windows 7 and my laptop is fairly new. I want to install Adobe Flash Player because when i go to Youtube it just shows a black screen for videos, Facebook doesn't load completely, when i go to google images, If i type in the most basic search

  • Run-time Error '432'  in WAD

    Hi Experts, While opening a web template in web application designer, I am getting following error, Run-time Error '432' : File name or class name not found during automated operation. If i press ok, exist from WAD. I have uninstalled the GUI and ins

  • How can i restore the files which are important to me which i suddenly delete the files in download?

    i nid to restore the file which i suddenly delete in download.. i was about to delete the files which are not important but i suddenly delete the files which are important... how can i restore it??

  • Oracle Grid general questions

    Our applications are running on their own application and database servers. We have a mix of hardware including Sun 4800, Sun 450, Sun 280, Sunfire 280, Dell Intel, etc. The OS on Sun boxes is Solaris 8 and on Dell Intel is Windows NT and 2000. To mi

  • Unable to see Member disk in ASM through DBCA

    Hi I am having standalone(NON-RAC) box with Linux AS3(Kernel Ver. 2.4.21.4) and oracle 10G installed on it. It is having one database as ORCL. Now i wants to configure ASM on it. For that I did the following activities. mkdir -p /u03 mkdir -p /u03/as