To start the EUI without dialog boxes follow these steps:
Please check with Eric Coughlin as the HMI software may already be installed on one of the ATS machines.
If not then liaise with Eric to decide which machine to deploy it on.

Instructions :

1. Open the “HMIConfig.xml“ located inside the EUI repo:
“HMIComputers/Configuration” 2. Here modify the following items to
set them as FALSE:

• <DebugTMAComm type="Bool">FALSE</DebugTMAComm>
• <AutomaticTestingSystemShowProcess
  type="Bool">FALSE</AutomaticTestingSystemShowProcess> 3. Now
  relaunch the EUI and there won’t be any additional dialog boxes.

Dave Mills and Eric Coughlin, what is the repository you need me to test?

If code is needed from Tekniker gitlab, navigate to the LabVIEWCode/HMIComputers

I can not access the one of submodules in LabVIEWCode/HMIComputers:

[submodule "tcp_framework"]

	path = tcp_framework

	url = ../../../../libraries/labview/tcp_framework.git

I tried to open LSST_HMIs.lvproj and it looks for the TDMSSaving.lvclass. In additional to this, I have the multiple error messages for the path and default reference templates:

It looks like the code did read the configuration file for interested items:
  

There are two top-vis:
1. HMIMain_EUI.vi
2. HMIMain_HHD.vi

But for the exectuable, only the HHDValidation is for the HMIMain_HHD.vi. The EUIValidation does not contain the HMIMain_EUI.vi:

The configuration files contain the following formats: ini, csv, txt, and xml.

The implementaion of FGV is by the "Feedback Node" instead of the "shift register". It looks like some people did use this method: feedback node global.

Some vis have the documents and some do not have.

The code contains the OOP, GV, FGV, and pure functional vis (mainly the view vi parts). Some vis have no callers, and this means the project might need to do some cleaning.

For the GV, it looks like the vi name will begin from GBL_. They are under different directories.

For the FGV, it looks like the vi name will begin from FGV_. Most of them are under the same directory.

I could only make sure the code did read the configuration file to decide the show-up windows. However, it looks like there is some problem for the repository to do the further test or modification:
1. The access of submodul (tcp_framework) is not in the (LabVIEWCode/).
2. The LabVIEW project contains some internal Tekniker template that are in the root of labview directory instead of repository. These templates may need to move to this repository. I will suggest to let the Tekniker modified the code to make sure the code can be cloned and run in a pure and clean virtual machine.
3. For the configuration files of ini, txt, and csv, it might be good to make sure the Tekniker has the documents to explain the details.
4. Please consider to let the Tekniker to fix the build of executables.

PS. Please see the comments in ticket to know the details.

Thanks!

OK, I guess we need another go-round with Tekniker