In the help documentation for the ni-scope the maximum delay time is defined in terms of the number of requested posttrigger samples and the actual sample rate. How does this work with continuous acquisition where the number of posttrigger samples isnt specified? The doc also mentions that external clock will affect the maximum delay also, but does not mention how..
↧
PXI-5122 max trigger delay time for continuous acquisition
↧
PXIe- 8135 OS update
Hello, everyone!
I have one NI PXIe 8135 in a NI PXIe- 1062Q chassis which runs on windows 7 and uses LabVIEW 2011. I want to upgrade it to windows 10. Can anyone suggest me how to do it and what steps should I go through? Thank you!
↧
↧
PXI Compatibility
Hi guys, I am knew on this type of simulation platform. I have the following equipment:
PXIe-1082, 8-Slot 3U PXI Express Chassis; NI PXI-5105, 8-ch, 60 MS/s Digitizer w/128 MB Onboard Memory; PXI-5412 100 MS/s, 14-Bit Arb with 8 MB; PXIe-8821, Win 7 (64-bit)
and I want to suggest me which of the following will work better by using the above mentioned equipment:
1. PXI-5691 8 GHz Programmable RF Amplifier Module
2. a. PXIe-4610 & b. PXI-4022
↧
what is replacement part for 778279-02
778279-02 was last orderable in May. what is recommended replacement
↧
Updating LabVIEW in NI PXIe- 1062Q
Hello!
I am trying to use NI DCpower drivers to access the pallettes to control the SMU port in the PXI 4130. The chassis currently runs on Windows 7 with Labview 2011 SP1 installed. But, for DCpower drivers to work, the LabVIEW software at least requires a 2009 version. So, as Windows 7 is compatible with Labview 2018, I was thinking it to update the LabVIEW. Can anyone suggest me how to do it with and without using an internet connection? Thank you!
↧
↧
udp broadcast Windows 10
Good Morning, I am seeking information, or assistance concerning the sending of a UDP broadcast message with an IP address pf 0.0.0.0. I was able to do this using NMap string on an 8820 controller Windows 7 in a PXIe chassis with 3 PXI 8234 ethernet cards. I am using a broadcast IP address of xxx.xxx.xxx.255. We are attempting to transition to a 1U Windows 10 NI computer using MXIe to replace the 8820. Using WireShark, I can verify the packet is received by the target only if I specify the target IP and port. It appears that if I attempt to to do a broadcast of xxx.xxx.xxx.255 or 255.255.255.255 that wireshark never see it. Any ideas, help or suggestions?
Thanks, Phil
↧
PXIe-6555 script - export marker issue
Hello,
I'm trying to synchronize HSDIO (PXIe-6555) marker with PPS (PXIe-4112) sequence iteration step (see attached screenshots). That is, I need marker to trigger next step in predefined voltage sequence. ... But an error is generated that trigger line (PXI_Trig0) is already in use that is a bit confusing, because PPS is waiting for trigger rather than export it (at least this is my understanding) ... Any ideas ?
↧
PCIe-8362 Not Detecting (2) PXIe-1084
Hello,
I am trying to connect (2) PXIe-1084 chassis's to a PCIe- 8362 on a Windows 7 imaged PC. Only one chassis is being seen in NI-MAX. I have enabled the DIP switch for BIOS Compatibility Mode, and downloaded the BIOS Compatibility Software as both were needed just to see one chassis in MAX.
Both chassis's are detected if I connect them one at a time, but not if I connect them BOTH at the same time.
When I connect both chassis's to the 8362 in device manager I see the following error
Any thoughts on why this would be happening? Again I can see both chassis's just fine individually, just not when they are plugged in together at the same time.
↧
Driving Between '0' and 'X'(Hi-z) in a single vector for I2C communication using PXIe-6570
Hi,
We are using NI PXIe 6570 for generating I2C patterns to test the I2C devices.
Currently we are building one full clock in a single vector. We are using SBC format to generate a clock signal and NR format to generate SDA line. In order to maintain the required I2C timing parameters like T_Low, T_High and Data Setup time, we are adjusting the drive edges in the vector. The time set and the pattern file that we are using is displayed below,
We have an I2C device with external Pullup and the I2C Master (PXIe-6750) should send an I2C signal toggling between 0 and X(Hi-Z) to communicate with the device. We are trying to use the same timeset configurations as mentioned above and drice '0' and 'X' as per the drive edges. When we place 'X' instead of '1' in the pattern file, the pin goes to Hi-Z state for the entire period of the vector and the drive formats and edges are not coming into picture. But we need to maintain different pin states with the same vector (for example, clock line should be at '0' for T_Low and 'X' for T_High).
Is there any way to drive between '0'and 'X' in the same vector as we needed?
↧
↧
Using PXIe 8234 as a EtherCAT Master
Hi every on
I'm using PXIe-1062 chassiss + Real-Time PXI controller
Can I use PXIe-8234 dual poGigabit Ethernet Interface as a Master EtherCAT?
↧
PXIe-6556 calibration support
Hi,
since the PXIe-6556 is not available anymore, will there be a point in time when the calibration support for this card ends?
regadrs
markus
↧
PXIe-6556 support in NI Modular Instruments Python?
Will there be a support for this card in the NI Modular Instruments Python library?
Is the nidigital_64/32.dll supporting this card?
regards
Markus
↧
"niSwitch Abort Scan.vi" takes a lot of time in scanning mode
Following example is based on
C:\Program Files (x86)\National Instruments\LabVIEW 2017\examples\instr\niSwitch\Switch - Scanning - Software Scanning (NI-SWITCH).vi
Environment Information
- LabVIEW 2017
- niSwitch 17.0
- PXIe-8821 + PXIe-1078
- PXIe-8821 + PXIe-1082
- PXI-2567
- ScanList: ch0->com0
I have a question why "niSwitch Abort Scan.vi" takes a lot of time under scanning.
When "Wait Between START and ABORT" was set to 0, the VI took about 16msec.
When I increased the parameter to 50msec, it took 1.6msec, error "-1074126842" returned.
I guess under scanning, the VI takes a lot of time. But it too long...
Is this based on my coding problem or hardware/driver?
Can I decrease the process time?
At above settings, the scan should finish within 1-5msec I believe. When I set "Wait Between START and ABORT" to 0, the VI took 16msec but when I set the parameter 15msec, the situation wasn't changed. From this result, the scanning was not finished, it took over 15msec.
Does scanning require so many overhead?
FYI: Error "-1074126842"
"The switch module is currently in scanning mode, and the operation cannot be performed at this time."
<<Under Scanning, no error but takes ~16msec>>
<<Scanning stopped, fast but error returned>>
↧
↧
Connecting strain gages to NI TB-4330
I'm trying to connect strain gauges to NI TB-4330, 8 Ch bridge.
The problem that I do not understand where the gauge wires should go. I'm attaching pictures, and I would appreciate any help.
Also, if there is an online resource that I can use for such information, please let me know.
↧
Calibration: PXI-4110 Fail .....NaN
1) PXI-4110 Calibration Fail at
| 0 | 0 | A | 0 | A | 0.00000 | A | -0.00400 | A | 0.00005 | A | 0.00400 | A | Passed | -0.00200 | A | 0.00000 | A | 0.00200 | A | Passed |
| 0 | 0.155683 | A | 0.227563 | A | 0.25000 | A | NaN | A | 0.15491 | A | NaN | A | Failed | NaN | A | 0.23148 | A | NaN | A | Failed |
| 0 | 0.384952 | A | 0.455557 | A | 0.50000 | A | NaN | A | 0.38158 | A | NaN | A | Failed | NaN | A | 0.45856 | A | NaN | A | Failed |
| 0 | 0.59482 | A | 0.683343 | A | 0.75000 | A | NaN | A | 0.58961 | A | NaN | A | Failed | NaN | A | 0.68113 | A | NaN | A | Failed |
| 0 | 0.850942 | A | 0.909144 | A | 1.00000 | A | 0.84294 | A | 0.85140 | A | 0.85894 | A | Passed | 0.90364 | A | 0.89755 | A | 0.91464 | A | Failed |
All connection is correct. Fail at 1A range Channel 0 only. Channel 1 and 2 is ok.
Calibration procedure is correct....Is Chassis or Controller can give such problem.?
↧
Requesting feedback on ni.com system Advisors
Are you satisfied with the capabilities on ni.com to spec out a system?
We are preparing to overhaul our ni.com system configurators (PXI Advisor, cRIO Advisor, cDAQ Advisor) and your feedback is critical to shape the next generation of these tools.
Please take a few minutes to complete the following survey about your experiences with the ni.com Advisors. Feel free to post feedback to this forum thread as well. Any and all feedback is appreciated.
https://survey.ni.com/jfe/form/SV_1GgsmWTeSeMqzKR
Gio L.
National Instruments
↧
PXIe-8840 black screen during shutdown
I have a PXIe-8840 Controller in a NI PXIe-1075 chassis with windows 10. When I shut down windows the monitor screen immediatley goes black and I can't see the shutdown process.
My problem is that the PXI chassis is part of our testsystem which has one main switch to switch off all devices. Since it is not possible to see the shutdown process the enduser might turn off the main switch before the system has completley shutdown.
Is there a way to show some shutdown information? Or a message at the end off the shutdown ("It's now safe to turn off...")?
Is that a normal behaviour? I already tried another monitor and cable but the result is the same.
↧
↧
PXI 8433/4 Half Duplex Help
Hello,
I have PXI 8433/4 Half Duplex card on my chassis. However, I don't know how to use it. I'm aware that I can read its COM port, but what if I want to read the line bit bit? I'm truely confused with this. My overall goal is to communicate with the FPGA card which is plugged into the same chassis.
Regards..
↧
Flex rio in rt target
Hi! I use a Basler aca 2000 340 km camera to grab images through ni 1435 frame grabber placed in a remote target with 8135 controller in a 1071 chasis
now i need to shift it to a 1483 adapter placed on a 7966R fpga flex rio
i have taken the 10 tap 8 bit camera with dram example and modified the project accordingly.
Now, there are 2 main vi.
1. 10 tap 8 bit camera with dram (fpga)
2. 10 tap 8 bit camera with dram (host)
The first one is successfully compiled in the fpga, but when the vi is opened (for interactive session) and i transmit some data through the UART transmit, it is returning a x15 which denotes not acknowledged (NACK) for the camera, but it should not be the case since the data i am transmitting is from the .icd file of the same camera for setting some particular parameters.
The second vi is running, the module enabled, and initialized indicators are glowing, when i start acquisition the Acq in progress indicator also lights up. But there is no image.
Now i am fairly new to this, and i donot know how to debug these also since, the probe indicators are also not available.
What am i doing wrong?
Is there any example for fpga module in remote systems?
↧
NI-PXI-6289 Analog Out
Can the NI-PXI-6289 Analog Out signal be set to trigger from an input from one or four input signals received by the NI-PXI-6289 Analog Differential input channels? I am monitoring a signal using a differential channel from the NI-PXI-6289. I want to use that signal to trigger an analog channel from the NI-PXI-6289 to turn on a power supply.
↧