Jump to content

infinitenothing

Members
 View Profile  See their activity

  • Posts

    371

  • Joined

  • Last visited

  • Days Won

    16

 Content Type 

Everything posted by infinitenothing

  1. infinitenothing
    It's been a while since I've used Vision but I remember seeing some weird things with the higher bit depth images. I remember that sometimes you had to explicitly set the bit depth of the image: http://zone.ni.com/reference/en-XX/help/370281P-01/imaqvision/imaq_image_bit_depth/ What pixel values are in your image? Could they just be really low? I'm guessing the gradient or rainbow pallets aren't helping
  2. infinitenothing
    You're not really an end user if the executable is being used by someone else. You're more like a middle user Can I suggest using a license that doesn't follow the binary, maybe Apache or MIT, for future work.
  3. infinitenothing
    Anyone tired of their myrio and looking to unload it? $1000 seems a little steep.
  4. infinitenothing
    I'm not sure I've ever seen a port freeze on my dev computer but I know I've heard of freezes in the field. I tell them to call IT. The only timing issue I've had is with flush and what happened was that flush was clearing data from a prior visa write.. Are you using NI serial ports? I'm guessing that's going to be more reliable or at least give you a better outlet for troubleshooting. I open the port at the beginning and close at the end. That's never been a problem. I use both sync and async read/writes.
  5. infinitenothing
    2048*48K= 983,040,000 pixels per second. Assuming 8 bit images You're at 7.9 Gb/s which is too fast for gige but in USB3.1 range.
  6. infinitenothing
    I remember many years ago, we'd have a camera in an inspection system and it would disappear or something and a reboot would fix it. Is this a thing ever anymore? Is there any best practice on what the best interface is for reliability. I'm thinking GigE is the way to go because of the locking connector. Any thoughts?
  7. infinitenothing
    There may also be third party tools that do something similar https://lavag.org/topic/19124-deploying-labview-code-to-raspberry-pi/
  8. infinitenothing
    Is your RMS at least better? Yeah, the symmetric errors do look like glitching. I wonder if the high input impedance is a possible contributor. You could throw a 1KOhm in parallel and see what that does. If that isn't enough add a 20nF cap in there.
  9. infinitenothing
    It might be worthwhile to look at what your AI waveform looks like. Maybe you have an offset in there.
  10. infinitenothing
    I know someone out there has a tool for handling window's window handles and you can make arbitrary EXEs a child window. I was hoping they'd chime in.
  11. infinitenothing
    Try this
  12. infinitenothing
    Your class type has the queue in it. Your accessors have to dequeue-modify-enqueue with a timeout as an input. You have to have a Create-Run-Destroy architecture.
  13. infinitenothing
    I don't run into this issue much but back before we had DVRs, many people were using single element queues for the same purpose.
  14. infinitenothing
    Let me poke a hole in that theory. Async wires aren't necessary for anything. The functionality already exists as shown in the Getting Started guide.
  15. infinitenothing
    It's one of those implicit features. You'd expect 2015 to open block diagrams from 2015.
  16. infinitenothing
    The important one is that you'll be able to open block diagrams from other people who are writing in 2015 without going back and asking for a down conversion
  17. infinitenothing
    Zer0, where do you initialize (write zeros to) the array? I'm guessing you have a race condition. Using a shift register will fix that race condition
  18. infinitenothing
    There have been some attempts: https://lavag.org/topic/5047-prototype-replacement-for-errorllb-second-attempt/ https://lavag.org/topic/10741-updating-the-labview-error-handling-core/
  19. infinitenothing
    Every time you start the outer while loop, you're going to start with the same initialized array coming into the wire. If you want labview to remember something from one iteration to the next, you need to put a shift register on that loop. The inner while loop does nothing as far as I can tell and probably should be removed.
  20. infinitenothing
    Also, you have no wait in your loop. Check your processor use—It's probably at 100% (not a great idea) for one of your processors. Try ~100 ms. If you still want to give the array event a try, here's an example of an event that is triggered by the array value change.
  21. infinitenothing
    I'm not totally clear on what you are having trouble with. After you bring in a CSV, you have an array. You need do some sort of array manipulation and comparison operations to trigger actions. I've attached a trivial example of what you can do with a 2D string array If you want that data to affect something physical you need help with DAQmx Here's a test CSV: Status,Number Normal,5 Broken,8
  22. infinitenothing
    Your VI is going to read the stop button (False) then invert that (True) make an array from that Sit at the edge of the event structure for a bit Lets say you press stop 2 ms into the event structure wait—you have an array of true waiting at the incoming edge of the event structure. That true is going to go into your "data array". The next iteration starts, the "true" at the stop control is read at the begging of the loop, you wait and execute the timeout event You can verify the above sequence if you are patient and set a really long timeout (~30 seconds) and turn on highlight execution In the picture, the shift register is just a way to make the first iteration different from all the others. On the first iteration, the timeout is 0. All other iterations have a timeout of -1. Most of us like trigger our actions based on events rather than letting the timeout lazily pick up changes as needed. To that end, you can create an event that will start executing as soon as your "data" array changes. Also, your DAQmx clear and stop are being performed in the wrong order. Follow the examples.
  23. infinitenothing
    No, that example writes to many lines at the same time. Look at the channel input: Dev1/port0/line0:7. That means that the "channel" is 8 lines. The input being an array goes along with this. Writing all the lines at the same time should be more efficient that writing them individually.
  24. infinitenothing
    Look at the example here: {LabVIEW Programs Folder}\examples\DAQmx\Digital Output\Digital - SW-Timed Output.vi One of the best things about DAQmx is there's so many good examples.
  25. infinitenothing
    Primarily, $1555
×
×
  • Create New...

Important Information

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

  I accept