NI Forum - Recent Threads

RE: Avnet Accelerometer (4030-002-120)

dougw — Fri, 10 May 2024 22:48:53 GMT

This sensor has analog outputs. Labview has all kinds of analog input capability. On the 2 g range the output is 1g per volt with 0.6 mV rms noise. So you would hit the noise floor at about 0.1 milli-g. To read this low (0.6 mV) Labview would need an A/D with about 14 bit resolution and accuracy.

Avnet Accelerometer (4030-002-120)

jimmy_almac — Fri, 10 May 2024 20:19:38 GMT

Is this avnet accelerometer (part number: 4030-002-120) compatible with labview? Also, how do I determine the minimum reading it is capable of?

Labview Community Edition 2024-Q1 released

Jan Cumps — Wed, 21 Feb 2024 19:03:07 GMT

Downloadable from https://www.ni.com/en/support/downloads/software-products/download.labview.html#521715

You need an NI account. And use the same account to download and activate.

If you have an existing community license, and activation fails, you may need to extend it here: https://www.ni.com/myni/products/en/

LabVIEW Course - We are in the process of judging

rscasny — Thu, 09 Nov 2023 14:30:19 GMT

I wanted to let everyone know that your final blogs are with the judges. We should have them scored and judged by early next week.

I have scored all the quizzes and the scores have been inputted on the status table.

Sincererely,

Randall

--element14 Community Team

Getting error when running with custom firmware on pico with labview

cbohra00627 — Sun, 29 Oct 2023 14:25:33 GMT

I am trying to create a labview driver for controlling the pi pico led. I went through the Digital Out Control.vi VI in pico_scpi_usbtmc_labtool and tried to replicate it for the led control. I took the blink example from pico-sdk examples directory and added the function to control led (i.e. gpio_put(LED_PIN, 1)) to the SCPI_DigitalOutput() function of gpio_utils.c file in pico_scpi_usbtmc_labtool. I created a new firmware with this change and loaded on pi pico. Now, whenever I do digital write HIGH, the led is turning on.

But when I tried to create a separate driver for led control with a separate SCPI command, I am getting some error while running the VI. The build was successful with my change and I loaded the firmware on the pico, but when I am trying to run my VI (snip attached below), I am getting the below error.

Code for led control:

led_utils.c:

led_utils.h

I have added the led executable and dir path to Cmakelists.txt and also added the INSTRUMENT_LED_OUTP_COMMANDS macro to scpi commands list in scpi-def.c

Am I missing something? Has anyone seen this error before?

RE: Getting error when running with custom firmware on pico with labview

cbohra00627 — Tue, 31 Oct 2023 17:55:19 GMT

Thanks everyone!🙂

RE: Getting error when running with custom firmware on pico with labview

cbohra00627 — Tue, 31 Oct 2023 17:54:12 GMT

Yes, after looking at the I/O trace, it became easier to identify the problem for me also.

RE: Getting error when running with custom firmware on pico with labview

Andrew J — Tue, 31 Oct 2023 17:50:57 GMT

Nope - I looked at the I/O Trace (then the image). You can see how the SCPI command has been mangled. In fairness, we may have spotted it by staring at the image long enough.

RE: Getting error when running with custom firmware on pico with labview

Andrew J — Tue, 31 Oct 2023 17:47:09 GMT

Great. Just to convince you - posting the NI I/O Trace helped us spot the error. If you can't spot the problem with breakpoints and probes, that tool is your go to debugging aid because it shows what is actually happening. Looking at the trace, you can see how the SCPI command has been mangled.

RE: Getting error when running with custom firmware on pico with labview

cbohra00627 — Tue, 31 Oct 2023 17:46:05 GMT

I think I used the wrong connector. The string should have been connected to "format string" but instead I connected it to "initial string". In the example VI, when I hovered over the top edge of the "format into string" block, it changed into resize cursor and I couldn't see the connector there and connected the string to the "initial string" connector instead in my VI. After connecting it to the correct connector, it is working fine.

RE: Getting error when running with custom firmware on pico with labview

Jan Cumps — Tue, 31 Oct 2023 17:45:58 GMT

I was wrong :) Andrew J found it by staring at the image

RE: Getting error when running with custom firmware on pico with labview

cbohra00627 — Tue, 31 Oct 2023 17:41:29 GMT

Its working now!

RE: Getting error when running with custom firmware on pico with labview

Andrew J — Tue, 31 Oct 2023 17:36:25 GMT

Really? If that works it is an excellent, truly excellent tip!

RE: Getting error when running with custom firmware on pico with labview

Jan Cumps — Tue, 31 Oct 2023 17:35:24 GMT

[quote userid="188728" url="~/products/devtools/ni-labview/f/forum/53896/getting-error-when-running-with-custom-firmware-on-pico-with-labview/216093"]Also, you'll need to sort out the \\n: that's a result of setting display codes[/quote]

If you use the Edit Format String option, you don't have to care about the "display codes" setting.

It's less confusing.

RE: Getting error when running with custom firmware on pico with labview

Jan Cumps — Tue, 31 Oct 2023 17:32:57 GMT

yes well spotted that's it ! The left top is initial string, top format string.

Wrong connector used.

RE: Getting error when running with custom firmware on pico with labview

Andrew J — Tue, 31 Oct 2023 17:32:05 GMT

Shouldn't that be into a terminal on the top of the Format block, not the left? It may just be the way the wire is shown but there is a terminal on the left there (intro string I think) and it's the wrong one so the default %s is tagged on to the end. Look at how the :Digital:OUTPUT:... to the left is wired. Also, you'll need to sort out the \\n: that's a result of setting display codes on when you already had the \n in the string - it's all a bit poor unfortunately, but I found the easiest was to delete the \\n then re-edit the string and just add \n. I think, it's been a while since I had the problem!

RE: Getting error when running with custom firmware on pico with labview

Jan Cumps — Tue, 31 Oct 2023 17:28:46 GMT

You can type the correct string there. Replace the %s with:

:LED:OUTPUT %s\n

then press OK,and test again

RE: Getting error when running with custom firmware on pico with labview

cbohra00627 — Tue, 31 Oct 2023 17:25:47 GMT

Its showing "%s" only.

RE: Getting error when running with custom firmware on pico with labview

Jan Cumps — Tue, 31 Oct 2023 17:23:03 GMT

yes.Right-click on the yellow format block, and select Edit Format String

What do you see (the one from my digital output as example)?

RE: Getting error when running with custom firmware on pico with labview

cbohra00627 — Tue, 31 Oct 2023 17:17:58 GMT

I ran the NI I/O trace, in that I am seeing error in alternate VISA read commands.

Then I ran the existing VI and my VI, I could see that there is some issue in the VISA Write command.

The VISA Write commands are different even if I am using similar format in the string.

The string in my command is not proper and I think that is causing the issue for the next run.

RE: Getting error when running with custom firmware on pico with labview

cbohra00627 — Tue, 31 Oct 2023 17:11:47 GMT

The existing examples are running fine but when I try to run my own VI, I am getting this error. The first run goes fine but the second run gives error. And this cycle continues.

RE: Getting error when running with custom firmware on pico with labview

Jan Cumps — Tue, 31 Oct 2023 16:51:17 GMT

(side note):

In the next version, the *IDN? will have the unique pico id:

The LabVIEW driver checks the first two partameters only, so it's backward compatible (and I tested it 🙂)

RE: Getting error when running with custom firmware on pico with labview

Jan Cumps — Tue, 31 Oct 2023 15:30:09 GMT

yes

It's a combination of a string ending in the terminator ";", a Concatete Strings (2nd top line), and a Line Feed Constant (second bottom line).

RE: Getting error when running with custom firmware on pico with labview

Andrew J — Mon, 30 Oct 2023 21:11:28 GMT

Useful. Is that in the String palette?

RE: Getting error when running with custom firmware on pico with labview

Jan Cumps — Mon, 30 Oct 2023 20:08:27 GMT

Found it back in the MCCDAQ driver I wrote for a road test:

So far for being consistent 🙂.