Jump to content

MartinPeeker

Members
  • Content Count

    31
  • Joined

  • Last visited

  • Days Won

    2

MartinPeeker last won the day on March 31 2016

MartinPeeker had the most liked content!

Community Reputation

5

About MartinPeeker

  • Rank
    More Active

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2012
  • Since
    2001

Recent Profile Visitors

1,289 profile views
  1. Use Read From Spreadsheet File.vi twice, once for each file. Index out first column of both resulting arrays, build new array using "Build Array" primitive. Probably you need to Transpose as well. But if the time stamps are to be connected to the measurement values, which looks to be the case, I would bundle each time stamp with the corresponding measurement value into a cluster and then have a 1D-array of those clusters.
  2. I just had the same problem. Couldn't create override methods using GDS. Couldn't remove file from project. Rename and remove worked, but still couldn't add override method with GDS. Adding it the override using LVOOP worked, but again, couldn't remove it from project. Turns out I had vi:s with the same name in dependencies. They were there since I had used the GDS clone method to another class for a number of vi:s, the removed them from the original class. This included a polymorphic vi that referenced these, only the references weren't transfered so they now pointed at the vi:s with the
  3. As I understand it your problem is having two child classes that are very similar except in some functionality. Your solution is to make one child inherit from the other so that you can benefit from the similarities, but this gives you problems when calling the parent, which forces you to make implementations in a parent or grandparent because of what the grandchild needs. I've been there a few times, and honestly mostly hacked my way around it, but the elegant design for this (if possible) should be to put the functionality that differs between the two children in an aggregated class that
  4. Without having worked with Control Design and Simulation and without having the possibility to look at the code, my guess is that your TransferFunction 7 and 8 expects its in data on the left and returns its out data on the right. Left to right is the default style guideline in LabVIEW, so try to re-wire those functions so that the output of Summation 3 goes to the left side of TransferFunction 7, the right side of TransferFunction 7 goes to the bottom input of Summation 3 (and similarly for Summation 4).
  5. I'm running LabVIEW on Ubuntu, and it's working pretty good. Mostly I'm still at 8.6 but I've installed up to 2012 and it is all running well. In 8.6 I have some quirks, more silent crashes than I would expect in Win, some computers have severe graphics problems with LV, fonts can be a bit messy although I suspect thats a general LV for Linux issue. Sometimes the windows management (KDE) can mess up a bit. I've developed a product that runs on a dedicated slimmed down Ubuntu distro with LV-RTE and that works fine, although I've hit performance degradation on those computers (while others s
  6. I'm not sure what would qualify as a major change that fundamentally changes the product. New concepts are introduced from time to time such as Embedded targets (8.xx?), the Project Explorer (8.xx?), native Object Oriented programming (8.20) and Actor Framework (20XX?). All version have good backward compatiblity and you can save your code for previous versions back to 8.0 at least provided you do not use things introduced after that. It's seldom very difficult to upgrade from an older version to a newer, although there are special cases when people run into problems. When it comes to fund
  7. Since LV2009 NI releases one major revision per year in august, named by the release year. This is then followed by a Service Pack containing bug fixes typically released in early March. So currently the latest release is LV2013SP1. Many prefer waiting with updating their systems until the service pack is released. You can find some information on versions here.
  8. This might be a good use case for Variant Attributes.
  9. Tried disabling the other event structures - didn't help....
  10. Thanks for that hooovahh. To make things a bit more puzzling, I thought I had a workaround by setting the key focus back where I wanted it in the 'Mouse down?' event. Works well in my little example, focus stays on my string control if I type and click the indicator at the same time. It doesn't work in my application though, focus is stolen and the typing jumps to the start of the string control. In all honesty I should mention that the actual application is somewhat larger and has three event structures in it, although no other event structure handles any mouse events nor any filter events.
  11. Crosspost from here, didn't get momentum there though. I'm trying to prevent accidental stealing of focus from a string control by discarding the Mouse down? filter event. It turns out however that mouse down on any control or indicator that can take any input, such as strings, numerics, paths etc takes focus away from the string control. Is there a use case for this that I can't see or is it a bug? FocusLab.vi
  12. I use multiple ES in the same block diagram, typically a similar situations others have mentioned. I let my system update running graphs and indicators with user events which is handled i one ES, UI interaction is handled by another ES that also checks system status in its timeout case. I even have ES i other parallel loops such as a clock loop, just to listen to a 'Quit' user event.
  13. I'm with Darren on this one. Mostly even down to single vi:s actually. Working with a SCM makes this even worse (might be better if it was integrated, but that is not my luck). I want to rename it in the SCM so that I don't lose the revision history, but that leaves you in the rename-on-disk world of pain for(imstuck) was talking about. I didn't know of the possibility to move files around in the File tab, one of those things I've overlooked, thanks for letting me know about this. How does this work with an inegrated SCM?
  14. This article describes some of the caveats with hyperthreading, having debug turned on being one of them.
  15. Hello again folks! A bit of a bump of an old thread here, I still haven't been able to solve this issue, it remains with LV2012. A short recap of the problem: I've been trying to track this down again lately, and my suspicions are now towards hyperthreading as this is one of the main differences between the computers. Machine 2 with a cpu described above as 2* Genuine Intel® CPU N270 @ 1.60GHz turns out to be a single core CPU with hyperthreading enabled, whereas machine 1 with a CPU 1* Intel® Celeron® CPU 900 @ 2.20GHz do not use hyperthreading. I've tried most pe
×
×
  • Create New...

Important Information

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