Neil Pate

OK, hopefully gotten to the bottom of it. Looks like it was just a messed up installation of LabVIEW. Removing everything NI related and re-installing the runtime seems to have fixed it.

Is there a holding thumbs emoticon?

Hi All,

I have a strange error which manifests itself on some of the PCs I am trying to run a built application on. I stripped everything out and have traced the error down to a single VI, OpenHandle.vi in the HTTP library which ships with LabVIEW. The error code I get out seems to point to something fundamentally wrong with this PC as it is saying "Failed to load library".

This does not happen on all PCs, only some. Does anybody know if the HTTP VIs call some DLL or something (the VI is password protected) that I should be distributing with the application?

Has anybody seen this error before? Google does not seem to know much about it.

If you want to make sure, then open a VI in the project and go to the VI Properties.  In the List Unsaved Changes dialog it will tell you what version the file was last saved in.

Thanks, I did not know about this feature.

Sure enough it is 2010. Now I am really confused as I would have bet (and lost) a lot of money that it was 8.6!

Thanks Shaun,

I am quite surprised by this as I was pretty sure it was 8.6. Now I have to do a bit of thinking!

Hi All,

I have some old code I need to make some changes to, and am not certain what version of LV it is done in. I so not have those old versions installed on my PC, and don't really want to install the wrong version.

The .lvproj has <Project Type="Project" LVVersion="10008000"> in it, does anybody know if this is 8.6 or 8.6.1? My suspicion is that is it 8.6.1

Thanks

Neil

Hi Neville,

 

Thanks for the thoughts.

 

Addressing things:

1) The globally shared reference seems interesting. Do you encapsulate it in a functional global or just a raw global?

 

2) I don't open multiple references continuously. I open one for one loop, one for the other. In the past I've tried just opening a single reference and branching the wire, but that seems to be even more unreliable.

 

3) Whether or not FPGA inputs update is dependant on whether at least one Open Ref manages to complete. (Because of my architecture/separation of responsibility). In some cases, one ref will acquire succesfully while the other will fail.

 

4) FPGA outputs are internalised in this case.

 

5) Memory & CPU is stable while running. This is a restart to restart problem (or appears to be). When I say they become unresponsive "after a while", I mean that, after a random number of system restarts, one or more Acquire Reference operations can fail.

 

Thanks again for your thoughts on this.

Have you considered you may just have a dud FPGA card or problem with the PCIe/PXI bus? I did some work on a system that has an industrial PC with a PCI bus extender, and had lots of very strange hardware problems that just went away when we used a different PC vendor.

I posted it here.  Unfortunately, I feel in that presentation I spent too much time on the inner workings (some of which are complicated), rather than on the use of the API (which I hope is simpler).  

Thanks. I am trying to understand it from the inside, rather than just a black box, so those slides will be good I think.

In the course of getting to grips with things I will probably knock together some really simple examples teaching myself the API, if I end up with anything worthwhile I will upload.

James, can you post your Euro-CLA summit presentation slides? Trying to dive straight in with this example is too much for me to grok.

Got it to run, time is not on my side though so not been able to poke around.

I like the debug message window 

Will dig in over Christmas hopefully :-)

 As far as implementation I take a labview class and stuff it inside a DVR and pass the reference around, I am not sure what the name is for this type of implementation.

I think could be called "the more popular implementation of ByRef LVOOP"   or TMPIOBL, it just rolls so easily off the tongue

I just rename them and let the SCC record the old class as deleted and the new one created.

Yup, rename inside LabVIEW and let the VCS tool worry about tracking the file-system changes.

Apprarently it's due to Dynamic Events! I've trimmed my code down, painfully removed all classes and DVRs (legacy fears) and the memory leak was still apparent. Now I've realised the rate of memory absorbption is exactly proportional to the rate of User Event Generation.

Ouch... that is quite worrying!

I do recall a colleague having quite a bit of memory problems with large 2D string arrays. The memory would never de-allocate even after the VI had finished running. This problem was unique to strings, it did not occur when the data type was changed to something else.

This was LV2012, so perhaps it has been fixed.

Rocking!     

I wonder how long has this been a feature?

Hi all,

So this has bugged me for basically forever. Is there a simple way to apply a library style icon to a single VI or control that was not previously part of the library?

I know it can be done using the properties dialogue of the library, but that applies the icon to all the VIs in the library which is really not desirable most of the time as then many other VIs need saving.

This happens a lot when I create a new VI or control and realise it probably belongs in a different library to the one I initially created it from.

Am I being stupid here and there is a menu option somewhere I have never noticed? 

Thank you Yair.

Format "painter" for FP controls/indicators (and perhaps BD constants) would allow the quick copying of the formatting from one object to another.

Click here!

Hi there,

Can anybody point me to the correct sub-forum on lava to post old NI idea exchange things so they can maybe get more traction? I seem to recall there being a sub-forum called "Orphan ideas" or something like that, but my search-fu has failed me.

thanks

n 

I add a vote to not taking this feature away.

Like others have said, I sometimes use a separate Event Structure for User Events that can then be packaged away into a sub-VI.

 Perhaps show the user what's taking so long.

Would love to have this.

I have a medium size project (approx 1000 VIs) that I have to maintain, and edit operations are very slow. Drop VI, wait, make a wire change wait etc etc. I have a similar version of the code base where I managed to fix this by re-organise the hierachy a bit (literally just moved one VI from a library into another, or made it a global variable or something like that), but I cannot seem to make it go away this time around, and do not have time to investigate.

The delay is almost certainly due to some type propagation checks or something similar, but I have no idea what the offending code is. If the LabVIEW IDE could just give me some way of letting me know what it is doing when it brielfy locks up I would be very grateful. 

My solution is to never, ever rename classes. I'm serious.

Man, I hope I never have to debug any of your code. 

A class (or VI) name should reflect what it does. I feel it is not really acceptable to compromise on this just because the IDE chokes sometimes when doing these kinds of modifications.

“Badly formed query”?  Excuse me?!?       Yes, that comment form is valid SQL.

SQL and I have never been best of friends. Perhaps it is time I dusted off my textbooks again! 

Well, this has just become a lot more relevant for me as a customer just emailed me this: 

 

1097 exception.png

 

First time I’ve seen it.  I use Windows XP while the client uses Windows 7; I wonder if 7 is more unforgiving of “reading someone else’s memory”?

Interesting query. Is the -- comment valid SQL syntax?

Could a badly formed query be throwing the exception?

So I'm on the dark side now?

 

http://lavag.org/topic/16925-controls-change-positions-on-runtime-system/?p=103828

 

neil, I am your father...

 

maybe...

That thread is from June, I told you my memory was bad 

I do seem the recall a thead on the darkside discussing fonts and this was where I first learned this tip. Of course I cannot find the thread anymore. Thanks for the reminder though, Anakin.