transsecs_configuration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| transsecs_configuration [2020/09/29 12:15] – wikiadmin | transsecs_configuration [2026/08/27 11:14] (current) – tputman | ||
|---|---|---|---|
| Line 36: | Line 36: | ||
| transsecs.resetsendmessagetrigger=false | transsecs.resetsendmessagetrigger=false | ||
| </ | </ | ||
| + | |||
| + | ===Controlling Event Triggering Behavior in TransSECS PLC applications=== | ||
| + | |||
| + | transsecs.ceidedgetrigger=true | ||
| + | |||
| + | If this parameter is set to true events will be triggered only when the value changes from low to high (eg 0-1). Changing from high to low is ignored. | ||
| + | |||
| + | transsecs.resetceidtrigger=true | ||
| + | |||
| + | If this is true, after the event is triggered, the value in the PLC (or other device) will be reset to zero. | ||
| ===Advanced Parameters=== | ===Advanced Parameters=== | ||
| Line 54: | Line 64: | ||
| to the startup script will enable this option. | to the startup script will enable this option. | ||
| + | |||
| + | ===Alarm Anti-Rebound=== | ||
| + | |||
| + | Two parameters prevent multiple set/clear alarms in a short period of time. This will prevent multiple alarms being sent on, for example, a switch bobbling. Set the anti-rebound timeout to a value > 0 to enable this feature. | ||
| + | |||
| + | < | ||
| + | transsecs.alarmantirebounddeadband | ||
| + | </ | ||
| + | |||
| + | For example, to prevent alarms within 0.5 seconds of the initial indication add: | ||
| + | |||
| + | < | ||
| + | transsecs.alarmantirebounddeadband=500 | ||
| + | </ | ||
| + | |||
| + | Note that adding an ECID AlarmAntiRebound_DeadBand can be used instead of the system property. If this ECID exists the value of transsecs.alarmantirebounddeadband configured in the ErgoTechConfiguration.properties file will be ignored. | ||
| + | |||
| + | ===Passive Host/Active Tool=== | ||
| + | |||
| + | This change should only be made under the direction of tech support and requires an addon package that contains the new configuration. | ||
| + | |||
| + | < | ||
| + | # Switch Active/ | ||
| + | # All tools become active | ||
| + | transsecs.passivewrapperclassname=com.ergotech.transsecs.secs.HSMSToolActiveWrapper | ||
| + | # All hosts become passive (not required for a tool, but useful for testing). | ||
| + | transsecs.activewrapperclass=com.ergotech.transsecs.secs.HSMSHostPassiveWrapper | ||
| + | # The address of the host | ||
| + | transsecs.activehostname=192.168.56.1 | ||
| + | # Optional. How often to wait between attempts to connect to the host in seconds | ||
| + | # the default is 5 | ||
| + | transsecs.activeretryinterval=5 | ||
| + | </ | ||
| + | |||
| + | ===HTTPS and Self-Signed Certificates=== | ||
| + | |||
| + | When TransSECS connects to an HTTPS endpoint that uses a self-signed certificate, | ||
| + | |||
| + | See [[transsecs_trusting_self_signed_certificates|Trusting Self-Signed Certificates in TransSECS]] for instructions on exporting the server certificate, | ||
transsecs_configuration.1601396116.txt.gz · Last modified: by wikiadmin
