Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by MikaelH

  1. Also can you add debug mode to the VI, so it can iterate through images from disk as well, and also supply those images.
    It makes it easier to help you with the task.
    I don't have a camera attached to my PC at the moment.

    Also a small description how your VI is supposed to work would make it easier to help you out.


  2. 12 hours ago, M.H.K said:

    Hi MikaeIH and thank you very much.It's exactly my goal.

    I will try your example and if I have a question, I will say you.

    Thank you again.

    No Worries, that's why we are here :-)
    The property node that will let you know the Coordinate Offset is a property node that is "Secret", you can only select this if you put this into your LabVIEW.ini file.

    If you don't want you use this property node, you can just use a constant value.


  3. To be able to do this, you need to have every point as a one plot, and then you can use the PlotImage.Front property node to follow the mouse to draw a ROI on the graph, and then find the plots-points that are within the ROI and change the Color of those plots.

    It might be easier to use a Picture Control Plot to start with.

  4. 10 hours ago, skshatri said:


    I am using UDP to transfer files from server to client but I cannot receive the complete file. I can receive only a part of it.

    For example if the size of the file to be sent is 25 MB, I am receiving only 60 KB at the client end

    Can you post your code?

    How big do you make the UDP packages?

    I guess you know that a one UDP package could only be 65,507 bytes

    So you need to split them into multiple packages with some header data, so you can see that you have received them all and put them together in the correct order.




  5. Look at the the OpenGDS (http://opengds.github.io/)

    It creates classes based on the UML modeller.

    The UML modeller can import XMI files and from there you can create the classes.

    It supports analysing and creating your classes, it's open source and you can see how it's done. in e.g. the VI:
    LabVIEW 20XX\resource\Framework\Providers\Open_GDS\ClassProviders\Provider_LvNativeClass\ClassWriterNative_class\CreateClass.vi

    View the videos here to learn about the tool:




  6. Way to go and mark your own answer rather than the dude that actually solved it. :angry:

    Not even a like for Shoneill? :shifty:

    Sorry about that, both are marked as the solution now. He pointed me in the right direction and my solution just showed how I had to implement it to get it working.


    That's not necessary. The FIFO size on the host side is independent of the FIFO size on the FPGA. You can configure the host-side buffer to be much larger and then do a single write as you originally intended. The DMA automatically copies data from the host buffer into the FPGA buffer as space becomes available.

    Interesting idea.

    So you can configure the FIFO in RT with the "Requestes Depth" to a much larger number that the FIFO on the FPGA supports, and the DMA will take care of the rest?!!?

    If so that is a very nice solution.

  7. You're correct.

    It looks like I'm running out of memory.

    I have enough Block Memory, but it looks like it’s using LUTs instead, so yes by reducing the FIFO sizes it starts to compile.

    The error message I get is: “The Design requires more LUT as Memory cells…This design requires 19337 of such cell types but only 17400 compatible sites are available in the target device.â€

    I just reduce the FIFO to the FPGA and that solved it.

    The problem was that I made the FIFO size to the FPGA too big, that design would make the SW easier just One Write on the RT, but now I need to do something like this in the RT:


  8. Hi FPGA expert.

    When I try “my way†of implementing a simple FPGA Analog Out VI, I run out of FPGA fabric (too may LUTs used).

    So what better way can I do this (if there is one), that don’t overuse my LUTs.

    My task is to:

    Make one analog measurement and control 2 analogue outputs that should be clocked out every time I get a digital trigger in.


    I’m running a sbRIO-9637 (Zynq7020)

    I’ve attached the simple application and I’m puzzled of what needs so many Look Up Tables (LUTs).

    Any suggestions?


  • Create New...

Important Information

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