Generating waves in Sin with NOR-6733

Similar Questions

• generate the signal f = 50 Hz with NOR-9264

  Hello. I am Sorin.

  I need to generate a sinusoidal waveform with f = 50 Hz, U is 3Vrms. I have a C, OR-9264 module. Is it good? Or can it only generates SCR?

  I don't have C modules: I for RTD, V, mA, universal and AO for V and mA.

  What can I use?

  Thank you.

  It DOES not say that it displays up to 25 kech. / s (25000 samples per second). It's more than enough for 50 hz.

• How to calibrate the PCI-6110 with NOR-DAQmx

  Hello

  I am a new user of the PCI-6110 Council tries to run the calibration using LabVIEW procedure. I look at the document "Calibration" on the page of the manuals for the Board of Directors,

  http://sine.NI.com/NIPs/nisearchservlet?nistype=psrelcon&NID=11888&lang=us&q=FQL: 28locale % 3Aen % 29 + AND + % 28phwebnt % 3 A 1081 + OR + phwebnt % 3 A 7075% 29 + AND + 28nicontenttype % 3Aproductmanual % 29 + AND + % 28docstatus % 3Acurrent % 29% 20RANK % 20nilangs: en & title = NOR + PCI-6110 + manual

  One of the first steps in the document is to call the AI_Configure command to set the input mode, beach, etc. I'm using LabVIEW 8.5 with the NOR-DAQmx software, and I can not find the command (which, in LabVIEW, seems to be "AI Config.vi") anywhere. The calibration paper was written in 2003, and I gather from Google searches (please, correct me if wrong) that this command is actually a part of NOR-DAQ traditional, who was replaced by driver OR DAQmx.

  My question is this: what is the equivalent to AI_Configure command in the latest software? Is it perhaps a subsequent document describing how to calibrate using NOR-DAQmx?

  Thanks much for any help.

  Tom McLaughlin

  Hi Tom,

  The calibration Procedure series B, E, M, S, which is also linked from this page, describes how to calibrate the PCI-6110 with NOR-DAQmx.

  Brad

• Generate a binary sequence with the NI USB-6008

  Hi all

  I'm new to LabView and I am trying to generate a binary sequence with a box NI USB-6008. The sequence, I'm currently generate is a counter of 5 bits, i.e. 00000 00001 00010, 00011... 11110, 11111 placing each bit in a different digital IO of the of the 6008 NOR, so that I can use the County as the bits of selection in a decoder/demux.

  I managed to simulate the binary sequence and produce a graphical interface, but I have not found how to generate the sequence of bits with the NI 6008.

  Totally, I'd appreciate any help you could provide. Thank you very much.

  Hi JosephM,

  Good Afternooon and I hope your well today.

  I just tested the code on a 6008 and also released the above code is very complex - I was for some reason any fixed on using Boolean tables.

  Please see the attached code, in LabVIEW 8.6.

  Mind you, I have configured the task as a channel for all lines. i.e. digital single I spent, is the task value should apply to all channels selected in the entry. So if you select only port0/Dev8/$line0 for example, the DAQmx driver will examine the LSB of the digital and work so $line0 must be true from the false. It will NOT update all other channels. So when I select line0:4 - it will update the first 5 lines (bits) in digital. As the code generates a number from 0-32 he emotional generates 00000 to 11111.

  

  I hope this finds you well and sorry for the first post!

• Support for alarms diagnosis field according to FF - 912 with NOR-FBUS Configurator 3.2.3

  I tried to control the utility alarm monitor and diagnosis field according to FF-912 alarms since a FF camera H1 with NOR-FBUS Configurator 3.2.3.

  Alarms standard block for example in the case of a change of parameter are monitored in the alarm monitor.

  Field diagnosis according to FF - 912 alarms are not controlled.

  Are field alarms diagnosis according to FF - 912 took supported by the NOR-FBUS 3.2.3 Configurator. or something special to do to activate the analysis.

  If not, what tools or host systems are available for monitoring these alarms?

  Alarm in the software OR-FBUS monitor doesn't have a field of diagnostics alarms. You can try to use NOR-FBUS C API nifWaitAlert2 to monitor this alarm. We will find the detailed description of the API OR FBUS Hardware and Software User Manual Chapter 6.

• Encoder interfaced with NOR-9401

  I bought a coder who has open collector and resistance to pull-up 3.3 kohm (TTL) logic output.

  The encoder comes with four sons: power + 5V, GND, channel A and channel B. channel A and B are logic output.

  Channel A and B are connected to the OID of NOR-9401 which is mounted on the cRIO.

  A standard VI for encoder counting is used and compiled under the FPGA environment.

  During the measurement, I have observed that there are number of significant loss in both directions encoder.

  I don't think that there is a problem with VI like I used it several times on the encoders with output RS422.

  Is there a problem with my current encoder with respect to its electrical interface with NOR-9401?

  Thank you.

  I don't think that there is a problem with pull-up resistance. Even if the digital IO ports have their own resistance to pull-up (usually of the order of 4.7kOhm - should be included in the manual), the power to be handled by the circuit of encoder output transistor is about 2mA. -Check your configuration for a correct connection GND. You must connect the encoder directly power GND to DGND to the printed circuit board Terminal.

• connect labveiw 8.2 with nor pci-6251

  I have no pci-6251 and its cd driver with labview 8. How can I connect the daq with labview 8.2 and run programs

  Hello

  I can't download the driver of NOR-DAQmx 8.7.1, connect labview 8.2 with NOR-DAQmx PCI-6251...

  Why?

  Please answer...

• Using PCI-8532 with NOR-DNET 1.6.6 / NOR-DNET 2.0.2

  I have a PC with the following configuration test set-up:

  • Card PCI-8532 DeviceNet
  
  
  • Windows 7 Enterprise, SP 1
  
  
  • LabVIEW 2010 Runtime
  
  
  • NOR-DNET 1.6.6 with MAX 5.0
  
  
  • No environment of LabVIEW Development
  
  
  • PCI-8532 isn't available in MAX and Windows Device Manager indicates the card as "PCI Device" with an exclamation mark.

  Here is a screenshot of Windows and MAX Device Manager:

  

  I can't install the NOR-Industrial communications for DeviceNet 2.0.2 on this computer because I get the following error:

  

  Well, I have two questions

  1. How can I install and use the PCI-8532 and see with NOR-DNET 1.6.6? If this is not possible:
  
  
  2. How can I create an executable file on my system (portable) development with LabVIEW 2010 or 2011 LabVIEW and run this executable on the test set-up. I currently have on my development system:
  
  
  • Professional 2010 LabVIEW and LabVIEW 2011
  
  
  • NOR-DNET 1.6.6
  
  
  • No hardware OR at all
  
  
  • I have to install the NOR-Industrial Communications for DeviceNet 2.0.2 on my laptop (my development system)
  
  
  • This will interfere with my current NOR-DNET 1.6.6 and then I select which driver to use at compile time

  Thank you

  Nick

  Nick HY,

  No, it is defenitely not a replacement yet and I will work with our Web Department who make clearer on our web page.

  The development of the new API is pretty well done, but based on your feedback, we are planning to improve compatibility, so you can for example use the old APi 1.6.x and the new APi of 8532 on the same machine, so you can use the old and the new material on this same machine. Which would be important for you?

  For the moment we intend not to allow only one type of material on the same machine to save you development time. Let me know what you think.

  To clarify the situation today: The InCOM for Devicenet component is not part of LabVIEW. It's just a very simple means of communication with the I/o variables and blocks of function for the MS. The driver should install fine even without installed LV. The error message is quite a Bug on our side, and the solution would be to use the Builder installer LV to create a new installer that can install 2.0.x Incom Dnet driver without having installed Lv.

  And today, you should be able to have the 1.6.x both pilot 2.0.x in parallel and use the API 1.6.x with old boards yonce and the variable approach of IO 2.0.x with your new Board of Directors.

  I'll keep this post updated as soon as we have a stable Beta available I'll post something.

  DirkW

• problem with loopback test base with NOR-6008

  I recently started to use DAQmx in c# .NET 4.0 with NOR-6008 USB DAQ. I tried a loopback test by connecting output to an analog input analog and tried readign the signal from the output to the entrance but did not send the signal (or maybe a problem with the code). The analog input readign reads a random value rather than the value entered by the user for the output. I connected ao0 and ai3 on data acquisition. Here's the code.

  private void button1_Click (object sender, EventArgs e)

  {

  Task analogOutTask = newTask();

  AOChannel myAOChannel = analogOutTask.AOChannels.CreateVoltageChannel ("Dev1/ao0", "myAOChannel", 0, 5, AOVoltageUnits.Volts);

  AnalogSingleChannelWriter writer = newAnalogSingleChannelWriter (analogOutTask.Stream);

  Double analogDataOut;

  analogDataOut = Convert.ToDouble (AnalogOut.Text);

  writer. WriteSingleSample (analogDataOut, true);

  }

  Private Sub button2_Click (ByVal sender As Object, EventArgs e)

  {

  Task analogInTask = newTask();

  AIChannel myAIChannel = analogInTask.AIChannels.CreateVoltageChannel ("Dev1/ai3", "myAIChannel", AITerminalConfiguration.Differential, 0, 5, AIVoltageUnits.Volts);

  AnalogSingleChannelReader reader = newAnalogSingleChannelReader (analogInTask.Stream);

  Double analogDataIn is reader. ReadSingleSample();

  AnalogIn.Text = analogDataIn.ToString ();

  }

  Hello

  I built an application using your code (with task.verify) and it works beautifully.

  Have you tried different channels of inputs/outputs?

  

  Curt

• PWM with NOR-USB 94xx?

  Hello everyone,

  already, I asked once about the creation of PWM with hardware. And I was pleased with the response. But now I found 94xx Series-USB OR hardware. Here are the materials of high-voltage-Digital i/o. If any of you have already met with this one, would like to hear your conclusion about them. Would also appreciate if you could answer my question:
  Is it possible to create a PWM Signal with NOR-USB 94xx?

  Thank you

  Grigory

  Grekov wrote:

  I'd be more interested in the USB Module NI 9472 USB connection. Because it's the only one that would match my request.

  What is your application?

  Why don't choose you something in this list.

  If your condition is out to say 24 v PWM signal... you can also plan to use a custom circuit intermediate, not only to scale the output signal of the device (at 24 v) but also the reader following circuit.

• Clock and hw external trigger with USB-6210 on Linux with NOR-DAQmx Base?

  I have two devices USB-6210 I need to synchronize so that they both collect data exactly at the same time. I was told by support OR I can send the clock off Dev1/PFI4 and have the two USB-6210 s read the clock in through their own PFI0. I also want to trigger data collected for each device by sending a trigger off Dev1/PFI6 and have two devices to receive the signal on PFI2.

  All my attempts to try this are filled with error messages and my research online seem to say that's not possible with USB devices on NOR-DAQmx Base 3.4.0f2 on Linux.

  I "ve tried using example AI programs and those who do not seem to work either for external clocks. Here is the code I tried:

  #include "NIDAQmxBase.h"#include 
  
  #define DAQmxErrChk(functionCall) { if( DAQmxFailed(error=(functionCall)) ) { goto Error; } }
  
  int main(void){    // Task parameters    int32       error = 0;    TaskHandle  taskHandle = 0;    char        errBuff[2048]={'\0'};    int32       i;
  
      // Channel parameters    char        chan[] = "Dev1/ai0";    float64     min = -10.0;    float64     max = 10.0;
  
      // Timing parameters    char        clockSource[] = "/Dev1/PFI7";    uInt64      samplesPerChan = 1000;    float64     sampleRate = 10000.0;
  
      // Data read parameters    #define     bufferSize (uInt32)1000    float64     data[bufferSize];    int32       pointsToRead = bufferSize;    int32       pointsRead;    float64     timeout = 10.0;
  
  printf("Calling CreateTask...\n");    DAQmxErrChk (DAQmxBaseCreateTask("",&taskHandle));printf("Calling CreateAIVoltageChan...\n");    DAQmxErrChk (DAQmxBaseCreateAIVoltageChan(taskHandle,chan,"",DAQmx_Val_Cfg_Default,min,max,DAQmx_Val_Volts,NULL));printf("Calling CfgSampleClkTiming...\n");    DAQmxErrChk (DAQmxBaseCfgSampClkTiming(taskHandle,clockSource,sampleRate,DAQmx_Val_Rising,DAQmx_Val_FiniteSamps,samplesPerChan));printf("Calling StartTask...\n");    DAQmxErrChk (DAQmxBaseStartTask(taskHandle));printf("Calling ReadAnalogF64\n");    DAQmxErrChk (DAQmxBaseReadAnalogF64(taskHandle,pointsToRead,timeout,DAQmx_Val_GroupByChannel,data,bufferSize,&pointsRead,NULL));
  
      printf ("Acquired %d samples\n", pointsRead);
  
      // Just print out the first 10 points    for (i = 0; i < 10; ++i)        printf ("data[%d] = %f\n", i, data[i]);
  
  Error:    if( DAQmxFailed(error) )        DAQmxBaseGetExtendedErrorInfo(errBuff,2048);    if(taskHandle != 0) {        DAQmxBaseStopTask (taskHandle);        DAQmxBaseClearTask (taskHandle);    }    if( DAQmxFailed(error) )       printf ("DAQmxBase Error %d: %s\n", error, errBuff);    return 0;}
  

  When I run the resulting program, I see this:

  $. / acquireNScans-ExtClk
  The CreateTask call...
  Call for CreateAIVoltageChan...
  Call for CfgSampleClkTiming...
  Error-89136 DAQmxBase: route specified cannot be satisfied, because the hardware does not support it.

  For example, a clock and a trigger can be imported via one of the PFI lines by using a USB-6210 on Linux with NOR-DAQmx Base? A clock and a trigger exportable via one of the PFI lines?

  If so, does anyone have the code example illustrating how to do this, or can you at least tell me the names of the lines ("PFI0/Dev1" or other) so I can try again?

  Clues or suggestions would be helpful.

  Thank you

  -Tom

  The clockSource in the example specifies an output rather than an input channel channel. Change source "/ Dev1 / PFI0" solved the problem.

  Please close this post.

• or-scope with nor-6229

  Hi all

  I would like to know if I can use or pci-6229 with nor-soft scope? I found no information on it.

  Thank you

  Dima.

  
  

• Measurement and Automation does not open and generates the MAXKnownException error with an unknown exception.

  Measurement & Automation does not open and generates the MAXKnownException error with an unknown exception.

  Heres the log

  Context where the exception was taken:
  (No context - the unhandled exception)

  Size version of Base module
  -------------------- -------- -------- ------------------
  NIMax.exe 00400000 0006 has 000 4.6.0.49152
  ntdll.dll 770E0000 00180000 6.1.7601.18247
  00110000-76060000 6.1.7601.18409 Kernel32.dll
  KERNELBASE.dll 74E00000 00047000 6.1.7601.18409
  SYSFER. 74830000 00072000 12.1.1101.401 DLL
  1BFB0000 0001 NiMaxImp.dll B 000 4.6.0.49152
  Shell32.dll 74E50000 00C4A000 6.1.7601.18429
  Msvcrt.dll 76830000 000AC000 7.0.7601.17744
  74 00000 00057000 6.1.7601.17514 SHLWAPI.dll
  76740000 00090000 6.1.7601.18275 Gdi32.dll
  00100000 76480000 6.1.7601.17514 User32.dll
  Advapi32.dll 75DD0000 000 A 0000 6.1.7601.18247
  sechost.dll 76CC0000 00019000 6.1.7600.16385
  000F0000 rpcrt4.dll 76980000 6.1.7601.18205
  SspiCli.dll 74AE0000 00060000 6.1.7601.18443
  CRYPTBASE.dll 74AD0000 0000 C 000 6.1.7600.16385
  LPK.dll 76470000 0000 has 000 6.1.7601.18177
  USP10.dll 768E0000 0009D 000 1.626.7601.18454
  Ole32.dll 75F00000 0015C 000 6.1.7601.17514
  Msvcp90.dll 739F0000 0008E000 9.0.30729.6161
  Msvcr90.dll 73DB0000 000 has 3000 9.0.30729.6161
  74470000 00009000 6.1.7600.16385 VERSION.dll
  IMM32. 00060000 60000 74 6.1.7601.17514 DLL
  000CC000 76BB0000 MSCTF.dll 6.1.7600.16385
  74320000 00021000 6.1.7600.16385 Ntmarta.dll
  Wldap32.dll 00045000 763E0000 6.1.7601.17514
  Uxtheme.dll 6EB20000 00080000 6.1.7600.16385
  NiMaxUI.dll 1C2D0000 00269000 4.6.0.49153
  Msvfw32.dll 6BE30000 00021000 6.1.7601.17514
  73970000 00032000 6.1.7601.17514 WINMM.dll
  Comctl32.dll 73E80000 0019E000 6.10.7601.17514
  Wsock32.dll 73DA0000 00007000 6.1.7600.16385
  74DC0000 00035000 WS2_32.dll 6.1.7601.17514
  NSI.dll 75AA0000 00006000 6.1.7600.16385
  Oleaut32.dll 76580000 0008F000 6.1.7601.17676
  6D8E0000 003 Mfc90u.dll has 1000 9.0.30729.6161
  MSIMG32.dll 6EBA0000 00005000 6.1.7600.16385
  dwmapi.dll 6EB00000 00013000 6.1.7600.16385
  MFC90ENU. DLL 6EAF0000 0000 D 000 9.0.30729.6161
  NiMaxRes.dll 1BFD0000 0007 has 000 4.6.0.49153
  BtMmHook.dll 10000000 00038000 6.4.0.2900
  PSAPI. DLL 76440000 00005000 6.1.7600.16385
  DCIMAN32. DLL 6E1F0000 00006000 6.1.7601.18177
  MXS.dll 1 B 240000 4.6.0.49152 0000F000
  mxsutils.dll 1B4D0000 00041000 4.6.0.49152
  Msvcp71.dll 7C3C0000 0007C 000 7.10.6030.0
  7 360000 00056000 7.10.6030.0 Msvcr71.dll
  mxsout.dll 1 B 400000 00075000 4.6.0.49152
  64600000 00014000 4.257.3.0 nirpc.dll
  Mswsock.dll 73A 90000 0003C 000 6.1.7601.18254
  profapi.dll 76460000 0000B 000 6.1.7600.16385
  mxMax.dll 1BF20000 00086000 4.6.0.49152
  58000000 00240000 6.5.0.3005 AsstntUI.mxx
  MFC80U. DLL 71210000 8.0.50727.6195 0010F000
  MSVCR80.dll 0009B 000 8.0.50727.6195 72E50000
  Comdlg32.dll 20000 75 0007B 000 6.1.7601.17514
  71180000 00087000 8.0.50727.6195 Msvcp80.dll
  ATL80. DLL 6BD70000 0001 B 000 8.0.50727.6195
  MFC80ENU. DLL 730F0000 8.0.50727.6195 0000E000
  59000000 00582000 6.5.0.3005 mxwTask.dll
  00011000 74180000 6.1.7601.17887 Netapi32.dll
  74170000 00009000 6.1.7601.17514 netutils.dll
  74150000 00019000 6.1.7601.17514 srvcli.dll
  wkscli.dll 74140000 6.1.7601.17514 0000F000
  56000000 00148000 6.5.0.3005 mxwRCEng.dll
  mxcal.mXX 1 A 110000 00056000 4.6.0.49152
  mxcat.mXX 1BE20000 000AB000 4.6.0.49152
  nidmfuiu.mXX 04360000 0010D 000 1.11.0.49152
  NIPALU.dll 64000000 00057000 2.1025.3.0
  64500000 00006000 2.1025.3.0 nipalut.dll
  NIPAL32.dll 00007000 1F700000 2.1025.3.0
  SETUPAPI.dll 76240000 0019D 000 6.1.7601.17514
  CFGMGR32.dll 75DA0000 00027000 6.1.7601.17621
  76220000 00012000 6.1.7601.17621 DEVOBJ.dll
  6 280000 00031000 1.9.0.49152 nimdbgu.dll
  6 000000 00017000 1.9.3.49152 niorbu.dll
  nimstsu.dll 6E180000 0001 has 000 1.11.0.49152
  nimhwcfu.dll 6DFD0000 000 B 6000 1.11.0.49152
  6 050000 0001E000 1.9.0.49152 nidimu.dll
  nimxdfu.dll 0003E000 1.10.0.49152 6D0F0000
  nimxpu.dll 6E1B0000 0000 000 1.11.0.49152 B
  Iphlpapi.dll 74280000 0001C 000 6.1.7601.17514
  WINNSI. DLL 74270000 00007000 6.1.7600.16385
  74B 40000 001BD000 11.0.9600.17126 WININET.dll
  76A 70000 API-MS-Win-Downlevel-User32-L1-1-0.dll 00004000 6.2.9200.16492
  770B 0000 API-MS-Win-Downlevel-shlwapi-L1-1-0.dll 00004000 6.2.9200.16492
  75AB0000 API-MS-Win-Downlevel-Version-L1-1-0.dll 00004000 6.2.9200.16492
  76430000 00003000 6.2.9200.16492 API-MS-Win-Downlevel-normaliz-L1-1-0.dll
  normaliz. DLL 76450000 00003000 6.1.7600.16385
  iertutil.dll 75AC0000 00219000 11.0.9600.17126
  76610000 00005000 6.2.9200.16492 API-MS-Win-Downlevel-advapi32-L1-1-0.dll
  76200000 00017000 6.1.7601.17514 USERENV.dll
  nidmxfu.dll 04470000 0049F000 1.12.0.49152
  nimru2u.dll 6EC70000 00044000 2.10.1.49152
  nimmgluu.dll 69830000 0001E000 1.11.0.49152
  nimercu.dll 6DFB0000 00019000 1.11.0.49152
  MFC71. 00106000 140000 7 7.10.6101.0 DLL
  MFC71ENU. 360000 5 0000E000 7.10.3077.0 DLL
  niGPIBui.mxx B 6, 000000 0008E000 2.7.0.49152
  niIVIui.mxx 02CE0000 000D 0000 4.2.0.49152
  niPXIui.mxx A 671 0000 000BC000 2.1280.1.49152
  niRemPXI.mxx 1 A 270000 00057000 4.6.0.49152
  mxRmCfg.dll 1 has 000000 00090000 4.6.0.49152
  niRMui.mxx 1AD70000 000FD000 4.6.0.49152
  NISRLUI.mxx 6B 500000 00061000 3.4.0.49154
  63800000 00010000 2.7.0.49152 NiSpyLog.dll
  niSWui.mxx 1A3B0000 00072000 4.6.0.49152
  niVISAui.mxx 63360000 0017D 000 4.1280.0.49152
  62 30000 0002E000 4.1280.0.49152 niVISAres2.dll
  RICHED32. DLL 40000 00006000 6.1.7601.17514 6FC
  Riched20.dll 61F70000 00076000 5.31.23.1230
  Wshtcpip.dll 73A 80000 00005000 6.1.7600.16385
  nisysapi.dll 68 has 00000-000B 2000 5.5.2.49152
  Dbghelp.dll 70F20000 000EB000 6.1.7601.17514
  -------------------- -------- -------- ------------------

  Application: C:\Program Files (x 86) \National Instruments\MAX\NIMax.exe
  User name: administrator
  OS version: 6.1.7601 (Service Pack 1)
  Exception code: C06D007E
  Exception addr: 74E0C42D

  Sender's address: 74E0C42D
  Function name: RaiseException
  Module name: KERNELBASE
  Parameters: 00000000 00000001 0518FD84 C06D007E
  Source file: (not available)

  Sender's address: 68A3C6F7
  Function name: DllUnregisterServer
  Module name: nisysapi
  Parameters: 00000000 0518FD50 005F59B8 0000001E
  Source file: (not available)

  Sender's address: 68A53D87
  Function name: DllUnregisterServer
  Module name: nisysapi
  Parameters: 00000350 68A791B8 005F59B8 00000000
  Source file: (not available)

  Sender's address: 68A0DC65
  Function name: nisysInitDiagnosticsByValue
  Module name: nisysapi
  Parameters: 68A 01680 00000001 68A93BB8 FFFFFF01
  Source file: (not available)

  Sender's address: 68A0DFC4
  Function name: nisysInitDiagnosticsByValue
  Module name: nisysapi
  Parameters: 005E2C40 00000000 00000001 00000001
  Source file: (not available)

  Sender's address: 68A 01698
  Function name: nisysInitDiagnosticsByValue
  Module name: nisysapi
  Parameters: 005E2C40 00000000 00000001 00000001
  Source file: (not available)

  Sender's address: 1BE27A73
  Function name: mxGetProvider
  Module name: mxcat
  Parameters: 020469F0 02047084 0518FED0 1BE76CBA
  Source file: (not available)

  Sender's address: 1BE30D2E
  Function name: mxGetProvider
  Module name: mxcat
  Parameters: 02029FA8 02047748 0518FF34 1BE21D4C
  Source file: (not available)

  Sender's address: 1BE35780
  Function name: mxGetProvider
  Module name: mxcat
  Parameters: 00000000 00000000 02047818 020469F0
  Source file: (not available)

  Sender's address: 1BE21D4C
  Function name: (not available)
  Module name: mxcat
  Parameters: 02029FA8 1BE6264D 0518FF7C 73DD3433
  Source file: (not available)

  Sender's address: 1BE21CDC
  Function name: (not available)
  Module name: mxcat
  Parameters: 02030018 00000000 00000000 9192C45C
  Source file: (not available)

  Sender's address: 73DD3433
  Function name: endthreadex
  Module name: MSVCR90
  Parameters: 00000000 0518FF94 7607338A 02047818
  Source file: (not available)

  Sender's address: 73DD34C7
  Function name: endthreadex
  Module name: MSVCR90
  Parameters: 02047818 0518FFD4 77119F72 02047818
  Source file: (not available)

  Sender's address: 7607338A
  Function name: BaseThreadInitThunk
  Name of the module: kernel32
  Parameters: 02047818 00000000 00000000 775D5D69
  Source file: (not available)

  Sender's address: 77119F72
  Function name: RtlInitializeExceptionChain
  Name of the module: ntdll
  Parameters: 02047818 00000000 00000000 73DD345E
  Source file: (not available)

  Sender's address: 77119F45
  Function name: RtlInitializeExceptionChain
  Name of the module: ntdll
  Parameters: 02047818 00000000 00000000 73DD345E
  Source file: (not available)

  If I could come with the OS discs for the thing, I think I'd do a new install of Windows 7.

  Mike...

• How to generate sine waves of the evolution of the frequencies with neither 6733?

  I have a card ni6733. I want a specific frequency of the output waveform. After a few cycles, waveform frequency must be changed several times without delay. Bandwidth varies from 0.1 Hz to 10 Hz.

  I'm new on the map of NI6733, if have no idea about it. I intend to use the scheme of double buffering for waveform generation. Timing here is critical.

  Please give the sequence of function (if possible).

  Hi Andrew, I found problem in double buffering when using the buffer of size less than 16384 (32768/2). Why? I don't know... also beyong 1,25,000 "stack overflow" error was coming. Anyway, I dropped the idea of using double buffering. Now I use generation of waveform buffer alone without the help of NIDAQMakeBuffer. Instead, I create the buffer myself having data points of variable frequency to set the number of cycles. as demand for time-duration of profile waveform must be generated is limited to 50 seconds, and I use the rate constant update of 1000 samples per second, buffer size if necessary not creating any problems so far (for now). Thank you very much for your generosity. Rahul

• Simulate the sine wave using LabVIEW FPGA with NOR-myRIO and display in real time

  Hello

  I'm relatively new to LabVIEW FPGA. I am trying to test (and later apply) controllers high speed on myRIO.

  At this point, I'm trying to simulate the sine wave from 1 to 10 kHz using Sinewave generator VI express. I also intend to display the sine wave on the time real (RT) using FIFO. However, I had a bit of trouble to understaing various synchronization parameters.

  1. how to encode information about the sampling frequency generating sine wave? (The side FPGA vi requires only the frequency of the signal and possibly phase and does not rate update lines)

  2. how to estimate the number of items in a FIFO? (that is, the relationship between the rate of updates to loop (RT), the signal frequency, sampling frequency and the number of items in the FIFO)

  It would be great if we could share a very simple program (side host and target) that did something similar.

  Thank you

  MILIN

  Milot,

  I think the problem is the type of data in your FIFO. Your FIFO is configured to use a data type of I16. The problem is the number, it displays only ever will be-1, 0 or 1. To resolve this problem, you must send the sine wave as a fixed point data and convert it to a double on the side of the RT. This should significantly improve your resolution.