JKSH

That means the computers aren't connected properly. You must get pinging to work first. Without this basic step, UDP definitely won't work. What are the IP addresses and subnet masks of your two computers?

Nice! Extra points for demo-ing with Star Control 2 I saw this on Google+ last month: https://plus.google.com/107942026210962154106/posts/9cZoas7UgLy Are you guys working together?

See http://floating-point-gui.de/ -- it explains why floating point numbers lose precision.

Hi, You can manually search for tabs yourself to split the text into separate strings. If you install OpenG, you'll get the "String to 1D Array" VI that is designed for your use case.

As ak_nz and drjdpowell have both said, it is perfectly fine to implement concrete code in an abstract class. This lets you make full use of inheritance to keep your project tidy and organized. "Rules" and "best practices" are established to guide you down a tried-and-true path, to maximize your chances of succeeding the first time you try. However, a set of rules will never cover all possibilities so simply following rules will not guarantee you success. As the software designer/architect, it is your job to decide whether or not it makes sense to follow a rule in a particular part of your project. Referring to the two quotes above, I'd say: "It's ok to inhibit parent behaviour if 2 out of 20 children need to do it, but not if 18 out of 20 need to do it. If 10 out of 20 need to do it, well... make a judgement call." I'll answer your question in multiple levels. Level 1: The definition of "Abstract" In OOP, an abstract method is defined as a method which has no implementation. Its purpose is to define an interface for children to follow, and it is the children's job to provide the implementation. An abstract class is a class that contains one or more abstract methods. An abstract class can contain concrete methods too. So yes, if you put code in your parent method, then the parent method is concrete, not abstract. However, this in itself doesn't make the parent class non-abstract. Level 2: The (lack of) necessity of "Abstract" From your original question, I gather that you're wondering if you need to keep your parent "abstract" in order to abide by some set of best practices, and your latest post suggests that you're no longer worried about this. To reaffirm: Many examples of inheritance show you an abstract common ancestor implemented by multiple children. However, there are no rules that say you must have an abstract common ancestor. You are free to have a fully concrete (and usable) class as your common ancestor if it makes sense to do so. Level 3: The (lack of the) concept of "Abstract" in LabVIEW Since you're interested in formal definitions and terminologies, I'll throw this in: LabVIEW does not support abstract methods in the traditional sense (yet?). As I said in Level 1, an abstract method has no implementation by definition. However, what people commonly refer to as "abstract VI"s do in fact have an implementation: This implementation simply does nothing. "Having no implementation" is not the same as "Having an implementation that does nothing". LabVIEW doesn't let you create a VI with no implementation. In other languages, your program cannot be compiled if you inherit from an abstract class but don't provide implementations for all of its abstract methods. This can be a useful way to remind developers to implement them. LabVIEW doesn't do this -- a LabVIEW program will happily run even if you call an "abstract VI". To work around this, what I did in a recent project was to implement pop-up dialogs in my "abstract VIs". This way, I'll get a message at runtime if I forget to implement something in a new child class a few months down the track. EDIT: LabVIEW programmers fulfil the purpose of abstract functions by doing 2 things: (i) Have a VI that does nothing, and/or (ii) select the "Require descendent classes to override this dynamic dispatch VI" option in the class properties dialog. See this post for more: http://stackoverflow.com/questions/391483/what-is-the-difference-between-an-abstract-function-and-a-virtual-function (Note that NI explicitly rejected the term "virtual" because it's confusing to talk about non-virtual-Virtual-Instruments, so they picked "dynamic dispatch" instead) At the end of the day, knowing terminologies is useful (and important!) when discussing concepts, but it shouldn't affect how you design your project. All the best!

The documentation explains more: Event Structure: http://zone.ni.com/reference/en-XX/help/371361L-01/glang/event_structure/ Elapsed Time Express VI: http://zone.ni.com/reference/en-XX/help/371361L-01/lvexpress/elapsed_time/

Hi, What version of LabVIEW are you using? There was a bug in LV 2010 that causes LVOOP property nodes to output wrong data. See issue #255982 http://www.ni.com/white-paper/11869/en/ It was supposedly fixed in LV 2010 SP1.

I prefer to post bug reports to http://forums.ni.com/ -- I seem to get better responses and CARs that way :-D Also, in the event that it's a PEBCAK (http://en.wiktionary.org/wiki/PEBCAK ) instead of a bug, there will be lots more people who can see my issue and point me in the right direction.

I converted C:\ProgramData\National Instruments\MDF (and other large folders that don't need to be on an SSD) into a symbolic link that points to a folder on a HDD. That way, the files don't take up space on my SSD, but programs can still find the files if necessary. No configuration required. http://technet.microsoft.com/en-au/library/cc753194.aspx

Hi Sharon, How do you read the text from Excel into LabVIEW? I'm guessing that the text that you read from Excel text is encoded in SHIFT-JIS. SHIFT-JIS can encode Japanese and English text, but it cannot encode text from Turkish or Russian languages. That's why Unicode was invented. Unicode can encode text from many many different languages at the same time. To display the text in LabVIEW Unicode mode, you must convert the text into a Unicode encoding first. As a starting point, read the link I posted earlier (https://decibel.ni.com/content/docs/DOC-10153 ). I haven't tried it yet, but the example under "Converting ASCII Strings to Unicode" should let you display your Japanese text in LabVIEW's Unicode mode. (I don't think it will correctly convert your Turkish and Russian text, though. But anyway, try it first, and let's do this one step at a time. Text encoding is a moderately complex topic, and you'll probably need a few days to fully understand your problem).

Hi, What encoding does your OCR software use? Is it UTF-8 or UTF-16 or SHIFT-JIS or something else? To display Unicode text in LabVIEW, you must give it Unicode data. If you provide SHIFT-JIS text but LabVIEW tries to interpret it as Unicode text, then the interpretation will be wrong. This page might provide more insight: https://decibel.ni.com/content/docs/DOC-10153

I agree with drdjpowell. The JSON standard says (emphasis added), "An object is an unordered set of name/value pairs." This library is standards-compliant and does not need to be changed. The problem lies in the API you're communicating with. Send its developers a bug report and get them to fix it. The world will thank you for it

@jdsommer: Thank you for your detailed and open explanations. Our current project (which doesn't need a wide range of data types) has been implemented using h5labview, so it looks like I won't be able to try out your toolkit for now. I do agree that high-level convenience APIs make a noticeable difference to a programmer's job.

Congratulations on your milestone! Could you tell us more about your toolkit? Your website says, "Several attempts at LabVIEW interfaces to HDF5 have been produced over the years. LVHDF5 is the most complete and flexible interface available". What advantages does it offer over the other attempts, like h5labview? (I notice also that LVHDF5 cannot be co-installed with h5labview) I work for a systems integrator, so we often need to interface with the non-NI world. HDF5 is a popular format in the scientific community. In our current project, we had to interface with the client's data logger, which provided us with HDF5 files. Our job was made much easier thanks to 3rd-party LabVIEW bindings.

A game: https://github.com/mrhappyasthma/Snake A measurement system: https://github.com/Naviss/Oto A LabVIEW IDE plugin: http://sourceforge.net/p/lv-cct-tool/code/ci/default/tree/ A library: http://sourceforge.net/p/h5labview/code/ci/default/tree/ (I haven't used any of them except h5labview, so I can't give you an assessment on their quality) If you want a good resource on LabVIEW tricks and designs, I recommend The LabVIEW Style Book by Peter A. Blume. He walks you through sample projects, points out their strengths/weaknesses, and provides lots of useful guidelines.

Good question; I've been wondering about this too. A nice application would be adaptive and type-safe variant-attribute dictionaries.

This isn't code review per se, but LAVA does have a Code Repository for people to share their work: http://lavag.org/files/ You can also search open-source hosts (e.g. GitHub, SourceForge) for projects written in LabVIEW.

I concede, it has never crossed my mind to try this.. :-D

+1. Calling something "sub" when it's not sub-anything feels silly to me. On the other hand, reeducation sounds like an uphill battle. For an alternative: How does "Child VI" sound? This makes sense too, actually -- VIs are "Virtual Instruments" after all, and were originally designed to be software versions of hardware instruments. The root cause of AQ's problem is that people don't think about the meaning of the name "subVI". But on a related note, the name "VI" itself is extremely overloaded. VIs started off as Virtual Instruments, but have since expanded to become all kinds of things. SubVIs, Polymorphic VIs, Global VIs, Control VIs, XControl Method VIs have very little to do with instruments. So now we have a construct whose name is "Virtual Instrument" but whose meaning is "One of several forms of LabVIEW code"

So that they don't burn out from overwork, and so that I can pay less wages P.S. For humans, I endorse the former, not the latter

Hi, Your understanding of "." and ".." is correct, don't worry LabVIEW treats library files as folders. The URLs are relative to the "inside" of that folder. Notice that: The class private data's URL is "Setting Element.ctl" (no "../"!) The VI's URL is "../Pseudo Array - Remove Row.vi" Where are the .ctl file and the .vi file on disk? The .ctl file is embedded inside the .lvclass file. The .vi file is not embedded -- instead, it lives one level above the .ctl file, on the same level as the .lvclass file.

Oops, I misread Wolfram Alpha. You're right, 254688 seconds is almost 3 days.

Milliseconds relative to what? Relative to the time when the controller started running? Relative to midnight of 1 January 1970? Something else? 0x0F2E3B2D is 254688045 in decimal. 254688045 milliseconds is about 8.8 hours. Had your controller been running for 8.8 hours when you captured that timestamp?

Hi, It sounds like the primary problem that you want to solve is the problem of a misbehaving IDE, and you have chosen LVOOP as your mechanism for working around that problem. Is this correct? Some good questions to ask yourself are: From your primary problem's point of view: Will replacing enums with classes make your IDE problem go away, without introducing new IDE problems? From an architectural point of view: Which approach feels more sensible to you -- your existing enum-based system, or your proposed class-based system? I agree that your first proposal feels weird: a "Mode" sounds like it should contain config information and parameters, but it shouldn't perform any actions itself. Thus, I'm also not convinced that the Parse method belongs in the Mode class. (Of course, this is also a matter of taste -- I'm sure there are others who are happy to use this approach) Having each Mode subclass report BytesToRead back to the caller sounds quite reasonable, but only if every current and future Instrument subclass is expected to read the same number of bytes for a particular Mode. (Would there be any cases where different Instruments read a different number of bytes for the same Mode?)

For the record, the correct way to do this from scratch is: Pass a reference of LabVIEWClassControl (not LVClassLibrary) into the "vi object class" input of New VI Object Save the newly-created LVClassLibrary object to disk Pass the path of the LVClassLibrary into the "path" input of New VI Object