CVI2013 DAQmxGetSystemInfoAttribute (DAQmx_Sys_DevNames, buf, 0);

Similar Questions

• Is it possible to enumerate devices by PCI properties, HAVE / AO?

  I asked this in the CVI forum yesterday, but there are probably more people who know NIDAQmx here.

  Reason: I would like to program my application to use some HAVE and AO, he can find on a CompactDAQ chassis. It is the 4th update to this app in 20 years, and I would leave the possibility to change the hardware without having to recompile.

  So, I saw AQmxGetSystemInfoAttribute (DAQmx_Sys_DevNames) which gives me a list of connected devices of NOR.

  Great, I can analyze that.

  But then I wanted to know which ones is input analog and analog outputs.

  I first looked at DAQmxGetChanAttribute (task, channel, DAQmx_ChanType, & Type), but you must have already set the channels yourself... Needless.

  Then I looked at NISysCfgGetResourceIndexedProperty() but I don't see any property that lists the available channels and tell me if it is ME or AO.

  How is that possible? I forget some obvious function calls?

  Thank you

  Thank you, I finally found it by looking at the header file that these functions are not all in the Panel of the function:

  DAQmxGetSystemInfoAttribute (DAQmx_Sys_DevNames, Str, 255);

  cDAQ9184-19E4514, cDAQ9184-19E4514Mod1, cDAQ9184-19E4514Mod2

  For a list of devices. And then for each device:

  DAQmxGetDevAOPhysicalChans (channel, Str, 255);
  cDAQ9184-19E4514Mod1/ao0, cDAQ9184-19E4514Mod1/ao1, ao2-19E4514Mod1/cDAQ9184, cDAQ9184-19E4514Mod1/ao3

  DAQmxGetDevAIPhysicalChans (channel, Str, 255);

  AI0-19E4514Mod2/cDAQ9184, cDAQ9184-19E4514Mod2/ai1, ai2-19E4514Mod2/cDAQ9184, cDAQ9184-19E4514Mod2/ai3

• In CVI2013 'mobile projects' need of a reconstruction

  Hello

  Although the bug reported below may be covered by the Bug No.433769 , it is perhaps not obvious so I wanted to share with you in case you have been reckless enough to upgrade to CVI2013...

  I'm working on a project on two different computers and so to transfer all the files back, i.e. the * .c, * .h, *.ico, *.uir, *.prj and *.cws files. In the past, it worked more or less okay with CVI2013 it fails: If you have a testament more recent file CVI2013 IUR use it not but one in the folder build CVI... so use the menu command 'rebuild' the standard 'build' button is not sufficient, you will see the old user interface...

  Hello Wolfgang,

  I have reproduced the issue and it seems that it is indeed related to bug 433769.

  Thank you for this information and best regards,

  = Nelu F. | National Instruments.

• Compilation of CVI2013

  Hello

  I'm still discovering all these exciting features of CVI2013, so here I am with two issues related to the compilation:

  (1) on the compilation Options / Configuration Options Panel, the check box 'Show indicators of warning in the window output to build' doesn't seem to have an effect: in both cases, I get the warning messages (warning level set to Custom). What is a warning flag?

  (2) the announcement of the new Albums of CVI2013 claims to build faster. My impression is that now, with the help of CVI2013 in debug mode, take it same code about 5 times longer to compile. Unfortunately I did not measure the compile time before the upgrade, so it's an indicative value only. Is there a setting I have forgotten?

  Thank you!

  Hi Wolfgang,.

  Thank you for the project. I confirm that we must, as you said, about 5 times more time to compile with CVI 2013. I don't have a reason for you at the moment, but I created a bug (#422103) report to study soon.

  Luis

• DLL in CVI2013 call

  Sorry for this question but I'm not very familiar with the external DLL...

  I have an older code where I used

  empty typedef (__stdcall * fp_SPNDLdllTYPE) (double *, double *, double *, double * long *, char *, long);

  I need it to assign the address of a function in the DLL using LoadLibrary and GetProcAddress.

  Everything was going well until I recompiled the code with CVI2013, .the obtained address now is zero...?

  Given that the compiler has changed, I have tried the two default calling conventions in the Build options, but it did not help...

  What should I change? Thank you!

  I would like to once again thank you to you all my apologies for this off-topic... It turns out that the issue is not related to CVI, is the dll that had changed...

  I was told that, in the last version, the missing subroutine has been divided in two pieces (with different names, of course)...

• CVI2013 f1 and preprocessor # directive

  CVI2013 with f1 gives error of generation of preprocessor # directive (token concatenation).

  See attachment

  You incorrectly use the # operator.

  The # operator is also called 'token paste operator', and its purpose is to tell the C preprocessor to concatenate two chips.

  You just want to concatenate two strings: you don't need any special operator:

  #define LocalDir   "E:\\"  SharedDir        // define
  

• With CVI2013 breakpoints work differently

  In the past, I used to insert lines 'doing nothing', but which allows me to set a breakpoint. Now, with CVI2013, the following doesn't work anymore:

  If (expression)

  {

  something

  }

  on the other

  {

  ;<- putting="" a="" breakpoint="" here="" is="" useless:="" the="" breakpoint="" is="">

  }

  The solution is to have something like

  If (expression)

  {

  something

  }

  on the other

  {

  Delay (0.1);<- putting="" a="" breakpoint="">

  }

  If clang is 'code optimization' even in debug... mode?

  In addition, set or remove a breakpoint causes the file be recompiled - it slows down a lot debugging

  Hello Wolfgang,.

  The compiler is 'optimization' code in configurations debug in the sense that it generates code for an empty statement (a semicolon). There is no any other kinds of optimizations. I filed the bug report # 423474 for the question, because as you point out, it can be very useful to set a breakpoint on these empty statements.

  I can't reproduce your second problem. I can set and remove breakpoints during a debugging session as in CVI 2012. The file is not recompiled accordingly and the debug session is not restarted or abandoned. I'm probably missing something. Can you post instructions step by step to reproduce the problem?

  (FYI: when you start to debug, CVI always checks if something in your project needs to be rebuilt and the Build output window appears.) But this does not mean that the ICB is reconstruction actually anything. It's just our way of saying "just check whether the project is always up to date. And it is. Move along. »)

  Thank you

  Peter

• CVI2013 f1 and lines excluded

  I already reported a bug using excluded lines with CVI2013 (see here)

  Now with the patch of f1, the bug was corrected partially, but the problem is still there if you exclude (CTRL + E) lines in a heare file included from another file to header (and not directly a source file).

  See attached example and exclude line 4 in dummy.h to see the problem (CTRL + E).

  Hey Vix,

  Thanks for explaining more.  I was able to reproduce the behavior, and I filed a bug (ID 439152) report to follow it.  We appreciate your comments!

  Best regards,

• upgrade recommended CVI2013-&gt; CVI2015

  Hello

  OR Update Service offers you the new CVI2015. There is a note that this "installation does not replace any other versions of LabWindows/CVI.

  I would like to replace my version of 2013 by the new (while keeping user settings as much as possible).

  What is the way recommended - first uninstall CVI2013? Or it uninstall after installing CVI2015?

  Thank you.

  So the bitter news, is that the Update Service cannot be used to upgrade CVI this way - it can only be used to install another version. Personally, I find that disappointing. OK, now I know and I hope that CVI users are notified.

• False ASCII control characters values in Variables and the call stack in CVI2013?

  Hello

  I think that there is an error in the window "Variables and stack calls" If you want to find your variables in ASCII format.

  (0-31) control characters are not displayed correctly. They are offset by 2.

  For example:

  Character in decimal format is 10 (LF), but when you're chancing to ASCII it is projection \012.

  The same with 13 (CR). This character is \015 as ASCII.

  I think that it was no problem in CVI2012.

  Best regards

  Gunther

  I do not use CVI2013 Yes so I can't answer about this specific product, but the code you are showing are the octal equivalent of the specified decimal value: it is possible that control characters (or generally the natually those non-printable) is replaced by their octal equivalent to the chain.

• RADIUS - Dest buf 512 more small then data len len 759

  I would like to ask that the community on RADIUS error connect 4.2 ACS (0) buld Patch 124 12:

  [079] message EAP valuse: Dest buf len small 512 data then len 759.

  Is this critical error that has deeply an EAP conversation between the authenticator and server?

  Where could trigger the buffer length?

  Hello

  It is a cosmetic issue and shouldn't cause problems.

  http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.do?caller=pluginredirector&method=fetchBugDetails&bugId=CSCsh37811

  Kind regards

  ~ JG

  Note the useful messages

• How to make apdu.getBuffer () return buf which is greater than 133 bytes.

  {} public void process (APDU apdu)

  Byte [] buf = new byte [256];

  buf = apdu.getBuffer ();

  GOOD PRACTICE: BACK 9000 ON SELECT

  If (selectingApplet()) {}

  return;

  }

  apdu.setIncomingAndReceive ();

  switch (buf [ISO7816. {} OFFSET_INS])

  case (byte) 0 x 01:

  It is my method of process. I have a command APDU length 200 bytes I want the buffer to read and store in a local byte array. However, apdu.getBuffer () only entering the first 133 bytes of data.

  According to javadocs:

  "The APDU object is owned by the Java Card runtime environment. The APDU class maintains a byte array buffer which is used to transfer incoming APDU header and data bytes as well as outgoing data. The buffer length must be at least 133 bytes (5 bytes of header and 128 bytes of data). The Java Card runtime environment must reset the APDU buffer before each new message received from the CAD. »

  Given the length of the buffer is greater than 133 bytes, why he declined the remaining bytes?

  I use jCardSim on NetBeans IDE, version 2.2.2 of the java card.

  Also, could someone explain to me what exactly does apdu.setIncomingAndReceive ()? My code is able to build/run with and without it.

  Thank you

  Hello

  your code is not correct.

  never allow something outside the constructors and methods of customization that you know are called only once

  It will destroy your card as a 'new' allocates data to the eeprom.

  setIncomingAndReceive also toggle the protocol handler for receive mode (t = 1 and without contact, sends ACK in T = 0)

  then he makes the data available in the buffer

  the buffer is at LEAST 133 bytes, but it may be more

  If your command apdu contains more data, then these data are already in the buffer

  read the Lc offset to know the actual length.

  BTW, the comment of 'good practice' indicates that you use a code of example jcop as-is without understanding... I saw so many times!

  good luck, javacard is not as simple as java desktop... think "on-Board Unit 8-bit! You're not going malloc() in the main loop of arduino, right?

• [XNET] [CVI2013] Search for the periodic signal CAN

  Hello

  I use CVI 2013 and the toolkit NOR automobile 1.1 command the diagnostic value.

  OR PXI-8513 to edge (2 CAN bus)

  I want to know how to check if a periodic signal is currently subject to be sent?

  Best regards

  Blue

  I couldn't find an example of CVI that illustrates the use of the nxGetProperty function to get the calendar type and pass the time of a framework. If I have time Monday I'll try to create a.

  In the meantime, I can provide a quick snippet of LabVIEW to illustrate the general idea of how to get these properties of a session reference:

  

• [CVI2013] DeleteFile() error

  Hi all

  I use the DeleteFile function to remove a few files. The problem is when I call this function, I get this error:

  Error - 6   "attempted to make unusable control the active control.

  Here's the call:

  DeleteFile (tcCheminBase);

  tcCheminBase = "C:\file.mdb" and the file exist for sure, I check it.

  If I get these windows errors: this one when I debug code

  

  and when I Test the UIR

  

  Can someone help me solve that please?

  Best regards

  Hello

  I use MakePathname so I'm not worrying about the path string.

  I resolved the probem. In fact, I had an open connection with the file in the folder I want to delete it, so if this file is used, you cannot delete even manually in the operating system.

  I followed the Open/Close link with the database, and I checked if all connections are closed.

  So when I callek function delete, I have no error.

  Hope this topic helps someone else.

  Thank you.

  Kind regards

• Debug the project with CVI2013 problem

  Hello NO,.

  the following scenario could be improved, I think that

  If I press the button "Debug Project" (green triangle), you can start compiling. As it may take some time one may be tempted to press the button "Debug Project". Interestingly, now the button is dimmed, but also the build fails.

  This behavior could be repaired if the green button would be grayed out as long as clang is running...

  Hi Wolfgang,.

  We're tracking at your request in bug report #423029.