Jump to content

MikaelH

Members
  • Posts

    828
  • Joined

  • Last visited

  • Days Won

    47

Everything posted by MikaelH

  1. You are right the NI-motion driver is not working in 64 bit, which is a really bad thing. But we use the NI motion drivers very successfully on from LV 64 bit....so how do we do that? We create a LV32 bit server application, that our LC64 bit application starts (if it's not already running). We then connect and send instructions over localhost-TCIP/IP, to the 32 bit written LV server application. We use this architecture for several driver components where e.g. the vendor only supplies a 32 bit dll version. Since we're using a GOOP based HAL inheritance structure the driver layer solves all our problems. I hope you don't give up yet on the 64 bit solution, since it will solve a lot of your problems.
  2. I hope you are running LV 64bit to start with, we only run 64 bit here, so we hardly get any out of memory issues. The easiest way it to stop disposing/destroying the image and see if that helps. If you create a "new" image with the same name, you'll just get the same reference. A pool is one way to go as well, but you need a acquire and release images out and into the pool, so if the pool is empty the next user have to wait for his turn.
  3. I would use for loops in your examples. And if you do, it's kind of impressive that you can run the loop with Parallelism activated, but them suddenly it takes 3 times longer time.
  4. The only time I inherit a concrete class, is when I have a Class Called e.g. Instrument123, that has many methods and been verified and work perfectly. Then a new model comes out "Instrument123+", that just needs tweaking in one method or so, to get the same behavior as the old instrument. I guess I do this because I'm lazy, but that's when I do it.
  5. The INI token "ModernBD=True", only changes the wire color for (what I can see) the Blue Numeric into: Instead of the old Blue:
  6. I've just started to use LV2016, and one thing I noticed is that the built-in function Icon's inner color isn't black any more when placed on the BD. It's black in the palette, but when placed it becomes gray. Some functions is still black, is this a new feature?
  7. Just a tip, start off with a base class called: Instrument Then children for the different abstract types, and children to those for the specific ones. Add a FactoryCreateAllInstruments method in the Instrument Base class
  8. I Agree that all those things are very easy to learn, but if the person knows about them, it tells me that they are curious enough to looks at our peoples solutions. So even if you have >10 years LV experiences but never heard about OpenG VIs, Custom Probes, VIPM or QD, that tells me that the person have probable not worked in a team, and been doing the same style of coding since the they started. They probably still thinks global variables are the best way of sending data between processes.
  9. When I interview someone I check: If they are familiar with the OpenG libraries. How much they know about version control If they know what VIPM is If they know and have used: Queues, Dynamic Events, DVRs, libraries(*.lvlib) and classes (*.lvclass) types. Which (if any) LV-forums they visit regularly (it's important that the person is looking around to see how other people solves problems) Then of course I ask them about Quick Drop and QD Short Cuts I ask them about: Custom probes. If you know all these things I would hire you :-)
  10. I would use a Picture control together with a plot, something like this. ExtraX-Scales.vi
  11. What they should have done, is to convert the U32 to U64 inside the node, so it handles the date correctly, but maybe it's not that easy
  12. Does anybody know why in some Point By Point functions there is a Type Cast from I32 to I32 in the code. E.g. Sort 1D Array PtByPt.vi Array Max & Min PtByPt.vi
  13. I had to use QD "fts" (Format To String) and the format %<%Y-%m-%d>T to get it working.
  14. Is it commonly knows that the Get date/Time String can't handle Time Stamps greater than 5PM the 6th of February 2040?!?!
  15. Now I've installed the needed VIs: and I've tested it, it looks nice :-)
  16. It looks I have to install: <userlib>:\_LAVACR\Scripting Tools\XNode Support\...
  17. I would use the low level SQL syntax to do this...if the database supports it. INSERT INTO test1 (Column1,Column2) VALUES(1,2),(3,4),(5,6); I've stopped using NI's DB toolkit, instead I use the LabSQL ADO drivers wrapped in my own driver. This is much faster. I've attached my version DB_Export.zip
  18. Sorry, it's using lots of internal libraries, but I've attached the the same HTML report with the JS and CSS files externally linked (this is the default way we save the plots, we refer to all JS and CSS files from a server). In this version you can see how easy it is to use the JQPlot API Report.zip
  19. BTW this is the end result with the VI above:
  20. Here is a quick hack that does the job. I hope you have the Vision Sub VI, to find the Line Intersection point. I use that in combination with a OpenGDS VI to see if 2 lines intersect, sorry didn't have time to document it nicely. //Mike OpenGDS_LineIntersectLine.zip
  21. 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.
  22. The VI:Draw Geometric Matches Position is missing
×
×
  • Create New...

Important Information

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