5 June 2020 CasTemp Wireless including CasTemp Superheat Page 18
9.4 Level 2 communication
CasTemp Superheat sends information to the plant but also requires information from the plant for the
functionality.
The following will be covered:
• Communication Protocols for output to plant
• Communication Protocols for input to CasTemp Superheat
• Telegram requirements
• Timings
9.4.1 Communication Protocols for output to plant
The following communication protocols can be used to send data from the CasTemp Wireless
instrument to the plant:
• Serial
• TCP IP (Server and Client)
• Profibus
• Ethernet IP
9.4.2 Communication Protocols for input to CasTemp Superheat
The following communication protocols can be used to receive data from the plant:
• TCP IP (Server and Client)
• Profibus
• Ethernet IP
Check the box ‘Use for inputs’ to enable this functionality in section 6.2.
Serial is the only communication that does NOT accept input from the plant.
9.4.3 Telegram Requirements
There are 5 telegrams that the CasTemp Superheat requires from the plant, these telegrams will be
explained and their format will be shown:
Identity assigned to the steel being cast through the tundish, normally
upon ladle opening and normally ignoring any time lag between the ladle
shroud and tundish outlet. Used to reset the liquidus value.
Plant time or PLC time reference, however the plant want to define this
reference, to enable time synchronization between the CasTemp
Superheat system and plant
A static or preferably dynamic time estimate of when the ladle will empty,
which is used as the last superheat prediction point.
Plant defined limiting superheat above current liquidus. Upon Superheat
reaching this value, plants would expect the caster operator to be taking
appropriate action.
A digital signal which is either tundish in casting position or tundish in
casting position and CasTemp connected and operational.
Tundish not in position and CasTemp connected represents preheat
“Ready to Cast” is used to define which instrument is in live casting and
therefore where CasTip liquidus information sent to both will be used