FPGA Disapearing Controls when copy and paste into VI

[wideofthemark]

Hi,

Strange effect here. I have a Vi which if i try to create a new control - or copy and paste a block diagram of controls into it , the controls don't appear on the front panel - although they are still on the block diagram.  It is a FPGA vi - but not sure if it is particularly FPGA that is misbehaving rather than the labview interface itself.  It seems like the problem may be an extreme version of the problem where new controls get sent to the middle of nowhere on the front panel if you copy to the block diagram - although in this case they don't appear to be anywhere - if you double click on them then you get taken to empty squares. 

Not sure if it is something to do with having a very long standing vi which i have been editing\adding\deleting stuff - so that somehow it has got to a state where it thinks the front panel is too full or something?  Anyone seen this before (and or have a solution to fix it).  It's really starting to bug me - because as a general rule it is best to test and develop FPGA stuff on a separate VI and then copy it into the main personality VI - but if this happens then it is a bit of a disaster.

** I have attached a project with a file in it that has reached this state of controls being off the front panel - if someone wants to check it out.  Basically some of the controls are on the front panel some are non existant. NOTE - the VI itself won't do anything useful - i deleted all the references to FPGA IO etc.

[wideofthemark]

...

[niNickC]

Hello,

Yes I can see the problems you are having. I will have a look at this over the next few days to see if I can discover anything.

Can I ask what version of LabVIEW are you using to develop your application?

[wideofthemark]

Thanks for looking at this for me.

Labview version - 2010 SP1.

V10.0.1 32 Bit

Working on a windows 7 system.

JP

[niNickC · Accepted solution]

Hello,

I've had a look at this and at the moment the only solution I have is to copy the block diagram into a new VI. Once in the new Vi controls can be copied in and behave as normal.

Unfortunately the VI has become corrupt somehow. Are you working with this VI off a network? This can often cause problems as things get corrupted in the network communication.

[wideofthemark]

Thanks,  I figured I might have to do something like that.  It seems like it still complains a little after copying into a new VI - you have to replace some of the controls that have disapeared - but after playing around a bit I got it to work again. 

As for the cause - I'm remoting into a computer over a network - but mostly the files are all on the computer itself.  My suspicion is that it is the fact that I had been using the same VI as a base for so long - copying loads of different variations of the code into it over the course of a year or so.  I think the revision number was on 300 or so.

Anyway - thanks for looking at it for me.

[niNickC]

That no problem,

We do occassionaly see problems with remotely stored VIs but I doubt a remote connection would make any difference!

I'll try to keep this thread in mind if I ever see anything else like this or hear of any better fixes.