Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 11/27/2018 in all areas

  1. 2 points
    The new version is ready for download under Untested Version https://opengds.github.io/
  2. 1 point
    I wasn't aware of the power of all those design patterns. This makes a great toolkit even greater. This discussion made me realize I have to take a closer look at all those different design patterns. I tried to add the new method as a property node instead of a normal method. That's why I couldn't find it. Having these templates for every design pattern makes them very easy to use. I downloaded the new version and it looks perfect to me. Thanks for updating the templates so quickly.
  3. 1 point
    Yes, that sounds like a solid solution. Good thinking, and congrats!
  4. 1 point
    Well after some research, this is what i came to. Sending the email in html format with the following VI to transform Unicode from LabVIEW to HTML character. I think it will work in most of the case. Benoit PS: Thanks for your help. Unicode to html.vi
  5. 1 point
    Hi Diego, to speed things up, you should consider separating the TCP read and the file writing in two separate loops. For example, if you make two parallel loops: one that reads and adds data to a queue, and a second which reads the queue and writes to file, then you can read multiple datapoints at once and write less frequently to the file. Investigate the use of a Producer-Consumer architecture. I took the liberty of reorganizing your example to demonstrate the concept. I'd probably approach your task where your Python code is the client that publishes data and LabVIEW would act as a server (instead of the other way around), but I wanted to keep with the spirit of your example. Client.vi
  6. 1 point
    main.vi I've back-saved to LV 2012 but I don't have 2012 available ATM to check (and can't remember when the "Inserted VI" property was introduced.)


×
×
  • Create New...

Important Information

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