Hi All, I would like to explain my program first, I wrote a program where trying to establish communication between Labview and microcontroller. By this program I am trying to select the serial com port automatically. I have attached VI which clearly shows the logic which I have used. Labview checks each and every port which are working on the computer, visa write 's' and waits to read 's' . If 's' is recived then loop ends here and diplays the right port where the microcontroler is connected. Otherwsie it continues to search...... every logic is working I tried to check for all cases it is working but it is only working in Highlight mode. When I try to run in normal mode the loop is continuously running not able to read microcontroller properly. I have checked for the Baud rate,no of bytes ect.,,, tried out somany ways....but still it is not working. I have checked with all the delays but i couldn't figure where the problem is coming from. I don't have much expirence with Labview......Can any one please help me to solve this problem? ThankyouDeepthi

@Deepthi23 wrote:Thankyou somuch @Daikataro I have tried out the code you have posted. It is working fine in the Highlight mode as before but showing a wrong resourcename as out put and not reading 's' in the normal mode. I couldn't find out the problem. I need to run the program without stopping untill it finds a right port without exiting the program but this code will not run the program untill we find the right port. Do you have any mopre suggestion for the code? Please help to find the solution.... May be my next update will 3 days later as I am in holiday......I am sorry!!! What do you expect? Bytes at serial port will return the numbers of bytes in the buffer at the moment it is executed. Not the number of bytes the device might send or not send in the future.In Highlight node there are many 100ms between the time VISA Write sends the command and Bytes at Serial Ports deterimines the number of bytes received in the receive data buffer by the COM port driver. When executing normally there is not even 1ms between the two and that is for most serial instruments not even enough to decode the command and decide what to return, and then returning the data takes even longer depending on the baudrate (your 9600 baudrate means at least 1ms per character also for sending, so from the moment your VISA Write returns, which only places the data into a buffer and doesn't wait until the data is actually sent to the device, it takes already at least 1ms before the actual character is transmitted to the device, some more ms for the device to decode the command and decide what to do and then again 1ms before the first character is received at your computer). LabVIEW can in that time execute Bytes at Serial Port a few 100 times and do in parallel some number crunching and graphic calculations too. And again my pet topic about VISA communication: DO NOT USE "Bytes at Serial Port" EVER. It is in 99.9% of the cases not only not necessary but even outright wrong! If you believe it is necessary think again, chances are almost 100% that you are wrong especially if you haven't already written a few 100 instrument drivers in LabVIEW or even just using VISA.

You're kind of convoluting the code too much. You can simplify it to just attempting to initialize the serial port which, if it is not the correct port, will merely return an error which you clear and continue the search. If it manages to make a correct connection, it sends S and tries to read back an S which, if succesful, sends a true to the stop condition and delivers the correct port and the read S. EDIT: I forgot to add a for loop instead of a while, so it will take the auto-indexed input and attempt once with each iteration.

Maybe your delays are still too short or maybe you need a delay elsewhere. Why are you configuring the serial port with every iteration of the loop? You only need to do that if one of the parameters changes. Do they ever?. While you are at it, try to eliminate all these "equal TRUE" Rube Goldberg code fragments. All it returns is the original boolean so a simple wire would be equivalent. Keep it simple! 😄

I see a lot of possible race conditions in your code and no delay between writing an "S" and reading the port. Also don't do this: Do it this way: You may have to invert your logic too.

Return to Home Page
Toggle navigation

Solutions

Industries

Academic and Research
Aerospace, Defense, and Government
Electronics
Energy
Industrial Machinery
Life Sciences
Semiconductor
Transportation

Product Life Cycles

Design and Prototype
Validation
Production

Focus Areas

5G and 6G Technology
ADAS and Autonomous Driving Testing
Electric Vehicle Test
Lifecycle Analytics
Radar and Electronic Warfare
Space Launch and Exploration
Validation Lab Innovations

See our approach to solutions

Get a Helping Hand

From troubleshooting technical issues and product recommendations, to quotes and orders, we’re here to help.

Products

Software

View All Software

LabVIEW
TestStand
FlexLogger
SystemLink
DIAdem
VeriStand
OptimalPlus GO

Software Suites

LabVIEW+ Suite
HIL and Real-Time Software Suite
Circuit Design Suite

SERVICES

View All Services

Repair Services
Calibration
Training Courses

HARDWARE

View All Hardware

Data Acquisition and Control

Learn About DAQ
CompactDAQ Bundles
Multifunction I/O
Voltage
Digital I/O
Temperature
Sound and Vibration
Current
Strain, Pressure, and Force
CompactDAQ Chassis

Electronic Test and Instrumentation
PXI Instrument Bundles
GPIB, Serial, and Ethernet
Switches
Oscilloscopes
Digital Multimeters
Source Measurement Units and LCR Meters

Wireless Design and Test

Software Defined Radios
RF Signal Generators
Vector Signal Transceivers

Application-Specific Systems

Semiconductor Test System
Power Electronics Test Systems

Accessories

Power Accessories
Connectors
Cables
Sensors

FEATURES

Entry-Level DAQ

RESOURCES

Advisors
Distributors

See all products

PC-Based Systems

Benchtop Measurement and Test

CompactRIO

Distributed Measurement and Control

PXI

High-Performance Test

Software

Systems Engineering Software

Perspectives

Perspectives showcases how NI sees what’s next in the world of test and technology.

View all articles

Charting the Course for Test Development with LabVIEW

LabVIEW remains key in test, promising speed, efficiency, and new features with NI’s investment in core tech, community, and integration.

Read our featured article

Support

Resources

View All Support Resources

Software Downloads
Register and Activate
Product Documentation
Release Notes
Online Training
KnowledgeBase
Code Examples

Request Support

You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.

Open a service request

Popular Software Downloads

See all Software Product Downloads

LabVIEW

Multisim

Academic Volume License

Popular Driver Downloads

See all Driver Software Downloads

NI-DAQmx
Provides support for NI data acquisition and signal conditioning devices. 
NI-VISA
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments. 
NI-488.2
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.

Community

About

My Account

Account

Cart

Solutions
- Back
- Industries
- Academic and Research
- Aerospace, Defense, and Government
- Electronics
- Energy
- Industrial Machinery
- Life Sciences
- Semiconductor
- Transportation
- Product Life Cycles
- Design and Prototype
- Validation
- Production
- Focus Areas
- 5G and 6G Technology
- ADAS and Autonomous Driving Testing
- Electric Vehicle Test
- Lifecycle Analytics
- Radar and Electronic Warfare
- Space Launch and Exploration
- Validation Lab Innovations
- See our approach to solutions
Products
- Back
- Software
- View All Software
- LabVIEW
- TestStand
- FlexLogger
- SystemLink
- DIAdem
- VeriStand
- OptimalPlus GO
- Software Suites
- LabVIEW+ Suite
- HIL and Real-Time Software Suite
- Circuit Design Suite
- SERVICES
- View All Services
- Repair Services
- Calibration
- Training Courses
- HARDWARE
- View All Hardware
- Data Acquisition and Control
- Learn About DAQ
- CompactDAQ Bundles
- Multifunction I/O
- Voltage
- Digital I/O
- Temperature
- Sound and Vibration
- Current
- Strain, Pressure, and Force
- CompactDAQ Chassis
- Electronic Test and Instrumentation
- PXI Instrument Bundles
- GPIB, Serial, and Ethernet
- Switches
- Oscilloscopes
- Digital Multimeters
- Source Measurement Units and LCR Meters
- Wireless Design and Test
- Software Defined Radios
- RF Signal Generators
- Vector Signal Transceivers
- Accessories
- Power Accessories
- Connectors
- Cables
- Sensors
- FEATURES
- Entry-Level DAQ
- RESOURCES
- Advisors
- Distributors
- See all products
Perspectives
Support
- Back
- Resources
- View All Support Resources
- Software Downloads
- Register and Activate
- Product Documentation
- Release Notes
- Online Training
- KnowledgeBase
- Code Examples
- Popular Software Downloads
- See all Software Product Downloads
- LabVIEW
- Multisim
- Academic Volume License
- Popular Driver Downloads
- See all Driver Software Downloads
- NI-DAQmx
- NI-VISA
- NI-488.2
- Request Support
- You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required. Open a service request
Community
About
Contact Us
Account

Home Community Discussion Forums Most Active Software Boards LabVIEW Topic

LabVIEW

Register
·
Login
·
Help

cancel

Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

Search instead for

Did you mean:

Topic Options

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Float this Topic for Current User
Bookmark
Subscribe
Mute
Printer Friendly Page

All Forum Topics
Previous Topic
Next Topic

Previous
- 1
- 2
- 3
Next

labview program working in highlight mode and not working in normal mode

Solved!

Go to solution

Re: labview program working in highlight mode and not working in normal mode

altenbach

Knight of NI

‎05-18-2016 12:34 PM - edited ‎05-18-2016 12:35 PM

Options

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report to a Moderator

@riotimus wrote:

Do you know why ???

Not unless you show us what you are doing.

If you use paths relative to the VI, you need to adjust things because the hierarchy in an executable is different (details). So this is my first guess.

LabVIEW Champion.