Error: lvanlys.dll – Resource not found.

If you are using an AMD (inparticular AMD Ryzen) processor, you might encounter this issue during the startup of some of our software modules like, e.g., thaTEC:OS or the DataInspector.

With recent versions of thaTEC:Core, this issue is solved automatically after eventually (once) granting Admin rights after the startup of thaTEC:Core.

In order to solve this issue manually, you need to add a new environmental variable named “MKL_DEBUG_CPU_TYPE” with a value of “5”.

To do so, please follow this procedure:

  •  Press the windows key, type “environment“, and select “edit the system environment variables“.
  • In the System Properties window, click on the “Environment Variables” button.
  • In the upper “User Environment Variables” section, select “New“.
  • Insert “MKL_DEBUG_CPU_TYPE” in the field “Variable Name“.
  • Set “5” as “Variable Value“.
  • Apply the changes and reboot your PC.

If you still encounter this issue, please contact us under contact@thatec-innovation.com

Add a network device to the VISA device list

Devices connected to the PC via USB or GPIB are usually automatically detected and can be selected from the dropdown list of the Device address control. Devices which are connected via ethernet are not detected automatically but the device adderss must either be entered manually in the form

TCPIP[board]::host address[::LAN device name][::INSTR]
e.g. TCPIP0::192.168.0.1::INSTR

or the device can be added to the device list using NI MAX. For instructions and more information, visit

https://www.ni.com/getting-started/set-up-hardware/instrument-control/ethernet-connect

Open a remote support session

Developing software modules for your hardware usually requires a debugging process. If the according PC is connected to the internet, the easiest way to debug the software is to schedule a remote support session with us so we can directly access your PC and debug the software modules.

Please note that no additional software needs to be installed!

To open a remote support session select Support => Open remote support session from thaTEC:Core’s menu bar:

The module might take some time to start. However, if any error message occurs or nothing happens, please update the support database as described here.

After the startup of the remote support module, the following window will appear, waiting for our remote access:

After connecting to your PC, you will need to grant access to your PC via the following window which will appear and will remain during the whole session allowing, e.g., to write text messages and stay in touch during the remote session:

Important note: During the remote support session, we will only have control over your mouse and keyboard as long as you are not using it. Thus, please do not use the accoring PC for other tasks during a remote support session!

Problems with reading/writing files

1) Is your file path to long? (Path length is restricted to 260 characters by Windows)
=> Solution: Try to copy file to another location / change file path

2) Check file or folder names for special characters

 3) Accessing the data file with, e.g., the thaTEC:DataInspector during the measurement can cause issues due to the simultaneous file access.
=> Solution: Check your live data only via thaTEC:OS !

How can I see the changes if an update for a software module is available?

It is possible to open the current changelog of the module before installing the update. For this, just right click on the respective module and select “Update” => “Open updated changelog”

Issues updating thaTEC:Core

In the latest versions, we changed the self-update procedure of thaTEC:Core. Thus, if you are using an older version (before 2019-08-06), the update is not always performed correctly and it might  still be indicated that a new update is available. In this case, please download the Core_updater module from the module library and run this module to manually perform the update.

The min/max values in scan definition in thaTEC:OS are not correct

During the connection process of a driver module to thaTEC:OS, the min/max values for each control are obtained from the properties of the individual controls and transmitted to thaTEC:OS. If the min/max values in the scan definition are not correct, there are possible origins.

1) The min/max values of the control were changed during the program runtime after the connection to thaTEC:OS. In this case, the properties need to be re-sent using the properties.vi. Please see also the example in the programming template (current range control).

2) Check the representation of your control. For example, currently, single precision (SGL) values are not recognized, thus, please change the representation of the control to integer or double precision.

Connection error to thaTEC:OS

Device module cannot connect to thaTEC:OS

=> Solution: Check connection settings in thaTEC:OS and in the device module via the menu bar > Communiation > Settings. If thaTEC:OS and the device module are on the same PC use the same PC setting.

Missing data points

Accessing the data file with, e.g., the thaTEC:DataInspector during the measurement can cause issues due to the simultaneous file access.
=> Solution: Check your live data only via thaTEC:OS !

See also Problems with reading/writing files

Labels/buttons in the user interface seem to overlap

This can happen if the Windows display settings has been set to a scaling value of larger than 100%. We try to develop our software modules in a way that this does not happen. However, if you are having trouble with this, the best solution is to set the display scaling to 100%.