Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by MikaelH

  1. Here is a quick example UDP_FileReceiver.vi UDP_FileSender.vi
  2. 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.
  3. You can have a second (or third page), hidden and change it so it becomes visible.
  4. As always, thanks you, thank you, thank you.
  5. If I want to do accurate measurements I always go with a telocentric lens. Of cause to buy one that can cover 20” is too expensive, but maybe consider a smaller FOV and an XY stage/gantry for the camera to move around over the object.
  6. I don't really follow, what is not working? BTW, after changing something under a class, you need to save the class.
  7. 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: //Mike
  8. 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. 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.
  9. 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:
  10. Thanks, I'll see what I can do to follow your tips, if anybody else see something strange please let me know. //MIke
  11. 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? FPGATest.zip
  12. I’m as puzzled as you. When ticking External, the wire becomes of a differnt type. But I can't understand how you could create an "External" DVR.
  13. Sure, I've played it but never realized the ghosts behave differently :-) I would still go with one single Ghost class and have different personalities/attribute to them.
  14. Nice game. Interesting design, any reason you created 4 different Ghost classes? Inky is dependeny on Blinky, why is that needed?
  15. That's a very cool way, this diagram type should be added to the UML standard :-)
  16. If you can take an image before and after, and subtract them that will help, since you have some background features you’re not interested in. Convert to grayscale (I tried extracting the Red Plane). Apply filters (Smoothing – Median 11x11) Lookup Table Setup (I tried the Square) Threshold (this is the tricky thing to use the right setting to convert it to Binary) Basic Morphology (Close Object Size=21) Advanced Morphology (Fill Holes) Particle Analysis
  17. It's all about lighting :-) Do you have some images to share? Can you get NI Vision Toolkit? I wouldn't even try without that, I always use the vision assistant to play with the image to see how to detect the feature the best.
  18. Yes, after browsing and selecting the missing VIs it works fine. Nice example
  19. just to let you know, your Back-Saving (this and also the Cluster to Tree upload) is behaving a bit strange. When opening it, looks for SubVIs under the LV2015 folder, and I have to manually browse for them and get a Conflict notification.
  20. Why not add the "Examples Images" as well :-)
  21. Looking for smart people to join my team

  22. We're using the free windows utility: srvany.exe It's easy to use and works great. https://support.microsoft.com/en-us/kb/137890
  23. We started using TSVN Toolkit from Viewpoint Systems, which is a great add-on, but for most of our LV developers it started to make LV too slow, since our projects are often very large. So we’ve gone back to just using TortoieseSVN (and with a quick drop shortcut that brings us straight to the file in the explorer window). We prefer the Edit, Merge option for out projects.
  • Create New...

Important Information

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