Deleting broken wires crashes Labview 2010

Hi
I am down to earth after
enjoying all the nice features of LV 2010.
I randomly encounter
hour-glass hang-up when I try to delete broken wires. This is really
unpredictable as far as I have watched. I t happens if click on a broken with
the mouse or when I select a couple of those. It does not happen, if I use
ctrl-b.
When you try to delete it,
the hour glass comes up and the window is no longer refreshed.
I use the task-manger to
kill LV after
that a wild hard disk action starts, whoever initiates that ??
After LV-restart I usually
can recover a lot, but this make RAEL work almost impossible.
I a running an English LV
2010f2 on a German WinXP professional.
And Please, please patch
this as soon as possible.
Gabi
7.1 -- 2013
CLA

Hi Gabi,
I'm glad to hear that you are enjoying LabVIEW 2010! Can i ask what is the specifiation of the computer you are using it on?
This is because it might be that your computer doesn't have enough memory for this program.
Also there is a patch for LabVIEW 2010, in this link.
Hope this helps!
John McLaughlin
Insides Sales Engineer Team Leader
National Instruments UK & Ireland

Similar Messages

Mass compile crashes LabVIEW 2010

Before I go ahead and call the support line
Pentium 4
2.8GHZ
2GB RAM
XP 32 bit
Anyone have issues mass compiling an application code from 8.6.1 to 2010 SP1 whereby it would seem to work fine for quite awhile then crash?
I tries no cache on the VI and all other items are off.
It seems to happen even in subdirectories of the application.
I just installed 2010 SP1 and the device drivers and when I look at them in isolation they seem to be installed correctly.
I can also load the 8.6.1 application
Im just wondering if Mass Compile is running out of memory and is it known issue or am I discovering something.
I will attempt to log results on the next try.

Hey guys, this is Paul with Applications Engineering at NI.
I have reviewed your issues, asked around, and have a couple tips and questions.
First, if there is any chance you could post your project in a zipped format, then we could examine it on our end and see if we experience the same issue, which would make it easy to file a CAR on. If you are wary of posting your code publicly, you can PM me, and we can work out a way to upload it to our FTP server that only NI employees can access.
richjoh, in your posted Mass Compile screen, I see a VI being flagged as bad. When you open this VI on it's own do you experience this problem? Can you locate in that VI where it calls the NanoMsg.lvclass?
Second, to either of you, were the controls and lvclasses mentioned still referenced in your projects anywhere? Were they included in the dependencies? If not, once you restored these files into the project, find them in the
dependencies, right click them, choose "Find">"Callers". Where they still being called anywhere?
Alternative to your solutions, have you considered creating a new project and adding all of your VIs into the new project? I have seen this resolve upconverting issues in the past.
Paul Davidson
Sound and Vibration Software Staff Product Support Engineer
National Instruments

LabVIEW 2010 F2 - Crash - Localization issue ?

Hi fellows !
I am using LabVIEW 2010 F2 (French localized version) and I am facing this strange behavior. Can you confirm that this is a bug and / or this is because I am using a localized version of LabVIEW ?
When using the Modifications:VI property node (CTRL+SHIFT+B) and connecting its output to a case structure everything works fine (it looks like that).
But now if I change the Modifications:VI property to Modifications:Front Panel and let the output of the property node connected to the case structure, LabVIEW crashes or the broken arrow appears.
If I click on the broken arrow or try to save the VI (CTRL+S), I get the following error message :
Fpsane.cpp line 442
Thanks for your help.
Regards,
Da Helmut
Attachments:
err.PNG ‏11 KB
test.png ‏14 KB
test.vi ‏7 KB

Hi,
Thanks for the answer.
There is another bug with LabVIEW 2010 (F4 this time).
To reproduce it you have to create a (strict) type definition that consists of a cluster and put a constant which is linked to this typedef on the BD (just select the .ctl file in the BD) and then delete the type definition from the hard drive.
Close the VI that has the constant in the BD.
Re-open the VI, and in the BD, right click on the cluster constant and select "View as Icon". Now you get LabVIEW crashed. (ok it is useless doing that on a non existing typedef but this is crashing LabVIEW, so I thought this should be reported).
Keep me informed if you have any further informations about that.
Regards,
Da Helmut

LabVIEW 2010 Crash

All,
LabVIEW 2010 now crashes every time I try and open it. It seems to crash at the "loading plugins" phase. I don't recall what I did to cause this. How can I solve this?
Also there's no error log in the LabVIEW data folder under my documents.
Regards,
Ken

Has anything changed about the system? Has the system ever been in a working state? Has the computer received recent updates from IT or the OS? Did you face any installation problems?
Has any third party software been recently installed on the computer?
Thank you very much for your time and follow up. Perhaps an installation repair for LabVIEW would assist in ensuring all the correct files are still on disk, in case anything may have been deleted.
Cheers,
Patrick Corcoran
Application Engineering Specialist | Control
National Instruments

Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

I build an application exe and then its installer along with run time environment.
The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash.
Problem signature:
Problem Event Name: APPCRASH
Application Name: AGMS.exe
Application Version: 1.3.0.0
Application Timestamp: 4c24e8f5
Fault Module Name: lvrt.dll
Fault Module Version: 10.0.0.4033
Fault Module Timestamp: 4c9273f4
Exception Code: c0000005
Exception Offset: 00005310
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Dell System XPS L502X
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
Memory: 8192MB RAM
Available OS Memory: 8106MB RAM
Page File: 3457MB used, 12753MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
Language: English (Regional Setting: English)
System Manufacturer: LENOVO
System Model: HuronRiver Platform
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
Memory: 4096MB RAM
Available OS Memory: 4010MB RAM
Page File: 1359MB used, 6658MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
Now as I see it, it could be a Run-time environment mis-match error.
For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
I checked DEP, for all 3 PCs and it was set to the following
Turn on DEP for essential Windows programs and services only (first option).
I am confused. I can not find a solution for this and it is really frustrating.

But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
Since from the picture you can see its including the support installers from '\Program Files (x86)\'
The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
Yes I did reboot every time after I ran the installation.
Still getting the same error.

LabVIEW 2010 in-placeness crash bug

[cross-posted to LAVA]
I found an odd LabVIEW 2010 bug that will cause a hard crash. The bug appears to be related to how LabVIEW operates on data in-place and some interaction between clusters, arrays, and the Aum Array Elements node. It's hard to describe verbally, so I'll just draw you a picture
LabVIEW 2010 CRASH.vi (16.56K)

No crash on my system: LV2010, W7 64-bit, Pentium E5200
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Labview 2010 crashes XP while looking for webserver

Hi,
I am using a Windows 7 laptop with LV 2010 to compile my 32-bit executable. I've copied it to my target Windows XP, SP3 computer and after running it for a short while it rebooted the computer automatically (I believe the reboot was caused by a BSOD).
I've gone into the Windows Event Viewer and there is an event that says "Labview information: Error: 404 "Not Found" for "national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc", file "c:/program files/national instruments/shared/ni webserver/www/national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc": Can't access URL ."
I'm attaching a jpg of the Event in case I typed it incorrectly. There is another post that mentions this error but there is no resolution and the discussion went in a different direction: http://forums.ni.com/t5/LabVIEW/LabVIEW-2010-unstable-on-Windows-7/m-p/1247366/highlight/true
Neither my Win 7 development laptop or my target Win XP system have this www folder.
Has anyone seen this before or know the cause? Thanks.
Steve
Attachments:
Event Viewer small.jpg ‏69 KB

Altenbach,
Thanks for the quick reply.
Yes, the time stamp of this error coincides with the crash. I guess I assumed that it caused the crash because I see about 20-25 instances of it in the Event Viewer. Immediately before these errors appear there are two instances of the NI Configuration Manager with the Description saying "Opening configuration database".
This only happened on time and I have not been able to reproduce it again.
I'll need to explain to my customer why this Error has appeared so many times in the Event Viewer, and also how I can get it to not happen again. Do you have any suggestions? Once I isolate this error and prevent it from happening again then I can monitor the computer for future crashes.
Thanks.
Steve

Labview 2010 crash at startup windows 7

Hi,
Labview crashes on startup. I get this message: "Labview 10.0 Development System has stopped working." I don't get any further than this.
I have 95 computers running Windows 7 64-bit Enterprise. To install Labview on these I use the automated installer with these options: "/q /acceptlicenses yes /r:n /applyspecfile k:\zfdmsi\Labview2010\yellow1\".
This was working on Windows XP. I have tried to install Labview manually on one of the windows 7 computers and it works fine.. But I cant do that on 95 computers...
Any ideas why it's crashing?
Thanks in advance.
Solved!
Go to Solution.

Yes, m: is a network drive. We have a local policy on all workstations redirecting My Documents to the M: drive.
I got the issue resolved by installing Labview 2010 SP1

LabVIEW 2010 crashes when changing representation of TypeDef

Hello NI,
I have to report a bug
which causes LV 2010 to crash with error in "datamgr.cpp", line 2720.
This crash is reproduceable.I use LabVIEw 2010, 32 bit on Windows 7.
To cause this crash you have to perform the
following steps (I attached a sample VI to reproduce these steps.):
Place a ring control on the FP, change
representation to I32
On the BD, create a property node “Strings
And Values[]”
The datatype of this property is Array of
Cluster with 2 Elems, “String” & “Value”, where “Value” is of type I32
Create a control of this property,
surprisingly the type of Value is “extended”
On the FP, select the cluster inside the
array, click “Customize Control…” from Edit- menu
In the Control- Editor change the DataType
of Value to I32, then exit the Control Editor without saving the control,
but replacing the original cluster
LabVIEW 2010 will crash with the error
message stated above
The problem is to change the
representation of the cluster element, where the cluster is part of a typedef. A
solution is to forbid to call the “Customize”- editor directly from the FP (not
nice) or to forbid to replace the orginal control, instead force the user to
save the altered control to a .ctl (nicer).
This shows a general problem with TypeDefs,
where the array of a not-typedefed cluster is typedefed. This was discussed
earlier with the cursor list of waveform graphs (couldn’t find it anymore, but
read it in this forum) where this problem also can occur. So this is an appeal
to National Instruments to change the TypeDef to the clusters and make arrays
of them.
And, after all, for me it is
unexpected behaviour that a constant / control / indicator, created from a
property (or any terminal / node I can find on the BD) has another datatype
than the original terminal or node.
Greets, Dave
Picture 1: Type of property node
Picture 2: Type of created control
Picture 3: Error message
Greets, Dave
Attachments:
Ring TypeDef Problem.vi ‏66 KB

Hi All,
I am also facing the same bug from the long time which causes loss of data unexpected.Please solve this bug and tell me any way to solve this.I am using Control Type Def in my project.
Thanks
Yogeshwar
Attachments:
error.jpg ‏19 KB

LabVIEW 2010 crash when calling user32.dll

Interesting LabVIEW 2010 "feature" I discovered this morning.
Attached are two identical VIs, one saved in 2010 and one saved in 2009. These VIs were specifically written to demonstrate the bug I stumbled upon this afternoon. Each VI when run should allow you to find a specific program (window) open in Microsoft Windows and bring it to the foreground. It relies on "user32.dll" to perform this operation. It also allows you to specify the calling convention for the function call.
In LV 2009, either calling convention works, without error. However, in LV 2010 the calling convention for the function must be "stdcall (WINAPI)" and not the default "C". If the calling convention is "C" then LabVIEW crashes and closes without warning.
If you happen to have both LV 2009 and LV 2010 on your computer, I would love to hear if this phenomenon is duplicated so that I can pinpoint whether the bug is LV 2010 related or is more specific to my personal setup.
Thanks,
~David
Solved!
Go to Solution.
Attachments:
LV2010 test.vi ‏13 KB
LV2009 test.vi ‏14 KB

221113
Return
CLFN with the wrong calling convention may siliently crash LabVIEW.
LabVIEW 8.5 through 2009 could adjust the calling convention at run time if the user selected the wrong option. In 2010 this no longer happens. More information is found in KnowledgeBase 59KB14WI
Workaround: Use the correct calling convention
Reported Version: 2010 32-bit
Resolved Version: N/A
Added: 07/23/2010
From 2010 release notes.
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Error 404 causes Labview 2010 to crash but only occasionally

Hello,
I am requesting help to solve a problem with LabVIEW 2010 crashing. I am new to this company and the last Labview developer left without providing
background on this problem. Labview crashes after running project VIs. Labview closes without warning or error messages. The project acquires data from pressure transducers, dP transducers, thermocouples, IEPE, load cells, and voltages through NI real-time system and has digital I/O. NI hardware includes PXI-1050 with modules 6221, 6280, 6224, 6220 and NI PXI-1052, SCXI-1306, SCXI-1112, SCXI-1520, and SCXI-1102. I've reviewed the labview program and the software relies heavily on shared variables, references, and local variables but I cannot find anything that stands out as a problem in the software .
The program crashed again today after running for only 1/2 hour and was not recording data. No error message occurred before the crash and the only error after restarting LabVIEW was the standard message that LabVIEW did not close properly. I went to the Event Viewer and at the time of the crash I received the following information:
Event ID = 3299
Source = LabVIEW
Log = Application
Level = Error
LabVIEW Information: Error 404 "Not found" for "/national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport", file "Crogram files (x86)/ national instruments /shared/ ni webserver/ www/ national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport": Can't access URL
According to Event Viewer, this error 3299 occurred 15 times in the last 3 days. LabVIEW crashed today at 10:19 am at the same time this error 3299 occurred but LabVIEW did not crash the other times this error occurred in the last 3 days. I believe this error is related to the crash but does not usually cause the crash. It appears to me from reading the error message that the error is the result of occasional lose of communication with the real-time system (Can't find URL). Any suggestions how to resolve this would be greatly appreciated.
Bill

1. Have you had this code working before on this or another machine?
2. Which operating system and version of LabVIEW are you running? (This can be found in Control Panel >> All Control Panel Items >> System)
3. Which National Instruments Drivers are you using? (This can be found in the measurement an automation explorer under the software tab [a screenshot would be good])
I would look into removing afsetup.exe which is a data collection tool provided by Microsoft which could a) not be installed correctly and/or b) trying to pull data from LabVIEW. I think this may help you out, as even though your programs aren't explicitly calling it, the service is running in the background.
Secondly, I would look into stopping the NI Web Server application that could be polling a web page that's not needed.

Wire mode bug in LabVIEW 2010?

I had an application written in LabVIEW 2009 for a CFP-2220 that stopped working when it was converted to LabVIEW 2010, and I have tracked down the problem to one thing: the software sets the wire mode of the serial port. Calling this method simply disables the whole program. It works when run from LabVIEW...but if you build a startup application it will not even start. Remove the wire mode call - and voila, the application runs as it should.
So - I can fix the problem easily by not calling the wire mode method, however this is no solution due to the fact that I need to use the RS-422/485 port in 2-wire RS485 mode.
MTO
Solved!
Go to Solution.

It turns out that this is an even stranger problem; the serial port init function will ONLY work in the built application if it originates from the vi.lib\Intsr\serial.llb file. If you do a save as and substitute with original...then you would expect it to still work, it's the same VI, it has just moved...but no (!). Again - there are no warnings, no errors, and everything runs fine in the development environment, but if you deploy and run this application on the cFP-2220 it will only run if the serial port init VI came from that location. Save it to another location (no conflicts caused by this)..build it again, and the application will not start. You can even move the whole serial.llb file to somewhere else and call the serial init file from there - and that's enough to stop it from working.
The reason why I though that I had linked this to the wire mode was the fact that I got everything to run when I used the standard serial port init VI...but if I saved a copy of this to another location and added the wire mode to it it stopped working...so I assumed it was the wire mode, because that was the only thing that had been changed that would logically produce any change...the fact that it was moved should not have any effect....it turns out that was wrong.
I have a few other variations to test (what if I edit the file directly in vi.lib\Instr, will it work then e.g.? That will not be a good solution, but a good thing to test anyway)...
MTO

Having Trouble Copy and Pasteing Local Variable in LabVIEW 2010

I am Having Trouble Copy and Pasteing Local Variable in LabVIEW 2010 in s subVI.
I have a VI that has a Local Variable called "Node Addr". I can select it OK, and it appears to Copy OK, But when I go to paste it, nothing appears. It doesn't matter if I use Cntrl-C Cntrl-V or the Copy and Paste from the Edit menu, I get the same results. I tried many times and got the same results. I made sure that I had click a paste location. I can insert the Local Variable if I use the Data Communication panel.
On one of the Paste, I got an error in the error list that said that a Local Variable was not connected to anything. When I clicked on the error, it took me to an insible item in the lower right corner of the block diagram that had nothing but a select box around it. I couldn't select the invisible item, but I could delete it.
Why does the copy and paste of this local variable not work?
Why does the paste cause the insertion of an invisible item?

dbaechtel wrote:
My VI is fairly complicated. In several places in the VI, I am either reading or writing to this variable which is an numeric Indicator on the Front Panel. Using local variables seems to be the best way to handle this situation rather that using wiring all over the VI. Since the VI is mainly a State Machine and there are only 2 Writes to the local variable, I am not afraid of race conditions in this case. NO!! While you may think that using Locals is your solution to wiring, it is not! The fact that you are writing and reading, most likely from several places, will most definitely contribute to a race condition. Depending on your implemetation, you should ALWAYS use wires. The wires are the variable. If you are using a loop (While, For), then using shift registers are appropriate means for routing values so that they are used by other sections of the code, later. One thing you must respect with LabVIEW is the dataflow. That's where Locals often fail.
I am not copying the Local Variable from one VI to another.
I am not copying the Local Variable from one VI to another.
The Data Communication panel is one of the panels that shows up in the Functions pop up list when editing the Block Diagram. It is the panel that includes the Local Variable function.
I don't know if the invisible item that was inserted in my block diagram was hidden or not. All I know is that the Errors List said that it was a Local Variable and that it was not connected to anything. I couldn't select it to get more information. All I could do was delete it.
You did not address my questions about why the Copy and Paste does not work properly for my Local Variable. Maybe it's a sign from the Software Gods not to use them LOL!..
So if I understand correctly, you are trying to copy & paste the Local Variable from within the same VI. How large is your block diagram? Did you try right-click on the variable and select "Find > Local Variables"? If it's a block diagram larger than 1 single screen (which it shouldn't), then it is possible that the Local is hiding beyond the screen. You should find it as I described earlier.
See my comments in red above.

Auto cleanup crashes LabVIEW (and VI isn't even that large)

Hi,
I'm trying to cleanup a VI, and whenever I hit auto cleanup LabVIEW crashes and when retsrated it doesn't even say it previously crashed. I narrowed down the problem location to a for loop. The wierd thing is that I went through all the wires and objects within the loop and did auto cleanup on them but it doesn't crash. So why when I do it on all combined does it crash?
I wrote a comment in the loop that crashes to show which on it is.
I'm on Windows 7 LabVIEW 2010.0f2 32bit
I did see this posting http://digital.ni.com/public.nsf/allkb/599FB39777BDB12486257514005B7293, but even when doing it manually as suggested it still crashes.
Thanks,
Matt
Solved!
Go to Solution.
Attachments:
Score Videos temp.vi ‏126 KB

This crash corresponds to a known issue in LabVIEW (CAR #298911), which has been fixed in the forthcoming LabVIEW 2011 release. I have attached a copy of your cleaned up VI from 2011, saved for 2010. You might try to copy the block diagram into a new VI and see if that still crashes LabVIEW, but otherwise an upgrade to 2011 when it's available should clear up the problem. Hope that helps.
John B.
Embedded Networks R&D
National Instruments
Certified LabVIEW Developer
Attachments:
Score Videos temp-1.vi ‏104 KB

LabVIEW 2010 local variable behavior

Hi -
I upgraded to LabVIEW 2010 from 2009SP1 and the attached sub VI no longer works correctly. This is a state machine case structure that gets called inside a loop. I'm setting a Boolean local variable true, then on the next call when the case changes the variable has been reset to false. It did not do this in LV2009.
Someone will immediately tell me I have a race condition, but these local variables are not being written anyplace else, just within these separate cases.
See the attached code, specifically, the local variable "Enable" is getting reset when going from case "Enable" to case "Turn on".
Anyone else seen this issue, or can shed any light?
I fixed the VI by writing the value in each case, but this different behavior makes me wonder what other issues are lurking in LV2010?
Thanks
Solved!
Go to Solution.
Attachments:
eq99_cycling.vi ‏42 KB

This code looks more like some sort of an Action Engine than a state machine, but not quite. It gets called repeatedly from a state machine, and it decides what the next state will be depending upon the inputs. Instead of using all those local variables, I would use uninitialized shift registers (nothing wired to the left side). They hold their value from one call to the next. One more case needs to be added in this case. An unnamed, default case that would set the initial values of all the shift registers. Make it the default case and don't even name it. It will be called first automatically because the shift register is uninitialized so the default will be called. Inside the default case, set all the shift registers to desired values. Next time this subvi is called, those values will still be there. That is as long as nothing is wired on the left side, Whatever is wired to the state shift register will be the next case called.
See attached vi. It is broken because I did not wire anything to the indicators.
- tbob
Inventor of the WORM Global
Attachments:
eq99_cycling-4[2].vi ‏33 KB

Deleting broken wires crashes Labview 2010

Similar Messages

Maybe you are looking for