03-10-2009 12:38 PM
I have an insturment driver LLB that is a total mess now.
It started out as a LV 5.11 LLB
I am working in LV 8.5 now and LV 8.5 will not open code written in LV 5.11 (Too old)
I have tried to mass compile it in LV 8.2 but I still am running in to VI's in the LLB that are too old for LV 8.5 to open.
That means they are still in LV 5.11.
Do I really have to open each and save every single VI in the LLB in LV 8.2 to be able to use it in LV 8.5?
03-10-2009 01:18 PM
03-10-2009 02:02 PM
03-10-2009 02:36 PM
Here is the LLB in question.
I don't know how many times I have mass compiled it, but just today the HP34970A Close.vi is still in LV5.11 and LV8.5 will not open it.
03-10-2009 02:48 PM
03-10-2009 02:58 PM
03-10-2009 03:11 PM - edited 03-10-2009 03:12 PM
Dennis Knutson wrote:
I was able to mass compile it. I did notice that you did not include the hp34970u.llb. Did you point to this during the mass compile. Also, this llb is long obsolete. There is a nice, modern 8.5 project style driver available as well as a plug and play driver. Why do you even need to convert this?
I have mass compiled it with out errors too, but it seems like it was not really compiled as I still keep running into vi's in it that were still in 5.11.
I have a decade (or more) of 5.11 code that I am maintaining and upgrading when I have a chance.
Production test is still coding and deploying LV 5.11
I have tried the newer version of the 34970A driver but it is missing some of the vi's that many of our 5.11 codebase uses so is is not a drop in replacement for upgrading code.
Here is the "u" llb too, I forgot to attach last time
03-10-2009 03:48 PM
I just downloaded the latest hp34970a.zip from:
to make sure I was not missing something.
It is missing the HP34970A Scan Memory.vi
So using the "nice, modern 8.5 project style driver" breaks all the programs I have to support.
03-10-2009 05:00 PM
There is a least one function missing in the 'u' llb (Utility Clean Up Initialize) but I still had no problems doing a mass compile and none were left as 5.1. Besides the Close which was already posted, what other VIs do you need?
Well, I once had a couple of hundred 34970's in service and always tried to keep the drivers up to date but I was lucky since the products had a much shorter life cycle so the old programs quickly became obsolete. There are so many other changes since 5.1 (i.e the event structure being a HUGE change), that the programs might benefit from a rewrite anyway.
03-10-2009 05:14 PM
I think I have it straightend out.
Part of my problem is LV was pulling the llb from my flashdrive when it was plugged in.
Keeping different LV versions seperated is a real pain in the you know what.
I find that if I need to open something in 8.2 to convert it from 5.11, next time I open 8.5 it pulls vi's and llb's from the 8.2 subdirectory.