LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

digital output 1 sec ON - 9 sec OFF

Solved!
Go to solution

Hi,

Thanks for the reply,

 

Can you help me with, how can i get the signal to my output channel from the snippet you attached.

So getting the output on my digital channels.

 

Thanks,

kind regards,

0 Kudos
Message 11 of 24
(1,185 Views)
Solution
Accepted by topic author sky_11

Hi sky,

 

you need to output an 1D array to your digital outputs:

check.png

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 12 of 24
(1,183 Views)

Thanks a lot 🙂

0 Kudos
Message 13 of 24
(1,176 Views)

Hi GerdW,

 

I am now using the output on my Digital channel. But I have a one small error.

When I press the stop button the output on the channel where I stopped it stays high untill i disconnet the usb cable.

 

I would like to have it in such a way, that when i hit the stop button the output is low on all the channels.

Can you help maybe?

 

Thanks.

Kind Regards.

 

0 Kudos
Message 14 of 24
(1,159 Views)

You just need to do one more write after the loop where you send it an array of all Falses before you stop the task.

0 Kudos
Message 15 of 24
(1,152 Views)

Hi,

 

can you maybe give me an example, How to do it. I tried something but i guess i am did it wrong.

 

Thanks.

Kind Regards,

0 Kudos
Message 16 of 24
(1,150 Views)

Hi sky,

 


I tried something but i guess i am did it wrong.


 

Usually you attach your "try VI" and we tell you what's wrong with it…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 17 of 24
(1,145 Views)

Here is the VI.

 

In this case on the Front panel i see the LED shifting but on the digital output of the Data acquistion the 1st channel stays high all the time.

 

But I want it the VI to stop output of all the channels when i press stop.

 

Thanks.

Kind regards,

 

0 Kudos
Message 18 of 24
(1,139 Views)

As said before: usually you should attach your VI, so we can give suggestions for improvements…

 

Edit: That's a picture, but no VI…

 

Solution: THINK DATAFLOW!

Did you debug your VI with highlighting enabled? Then you would notice why it behaves like it does and where the problem comes from…

 

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 19 of 24
(1,134 Views)

Here is the VI.

I thought we could use in to drag in the block diagram. Sorry for that.

 

0 Kudos
Message 20 of 24
(1,118 Views)