Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/07/2010 in all areas

  1. At a quick glance I would approach this by developing a hardware abstraction layer for the two cards that presented identical data and command structures to the rest of the program. If you do that then you can develop a single set of code for your application. Check out the tutorial http://zone.ni.com/devzone/cda/tut/p/id/3271on Developing LabVIEW Plug and Play Instrument Drivers for more info. Jason
    1 point
  2. This is a bit of a stretch, but if you have matlab, you could use a matlab script node. They have a very large standard image processing library. But you might as well use Matlab for the project. Similarly, you could also use c code nodes, or compiled dlls, but this is overkill for labview. You'd probably do better developing natively in something else, rather than writing dlls for labview. As for LV practice, I hate to rain on your parade, but do you know how many man-hours go into a toolkit for Labview (or for any programming language, for that matter)? I assure you that you will spend more time repeating other's work than doing your own. Remember, your time is money, too. Assuming you are an engineer, two weeks of your time is definitely more costly than a license. If you're a grad student, I can sympathize (I wear both hats), and I've heard the "make it work" message. so much for "how to paint a house without a paintbrush"... - Jon
    1 point
  3. Everyone is entitled to their opinion. I'll be the first to admit that I am making an assumption here, but that is just the way I feel about the situation. I also like, and think its nice, that some LAVA members are rallying-behind and supporting one of their own.
    1 point
  4. Are you looking for session times? I'm not sure how final that list is.
    1 point
  5. So some developers jumped ship from Endevo/Simbio to start AddQ, took the GDS sourcecode, repackaged it as their own and added a few bells and whistles to it, without your permission. The crazy thing is that if anyone wants to add OOP farmeworks into GDS all you have to do is contribute, and if you have ideas or sugestions on new features to GDS then Mikael would love to hear it. I'll keep using GDS, it Rocks, and I'm looking foward to contributing more.
    1 point
  6. Mattias, I can see that you have rewritten lot of the code, but from scratch.... It’s of cause just by coincident controls on the front panel have the same pixel coordinates, e.g. like this: ..or that the connector pane are almost identical, e.g. like this: Cheers, Mikael
    1 point
×
×
  • Create New...

Important Information

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