Chris Davis

Show us some of the code you've already developed and we will be more likely to help you out. LabView is a graphical language after all!

Thats a new one to me, where are these keywords defined in the project?

This VI is almost the same as yours, but more reusable. You'll have to add the Defer panel updates since you are doing lots of controls. Enjoy.

You might want to check out these examples. The one on creating a polymorphic VI will probably help the most, but you may want to look at all the examples to get a good feel for how to get started scripting. Enjoy!

It sounds like you are looking for a "No Hardware" version of your C code with minimal modifications to its operation. I haven't done this for any c projects I've done, but I have done it for LabView projects. If you make all of your hardware calls through a DLL with an API you create, then you can create a DLL to match that API and operate without hardware. This can be useful in debugging parts of the program without hardware, or if you have to access multiple hardware targets. I wouldn't try to create a C parser in LabView, you'll never get it right, and it will always be a question in your debugging process.

Perhaps you haven't looked at this card. Fast sampling rate, better resolution, simple connector, and DAQmx support! But no analog out. Anyway, usually speaking to your local NI rep (if you have one) can help you find a card / solution within your price range.

One suggestion. Take a look at the code behind the express VI you are using. Right-click on the express VI and click on "Open Front Panel". **Warning: You won't be able to edit this express VI as an express VI anymore once you do this, so you might want to make a copy of it before you open its front panel.** Once you have the express VI open, you will see a constant listing of the channels that you use in the express VI. Make this constant into a control, and make the "Dev#" part of the string controlable by your program. There are also DAQmx routines that will list all of the avaliable devices on your machine, and exactly what card they are before you try to use them.

CIN nodes are hard to deal with. If all you really want to do is work with an NI DAQ card, I would suggest using DAQmx. It will make your code much easier to work with. If you feel like you have to stay outside of LabView to do this, you should check out making a DLL. DLLs are much easier to find information for, and are more common, thus easier to get help on. You don't mention what platform you are working with (Mac, Linux, or Windows) and this will make a difference in who can help and how much help you get with your CIN. Along with your platform, you'll want to mention your compiler and LabView version. You may also want to search for help on the NI forums for CIN nodes, they have much more documentation and help information for these getting started type questions. Good Luck.

I found the locals to be friendly as well. The only problem I had on my trip to Toulouse was paying the cab fare the night I arrived. I either paid to much or to little, but the cabbie couldn't communicate the exact amount, so I think we finally got to the point of writing it on paper. That seemed to get the message across. My trips outside of Paris, to the countryside (not Disneyland Paris!) were my favorite, since there were less tourists around, and you could emerse yourself in another culture.

:laugh: :laugh: :laugh:

Right.... Sorry about the spelling, it has been a while since high school french. I've visited Paris twice, and Toulouse once. I really enjoyed the food/beer/wine in Toulouse. We also got to visit the Cit

Sorry about that, I've made an update to correct that. I can open the Empty Polymorphic VI just fine on my computer. I'm not willing to call the behavior you are seeing a bug, because it seems to be dependent on the fact that you have a FDS copy of LabVIEW. There may very well be a piece of code in the FDS that prevents users from editing a polymorphic VI, and causes LabVIEW to shut down in the process. I don't have a FDS copy of LabVIEW to even begin to debug this with. I also believe that you (and consiquently I) are getting into a legal gray area with what you are trying to do with my example. I'm not going to remove my CR entry, but I will ask you to stop the effort to try and add polymorphic VI capability to your FDS of LabVIEW. If you really need that capability please consider upgrading to the Developer Suite, or the PDS version of LabVIEW. That being said, I have provided this example as an example of what could be done, and you can explore other possibilities at your own risk. BTW, I added unique icons to each polymorphic subVI so that it matches the type of numeric control that the subVI will create in a scripting environment.

You'll have to give us a little more to work with. Perhaps you could post your code, or a screen shot of it, so we can try to help.

You might also consider relocating the CPU of the computer to a non-user accessable place. Such as in a locked cabinet. If the user can't get to the CD drive he can't (typically) load up a game. If the machine doesn't have access to the internet, the user will be hard pressed to find some way he / she could load things on the computer. You might also look at LitePC and thier windows xp lite product. In the end, there is only so much you can do, a determined user will (probably) find a back door. Good luck.

I wish I could change the format of the data file, but, for various reasons, I can't. Thanks for the help. I'll try this tomorrow. For future reference, I believe the function you are using in your screen shot was introduced in LV 8. Thanks! :thumbup:

amen to that!

I haven't looked at the code yet, but Mike is right. Clean it up then add it to the CR. Even if you are the only person who ever looks at it. If you have to put it away for awhile, someone else might get a spark from your example. As long as your CR submission is labeled as an example, I don't think anyone will expect it to be any more than that.

I've got a CSV file I'm trying to read with lines like the following: "Chris","Davis, Jr.","Nothing",100.00,80.00,34.10,"Nothing""Christopher","Relf","LabVIEW Expert",100.00,90.00, 50.10,"LabVIEW Expert" When I read this type of file into excel I get 7 columns, when I read it with LabVIEW I get 8 columns. I'm using a spreadsheet string to array with a comma delimiter. I know that I can seperate the file just like excel does, but I don't know the easiest and most efficent way of doing it. Any pointers? Thanks in advance...

I've also found that a willingness to move is a big plus to finding a new job. Unfortunantly having small children can, sometimes, prohibit this process. Still it is a good idea to look at the job market every once in a while to see where you stand, and if it would be worth it to make a big change. BTW, my current employer also values the degree more than the experience on new employees. I am part of our college recruiting team, and I always look for the "diamond in the rough" when I'm out recruiting. Sometimes you see one, sometimes you don't, but it is worth the time it takes to talk to people who want to work at your company.

I haven't used that package, but it looks like it is just a zip file you download and unzip. If it doesn't work for you, you'll have to post to the openg forums, or perhaps the original author can provide you some information here on LAVA.

You should be able to make "Number of Matches" high (>100) and get the actual number of matches out of the IMAQ Match Pattern VI. Each match will have a cluster of information with contains its position.

Check out the new CR Example (link above). It has an empty polymorphic VI as part of the zip file.

You have to create a blank polymorphic VI in LV 7, read it in as a string and replace the string constant on the diagram that represents the empty LV 7.1 Polymorphic VI. After you do this, the LV 7.0 version of the code will work. Check out my new CR Example with its lv7.0 version

Sorry, Its not possible to use my example in LV 7.0. NI didn't add support for this capability until LV 7.1. Take a closer look at this post (which you also posted in) for more information. Specifically take a look at the first couple of posts. EDIT: Well, now that I've tried it, it does work. I'll add the LV 7.0 version to the CR later today. Sorry I jumped to conclusions and assumed it wouldn't work.