Quantcast
Channel: Digital I/O topics
Viewing all 2182 articles
Browse latest View live
↧

Push-in spring terminal connector plugs for NI USB-6501

September 24, 2021, 5:41 am
$
0
0

Dear forum,

the NI USB-6501 is shipped with screw terminal connector plugs. I want to replace them by push-in spring terminal connector plugs (connecting/disconnecting a wire is much easier). It seems that the NI USB-6501 has COMBICON Jacks (see User Guide, page 5), so there should be matching plugs available by Phoenix Contact.

 

Can somebody give me a part number or a link for matching push-in spring terminal connector plugs, please?

 

If not: Does somebody know the exact pin spacing of the NI USB-6501?

 

Regards,

cpschnuffel

↧
Search

PXI-2586: Is there a spec on channel leakage resistance?

September 28, 2021, 8:50 am
$
0
0

Is there a specification for the minimum leakage resistance in any channel?

↧
↧

NI9403 with c# .net (without measurement studio)

September 28, 2021, 12:52 pm
$
0
0

hi

I would like to control the NI9403 with a C # application but without using the measurement studio.
I have looked in the examples which is in:
C:\Users\Public\Documents\National Instruments\NI-DAQ\Examples\DotNET4.5\ Digital
but I have the impression that uses the measurement studion because the examples are not functional for me.
Please advise or give me any example.

 thank you

↧

Trigger an output pulse every N input pulses

October 11, 2021, 11:16 am
$
0
0

Hello. I am new to LabVIEW and DAQs; the examples and this forum are very helpful.

I am using a USB-6341 DAQ.

 

I have a digital input signal that I would like to use to trigger a digital output. I can use the Counter - Single Pulse Output example vi from the Help menu and it works as expected.

 

However, what I would like to achieve is to trigger the digital output only every N input pulses. eg only on odd input pulses, or only every 5th input pulse.

 

To achieve this I think I should count the input pulses. I can use the Counter - Count Edges example vi, which works as expected to count the imput pulses.

 

What I am not sure about: how can I wire the number of edges from the count edges such that it becomes a 'trigger' for a single pulse output?

 

If you have any suggestions, or relevant links to help me with my problem I would be very greatful.

↧

Can I use NI 9264 to control a dimmer?

October 13, 2021, 4:28 am
$
0
0

Hello,
I am trying to integrate an LED light powered by a dimmable power supply into my NI 9264.

 

The dimming in the power supply is achieved by 1-10V PWM resistance, which I had previously controlled manually by a simple potentiometer installed on the dedicated dimming cables of the power supply.

 

I was wondering if I could use the NI 9264 I have to integrate the dimming somehow.

 

I might not be making too much sense, I'm pretty new in this...

Thank you
A.

↧
↧

USB-6501

October 13, 2021, 11:52 pm
$
0
0

USB-6501 上电默认为输入高电平，在不做硬件能通过NI MAX设置上电默认port0和port1的0~7引脚为低电平吗？

↧

PC crashes after installing HSDIO

October 14, 2021, 8:54 pm
$
0
0

PC:  Dell vostro-5890, i5 11400F 8G, win 10 system

 

I try to build a time sequence with PCI-6542. Since the card is too big, I connect the card to my mainboard through a PCIe-PCI patchcord. 

 

After the connection, PCI-6542 appears in NI-max but with no driver(labeled with a '!'). So I installed HSDIO, and reboot the computer. The computer goes crashed each time on the interface where the password is required. I can enter the system only after unplug the PCI-6542 card.

 

Do you know that is the problem and how to solve it? Thanks a lot,

 

Wang

↧

card development

October 17, 2021, 4:35 am
$
0
0

لدي بطاقة PS-5122 ، وأجهزة الكمبيوتر قديمة وبدأت تواجه مشاكل. أرغب في تطوير الأجهزة ، لكن الأجهزة الحديثة لا تحتوي على منافذ. ما هو البديل المناسب لهذه البطاقة؟

↧
Search

USb 6501 control with Excel 64 bit

October 17, 2021, 1:38 pm
$
0
0

Hello,

I am using USb 6501 to control various inputs on my board using the below Excel VBA code.

https://forums.ni.com/t5/Example-Code/Using-DAQmx-with-Microsoft-Excel-Visual-Basic-for-Applications/ta-p/3518041

This works fine with  32 bit excel on 64 bit Windows 10 PC. But this code doesn't work with 64 bit Excel on Windows 10 64 bit PC. Tried to modify the code as per suggestions from google search (Like changing "Long" to "LongPtr" etc..) and is not helping. Any changes in NI DAQmx C API needed?

Really appreciate a help on this so that I can control USB 6501 using 64 bit Excel VBA.

Thanks,

Leyo

↧
↧

Multiple I2C Busses on NI 8452 or 653x

October 18, 2021, 1:23 am
$
0
0

Hello,

 

for a current project, I need to communicate with multiple (e.g. 16 or 32) sensors via I2C in parallel. As the sensors are all identical and therefore have identical (unchangeable) I2C addresses, I need to use separate I2C busses. In addition, I would like to communicate in a parallel fashion, i.e. read/write for each bus independently. We use Matlab for high-level experiment control.

 

1) We already have a NI-8452 in the lab that we have used to communicate with a single device successfully. In the manual, a I2C port is mentioned (and can be read out (=0) with the C library). The Manual however never specifies whether there is only a single port or if it is somehow possible to create a second port. On the other hand, since the DIO lines are all software-timed, my assumption would be that this is not possible - then why does the IC2 port exist in the first place?

 

2) Assuming the NI-8452 (or a couple of those in parallel) is not a good option, what would be my best Hardware option from NI for this task?

E.g., would the PXI-6535/6/7 line be suitable for such parallel I2C operation?

 

Thanks in advance for your help,

 

Cheers,

Jakob

↧

NI 9205 - Input Bias Current

October 19, 2021, 6:10 pm
$
0
0

Hello,

 

Does anyone know if the Input Bias Current from the NI 9205 (100 pA) is per pin channel or for the entire module?

 

Thank you.

↧

matlab2018b中simulink模块里的real-time模块中没有pci模块

October 20, 2021, 1:52 am
$
0
0

matlab2018b中在simulink模块下的real-time模块中没有关于pci相关的模块，但是2014b中就有，请问有大神遇到过吗？这种该怎么解决？是什么问题？

↧

Setting clock reference for USB-6001

October 20, 2021, 1:12 pm
$
0
0

I am trying to set up a USB-6001 to send a pre-programmed sequence of TTL pulses on software command. I am doing the programming in Python (via nidaqmx library). However, I can't seem to be able to set the rate for the sample clock. I'm able to set up a task and change the state of a pin by command, so I know everything is loaded correctly, at least.

 

 

 

>>> task_do.do_channels.add_do_chan('Dev1/port0/line0') DOChannel(name=Dev1/port0/line0)>>> task_do.do_channels.add_do_chan('Dev1/port0/line1') DOChannel(name=Dev1/port0/line1)>>> task_do.write([True, True]) 1 #I can observe pins turning on>>> task_do.write([False, False]) 1 #I can observe pins turning off>>> task_do.timing.cfg_samp_clk_timing(rate = 1000) Traceback (most recent call last): File "<pyshell#28>", line 1, in <module> task_do.timing.cfg_samp_clk_timing(rate = 1000) File "C:\Users\bglebov\Python36\lib\site-packages\nidaqmx\_task_modules\timing.py", line 3007, in cfg_samp_clk_timing check_for_error(error_code) File "C:\Users\bglebov\Python36\lib\site-packages\nidaqmx\errors.py", line 127, in check_for_error raise DaqError(error_buffer.value.decode("utf-8"), error_code) nidaqmx.errors.DaqError: Requested value is not a supported value for this property. The property value may be invalid because it conflicts with another property. Property: DAQmx_SampTimingType Requested Value: DAQmx_Val_SampClk Possible Values: DAQmx_Val_OnDemand Task Name: DO test Status Code: -200077

 

 

From what I understand, I need to set the clock before setting up the waveform. For this, I'd like to use the internal clock of the USB-6001. The spec sheet defines the timebase frequency at 80 MHz, and max sample rate at 20 kHz. However, I get the above error for any rate value. (Just for kicks, I also tried passing a string for rate value, and it came back with a different error - so it's not a type error, at least.)

 

Does USB-6001 even have an internal clock reference, or does it have to us an external one? If so, how do I set this up?

 

Also, assuming I can set this up, would the sequence fire off whenever I run task_do.start()? I couldn't find a setting for a software trigger.

↧
↧

read and write at the same time DIO NI-9375

October 26, 2021, 12:32 am
$
0
0

Hello all,

 

 I am working on a project in Labview, and I am having some issue to understand how I need to configure the DIO module NI-9375. I want to read some digital inputs but in the same time I have buttons in Labview interface and when I click on one of them I want to write a digital output. I got the error 200419 when I try my code. From what I understand I cannot read and write at the same time with this module but I don't know how to correct this.

 

I am completely new to Labview so I may missed something in the configuration but I have been trying to solve this problem for days and it makes me loose time...

 

I put the code in attached files and the error message I get. Any help would be appreciated to understand how the module works.

 

Thanks in advance,

 

Regards,

Agathe

↧

Power requirement for NI 9266 @ 24VDC

October 26, 2021, 12:35 am
$
0
0

What is the total power requirement for NI 9266 @ 24VDC from external power suppluy and from chassis

↧
Search

communicating with a sensor through SDI12 protocol

October 26, 2021, 4:04 pm
$
0
0

Has anybody been able to read a sensor that communicates through SDI12 protocols? Any leads would be very useful.

 

This is what I have:

Sensor: ATMOS 14 from Meter.com. The sensor specifies compatibility with any data acquisition system capable of 3.6- to 15.0-VDC power and serial or SDI12 communication.

Data acquisition: NI USB-6008   (it is unclear to me if this datalogger works, it does have digital I/O channels so it seems it should work)

 

I tried connecting it to NIMAX following the steps below:

Connecting Digital Input Signals to a DAQ Device - National Instruments (ni.com)

But I basically only see the image below regardless of what is connected where in the datalogger

awayllace_0-1635289209002.png

 

I tried running the program "Digital continuous input.vi" from the examples provided in LABVIEW2018, and it just gives me an error.

 

I know many sensors communicate through SDI12 protocols so I am hoping someone did something similar before?

 

The integrator guide of my sensor provides commands to interact with the sensor, for example ai! for identification, etc.

 

Thank you!

 

↧

HSDIO: Error -1074115898 (0xBFFA4AC6) - Hardware clocking error occurred

November 3, 2021, 4:21 pm
$
0
0

Full Error:

Error -1074115898 occurred at niHSDIO Write Named Waveform From File (HWS).vi

Possible reason(s):
Driver Status: (Hex 0xBFFA4AC6) Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, please contact National Instruments Technical Support.

Device: 6548_HSDIO_1

Status Code: -200313

 

I am attempting to set up a Generation based on an HWS file that was imported from a VCD through the NI Digital Waveform Editor.  Speaking to others, the Waveform Editor is evidently known to be extremely buggy... which is why it has been extremely difficult to even import the file.

 

When I call write named waveform with the file, I get the error above.

 

I am trying to get this generation to use an external clock.  The clock is not running yet, as it's generated by an external piece of equipment that thinks it's communicating over a parallel SPI bus.  The idea is to set up the generation with the external clock, start it, and then trigger the external device to start communicating.

 

This appears to not work... the generation seems to want the external clock to be running when I write the waveform.  But the waveform needs to be buffered and ready for the first pulse of the clock.

 

EDIT:  I loaded their simple External Clock Dynamic Generation code and it's got the same error.  So yeah, it seems like their driver wants the clock to be running when you write the waveform to the device.  Since my clock is external and runs in synchronized bursts, I don't understand how this could work.

 

(The error occurs at the Write Data function)

 

HSDIO_ExtClockGeneration Snippet.png

 

↧
↧

I2C Communication with NI-9401 or NI-9403 Modules

November 4, 2021, 8:43 am
$
0
0

I need to configure a component over I2C and the only DIO modules I have are the NI-9403 (slow, 32-channel) and NI-9401 (fast, 8 channel). I'm using the cRIO-9048. I have found this NI article about I2C communication. It says:

 

"I2C communication requires the device to tri-state the DIO lines on the fly. The 9401 is unable to do this without external hardware. NI thus recommends the 9402 for I2C communication."

 

So I can't use that package with my 9401, but can I use the 9403? I downloaded the package and dove into the subVIs a bit and found that the I/O is accessed inside a single-cycle timed loop. It seems the 9403 does not support use in a SCTL and changing it to a normal while loop doesn't seem to work (not surprising). 

 

I managed to find another package called I2C Implementation in LabVIEW FPGA by NI, which seemed promising. Looking at the VIs it doesn't seem to rely on an SCTL. However, I can't seem to make it work - there are all sorts of "not executable" errors. Maybe I just haven't installed it correctly, or it's for an older version of labVIEW or hardware.

 

Am I out of luck? Can anyone recommend another LabVIEW I2C package that will work for me?

↧

HSDIO: PXIe-6548 with non-continuous 4MHz external clock

November 4, 2021, 10:19 am
$
0
0

We have an application where we are essentially synthesizing a response from a sub-component.  There is a master component that initiates and drives the communication, and our system will act as the client that will respond.

 

The master will provide a clock that is pulsed only with the data being driven when it sends commands, and then it will send a continuous clock until the client responds on the data lines.

 

When setting up the generation side of the Bi-directional communication, I am getting an error when I set the task to use CLK_IN, but then don't have the clock started before starting the task.  I can't have the clock started prior to the task running, because the clock is only generated when the master is sending data.  And the data chunks are literally 12bits long, so even if I could trigger data out on the master, the HSDIO card is not going to see a continuous wave.

 

For testing, I hooked up a function generator and ran a continuous pulse at 4MHz.  This made the NI examples work.  So I know the issue is that there is no clock provided when starting the task.

 

(Actually, there are two places when the error can occur.  If I have no trigger defined, the error will occur when writing the output wave to the buffer.  If I have a trigger defined, this will be OK, but the START function will error if there is no clock.)

 

So the problem is that I need to set up and prep the HSDIO dynamic generation PRIOR to the start of an external clock.  Then, the external clock will not be continuous, but the pulses will occur in groups (very similar to a SPI communication)

 

Any ideas?

↧

DAQmx (Specifically NI 9042) trigger pulse width specifications

November 4, 2021, 5:45 pm
$
0
0

Hi Everyone,

 

We are trying to trigger DAQmx functions using the FPGA on the same cRIO.

 

The idea, as it stands, is to use a NI 9042 in FPGA mode to export the trigger signal to the NI 9042 that is in Real-Time acquisition mode.

IIRC, there are ways to do this via the backplane or without any external wires, but team lead explicitly desires hardwiring externally like this.

An alternative I might try to pitch is to export via the 9042 into the PFI0 input.

NEVER THE LESS we're trying to capture as high resolution precision as possible... so I need to know more distinctly what is the minimum pulse width I need to generate on the FPGA for the DAQmx trigger function to detect it correctly.

An initial hunch is that the refresh rate will be limited by the real-time operating frequency. (somewhere in the ms range)

The nanosecond resolution is only for allowing us to precisely synchronize the trigger, I don't need to do this repeatedly such that we worry about data handling over multiple clock rates or anything super complicated like that.

 

From what I have looked up the specs on the NI 9042 say a propagation delay averaging ~20ns, but maxing up to 55ns. Between two of them that'd be ~40ns, 110ns... is that my answer sitting right in front of me (making the pulse width more than 110ns?) or do I have to account for the slow speed at which the real time system cycles?

Say the real-time system is running at 1khz... if a 125ns pulse comes, is it not going to be registered by the DAQmx trigger VI?

 

Thanks for your time

↧
Viewing all 2182 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>