Prev: LIN control application
Next: Labview 8.2 is very forgivable..
From: maximint on 12 Jan 2007 08:40
Hi, thanks for you Codesoft VI. I tried them now with success, this means, at startup of my program, I run one time the OPEN, INIT etc. and multiple times the PRINT.But one problem still occurs:I tried to simulate our future main VI: as described, calling one time the OPEN, INIT etc and then running a while loop where I can start your PRINT VIby pressing a button. Here I found that the print of the label isn't realized immediately. It takes some seconds. Too long for our production. I guess that the while loop takes too much performance and the activex component doesnt get enough.Therefore I want to wait for the event "End Printing" and tried to handle this with the attached VIs. But although the printer is ready, I cannot recognize the corresponding event.Could you have a look, pls. Thanks.


ActiveX Event Callback for Codesoft.vi:
http://forums.ni.com/attachments/ni/170/223889/1/ActiveX Event Callback for Codesoft.vi


end printing event call back.vi:
http://forums.ni.com/attachments/ni/170/223889/2/end printing event call back.vi
From: rolfk on 12 Jan 2007 10:10
maximint wrote:Hi,thanks for you Codesoft VI. I tried them now with success, this means, at startup of my program, I run one time the OPEN, INIT etc. and multiple times the PRINT.But one problem still occurs:I tried to simulate our future main VI: as described, calling one time the OPEN, INIT etc and then running a while loop where I can start your PRINT VIby pressing a button. Here I found that the print of the label isn't realized immediately. It takes some seconds. Too long for our production. I guess that the while loop takes too much performance and the activex component doesnt get enough.Therefore I want to wait for the event "End Printing" and tried to handle this with the attached VIs. But although the printer is ready, I cannot recognize the corresponding event.Could you have a look, pls. Thanks.



Sorry not for the moment. I'm actually only doing the init at program startup, loading a new template whenever is required, replacing the template variables as needed and then printing it out. Most software has a serious delay from the moment starting the print command until data is actually rendered and passed to the printer driver. I'm not sure you can get sub seconds reaction with standard Windows printing at all. Anyhow for me it is not a problem at all as I print a label only after some more or less lengthy test procedure when the tests have succeeded so printing even if it takes a few seconds is fast in comparison to the rest.
Rolf Kalbermatter
First  |  Prev  | 
Pages: 1 2
Prev: LIN control application
Next: Labview 8.2 is very forgivable..