@LVPS28 wrote:
@RavensFan I tried to fix that it is slightly better but still having some here and there.
Also how do I not make it update while typing while entering a command to Serial write?
Why do you want to "update while typing"? That is a feature in LabVIEW that is only used in special situations. Like if you wanted to create some sort of filtering feature that modifies some other indicator or control while you type.
Your question caused me to notice something in your VI. I can only see your question applying to 2 string controls in your VI. First would be Commands. But that doesn't make sense. You have to actually enter whatever you want in there before you Run the VI because that control is read immediately and never read again. That is actually a poor user interface choice. But then again, you never use the value from that control anywhere in your program, so you should just delete that control.
The other spot is "Enter" string. it is NOT set to "Update while typing". This is where I just noticed you used a "Key Down" event for that. Why? There is no way that could work properly. Let's say you would enter "123" as your command. You'd key down on "1". Guess what, that event will execute and VISA Write a "1" followed by a carriage return. Then you key down on "2". Now it VISA Writes "12" followed by a CR. Now you key down on "3". Now it writes a "123" followed by a CR. There is no way that is what your device would want you to do. But it could very possible cause it to send multiple messages if it is responding to 3 different commands. So I think your current Key Down event is effectively causing it to behave the same way as "update while typing". And you definitely don't want that.
That event should be a value change event so when you type in "123" and hit Enter to enter it, the value change event would run once and send "123" followed by a CR. For me, a better user interface is to add a separate button called "Send" and have the code execute on the "Send" button's value change event. This causes the command to only execute when the user explicitly presses that button. Otherwise there is a chance they could accidentally click enter while that string control is active and cause a command to be sent when they didn't really mean to.
