Close FPGA VI Reference breaks when moving project...

I created a cRIO project with an FPGA target, and assigned the output of Open FPGA Reference to an indicator.
When I moved the project to a different computer, the wire to the indicator broke, so I selected "Bind to Typedef..." on the Open FPGA Reference node, replaced the indicator, reconnected all the local variables from old indicator to the new one, and deleted the old one. So far so good.
But now, when I move the project to a different computer, the wire to the Close FPGA VI Reference breaks.
If I delete and replace the broken wire whenever I open the project on the new computer, everything's fine. Am I stuck with that? It could be worse, I guess, but I'd like to fix this for real. Any suggestions?
Thanks in advance.

Hi Ron,
I do not believe that there are any other workarounds for this behavior. I've been attempting to fix this myself in another way, but it seems that due to the simplistic nature of the close reference vi, it is not possible to go about this in another way when distributing applications. I will try to see if we can make a product suggestion for this in the future releases of the software.

Similar Messages

Intel Macs & G5s: Problems when moving projects between them

An earlier post* suggesting complete compatibility between the latest FCP in a G5 and in an Intel Mac may be in error.
We are experiencing continuing crashes using our Intel Mac when we work on projects that were originally either imported or partially rendered in the G5.
It has gotten to the point where we feel we must keep projects completely isolated from each other: Either it is a "G5 project" or it is an "Intel Mac" project. Moving projects back and forth between the two leads to problems such as:
The Intel Mac does not recognize any renders done in the G5...
The Intel Mac crashes when rendering 'G5' projects...
The Intel mac crashes when compressor goes to work to export sequences to mpeg...
The G5 works fine with Intel Mac-originated material: It is only in the Intel Mac where we have these problems.
Both systems are up-to-the minute on their OS, security updates, and FCP versions. We are using variously 720p/30 from the JVC GY-100UA and 1080i/30 from the Sony Z1U.
Our questions are:
Is anyone else experiencing similar problems moving projects between a G5 and an Intel Mac?
Is anyone moving projects between the two platforms and experiencing NO problems at all? That information would be just as valuable, and very welcome.
Apple FCP development team: Is our experience unique or have you had other reports like this? Any idea what could be causing our problems -- and what we can do to fix them?
* http://discussions.apple.com/thread.jspa?messageID=3604812&#3604812
Intel MacPro Tower, 3gHz, 8mb Mac OS X (10.4.8) Also a G5 Tower, 2x2.5ghz, single core

Scott,
Welcome to the discussions!
I have had no problems moving my G5 projects over to my MP.
You can not move render files between machines.
When you changed systems, did you use Migration Assistant to transfer your files over to your new Mac Pro? You might need to install from the disks in order to achieve native Intel performance. See if you installed Final Cut 5.1 on your G5 then it installed the PPC code... if you put that drive into your Mac Pro or used Migration Assistant to move the app over it is still the PPC code... When you install from the installation disk, Installer determines what system you are installing on (PPC or Intel) and that's what it installs. This goes for all of your "Universal Binary" apps...
In the System Profiler app. under Software/Applications
Final Cut Pro "kind" should be Universal on your MP.
The FCP development team do not read these posts, only users do.

Problems when moving projects to different workstation.

hi everyone,
Im done making an application and when i moved to a different workstation, something went wrong.. i created a JPanel + database driven components, i added it to the pallete using pallete manager. every is ok until when i changed my computer, a warning message appear when i view it in design view... "WARNING: Form loaded with errors." The thing is i compiled it and nothing is wrong. the project still runs but a NoClassDefFound error occur... im using same versions of netbeans 5.5 and jdk1.6....
am i doing the transfering of the project folder right or is on adding the jpanels to the pallete window. Or is it something else...
im learning java but had confusions in netbeans.
thanks...
ieMoon

Oops... sorry for posting in the wrong forum... thanks anyway... the problem is i missed that my app requires the GroupLayout manager classes, and was not include in the jar... anyway, sorry...
:)

IMovie 11 quits when moving projects to external hard drive

I am trying to move my iMove projects to my external harddrive to save space on my computer (MacBook white unibody 2010/11 running OSX 10.6.8 and iMovie 11 version 9.0.4 (1634). I used the instructions on Apple's iMovie 11 support page (see here http://support.apple.com/kb/ph2289). Every time I try to do this iMovie unexpectedly quits. Actually, the first time I try it says "Copy Failed: The copy could not be filed..." - when I try again the application quits and it gives me this message:
Process:         iMovie [3663]
Path:            /Applications/iMovie.app/Contents/MacOS/iMovie
Identifier:      com.apple.iMovieApp
Version:         9.0.4 (1634)
Build Info:      iMovieApp-16340000~2
Code Type:       X86 (Native)
Parent Process: launchd [104]
etc....
I have a ScreenCast video of exactly what happens when I try here: http://screencast.com/t/QWN6yWxN
Thank you in advance for your suggestions.
Kris

Here are the steps to move the library safely to an external hard drive. Okay. Make sure iTunes is open first. Hide it. Find the iTunes folder. Click and drag to external hard drive. Wait till it is copied then go to prefernces in iTunes. Go to the advanced tab and then hit the genral tab. Change the iTunes folder option to the folder within the titled "iTunes" folder to the "Music" folder. Also click the boxes "Keep iTunes folder organized" and "Copy Files to iTunes folder". This worked for me and did not effect the ratings. Let me know if it works. It should. Oooh. One more thing. Back up your library first incase you make a mistake or it doesn't work!

Video changes when moving project over to CC (2014.2)

I have just moved across a project from Premiere Pro CC to Premiere Pro CC (2014.2).
A notice popped up to say that the file had to be converted, after doing so, alot of the footage and sub clips are not actually what i have edited, it is from different times of the video?

thanks i appreciate the advice, however that's where the problem originally lies. After perhaps prematurely clearing to cache database to free up space before i had finished the project, it now get's stuck whilst trying to conform. This time it has got stuck whilst auto saving which i will now turn off, however i am worried i will have to wait a very long time untill all the video conform as this is a big project with a large number of video files.

Flash file breaks when moved to PC

I created several flash files on a Mac using Flash CS3 and then recently moved them to my PC. I tried to open them up on the PC and when I run the code, my .load no longer works. It doesn't make any sense because the AS should work the same no matter what. I also no longer have assess to my Mac, so I can't go back and change anything.
My codes goes a little like this:
testingXML = new XML ();
testingXML.onLoad = loadingAction;
testingXML.load ("http://www.google.com");
Thanks!

In my case, this exception was due to a defect in some timeout code I'd written. I didn't want to wait forever for the command to complete, so after an appropriate amount of time, the code would destroy the process. That invalidated the data streams however, causing the bad file number exception in the reader threads.
So you may look for ways in which the executed process might be getting destroyed.

FCPX freezes when moving projects

Every time I try and move a project to a different drive FCPX is freezing. All I get is a spinning wheel that says "preparing to process" and the pizza wheel.
I am not moving the referenced events, just the projects themselves. Any ideas?

First trash your preferences.
Try copying it in the app. What drive are you going to, how is it connected and formatted? How big is the project folder?

Using Open FPGA VI Reference in a distributed VI

Hi all.
I have some problems with the Open FPGA VI reference. In my project I have a VI which uses the Open FPGA VI Reference. In the Configure Dialog I’m using a lvbitx file located under “C:\Program Files (x86)\National Instruments\NI VST\Custom Bitfiles”. This works as it should while running the VI on my development machine but after building an installer including all this, the path to the lvbitx file gets wrong. When I build the installer I’m using VIPB but the same problem occurs if building an installer using NI Build Spec. When I try to use the distributed VI on a “customer machine”, it automatically starts searching for the lvbitx file but the path to the file is incorrectly set to ..\..\..\..\..\Program Files (x86)\National Instruments\NI VST\Custom Bitfiles, and this forces the user to manually find the bit file. I don’t like that, the distributed VI should have the correct path to the bit file so that the user can use the VI directly.
I have found out that the path to the bit file in the distributed VI is relative to a temporarily build path used by the package builder. So, I have tried using several different temporarily build paths, but I have never been able to find a relative path that is correct. Even if my distributed VI seems to have the correct relative path to the bitfile it cant find the bitfile… Any suggestions for how to use the Open FPGA VI reference successfully on a distributed VI?
Regards
/Gunnar

Hi Gunnar,
What version of LabVIEW do you use? Something new in LabVIEW 2013 is the "Open Dynamic Bitfile Reference". With this, you could use e.g. an "Application Directory" node and build the path at runtime:
http://zone.ni.com/reference/en-XX/help/371599J-01/lvfpgahost/open_dyn_bitfile_reference/

Moved Project To Knew Computer After Everything Is Named-Drive Formatting?

Did search, and seems to be a common problem, but there are a little differences. In the past, when moving project, after starting, everything just showed up. This time, the red lines everywhere. Tried renaming file to clip and vice-versa, and nothing. Double-checked and have all the media. I thought the pathway pointers were imbedded, maybe not. Do have sub-clips. Did hear some talk about how the original media(P2 DV)is saved, can affect it. Was original saved to portable firewire drive that is Fat 32 to capture P2 in the field for Macbook pro. New media drive is extended. Any help is appreciated.

Assuming that you have canvas and/or viewer set to "image" not "wireframe" the only thing I can say is that you double check again that you have the most updated version for Motion or a version that your FCP version would expect to connect with. I have seen other people experiencing this, the answer could be the awkward worst case scenario you want to avoid or simply an update inadvertently missed. Rather difficult to establish without investigating further within your actual workstation.
G.

A series of video files (0001.MTS to 0005.MTS) were imported into premiere, when moved to timeline premiere combined them and made them look like one long clip nmed 0001.MTS. Multiple motion edits and opacity edits were made. When project manager moved th

A series of video files (0001.MTS to 0005.MTS) were imported into premiere, when moved to timeline premiere combined them and made them look like one long clip named 0001.MTS. Multiple motion edits and opacity edits were made. When project manager moved the project, the actual video content of 0002.MTS to 0005.MTS was missing(source clips are still there but they were playing and working as part of that 0001.MTS timeline clip before). Those parts of the 0001.MTS clip in the timeline were Danger Striped and can be relinked but now have no edits anymore. The edits are apparently only linked with the original 0001.MTS source clip but extend beyond the actual range of the actual source clip. At the time I thought it was weird that premiere displayed the whole string of clips as one (with one name and no breaks) but it all works in the original project file but cannot be transferred to another location without multiple clips showing Danger Stripes.I need to move it and preserve the dozens of motion and opacity edits linked to the apparently oversized timeline clip. HELP!! any ideas?
I did not nest any clips or sequences, premiere just seemed to combine the clips under one name when I moved them to timeline.
I am using CS5.

A series of video files (0001.MTS to 0005.MTS) were imported into premiere, when moved to timeline premiere combined them and made them look like one long clip named 0001.MTS. Multiple motion edits and opacity edits were made. When project manager moved the project, the actual video content of 0002.MTS to 0005.MTS was missing(source clips are still there but they were playing and working as part of that 0001.MTS timeline clip before). Those parts of the 0001.MTS clip in the timeline were Danger Striped and can be relinked but now have no edits anymore. The edits are apparently only linked with the original 0001.MTS source clip but extend beyond the actual range of the actual source clip. At the time I thought it was weird that premiere displayed the whole string of clips as one (with one name and no breaks) but it all works in the original project file but cannot be transferred to another location without multiple clips showing Danger Stripes.I need to move it and preserve the dozens of motion and opacity edits linked to the apparently oversized timeline clip. HELP!! any ideas?
I did not nest any clips or sequences, premiere just seemed to combine the clips under one name when I moved them to timeline.
I am using CS5.

How to close FPGA reference out from different while loop

Hi Friends,
I`ve different while loop which performs the FPGA read port on different loops I`ve the FPGA out on every terminal at the end of the while loop. I`ve just connected the merge error function in which all the error out of the FPGA are combined and given to simple error handler. How to close the FPGA Reference.

Can you attach your VI? I'm not clear on what you mean. Are you saying that you are using the FPGA reference which is passed into multiple loops, and then continuing the reference wire to pass the ref out of each of the multiple loops?
If that is the case, I don't believe you can't merge references like you can error clusters. You will just need to wire one of the reference to the close FPGA VI. Additionally though, I'd recommend that you use your error clusters in some manner to ensure data flow so that all the other loops stop first, and you are sure you are closing the reference after all the other loops are done with the ref.

Bridge CS5 closes when moving files

Bridge CS5 abruptly closes when moving files. It does not matter if I drag and drop or if I cut/copy and paste to different folders -- I get the same behavior either way. When I try to move files, I get a Windows dialogue box saying the program has experienced a problem and will close. After Brdige closes and I open it again, the files have been moved. Still, it is a pain to have the program crash everytime I move a file.
I have a new computer with great specs and lots of memory (see below). I did not have this problem before and only began to experience it recently. The only changes since then are that I downloaded a trial version of Adobe Dreamweaver. I found another instance of this problem in the forums and followed the advice of disabling all scripts, but it did not help. What can I do to move files in Bridge?
Computer: Studio XPS 9100
Processor: Intel Core i7-920 processor(8MB L2 Cache, 2.66GHz)
RAM: 12GB DDR3 SDRAM,1333MHZ, 6x2GB
Video Card: ATI Radeon HD5670 1GB GDDR5
OS: Windows 7 Home Premium, 64bit, English

I have a computer setup very similar to yours, in fact you have one notch higher ram and video card. It should work. I do use drag and drop sometimes, but almost always use right click and "copy to". It will list the last 10 places you have visited so it is easy to click on the folder (or visit it first). More of a hassle if you have to browse.
I had to add "copy to and move to" to the right click function in Vista and Win7. Check on-line and there is an automatic program that inserts it into the registry. It confident instructions are given to do it manually.
Have no idea why it will not work. Can you drag and drop in Win Exp?
Hope this helps.

InDesign CS 5.5 - links break when folder is moved

I'm running OS X 10.5.8 on a 2.66 GHz Dual-Core Intel Xeon with 2 GB 667 MHz DDR2 FB-DIMM.
Ever since I upgraded from CS3 to CS 5.5, the links in my publications break when I move the folder they're in. This never happened with the older versions. Usually if the entire folder was moved, the links stayed intact. Our workflow makes it necessary to move the folder twice during the production process, and it can often take quite a long time to wait for the files to relink.
Does anyone know if there's some sort of default setting I can turn off to stop this???
Thanks,
CQ

Since this is an application-specific question, it would be best to ask this in the InDesign forum.

Use of "Open FPGA VI Reference" function --- Build Specification vs VI vs Bitfile

When using the "Open FPGA VI Reference" function in a LV2012 cRIO application, there are 3 options: Build Specification, VI, or Bitfile. What would be the reasons for selecting one over the others? Does it affect the resulting startup.rtexe when the cRIO application is built? I searched through the help and in these forums, but I don't see criteria for selecting one over the others; maybe I missed it.

Hello Chris,
Apologies in advance for a long reply.
The reference method won't change the functionality of your rtexe.exe. They all end up dropping a bitstream, based on a bitfile, onto the cRIO's FPGA.
To a degree, the method used to reference the FPGA code is a matter of taste, but there are situations where one method is better suited than the others.
Reference by VI:
Setting the configuration options to open reference by VI is helpful during development when you are making changes to an FPGA VI often and building/testing using the same spec. When this option is used, a bitfile is selected based on the default build specification for the project. A project may have only one default build specification. You can make any build the default by checking the option under the Source Files category in the build properties. The default build is indicated in the project explorer by the green box around the builds icon.
Reference by Bitfile:
This option references a bitfile directly. Through the configuration window, you can select one specific bitfile to open a reference to (this is not dynamic and does not change unless you physically go make a change to that path). If you're using this method, it helps to give your bitfiles more meaningful names than the ones that are automatically generated by LabVIEW. When you run subsequent compilations off of the same build specification and do not change the bitfile nname or path in the build configuration, the old bitfile is overwritten and replaced with the new one. When you are using this option, it is critical that you keep up with which bitfile is the one you want to be using. There is an option now that will help alleviate any problems referencing by bitfile through the Open FPGA VI Reference function. There is a new VI called Open Dynamic Bitfile Reference. It is typically used when you want to chose a specific bitfile to load depending on something in your host code (a configuration option etc) - but it allows you to dynamically reference a bitfile on the block diagram by path.
Referency by Build Specification:
This option is good for when you want to always use a bitfile that is associated with/compiled with the same build configuration. Say you have two options for top level FPGA VIs in your project (each with its own build spec). Both of these VIs have the same interface (read/write controls, DMA) but they run different algorithms or something. This is nice because you can easily switch your host application between them by picking the build spec associated with the FPGA VI you want to use. In this type of sutation, referencing by VI is no good because you can only have on default build spec.
cheers.
Matthew H.
Applications Engineer
National Instruments

Error message when moving to a different page

Post Author: EvDev
CA Forum: .NET
I have an ASP.NET 2.0 and Crystal Reports 11.5 project that works fine
when it's being debugged and when it's on our test server, but when we move it
to our production server the user will receive an error message when moving to a
different page of the report. It's an
"Object reference not set to an instance of an object". It seems very
odd for me for something to work on the test server but not on production. Has
anyone seen this before? Thanks

Hi there,
This does seem like a very valid process to be sure
I'm guessing that the fix is shown in "Solution 1" in this doc;
http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_tech_note09186a0080b04158.shtml
Cheers!
Rob

Close FPGA VI Reference breaks when moving project...

Similar Messages

Maybe you are looking for