SMU 8135 GPIB

Similar Questions

• SMU 8135 cannot ping pc when installing labview

  HJ. Help me

  my laptop do not install labview 2012 can ping with SMU 8135 but labview installed on my laptop cannot ping with SMU 8135. I don't understand

  Hi ffefef,

  Could you explain in more detail the question, you encounter?

  Thank you

• Setting IP error incompatible. SMU-8135

  Hello NOR Forum,

  I recently got a new laptop. I want it to work with the NI SMU-1078 chassis with controller Embeded PXIe-8135. I'm having a problem to connect to it. There is an error in Measurement & Automation Explorer > remote systems > NOR-PXIe8135-# > status "Incompatible IP Settings."

  I tried this http://digital.ni.com/public.nsf/allkb/A0F6EFF8A33578948625749C006DEC3B , but it wouldn't let me change my static IP address. Help, please.

  Hey waterox,

  1 take a look at this article, because it seems to apply to your current situation-

  Why can I not connect to my PXI real-time (RT) target on the network

  http://digital.NI.com/public.nsf/allkb/24D16468DE8838B2862568E200746D7E

  2. reformatting of the target can be a quick way to solve this problem.  You should be able to configure the IP address of the target once reformatted.

  3. make sure that your network card settings are correct on your host computer.  The following document describes the process with a CompactRIO which should act the same as your real-time target.

  Configure the CompactRIO with a static IP address

  https://www.NI.com/getting-started/set-up-Hardware/CompactRIO/static-IP

  4. how many NIC's a laptop?  You have active Wifi?  If Yes, take a look at this-

  Best practices for using multiple Interfaces (NICs) with products OR

  http://www.NI.com/white-paper/12558/en/

  I hope this helps!

• Problem sending trigger software through backplane PXI (chassis SMU-1082, SMU-6363 DAQ, SMU-6544-HS-DIO)

  Dear community,

  I am trying to implement a background basket (software) PXI trigger on a chassis NI SMU-1082 with LabView 2015 (32-bit) running on an SMU-8135:

  HS-DIO (SMU-6544) in slot 2,

  -Acquisition of data (SMU-6363) into the Groove 4,

  -Flex RIO (SMU-7962R + OR-6583) in the Groove 3.

  The trigger schema is explained in the attached file ' LV-PXItrig-HSDIO-DAQ - overview.jpg ".

  Scenario 1: written DAQ analog signal and sends signals trigger HS-DIO (software) through bottom of basket, after East of waveform of the complete signals to DAQ for acquisition.

  Scenario 2: logical impulse on an external port HS-DIO triggers signals HS-DIO, after HS-DIO waveform is complete DAQ triggered for the acquisition of the ADC by the backplane.

  In principle this breaks down to send a trigger of module A to B by PXI backplane. The SMU-1082 chassis has a bus trip with 8 lines (PXI_trigX, X = 0,..., 7) more a trigger in Star controlled the slot 2.

  I've linked to implement a software trigger, but I can't access the refreshing resource and execution, see the attachment. Other ways of implementation including the DAQmx Terminal / routine disconnect Terminal have not worked for me either. I am aware about the connection of trigger using the node property VISA but I can't make a trigger.

  Tips, comments or solutions are appreciated. Thank you!

  For scenario 1, you want to trigger the HSDIO acquisition to begin as soon as the analog output DAQ starts?  You can use DAQmx Export Signal to send the trigger for the start of one of the lines from the Trig PXI backplane. Then, you need to configure your HSDIO acquisition to use a trigger digital beginning on the same line of trigger. Take a look at the example of the "Dynamic hardware generation start trigger" in the Finder of the example (help > find examples)

  For scenario 2, looks like you do a dynamic unit HSDIO generation when a digital trigger arrives on one of the PFI lines. Once the build is complete, you want to send a trigger for the DAQ hardware to begin sampling. If this is the case, you again use a trigger to start material in your task of NOR-HSDIO, as you did for scenario 1, but use external trig line as the source, rather than the bottom of basket. There is no case of material when the build is finished, but you can use a marker in script mode event instead. The example of the Generation with dynamic event marker' in the example Finder gives a good starting point for this type of operation. You'll want to set the output terminal for the event to be a line of backplane trig, and then tap the DAQmx to start on the same line trig trigger.

• Unable to access SMU-7962R + OR-5734 in LabVIEW

  Hello

  I have already developed a SMU system that uses FlexRIO. This has worked well. FlexRIO devices appear in MAX OR as follows (note that FlexRIO modules have yellow icons of FPGA, and their adaptation modules are shown):

  

  I'm now trying to build an exact copy of this system. I put together a together identical material, and (far as I can tell) I installed all the same components as the original system (using the NI Developer Suite 2015 DS1 set). However, something is not quite right. Here's what MAX OR shows me in the new system (note that FlexRIO devices now have generic grey icons instead of yellow icons of FPGA, and adaptation modules are not visible).

  

  In addition, the LabVIEW code that I developed for the original system generates a runtime on the new system error "NOR-RIO: (Hex 0xFFFF0928) the name of the supplied resource is not valid in a resource name of RIO or the device was not found." Use MAX to find resources appropriate for the expected device name. " LabVIEW is unable to find RIO devices:

  

  Here is the list of software installed on the new system:

  

  I also installed NI FlexRIO Adapter Module Support 14.1.0 (who does not appear in NI MAX). Can anyone place what Miss me?

  Thanks in advance!

  Hi David,

  2 controllers had exactly the same BIOS (version 1.2.0f0), which was the latest version for the SMU-8135.

  It turns out that, even if I had installed the drivers, Windows had not "registered" (?) the drivers properly for some reason any. There was a lot of articles in "Device Manager"-> "devices OR-RIO":

  • x 15 "NI SMU-7962R", were all OK
  
  
  • x 15 "NOR-RIO FPGA Device", all had yellow exclamation on them.

  I clicked "NOR-RIO FPGA Device" and selected "update driver software...". '-> 'Browse my computer for driver software'-> "Let Me pick from a list of drivers on my computer"-> 'NI - RIO FPGA Device'. After that I did "device of FPGA OR-RIO", all 15 exclamation points disappeared and I could use my FlexRIOs correctly.

• SMU-8383mc in Slot 2 is not identified by SMU-1078

  Hello

  I have a problem with SMU-8383mc, which is connected to 2 SMU-1078 chassis. After I can't establish a connection through x 8 MXI cable (the pcie in the host pc card is properly recognized and listed in the Device Manager) I plugged the SMU-8135 embedded controller via LAN cable to my PC (Win7, x 86).

  After starting NI MAX it presents all the other Modules connected in the Slot 6 and slot 7 but Slot 2 seems to be empty, it is not listed. Has installed all the software I found on the host and more NI MAX system all software for SMU-8135. (after installing all the software I have to error on screen 1 boot: niecatapisv.dll not found!) ((dependency), but it's another thing).

  The SMU-8383mc Module has 2 status LED: green and not flashing do not. (PWR/LINK, MC). I have more ideas to solve the problem. Help, please.

  Thanks in advance for any help!

  Hello mgold,.

  NOR-PXImc 1.0, SMU-8383mc software is visible in MAX OR on the system connected via backplane (in your case, SMU-8135) only if the system is running Windows OS. So in your case of SMU-8135 running LabVIEW Real-time, you wouldn't be able to see the MAX NI SMU-8383mc device.

  However, because the lights are green the device is displayed in the Windows Device Manager, it is in a good condition and ready to use. You can verify that the hardware and software work properly by running PXImc examples in LabVIEW.

  Kind regards
  Sarah B.
  Software engineer
  National Instruments

• SMU FlexRIO DMA FIFO host read the FIFO overflows broadband bandwidth/DMA issues

  I'm working on an application that uses 2 modules FlexRIO, and 2 LVDS digital I/O adapters.  I'm driving each of the SDC A/SDC B ports on LVDS 16-bit data at 50 MHz adapters.  The FlexRIOs are expected to receive the data and write down them on four targets-to-host DMA FIFO (one per connector SDC), or two by FlexRIO.  The host reads the FIFO and brings together a series of tables each FIFO output 2D.  Ultimately, the individual tables (we're each a quarter of single image) will be assembled in simple images, but I haven't gotten that far yet.

  The duty cycle for the data is about 80% (in other words, I'm only transmit data to the FlexRIOs 80% of the time, the rest of the time the transmitters are disabled), so the flow is about 80 Mbytes/sec/port total invasion, or 320 MB/s on the four FIFOs DMA.  I find that the acquired data gaps sometimes inside that line up along the length of the material part of the DMA FIFO in FlexRIO modules.  In other words, if my memory FIFO DMA are set to 65535 length, I'll see a break in the data acquired at the word of data 65536th.  Data is a waveform of sight, which is essentially just a counter, so it's easy to see the break in the model.  For the words of first 65535, adjoins the data, then from Word 65536 model is discontinuous and starts counting again from there, contiguously.  At the beginning of the acquisition, the FIFO is erased: the beginning data read from the FIFO is always aligned correctly, so I know that the process starts at a good point.

  The error is not always the case: sometimes I get continuous data through the point 65536.  In addition, the error occurs independently between the four FIFO: on a particular race, a FIFO could have data of interest and some bad.  Rarely, all four FIFOs have good data.

  The fact that the gap of the configuration is to the point even the depth of the FIFO DMA tells me that fills the FlexRIO FIFO, the FPGA hardware without the system managing to move to read, which means that the data gets dropped during the period that the FIFO is full.  Then transfer to the host comes into action, there again is the space in the FIFO, and the data is once more contiguous in FIFO memory for a large amount of data (I have not yet tried to locate a second gap in the data of a single acquisition).  It seems therefore that the host doesn't have enough bandwidth between the FlexRIOs and the host of RAM to prevent the filling FIFO, or comes along some software process on the host that is temporarily stop the ability to instantly transfer.

  Are at - it a specification for the SMU flow system that would indicate that we are trying to use too much bandwidth?  Or are there priority controls on DMA FIFO that would allow us to raise the priority of the FIFO transfers as they are guaranteed to go in preference to other system tasks?

  System Specs:

  SMU-1075 chassis

  SMU-8135 CPU

  2 SMU-7962R FlexRIO modules

  2 digital i/o modules of NOR-6585

  LabView 2012 32-bit SP1 version 12.0.1

  A suggestion of an applications engineer of NOR and some experimentation has solved the problem. It turns out that I was calling the method FIFO of DMA stop just before the outbreak of the transmission of the data via a control for the FPGA FPGA VI. I did this in order to clear the FIFO before you begin data acquisition, but I didn't know that this method disables also transfer data between the memory FlexRIO and host. Following this call, I trigger the FPGA code to start filling its FIFO and then begin reading. Calling the Read of FIFO of DMA apparently light up the transfer back, but it seems that the host VI has been randomly slow down enough to move to the bed such as filling the side FlexRIO FIFO and dat would be lost. I changed the host VI to insert a FIFO method call start before the trigger for the FPGA signal, and the problem is now gone.

• Synchronization of VST: Ok with RFSG, problem with DAMA

  Hi all

  We strive to synchronize 2 VSTs (5644) with DAMA OR and NI RFSG.

  So far, we have been able to sync the RF Transmission of the VST 2 with RFSG, down a less than 100ps difference. It's excellent!

  But we have not been able to renew this success with DAMA: we have time differences in the order of between 2 VST 100us.

  We believe that we follow all the indications of the documentation of DAMA, as shown here:
  http://zone.NI.com/reference/en-XX/help/372058N-01/vstdevices/5644_rfsa_gsynchronizing_clock_signals...
  We ensure same buffers are empty at the beginning of the acquisition by manually empty the VST buffer before calling RFSAInitiate.

  NOTES:

  Our application is coded in C++ only.

  We do not and cannot share the LOs between 2 VSTs, as we Rx/Tx at different frequencies.

  Does anyone have an idea of what we could try?
  We attached the sign of e/s OR our acquisition. Please, let us know if you see something wrong.

  We use DAMA 14.5
  SMU-8135 controller, Win7 x 64
  SMU-1075 chassis.
  SMU-5644R in the location #2 and #6

  Best regards
  Serge

  Hi all

  Finally, support (Kevin Sooch) helped us to solve the problem:

• Error 1074097808 (Initialize with Topology.vi niSwitch)

  In trying to "initialize" the PXI-2527 switch module using "niSwitch Initialize.vi", I get the following error

  "Error - 1074097808 occurred at niSwitch Initialize.vi.

  Reason: unable to load dynamic library.

  "Name of the library: niswitchDAQmx.dll.

  I can see the switch module and configure the channels in niMAX. I reinstalled the software 15.0 NOR-DAQmx, 4.8 OR-Switch and NI Switch Executive several times to see if all the missing drivers would be restored. Also, I searched the entire hard drive, the Web site or Google, search FTP sites available and the NOR install discs, and I have not found such a driver under the name of "niswitchDAQmx.dll". If it's the simple solution, could someone please point me to the site where I can download it. I am running Windows 7 on an embedded controller with LabView 2013 SMU-8135. The module includes a PXI-4065 DMM and 2527 OR-Switch with a TB-2627 (Terminal). I have attached a screenshot of the 'NI Max installed hardware", a screenshot of the error message, a screenshot of the code segment and a screenshot of the software installed (OR MAX). Also, I am able to communicate with the 2527 switch OR use NI MAX "Test Panel", but I'm not able to create a DAQmx task for the switch (ex: resistance Signal acquisition). Any suggestion would be great. Thanks in advance.

  micgraph,

  Long story short:

  You will need to reinstall the COMPLETE OR-SWITCH 15.1 (link) and make sure the following option is selected. Installation with the default options * SHOULD * install this component and solve your problem.

  

  Long story:

  In order to allow smaller installs components helped break the driver and activate the dynamic dll loading. This allows customers to install a smaller part of the driver. (Instead of install to all HW, you can install it with the type "SwitchCA1, 2, & 3" [install huge] or with the type 'SwitchCA4' [small Install].)

  It seems (glancing at your MAX configuration) that you have installed the version 15.1 of the Runtime 'SwitchCA4 '.

  When you have completed the installation of the full version of NOR-SWITCH 15.1.1, it should appear in MAX with additional options.

  

• [VxWorks PXI] How to ensure that all updates in the buffer of data has been written to disk before you stop?

  Hello

  I have a RT SMU-8135 that records events and data from various sources in CSV files and custom binaries. I'm looking for a way to protect against data loss during a normal shutdown.

  Windows or Linux, I can programatically close the application and the operating system; It's enough to dump all the data disc and turn the power off when it is safe. However, as far as I know, there is no way to programmatically close a VxWorks target (e.g. http://forums.ni.com/t5/Real-Time-Measurement-and/Shutdown-of-cRIO-or-sbRIO-via-software-command/td-... )

  The best method I can think of right now is shut down properly the application of RT, wait "long enough" for buffers to clear and resources to be released, and then press the power button. The challenge is, I can't get good reviews when the application is fully closed.

  Is a more reliable way to do this? (Or am I overthinking things?)

  Thanks in advance for any advice!

  Hey JKSH,

  A number of things. First of all, are you sure that the SMU-8135RT is running VxWorks? The link below suggests that it is running Phar Lap ETS. On this basis, see the second link below, which tell about a similar question regarding the Phar Lap. The short of it is that it is not a software based on RT Linux targets non stop. Essentially, if you want to make sure that things are not going when you turn off, you will need to do something as printed in the console as it is ready to be put off tension after you have completed the activities, or have an LED start or stop flashing. So far, it doesn't seem there's a clear way to determine when all other activities have finished, but it seems that it is always "safe" stop the target at any time (safe for the target, but this does not guarantee that all activity is performed).

  What operating system is my controller real time running and why?

  http://digital.NI.com/public.nsf/allkb/35F1FD98520D6E0E8625783A005AF557

  Stop ETS

  http://forums.NI.com/T5/LabVIEW/switch-off-ETS/m-p/841366?requireLogin=false

• Increase the rate of target on Veristand

  Hello

  I am a novice user of Veristand. I'm doing a feedback from control with the help of a compactRIO:

  RT OR cRIO-9024

  Chassis cRIO-9113

  9220 and 9263 modules.

  I use Veristand with a compiled since Simulink model to make my will.

  I want to be able to reach frequencies of 10 KHz loop or more, but the loop of the target rate freezes the system when I try to go beyond 700 Hz.

  Is it possible to do?

  My model is very simple, for now, I'm simply connect the 9220 1 entry at the exit of the 9263.

  Thank you in advance,

  Kind regards

  Rates

  Hi prices.

  The 9024 is unable to run NI VeriStand at your desired pace. As you can see, it tops out around 700 Hz. There are several reasons for this, but the end result is that you will need different hardware to run at your desired pace. A 9082 will be much faster, and a SMU-8135 will be even faster than that. Also if you use PXI, if you only need of IO and no treatment only Co, our PXI DAQ devices allow you to hit the NIVS rates much faster than the PXI FPGA devices.

  Good luck!

• Playback issues of Thermocouples a 9214 in EtherCAT 9144 chassis

  I have an SMU-1078 chassis with an SMU-8135 controller and chassis EtherCAT 9144 with multiple C-modules, including a couple of 9213 9214, running Veristand 2014 and 2014, inertia. I updated last week so I think I have the latest updates for the hardware and software.

  The problem I encounter is that I can read my Type K thermocouples with Thermocouple 9213 modules, but when I connect them to the Thermocouple 9214 module, I see only TC0 change and the rest of the TC 9214 channels are 0 ° c. tried to use high speed and high resolution modes, but no difference. I also moved the module in slot 8 in the EtherCAT chassis, also without success. Then I moved the 9214 with its connector and thermocouples to another machine with a chassis cDAQ in 9188XT and I have read all the thermocouples with NI MAX. This proves that the module is working and that the module connections are good.

  I need to use the 9214 because of his ability to handle the higher common mode voltages. I need help. Please, I beg you.

  Thank you in advance

  Richard

  It ended up that I had to download the last update, 14.0.1 for the NOR-RIO. This solves the problem. I did have to reinstall Veristand, Labview, or any other driver.

  Thank you very much for your answers.

• Camera IP IMAQdx: Error 0xBFF69035 that the camera returned an unknown HTTP error

  Hello

  Thanks to the detailed advice to http://forums.ni.com/t5/Machine-Vision/Do-IMAQdx-and-NI-hardware-support-GigE-Vision-2-0/m-p/3164373... we decided to move from GigE cameras (Basler BIP2-1920-30 c) IP cameras to reduce CPU load.

  Unfortunately, I cannot acquire images from the camera via IMAQdx. When I click on "Snap" NI Max, I get "error 0xBFF69035 the camera returned an unknown HTTP error. This could be the cause? (The only other thread, that I found is http://forums.ni.com/t5/LabVIEW/camera-return-to-unknown-HTTP-error-in-Ni-Max-during-the-IP-axis/td-... but the steps proposed refers to GigE documentation that is not relevant)

  Notes:

  • The camera is connected directly on the LAN 2 port in the SMU (SMU-8135) controller.
  
  
  • I can ping the camera.
  
  
  • I can see the video stream from the camera via its web interface (using Internet Explorer to access http://169.254.75.137/webapp ).
  
  
  • OR MAX detects the camera, but he doesn't seem to let me set up properly. If I enter any number in the 'width' or 'Height', she gets has forced 1 - this behavior seems fishy.

  

  Thanks in advance!

  Hi BlueCheese,

  Thanks for your suggestions. It turns out that the IP settings are fine (although I still like to set static IP addresses for the camera and the PXI controller before you deploy the system).

  I found the system log unit of the Basler, who gets a new entry whenever I try to start an acquisition of NI MAX: user.err mjpeg: {2714} HTTP error 503: selected stream has wrong type of video (1! = 5). Then I discovered that (i) the camera default H.264 and (ii) IMAQdx only supports MJPEG, H.264 not.

  Setting the unit to use JPEG compression solves the problem.

• Generation of functions NI PXI-6704

  Hi forum people,.

  I have a question about the generation of functions, to be precise, without the adequate hardware PWM. I'm under NI SMU-8135 embedded controller in a chassis NI SMU-1078. It is equipped of PXI3 OR-8532 (DeviceNET), NI PXI-6515 industrial digital I / 0, NI PXI-6225 (M: multifunction DAQ series) and NI PXI-6704 (analog output). My question is: can I generate PWM of any of these materials?

  Thank you!

  Start with help > find examples or search the site of pwm.

  Fix your code if you want to help with it.

• Progress of asynchronous data TDMS wrote for LabVIEW RT

  Hi all

  I save data in many channels TDMS files.

  Data record should be done on a real-time target OR SMU 8135 with LabVIEW RT operating system.

  The data of all channels of the recording in a cycle time of 1ms.

  Question: What Advanced TDMS mode should be better suited for this task? Sysnchronous or asynchronously?

  It seems that the advanced TDMS asynchronous logging is not supported by LabVIEW RT? Is this true?

  Thank you.

  Rahul

  Hello Rahul,

  Advanced asynchronous PDM are not supported on RT.

  Best regards

  Christoph