LabView Programming :: Portland OR, Seeking a local programmer to assist with code and application develop

I am looking for someone to professionally develop some code I've cobbled together. The
'program' I have developed has received some acceptance within my
larger team, and I am hoping to bring in an external expert to assist
us with streamlining the code and creating a stand-alone executable.
There is no real DAQ, just data manipulation.
We are looking for LOCAL PROGRAMMERS only please. I would like to meet with any applicants in person.
Please PM me on this forum with your resume/expertise...
Kind regards,
Geoff

Geoff,
Thanks for the post. Could we have an email contact for you? Or perhaps you could send me an email at jimlaudie-at-gmail-dot-com and I could reply?
Best of luck,
Jim

Similar Messages

Error 1097, but unfamiliar with code and programming

USB device (Hantek DSO-2090 USB Oscilloscope) came with .dll and sample Labview file. It wasn't working until I applied a path constant to each Call Library Function Node, yet the largest one always seems to yield Error 1097. Not sure why, but I'll include everything. Please help!
Attachments:
DSO2090.zip ‏85 KB

Actually wrong calling conventions quite often crash instead of causing error 1097. Error 1097 can have lots of causes but one of the most common is that the programmer has not preallocated array or string buffers used as output data before calling the C function. Most LabVIEW programmers are so used to LabVIEW handling array and string resizing automatically, that they don't even think about that this could be different when dealing with the Call Library Node. But here the external C code has normally no way of resizing such arrays to whatever size it needs and LabVIEW has no way of knowing what size the C function requires for the buffer. So there needs to be the programmer who deduces that information from function documentation, intuition, experience and sometimes simple trial, error and crash exercises to make this explicitedly.
I took a quick look at the VI in the OP and I was truely appaled by it's lack of structure and architecture. This is not a LabVIEW example to show off for sure. Nevertheless, based on the claim of the OP that the LARGEST node causes the error, (talk about clearness in communication caused by such a spaghetti diagram) I assumed he meant the dsoGetChannelData() CLN and that indeed has two array inputs that are meant to be filled by the function. They are connected to two hidden array controls containing 30000 elements of default data each, so as long as the function does not try to return more than 30000 samples for each of the two channels, this should not be the problem. But I'm not sure if this oscilloscope will ALWAYS return exactly 30000 values for each channel, or if this number can be adjusted somehow. It's however the only thing I can say based on the claim that the largest node causes the error. And digging into this deeper requires the DLL documentation and lots of time, which I don't plan to invest in such a poor piece of software.
The reason that he needed to define the path to each node is that the DLL clearly is not located in a standard nor fixed location. Windows will never search any directory in the Program Files directory for DLLs, unless that directory happens to be listed in the PATH environment variable. And the Program Files directory path can change based on Windows bitness, system administrator configurations and more. In order for LabVIEW to find the DLL on any system, the DLL has either to be:
1) in the same directory as the VI or project file
2) in the executable directory (where labview.exe is or yourapp.exe for a built application)
3) in the $(System) directory
4) in the $(Windows) directory
5) in a directory that is listed in the PATH environment variable
But moving around DLLs without knowing what you are doing can make the DLL unloadable as it may be missing dependencies that way.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Has anyone experienced Labview 8.2 crashing when attempting wire a cluster filled with object and task references?

I am getting a complete shutdown (crash) of Labview 8.2 when placing the wiring tool over a cluster that is filled with task and object references. The crash occurs on all computers I have attempted it on and happens throughout all VIs in all classes that distribute multiple references throughout the VI using a cluster. The entire project I am developing is programmed in GOOP. Has anyone experienced anything like this? I have provided a screen shot of the place where the crash is generated. Let me know if anyone has any insights.
B
Attachments:
LV screenshot.JPG ‏156 KB

There are several known crashes with LVClasses. One of the easiest
fixes is to load your application into memory and then hit
ctrl+shift+click on the Run arrow of your top-level VI. Then do
File>>Save All. You might also try selecting that wire (with the
selection tool -- use the Tools Palette to explicitly select a tool
other than wiring) and deleting it and then rewiring those terminals.

Mod_wl.so "Thread Local Storage" load error with Apache and WL 7

I'm using Apache 1.3 and WL 7.0, and after configuring Apache to load mod_wl.so,
I get the following error when starting up. I'm using the mod_wl.so that is
for hpux11.
Thanks for any help.
$ ./apachectl start
/usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage: /usr/lib/libcl.2
/usr/lib/dld.sl: Exec format error
Syntax error on line 1053 of /opt/apache/etc/httpd.conf:
Cannot load /opt/apache/lib/modules/mod_wl.so into server: Exec format error
./apachectl start: httpd could not be started

Sunny,
When you build apache on hpux, you should do the following before the
configure:
export CFLAGS="-lstd -lstream -lCsup -lm -lcl -ldld"
Regards,
Eric
"Sunny Yee" <[email protected]> wrote in message
news:[email protected]..
>
I'm using Apache 1.3 and WL 7.0, and after configuring Apache to loadmod_wl.so,
I get the following error when starting up. I'm using the mod_wl.so thatis
for hpux11.
Thanks for any help.
$ ./apachectl start
/usr/lib/dld.sl: Can't shl_load() a library containing Thread LocalStorage: /usr/lib/libcl.2
/usr/lib/dld.sl: Exec format error
Syntax error on line 1053 of /opt/apache/etc/httpd.conf:
Cannot load /opt/apache/lib/modules/mod_wl.so into server: Exec formaterror
/apachectl start: httpd could not be started

Local Director http probes with URLs and http redirect mode

I am trying to configure http probes on my Local director 430 running 4.2.3
I am using http redirect mode so the Virtual is bound to URLs not REALs with are linked to DIPs which are bound to REALs. So far the probes seem to not actually do anything. Does anyone know if the probes are compatible with URL redirect loadbalancing. And if so how one would go about configuring it.
Thanks for your help.

keepalive can be used for the probe notification in this case.
Check the following url for details.
http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/bsccfggd/services.htm#xtocid727448

Problem with servlet and application program

i have this error appearing in my browser...
i have this feeling it is about the application, but if application alone, i now having some trouble running it, once i bind it with an applet i always have this message:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
java.lang.NullPointerException
     exString.triming(exString.java:12)
     exString.geta(exString.java:113)
     forplay.play(forplay.java:9)
     textServe.doGet(textServe.java:14)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.apache.catalina.servlets.InvokerServlet.serveRequest(InvokerServlet.java:419)
     org.apache.catalina.servlets.InvokerServlet.doGet(InvokerServlet.java:133)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs.
i know this is a simple problem...
how come my application is having some difficulty in running my application...
this servlet by the way is a get parameter base...

Its caused cuz ur exString is null..
rgds
shanu

Livonia, Michigan LABVIEW PROGRAMMING POSITION

Livonia, Michigan LABVIEW
PROGRAMMING POSITION
Revolutionary Engineering,
Inc. is dynamometer testing systems integrator and service corporation. We provide systems and services for the
automotive industry as well as in-house dynamometer testing. We currently have a position open for an LABVIEW
Programmer. A brief description of the
positions responsibilities and benefits are summarized below. If you are interested please e-mail us at [email protected].
Position Available
Controls Engineer /
Programmer
Requirements
Bachelors Degree in
Electrical Engineering or Computer Science
LABVIEW programming experience
a most
CAD Experience a plus
Experience with Microsoft
Office Software
General knowledge of shop
procedures and tool usage
Ability to work with other
technicians and engineers
Ability to communicate
technical information both verbal and written
Responsibilities Include (but not limited too)
Develop control and data acquisition software for
dynamometer testing using National Instruments LabVIEW.
Develop third-party software drivers and
interfaces for industry-standard software such as ETAS INCA, and MATLAB
Simulink.
Setup control modes for in-house and customer
test cell operation.
Assist test engineers in designing control
strategies for various testing scenarios.
Recommend new ideas and processes where needed to
improve software and testing operation.
Commission and troubleshoot dynamometer test cell
software and instrumentation issues.
Evaluate project quotations, and develop project
requirements and development scheduling for automated test cells.
Maintain customer relationship throughout project
development and warranty periods.
Evaluate problem resolution and development
progress patterns.
Coordinate with suppliers on issues with development
platforms as they arise.
Coordinate technical information and items under
development among team members.
Maintain software releases using Source Code
Control databases.

Must have authorization to work in the United States on a full-time basis for any employer

I have some software problems of running matlab script node in the LabVIEW program.

Hi there,
I wrote a simple matlab code, like x= 1, y = x*2. Then I tried to put them into matlab script node in LabVIEW.
However, when I ran the program, I couldn't run and Labiew show some error.
Then I tried the method talked before on this forum. Please see the following link.
http://forums.ni.com/ni/board/message?board.id=MathScript&thread.id=571
I followed the instruction and open the "command prompt," type some commands then I could run the program, and simultaneously, the LabVIEW program open "Matlab command line window" and run my labview code. However, if I didn't use the command prompt, the "matlab command window" will not be opened by running the labview program. It would just show some error. And even if I turn on the matlab program in advance, I still couldn't run the labview program.
Is there any effecient way to deal with this problem without using "command prompt?" Because I try another PC with both matlab and labview installed on it, I "can" run my simple matlab script node on it, and it will open the matlab command line window automatically by running my code. Therefore, I thought there might be some software linking problems in the previous PC I used . Do you have any ideas?
Thanks in advacne.

This board is for Mathscript, but you seem to have a matlab problem. You should probably post in the LabVIEW forum instead.
What is your LabVIEW version? What is you matlab version?
LabVIEW Champion . Do more with less code and in less time .

Should the LabVIEW program be reduced to the speed of data collection?

I'm using a LabVIEW program created by Ocean Optics for a
Spectrophotometer probe with is run through the USB port. The problem
occurs when we attempt to collect data over a time frame of one
second. For some reason the whole LabVIEW program will begin to
operate at the speed of data collection when we try to run the VI with
an integration time of +500 ms. If anyone would be able to offer any
kind of explanation or theory it would be greatly appreciated. Thanks
for any and all help.
Daniel

Dear Daniel,
since LV has no support for USB this must be done through a DLL or Active-X control. A call to a DLL or Active-X method is a synchronous node in LV, that means LV will go on executing when the call completes.
My theory of your problem is that the program makes such a call and it would take that time to collect the data in the DLL or Active-X control. If you have only one loop in the program and do not use dynamic loaded VIs through the VI server than the program seems to hang on each of this calls.
I hope this helps
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

How to create a labview program and use it as a compiled prgram

I am a mechanical engineer, and I have some formulas and equations that I used to obtain maximum thickness of pipelines and also in the design of steel structures, what I need now is to use Labview to put these huge number of formulas in one program. I can do that, but the problem after I make the program I want it to be used by anybody on any PC which is not installed Labview on it, and that is the problem, I don't know if I can make an excel sheet or something to be the interface that can be used by the user, and if I can, I hope that I can have the details of who to execute that.

LabVIEW interacts with Microsoft Excel using its Active X hooks. Anything Microsoft has exposed in the Active X API, LabVIEW can do. This includes opening Excel, reading values, writing values, etc. Doing this can be tricky for a novice programmer and NI has created the Report Generation Toolkit for Microsoft Office that plugs into LabVIEW for a more streamlined experience.
The Developer Zone is a good place to start a search looking for Active X Excel examples: http://zone.ni.com/devzone/fn/p/sn/n16:en/sb/navsRel?q=microsoft+excel+labview&x=0&y=0
As well as the Forum: http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=2391
Reading and writing to an open Excel file could become quite cumbersome however. If the Excel file is open and the user is interacting with it, writing to that same file will return an error saying that the file is currently open. It would have to end up like this: User opens file, modifies some fields, saves file and closes excel. LabVIEW program opens file, reads fields and writes a result, then opens Excel to display to the user the result.
Is there any specific reason you want to use Excel as your user interface? You can use the front panel of a LabVIEW application to enter the data and display the results, all while writing this data to an Excel file for logging/reference in the future.
Message Edited by Stephen B on 11-17-2008 01:26 PM
Stephen B

Labview program interface

Dear all,
I have a some problem in running my labview program.
I intention is to generate an output voltage by using my machine (by Nanonis), thus I am using their program in Nanoinis program interface. However, I might have make some connection wrongly somehow as it is not working. I want to try controlling the duration of the output voltage, maybe like 10 seconds. However, I must have made an error somewhere in the program as no voltage is generated
I would appreciate if anyone can advice me on this matter.
Thank you.
Regards,
uranus999
Attachments:
RelayOutput(Analog output) (trial).vi ‏19 KB

Dear Lynn,
I understand that it might be difficult to understand with looking at the Nanonis sub vi's. Sorry about that. If I upload a PDF of the block diagram, would it help at all?
Anyway, I should clarify one thing about the program. Actually, previously, I have use the similar block diagram but I have tried to generate the voltage by using a DAQ. This time, since I intend to use the Nanonis programming interface (replacing the wire lines) from the relay output to the programming interface-Open App ref instead of the NI daq. I expected that it should work but unfortunately, although the program work for the NI DAQ, it doesn't for the Nanonis programming interface. Thus, I am seeking advice on what might had happen and what I should do. I am still a new in writing Labview programs, thus I really do appreciate to get all the advice that I can get.
Thank you.
Regards,
uranus999

How to deallocate memory used by the labview program?

Hi,
I have bulit a large application in labview 2012 that uses a couple of subvis, local and global variables, some uninitialized shift registers (functional global variables) and some c++ and .net dlls as well. When I open my application the memory usage shown at Windows task manager is around 1.4GB. After running the application and enabling all processes used in the application, the memory usage goes up to 1.55GB but when i stop the application, memory is never released/deallocated until i close the application plus exit labview. Can you suggest how to deallocate this memory? and how can i use the request deallocation function for this application? labview help says i have to place it inside a subVI for which i want to deallocate memory. But i have a lot of subVIs used in my application. I tried placing it in the top level VI and called it after stopping all processes but it didn't work... I am also closing references to all of the .net dlls at the end. Any workarounds??
Thanks

sandee wrote:
When I open my application the memory usage shown at Windows task manager is around 1.4GB. After running the application and enabling all processes used in the application, the memory usage goes up to 1.55GB but when i stop the application, memory is never released/deallocated until i close the application plus exit labview.
You already got some good advice. One thing that was not clear was how you are measuring memory. Since the task manager is capable of showing the memory used by LabVIEW alone (you simply need to look elsewhere), and you said that the memory gets released when you exit LabVIEW, you gave the impression that the 1.4GB was the LabVIEW portion.
OK, so a couple of hundred MB used by LabVIEW is really nothing to worry about. Are you running into memory or other performance problems? What are the symptoms?
sandee wrote:
I have bulit a large application in labview 2012 that uses a couple of subvis, local and global variables, some uninitialized shift registers (functional global variables) and some c++ and .net dlls as well.
We really need to see some code. It is very well posssible that you have a lots of unecessary data copies in memory due to sloppy programming. How big are the data structures? Do you use local variables for big data structures? What does the program actually do?
LabVIEW Champion . Do more with less code and in less time .

CPU usage is 98% when running my exe labview program

Hi
I have made an executable and installer for my labview program. When I install and run, the program uses a lot of cpu - almost 100%, even when the program is not computing. I recently changed over to LVIEW 8.2 from LVIEW 7.1. I had none of these issues with 7.1.
Programatically, I use a state machine to continuously execute the program. I also use a couple of while loops as slaves to plot the results processed in the main loop. In all while loops I have a 'Wait' until next ms' vi to prevent the program using all the cpu, but it doesnt seem to be helping in LVIEW 8.2. This is somewhat strange.
Can someone suggest what may be happening? and are there any methods that I can use to reduce cpu usage of my program?
Cheers
RVR

It will be impossible to really troubleshoot this without a lot of additional infomation.
Is the CPU usage only high in the built application, or is it also high if you run the same program in the 8.2 development environment?
Was the 7.1 program exactly the same, or did you make any modifications since?
Are you running 8.20 or did you upgrade to 8.2.1?
What does the program actually do? Does it interact with DAQ hardware? File I/O?
What does the program do when it is "computing"? Is the CPU use even higher then?
Is there also a wait statement in the main while loop?
What is your OS (windows, linux, mac, etc.)
Is your computer reasonable for the task. Enough RAM, etc.
How do the various loops communicate with each other? (queues, local-, global-, shared- variables, etc.)
How much data is exchanged between the loops? At what rate?
Do you use fixed or variable size arrays?
Can you give us a more detailed overview of the code?
How is the memory usage?
have you done any profiling?
LabVIEW Champion . Do more with less code and in less time .

Can Labview Programs run from the Windows System Tray?

Does anyone know if Labview Runtime executables can be run in the Windows System tray? Any help would be appreciated.
I'm creating a program that I want to run in the background, not visible on the desktop or taskbar.
Thanks,
Tom

Requirements Price: $29.95
Application Software:
LabVIEW 7.0+
Toolkits Software:
Additional Software:
Language's:
LabVIEW
INVtray LabVIEW Toolkit allows the programmer to create a LabVIEW program that can be hidden from the task bar and accessed through the System Tray. Comes with a sample VI that demonstrates all the features of the toolkit.

HP4275A can not pass self test after running the labview program

I am using Labview to control HP4275A LCR meter. The Labview program is just the instrument driver for the HP4275A, and it works great. Before running the program, the instrument can pass both Open and Short test perfectly. But after running the program, it can not pass self test, neither Open nor Short. I don't know why?? Is it relative to my Labview program??
Thanks

Thank you so much for your help. Yes, the instrument is in Local after running the instrument driver. In normal Open self test, just choose Capactiance as the Display A, and leave the four output terminals open then press the Self Test button. The Open self test will start and "OP" will be shown in the DIsplay A window, after 2 seconds, the open test will be finished. If something abnormal, the number of the abnormal step is displayed in Display A. Similar with the Short test.
The problem I had was: before running the instrument driver, the self tests pass; but after running the instrument driver, the Open and Short test show abnormal, Open test is abnormal at step 17, and Short test is abnormal at step 24.
And the instrument driver is only write commands into the instrument and then read back measuring values from it. Nothing else. So I am not sure if the problem is my instrument driver.
The weird thing is the problems happened several times and then if I do the Open and Short self test again after running the instrument driver, both pass. I am not sure whether the problem will come back or not.
Ia there any help??
Big thanks

LabView Programming :: Portland OR, Seeking a local programmer to assist with code and application develop

Similar Messages

Maybe you are looking for