Software triggering

Dear All,
I'm using LabVIEW 8.0 and Daq-mx to program an application where I use
a finite retriggerable pulse train to time analog output of a waveform.
Currently, I'm using a hardware trigger pulse from another counter to
trigger the pulse train. Is there any way that I can change this to a
software trigger, such that, once I run the program, if I press a
button on the block diagram, it will set off the pulse train and I can
keep on repeating it without having to stop and restart the program?
Anyway help would be greatly appreciated.
Thanks in advance.
-Ashesh
Message Edited by Ashesh on 08-23-2006 01:41 AM

Hi Ashesh,
Thank you for contacting National Instrument's support!  That's an interesting question, and I think that you're very close to the solution already.  It sounds like you already have the foundation to your program, which will probably be very similar to our shipping example called "Gen Dig Pulse Train-Finite-Retriggerable."
Basically, our counters are only hardware triggered.  If you look at the source list for all potential trigger sources, you'll notice that they are all hardware related.  Unfortunately, we don't have any software triggers as such.
However, what you could do is use a software trigger to generate a digital high on one of your digital ports, and wire that over externally or internally (depending on your hardware, using the Connect Routes vi.  Check in your Measurement and Automation Explorer >> DAQmx Devices >> Device Routes to see what available options you have).  You would want to do something similar to the "Write Dig Chan" example program that is also shipped with LabVIEW. 
I hope that this points you in the right direction.  If you have any questions on implementing this solution, feel free to ask again and I'd be more than happy to help.  Thanks for choosing National Instruments!
Regards,
Daniel L.
Applications Engineer
National Instruments

Similar Messages

  • How to use and configure DAQmx software triggering in Labview 7.0

    Dear NI support staff,
    I want use to software triggers to start and stop acquiring an indefinite amount of analog samples (as opposed to a fixed number of N samples in most of your code examples). I don't know the correct way to configure the DAQmx property nodes and the DAQmx send software trigger VIs. In the property node VI it doesn't seem to have an entry for software trigger. So I think I am not on the right track. Would you please help me out? It would be great if you can show me an example. Thanks a lot!
    Regards,
    Bennett

    Hello Bennett,
    The example below demonstrates how to perform an analog software triggered acquisition in NI-DAQmx. The example allows the user to specify the triggering condition and the number of pre-trigger samples to acquire.
    Example Code - Triggering
    Let me know if you have further questions.
    Good luck and have a great day!
    Regards,
    Koninika
    Applications Engineer
    National Instruments

  • Repeated software triggering

    hi
    I want to repeatedly record data using a software trigger. I used the acquire N scans analog software trig.vi example and adjusted the input paramteres for my needs. For one aquicisition the vi works fine. Now i want to repeat the triggering and recording process because i want to do averaging. i tried to use a for-loop or a while loop as shown in attachement, but i get errors.
    does anybody know which adjustements i have to make to get the vi running ?
    Thanks Philipp

    and here is the attachement .....
    Attachments:
    trigger.jpg ‏302 KB

  • PackageKit (gnome-software) triggered reboot for updates?

    Hello!
    Some days ago I installed "gnome-software" out of curiosity. Is it possible that "PackageKit" in the background triggers some sort weird Red Hat behaviour, with an unrequested reboot for an autonomous update of systemd? This seems to be named "pk-offline-update".
    What happend:
    1. pacman -Syu # this morning, systemd updates included
    2. shutdown through GNOME UI this afternoon
    3. machine hangs for minutes (screen blank, no reaction on keyboard)
    4. turned off through power button
    5. turn on again through power button
    6. some short messages from systemd on tty1, can't read
    7. systemd turns off itself again
    8. turn on again through power button, everything back to normal
    /var/log/pacman.log
    [2015-04-24 09:38] [PACKAGEKIT] synchronizing package lists # this is gnome-software, okay
    [2015-04-24 09:38] [PACKAGEKIT] synchronizing package lists # this also
    [2015-04-24 09:39] [PACMAN] Running 'pacman -Syu' # this is me
    [2015-04-24 09:39] [PACMAN] synchronizing package lists
    [2015-04-24 09:39] [PACMAN] starting full system upgrade
    [2015-04-24 09:40] [ALPM] transaction started
    [2015-04-24 09:40] [ALPM] upgraded libsystemd (219-5 -> 219-6)
    [2015-04-24 09:40] [ALPM] upgraded systemd (219-5 -> 219-6)
    [2015-04-24 09:40] [ALPM] upgraded systemd-sysvcompat (219-5 -> 219-6)
    [2015-04-24 09:40] [ALPM] transaction completed
    [2015-04-24 16:37] [ALPM] transaction started # not me, I've told GNOME to shutdown the machine instead it hanged forever, turned it off with the power button
    [2015-04-24 16:37] [ALPM] reinstalled libsystemd (219-6)
    [2015-04-24 16:37] [PACKAGEKIT] reinstalled libsystemd (219-6)
    [2015-04-24 16:37] [ALPM] reinstalled systemd (219-6)
    [2015-04-24 16:37] [PACKAGEKIT] reinstalled systemd (219-6)
    [2015-04-24 16:37] [ALPM] reinstalled systemd-sysvcompat (219-6)
    [2015-04-24 16:37] [PACKAGEKIT] reinstalled systemd-sysvcompat (219-6)
    [2015-04-24 16:37] [ALPM] transaction completed
    [2015-04-24 16:41] [PACKAGEKIT] synchronizing package lists
    journalctl -r
    -- Reboot --
    Apr 24 16:37:07 ws-lnx-pew systemd-journal[152]: Journal stopped
    Apr 24 16:37:07 ws-lnx-pew systemd-shutdown[1]: Sending SIGTERM to remaining processes...
    Apr 24 16:37:07 ws-lnx-pew systemd[1]: Shutting down.
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: failed to change mode for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: shutting down
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: writing actual results
    Apr 24 16:37:07 ws-lnx-pew PackageKit[350]: update-packages transaction /1_daebeeca from uid 0 finished with success after 1395ms
    Apr 24 16:37:07 ws-lnx-pew PackageKit[350]: in /1_daebeeca for update-packages package systemd-sysvcompat;219-6;x86_64;installed was updating for uid 0
    Apr 24 16:37:07 ws-lnx-pew PackageKit[350]: in /1_daebeeca for update-packages package systemd;219-6;x86_64;installed was updating for uid 0
    Apr 24 16:37:07 ws-lnx-pew PackageKit[350]: in /1_daebeeca for update-packages package libsystemd;219-6;x86_64;installed was updating for uid 0
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: status finished
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: package finished systemd-sysvcompat-219-6.x86_64 (installed)
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: percentage 100%
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: package updating systemd-sysvcompat-219-6.x86_64 (installed)
    Apr 24 16:37:07 ws-lnx-pew pk-offline-update[339]: package finished systemd-219-6.x86_64 (installed)
    Apr 24 16:37:07 ws-lnx-pew systemd[1]: Unit type .busname is not supported on this system.
    Apr 24 16:37:07 ws-lnx-pew systemd[1]: Detected architecture 'x86-64'.
    Apr 24 16:37:07 ws-lnx-pew systemd[1]: systemd 219 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCO
    Apr 24 16:37:07 ws-lnx-pew systemd[1]: Reexecuting.
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 66%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 65%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 64%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 62%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 61%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 60%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 59%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 58%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 57%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 56%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 55%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 54%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 53%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 52%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 51%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 50%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 49%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 48%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 47%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 46%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 43%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 42%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 41%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 40%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 39%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 38%
    Apr 24 16:37:06 ws-lnx-pew dbus[346]: [system] Reloaded configuration
    Apr 24 16:37:06 ws-lnx-pew dbus[346]: [system] Reloaded configuration
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 37%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 36%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 35%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 34%
    Apr 24 16:37:06 ws-lnx-pew dbus[346]: [system] Reloaded configuration
    Apr 24 16:37:06 ws-lnx-pew dbus[346]: [system] Reloaded configuration
    Apr 24 16:37:06 ws-lnx-pew dbus[346]: [system] Reloaded configuration
    Apr 24 16:37:06 ws-lnx-pew dbus[346]: [system] Reloaded configuration
    Apr 24 16:37:06 ws-lnx-pew dbus[346]: [system] Reloaded configuration
    Apr 24 16:37:06 ws-lnx-pew dbus[346]: [system] Reloaded configuration
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: package updating systemd-219-6.x86_64 (installed)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: package finished libsystemd-219-6.x86_64 (installed)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 33%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 27%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 18%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 14%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 3%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 0%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: package updating libsystemd-219-6.x86_64 (installed)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: status update
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 100%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 88%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 44%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 0%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 100%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 88%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 44%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 0%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: status test-commit
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: status running
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 100%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 99%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 34%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 0%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: status setup
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 100%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 99%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 34%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 0%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 100%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 100%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 99%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 34%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 0%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 100%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 88%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to display message on splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 44%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: failed to set percentage for splash: Failed to execute child process "plymouth" (No such file or directory)
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: percentage 0%
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: status sig-check
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: status running
    Apr 24 16:37:06 ws-lnx-pew pk-offline-update[339]: status test-commit
    Apr 24 16:37:05 ws-lnx-pew pk-offline-update[339]: status dep-resolve
    Apr 24 16:37:05 ws-lnx-pew pk-offline-update[339]: status running
    Apr 24 16:37:05 ws-lnx-pew packagekitd[350]: (packagekitd:350): PackageKit-alpm-WARNING **: systemd-sysvcompat-219-6 is up to date -- reinstalling
    Apr 24 16:37:05 ws-lnx-pew packagekitd[350]: (packagekitd:350): PackageKit-alpm-WARNING **: systemd-219-6 is up to date -- reinstalling
    Apr 24 16:37:05 ws-lnx-pew packagekitd[350]: (packagekitd:350): PackageKit-alpm-WARNING **: libsystemd-219-6 is up to date -- reinstalling
    Apr 24 16:37:05 ws-lnx-pew pk-offline-update[339]: status setup
    Apr 24 16:37:05 ws-lnx-pew pk-offline-update[339]: status wait
    Apr 24 16:37:05 ws-lnx-pew PackageKit[350]: uid 0 obtained auth for org.freedesktop.packagekit.package-install-untrusted
    Apr 24 16:37:05 ws-lnx-pew PackageKit[350]: new update-packages transaction /1_daebeeca scheduled from uid 0
    This looks for me like "gnome-software" trigged this through "PackageKit". I don't really use "gnome-software", because I'm following the generic approach of Archlinux and do all administrative stuff through the terminal. This means, I use only the official programs from Archlinux, pacman, pacdiff and in my case sometimes VIM. I really don't want reboot my machine for updates, if it is not really my own decission and desire because it is technially required. Basically I just ask for conformation on this issue. If I'm right about "PackageKit" and "gnome-software" as responsible for this frightening* incident, I will remove gnome-software, at least untils is behaviour is switched off.
    Thanks
    Hoschi
    Problem solution:
    Windows? Reboot!
    GNU/Linux? Be root!
    * Sorry for that expression...but...Windows!!!
    Last edited by hoschi (2015-04-24 15:17:12)

    I noticed that when I shut down via GNOME with gnome-software installed and updates to install, there is a checkbox for installing updates in the shutdown dialog. If this is checked (which it is by default), the computer will reboot, install updates and only then shut down.
    You probably didn't uncheck this checkbox, or maybe use an extension which bypasses the shutdown dialog. Since your computer froze and was power-off, the installation step only occured after you manually powered it on again.
    Last edited by symen (2015-04-25 11:23:22)

  • Software triggered single Pulse Generation

    Hi,
    I have an AT-MIO-16E10 board and I am trying to generate multiple but
    finite digital pulses without having to reset, configure and rearm the
    counter for every pulse. This takes too much time for my application. I
    would like to configure just once the counter and gate it by any
    software method. I am using LabWindows/CVI.
    Does anybody know if it is possible to rearm the counter without having
    to reset and configure it previously?.
    Does anybody know how to generate a software trigger?
    Thanks
    Manolo

    Hi Manuel,
    Configure your counter for retriggerable pulse generation, and connect
    one of the digital lines to the counter gate. Toggle the digital line each
    time you want to generate a pulse. See GPCTR_Set_Application(),
    application = ND_REGRIG_PULSE_GNR in the NI-DAQ Function Reference
    Manual for details. Please feel free to email me if you need more help.
    Regards,
    Reed.
    Reed Blake
    Beta Technology
    Industrial and Scientific Computing
    Manuel Prieto Mateo wrote in message <[email protected]>...
    >Hi,
    >I have an AT-MIO-16E10 board and I am trying to generate multiple but
    >finite digital pulses without having to reset, configure and rearm the
    >counter for every pulse. This takes too much time for
    my application. I
    >would like to configure just once the counter and gate it by any
    >software method. I am using LabWindows/CVI.
    >Does anybody know if it is possible to rearm the counter without having
    >to reset and configure it previously?.
    >Does anybody know how to generate a software trigger?
    >
    >Thanks
    >
    >Manolo
    >

  • How can I access 6534 onboard timers for software triggering with LabView?

    I want to access the internal timers (with a VI?), so I can delay data output of the board (high precision timing, no system clock)?
    Thanks in advance!

    Sanchez,
    I am not sure that I totally understand your question. Do you want to replace the timing that the operating system provides LabVIEW with the timebase available on the NI 6534? If so, this is not going to be possible. If I have misunderstood your question, let me know.
    Spencer S.

  • Triggerring PXI-4110 to measure 1 current value while HSDIO PXI-6552 generating waveform

    Hi,
    Some question about PXI-4110 to measure current while PXI-6552 is generating the waveform. 
    1. Let say, I need to measure 3 points of current values, i.e. while PXI-6552 is generating sample-1000, 2000 and 3500. On the edge of sample 1000,2000 and 3500, the PXI-6552 will send a pulse via PFI line or via PXI backplane trigger line. My question is, is it possible to trigger PXI-4110 (hardware trigger or software trigger) to measure current values at these points ?
    2. Let say I need to measure the current on 0ms (start of waveform generation by PXI-6552) , 1ms, 2ms, 3ms, 4ms... and so on for 1000 points of measurement, code diagram as shown at the figure below. It is possible for the VI "niDCPower Measure Multiple" to measure exactly at 1ms, 2ms, 3ms .. ? How much time will have to spend to complete acquire 1 point of measurement by "niDCPower Measure Multiple" ?
    Thanks for viewing this post. Your advice on hardware used or software method is much appreciated. Thanks in advance.  
    Message Edited by engwei on 02-02-2009 04:24 AM
    Attachments:
    [email protected] ‏46 KB

    Hi engwei,
    1. Unfortunately, the 4110 does not support hardware triggering. Therefore you cannot implement direct triggering through the backplane or anything like that. However, there are a couple of possible workarounds you can try:
    a) Use software triggering: Say your 6552 is generating in one while loop, and your 4110 is to measure in another while loop. You can use a software syncrhonization method like notifiers to send a notification to your 4110 loop when your 6552 has generated the desired sample. This method, however, will not be very deterministic because the delay between the trigger and the response depends on your processor speed and load. Therefore, if you have other applications running in the background (like antivirus) it will increase the delay.
    b) Use hardware triggering on another device: If you have another device that supports hardware triggering (like maybe an M-series multifunction DAQ module), you can configure this device to be triggered by a signal from the 6552, perform a very quick task (like a very short finite acquisition) then immediately execute the DCPower VI to perform the measurement. The trigger can be configured to be re-triggerable for multiple usage. This will most likely have a smaller time delay then the first option, but there will still be a delay (the time it takes to perform the short finite acquisiton on the M-series). Please refer to the attached screenshot for an idea of how to implement this.
    2. To make your 4110 measure at specific time intervals, you can use one of the methods discussed above. As for how long it will take to acquire 1 measurement point, you may find this link helpful: http://zone.ni.com/devzone/cda/tut/p/id/7034
    This article is meant for the PXI-4130 but the 4110 has the same maximum sampling rate (3 kHz) and so the section discussing the speed should apply for both devices.
    Under the Software Measurement Rate section, it is stated that the default behavior of the VI is to take an average of 10 samples. This corresponds to a maximum sampling rate of 300 samples/second. However, if you configure it to not do averaging (take only 1 sample) then the maximum rate of 3000 samples/second can be achieved.
    It is also important to note that your program can only achieve this maximum sampling rate if your software loop takes less time to execute than the actual physical sampling. For example, if you want to sample at 3000 samples/second, that means that taking one sample takes 1/3000 seconds or 333 microseconds. If you software execution time is less than 333 microseconds, then you can achieve this maximum rate (because the speed is limited by the hardware, not the software). However, if your software takes more than 333 microseconds to execute, then the software loop time will define the maximum sampling rate you can get, which will be lower than 3000 samples/second.
    I hope this answers your question.
    Best regards,
    Vern Yew
    Applications Engineer, NI ASEAN
    Best regards,
    Vern Yew
    Applications Engineer
    Attachments:
    untitled.JPG ‏18 KB

  • Saving software trigger in project

    I created a project with Signal Express v3.0 where I use software trigger to start and stop acquisition. When I close signal express and then reopen the project the software triggers do not show up in the bar below the menus.
    Is there a way to keep the software triggers in the bar when we close the project and signal express?
    Thanks,
    Ben

    Duplicate post on Signal Express forum here
    Misha

  • Software trigger

    I created a project with Signal Express v3.0 where I use software trigger to start and stop acquisition. When I close signal express and then reopen the project the software triggers do not show up in the bar below the menus.
    Is there a way to keep the software triggers in the bar when we close the project and signal express?
    Thanks,
    Ben

    Hi John, if you look at the attached screenshots view1 shows the top part of the project when I open it. In view3 the software triggers are present. In view2 I display the start condition settings of the project. When I open the project I have to remove software trigger A and then add it back to have both trigger A and trigger B buttons appears at the top as in view3.
    Ben
    Attachments:
    view1.PNG ‏16 KB
    view2.PNG ‏32 KB
    view3.PNG ‏16 KB

  • Software trigger the PCI-5122

    hi
    I am going to program a board with PCI-6552 and in meantime in specific times capture just one sample of the anolog output of the board by PCI-5122.
    1) Can I use the digital output of one channel of PCI-6552 as trigger for PCI-5122 (to activate the fetching of PCI-5122) e.g. by connecting the output of PCI-6552 to the external trigger input of PCI-5122.
    2) Does it need to synchronize the two boards.
    2) Is there any example for software triggering the PCI-5122, and how long it takes from triggering to sampling the data.
    3) How I can capture just one sample in every triggering time and then wait for another trigger time.

    1) after programming the two output of the NI-6552 (DIO0 and DIO1) with the same pattern and connecting the DIO0 to Ch0 of PCI-5122 and DIO1 to external trigger of PCI-5122 and assigning the external trigger as the edge trigger source, the the signal is different from when the Ch0 is assigned as the trigger source. why are they different, also it does not accept two triggers sequentially. (Pic 1)
    2)I am using a loop for generating the data and a loop for aquisition, when I using two trigger in one cycle and select niscope repeat_time=4, the signal position for 8 aquisition should be the same but as you can see in figure 3 the first two pulse are correct but the other ones are different.
    Attachments:
    pic1.bmp ‏2305 KB
    pic2.bmp ‏2640 KB
    pic3.bmp ‏2305 KB

  • 5122 and continuous triggered acquisition

    I have a PCI-1522 and I want to do a continuous synchronous acquisition and have tried a number of things in NI-SCOPE without success. The signal I want to acquire is triggered (or to be more technically correct is synchronous with a second external signal) at 10 or 20 kHz and I want to sample at about 20 MS/s. Setting up the ext trigger is fairly straightforward if you put the initiate and fetch within a while loop. But then you have to loop on each trigger every 100 us (which the software is not fast enough to do even without the decimated processing I want to do) or acquire a larger chunk of data. This latter approach essentially initiates on one trigger pulse but acquires a large number (2M) of samples at 20 MS/s and therefore is subject to jitter if the samples acquired aren't exactly right. (I adjusted the sample size to correct within one sample and there is still persistent jitter so without triggering the accuracy required is less than one sample.) Bottom line is you aren't synchronous with either approach. With the fetch forever example, you move the initiate outside of the while loop which is great. But you have to use a software trigger in order to get it to work. All of the possible solutions essentially boil down to software triggering. I suffer either from jitter or drift.
    I thought about using the video ref triggering schemes but then I have to configure my signal to fit into the pre-defined video formats which may not be possible. I haven't thought too much about a DAQmx solution. Are there any examples or solutions of a hardware-synchronous, continuous acquisition in NI-SCOPE or DAQmx?

    Hi Dan,
    You might want to take a look at the niScope EX Multi Record Fetch More Than Available Memory.vi shipping example.  With this VI you can set up a multirecord acquisition and fetch records as they are being acquired.  This allows you to acquire more records than will fit in the onboard memory.  Currently, there are limitations in the driver which limit you to fetching about 2,000 to 3,000 records per second, so you will not be able to keep up with your 10 to 20 kHz trigger signal indefinitely.  However, we are currently working on fetching optimizations which should bring this number up to the 10 kHz range in the future.  We hope to release these optimizations in Q1 of 2007.
    I hope this helps.
    Regards,
    Sean Close

  • Software trigger example for NI 5911

    Where can i find the software trigger example for NI 5911,
    thanks

    Hi dreamhawk,
    There are some examples online that demonstrate software triggering with a High-Speed Digitizer such as the NI 5911. Because you didn't specify which programming language you're using, I'll assume you're using LabVIEW. I suggest you take a look at the example program "Software Triggering with NI-SCOPE and a High-Speed Digitizer" at
    http://sine.ni.com/apps/we/niepd_web_display.displ​ay_epd4?p_guid=B45EACE3E89156A4E034080020E74861&p_​node=175383&p_source=External.
    Regards,
    David Shatila
    Applications Engineer
    National Instruments

  • Secure boot Software Reset

    Hi All
    Is it posible in any way to allow a system reset when booted in secure boot mode?
    Our setup on Zynq 7020
    1) eFuse AES key set
    2) eFuse AES only set
    3) encrypted FSBL in QSPI flash
    4) Fully encrypted boot.bin including linux ramdisk loaded
    We need a method to reboot the system from linux once running, any attempt made results in a secure lockdown.
    What I would like to happen is basicaly a software triggered Power On Reset.
    Is this posible from within the Zynq?
    I haven't managed to find anything in the Technical Reference Manual
    Regards
    Alex
     

    I want to re-trigger the FSBL on a Zynq7020 after booting into a secure image using only software. Writing a 1 to register (PSS_RST_CTRL) results in a secure lockdown.
    My FSBL is:
    the_ROM_image:
      [aeskeyfile] aes.nky
      [encryption=aes, bootloader]FSBL.elf
    using the efuse AES key
    After booting the FSBL shows this:
    "User not allowed to do any system resets"
    This is from Xilinx's default FSBL
    Now once I have fully booted into linux, I want to reboot the device all the testing I have done results in secure lockdown. Now this may be the intended operation for a secure boot and it is imposible to do what I want without externaly triggering a Power On Reset.
    If anyone knows if this is possible please let me know.

  • One device aquires one triggers

    Here is my problem
    I have a NI-9234 using a NI USB-9162 sleeve. The NI-9234 does not support hardware triggering, and the software triggering does not meet my needs for timing. Is there a way to use my DAQCard 6062E to trigger in someway either the vi or the acquisition
    - there is always an easy way, but it is always the hardest to find

    Hello,
    I am assuming that you are using the example from the Example Finder titled Cont Acq&Graph Voltage - Analog Software Trigger.vi.  Please clarify if this is the example that you are unhappy about the samples relative to the trigger.  This type of software trigger is going to be the best solution of a trigger on the 9234.  If you believe that the examples is not grabbing all the post samples that you would like, please futher example the setup with how many pre and post samples are needed.
    I do understand that you have a 6062E to hardware trigger from, however routing this trigger in software is also going to have some limitations.  The code you have attached is going to have delay between when the trigger happens ... the 6062E task will have to finish the read of 100 samples and then the error status will trigger the 9234 task.  I also wanted to note that the code posted in missing a sub vi needed to run.  I look forward to hearing back from you.
    Samantha
    National Instruments
    Applications Engineer

  • Ni-DAQ single-point analog sample latency.

    I am maybe in my own little world here in wanting to do software-triggered analog sampling and wanting to do it fast. Having bought a PCI-6014 which is capable of 4 microsecond analog sampling I found a simple AI_Read took 95usec. I was somewhat disappointed. Much reading of FAQs and other's postings here didn't help. I posted my own question and got little help.
    Well, having spent days working out such problems as how to access hardware under windows I would just like to throw this to the NI world:
    Digital in/out: was 6 usec. now 0.9usec.
    Analog in: was 95usec. Now 19 if a channel/gain change is required. 6 usec if not.
    To the hardware developers - lets have a cheer. The register-level programming is a bit con
    voluted, but that comes with the territory when the triggering, etc, is so flexible.
    To the software developers - boo, hiss. Wake up, get your act together. So far as programming the card is concerned I did exactly as described in the "E-Series register-level programming manual". The no-change-to-gain-channel case just does the last, trigger step.
    Now, imagine what I could charge if I could make the latest nVidia or ATI video card go 10x faster. I suspect those guys know how to write drivers though.

    Hi Michael,
    There's no question that efficiencies can be exploited once we start using RLP. Configuring the hardware is definitely quicker using this approach. However, programming specific applications using RLP begins to be a headache once you leave the realm of the simple application.
    Using the NI-DAQ driver on the other hand gives me a consistent, intuitive interface over almost all of their hardware products. I am also able to pick up LabVIEW, look at some example code and have an application up and running in less than a couple hours without ever programming data acquisition before. NI-DAQ also has an abstraction layer which offers programming benefits but will invariably add some delay to function calls.
    It is also important to note that acquisition times are not lost because of the latency of the configuration calls. You will be able to acquire triggered and continuous data at hardware rates!! The only benefit that is lacking is if you want to start a software call to the card in 6us. But this seems to be a mute point since your software timing is OS dependent anyway. Why push a software call to be 6us when your are not sure when the OS will process your application's code.
    The only time having a quick configuration would be a benefit is if you are constantly reconfiguring in a software loop. But then your are still restrained by OS timing so you will never have true deterministic results unless you go to an RT system.
    The developers of the NI-DAQ driver have had to make many trade-offs when developing such a comprehensive and flexible driver and accommodating every scenario with every user is an impossibility. This particular instance happens to be one of them.
    I would like it to be known though that I have been successful, with the NI-DAQ 7.0 driver, at acquiring continuous pattern input with the PCI-6534 card at 50ns resolutions (20MHz). Obviously, the driver has its benefits!!
    Anyway, I appreciate the chance to discuss this type of situation.
    Ron
    Applications Engineer
    National Instruments

Maybe you are looking for

  • How do i delete an existing iTunes account

    i have 2 itunes account and i want to delete one of them, how do i do that? is there a number i can call?

  • Time Machine: Old Computer / New Computer

    I had been backing up my Mac Mini to an external drive using Time Machine for a couple of years. I just got a new iMac, connected the same drive to it, and am in the process of running a back up on it. Whne I open the external drive folder I see one

  • Receiving error 2324 help

    Help I am receiving error 2324 as I am trying to upgrade my I Tunes And now I can not log in?

  • Upgrading MacBookPro Leopard

    I have Leopard 10.5.8 on my MBP17. Using CS4 Premiere How far can I upgrade the Mac & upgrade the CS safely with stability? Snow Leopard? Lion? Mountain Lion? CS5? CS5.5? CS6? Primarily interested in Premiere. thnx

  • Strange results with Insert statement having select query

    Hi all, I am facing a strange issue with Insert statement based on a select query having multiple joins. DB- Oracle 10g Following is the layout of my query - Insert into Table X Select distinct Col1, Col2, Col3, Col4, Function(Col 5) from Table A, B