Set this to something between 0 and 19 (for staggering different broadcasts over typical 1 second interval). Use it to initialize data publication timer counter (which is currently not initialized at all).
that could be a good idea, but in lockdown we assume the application POST is passed, otherwise we cannot do the manufacturing setup. so technically it already checked in application POST.
This is for stripping the output file. The I am assuming that we are running this script on the build server, which may not give us the right path. This is why the script is also asking for the "device path"
The output file looks like this: <HASH> <current path of conf file in server>
Just pulled your latest branches and get the following warnings when I build: Description Resource Path Location Type #179-D function "dequeue" was declared but never referenced NVDataMgmt.c /DG/FWCommon line 2484 C/C++ Problem #179-D function "setFillInfoToRTCRAM" was declared but never referenced ModeFill.c /DG/App/Modes line 997 C/C++ Problem #552-D variable "chemDisinfectFlushUIState" was set but never used ModeChemicalDisinfectFlush.c /DG/App/Modes line 115 C/C++ Problem #552-D variable "rsrvrFillStableTimeCounter" was set but never used ModeChemicalDisinfectFlush.c /DG/App/Modes line 127 C/C++ Problem #552-D variable "R1ChemDisinfectVol" was set but never used ModeChemicalDisinfect.c /DG/App/Modes line 171 C/C++ Problem #552-D variable "R2ChemDisinfectVol" was set but never used ModeChemicalDisinfect.c /DG/App/Modes line 172 C/C++ Problem