multi line

[AliMolaei]

Hi


How can I see the full text being read in the read buffer?

[dsb@NI]

Please provide more information to help us help you!

Give the topic a descriptive title.
In the description, provide enough context for us to know what you are trying to do and where you are stuck.

Attach your VI. Make sure to save values as control defaults.
What are you expecting?
What are you seeing?

What have you tried so far?

[altenbach]

Sparse questions can only get sparse answers.

Connect an indicator and make it large enough for the contents. If you expect non-printable character, change the display to hex or \-codes.

[AliMolaei]

I uploaded VI;

I want to control a DC motor using an Arduino and a DS18B20 sensor, and display the motor speed in LabVIEW.
Now, in the video whose link I attached, you can see that only a limited portion of the sent text is displayed.

The challenges I’m facing are:

1. How can I display all the text inside a text box?
2. Can I control the motor’s RPM using a motor driver to make my project more advanced, and how can I display the motor’s **RPM** in LabVIEW?

https://filebin.net/3okw9wk72h9qnezx/MaybeFinally%20TF.vi%202025-11-17%2000-33-49.mp4

[dsb@NI]

What happens when you increase byte count?

[Bob_Schor]

Many long-time LabVIEW users (with lots of experience) might not have the "latest version" installed, hence cannot open your VI.  Please open it in LabVIEW 2025 and then (on the File Menu) "Save for Previous Version" and specify, say, LabVIEW 2021 or 2019.

I'm grateful for the warning FileBin pops up, so I immediately did not download your mp4 file.  You can attach a "picture" (.png) file that illustrates the "limited portion of the sent text" (or just type the "expected text" and "actual text").

Bob Schor

[Xonmyth]

Since I could open it, I saved it for 2019.

I am not the OP.

[Bob_Schor]

What is generating the information you hope to be reading with VISA?  Is it a "serial line" interface?  That is to say, if you were to examine what your device (have you told us anything about this device, such as it's an Arduino or something we'd recognize?) and look at all the characters in the Read Buffer, would they be things that look like responses to commands, or data streams in Human-Readable Text strings?  [In my experience, most of the time, the answer to that question is "Yes".]

If that's the case, you want to not use the "VISA" VIs on the Instrument I/O Palette, but the VIs on the "Serial" sub-Palette. 

This VI is called "VISA Configure Serial Port.  You use it to set the Baud Rate and other serial parameters for your sending device.  It also (by default) is set so when your device sends an Ascii string to you and terminates it with something like <CR><LF>, a VISA Read specifying a ridiculous number of bytes (most often 1000, though I use 1024 "just because"), the Read will read only up until it sees the terminating sequence.  [If you search the Forum, you can find an excellent talk by @Crossrulz presented at NI Week a few years ago that explains the right way to do serial communication].

Replace the rest of the "VISA" VIs on your Block Diagram with their corresponding versions from the Serial sub-Palette, and do NOT specify a Byte Count (as I mentioned at the end of the previous paragraph].  The only thing you need to worry about is when to stop reading lines of text from your device -- it should "tell you" when it's time to stop reading.

However, some of what I've said may be completely wrong -- you never told us what instrument is sending you commands, never provided a manual of commands this routine needs to attend to.  I notice that you are sending a string "1" or "2", no terminating character, so my assumption above that this is the type of VISA device I've been programing for a decade or so might not be doing "serial VISA".

Makes it hard to help you.  We are reduced to "guesswork" ...

Bob (Puzzled) Schor