Block Diagram Error

I'm getting an error when i try to connect two sub-vi's.
Error:
The type of the source is 1-D array of double.
The type of the sink is 1-D array of waveform.
Does someone know.
I'm using LV6i.
Iwert

Yeah. You've gotten the error because you've tried to wire an array of
doubles to a waveform array
Type "waveform" is a new datatype introduced in LV6 that's essentially a
cluster of the DBL data array and timing information. The resizable function
"Build Waveform" under the "Waveform" palette allows you to combine your 1-D
array of doubles with t0 and dt values to get a waveform that can be fed
into the waveform terminal.
Iwert Mijnders wrote in message
news:<[email protected]>...
> I'm getting an error when i try to connect two sub-vi's.
>
> Error:
> The type of the source is 1-D array of double.
> The type of the sink is 1-D array of waveform.
>
> Does someone know.
> I'm using LV6i.
>
> Iwert
>
>

Similar Messages

DIO Port Config & DIO Port Write Block Diagram Errors (Call Library Function Node:library not found or failed to load)

Hi Guys, need help on this.
I have this LabVIEW program that used to work on the old computer.
The old computer crashes most of the time, so I upgraded the computer
and used its Hard Drive as slave to the new computer.
I have no idea where are its installers since the guy that made the program
is not in my department anymore.
I downloaded all the drivers needed from NI: NIDAQ9.0, NIVISA,NI488.2,
and drivers of some instruments needed in the setup. I'm using LabVIEW8.2.
Everything's fine until I open the LabVIEW program for our testing.
Here goes the error:
   DIO Port Config
   DIO Port Write
Block Diagram Errors
   Call Library Function Node: library not found or failed to load
Attachments:
ErrorList.JPG ‏200 KB

Honestly, I'm a newbie on Labview. I just want this old program to run on the new computer.
The guys that installed the drivers on the old computer are no longer here in my department.
And I have no idea where the drivers are. So I just downloaded the drivers needed for my hardware and instruments.
Here's my hardware: (cards: PCI-DIO-96, PCI-GPIB), (instruments: SCB100,E4407B, HP83623, HP3458, HP8657)
OS: Windows XP Pro
By the way, I have unzipped the TraditionalDAQ drivers. First I tried the 7.4.1, but installation error appeared.
I thought maybe the installer is corrupted, so I downloaded the 7.4.4 and unzipped it.
But, still same installation error appears. I don't understand, both TraditionalDAQ drivers have same installation error.
Now I have tried the DAQmx8.7.2 driver, bu still the DIO Port Config and DIO Port Write have errors.

Block diagram errors even when block disabled

Should LabVIEW give the broken arrow for errors within a disabled block?
I have a block disabled where way down in the call tree from a VI within that block there is a broken VI.
Nothing else calls this broken VI except the VI from the disabled block.
Why should I get the broken arrow if the top level caller is disabled?
TestStand 4.2.1, LabVIEW 2009, LabWindows/CVI 2009

Thanks for the thoughts guys.
I have discovered that the errors in the disabled section appear in the error list box when there are other 'real' errors.
When there are no other errors, then the errors in the disabled section do not affect the run arrow.
Typically commented or disabled code is ignored by a compiler - and so I think it should be the case with LabVIEW too.
TestStand 4.2.1, LabVIEW 2009, LabWindows/CVI 2009

I created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

i created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

Expanding and clarifying what BJD said;
After you create the temporary sub-VI that BJD mentioned, open its front panel and copy the reference control that LV created when it created the sub-VI.
This reference control will be correct class etc that you need. Use the control to replace the original control that you were attempting to wire up.
The technique of "create sub-VI...copy" always works for me.
There is one more thing that you should watch out for.
The mechanical action of the boolean can not be set for latch action when attempting to read the value using a value property node.
Trying to help,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Error cluster constant appears different in two locations on a block diagram

I am a newbie to LabVIEW. I have taken Core 1 & 2 and Machine Vision and I have not com across this before.
The image on the right is obviously an Error cluster constant used in the block diagram to create an Error cluster and wire it to an error out terminal. As far as I can tell the image on the left is about the same thing, but why does it look different? The different appearance causes raises a concern that there is a difference in behavior that I do not understand. LabVIEW help suggets that both are Error constants. When I create a new error constant, it always ends up appearing like the right image above. I have not been able to create someting looking like the image on the left.
Could someone please confirm what the image on the left is on a blck diagram?
Thanks,
Bill
Solved!
Go to Solution.

The image on the left is an error cluster control. It has a front panel presence and can be set either via the front panel or through a property node or local variable. The image on the right is an error cluster constant. It is a static value.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Why do I get an Error Code 70229 when running Block Diagram ?

Hi everyone,
This error is very weird because at one time I got the block diagram to run and it worked well then when I tried it again after reopening the block diagram I got this error .
Can someone help me please ?
I am using SolidWorks Premium 2014 x64 Edition.
The attached files show the version I got for SoftMotion and for Labview 2013 32 bit installed .
PS. I had Labview 2013 64 bit installed but I removed it. not sure if any files remained that may cause this...
Thank you,
Isaiah
Attachments:
Softmotion.JPG ‏54 KB
Labview2013.JPG ‏55 KB

Read related topic
Thank you & Best regards
syrpimp
=======================================================
“You must continue to gain expertise, but avoid thinking like an expert." -Denis Waitley

I am trying to create an executable vi that will call out another vi and show its front panel in the executable. When I try this I recieve this error message "top level vi (my main vi) was stopped at unknown on the block diagram of (my sub vi)

I am trying to create an executable vi that will call out another vi and show its front panel in the executable. When I try this I recieve this error message "top level vi (my main vi) was stopped at unknown on the block diagram of (my sub vi)

Well the most common way is to enclude the vi's in the build spec either directly in the dependancies that the App builder automatically generates OR by declaring them in the build spec as "additional enclusions" (like you must do for dynamic vi calls in your app.
I have heard rummors about My.app Stuff.vi in a nugget Intaris posted- and I've wanted to dig deaper into Intaris' claims- but have not tried it myself.
If you go down the stuff.vi route Keep us curious guys posted
Jeff

Error -- Block Diagram is Completely Black

Hello,
I've been working on a relatively complicated .vi that has a good amount of case structures and flat sequences. As I was testing the front panel and going back and forth between the block diagram, the block diagram became entirely black -- all I see is a black background -- no wires, blocks, etc. I am still able to add blocks through the menu but can't actually see them being placed or anything. Is there a way to fix this, or revert back to normal? I would really not like to redo all this work...
Thanks,
Bryan

I think there are some unusal observations of you exceed a certain diagram size ( e.g. 16000 (?) in pixels). How big is your diagram?
(Other possibilites are issues with your video card, graphics driver, or color depth setting of the OS.)
LabVIEW Champion . Do more with less code and in less time .

LabView application hangs up when scrolling the block diagram

Hi all.
I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
Regards,
Francisc
Hi all.
I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
Regards,
Francisco
Attachments:
Main (v3.1).vi ‏257 KB

It didn't hang up on my computer, but it did make me nauseous, luckily I keep a bucket by my desk.
You might have video card issues. Try this: open the VI, and hit Auto Cleanup, then save. Close LabVIEW, reopen. If that does not work, try to get to the far right side by going to the Front Panel, and double clicking something that will take you there. If you get there successfully, use the disable structure to disable ~ 1/8 or more of the diagram on that side. Save, reopen.
Richard

Block diagram out of... block diagram

Hi, I need your help. Im the wrong person to this job, but I have to do this, so I'm dependent on your help. I need to explain how the LabView program (pasted below) works, but I don't understand it by myself I would like to ask if someone can create a simplified block diagram of the LV block diagram I paste in here. I would appreciate any help, and please take into considaration that I'm running out of time
https://dl.dropbox.com/s/yd10z7yorxvbzux/LVdiagram.jpg
It's a counter. Photon counter to be exact.
Solved!
Go to Solution.

Hi Waise,
I will try to explain you briefly what does this application do:
Following materials might help you in understanding the concepts behind:
http://www.ni.com/pdf/manuals/371022k.pdf
This is the M series manual - the chapter 6.7 and 8 explains how the digital lines work, the counter and what is a PFI.
When you open the block diagram of your application you can see multiple branches going from left to write.
The first one, on top is creating a path to a file. That path will be used to write data to a binary file. The data represents the number of pulses that are being counted as rising edges of a signal connected to counter 1. This information ca be read if you follow the logic on the second branch from left to right where the first VI is CI INT Edges (Counter edges), and it will count up, on rising edge of the signal connected to CTR1.
Later, there is another task created for counter 3, that generates pulses. The pulses seems to have 10uS length and 50% duty cycle. The signal generated by that counter will be used as sample clock for the measurement and counter 1. Also, the same signal from counter 3 will be used by counter 4 to count the digital edge and create a clock that will clock the timed loop. Basically the frequency of the timed loop is given by the task on Counter 4 that counts the pulses generated with counter 3.
The 3rd branch from left to right, creates three tasks on three digital output: Line 0, 1 and 2 where it is being controlled by three buttons F0, F1 and F2. Basically, your timed loop will have a specific iteration time, and with every iteration the buttons will be read and will update the digital output specified above.
Whenver there is an error or the Stop button is being pressed, your application will stop and will close the binary file and dealocate the used resources.
I invite you to look also in the manual specified above.
Best regards,
Ion R.
Attachments:
printscreen 1.png ‏178 KB
printscreen 2.png ‏183 KB

Frequent Crashes - Running, Exiting, While in Block Diagram...

I am suffering from frequent crashes and lockups of LabVIEW 8.5 Base version. I have not been able to pin down the root as the occurances may happen when my program is running , or when I try to exit, or when working in a block diagram. It seems like it is more likely to occur in and around vi's created using the dll conversion wizard. The vi's are for the API for Silicon Labs CP210x USB to UART configuration. In my test the device powered on an off several times and so appears and disappears several times, and this gets repeated as new devices are tested.
How do I track this down?
How do I practice "safe" programming to avoid unexpected occurances that crash LabView?

Hi MG,
Are you using the Import Shared Library Utility from Tools >> Import >> Shared Library (.dll)? This is a tool within LabVIEW that can be used to convert shared libraries to VIs.
In response to your most recent question, by controlling or adding a timeout for the COM (USB) communication you would be able to stop a portion of the process or the entire VI. This is because when the timeout value is exceeded this initiates an error which will propagate to the subsequent code and prevent any further operations from executing. In order to stop this error chain from continuing to the end of the code a General Error Handler VI can be used with the COM timeout error code wired to the 'exception code' terminal to ignore this error for future code execution.
Hopefully, this is a possible solution for your application. If you need any further clarification, please let me know.
Jason W.
National Instruments
Applications Engineer

As I can include a "IVA" in the Block Diagram.

Hello friends. I have a question about how to use the "IVAMATCHPATTERN ALGORITHM.vi" I located in my pc and is part of a library "LLB" but I can not carry it, I get a message that says it was compiled on an OS different. I am working with LV8.5.
Thank you.

Hi Xontrol,
as the error message says: the files can't be loaded because their block diagram has been stripped.
You can load them only in LV8.2.1 - all newer version need to recompile the VIs, which is impossible due to missing block diagram...
Just reading that error message...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

LabView Crashes When Editing Block Diagram

When least expected and usually at the most inopportune times the LabView 8.6.1 development environment crashes when I am editing my block diagram. It usually happens when I am moving VI's or wires using the arrow keys. This has happened to me several times. Is anyone else having this problem? Is there a bug fix out there? Attached are some of the windows error logs
Attachments:
lvlog06-17-09-11-01-33.txt ‏2 KB
lvlog06-16-09-15-52-19.txt ‏9 KB
lvlog06-15-09-13-53-20.txt ‏2 KB

There is a known issue with LabVIEW running out of memory slots in it's image table
http://zone.ni.com/devzone/cda/tut/p/id/7324#36543_by_category
I have experienced this issue first hand and it does make LV very unstable with crashes at the most inopportune times.
Try uninstalling those toolkits and drivers that you are not currently using. In my case 8.6.1 became completely stable after that.

Why does my block diagram change when I copy my code to another system?

I am doing development work on a laptop on Win XP and using LabVIEW 2009 with service pack 1. When I copy the code to the target system, my block diagrams are changed and no longer fit the screen. Much of the code is spread out, mainly down. The target system is running Windows 7 and also has LabVIEW 2009, SP 1.
I notice that any constants that are clusters are expanded when copying the code to the other system. I've gone in and turned off the autosizing for these clusters but they are still expanded. I like to shrink them to a small size for saving space.
I've gone through and manually re-adjusted the block diagram on the target system, but when I copy it back to my development laptop, the same thing happens again. This is not an acceptable way to develop code and it has caused a real problem to proceed. I'm contracting this work and must develop this code offsite. Can anyone please help me with this? I can't keep restructuring my block diagrams every time I copy the code from one system to the other.

Windows XP used Tahoma size 8 as its basic system font. When MS came up with Vista, they changed it to Segoe size 9. I'm not sure what Win 7 is, but I think it is the same as Vista. That font change, and certainly font size change seems to be the underlying cause for block diagrams changing their appearance. (And for front panel controls and labels as well.)
LV seems to use the Windows system font as its default font. Interestingly, it seems like the font sizes in LV are something like size 12, 13, 14, 15. I think a size 9 is equivalent to a size 15, but I'm not sure about the comparisons. (Check out this thread.)
There are a few things you can do to try to make one system look more like the other.
1. Go into the Windows screen settings. In Vista, right click desktop, Personalize. Window color and appearance. Open classic appearance properties. Try changing the color scheme from Windows Aero, to something like Windows Classic or Windows standard. They both use Tahoma 8.
2. Or same as Step 1, but go further into Advanced button. Pick on any option that uses font such as Menu, Message Box, Active or Inactive Title Bar and change the font there. I'm not sure which of the items that has a font setting is the key one.
3. LV uses 3 fonts called Application, System, and Dialog. I think each of those map to one of those Windows options, but I'm not sure which goes to which.
4. In LV, Tools/Options/Environment has a subsection called Fonts. Those 3 basic LV fonts are selectable there. There is also a checkbox for me which is checked and says to use default. If you uncheck that checkbox, a Font Style button becomes enabled. You go in there and you can choose fonts and sizes. And the Application, System, and Dialog fonts as well as all the usual fonts names (Arial, MS Sans Serif, Greek, ....) are selectable along with fonts sizes. Play around in there. The whole section is very confusing, and I have no idea how it works. I recommend going to this idea A better way to specify (default) fonts and putting in a vote. Also this idea, Fix font behavior between windows versions, platforms & executables, deserves some love.
5. Some of these settings can also show up in your LabVIEW.ini file.
FPFont = "0" 15
BDFont = "0" 13 (I think the "0" means app font, "1" means system font, and "2" means dialog font)
Also,
appFont="Tahoma" 13
systemFont="Tahoma" 13
dialogFont="Tahoma" 13
(And if necessary, put these in your built application's .ini file)
As you can see, there are a lot of different things going on and they also seem to conflict with each other. I starting stumbling on the block diagram issue between working on my app on XP at work and on my Vista machine at home about 6 months ago. I think my problem actually started with the front panel when I was trying to align labels, and use some arrow head decals on boolean buttons. I think I did the customization of buttons in a couple different ways (because I did some, came back later to do others, and couldn't remember exactly how I did it.) As a result some decals looked different than others when I changed machines. And I swear going from XP to Vista, or Vista to XP the problem got both worse ways rather than let's say larger one way, and smaller the other way.
Replying to your message is about as much to me trying to combine all the pieces of knowledge I've stumbled across over the past months and year as it is for trying to help you. Hopefully, this information gives you some places you can look at and play with. (I bet #1, would be a quick, easy way to solve your immediate problem, but I haven't really tried it myself to be sure.)
I hope someone from NI who has a better understanding than me about these font issues could jump in and correct any mistakes I made, or add anything I might have left out. What we really need is some sort of "nugget" or National Instruments white paper that really explains all of this in ways we can use rather than us stumbling around in the dark doing things trial and error to figure it out. Generally, any changes to the .ini files require you to shutdown LV and restart it to take effect which can take a couple minutes. And considering all the various combinations of things that can be done above, your talking about dozens of possible restarts, and sending .vi's between two different PC's with two different operating systems, before figuring these things out.

LabVIEW exits while editing block diagram unexpectantly

Hi all, while editing block diagram in LabVIEW 2010, I have experience some strange behaviour from the software. I have two monitors, one has the front panel of main VI and the other - block digram of the specifed VI. When I switch from block diagram to front panel, and vice versa, every now and then the LabVIEW exits unexpectantly without the notice. Upon restarting the program again I get the undo.cpp error. I have attached the error log for my clarification on the type error that I am dealing with. Does anyone have any ideas why this is occuring? Thanks in advance for your help.
Viktar
Attachments:
lvlog2010-09-17-09-35-46.txt ‏2 KB

Thanks for all the responses.
I was using an existing VI as template to create a new program. There were nested loops in the original program and I needed the logic for the outter loops only for the new program. After deleting many objects in the 'yes' case in the inner loop, I was left with many loose wires in the 'no' case. And that's when my problem started, when I was trying to delete them. Yes, I tried rebooting my PC and that did not help. The problem seemed to get progressively worse, as crashing started to happen even when I was only selecting a wire. But somehow I was later able to select one wire, delete it, and did a save. Then I went to the next wire, and so on. My program is now cleaned up and I'm ready to go on. I will experiment more when the problem returns.
Thanks again.

Block Diagram Error

Similar Messages

Maybe you are looking for