Kurt Friday

Hi Feri I'm not sure where you would find more examples for this particular instrument. Were you able to run the examples and get results? What type of examples are you after?

No problem, happy to help

Hi Adam As I understand it you have a VI running on one machine acquiring data under MAX 3.0.1 and you are trying to acquire on another machine using the same vi under MAX 4.2.1. Just a couple of questions. 1) What version of NI-DAQmx are you using on each system? You can find this out by going to MAX then expand the tree to display the Software versions. It may be that your hardware is not supported in the version of NI-DAQmx on the system with MAX 4.2.1 2) What acquisition hardware are you using? 3) Can you take a measurement on each system using the test panel? 4) If you are using NI-DAQmx tasks are they setup identically on each system? 5) Does your vi return an error? 6) You mentioned if it matters which breakout device you are using, what ones are you using? Also have you tried plugging the breakout device from the working system into the one that doesn't work?

Hi Brad I think the problem is that you are assuming that the +5V is referenced to AI_Gnd, its not its referenced to D_Gnd, so just include D_Gnd in your circuit.

Hey Mate LabVIEW executes callback vi's on certain events, take a look at this article on OpenG.org You could possibly edit the lv_new_vi.vi that is called when you select New VI so your new vi isn't called Untitled X.vi I haven't played with this but sounds like the way to go.

Hey David Ok, I didn't realize it was built from an example, so I've got it now. You are almost there, I'm able to get it working however there are a few issues that I was able to identify and may have contributed to it not functioning as expected. 1) Initialize your shift registers and feedback nodes. 2) Your PID isn't tuned properly try setting Inflow Rate = 1000 L/sec, Off Limit = 20 cm, High Level Limit (setpoint) = 10cm PID Limit = 5 I was able to get PID control of the tank, but its oscillating quite badly so experiment with the settings till you get it right. Some suggestions to make your code better. 1) You have subvi's with uninitialized shift registers, have an initialize Boolean that initializes the shift registers with appropriate default values. 2) Your subvi's are a little confusing as you are not following the connector pane convention of inputs on the left outputs on the right, if you are running out of terminals to follow the convention then try a connector pane pattern with more terminals or try using a cluster, ie your PID inputs could be input as a cluster. Hope this helps

Hi Ginos Take a look at the code snippet below it should guide you as to how to log N samples to the spreadsheet but continue to display. If you want to acquire a finite number of samples use the Sample Mode = Finite Samples in the Sample Clock and in your code check if the task is done using DAQmx Is Task Done.vi and if so terminate the loop as shown.

Yair has a good point, have a look at the colorbox option. To see how to use the LED.ctl just drop it onto your front panel, make it an indicator and then wire a numeric control to it. You will see that. 0 = Red 1 = Blue 2= Dark Green 3 = Yellow So your 4 states or colors map to a numeric value. To make the LED.ctl I started with a classic pic ring and then copied images of a Boolean LED that I had painted different colors. You can get the images of the Boolean LED by editing the boolean control and then copying the image component. Then paste it into the pic ring. For more detail about editing controls have a search on the NI site. I'm not sure about your other issue, the link you have posted appears to be broken

OK, Something clicked with this while I was having my coffee and Vegemite on toast. I think your problem is that your dynamic vi has dependencies on LabVIEW vi.lib, user.lib or instr.lib. The runtime engine doesn't have the capability to include vi's that are outside the vi's root folder, ie if you call a dynamic then all the depenant vi's and ctls must be in the same folder or they all must sit in a llb. So what you need to do is in your project create a Build called a Source Distribution for your dynamic vi Beta.vi that will copy all the dependancies to a distribution folder. I've included an example in 8.2 that demonstrates this. DynamicCallDemo.zip Included is the source and a build that demonstrates your issue and one that resolves it. The demo is dependant on OpenG Lib so included is Packages.vipc use VI Package Manager to install the OpenG Packages you need. Hope this helps

Hi Vane Take a look at this post and see if anything applies to your case. If you are still having no luck post an example of your code that duplicates the issue. Edit OK I just noticed an older post of yours regarding the same issue

Another way is to just use a pic ring, example attached. 4ColorLED.ctl

Hi PJM I haven't seen that before and I've played with scripting a bit. Can you define the scripting operation which caused the error?

Hey Norm A great tool I've found is the get and set linker info scripting methods. You could copy your subvi's to a new location and then run a utility that would look at the linkages of each vi, if the linkage points to a symbolic path but that vi exists within the folder hierarchy that you have copied to then update the linkage info to point to the correct or desired vi. Edit I couldn't help myself, I had to play with it. The attached will re-link all your subvis contained within a directory, hence remove the linkage to symbolic paths. Doesn't handle LLB but it could be easily modified to do so LVLinker.zip

I'd like to go to a wave function.

Ah, yeah forgot about that. I've updated the code and included a build. SpawnFP_2.zip Curry was OK, nothing special just some takeaway from the local, could have been a bit spicier. I made Beef Rendang the other day that was damn good, poked me right between the eyes.

Hi Feri Just browsing the NI Instrument Drivers and I found a driver for your instrument HP8714B This would be the best starting point, usually the drivers have a few examples that you could use to guide your application.

One vi is missing "Level.vi Also, can you be a bit more explicit in describing the problems that you are having with your solution. What tests have you done on your code that are showing the issue? Present as much information as you can that demonstrates that you have had a good go at trying to resolve the issue.

No prob mate Just having a beer waiting for a curry, I can squeeze one out. Have a play with this. SpawnFP.zip

Just put a case structure around the write to spreadsheet. If number of samples is less than or equal to 2000 then write to spreadsheet else don't.

Hey Ginos Have a play with putting the write to spreadsheet inside your loop but wire a path to it so it doesn't prompt you every time. Also set append to file = True. Have a tinker and see how you go.

Did you have any success with the software from Uni-Trend?

Try this

Do you mean that you may have more than 100 LED indicators working from the 1 input string?

What was the solution?