LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

error: Undefined symbol '_NewAsyncTimer@24' referenced in "f:\程序 CVI - 副本 2 - 副本\cvibuild.test_face\Release\test_face.obj".

Solved!
Go to solution
It was originally a program that could be run. After copying it to a new computer, it appeared when compiled, and the compilation failed.
0 Kudos
Message 1 of 4
(2,540 Views)

It seems the asynchronous timer instrument is not loaded when you compile your project.

The instruments like that can either be loaded in Instrument menu or in Library menu: while in the first case the choice is remembered in the project, in the latter case this is not true and this may be your problem. Check the original machine and look after the Async Timer instrument, then reply this setting in the second machine and all should begin working again.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 2 of 4
(2,478 Views)
Solution
Accepted by topic author 232356

Hi,

One possibility would be the async timer library not located correctly in the new computer. You might need to add the async timer library to your environment.

Try to resolve it by:

1. Going to Library->Customize in LabWindows/CVI
2. Browsing for the asynctmr.fp file (for example, normally located at C:\Program Files (x86)\National Instruments\CVI2017\toolslib\toolbox) and adding it to the user libraries
3. Restarting LabWindows/CVI.

0 Kudos
Message 3 of 4
(2,461 Views)

Hi,

One possibility would be the async timer library not located correctly in the new computer. You might need to add the async timer library to your environment.

Try to resolve it by:

1. Going to Library->Customize in LabWindows/CVI
2. Browsing for the asynctmr.fp file (for example, normally located at C:\Program Files (x86)\National Instruments\CVI2017\toolslib\toolbox) and adding it to the user libraries
3. Restarting LabWindows/CVI.

0 Kudos
Message 4 of 4
(2,461 Views)