Jump to content

infinitenothing

Members
  • Posts

    362
  • Joined

  • Last visited

  • Days Won

    15

Posts posted by infinitenothing

  1. To clarify the second image was posted before the forum update. Here's the thread:

    https://lavag.org/topic/20671-programmatically-select-all-boolean-best-way-to-avoid-race-condition/?tab=comments#comment-125949

    So, I'm guessing the forum is stripping the metadata on upload now. I reposted that image in this thread by copying the link into the editor box. The box "embedded" the image for me automatically.

  2. I want to clarify that as far as I know there's no standard way to store an image in a SQLite database. That is, @Gepponline, your question has nothing to do with SQLite much less this toolkit. As far as we know, SQLite Administrator uses a proprietary binary format for storing the images as blobs. You should really go to that community to determine what that format is. Unfortunately, that project looks like it was abandoned with no source code available so you might just be out of luck.

  3. I suggest you break your question down into parts as different threads and forums will be able to answer each part better. It looks like your SQLite stuff is correct and your issue is just flattening and unflattening so the machine vision forum might be a better place to ask for help. In the interim, here's one way to do your flatten unflatten using the IMAQ toolkit.

     

    Store in blob.png

  4. The attached code shows how SQLite will interpret various types into an integer. It makes me a little nervous that there's no warnings or other way to determine that a value might not match what was requested. I guess I could check every value for its column type. Is there an easier way that I'm missing?

    Test type handling.png

  5. Coerce to type is useful for getting nontypedeffed data into a typedef form but there's a small problem of type safety. For example, if you try and coerce an I32 to a U8, the value will silently wrap without even so much as a coercion dot.

    But in recent versions of LV, we have something to ensure a little safety— "Assert Structural Type Match"

    And fortunately, for this use case, it's not so sensitive as to disallow typedeffed data from matching it's plain counterpart so we can use it to enforce a runtime error if someone wires an I32 up. And, to make this new function more convenient, you can wrap it up in a VIM. 

    TypeDef Snippet.png

  6. No, by current spec I mean:

    Quote

    ±16 mA all channels maximum; ±4 mA per channel typical

     

    By "how are you connecting", I meant connecting to the analog side of the module. For example do you have one of these: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210164

    I see that you have the module setup for differential, that's a little more tricky right? Can you try single ended? maybe with a battery or a potentiometer. Otherwise you have to watch out for things like common mode voltages and such.

  7. I assume you've configured the 9205 for single ended vs differential correctly?

    Are you within the current spec of the 9264?

    How are you connecting the modules? A cable or one of NI's breakout boards?

    Try and simplify things as much as possible. For example, use a battery as a voltage source directly to the input and disconnect the outputs to rule out loading issues.

  8. I made a snippet to illustrate what I was thinking. I have a Basler dart camera that I was able to test with and it looked OK in theory. You'll notice it is in continuous mode. I'm hoping that since trigger and the exposure both go through property nodes, the settings will apply in that order. There might be a theoretical race condition that would apply the new exposure to a capture in progress, I guess for that, you could capture the exposure before and after and have some sort of indeterminate case but I think it would be nearly impossible.

    image grab triggered.png

    • Like 1
×
×
  • Create New...

Important Information

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