Dr Tallman

I have installed the VI package manager and combed through the OpenG packages but had a hard time finding anything along the lines of "write/read control/indicator values" etc. Could you help me find where they may be located? Greatly appreciated.

Yes they did. The CAR number is 297680.

Is there any way to read (and edit) files generated by flattening the values from the Ctrl Val.Get All (Depricated)" invoke node? I have borrowed this piece of code which works great but I would like to edit it off line and then read it again in an opposide action.

For those who may be interested, I finally found out what was happening. After working with NI and going back and forth, it was considered a glitch (apparently also happening in versions of LabView more recent than mine, 8.5). I discovered that putting anything on top of the chart (label, line decoration etc.) caused the problem. The lines and labels you see on my chart were added on top as decorations and lines. Removing them, resulted in perfect behavior.

The Strip Chart and Scope Chart modes work exactly as advertised. The Scope chart keeps the old data about 1/2 the time.(see below). I have tried playing with the "Chart History Length" (is that the same as the Chart Buffer?) but that doesn't seem to have any effect.

Correction! The sweep chart isn't actually erasing. It is taking the last value at the right border and quickly plotting it across the entire chart (thus erasing the old data) and continuing normally from the left. This is what it looks like at that point. Any ideas why that would happen? Thanks again. Richard

I have built a simple patient monitor that "looks up" and plots four tables of numbers. The basic diagram is shown below in Sweep Chart.JPG. Also, the VI I use to read the tables is shown in Waveform Read.JPG. These are relatively short tables containing between 300-400 elements. Alone, this works very well but when put into a larger system, two things happen that are unexpected. 1) The sweep chart erases after it reaches the right border. This doesn't happen all the time but seems almost random 2) the chart hesitates after reading each table. This only happens in the vi. that has an A/D option. This does not happen in the exact same vi that uses a numerical control instead of the A/D input What external conditions would give rise to these two problems? By the way, I am using the NI USB-6009 with a DAQ Assistant Express vi. sampling 2 channels. Thanks in advance for your help. Richard Tallman

An RS-232 option would be acceptable but I really did want to have a completely wireless option. A little background. I have developed a patient simulator designed to work with a heartlung machine. It consists of a series of reservoir bags, tubing etc. and pressure and flow sensors connected via A/D. A heartlung machine attaches to the simulator and when bypass is initiated, the simulator mimics a patients response. The simulator output is the monitor (1.jpg). Also, running seperately is a VI that the "instructor" is running (2.jpg). This VI is used to keep track and evaluate the "student" running the heart lung machine. This second VI is designed to work on a tablet and uses handwriting recognition to input comments. My plan is to use the "Instructors" VI to change certain controls on the Simulator. Sliders, booleans etc. Both of the computers I used have WiFi but I don't want to use any external network. Thanks for your Help. Richard

Is there a straightforward way to establish direct communication between two computers (WiFi or bluetooth) allowing a vi on one machine to control a vi on the other? I need to establish this capability in places without internet access. Thanks. Richard Tallman

Reed, Thank you for your help. I was unaware of the update. After rerunning the translation, the wires that were broken before appear to be fixed although several new broken wires have appeared. I suspect that the CGD vectorSelectorNode.vi is the culprit. Thanks again.Richard

Does anyone have any experience using the Simulation Translator (found in Simulation Module v2.0) to convert MatLab Simulink models to LabView? I am trying to convert the PHYSBE model which can be found at... Physbe Model Besides creating messy vi's with many broken wires, it created two sub vi's called"CGD vectorSelectorNode.vi" which are password protected. They are the two white vi's in the diagram above. I cannot find anything helpful in the NI documentation. I would appreciate any insight. Thank you. btw, I am using LV 8.0. Richard Tallman Associate Professor The Ohio State University