Prebuild step of the veristand Custom Device template fails

[ARLROB]

I am using the Veristand Custom Device Template to start a new custom device, when I try to build my :configuration I get a build error, I know the error is related to the pre-build step.  Any ideas?

[ZYOng]

I guess you are following the steps in Implementing a Custom Device — VeriStand Custom Device Handbook 

The error comes from Utility\LLB Pre-Build CHM Build.vi

This pre-build VI assumes a CHM file name with "Custom Device" appended to it but the actual CHM generated does not have it. What I usually do is write the file name in that VI. 

[BigApple0]

After debugging the same exact error, I have to say whoever designed the CHM Builder is a moron. The way "LLB Pre-Build CHM Build.vi" and "Build CHM.vi" work are asinine.  They both make terrible assumptions on folder NAMES and STRUCTURE.  Why the usage is not documented somewhere or commented in the code is beyond me.

Note to anyone attempting to use this, it is VERY important you get folder NAMES and folder STRUCTURE "correct."

By "correct" I mean what "LLB Pre-Build CHM Build.vi" and "Build CHM.vi" are expecting:

• Pay attention to subfolders and folder names
• Pay attention to the name your .chm file name.
• A .chm file may already need to exist in the Help folder.  Manually create one if one doesn't exist.
• The Custom Device Wizard does not do some of this by default.
• Depending on your folding structure, you may need to change the contents of the "Build CHM.cfg" file.

Otherwise, the build will fail with the following error

Click the link below to visit the Application Builder support page. Use the following information as a reference:

Error 7 occurred at List Folder in Copy .LLB to NI VeriStand dir.vi->AB_Build.lvclass:User_PostBuild.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW: (Hex 0x7) File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
=========================
Nonexistent GPIB interface.

Good luck figuring this out.