Termination character for serial write

Hi there,
(LabView 6.02 on Win2k)
Trying to communicate with a serial device I open a VISA-session on
COM1 and it all works fine except that I'm not able to configure a
termination character.
I've tried the as well as the VISA property
nodes. But I never get the desired termination characters (0xA or 0xD)
sent to the port.
What am I doing wrong?
Thanks in advance,
\Ulli.

finally I found out the following:
For the VISA session you have to setup (by means of property nodes)
not only and
but also set to "TermChar". Now everything
works fine :-)
Bernd-U. Seifert wrote:
> Hi there,
>
> (LabView 6.02 on Win2k)
> Trying to communicate with a serial device I open a VISA-session on COM1
> and it all works fine except that I'm not able to configure a
> termination character.
> I've tried the as well as the VISA property
> nodes. But I never get the desired termination characters (0xA or 0xD)
> sent to the port.
>
> What am I doing wrong?
>
>
> Thanks in advance,
> \Ulli.
>

Similar Messages

How can I define more than one termination character for RS-232 interface communication?

Hi,
I have to communicate through the PC's RS-232 interface with a microprocessor board. I am using the "Advanced Serial Write and Read.vi" out of the LabVIEW examples and it works on principle.
My problem is the termination character: It looks like I just can set one termination character, EITHER 0xA (so LF / newline) OR 0xD (CR / carriage return), but I have the need to react on various termination characters like "<CR> <LF> <CR> <LF> OK <CR> <LF>" or "<CR> <LF> <LF>"; which I would like to set in a control (this VI will be used in a TestStand sequence).
Is there a way to do that, so that I can set wichever termination character(s) I need? The property node in "VISA configure serial port" just accepts an unsigned integer, nothing else. Sure I can get it running with the timeout - but this is not very nice and extends testing time unnecessarily.
Thanks & Regards!
Regards,
gedi
Solved!
Go to Solution.

That would be for the write. The poster is asking about the read. For the read you will need to write your own read routine. You will basically need to use a loop and inside the loop use the VISA Bytes at Serial Port to see if there's any bytes available. Read that many bytes, and append them to a string that you build up in a shift register. After concatenation check to see if you've got the termination characters. If so, the read is done. Fairly simple. Be sure to turn off the termination character enable in the VISA Configure.

Termination character for RS232 Instrument

I have an instrument that I am trying to communicate with via RS232. I am having a difficult time figuring out how to write a command to the instrument using the VISA write VI. I am able to successfully communicate with the instrument using a software program called Terminal (similar to hyperterminal). A typical command starts and ends with ^m in Terminal. For example, here is the command ^md01v00,00^m that returns the heat rate. How do I write this command in the VISA write VI? Is the ^m an unprintable character in LabVIEW that is represented in some other format?
Attachments:
Screen Shot.jpg ‏30 KB
test.vi ‏26 KB

Hi SumTumWong,
I'm thrilled to hear that you resolved your serial communication issue. As for your framing error that occurs, this is a common issue and we have a Knowledge Base article that explains what this error in full and how to resolve it. The most common reason why this error occurs is that your serial port and device are configured to use a different settings. The article shows how make sure that the settings of both your serial port and device are configured properly using Measurement & Automation Explorer (MAX). Let us know if you have any more questions. Have a great day!
Regards,
Todd Venable
National Instruments
Applications Engineer
NI Prototyping Community

Serial port termination character status?

Hello,
I need to read a message from a serial port and I'm having some problems. I used the advanced serial communication example and came up with the attached program. Everything works perfectly fine except for the fact that if no message is sent for 10 seconds as designed the serial read outputs an error. I know normally I can check to make sure there are bytes at the port before I do a read operation which solves this problem. However, when using the buffer to terminate the read once a termination character is provided the bytes at port property always returns 0 so I can't use this as a conditional for reading the port.
Is there a way to prevent the serial read from timing out in the attached program? Thank you.
Attachments:
serial_buffer.gif ‏19 KB
serial.vi ‏15 KB

Let me maybe give a bit more details about the application. I want to be able to get any amount of characters as a string that someone inputs in to the serial port. This will be a computer so I can expect the commands to usually be valid but I want to provide some additional redundency incase a person at a terminal is writing commands. The commands might be "measure 110" or it might be "set 23 34". So the amount of bytes being sent will depend on the command. I used 1000 as the byte count on the read just to provide as much room as possible, setting it to 100 doesn't really make a difference in this application, the same thing happens. If someone starts typing in a terminal "measure 110" (for example) but forgets to hit enter for the termination character the program will time out since the error cluster is connected to the stop button of the loop. When this happens the entire program needs to be restarted. Not really ideal.
If I disconnect the error cluster from the stop button I noticed it works perfectly fine. After 10 seconds of the terminator character not being entered the buffer clears and the loop simply restarts. What I worry about is if there is some other fatal error (such as not being able to connect to the serial device) that the program will keep running. Is this something I even need to worry about?
Attached is a screenshot of my latest program which works great but like I said I'm just worried about not wiring the status from the error cluster to the stop button since that seems to be what I've always been taught to do. If I wire the byte count to the number of bytes property it will only collect the number of bytes I set, since this will vary based on the command that won't really work in this application.
Attachments:
serial_buffer.gif ‏20 KB

Serial Recieve with termination character

Hi All,
I have developed a seqence fileto transmit data on the serial port and loop back to recieve the data on reciever of same port. I'm transmitting "Test
Serial" (Note: I'm not transmitting "Test\\rSerial") and recieving the data with termination character "carriage return".I'm using ASCII value 13 for the carriage return,but the recieve is not terminating on carriage return.
It seems Teststand is not able to recognize "13" or "\r" is seen as 2 character.
I'm attaching the sequence file for your perusal.It would be great if somebody can suggest me ways to make this work.
Thanks in advance.
Regards
VDC
PS: IVI serial driver need to be installed.You need to select Serial driver in device driver installation
Attachments:
SerialReadWrite_Term.seq ‏23 KB

HI,
I tried to find this dll, where is it located?
If this is using "IVI" then you could see every action in NI-Spy !
I watched you code. Another thing you could try is disabling the caching. Try Cache=0
now data shold send very time to your device by the IVI engine
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

HT204347 Thanks, the write-up was informative, But it do not answer for my question, that is where to look for serial # on my Macbook Pro Mid 2010 White Unibody Core 2 Duo 2.4 GHz 13.3"? Its not on bottom-case and the above article does not mention this m

Thanks, the write-up was informative, But it do not answer for my question, that is where to look for serial # on my Macbook Pro Mid 2010 White Unibody Core 2 Duo 2.4 GHz 13.3"? Its not on bottom-case and the above article does not mention this model?

Click on the Apple and then on about this Mac. In the new window, click on the "version 10.9.2" until you see the serial number displayed.

Cannot write anything when terminal asks for password

I try to uninstall a F-secure product with uninstaller but when prompted about password I cannot write anything there

Cannot write anything when terminal asks for password
When using sudo in Terminal, which requires a password, typing the password will not show as asterisks. It does not visually echo the keystrokes, but it is accepting them.
Just carefully type the password, and press Return when finished,

PDA (Pocke PC) - Serial Write Timeout

Hello List,
I am developing serial routines to communicate with external hardware. In many cases, XON/XOFF flow control is used.
I have configured my PDA device to write out a large file. During the transmission, I use my development computer to monitor the transmission. During the transmission, I can send XON/XOFF characters to the PDA. If I send an XOFF, it will "pause" until I send an XON character. It works great unless I wait for more than about 3 seconds. If the PDA is forced to wait for more than 3 seconds, the transmission is terminated with an error. However, if I send an XON character, before the 3 seconds delay, it continues the transmission and no error occurs.
It seems that a 3 second timeout is being enf
orced within the routines but I have not been able to determine if I have control (within the PDA Serial Routines) over the timeout variable. Personally, I would like the timeout to be indefinite unless I want to enforce one.
FYI: Based on industrial experience, for very large files, delays during the transmission of several minutes may be necessary.
TIA,
Guy

Hello,
I apologize for the delay in responding to your post. You are having a timeout issue when using software flow control (XON/XOFF) to transfer data between a PDA and a host computer, right? Are you getting error code 7 when the PDA times out? I was able to duplicate this issue here. This error code is a timeout error and it means that not all bytes have been sent. I spoke with members of the R&D team and they know about the problem. While they were unable to offer a formal solution at this time, they did provide a workaround which I hope works for you.
Put a while loop around the serial write VI on the PDA.
Continue the while loop until there is no longer an error code 7 (i.e. until all bytes have been sent).
Essentially, this will ignore the repeated timeouts from the serial write VI. You can manually add a timeout mechanism by obtaining the time before the loop and checking it during the loop. However, you mention an infinite timeout is acceptable in which case no additional code is necessary.
I have attached a couple of VIs that implement serial communication using XON/XOFF flow control and that use the above workaround. Please let me know if this solution works for you. If not, can you provide some additional details such as the error code and if the timeout is happening on the PC side or the PDA.
Happy coding,
Grant M.
National Instruments
Attachments:
Serial_XonXoff_(Host).vi ‏55 KB
Serial_XonXoff_(PDA).vi ‏68 KB

VISA Flush I/O Buffer doesn't work on my Serial Write and Read VI

Hello,
I've been working on a serial interface .vi that communicate with simple GPRS/3G modems via AT commands.
This VI is working very well except when its used repeatedly:
Even if I use "VISA Flush I/O Buffer" or "VISA Clear" or clear the "Response" control string, the VISA Read keeps delivering the response concatenated after previous responses. Can you spot the bug in my VI?
I've had searched this forum for smiliar topics, but none of them were related.
Thanks,
Antonio

RavensFan escreveu:
You are going to keep seeing previous messages because you are storing them in a string in the feedback node. It doesn't matter what you do with the serial port or its buffer, you've created your own buffer with the feedback node.
Well... and it's working fine! Thank you very much RavensFan!
I started develloping this code as my first steps into Labview, and it's based on previous and bad programmed serial.vi that my coworker had done.
Right now, I have less than 3 months of LV experience and, believe it or not, I'm the company's specialist.
It's hard to solve all these little bugs!
Why are you using VISA events? I don't find them very commonly used, and I don't see where you are using them anywhere else.
Why are you using Bytes at Port? I don't see where you are controlling the speed of your loop, so you probably wind up reading the serial port a byte at a time or something like that.
Where are you sending your commands?
Why don't you use the termination character to determine when to stop reading on a VISA read so it will responde quickly, but guarnatee you get a complete message.
I used VISA events because I wanted to get rid of the constant "wait for X ms" function between read and write. This way I read the answer at the time it arrived. I can't remember why I used Bytes at Port, probably because the program required it. I got to take a look on this later.
The commands are sent through the Command control.
And about using the termination character, It's not garanteed that the device will always respond with a termination character. But I will talk again with the hardware team about this.
Again, thank you!

Termination character enable is FALSE but active

When opening a new VI and starting to write code (in the other words, no special initialization is done to the serial port settings, as yet), the Term Char Enable indicates FALSE. The reads do get terminated with \n (\x0A). After a little while, I found in the support that actually one needs to check a different attribute (ASRL End In), in order to have the correct picture. Is this behaviour by design (??!!!???), or is it a bug?
Sincerely,
Albert Lysko

In VISA Configure Serial Port, setting Enable Termination Char to true (the default mode) does two things. It sets the VISA Message Based Settings property Termination Character Enable to true, and the Serial Settings property Serial End Mode for Reads to termchar. The serial end mode for writes is not set in the function and if you want to terminate each write operation with a termination character, you have to set Serial End Mode for Writes to termchar.

Send/receive data without a terminating character

I am trying to use the visa driver to send hex data over a serial port. I have tried to disable terminating characters but when I read from the port the trasnmission still terminates with a 0x0A character. How can I send/receive data without a terminating character???

You need to call viSetAttribute with VI_ATTR_ASRL_END_IN set to VI_ASRL_END_NONE. In LabVIEW, use a write property node with the Serial End In mode set to None (0).
Dan Mondrik
Senior Software Engineer, NI-VISA
National Instruments

Termination character

Hello,
I'm communicating with an 20 years old optical spectrum analyzer with GPIB connection using VISA.
I having trouble reading the entire data. I've try to use the termination character options to solve this but my instrument use both line feed and EOI termination codes.
I've found this help text: http://www.ni.com/white-paper/4256/en/
but could understand it to the end.
what is the symbol accepting the arrow symbol at and zero constant at the end? where should I put this property node in case I want to read many bytes ending with the above characters? before VISA - WRITE? after VISA read? and how can I combine two termination character? how do I represent two EOI?
thanks, Avishay

Specify too many bytes to read and the visa read wil stop on the first end character or eoi that appears.
For two eoi's read twice.
greetings from the Netherlands

Termination character enable

I am connected to hardware via an RS-232 cable and am using VISA’s to request and read information from memory addresses. When I encounter a 0x0a (hex) in memory, the VISA Read stops reading because it thinks it has read the termination character. This only happens when a 0x0a is encountered, all other characters from 0x00 to 0xff are read in correctly (provided there isn’t a 0x0a in the location).
I have set the Termination Character Enable property node to FALSE and it doesn’t seem to help (Ver 6.0.2). Any help on disabling the Termination Character would be appreciated.
Thanks,
DH

I would think that setting the Termination Character Enable to false would prevent this. Maybe something else is turning it back on. If you use the VISA Configure Serial Port.vi (In instrument I/O>>Serial) it will turn this setting back on. So make sure you turn it off after any of these functions. One other thing that have done is set the Termination Character to 0x00, although I'm not sure what would happen if you got a 0x00 (NULL?) back from the port. Also check for other functions that may alter these settings after you set them.
Hope this helps!
Brian

Error while scanning for Serial-ATA devices.

There was an error while scanning for Serial-ATA devices. I'm not sure how to trouble shoot this. I believe a secondary drive in bay 2 died.

I also have just began to hit this issue.
I have 4 2T enterprise class WD drives in a raid 1+0 (or was it 0+1) config.
Device Model: WDC WD2002FYPS-01U1B1
One disk (disk0 in bay 2) keeps disappearing. Completely. /dev/disk0 and /dev/rdisk0 vanish.
If I look at "about this mac" / "More Info" / "Serial-ATA" I get the "error while scanning ...".
If I reboot, the offending disc comes back and the raid volumes start rebuilding.
The SMART status is (reported to be) fine.
I use the 'smartmon' tools and look at the extended SMART status and the values of the counters all looks the same as the other drives. I can run an extended offline test, which takes forever to execute. disk 1 and 3 eventually finish with success (it writes this status into a SMART log area on the disc).
Disk 2 and 0 take longer. I image this is because 2 is being read to resilver 0. Currently, I am running with disk0 absent again, and disk 2s test did not complete. It claims it was aborted by the host, so I imagine the one on disk0 will claim the same after I reboot.
My system is under extended AppleCare until 16 Jan 2011, so if I can determine that this is a disc controller error, I can get it fixed. The drives have a 5 year warrantee, and are less than 1yr old, so they are covered. I just need to figure out what the issue is.
I will now reboot and recover disk0 and see if perhaps there is anything recorded in the SMART log.
There is nothing in kernel.log specific to disk0. I include the log extract here for posterity. The "speed" volume is not raid 0+1, just striped, which is why it gets aborted.
Dec 21 23:30:26 8way kernel[0]: AppleRAID::restartSet - restarting set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D).
Dec 21 23:30:26 8way kernel[0]: AppleRAIDMirrorSet::rebuild complete for set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D).
Dec 22 04:17:22 8way kernel[0]: AppleRAID::restartSet - restarting set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76).
Dec 22 04:17:22 8way kernel[0]: AppleRAIDMirrorSet::rebuild complete for set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76).
Dec 22 05:23:16 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:23:30 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:23:44: --- last message repeated 1 time ---
Dec 22 05:23:44 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:24:14: --- last message repeated 4 times ---
Dec 22 05:24:19 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:24:56: --- last message repeated 2 times ---
Dec 22 05:24:56 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:25:17: --- last message repeated 1 time ---
Dec 22 05:25:17 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:25:31: --- last message repeated 1 time ---
Dec 22 05:25:31 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on EB932B0E-8476-480C-BBD4-53A9A77D9FEF
Dec 22 05:25:45: --- last message repeated 1 time ---
Dec 22 05:25:45 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:26:15: --- last message repeated 2 times ---
Dec 22 05:26:21 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:26:51: --- last message repeated 4 times ---
Dec 22 05:27:12 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:27:33: --- last message repeated 1 time ---
Dec 22 05:27:26 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:27:40: --- last message repeated 1 time ---
Dec 22 05:27:40 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:28:24: --- last message repeated 1 time ---
Dec 22 05:28:24 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:28:39: --- last message repeated 1 time ---
Dec 22 05:28:39 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:29:14 8way kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002ca detected for set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76), member 3C6E9EA4-831A-4
57A-8CA5-6E7E9CBEED25, set byte offset = 222462894080.
Dec 22 05:29:14 8way kernel[0]: AppleRAID::recover() member 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25 from set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76) has been marked
offline.
Dec 22 05:29:14 8way kernel[0]: AppleRAID::restartSet - restarting set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76).
Dec 22 05:32:38 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:33:22: --- last message repeated 1 time ---
Dec 22 05:33:22 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:34:06: --- last message repeated 1 time ---
Dec 22 05:34:06 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:34:53: --- last message repeated 1 time ---
Dec 22 05:34:53 8way kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002ca detected for set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D), member 9722C38E-DFF9-4
68F-8DE5-809432493168, set byte offset = 35194773504.
Dec 22 05:34:53 8way kernel[0]: AppleRAID::recover() member 9722C38E-DFF9-468F-8DE5-809432493168 from set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D) has been marked
offline.
Dec 22 05:34:53 8way kernel[0]: AppleRAID::restartSet - restarting set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D).
Dec 22 05:37:24 8way kernel[0]: AppleAHCIDiskQueueManager::setPowerState(0x13d64500, 2 -> 1) timed out after 100113 ms
Dec 22 05:37:44 8way kernel[0]: Failed to issue COM RESET successfully after 3 attempts. Failing...
Dec 22 05:37:44 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002be on EB932B0E-8476-480C-BBD4-53A9A77D9FEF
Dec 22 05:37:44 8way kernel[0]: AppleRAID::recover() member EB932B0E-8476-480C-BBD4-53A9A77D9FEF from set "speed" (190EC75B-C702-4481-ABCF-8C5A0D54BBE0) has been marked
offline.
Dec 22 05:37:44 8way kernel[0]: AppleRAID::restartSet - restarting set "speed" (190EC75B-C702-4481-ABCF-8C5A0D54BBE0).
Dec 22 05:37:44 8way kernel[0]: disk4: media is not present.
Dec 22 05:37:59 8way kernel[0]: speed::terminate(kIOServiceSynchronous) timeout
Dec 22 05:37:59 8way kernel[0]: AppleRAID::completeRAIDRequest - underrun detected, expected = 0xa000, actual = 0x9e00, set = "speed" (190EC75B-C702-4481-ABCF-8C5A0D54BB
E0)
Dec 22 05:37:59 8way kernel[0]: disk4: data underrun.
Dec 22 05:37:59 8way kernel[0]: jnl: disk4: dojnlio: strategy err 0x5
Dec 22 05:37:59 8way kernel[0]: jnl: disk4: end_transaction: only wrote 0 of 40960 bytes to the journal!
Dec 22 05:37:59 8way kernel[0]: disk4: media is not present.
Dec 22 05:38:00 8way kernel[0]: jnl: disk4: close: journal 0x13f34e04, is invalid. aborting outstanding transactions

Hidden Bluetooth settings in 10.9 for serial

The new OS 10.9 Maverick hides the Bluetooth settings, I am no longer able to add new serial ports for my Bluetooth devices in order to connect to them via the screen command (screen /dev/tty.Bluetooth...).
I'm interfacing my phone with my computer and need a serial port to communication, this needs to be set up in the Bluetooth settings. As of the new OS it has been dumbed-down so much that these settings do not exist anymore. Funny thing is when you search for "serial" in the system preferences window it will only highlight the Bluetooth settings:
Please give back these settings, I'm no longer able to work with my computer because of this.

I'm hoping the original poster has found some way to remedy this situation since this is an old topic. I do wonder how far you are all getting into the process, from what I can tell once you pair a device & connect to it you get new entries under /dev. One for a tty and one for a call up device (cu…). You may have others depending on the device capabilities.
ls /dev
/dev/cu.DeviceName-SerialPort
/dev/tty.DeviceName-SerialPort
Are they not the connections you are looking for? I'm not sure that you need to see the serial ports in the GUI to be able to use them via Terminal.
Please tell me what I'm missing.

Termination character for serial write

Similar Messages

Maybe you are looking for