Automating Button Clicks

[jackson040]

I am not sure what happened but the error message that I was recieving is no longer popping up inititially, and the original message has returned.   I was looking at it and noticed in that Problem_SubVI I attached earlier the slave address is set to 0, but in the front panel of the temp controller VI it is set to one.  Could this be the issue?

Edit: I have found another NI community disscussion that acheives the same goal I have, but I do not know how to implement it with this program.  If you think it would help I have attacked the link below.

https://forums.ni.com/t5/LabVIEW/Auto-pressing-a-button/td-p/2180398

[cbutcher]

---

@jackson040 wrote:

I am not sure what happened but the error message that I was recieving is no longer popping up inititially, and the original message has returned.   I was looking at it and noticed in that Problem_SubVI I attached earlier the slave address is set to 0, but in the front panel of the temp controller VI it is set to one.  Could this be the issue?

---

That does sound suspicious, but might be due to an error in the first call during the Read case making the second call go through the Error case and output default values. In that case, it isn't the cause of the error, it's just a subsequent symptom.

---

@jackson040 wrote:

Edit: I have found another NI community disscussion that acheives the same goal I have, but I do not know how to implement it with this program.  If you think it would help I have attacked the link below.

https://forums.ni.com/t5/LabVIEW/Auto-pressing-a-button/td-p/2180398

---

That thread is indeed similar to your original request, but the solutions you received in the first few posts here include either the same solution, or equivalent solutions. If you read that page again you'll see what I mean better. Now it seems like your problem is only with serial communication, not button clicking.

Let's go back a step. Before making any modifications, did the program work correctly for multiple button clicks? If so, can you go back to that version and check again to ensure it still works?

If it does, what has changed (in the Read, Open, Close or otherwise cases of the bottom loop) that might affect it? If you're not sure about the affecting part, then just, what has changed?

[jackson040]

The original VI works for dozens of read, write, and clear error button clicks. I have looked through the edited VI and there are two things I came up with that could be causing the issue.

1) There was a timing structure somewhere within one of the subVI's that was interfered with when the timing loop was added into the VI.  However, I didn't see any timing structures as I went through the VI so I don't think this is likely.

2)Repeating the section of in the snippet in both the top and middle loop caused an error in how the read function was called in the middle loop.  I do not know if this is actually something that would result in this spefic error, but it is the first thing that came to mind.

Thank you,

Jackson

[jackson040]

The original VI works for dozens of read, write, and clear error button clicks. I have looked through the edited VI and there are two things I came up with that could be causing the issue.

1) There was a timing structure somewhere within one of the subVI's that was interfered with when the timing loop was added into the VI.  However, I didn't see any timing structures as I went through the VI so I don't think this is likely.

2)Repeating the section of in the snippet in both the top and middle loop caused an error in how the read function was called in the middle loop.  I do not know if this is actually something that would result in this spefic error, but it is the first thing that came to mind.

[jackson040]

Hello all,

This will be my final post on this thread.  I have found a solution to my problem, and I am attaching it below for anybody who is having similar issues. 

I have eliminated most of what came in the initial VI, but it works as intended.  This new VI will take readings once  per second, but you can't edit the Set Point while the program runs.

Thank you for all the help,

Jackson