Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


infinitenothing last won the day on October 23 2018

infinitenothing had the most liked content!

Community Reputation


About infinitenothing

Profile Information

  • Gender
    Not Telling
  • Location
    San Diego

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you don't want to use a feedback node, another option is using a local variable (see example below) It sounds like you're trying to process losslessly. If that's the case, you usually need some sort of buffer. In this example, I use the event queue as my buffer.
  2. Initialization behavior is well defined in the settings of the feedback node. https://zone.ni.com/reference/en-XX/help/371361L-01/lvconcepts/block_diagram_feedback/ I'm not sure what you mean by force. Are you trying to make it into a d latch?
  3. To clarify the previous post, the two loops can share a wire as long as that wire is an input to both of them. If the wire is an input from one and an output to the other then the loop that is expecting the input will have to wait for the other loop to output the data. If you intended to use that wire to communicate data between the two loops, maybe convert the wire between them to a channel wire?
  4. I'm not too familiar with the FIFOs so I can't answer those questions but I noticed your error handling is a little weak and doesn't capture errors while you're inside the loop. Usually you want to run your timed loop at your control rate (some target rate you choose). It's a little less common to try and run it losslessly as you might trying to do. If you wanted to run losslessly, you could maybe set the loop time to 0 or maybe create a timing source from your task: http://zone.ni.com/reference/en-XX/help/371361R-01/glang/create_timing_source/
  5. I think you need to replace your rotate array with another for loop with your wait inside. The inner for loop will autoindex your array and output the values one by one. If you post a VI or a snippet, we might be able to better show you what we mean.
  6. The outer one can't turn true while you're inside of the inner one. It's just like a nested if statement in C.
  7. It should still work in RT even if it doesn't show up on the pallets. Try it. Or, check out the underlying code and copy that.
  8. Basics lesson 1 has that VI in the lower right quadrant. You can also search for the VI by name using quick drop Also, on the help page it tells you the owning palette (Timing VIs and Functions) so you can find that VI.
  9. I recommend you change your booleans on the main panel to Latch When Released I modified your bool test subVI so it would pop up and stay active until the user closed the panel
  10. It would really be nice to see some code or even like just the concept to see what you're talking about. Have you seen this VI? http://zone.ni.com/reference/en-XX/help/371361P-01/glang/stall_data_flow/
  11. You can tell the graph that your waveform is offset by using bundle cluster
  12. I doubt there are plans to fix any of the bugs. Some of them have been going pretty much since the start.
  13. Are you setting verify to "false"? The verify server input is for using client certificates. I don't think you need it if you are connecting to a public site. I believe in that case, the function will verify with public CAs instead of using your client cert.
  14. Recert by points always seemed like too much accounting effort. I'd do it if there was a website where you could submit the request and have it keep track of everything.
  15. Yes, what you're doing is super common. It might be worthwhile to use the TDMS file format instead of a spreadsheet file. It's a very easy format for recording and playing back data. I'm a little curious why you're using a CRIO. It's not a bad choice but something a CDAQ could be simpler.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.