darwins, on 01 March 2023 - 09:19 AM, said:
So with a "sprung" safety valve, the action is gradual rather than sudden--makes sense. So for the purposes of defining the action of the safeties, the code would be something like this:
Comment (** Example code for a sprung safety valve. **) ORTSNumSafetyValves ( 2 ORTSSafetyValve ( ORTSSafetyValveType ( Sprung ) ORTSSafetyValveTriggerPressure ( 200psi ) ORTSSafetyValveMaxSteamUsage ( x lb/hr ) ) ORTSSafetyValve ( ORTSSafetyValveType ( Sprung ) ORTSSafetyValveTriggerPressure ( 200psi ) ORTSSafetyValveMaxSteamUsage ( x lb/hr ) ) )
Comment (** Example code for a pop safety valve. **) ORTSNumSafetyValves ( 2 ORTSSafetyValve ( ORTSSafetyValveType ( Pop ) ORTSSafetyValveTriggerPressure ( 200psi ) ORTSSafetyValveMaxSteamUsage ( x lb/hr ) ) ORTSSafetyValve ( ORTSSafetyValveType ( Pop ) ORTSSafetyValveTriggerPressure ( 206psi ) ORTSSafetyValveMaxSteamUsage ( x lb/hr ) ) )
Also, in terms of the sounds associated with sprung safety valves, it would mean a new .sms variable trigger type would need to be defined...