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

crossrulz

Members
  • Content Count

    403
  • Joined

  • Last visited

  • Days Won

    12

crossrulz last won the day on June 15

crossrulz had the most liked content!

Community Reputation

64

About crossrulz

  • Rank
    Extremely Active
  • Birthday 04/22/1982

Profile Information

  • Gender
    Male
  • Location
    Cincinnati, OH

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since
    2005

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. crossrulz

    LabVIEW 2018 SP1 Released

    I downloaded the DS disks last week and the speeds seemed good to me, considering the corporate IT mess I have to get through.
  2. crossrulz

    start with xml data

    1. Help->Find Examples. Do a search for XML 2. Go look at packages in VIPM. NI has a Simple XML library that I used to figure some things out. Then JKI and MGI have their own XML packages you can have a look at.
  3. crossrulz

    OpenG ini file issues

    Yes, I still heavily use ini files. Admittedly, I am starting to transition my code to use XML.
  4. crossrulz

    Once again: vi version conversion

    Here are your VIs saved in 2015. 2015.zip
  5. Right-click on the timer indicator and choose Display Format. Choose the Relative Time type and then the HH:MM:SS radio button. The indicator will now show your hours, minutes, and seconds.
  6. crossrulz

    Example Project in LVOOP

    I still maintain that using parallel loops is greatly beneficial to you here. But if you insist on LVOOP, you should have a nice long look at the Actor Framework.
  7. I can't say I support the use of the Write DVR Value. The point of using a DVR is to protect critical sections of code (ie avoid race conditions). If you are just randomly writing a value to a DVR without doing the Read-Modify-Write protection, you might as well use a Global Variable and get better performance.
  8. You might want to monitor the communications with something like Wire Shark. You might find the instrument sent a command code and is waiting for you to confirm it.
  9. As long as you don't need the command codes, just look to the TCP Client and TCP Server examples already built into LabVIEW. Telnet only gets complicated (at all) when the command codes are used.
  10. crossrulz

    LabVIEW 2018

    I would stick with 32-bit. I have yet to see a reason to go 64-bit unless you are doing massive amounts of memory intensive processing (Vision immediately comes to mind).
  11. crossrulz

    Alternative to compactRIO

    You could probably get away with a simple Arduino or Raspberry Pi or even an office level PC.
  12. My only TestStand roadblock so far (and has not been nearly as big of one as I expected) is the deployment license cost. Though, put that cost against a VST and it is a small drop in the bucket. (The VST is literally half of the cost of my current project's entire test rack.) As far as going away from TestStand, I have ran into a couple situations where I was told to use TestStand and I convinced the customer/management that the project really just needed a decent State Machine with a few other loops for logging and instrumentation. Sorry, no real ammo coming from me. But I am very curious about other people's reasons.
  13. crossrulz

    LabVIEW 2018 Available for download

    Or for those looking for the Developer Suite: http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/n1:2018_Spring,n8:142,ssnav:pdl/
  14. crossrulz

    OR Condition LED

    Sounds more like you need a NOT, not an OR. And what's wrong with using logic gates?
  15. DVRs were introduced in 2009. I skipped from 8.6 to 2011, but I do remember having tons of issues with 2009. But we all know that the best "must have" feature of any LabVIEW version was the new icons that showed the version starting with 2014! Other notables: Vivado compiler for LabVIEW FPGA (2014), Channels (2016), Malleable VIs (2017).
×

Important Information

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