I just ran into a small snag on the EPIC while writing files. I noticed that a particular file was not updating, it’s something that should be over-written at some interval, but it wasn’t doing so.
I tracked this down, and found that I was receiving an undocumented error code on the ‘OpenOutgoingCommunication’ command - error -408. I’m going to go out on a limb here, and guess that this is some sort of permissions error, because of my further findings:
Through testing and trial-and-error, I found that if I deleted the file using groov Manage, the PAC program is now able to write it, and rewrite it as expected. It’s only going to throw that error if the file was written to the controller by dropping it into the unsecured folder using groov Manage. I’m guessing that groov Manage sets the linux permissions in some way that the PAC program is not allowed to now overwrite the file.
So, what I need to be sure of (at least for now) is that my techs aren’t sending that particular file through groov Manage. Trouble I have is that this file is used to load setpoints on the machine for initial commissioning, so they have to load it once, use it, then remember to delete it so it can be rewritten from then on. A bit of a chore.