LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Boolean button stays pressed

Hi,

 

I made a application with some boolean buttons.

No I'm having the following problem:

After I build the project and test it, the buttons are not pushed (False).

That is excactly what I want.

But when I connect it to the PLC, there are some buttons that are pushed (TRUE) automatically.

In my opinion it is very strange that some buttons do that, beceause they al have the same operation: "Switch Until Released".

 

Do I have to change the operation?

When I have to do this, it is very strange that some buttons work properly, and some buttons not.

 

I hope someone can help me.

 

Greets.

0 Kudos
Message 1 of 10
(6,569 Views)

jpg.JPG

 

You can use a invoke node and select "reinitialize to default".

Message Edited by muks on 03-22-2010 04:04 PM
0 Kudos
Message 2 of 10
(6,563 Views)

make sure that all your boolean buttons have the property "Latch when released" (offcourse based on your application)

 

 

Or there might be a chance that you have created some locals or property nodes which are wired with a true constant

 

Guru

 

Regards
Guru (CLA)
0 Kudos
Message 3 of 10
(6,562 Views)

Cheese11 wrote:
[...]

But when I connect it to the PLC, there are some buttons that are pushed (TRUE) automatically.

[...]

What does that sentence indicate? I suspect:

- Frontpanelbinding

- Reading shared variables/datasocket and writing data to the buttons (variables/property  node "value")

 

Without seeing the code, it is impossible to tell what is going on....

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 4 of 10
(6,556 Views)

Is it also OK when I use the "Switch Untill Released" operation?

Beceause most of the buttons that I use have this operation.

But some are staying switched, very weird.

But I will try to do the handlings that Muks said.

 

There are no locals or property nodes, so there is no constant true.

0 Kudos
Message 5 of 10
(6,552 Views)

Norbert, 

 

There is a variable coupled to the button.

The variable stands in a DB (as boolean ofcourse), and this is coupled in a program.

The variable is just used to reset the variable.

 

In my opinion the variable is nowhere set to TRUE.

So what can the problem be?

0 Kudos
Message 6 of 10
(6,550 Views)
And if that doesnt help post your vi so that we can have a look.
0 Kudos
Message 7 of 10
(6,547 Views)

I have NEVER seen buttons to change their value just on their own. This is independend of the setting of the button....

So there has to be some code changing the value of the button.

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 8 of 10
(6,545 Views)

Norbert B wrote:

I have NEVER seen buttons to change their value just on their own. This is independend of the setting of the button....

So there has to be some code changing the value of the button.

 

Norbert


I too accept and feel you will atleast be using a case structure where the value is getting set and not getting revoked. Just a pure guess.:smileywink:
0 Kudos
Message 9 of 10
(6,539 Views)

To stop everyone having to wildly guess could you just PLEASE post your code. Im sure that someone will take the time to look at it and rectify.

 

Thanks.

------------------------------------------------------------------------------------------------------
"Everything should be made as simple as possible but no simpler"
0 Kudos
Message 10 of 10
(6,502 Views)