How to delay a PXI-5122 trigger before routed to string of PFI

Similar Questions

• How to delay and trigger output for redeclenchables DAQ

  I make redeclenchables data acquisition based on the technique described here and that my departure point couple year I used joint comes with LabVIEW example.

  What I realize now is also already done that I need to delay the recognized outbreak and output as a trigger for any other device signal.

  How to make a simple diagram:
  Trigger is recognized-> DAQ [which works perfect already more than a year]
  -> wait 100ms-> exit the trigger [to be added]

  Using Windows XP edition family, NI PCI 6110

  I thank you in advance to anyone interested

  
  

• While with PXI-5122 digitizer loop counter

  Hello world

  I am a beginner of products NOR. Currently I use the PXI-5122, 2014 Labview for the ultrasonic signals. I have a problem when you count the number of signals using an external trigger (by a function generator) source. When I trigger the digitizer under 50 Hz, the meter is working properly (a single trigger = a signal). With a frequency greater than 50 Hz of trigger, the meter is malfunctioning. For example, with the shutter to 50 Hz and 500 number of signals, the counter takes 10s to get data. But, with the trigger of 100 Hz and 500 number of signals, the acquisition time was always around 10 s.
  You can see the code in the file attachment.

  Please let me know if you have any suggestions or recommendations for my situation, I would appriciate that.

  Thanks in advance!
  Best regards
  You

  WorldALoneMe,

  Looking at your code, you're software re - trigger your device.  With your Setup, you configure the digitizer to hold a single record acquisition in your "A - Scan.vi".  This VI opens the resource OR-SCOPE, configure, captures, returns the data, then closes the resource OR-SCOPE.  It then does this for each unique A-Scan that you do and would be the reason that b Scan.vi takes so long.  It appears then that fewer than 50 Hz, this reset any software and reconfiguration and the acquisition can occur without missing a trigger, but more than that, your triggers occur faster it takes to do these things.

  What you need to do set up the digitizer to a multi-record acquisition.  This is done using the 'niSCope configure horizontal timing.vi' and wiring in a number higher than '1' in the entry "number of records".  "You can find an example of how to perform a multi-record acquisition if you open the Finder of example OR > material input and output > Modular Instruments > NOR-SCOPE > Getting Started > niScope EX Multi Record.vi.

  In this example, the digitizer is only once configured, and it returns all the documents requested at the same time.  For your application, each record would be a simple Scan of A, and then if you configure 500 files, your B-Scan would be 500 wide.  This time allows the material to rearm between triggers that is much faster to do it in software.

  For a verification of more complex example out (in the finder of the example) "niScope EX Multi record go get more available Memory.vi"

  Kind regards

  Nathan P.

• Trip trying to rearm with the pxi-5122 times

  Hi all!
  This is my first discussion in this forum so I'm not sure this is the right place to post, because I'm using LabView, but maybe it's a hardware problem.

  Then... I have a problem to calculate the tripping time rearm to pxi 5122.
  Compared to data sheets, I read that it should be about 3 us with the CDT to the large or 12 US if on.
  But I need a precise measurement of the time out after each record measured so I decided to find it by myself...
  With the help of an acquisition program that I have previous written in LabView, I started only acquisitions of 10000 records and each record is composed of 128 samples; as signal I've used waves square with different frequencies, 10 volts peak-to-peak (my trigger was set on the first channel of 5122 with 1 volt in value of edge).

  First acquisition: wave of 50 kHz. Theoretically, I s 0,2 need to capture 10000 records without losing all the square wave signals. Choose a time of acquisition for a single record of 15.3 us, I found that the time required is 0.199998 , very similar to the one expected.
  Then by choosing a time of acquisition for a single record of 15.4 us, I found approximately 0.4 s.
  I can guess that this latter one each tops of two waves will lost so I held twice the capture of 10000 records time.

  Because the wave is 20 us I calculated a timeout of 20-15, 3 = 4.7 us.
  It wasn't like the 3 described us for the 5122 but I was not impressed and I went with my essay.

  Second wave: 20 kHz. I need 0.5 s to capture 10000 records without losing the square wave signals.
  What I found was that in this case, choose us an acquisition time for one record of 39.6 required 0.5 s to capture all vertices, then with 39.7 us I held about 1 second, once again, twice by the time.
  The previous example, I calculated the dead time: 50-39, 6 is 10.4 us.

  Very strange... idle time I'm supposed to be the trigger for rearmament (and thus fixed) did not differ in 2 cases.
  Tried with other wavelengths, the values are always different.

  This also the frequency of the square wave of fixing and changing the number of samples per record.
  For example, with 128 samples per files as I told before, I needed a measurement time of 15.3 US to collect all the consecutive summits, while 64 samples I need 12.8 us and so forth.

  So it seems to be a dependency between the dead after a record time (the trigger reset? now I'm not sure if I can call it that) and the sampling frequency of the pxi 5122.
  But I don't know why, the acquisition of data behave in this way.

  Is this good? Rearm time should be set, shouldn't it?

  I know it took some time to read my problem but I tried to be more precise, I could.
  Thank you in advance.

  Giacomo

  Yes that's correct.  However, I do not think that its acceptable rate of the nearest synchronization that is chosen.  I really think he goes to rate lowest according to acceptable timetable.  So, if a synchronization rate is 2 and another is 5, and you want a 4.9uS rate, the synchronization will be 2, while 5 is the closest.  (Or maybe it's the other way around)  That's why you see the double period during the change of rates by just a fraction.

• Error-201427 on PXI-5122 since NI MAX system

  I need to check that the PXI-5122 is supported by NO-Scope 4.0.0 under WINdows 7 64-bit. If so, I guess I can get a damaged card. The system was running under the old computer / code / drivers last month.

  Scenario is this: I'm upgrading of already running code to a new computer and 32-bit 64-bit CVI CVI. After plowing, of code tweaks, PXI, 5122 digitizer shows through a new error in the code. I go back NI Max and I get this related error when I try to post.

  "The driver could not communicate with PXISlot2, generates the following message:

  Error-201427 to the autotest

  Possible reasons:

  The specified device is not supported in the API OR-DAQmx.

  Specified device PXISlot2.

  Seeing this, I have tried NOR updated, and nothing has been marked. I shut down the system and reseat the card. Then I checked the version of NOR-Scope (was 3.9.4) OR MAX I downloaded manually OR-Scope 4.0.0. Same mistake.

  The 5122 is in slot 2 and NI MAX identifies the card as "2: NOR-PXI-5122"PXISlot2"

  More information on the current system

  Dell Precision T3600

  Win7 64 bit Enterprise SP1

  Spincore NMR TIming Pulsebalster PCI card

  PCIe copper x 4 remote link to the chassis OR 1062 q

  In the NI 1062 q

  Slot 1: NI SMU-8370 remote control

  Slot 2: OR PXI-5122

  SLOT3: NOR SMU-5442

  Slot 4: reports of empty in fact NEITHER SMU-8262 linked to a NI PCIe-8263 (shows in Windows, normal visibility NI Max is unknown)

  Slot 5: OR PXI-6733

  Slot 6: OR PXI-6733

  Slot 7: vacuum

  Slot8: OR PXI-5421

  Measurement and Automation Explorer System Information (current after upgrade NI-Scope) is attached

  Before I track down a loan 5122, I wanted to see if there are known incompatibilities that come to mind.

  Thanks in advance.

  There is a material-200313 error on the map (and the first replacement) as revealed by an earlier version of NIMAX (another computer and PXI chassis). The information contained in the attached document can help improve diagnosis in the future (rather than the more highest credits of the error).

  With a third scanner system is running.

• When to compensate for and win on a PXI-5122 niScope change?

  In my application, I use the niScope VI Fetch (I16 2D) to extract a multi-record, multichannel on a PXI-5122 digitizer acquisition.  Trying to optimize my code, this has led me to this question.

  I am taking 32 successive acquisitions and adding (on average) all waveforms.  According to the notice in the scale and standardization of binary data, I first apply the parameter wfminfo.gain to data I16, sum which, then apply the offset.  MATLAB-like pseudocode for my Labview code, it is something like:

  sum = zeros (1,1000)
  
  offsetsum = 0
  
  for i = 01:32
  
      [wfminfo, samples_i16] is niscope_fetch_i16 (...);
  
      samples_float = wfminfo.gain. * float(samples_i16[0,:]);
  
      Sum = sum + samples_float
  
      offsetsum = offsetsum + wfminfo.offset
  
  end
  
  Sum = sum + ones (1,1000). * offsetsum

  So my question is whether it is prudent to assume that the wfminfo gain (and offset) settings remain constant for the duration of a session of acquisition (since time niScope Acquisition throw is called until the moment where the acquisition completed)?   The reference above on normalization coefficients indicates that these coefficients are a function of resolution and vertical calibration settings.  That would allow me to move the multiplication of gain outside the loop of the acquisition and perform arithmetic on integers.  It's a safe assumption?

  Hi Gregory,

  We tested this here, and you should be able to pull these gain and offset parameters before the while loop is entered and the arithmetic operation later outside of the loop.  To do this, you can place a niScope get Wfm Coefficients VI before the while loop, set it to obtain the Coefficients of standardization and route those elsewhere, because they will remain constant over the acquisition.

• PXI external trigger jitter

  Hi all

  I use a Board PXI-5422 generator of finished generation mode signals to generate an external trigger signal (PFI0) about every 5ms. There is a nominal 1.7µs delay of the input trigger for the start of the generation. That in itself isn't a problem (I can compensate for the delay), but there are up to 50ns jitter on this period, which is a problem. Does anyone know if there is anything I can do to minimize this jitter? (Incidentally, PFI1 exhibits the same behavior, but it is not a surprise)

  Thank you very much

  Hello GVR123,

  I had a glance at the manual for the PXI-5422 and I found the note for the ' delay of start CH 0 analog output Trigger "which is indicated as"65 sample clock periods + 110 ns. With this information, I calculated that

  1.7 - 0, 110 = 1.59

  and

  1.59/65=0.025 (bulk)

  that points to a clock of 40 MHz. So I guess that's what you use.

  25ns deviation (40 MHz) each side (50ns total), you see the expectation, as there is no way to ensure that the trigger falls exactly on a rising edge of the sample clock.

  I hope this helps.

  Kind regards

  Michael S.
  Technical sales engineer
  NEITHER UK & Ireland

• PXI Questions - trigger and save the Communication function

  I would like to use the VISA API for working with modules in my chassis SMU-1062 q. I have installed the following modules in the chassis:

  1 NI PXI-5102 (scope)

  2 NI PXI-5402 (fgen)

  Instruments based on the registry as PXI modules are new to me for example I only worked with instruments of message in office until now. I had a number of questions on how to work with these appliances with VISAS, let me start by two of the most pressing problems for me right now:

  1. I don't understand how material trigger works in a PXI chassis. For example, if I'm working with the PXI-5402 (fgen) and I want to make a hardware trigger on TTL0 that the PXI-5102 (scope) can listen, how to configure it? What I see in the NI-VISA support, the VI_ATTR_TRIG_ID attribute allows you to specify the trigger line of material (TTL0 - TTL7) for a device. Once this is done, I'm supposed to (apparently) use the function:

  viAssertTrigger

  with the value: VI_TRIG_PROT_RESERVE

  in order to 'book' in the line. It is clear to me as agglomerates that produces a trigger on TTL0. At this point, I guess if I wanted to the PXI-5102 to be triggered by the TTL0, then I put the VI_ATTR_TRIG_ID in TTL0 for this camera as well? In addition, what is the difference between the implementation of VI_ATTR_TRIG_ID in TTL0 for the device (INSTR resource) against the implementation of VI_ATTR_TRIG_ID to TTL0 to the chassis (substantive resource of BASKET). What happens when I use viAssertTrigger in each case?

  2. my other question concerns using the PXI modules using ONLY VISA orders (I rather not use NISCOPE and NIFGEN at the level of the API). I understand how to use ViPeekN (16.etc, N = 8) and ViPokeN for reading and writing to/from the registry of PXI Configuration. What I don't understand how to use functions such as ViMoveIn, ViMoveOut etc to run modules, for example, make the PXI-5402 generate a sine wave. In other words, where can I find an explanation of how to order the PXI modules and send data using the API of VISA. It seems that I need documentation that explains how to issue orders of these devices from the registry, which brings à la carte, at the place where to read data from the etc.

  Thank you

  I did some looking and unfortunately we do not have any support for programming level registry with our Modular Instruments.

• Satellite M300 - how do I back up the data before using the recovery disk

  Hello everyone,

  Today, I closed my laptop Toshiba Satellite M300.
  Just after a few seconds, it automatically in service and reported some "boot error".

  She also suggested I put on the recovery CD. When I put the CD, nothing happened.
  After awhile, I read the instructions in the CD cover that says that I have to hold the C button and it will start the recovery process.

  How the process goes, the system told me that all the files that I had in the computer would be removed.
  Is it possible how I could back up my documents before as I recover my Vista?

  I would be very grateful if someone could help me!

  Sincerely,

  Milan

  Hello

  If I understand correctly, you are not able to boot into the Windows operating system; According to the normal starting procedure or by using safe mode. Is this good?

  If Yes, then I don't see many options to get access to the files on the HARD drive.
  What you could try is to remove the HARD drive and use an external USB 2.5 enclosure to connect the HARD drive on another computer.
  Then you could test whether it is possible to access the HARD disk and save the data.

  The Toshiba Recovery disk does not any option that allows you to save the data, the drive formats the HARD drive and erases all partitions.

• Pulse output PXI - 5122 PFI

  PXI5122

  It is not very clear if I can do this, but it is

  possible to arm the PXI5122 (pending a

  external trigger) and a pulse output on

  either PFI lines?

  The PFI 5122 trigger material ext and

  the 5122 will read the result.

  I try to use the LOAN to START at EVENT

  Which States 'generate a pulse when the digitizer is. "

  initiated and ready to start the acquisition to start sampling '

  TIA.

  Hello

  Yes, you can use the niScope export Signal.vi to produce a digital on one of your lines PFI pulse when a certain condition is met.  From your post, it seems that you may already use this VI.  I have attached a screenshot of the Signal VI export and included context-sensitive help and detailed about what parameters to signal help is available.

• PXI-5122 and PXI-6259 read 2 channels simultaneously

  There is a single PXI-5122 digitizer card and a PXI-6259 DAQ card in our PXI system, we use Labview and TestStand (model Batch) to test the multiplication Board simultaneously, sometimes up to 8 boards are tested. We have some problems, such as the results of the tests is not reliable and sometimes blocking of Labview. Everything works fine when test single board. Thus, we feel that multiply causing this problem of acquisition of string data. It's great, if someone has the same problem and we can share the knowledge. My question is as follows:

  1. If two channels have been configured, read the two channel simultaneous cause blocking of the system or data damaged?

  "lu niScope WDT.vi" is reentrant, we can use two Subvi to call the "niScope Read WDT.vi' access the two channels simultaneously.

  2. If we set up a channel in another channel is reading the data, this situation will cause the search system or corrupt data.

  Concerning

  Samuel

  Hi Samuel,.

  You shouldn't have any difficulty to read several channels on your 5122 or between your 5122 and your 6259. You receive an error message when your test is blocked? What happens when your test is not reliable? Are you incorrect data and if so what is the data vs expected data acquired? You should be able to set both your channels in a single task, which would be using a read niScope WDT.vi to be used by the device. You are working from example or have you developed your own code? What version of the driver NOR Scope and NI-DAQmx driver do you use? You can find the driver version number in the measurement and Automation Explorer under the software section.

  What kind of test are you running? Your PXI chassis is controlled by a computer or by an on-board controller? Evolution of the rate of acquisition has an effect on your program?

• How can I stop printing on HP8720 before it expires?

  How can I stop printing on hp8720 before it expires?

  How can I stop printing on hp8720 before it expires?

  Simply cancel the print queue item.

  You don't say what version of Windows you are using. It is the documentation for Windows XP well: -.

  

• is there a vi for inputs/outputs using AWG (PXI-5421) and DIG (PXI-5122)?

  Hi, I'm looking for a vi that applies to an input through the AWG (PXI-5421) signal and measures the output through the SEARCH (PXI-5122). In particular, I'm trying to apply an entry by a multiplexer, then close this channel of the multiplexer through which the entry came and then measure the output using the SEARCH signal.

  Any help will be greatly appreciated.

  Thank you.

  Hello Deepjunior,

  I understand that you wanted to find an application that will be output on an AWG device and acquire a table digitizer at the same time. While there are many methods to achieve this, the easiest starting point would be to just take a simple example of niFgen and a simple example of niScope and run them together or combine them. According to exactly what your application requires, you may need to implement additional features, but it is a good starting point.

  In particular, you can find an example of this from the example of area developer program: OR-TCLK synchronize AWG and digitizer high speed. Basically, this example combines niFgen and niScope examples and using the API OR-TCLK to synchronize devices. I recommend watching the program and trying to start from there. Hope this helps,

• Updated Photoshop CC and now it crashes.  How should I take this back to before the update?

  I spent 3 hours this afternoon trying to get help from the cat but nothing is fixed.  I have photoshop, lightroom, and bridge.  Updates to Lightroom and bridge agree. How can I reinstall the CC PS before the update?  My Macbook Pro is not able to manage it, maybe... being older video card.  I have a backup on my external hard drive, but it does not work correctly if I'm well obviously not doing it correctly. I'm not all that technical, but I can follow the exact instructions.

  My Office CC is not any 'previous Versions' of applications so I can't take it back to 2014 version.

  Please can someone help get this sorted out?  I would really appreciate it.

  Relocation of can be worth a try, Yes...

• TRIGGER BEFORE INSERT OR UPDATE OR DELETE

  I want to create a single trigger before each insert or update or delete, a record gets copied into the AUDIT table. works very well on the insertion and to day but you have problem clear.

  Can you please help me debug this error. The problem of mutation.

  create or replace

  BIU_FS_Test_T RELAXATION

  BEFORE INSERT OR UPDATE OR DELETE

  ON FS_Test

  REFERRING AGAIN AS NINE OLD AND OLD

  FOR EACH LINE

  DECLARE

  number of voffender_history_id;

  Start

  IF the INSERTION

  SELECT FS_Test_history_seq. nextval in the double voffender_history_id;

  INSERT INTO FS_Test_history (OFFENDER_HISTORY_ID,

  OFFENDER_ID, FIRST_NAME, MIDDLE_NAME, LAST_NAME.

  SX, SKIN_TONE, HEIGHT, WEIGHT, RACE, EYE_COLOR,

  HAIR_COLOR, BLOOD_TYPE, VARIOUS, DATE_OF_BIRTH.

  PLACE_OF_BIRTH, TRANSACTION)

  VALUES (voffender_history_id,

  : new. OFFENDER_ID,: new. First name: new. MIDDLE_NAME,: new. LAST_NAME,

  : new. RACE: new. SX,: new. SKIN_TONE,: new. HEIGHT: new. WEIGHT: new. EYE_COLOR,

  : new. HAIR_COLOR,: new. BLOOD_TYPE,: new. VARIOUS: new. DATE_OF_BIRTH,

  :new. PLACE_OF_BIRTH,

  "INSERT");

  ELSIF UPDATE

  et (

  NVL (:OLD. First name, 'x') <> nvl():NEW. First name, 'x') or

  NVL (:OLD. MIDDLE_NAME, 'x') <> nvl():NEW. MIDDLE_NAME, 'x') or

  NVL (:OLD. Last_name, 'x') <> nvl():NEW. Last_name, 'x') or

  NVL (:OLD. RACE 0) <> nvl():NEW. RACE 0) or

  NVL (:OLD. SX 0) nvl(:NEW <>.) SX 0) or

  NVL (:OLD. SKIN_TONE 0) <> nvl():NEW. SKIN_TONE 0) or

  NVL (:OLD. HEIGHT 0) <> nvl():NEW. HEIGHT 0) or

  NVL (:OLD. WEIGHT 0) <> nvl():NEW. WEIGHT 0) or

  NVL (:OLD. EYE_COLOR 0) <> nvl():NEW. EYE_COLOR 0) or

  NVL (:OLD. HAIR_COLOR 0) <> nvl():NEW. HAIR_COLOR 0) or

  NVL (:OLD. BLOOD_TYPE 0) <> nvl():NEW. BLOOD_TYPE 0) or

  NVL (:OLD. VARIOUS, ' x') <> nvl():NEW. VARIOUS, ' x') or

  NVL (:OLD. DATE_OF_BIRTH, January 1, 1900 ") <> nvl():NEW. " DATE_OF_BIRTH, January 1, 1900 ") or"

  NVL (:OLD. PLACE_OF_BIRTH 0) <> nvl():NEW. PLACE_OF_BIRTH 0)

  )

  THEN

  SELECT FS_Test_history_seq. nextval in the double voffender_history_id;

  INSERT INTO FS_Test_history (OFFENDER_HISTORY_ID,

  OFFENDER_ID, FIRST_NAME, MIDDLE_NAME, LAST_NAME.

  SX, SKIN_TONE, HEIGHT, WEIGHT, RACE, EYE_COLOR,

  HAIR_COLOR, BLOOD_TYPE, VARIOUS, DATE_OF_BIRTH.

  PLACE_OF_BIRTH, TRANSACTION)

  VALUES (voffender_history_id,

  : new. OFFENDER_ID,: new. First name: new. MIDDLE_NAME,: new. LAST_NAME,

  : new. RACE: new. SX,: new. SKIN_TONE,: new. HEIGHT: new. WEIGHT: new. EYE_COLOR,

  : new. HAIR_COLOR,: new. BLOOD_TYPE,: new. VARIOUS: new. DATE_OF_BIRTH,

  :new. PLACE_OF_BIRTH, "UPDATE");

  ELSIF DELETION THEN

  SELECT FS_Test_history_seq. nextval in the double voffender_history_id;

  SELECT FS_Test_history_seq. nextval in the double voffender_history_id;

  INSERT INTO FS_Test_history (OFFENDER_HISTORY_ID,

  OFFENDER_ID, FIRST_NAME, MIDDLE_NAME, LAST_NAME.

  SX, SKIN_TONE, HEIGHT, WEIGHT, RACE, EYE_COLOR,

  HAIR_COLOR, BLOOD_TYPE, VARIOUS, DATE_OF_BIRTH.

  PLACE_OF_BIRTH, TRANSACTION)

  VALUES (voffender_history_id,

  : new. OFFENDER_ID,: new. First name: new. MIDDLE_NAME,: new. LAST_NAME,

  : new. RACE: new. SX,: new. SKIN_TONE,: new. HEIGHT: new. WEIGHT: new. EYE_COLOR,

  : new. HAIR_COLOR,: new. BLOOD_TYPE,: new. VARIOUS: new. DATE_OF_BIRTH,

  :new. PLACE_OF_BIRTH, 'CLEAR');

  END IF;

  end;

  Error I get

  Error from the 1 in the command line:

  Remove from the fs_test where PK = 41476

  Error report:

  SQL error: ORA-04091: table get OUT. SOR_O_HISTORY is changing, function of triggering/can not see

  ORA-06512: at «GET. » BIU_FS_TEST_T', line 111

  ORA-04088: error during execution of trigger ' EB. BIU_FS_TEST_T'

  04091 00000 - «table %s. » "%s is changing, function of triggering/can not see.

  * Cause: A trigger (or plsql user-defined function that is referenced in)

  ( this statement) attempted to watch (or modify) a table that has been

  in the middle to be modified by the statement that shot.

  * Action: Rewrite the trigger (or function) so it does not read this table.

  PS 11g r2

  Thank you.

  n_shah18-

  Is there a parent-child relationship between the tables involved in the triggering event? Is there a foreign key used above the child table that references the parent table?

  If you have a parent-child relationship and a trigger on the parent table must be running some DML on the child table, and, if the child table as a foreign key (FK) back to the parent table, any DML on the child table will cause a recursive SQL statement to check the constraint. Indirectly, this will cause an exception table mutation.

  So watch the dependencies on SOR_O_HISTORY / FS_TEST_HISTORY/all other related table. A FOREIGN KEY can make it to mutate (no pun intended).

  Hope this will help you find the root cause.