LabVIEW
Zebra ZD420 - checking for "downloaded" fonts
Solved!
@Mark_Yedinak wrote:
Crete a virtual folder named "resource" in your project. Add the file c:\Program Files (x86)\National Instruments\LabVIEW <VERSION>\resource\lvimptsl.dll to the virtual folder. In your application builder add this to the Always Include section.
Also, just to confirm you, your are using the 32 bit version of LabVIEW. I doubt very much this USB library will work in the 64 bit version.
Mark, there is a good chance that you can get rid of that lvimptsl.dll altogether. Most locations where you use the GetValueByPtr VI macro are actually completely superfluous. I took a stab at following functions to remove that completely:
Get Port Status.vi
Get Last Error.vi
There are other things that could be optimized such as your parsing of the binary response using the Regular Expression node, but that is more a cosmetic issue.
The only thing that I saw at a quick glance that can't be easily simplified like this is the actual Get Printer Information.vi which needs a pointer to work with all the other functions. However that GetValueByPtr could easily be replaced with a direct call to the LabVIEW MoveBlock API so that your entire library won't depend on the special LabVIEW DLL anymore.
I would also change the Printer Data Buffer Reference throughout your VIs to be an U64 value and change the according Call Library Node parameters to be a pointer sized (unsigned) integer. Even though you only have a 32-bit DLL by now, if you ever get a 64-bit version by your developer, your VIs are already prepared to deal with that for this parameter.
@rolfk wrote:
@Mark_Yedinak wrote:
Crete a virtual folder named "resource" in your project. Add the file c:\Program Files (x86)\National Instruments\LabVIEW <VERSION>\resource\lvimptsl.dll to the virtual folder. In your application builder add this to the Always Include section.
Also, just to confirm you, your are using the 32 bit version of LabVIEW. I doubt very much this USB library will work in the 64 bit version.
Mark, there is a good chance that you can get rid of that lvimptsl.dll altogether. Most locations where you use the GetValueByPtr VI macro are actually completely superfluous. I took a stab at following functions to remove that completely:
Get Port Status.vi
Get Last Error.vi
There are other things that could be optimized such as your parsing of the binary response using the Regular Expression node, but that is more a cosmetic issue.
The only thing that I saw at a quick glance that can't be easily simplified like this is the actual Get Printer Information.vi which needs a pointer to work with all the other functions. However that GetValueByPtr could easily be replaced with a direct call to the LabVIEW MoveBlock API so that your entire library won't depend on the special LabVIEW DLL anymore.
I would also change the Printer Data Buffer Reference throughout your VIs to be an U64 value and change the according Call Library Node parameters to be a pointer sized (unsigned) integer. Even though you only have a 32-bit DLL by now, if you ever get a 64-bit version by your developer, your VIs are already prepared to deal with that for this parameter.
Thanks for the suggestions. I will take a look at them. This library was written about 15 years ago and has been not been updated very frequently.
@Mark_Yedinak wrote:
Crete a virtual folder named "resource" in your project. Add the file c:\Program Files (x86)\National Instruments\LabVIEW <VERSION>\resource\lvimptsl.dll to the virtual folder. In your application builder add this to the Always Include section.
Also, just to confirm you, your are using the 32 bit version of LabVIEW. I doubt very much this USB library will work in the 64 bit version.
Hi Mark,
finally got the printer back and had a look this morning . . . so I added the lvimpts.dll to a virtual folder and then added it to the always include section
I rebuilt the EXE and . . .
the printer isn't found by name.
From the Dev environment . . .
. . . the same dialogue shows the printer is found by name.
@RaptorUK wrote:
@Mark_Yedinak wrote:
Crete a virtual folder named "resource" in your project. Add the file c:\Program Files (x86)\National Instruments\LabVIEW <VERSION>\resource\lvimptsl.dll to the virtual folder. In your application builder add this to the Always Include section.
Also, just to confirm you, your are using the 32 bit version of LabVIEW. I doubt very much this USB library will work in the 64 bit version.
Hi Mark,
finally got the printer back and had a look this morning . . . so I added the lvimpts.dll to a virtual folder and then added it to the always include section
I rebuilt the EXE and . . .
the printer isn't found by name.
From the Dev environment . . .
. . . the same dialogue shows the printer is found by name.
Did you add it to a virtual folder named "resource"? Also, did you include the resource folder as a destination in the build spec?
You can also try an experiment and go to the folder where you placing the application (exe) and se if the resource folder with the lvimptsl.dll file is there. If not, try copying it there and run your application again.
If this doesn't work, the add some debug code to your application to output all of the results of the printer enumeration. Compare this with what you see in the development environment.
