05-26-2017 05:36 PM
The VI works great to extract the individual VIs from the llb, however, the VI name was not working in LabVIEW 2014 (did not test in other versions). In LabVIEW 2014, the VI name is stored at the end of the VI content and always starts with "80 FF FF FF FF", the 12th byte after this string is the size of the VI name. the VI name follows that size.
The updated repair VI is attached. VI names other than .vi were not tested.
10-08-2022 08:26 AM
Thank you for posting this vi. Unfortunately, though, it doesn't seem to work with a corrupted (or even non-corrupted) llb under LabVIEW 2022 Q3. Perhaps this is because of a change in llb format between LabVIEW 2014 and LabVIEW 2022?
Enclosed is a test llb under LV 2022. I would be very grateful for any advice.
Best,
Lyle
10-08-2022 12:07 PM - edited 10-08-2022 12:09 PM
@KoenVervaeke wrote:
Thank you for posting this vi. Unfortunately, though, it doesn't seem to work with a corrupted (or even non-corrupted) llb under LabVIEW 2022 Q3. Perhaps this is because of a change in llb format between LabVIEW 2014 and LabVIEW 2022?
Enclosed is a test llb under LV 2022. I would be very grateful for any advice.
Best,Lyle
------------------------------------------------------------ -- Lyle J. GrahamNeurophysiology of Visual Computation
Centre Giovanni Borelli - CNRS UMR 9010Université Paris Cité
45 rue des Saint-Pères, 75006 Paris, FRANCE
Tel: [33]6.01.36.66.74
http://lyle.neurophysics.eu/------------------------------------------------------------ --
Maybe NI finally deprecated them? They've been trying to move away from llb files ever since LV 8.x when they went to project files, for a couple of reasons, losing the whole project because of a corrupt llb is one of them.