LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Unwanted data strings in settings, for connectivity to serial port.


@JÞB wrote:

@billko wrote:

Are you saying that you query the iinstrument through the serial port to get the serial port settings???  This can't have a happy ending...


No, this problem is with this config file.  Has nothing to do with a serial port other than the file should contain some port settings.  The Data in the file is getting out of whack.

 

UNDERSTANDABLE since the OP is opening the file with a depreciated function and writing keys to it with a different API.

 

Replace that open!  then clean up the file  youll be fine


Got it.  Thanks, I was having trouble understanding the problem.  🙂

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 11 of 14
(436 Views)

I have updated the "open Cong files" in the Project manager data hoping that it updates all incidences where "Write Settings INI.Vi" Occurs. 

 

But this problem still occurs. 

 

If I ran this VI before updating the OPEN cong files would that have caused any data strings to get out of wack? 

 

I have some VIs that have the little red dot next to the input terminal, means that my data has the wrong representation. Would that be causing my strings to get out of order?

0 Kudos
Message 12 of 14
(426 Views)

So far, you have offered the equivalent of calling up your new family doctor on the phone and telling him/her, "Doc, I think I hurt somewhere, maybe above the knee. I took my temperature, and blew my nose, but my snot is not yellow. I've already sent you a picture of my handkerchief in an email, before and after I blew my nose. There is a pimple on my forehead, and I did not stay in a Holiday Inn Express last night. Will you prescribe me some medicine to fix what is wrong?"

 

Now, if you would come in to the office (attach a non-working sample of your code to poke and prod), possibly someone could help you. But no one here is clairvoyant, or at least I have not heard anyone claim to be.

 

Cameron

 

 

 

To err is human, but to really foul it up requires a computer.
The optimist believes we are in the best of all possible worlds - the pessimist fears this is true.
Profanity is the one language all programmers know best.
An expert is someone who has made all the possible mistakes.

To learn something about LabVIEW at no extra cost, work the online LabVIEW tutorial(s):

LabVIEW Unit 1 - Getting Started</ a>
Learn to Use LabVIEW with MyDAQ</ a>
0 Kudos
Message 13 of 14
(411 Views)

camerond wrote:But no one here is clairvoyant, or at least I have not heard anyone claim to be.

 

Cameron

 


Ben proved it once or twice

see posts 6 & 7 of this thread https://forums.ni.com/t5/LabVIEW/tab-activate-inactive-controls/m-p/1092078/highlight/true#M483157


"Should be" isn't "Is" -Jay
0 Kudos
Message 14 of 14
(407 Views)