Similar Questions

• Measurement and automation cannot find the pxi-6070e in the Groove 3

  I just moved my PXI-1002, containing a PXI-6070e in the Groove 3, to a new computer. The new computer is Vista. I installed the drivers of NOR and measurement and automation (via NIDAQ880f2). After connecting the chassis and turn on the computer, M & A sees the chassis but says the range containing the 6070E is empty. The link and the power lights are lit (green) on the 6070E. Any help would be appreciated.

  These suggestions have worked. Thank you.

• Measurement and automation cannot find PXI cards

  When I start measuring and automation and watch devices & Interfaces I get the "MAX database connection error.  I followed the steps for "corrupt" of the database, but I can not any more to discover that any file or folder exists.

  C:\Documents and Settings\All Users\Application Data\National Instruments\MAX\Data Dictionaries\Last

  When I look for this place, I find that there is no record of MAX.

  How should I proceed?  There are otherways I do devices and Interfaces show me what PXI cards I have?

  Thank you

  Kevin

  Great!

  So, how did - it go!

  -laboratory

• measurement and automation

  I'm just starting using the measurement and Automation Explorer.   Half an hour ago, I performed a calibration of temperature to get familiar with the process.  It seemed to work.

  I tried calibrate again.  It says my current calibration is 31/12/1903 - Question 1) why is this?

  I pressed the button , then came the name of my Stallion, then

  I left the characteristics of calibration because it was one of the screen: 1000 samples at a frequency of 1000 hz, then I pressed

  I received the following message is displayed:

  Error 50103 the DAQ Assistant.  -Question 2) what is this error code for

  Question 3) where can I find a list of error code numbers and their meaning?

  Thank you

  jdsnyder

  OK, now the problem is finally solved!  I re - adjust the device.

  At work the first time, he then had to be reset.

  Thank you

  Jon SNyder

• AVT Marlin not recognized by measurement and Automation Explorer

  Hi all

  I use an AVT Marlin F046B on Windows 7 and sometimes this camera is not recognized by Machin Vision: measurement and Automation 5.0 (MAX), no IEEE 1394 devices is displayed.

  This problem appears randomly. When the camera is not recognized by MAX, if I use the driver of the TRA for IEEE1394 card, the camera is recognized by AVT SmartView and when I installed the driver of return of Microsoft for IEEE1394 card, the camera is not always recognized by MAX.

  Could there be a problem of compatibility somewhere?

  Thanks in advance,

  Hello gege91,

  It is a driver problem Windows 7. Please see the following link for more details:

  http://www.alliedvisiontec.com/EMEA/support/knowledge-base.html?tx_nawavtknowledgebase_piList [uid] = 1...

  Oliver

• Measurement and Automation Explorer

  Hello

  I use the controller measurement and automation. It has detected my usb USB-HS-GPIB interface, up to now, no problem.

  I have a device connected Keithley, I want to detect, but there is no scan button for devices when I go into my USB interface. He's just "open test VISA Panel' and 'Save' buttons. Any idea what the reason could be?

  It does not show the unit. Screenshot is attached.

  Kind regards

  Guy

  I had problems with the old version of MAX do not recognize USB devices correctly. OR recommend the latest version of MAX to solve the problem. I would not recommend the old version 2.7 or 2.8 and MAX that comes with them. I had to install the DAQmx 9.0 x to get the last MAXIMUM to solve the problem. It has been incorrectly grateful as USB devices or instruments. When I've updated DAQmx and MAX I then could finally remove the list of bad devices.

• You want to know the NI-VISA order in measurement and Automation Explorer

  Hello

  I use measure and Explorer of automation to connect my equipment through LAN and it works well.

  But this device does not detect my code VBA with Ni-VISA. I want to know how the software (measurement and Automation Explorer) generates the connection and reading the message of compression inside the unit.

  It's my code. I check the read back value if it is "100 connection accepted."
  ----
  Public Function VNAconnection() As Boolean
  = stat viOpenDefaultRM (defaultRM)
  msDly (1000)
  Stat = viOpen (defaultRM, ' TCPIP0::10.85.148.60::5000:OCKET ", VI_NULL, 20000, NETWORK" ')
  msDly (1000)
  = stat viSetAttribute (RÉÉS, VI_ATTR_TMO_VALUE, 15000)
  msDly (1000)
  Feedbk = Space (80)
  status ("Waiting for connection VNA")
  = stat viBufRead (NETWORK feedbk, Len (feedbk), Actual_Length)
  If InStr (left (feedbk, Actual_Length), "accepted") = 0 Then

  MsgBox "error has occurred. Ethernet connection not accepted! »
  NETWORK viClose

  viClose defaultRM

  VNAconnection = False

  Exit Function

  End If
  End Function

  Thank you

  Michelle,

  I found I need to add viWritebuff to * IDN, equipment, then he will answer a message accepted.

  Thank you

  Xin

• The measurement and Automation Explorer is completely empty. No idea why?

  Hello

  When I open Measurement & Automation Explorer, there is nothing in the main boxes, boxes are completely empty. The top toolbar with file/Edit/tools is there, but all that is empty.

  I had good success with the SCXI-1000 chassis in a few years when I did further research at another University. At my new University, it gave me access to an SCXI-1000 chassis with an SCXI-1600 module to connect to the computer via USB. I reinstalled windows on an old computer to 64-bit, had the hand of the entire system, the Measurment and Autiomation Explorer open as expected, then was that NEITHER ceased support for the SCXI-1600 on a Win 7 Pro 64-bit modules. So, I've divided the hard drive into two partitions, installed Win 7 Pro 32 bit and reinstalled NOR then installed the updates for a few hours.

  When I try to turn on measurement and Automation Explorer, there is nothing in the window. What can I do to get the various boxes? I went to tools > reset Configuration data.

  

  Nicholas,

  I recently saw a similar problem on another post. This person has received the exact same blank screen because Windows Firewall has blocked MAX (nimax.exe). Try turning off your firewall temporarily and then see if MAX runs. If so, you will need to add an exception in your firewall settings. If this isn't the case, you could have operated in a corrupted installation and the need to do a repair.

  Ryan

• 6602 not detected measurement and Automation Explorer or Windows 7 Device Manager

  I have a PCI-6602, in a PC that is running windows 7 Home premium and it appearing not not in the Device Manager and as a result measurement and Automation Explorer.  What is strange, is that I don't see either the PCIe-6535.

  Hey M,

  Unfortunately if the windows Device Manager is unable to see the devices on multiple computers, it certainly points to the cards being broken.  I recommend you head over to http://www.ni.com/support/ and create a Service request to begin the process of repair for these devices.

• NOR-DAQ traditional (old) devices of measurement and automation explore 4.7 with LabView2010 under Windows 7.

  In measurement and Automation Explorer 4.7, with LabView2010 in Windows 7, peripheral OR-DAQ traditional (old) appears under devices and Interfaces and it allows me to create a chassis SCXI-1000, and she agrees "Reset for NOR-traditional DAQ.  However, it does not search the modules in the SCXI1000, and when I ask 'trial', he says 'Impossible to test the chassis at this time.'  The entrance of NOR-DAQmx devices for the SCXI-1000 chassis has no problem and detects the modules very well.  I need the Legacy DAQ to a popular former teaching tool that has no equivalent in NOR-DAQmx.

  Unfortunately, NEITHER-DQA traditional (old) for Windows Vista and 7 functions of the only driver on Windows 7 32-bit, as seen on the page of the driver at the end of paragraph 1 Solution. I recommend you move your program to DAQmx.

• No COM port available in the measurement and Automation Explorer

  Hi all

  I installed Labview version 9.0 (32-bit version) on a computer running Windows XP with Explorer Measurement & Automation. When I opened it, the program cannot find the COM or LPT ports. Anyone has a solution on what to do?

  Equip your CD/DVD device driver and reinstall the device drivers.

• Measurement and automation Reconoce mi PSC pero no lo reconoce mi of the project. If I have Real - Time Module

  The problem that I have are Measurement & Automation Reconoce mi cFP-2200 pero no lo reconoce mi project osea that al tratar add a new target and the device don't lo encuentra en red y me da el error Bank does not

  That tal Estel3an;

  You can have several reasons para you no one el proyecto the CFP in red, the first seria as the IP address of you PSC not accessible from the sea, are sea porque esta in una diferente subred o porque haya complicaciones in red you see Québec no you allow verlo. En that mencionas como MAX if lo puedes music y detectar none are not likely tan, ordered checar the direccion pero of you PSC y determining what is in the same segment that you PC o see if no is "cae" you red momentaneamente y esto no you eprmita see the CFP.

  Otra razon could ser as the instalacion del software to haya hecho en UN orden distinto al recomendado, for example if instalaste primero LabVIEW Real-time y despues LabVIEW o If instalaste los drivers (NOR-Fieldpoint) LabVIEW time before real tambien you could estar afectando. Instalacion practice are LabVIEW, despues Modulos (in this case LabVIEW Real-time) y por ultimo controllers (in this case NOR-Fieldpoint) of all manera las ligas queden creadas.

  Por ultimo could deberse problem of material of the United Nations, el as ¿podrias asegurarte status LED parpadeando en este no you driver of PCP? para descartar than sea por a problema en el PCP is not in you PC.

  I hope the information you sea ayuda.

  Suerte

• Measurement and automation software can not find DAQ

  I use a USB-6009 OEM data acquisition as part of a test set-up, and everything works fine.  We recently sent a Board in China with the same software we use, which they installed on a brand new computer.  When they plug the USB cable, the LED flashes on the DAQ card, and USB DAQ appears in the Windows Device Manager.  However, when they opened the software of Measurement & Automation, the device isn't isn't here.

  I got to try refreshing, reinstall, then by restarting without result.  No idea what they could do differently?

  Have they installed the patch that was published for NOR-DAQmx?  It is possible that they are using a computer with one of the affected USB HID devices.

• 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...

• NOR USB6210, problem to trigger on a PowerPlay with measurement and automation

  Hello

  I use Labview version NIDAqmx 8.7 driver version 8.5.1,, Measurement & Automation explorer 4.4.1 and a device OR USB6210.

  I create a task with Measurement & Automation to make an acquisition of voltage on the AI0 channel.

  I want to use the function of digital triggering with the channel PFI0. I connect a signal square on the AI0, and PFI0 channels. I put the edge on the RISE, for example. When I make several acquisitions, and I notice on the curve that the USB6210 device does not fire correctly, sometimes used trigger edge is on the RISE and sometimes FALL.

  Could you help me? Is it a driver problem?...

  Thanks in advance, Daniel.

  OK, nice to hear that everything works as expected.

  Good luck,