Error : TX RX Data Communication

April 20, 2020, 3:16 am

≫ Next: NI 4431 - Found by DAQMX, but NOT found by Labview instrument driver

≪ Previous: Keithley 2010 Scan and Read Channels

i used USRP2921 and LabVIEW NXG 2.1 and I setting the RF Communications that

<Tx setting>
IQ rate = 8M
Tx Gain = 8
Tx Carrier Frequency = 2.5G

<Rx setting>
Rx IQ rate = 10M
Rx Gain = 10
Rx Carrier Frequency = 2.5G

Tone amplitude = 0.707
Tone Frequency = 5k

size of waveform = 15k
number of samples =10k.
//
If set and executed as above, an error occurs at Tx, Rx and the program does not work.

Tx error = niUSRP write Tx data (CDB cluster).gvi [ERR] underflow: Empty the Tx buffer before new data is available. Consider reducing the I/Q ratio, speeding up writing, or increasing the number of samples per write. The recommended number of samples per write is multiplied by 363.

Rx Error = niUSRP Import Rx data (CDB WDT)Gvi [ERR]Packet timed out before receiving or sending. Not all samples may have been received or shipped. Consider increasing the timeout.

I don't know where the Tx, Rx errors occurred.

↧

NI 4431 - Found by DAQMX, but NOT found by Labview instrument driver

April 20, 2020, 2:40 pm

≫ Next: How to collect Uart information from a Texas Instruments MSP-FET Flash Emulation Tool

≪ Previous: Error : TX RX Data Communication

I have a NI 4431 which has been working well. It is recognized by MAX 19.5 and I am able to create tasks for it to make measurements, etc.

However, I am unable to use it within LabVIEW as the instrument driver finder cannot find it. I am able to find other instrument drivers such as my Agilent oscilloscope without issues.

Can you tell me what am I missing?

Thanks!

↧

How to collect Uart information from a Texas Instruments MSP-FET Flash Emulation Tool

April 21, 2020, 8:58 am

≫ Next: myRIO Auto Play

≪ Previous: NI 4431 - Found by DAQMX, but NOT found by Labview instrument driver

I use the TI MSP-FET Flash Emulation Tool to provide a usb/serial type connection to some devices. The tool establishes two com port connections to the computer: one for flashing the firmware to a device it's connected, and the other for providing Uart information from the device.

Normally, I use Ubuntu to SSH the computer where the tool and device is attached, then TMUX and picocom to get the device Uart info to display in the session window. My goal is to combine time stamped Uart information from the device with reference data I'm collecting in LabView. I'm not trying to use LabView to automate the firmware flashing, at least not yet.

I've debated different approaches to try. I thought about just recording the SSH session and removing the non-Uart device info. I also thought about using ExtraPutty to record the session and then use LabView to read information from the recorded file. But it seems like there should be a way to directly read the Uart info from the Texax Instrument's tool straight into Labview.

Any suggestions, ideas, or links to info that would help me?

Thanks!

↧

myRIO Auto Play

April 21, 2020, 11:28 am

≫ Next: Withdrawal.

≪ Previous: How to collect Uart information from a Texas Instruments MSP-FET Flash Emulation Tool

Hey Guys,

I am trying to connect a myRIO to my laptop and every time I do, I get this error. I made sure that have the myRIO Toolkit downloaded, but I am still getting this error message after a couple minutes after plugging the myRIO into my laptop with a USB cable. I tried plugging it in to different usb ports. I tried running it in "safe mode". It is a device that has been used before on a different laptop. I also tried to find it in NI MAX under remote devices and it doesn't show up. If there is any advice to fix this problem, it would be greatly appreciated.

↧

Withdrawal.

April 22, 2020, 12:23 am

≫ Next: PID Controller using video analysis

≪ Previous: myRIO Auto Play

Withdrawal.

↧

PID Controller using video analysis

April 22, 2020, 10:55 am

≫ Next: Does visa32.dll have a viFindResource() function

≪ Previous: Withdrawal.

Hi,

I am developing a PID controller, using video analysis.

The system works as follows: A potential difference is applied to an actuator that deforms mechanically. A camera captures the shift and sends a signal to the controller.

However, it is necessary to convert the image data into an electrical signal.

How can I do this?

↧

Does visa32.dll have a viFindResource() function

April 23, 2020, 7:05 pm

≫ Next: Visa Close is Freezing

≪ Previous: PID Controller using video analysis

hi：

I found that if I want to find devices on the network, I need to use the viFindResource() function. However, there is no description of this function in the description of visa32.dll. How should I call it

I replace viFindRsrc() directly without any return value.
thank you

↧

Visa Close is Freezing

April 24, 2020, 2:14 am

≫ Next: Error -1073807360 occurred at Property Node (arg 1) in VISA Configure Serial Port

≪ Previous: Does visa32.dll have a viFindResource() function

I use an USB based - Virtual Serial port - communication unit in my application. It uses the supply to send a signal to my DUT. Voltage one way and Current the other way. It is plugged directly into the PC, not via an USB hub

For every DUT the Serial port is opened and closed again after communication is done.

The problem is that once in a while the VISA Close is FREEZING. I see it maybe once for 1000-5000 units which is about 2-3 months of production. I have seen it on 3 different LABVIEW/TestStand versions with different VISA driver versions. Each are running on different computers

Could it be the VISA Driver?

Could It be the HW in the communication unit?

Could it be the Driver of the communication unit?

I have only seen the VISA Close to freeze in relation to this Hardware.

If it is related to the Hardware, why is the VISA Close freezing instead of returning an error?

The workaround is to unplug and re-plug the communication unit

Any suggestions are welcome

↧

Error -1073807360 occurred at Property Node (arg 1) in VISA Configure Serial Port

April 24, 2020, 4:53 am

≫ Next: Read oscilloscope data in real time

≪ Previous: Visa Close is Freezing

Hi everyone.

I've encountered the error shown above.

Info:

I've been using 2 Arduino-based controllers called Controllino MAXI.

They are based on The Mega 2560. In the past I've been able to connect to both of them through different ports by using the LINX interfaces.

However, recently I've only been able to connect to on of the controllers, and not the other.

The device manager recognizes them both as it has in the past, as Arduino Mega 2560 (image attached).
The Arduino IDE recognizes and allows uploads to COM6, but doesn't recognize any connection to COM3, giving the following message (verbose on):

Arduino: 1.8.12 (Windows 10), Board: "CONTROLLINO MAXI"

C:\Program Files (x86)\Arduino\arduino-builder -dump-prefs -logger=machine -hardware C:\Program Files (x86)\Arduino\hardware -hardware C:\Users\gr\AppData\Local\Arduino15\packages -tools C:\Program Files (x86)\Arduino\tools-builder -tools C:\Program Files (x86)\Arduino\hardware\tools\avr -tools C:\Users\gr\AppData\Local\Arduino15\packages -built-in-libraries C:\Program Files (x86)\Arduino\libraries -libraries C:\Users\gr\Documents\Arduino\libraries -fqbn=CONTROLLINO_Boards:avr:controllino_maxi -vid-pid=0000_0000 -ide-version=10812 -build-path C:\Users\gr\AppData\Local\Temp\58e9973bb6e2e908c6c199f5a9d39075.tmp\output -warnings=none -build-cache C:\Users\gr\AppData\Local\Temp\arduino_cache_972135 -prefs=build.warn_data_percentage=75 -prefs=runtime.tools.avr-gcc.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.avr-gcc-4.9.2-atmel3.5.3-arduino2.path=C:\Users\gr\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\4.9.2-atmel3.5.3-arduino2 -prefs=runtime.tools.avrdude.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.avrdude-6.3.0-arduino8.path=C:\Users\gr\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino8 -prefs=runtime.tools.avrdude-6.3.0-arduino17.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.avr-gcc-7.3.0-atmel3.6.1-arduino5.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.arduinoOTA.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.arduinoOTA-1.3.0.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -verbose C:\Users\gr\AppData\Local\Temp\untitled1374694073.tmp\sketch_apr24b\sketch_apr24b.ino
C:\Program Files (x86)\Arduino\arduino-builder -compile -logger=machine -hardware C:\Program Files (x86)\Arduino\hardware -hardware C:\Users\gr\AppData\Local\Arduino15\packages -tools C:\Program Files (x86)\Arduino\tools-builder -tools C:\Program Files (x86)\Arduino\hardware\tools\avr -tools C:\Users\gr\AppData\Local\Arduino15\packages -built-in-libraries C:\Program Files (x86)\Arduino\libraries -libraries C:\Users\gr\Documents\Arduino\libraries -fqbn=CONTROLLINO_Boards:avr:controllino_maxi -vid-pid=0000_0000 -ide-version=10812 -build-path C:\Users\gr\AppData\Local\Temp\58e9973bb6e2e908c6c199f5a9d39075.tmp\output -warnings=none -build-cache C:\Users\gr\AppData\Local\Temp\arduino_cache_972135 -prefs=build.warn_data_percentage=75 -prefs=runtime.tools.avr-gcc.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.avr-gcc-4.9.2-atmel3.5.3-arduino2.path=C:\Users\gr\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\4.9.2-atmel3.5.3-arduino2 -prefs=runtime.tools.avrdude.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.avrdude-6.3.0-arduino8.path=C:\Users\gr\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino8 -prefs=runtime.tools.avrdude-6.3.0-arduino17.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.avr-gcc-7.3.0-atmel3.6.1-arduino5.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.arduinoOTA.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -prefs=runtime.tools.arduinoOTA-1.3.0.path=C:\Program Files (x86)\Arduino\hardware\tools\avr -verbose C:\Users\gr\AppData\Local\Temp\untitled1374694073.tmp\sketch_apr24b\sketch_apr24b.ino
Using board 'controllino_maxi' from platform in folder: C:\Users\gr\AppData\Local\Arduino15\packages\CONTROLLINO_Boards\hardware\avr\3.0.2
Using core 'arduino' from platform in folder: C:\Program Files (x86)\Arduino\hardware\arduino\avr
Detecting libraries used...
"C:\\Program Files (x86)\\Arduino\\hardware\\tools\\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fpermissive -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -flto -w -x c++ -E -CC -mmcu=atmega2560 -DF_CPU=16000000L -DARDUINO=10812 -DARDUINO_AVR_MEGA2560 -DARDUINO_ARCH_AVR "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\cores\\arduino" "-IC:\\Users\\gr\\AppData\\Local\\Arduino15\\packages\\CONTROLLINO_Boards\\hardware\\avr\\3.0.2\\variants\\Controllino_maxi" "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output\\sketch\\sketch_apr24b.ino.cpp" -o nul
Generating function prototypes...
"C:\\Program Files (x86)\\Arduino\\hardware\\tools\\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fpermissive -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -flto -w -x c++ -E -CC -mmcu=atmega2560 -DF_CPU=16000000L -DARDUINO=10812 -DARDUINO_AVR_MEGA2560 -DARDUINO_ARCH_AVR "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\cores\\arduino" "-IC:\\Users\\gr\\AppData\\Local\\Arduino15\\packages\\CONTROLLINO_Boards\\hardware\\avr\\3.0.2\\variants\\Controllino_maxi" "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output\\sketch\\sketch_apr24b.ino.cpp" -o "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output\\preproc\\ctags_target_for_gcc_minus_e.cpp"
"C:\\Program Files (x86)\\Arduino\\tools-builder\\ctags\\5.8-arduino11/ctags" -u --language-force=c++ -f - --c++-kinds=svpf --fields=KSTtzns --line-directives "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output\\preproc\\ctags_target_for_gcc_minus_e.cpp"
Compiling sketch...
"C:\\Program Files (x86)\\Arduino\\hardware\\tools\\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fpermissive -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -MMD -flto -mmcu=atmega2560 -DF_CPU=16000000L -DARDUINO=10812 -DARDUINO_AVR_MEGA2560 -DARDUINO_ARCH_AVR "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\cores\\arduino" "-IC:\\Users\\gr\\AppData\\Local\\Arduino15\\packages\\CONTROLLINO_Boards\\hardware\\avr\\3.0.2\\variants\\Controllino_maxi" "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output\\sketch\\sketch_apr24b.ino.cpp" -o "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output\\sketch\\sketch_apr24b.ino.cpp.o"
Compiling libraries...
Compiling core...
Using precompiled core: C:\Users\gr\AppData\Local\Temp\arduino_cache_972135\core\core_CONTROLLINO_Boards_avr_controllino_maxi_0c812875ac70eb4a9b385d8fb077f54c.a
Linking everything together...
"C:\\Program Files (x86)\\Arduino\\hardware\\tools\\avr/bin/avr-gcc" -w -Os -g -flto -fuse-linker-plugin -Wl,--gc-sections,--relax -mmcu=atmega2560 -o "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output/sketch_apr24b.ino.elf" "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output\\sketch\\sketch_apr24b.ino.cpp.o" "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output/..\\..\\arduino_cache_972135\\core\\core_CONTROLLINO_Boards_avr_controllino_maxi_0c812875ac70eb4a9b385d8fb077f54c.a" "-LC:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output" -lm
"C:\\Program Files (x86)\\Arduino\\hardware\\tools\\avr/bin/avr-objcopy" -O ihex -j .eeprom --set-section-flags=.eeprom=alloc,load --no-change-warnings --change-section-lma .eeprom=0 "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output/sketch_apr24b.ino.elf" "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output/sketch_apr24b.ino.eep"
"C:\\Program Files (x86)\\Arduino\\hardware\\tools\\avr/bin/avr-objcopy" -O ihex -R .eeprom "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output/sketch_apr24b.ino.elf" "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output/sketch_apr24b.ino.hex"
"C:\\Program Files (x86)\\Arduino\\hardware\\tools\\avr/bin/avr-size" -A "C:\\Users\\gr\\AppData\\Local\\Temp\\58e9973bb6e2e908c6c199f5a9d39075.tmp\\output/sketch_apr24b.ino.elf"
Sketch uses 656 bytes (0%) of program storage space. Maximum is 253952 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 8183 bytes for local variables. Maximum is 8192 bytes.
An error occurred while uploading the sketch
C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf -v -patmega2560 -cwiring -PCOM3 -b115200 -D -Uflash:w:C:\Users\gr\AppData\Local\Temp\58e9973bb6e2e908c6c199f5a9d39075.tmp\output/sketch_apr24b.ino.hex:i

System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf"

Using Port : COM3
Using Programmer : wiring
Overriding Baud Rate : 115200
avrdude: ser_open(): can't open device "\\.\COM3": The semaphore timeout period has expired.

avrdude: ser_drain(): read error: The handle is invalid.

avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_send(): failed to send command to serial port
avrdude: ser_recv(): read error: The handle is invalid.

avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_send(): failed to send command to serial port
avrdude: ser_recv(): read error: The handle is invalid.

avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_getsync(): timeout communicating with programmer

avrdude done. Thank you.

the selected serial port
does not exist or your board is not connected

Also, I've tried re-uploading the LINX firwmare onto the device connected to COM3, but haven't managed to create a connection. There is often an icon next to COM3 when I try to upload the firmware (image attached). I think it means that the connection is busy, but I don't knwo what to do with that information.

I believe that the problem is an abrupt stop to a program disconnected the program and left my controller in some sort of VISA loop, but I haven't been able to reset it. I've tried restarting my PC multiple times, with the controller connected and disconnected, with an external power source and without one. I'm at the end of my wits with this problem.

Does anyone have any suggestions? Please let me know if any additional information would help you to help me.

↧

Read oscilloscope data in real time

April 24, 2020, 10:23 am

≫ Next: VS 2013 control instrument by ni488.2 （64)bit

≪ Previous: Error -1073807360 occurred at Property Node (arg 1) in VISA Configure Serial Port

My oscilloscope is "Rohde & Schwarz rtb2004", and I need to read the acquired data of the oscilloscope in real time on the PC (USB-TMC that I use). I have tried to send SCPI commands "SINGle" and "CHAN: DATA? "To perform “Single acquisition” mode, and loop multiple times. However, some sampling points will be lost between each acquisition. I try to use continuous sampling mode, but how can I read data while sampling is in progress? If I have to wait for the “Continuous acquisition” to finish before reading the data, is there a better way to obtain continuous real-time data through the oscilloscope? If I can get advice, I would appreciate it!

↧

VS 2013 control instrument by ni488.2 （64)bit

April 25, 2020, 7:16 pm

≫ Next: Keithley 2470 ID Query Failure

≪ Previous: Read oscilloscope data in real time

Before, I used to control the instrument with a file named gpib_32.dll. But this dynamic library is 32-bit. Now I want to compile a 64 bit program file. I downloaded the latest driver software of ni488.2 (version 19.5). Now I want to reference that dynamic library to compile a 64 bit program. I don't want to use visa dynamic library function. It seems that the dynamic library file named ni4882.dll is also 32-bit.

↧

Keithley 2470 ID Query Failure

April 27, 2020, 10:54 am

≫ Next: communication between two computers

≪ Previous: VS 2013 control instrument by ni488.2 （64)bit

Hello,

I'm connecting a Keithley 2470 SMU through LAN to my computer. I have the latest version of their driver and LabView 2018 SP1.

When I do an ID Query on the instrument through it's Initialize VI, provided by Keithley, occasionally I will get the following error.

-1073807312
VISA Read in Common Framework.lvlib:Keithley 2450.lvlib:Initialize.vi->
Common Framework.lvlib:Keithley 2400.lvclass:Initialize.vi->SMU Test.vi

VISA: (Hex 0xBFFF0030) User abort occurred during transfer.

The error does not occur every single time I call the Initialize VI with an ID Query request, maybe 1 out of 20 calls, the error will be thrown, it seems completely random when it happens. When I run the code without requesting an ID Query, everything works fine without any issues. This leads me to believe that something is happening with the VISA Read VI, but I can't figure out what.

Any help or info is appreciated. I've attached a picture of the VI in question.

↧

communication between two computers

April 27, 2020, 12:13 pm

≫ Next: Instrument Communication with GPIB through LabVIEW NXG

≪ Previous: Keithley 2470 ID Query Failure

hello, I'm getting a problem, can someone help me or give me an idea?
I need to run a VI on a computer 1 and run another VI on a computer 2, what is the best way for the computer to get information from computer 2 through labview? and how can i do that?

↧

Instrument Communication with GPIB through LabVIEW NXG

April 27, 2020, 4:22 pm

≫ Next: Win95/8 GPIB driver for unknown NI board (see pic)

≪ Previous: communication between two computers

Hello Everyone,

I'm new to LabVIEW in general, so please be patient.

I have an Agilent 34401A DMM, which I have the drivers for and have even made a couple simple VI's for, and an Agilent 33522A function generator. I downloaded the drivers for the function generator, but no new drivers appeared in the Hardware Interfaces tab. Package Manager shows that I installed the drivers, but I'm all "sad pandas."

Top is the Hardware interface, and the bottom is NI Package Manager

The good news is I can communicate with both the function generator and the DMM with the VISA test panel in NI Max, and I can see all my "installed" devices in System Designer, so I know LabVIEW can see them - happy dance. However, I have four more very old power supplies, and two of them don't appear to have drivers. All of them communicate over GPIB.

I assumed that communication was straight forward. So I tried the following and failed, but it looks pretty. My goal was just to take GPIB code that would produce a sine wave on output 1 of the function generator.

However, this didn't work, I got the following error. I did a google search on said error and that wasn't very helpful.The error code is -1073807195, and this isn't in the range of the VISA code I found, so not helpful.

If I can just communicate with my equipment with basic GPIB commands through LabVIEW I will be one happy dude.

Thanks for your time.

~Triston

↧

Win95/8 GPIB driver for unknown NI board (see pic)

April 29, 2020, 3:05 am

≫ Next: Sending string through SerialVISA Write

≪ Previous: Instrument Communication with GPIB through LabVIEW NXG

Hi,
Thanks in advance for any help.

A friend of mine owns a photo-processing business and I help out with IT/tech matters
He has come into possession of an unused Imapro QCR-35 film recorder, driven from a rather old Win95/8 computer via a GPIB board. The board is manufactured by Imapro with NI chips - please see images
Athough he has all the old software that came with the recorder we can not make it work as it relies on other pieces of kit (such as out of date densitometers) and the company Imapro is long gone.
The GPIB board in the computer appears to be functional but the driver is proprietary and when used with non-Imapro recorder software, (specifically WERP - an american program dedicated to driving image recorders via GPIB) does not appear to function.

We are thus trying to find a generic win95/8 driver for this board that will (hopefully) work with the imaging software to drive the recorder.

If more details are required please do contact me; Any suggestions very welcome and thanks again.

regards

Gary

↧

Sending string through SerialVISA Write

April 30, 2020, 12:25 pm

≫ Next: Im desperate Matlab - VISA- Siglent

≪ Previous: Win95/8 GPIB driver for unknown NI board (see pic)

Hi all,

I am trying to create a communication through serial between LabView and Arduino but I am having some problems.. Your help would be really appreciated.

I have attached the .VI to make my problem clearer.

I want to send a string to Arduino basing on what the user decides in the front panel through some radio buttons.

I've got a string indicator to know which is the string I am sending..

The problem I am facing is that actually it seems that I am not sending values at all and I am not getting why..

Do you have an idea of what is happening here?

Thank you so much in advance!!

↧

Im desperate Matlab - VISA- Siglent

May 1, 2020, 12:05 pm

≫ Next: Connect SRS SR830 DSP to LabVIEW via GPIB USB HS

≪ Previous: Sending string through SerialVISA Write

Hello everybody,
i have this problem: trying to upload arbitrary waveform into SDG6022x, but i just cant figure out the data format, anyone who could help me with that ? its 16bit 2's complement,

but signed integers doesnt work,
unsigned integers doesnt work,
if i devide data into 2 bytes it still doesnt work
or im doing something wrong ...

↧

Connect SRS SR830 DSP to LabVIEW via GPIB USB HS

May 1, 2020, 12:38 pm

≫ Next: NI myRIO-1900 drivers for windows 10 to use with Labview 2020 community edition

≪ Previous: Im desperate Matlab - VISA- Siglent

I have a lock-in amplifier that i want to connect to labview, it connects to the PC via GPIB USB HS. I believe neither the GPIB nor the SR830 are DAQ compatible devices. I have read NI's "Connecting Instruments via GPIB" page but when I get to searching for an instrument connected to the GPIB, my GPIB entry on the right has no drop down options.

NIMx capture.PNG

TLDR, what is the easiest way to hook up a GPIB USB HS deivce to Labview, I am not very tech savvy but I understand the basics of labview.

↧

NI myRIO-1900 drivers for windows 10 to use with Labview 2020 community edition

May 2, 2020, 7:44 pm

≫ Next: VISA commands and arguments - What are they?

≪ Previous: Connect SRS SR830 DSP to LabVIEW via GPIB USB HS

I have a myRIO-1900 and recently downloaded LabView 2020 Community Edition on my Windows 10 laptop. How do I make the two work. I cannot find the right drivers for this device. Any help is appreciated.

Haroon

↧

VISA commands and arguments - What are they?

May 6, 2020, 1:39 pm

≫ Next: PXI-8360 / PCIe-8361

≪ Previous: NI myRIO-1900 drivers for windows 10 to use with Labview 2020 community edition

I am trying to access a Siglent power supply using VISA32.dll. I have the commands that I need for the power supply. I can use them with the application that came with the power supply. BUT I want to write my own interface using Liberty Basic to control the power supply. Liberty Basic's interface to dlls is basically send command to dll followed by required arguments. Everything I am finding is "use this function" to do this or that for this language, with no definition of the function included. Is there some source that defines what the VISA32.dll expects for commands and arguments?

↧