Tim_S
Members-
Posts
873 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by Tim_S
-
I was referring to basics versus the example this topic started with (so a "101" course, though not necessarily a class). The class jgcode linked to would be a good introduction. Tim
-
Realized that refnums would have been a better analogy, but... Highly recommend going to LVOOP 101 and starting there. But, to answer your question, you are looking at the private data of the class. The class isn't required to have any private data, hence why it can be "empty". A child class will inherit all of the data from the parent class plus everything it defines. So, for example, a vehicle class can have the number of passengers in it. A child class of the vehicle could be car and boat. The car would have wheels, brakes, etc., and the boat would have sails, rudder, etc., defined in addition to what makes them vehicles. Tim
-
Actually it's not breaking the rules. The way inheritance of objects work it is the same as if you wired a I16 into a queue set up for a I8 (well roughly). In my example both are numeric types and LabVIEW type casts for the correct type. In the code you are looking at both are "UI Command Manager" type and LabVIEW type casts appropriately. Tim
-
The typecast would occur if UI Initialize is a child of UI Command Manager. Any chance that's the case? Tim
-
I've not seen that error before, however a former coworker has done long-term data collection with success. He created a highly packed binary file. The data collection was setup to return counts instead of voltage. The unscaled counts were saved to file, thus requiring less space than a single or double floating point. The DAQ card was 12 bits which meant that 4 bits of the I16 was unused data. He took out the unused 4 bits and packed the 12-bit values together, thus further reducing the file size. Downside to all of this is the processing to save and read it back and you can't pull it into something like Excel.
-
It seems like everyone is commenting on software. I believe the rules would change dramatically if you ever specify hardware to be used.
-
Only if I can plead the fifth...
-
I have to agree with Mark: have you put the offending subVI in "always include" section? Another thought is to go into the Source File Settings and navigate to your subVI; from there you can change if the block diagrams get stripped, window appearance, execution, etc. Tim
-
How do you make your application window frontmost?
Tim_S replied to Michael Aivaliotis's topic in User Interface
You're looking for the SetWindowPos function from the user32.dll. -
Have you tried setting the "Enable Debugging" flag in the build specification? This lets you put breakpoints and lets you watch code execution in the executable or DLL (using the Operate->Debug Application or Shared Library menu option). Your executable won't run quite like it will without the option turned on, but it helps with the kind of thing you're describing. Tim
-
A very big second on that one. Debugging why executables don't work like source code is a big headache to me. Tim
-
Man, nothing so cool sounding as other people. I've got cleanup of a NVH tester for a automotive transmission, about to start debug of a functional tester of a medium-duty transmission, and upgrading the calibration service used in our core test executive software in between. Best not to kill the operator... too much paperwork. Tim
-
I'm confused; why wouldn't it? If you have two To More Specific Class primitives where class A goes into the reference of the first and into the target of the second, and class B goes into the other inputs, then you should get an error on both only if there is no relation between the classes. Tim
-
Have you tried using "To More Generic Class"? You should get an error if it's not a child. Tim
-
Do a google search on computer controlled relay or look at the Andurino documentation for schematics on how to do what you describe. Connecting a TTL directly to a relay would be bad. Tim
-
Hrm... Why not use a temperature switch tied to a digital input? Tim
-
Issues TCP-ing with a C program on same computer
Tim_S replied to Cat's topic in Remote Control, Monitoring and the Internet
Have you tried running in compatibility mode on Win7? Tim -
Heh, yea, yet it is surprising how many times it's been that long especially when there are multiple projects going on at once.
-
I have a composition book of descriptions and flowcharts and (pseudo-) state diagrams and UML models and K-maps and ... well, you get the idea. It helps me think through to a good implementation of the system and writing it down ensures that I'll remember (or have a good reference) to what I was thinking a month ago before something interrupted me. Tim
-
Issues TCP-ing with a C program on same computer
Tim_S replied to Cat's topic in Remote Control, Monitoring and the Internet
Not a problem, especially as this is related to something I'm working on! Tim -
Issues TCP-ing with a C program on same computer
Tim_S replied to Cat's topic in Remote Control, Monitoring and the Internet
LV 2010 on the same machine ran for 2 hours with no signs of stopping. Tim -
Issues TCP-ing with a C program on same computer
Tim_S replied to Cat's topic in Remote Control, Monitoring and the Internet
I've had the VIs running on a WinXP SP3 Core2 Duo 2 Ghz machine with 2 GB of RAM under LV 2011 for about 1-1/2 hours with no sign of issues. Can try with LV 2010, but don't have 9.0 installed. Tim -
LabVIEW is a programming language and not something that you script, so it's going to take some work. You'll want to learn about how to create a state machine. I would check the manufacturer has "LabVIEW drivers" or example VIs to communicate with the optical attenuaters and the other hardware you're looking to control. The Basics I and II courses will get you familiar with how to work in LabVIEW development environment. Make good use of the examples that ship with LabVIEW and look through the different functions pallets to get a good feel for what is there. Tim
-
What's New in LabVIEW 2011: Accelerate Your Productivity
Tim_S replied to Phillip Brooks's topic in LabVIEW General
Yea, don't is the only option. It extends beyond the source code from my experience to where you have to compile a LabVIEW DLL in the same version of LabVIEW you are using to call it. Tim