Jump to content

gleichman

Members
  • Content Count

    172
  • Joined

  • Last visited

  • Days Won

    3

gleichman last won the day on April 11 2018

gleichman had the most liked content!

Community Reputation

10

About gleichman

  • Rank
    Very Active

Profile Information

  • Gender
    Male
  • Location
    Plymouth, Michigan

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    1993

Contact Methods

Recent Profile Visitors

1,594 profile views
  1. Why post a critical remark to what looks like a homework question from 2.5 years ago? Acquiring electrical current data is not the challenge of this problem which is very doable with the correct hardware. The challenge is knowing when the current exceeds the "Time-Current Characteristic Curve". The curve defines for a given current level how much time passes before an over-current occurs. The higher the current the quicker the reaction time, but the shapes can vary.
  2. Is there a reason you're not using the actual "Strip Path" and "Build Path" functions? These allow you to manipulate the path, platform independent. No worries about slash direction and appending the root.
  3. Why are you using UDP if lost packets aren't acceptable? Even if you are on a closed network, there is no guarantee that all the packets get through. Sounds like you should be using TCP.
  4. Also, NXG 3.0 is available through NI Package Manager.
  5. It now shows "Release date: 12-03-2018"
  6. I've purchased my ticket. Looking forward to another NI Week.
  7. Here's some pictures from the year twitter was created.
  8. We used to get a bus and I thought NI used to arrange it for us even though it was not an NI event.
  9. I also had these same issues. Mine was due to a bad beta install and was so bad NI PM would not work which created a interesting catch-22. I finally got NI PM working and was able to uninstall everything and re-install. https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019R9WSAU
  10. It does work if typed in the same format as the display format. For example, if you type in 00:5 it will display "00:05", but if you type in just "5" LabVIEW sees it as an incomplete input and reverts to the last value. It works the same in LV16. I don't have older versions at home to test. NI will probably say that this is the more correct way of operating even though it is less optimal for your users. You could create an xControl that mimics the LV12 mode of entry.
  11. Nice example of a VIM. I'm finding VIMs to be very useful. I think they be the best new LabVIEW feature since the event structure.
  12. I've done something like this with a MultiColumn Listbox to show the configuration as plain text and a Tab or SubPanel for editing the selected line of the MCL.
  13. I ran DETT and found a reference leak. I fixed it and verified the fix with DETT, but I still have the same GDI object leak afterwards.
  14. I run the system as an executable and it has the same problem. I was hoping to find out what kind of LabVIEW functions create new GDI objects. This is probably something bad that my code is doing, but my system is large and it has been difficult to isolate the culprit.
×
×
  • Create New...

Important Information

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