Just a quick note to anyone who might be using LeCroy IVI drivers (at least
for the Wave Runner 6100 oScope) with LabVIEW. It appears that if you try to
recompile them for LabVIEW 7.1, they won't work. It shows up as an IVI Error
Conversion VI that won't run (broken arrow). Not only will it not
I just got the update in the mail for the Developer Suite. I'm sure many of
you will be pleasantly surprised to find out that ALL Professional versions of
the various Developer Suits now include the following:
LabVIEW State Diagram Toolkit 1.0
LabVIEW VI Analyzer Toolkit 1.0
LabVIEW Express VI
One other detail to think about.
Are you intending to use this code for internal use only? If so, then why
should anyone care how you get your code? I work for a large defense
contractor as well, and no one seems to mind as long as I get the job done and
actually have all the source. (although
I am posting this on behalf of a friend.
There is a job available here in Charlottesville Virginia for a test
engineering position at a company that makes pharmaceutical equipment.
Basically they need someone NOW. The candidate would NEED test engineering
experience as well as be a competent
Sorry for the late response.
I just discovered another option for standardized data in test applications.
ATML is just XML with some standard formats for ATE applications. Some more
work is needed, but you can take a look at what is available at
http://www.atml.org/. (you will need to join to
I wonder if the following would be useful.
How about a tool using a tree view control, which would present a hierarchical
overview of a LabVIEW application in the left pane of a window, and detailed
VI/Library information in the right pane. One of the details presented could
be where the VI is
I hope no one minds me bringing up LCOD again - it just seems like a really
good solution here. :)
LCOD (LabVIEW Component Oriented Design as explained in the book A Software
Engineering Approach to LabVIEW) provides a very elegant solution to this
problem. Using LCOD one would encapsulate all
It may not be considered a bug, but it is a royal pain in the you know what!
It essentially makes the ability to add color highlighting to changing text
too difficult to be worth the effort in most cases. (in my opinion)
This brings up another problem I've had. Trying to color text in
Right - of course. There I go spouting off again without thinking first.
Like you say, an append method might make what we desire possible. I still
think we should be able to accomplish something similar using tables and
arrays though.
John Howard
Michael Sachs 02/18/04 12:49AM
Problem
whenever a DLL implementation question
pops up. I'm sure I can speak for many other info-LVers in thanking you for
your regular contributions!
Cheers!
John Howard
Rolf Kalbermatter 02/14/04 07:54AM
Howard, John [EMAIL PROTECTED] wrote:
I am considering using a PCI card (Sabtech NTDS interface
Uwe Frenz 02/13/04 02:49AM
...but almost all dual monitor cards should work well too. ...
This may be true in general, although I saw one dual monitor card do nasty
things. The brand name was something like Apien or Apex or something like
that. (does that sound familiar to anyone?) It was
I seem to have more limitations imposed on me by the monitor than the video
card. According to the G550 specs, it has dual integrated RAMDACs, a 360MHz
Primary and a 230 MHZ Secondary. It claims up to [EMAIL PROTECTED] on the main
display, but my monitor can't go that fast. Likewise, the
OK, I think I am in over my head. :)
I am considering using a PCI card (Sabtech NTDS interface card for those
interested), and it doesn't seem to have a nice simple DLL like I am use to.
Instead it has a kernel mode Windows 2000 device driver, and I am expected to
use ...normal Windows I/O
If any of you think you might use DAQ OPC on Windows XP computers, this email
might save you a whole lot of headache.
Those who have used the OPC server for NI DAQ, have probably had to mess with
DCOM security settings in order to get it to work. NI has some of this
documented on their web site.
One tip that I would offer is to consider using a Strict TypeDef Enum to drive
your state machine rather than a string.
Part of the reason for this is to prevent accidental coding errors such as
mis-typing a string or forgetting to implement a case. Also, if you further
develop your state
It lets you create state machine based LabVIEW programs by 'simply' drawing a
state diagram. You can switch between diagram view and code view. It
probably mostly useful for documentation, where state diagrams are needed.
It is not part of any version of LabVIEW, you have to pay for it
Rolf,
You were right about security for navigating the hive. I had to give
permissions at the HKEY_LOCAL_MACHINE\SYSTEM level before I could navigate
further down.
However, this did not fix my problems with OPC. I still get the same error
message when trying to browse OPC Servers on remote
17 matches
Mail list logo
