A number of parameters can be controlled by the ErgoTechConfiguration.properties file. A sample, file is installed with the application. it is also used for every TransSECS deployment to be able to tweak runtime behavior.

# needed if trigger source is reset automatically back to boolean false (PLC)
transsecs.resetceidtrigger=false
#message handling threading model, 0=all messages on same thread, 1=Push the processing of each message onto a new thread, one thread will be used for primaries and many for responses.
transsecs.threadingmodel=1
# voyeur option
#transsecs.passthrough=true
# set debug level higher for more verbose session manager logging
sessionmanager.debuglevel=0
# id type defaults to 54 if this options is excluded (options 50, 51, 52, 54, etc.)  This is used by the tool to set all the id types (ceid, vid, dataid, alid, rptid).
transsecs.idtype=54
# following four used for GEM host applications (id type options 50, 51, 52, 54, etc.) 
# gemhost in the name of the tool defined in the TransSECS project.  
gemhost.ceidsecsformat=54
gemhost.vidsecsformat=52
gemhost.dataidsecsformat=52
gemhost.alidsecsformat=52
gemhost.rptidsecsformat=54
# there can be multiple entries if multiple hosts are deployed in the same application
anothergemhost.ceidsecsformat=52
anothergemhost.vidsecsformat=52
anothergemhost.dataidsecsformat=52
anothergemhost.alidsecsformat=52
anothergemhost.rptidsecsformat=52
######
# activate simple S7Fx (x=3,5,17,19) file based recipe handling (default is 0, no recipe handling, set to 1 to enable recipe management)
transsecs.recipemanager=0
#used only if recipemanager is set to true
transsecs.recipemanager.basedir=./
transsecs.recipemanager.extension=rcp
#######
# needed for MQTT so that send message trigger tag is reset automatically
transsecs.resetsendmessagetrigger=false

In general these parameters should not be set unless suggested by ErgoTech tech support.

secs.maxmessagelength

This limits the maximum size of a SECS message. Certain SECS/GEM implementations send valid, but inaccurate length bytes in HSMS messages. This avoids “OutOfMemory” errors if the size provided is extremely large.

The value is provided in kb. Messages are normally small, a few kb. Setting this value to 100 should avoid any issues with normal, or abnormal operation. For example, adding the line:

secs.maxmessagelength=100

to the configuration file, or adding:

-Dsecs.maxmessagelength=100

to the startup script will enable this option.