In some cases - particularly on computers with Chinese or Korean characters in path names and/or computers where the default Documents folder is on the users One Drive - the application will crash because it can't find the Documents folder. The typical symptom is that nothing really happens when you double-click on the application shortcut.
In these cases an Envioronment Variable can be defined that causes the application to put the IOLab-Workfiles folder (used by the application to store data) in a different location.
If you think this may be your issue you can try the following:
1) Create a folder on your C drive called C:\temp.
2) Open the Environment Variable control panel by typing “Environment Variable” in the windows search bar:
3) Set the environment variable IOLabRootDir to point to this directory using the Environment Variable control as shown below. This will cause the IOLab working directory to be put in C:\temp rather than your Documents folder:
4) Try running the application again.
If the status bar looks like this then your computer has not recognized the IOLab dongle:
This has only been seen in Windows so if you are using a different OS this is not your problem.
You can check for this problem by opening your device manager and looking in the Ports section, which will tell you which devices have been detected and what COM port they have been assigned by Windows:
You should replace the two AA IOLab batteries with new ones. Use the included screwdriver to open the battery compartment on the back of the device. Make sure you are using brand new replacement batteries. Our experience has been that low quality batteries don't last very long and don't end up saving money, so try to use name-brand batteries if you have some available. The battery voltage reading in the Remote 1 status indicator should be well over 3 volts if the batteries are new (shown below):
Some anti-virus software - specifically those designed to stop ransomware attacks - can prevent the IOLab application from writing to the Documents folder. This will cause the application to stop after a few seconds. A common product that does this is called Avast. The following three images show how you can temporarily disable the ransomware feature on Avast, which will allow the IOLab software to run.
Students have reported that if the above approach didn't work they tried uninstalling and reinstalling Avast. After doing this they ran IOLab again and this time a pop-up appeared asking if they wanted Avast to block or allow IOLab, which solved their problem
Similar approaches should work for other anti-ramsomware products as well, like the one built into Windoes 10 (which seems to be disabled by default).
The +Add run button can be used to acquire new data while previos runs are still displayed. The ID's of the data sets is displayed to the left of the charts. If an export is done, either to a CSV file or to the cloud repository, only the last run will be included in the export.
Even though only the last run is exported, all of the runs are saved and can be seen by clicking on to open the Resource manager. Any of the runs can be reparately recalled and exported in this way.