Jump to content
News about the LabVIEW Wiki! Read more... ×

JKSH

Members
  • Content Count

    306
  • Joined

  • Last visited

  • Days Won

    25

JKSH last won the day on May 17 2018

JKSH had the most liked content!

Community Reputation

67

1 Follower

About JKSH

  • Rank
    Extremely Active

Profile Information

  • Gender
    Not Telling
  • Location
    Perth, Western Australia

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    2011

Contact Methods

Recent Profile Visitors

2,283 profile views
  1. JKSH

    LabVIEW snippet PNGs are being sanitized

    It used to work, then it stopped: https://forums.ni.com/t5/LabVIEW/Notice-Attach-VI-Snippets-to-post-rather-than-upload/td-p/3660471 Attachments (as opposed to inline images) should be fine, apparently.
  2. JKSH

    LabVIEW Not Responding

    In the video, you used the "Abort" button to stop the code. Does the delay still occur if you shut down everything gracefully instead of aborting? Does the delay still occur if you use File > Save All to save your changes before running again? Does the delay still occur if you disable "Separate compiled code" for all your VIs and classes?
  3. I think it makes sense to have separate APIs for text strings and byte array "strings". However, both are still incomplete at the moment. The feature I miss most from LabVIEW Classic is "hex mode" on a string indicator for inspecting the contents of a byte array. I find the Silver palette quite decent Simply setting the background to white (as opposed to "LabVIEW Grey") also does wonders. A note on your last link: That "stark example of modernity" depicts an old widget technology, basically unchanged for over a decade -- it's still maintained today, but only in bugfix mode. Here's an actual example of modernity.
  4. Only for LabVIEW Communications type applications (on PXI). FPGA through RIO (and RIO in general) is not yet supported. Note that Python support is Windows-only. I was hoping to use the Python Node on my LinuxRT cRIO, but no dice. Related: http://www.ni.com/pdf/products/us/labview-roadmap.pdf > Is it using a VI at all? Yes, but the file format is different. > Does it support scripting Not yet (see Roadmap link) > and OO? Mostly. But we can't have type definitions inside classes. > Could I use llb/lvlib/lvlibp/...? llb: Gone in NXG (which is a good thing; these are terrible for source control) lvlib: Yes lvlibp: Not sure > Is the FP resizable?  No. My company finds WebVIs pretty useful. We've started using it for some real projects (but only for the web client -- we still use LabVIEW Classic for other parts of the project, including the web server)
  5. You could save the data to file and then use the System Exec VI to run your choice of Linux chart generation tools like gnuplot (a command-line application) or Matplotlib (a Python library).
  6. JKSH

    LabVIEW 2018 SP1 Released

    Just got "The page you requested may have moved, been deleted, or is inaccessible. Search below for other content, or contact NI for assistance." on all 3 Fall 2018 links
  7. JKSH

    start with xml data

    No problem. We are happy to help, but we'd appreciate it if you try to follow our instructions. Good luck with learning LabVIEW.
  8. JKSH

    start with xml data

    Open LabVIEW and click Help > Find Examples... then search for "XML". @crossrulz gave you this advice earlier.
  9. JKSH

    start with xml data

    Why do you refuse to use the code that @Benoit already wrote for you? Like I said before, your XML file is corrupted. The XML palette won't work on it.
  10. JKSH

    start with xml data

    Where did you get this XML document from? It is corrupted (There are many stray "-" characters, so XML parsers will give you an error) Also, take the time to follow @crossrulz's advice:
  11. Yuck. Has NI been prodded about this?
  12. Yes, that sounds like a solid solution. Good thinking, and congrats!
  13. I just did a quick test. It looks like LabVIEW assumes that the email text is encoded in your PC's default 8-bit encoding. Then, LabVIEW automatically tries to convert the text to UTF-8. I think this means the only way to send Japanese emails through LabVIEW is to configure your whole PC to use Japanese 8-bit encoding and/or use the Japanese version of LabVIEW. (I'll have to leave for now, sorry. I'll try some more tests tonight to see if anything else works)
  14. First, how do you input the Asian characters into your program?
×

Important Information

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