mumu_akuatikus wrote:I voiced the concern with one of the people responsible for the project, and he believes that it may be an unusual problem with the controller. I suppose I can say this... The reflectometer I'm making the program for is actually the world's largest reflectometer. It is brand new so the components may not be perfect, and they may present slightly unusual problems. He thinks that this may be the cause of the problem. Although we don't know exactly why this happens, he is confident that there is a slight but significant lag between writing the command and reading the feedback. Since it could not be read completely by the first, it was read in the second text box. Some evidence for this is when I turned on "Highlight Execution" for debugging. When it was on, the problem did not occur, and I was honestly baffled and did not know what to do. Perhaps it's because the highlight made everything slower and gave the reflectometer enough time to respond.
Obviously, time is an issue and it is not the most efficient way of doing things, but we are prioritizing "It works" over "It's fast" at the moment. Although it definitely could be faster, time is not issue right now. I will save this link for future purposes if someone with more experience ever decides to upgrade the program.
I'm sorry this is such an unsatisfying response. Thank you everyone for helping out.
Hey, no need to apologize. Sometimes the best solution isn't the most efficient one. In the real world, oftentimes you don't have the time or the money to investigate doing it the right way, and you have to settle for a compromise. Some people may chime in and say that it will cost you more down the road, but management decisions are like that a lot.