The default SDL file that comes with the SECS/GEM module is only coded for some of the more common SECS commands. When people run into the situation where the SDL file does not have the definition for a SECS message that they need to send, they create the definition themselves and add it to the SDL file on the gateway. What you will have to do is translate the XML definition you have into a JSON definition that can be added to the SDL file under the S14 section. This is one of those situations where you have to sit down with a text editor and build out the JSON one line at a time. The S14F9 definition is in the SDL file, so I would start with that as a reference.