|
Re: Power Cycle Persistence
If you haven't already moved away from the persistence, there are two small edits that make it work well for me.
First one is to open the NILVConfig.lvlib/Save Config File.vi. It is located in vi.lib/Utility/config.llb. This VI opens the ini file, writes the strings, and closes the file. If you wire a True constant to the Open so that it disables buffering, this solves the root of the issue. Whether this is a workaround or the best fix remains to be seen as I've also asked for others to look at this.
While looking at it, I saw something else that was a race condition and may also contribute. If you open the NT Server.vi. The initialization code on the left of the diagram reads the file to identify the persisted variables and their values. In parallel, the lower right code is started up to handle dirty variables that need to be propagated to other clients. This is also where the code updates the values of persisted variables to the ini file. While there shouldn't be any dirty variables for a bit, I'd rather make sure that we don't update the file before we know which variables are being persisted. The fix is to branch the error wire that connects the init code and the communications loop and connect it to the sequence around the DirtyList handler.
Please let me know if you make the changes, build, and still see the issue.
Greg McKaskle
|