Solutions for potential network scan issues with test.con
Windows 11 test.con scan issue
After the update to Windows 11 the test.con network scan may have some issues. There is a workaround to get test.con to connect to a known controller by editing a file in the test.con installation directory.
Navigate to: C:\Program Files (x86)\Gantner Instruments\test.con V7.0.0E R1(B01)\BIN
Open GiComTCPIP.lst that contains entries of the last devices found.
[GLOBAL]
NUMDEVICES=1
[DEV1]
IsDeviceSupported=1
IsCloudDevice=0
IsTCRDevice=0
IsConnected=1
HasUserApp=1
UserAppHasPasswd=0
UserAppIsOccupied=0
HasStartApp=1
StartAppHasPasswd=1
StartAppIsOccupied=0
HasRtApp=1
RtAppHasPasswd=0
RtAppIsOccupied=0
serialNo=751898
location=Undef
type=Q.station 101 DT
firmware=V2.15 B02 2023-07-07
ipadr=192.168.178.53
modulid=MK175007#
deviceid=??????
The file only exists if a scan has worked once. Otherwise, a text file must be created or the file linked here must be used as a template:
https://dev.gantner-instruments.com/webfiles/public/Download/Support/test.con_default/GiComTCPIP.lst
user: support
pw: gins
Manual editing is rather inconvenient, but editing the entry at least allows you to continue working with the Windows 11 computer. It is recommended to always enter the IP address, serial number and type of controller. The connection should directly depend only on the IP. Serial number and type have been added so that you know which controller you are trying to read.
Update the 32-bit test.con.exe, which should fix the error:
https://dev.gantner-instruments.com/webfiles/public/Download/Support/test.con_default/test.con_V7.0.0G_R1B01.exe
user: support
pw: gins
Network Scan Patch
For some PCs there is a patch for the network scanner that can improve scan results
Replace the dll and application files from the zip file in the test.con directory
C:\Program Files (x86)\Gantner Instruments\test.con V7.0.0E R1(B01)\BIN