Flexotemp

1 Bus and Communication structure

• Profinet (via Ethernet) handles the cyclic uplink communication to PLC.
• TCP/IP (via Ethernet) handles the acyclic uplink data exchange to PVSS parameter panel, Flexotemp manager and Web interface.
• CAN Bus handles the locale communication between PCU and remote I/O´s.

File:Flexotemp System Overview.png

2 Modules

2.1 Process control units

• PCU 128 PNIO + PCU 48 PNIO are the name of the Process Control Units (PCU). Located in IPC switchboard, each PCU can handle up to 128 or 48 loops. The PCU is equipped with 2 different uplink communication ports:
  • Profinet – IO (PNIO)

Ethernet based RJ45 ports (Hub function) provide the link to PLC. All PLC based cyclic communication will be handled by this port´s. PNIO - IP address = TCP/IP address + 10, address response a ping

• TCP / IP

1 Ethernet RJ 45 port is independent in hardware setup from PNIO interface, all acyclic TCP + UDP Ethernet communication for configuration, parameter and state information will be handled by this port. Ethernet address of 1^st device = 10.XX.YY.232, address response a ping.

2.2 CAN Bus communication modules

The Can Bus is provided on at the backplane connector on the right hand side of the PCU. Extension to Field CAN Bus only by CANBE or BE (-F) modules. The CAN Bus links all the remotes to the PCU.
Different type of modules handles the CAN Bus communication:

• CANBE, CAN Bus interface module with repeater function.
  Is in use after the PCU to handle the maximum of 2 independent CAN Bus segments. Connection of Bus by CAN Bus SUB-D connectors. 2 different types:
  • with internal CAN Bus termination resistor
  • without internal CAN Bus termination resistor
• BE, CAN Bus interface to extend the CAN Bus from the backplane connector to Sub-D
  Is in use after the PCU to handle 1 CAN Bus segment. Use 1 CAN Bus interface (SUB-D) on frontside. This module have no own address, is not an active CAN Bus member and will not be shown in the Flexotemp Manager configuration.
• BE-F, CAN Bus interface to extend the CAN Bus from the backplane connector to ribbon cable
  Is in use after several Peripheral I/O modules to extend the CAN Bus by ribbon cable to HPC modules. This module have no own address, is not an active CAN Bus member and will not be shown in the Flexotemp Manager configuration.
• CANBC, CAN Bus interface I/O header module

connection by 1 CAN Bus interface (SUB-D) to CAN network and extend the CAN Bus by backplane connector to I/O´s. This is the 1^st module at remote, behind this module the peripheral I/O modules are lined up.

2.3 CAN Bus I/O modules

Input / Output modules are lined up after a PCU or CANBC module, linked by the backplane connector. Each module get a own unique CAN Bus address Template:Notice bms Different type of modules are avalible:

• DO 08 R, output module with 8 dry relay contacts
• DO 16, output module with 16 digital outputs (24VDC)
• DIO 16 CI, module with 16 digital channels each may be configured as DI or DO (24VDC) equipped with current measurement interface
• DIO 16 CI SPL, module with 16 digital channel éach may be configured as DI or DO (24VDC) equipped with current measurement interface and smart power limitation
• AOI 04, analog output module with 4 channels outputs (0..10VDC / 4..20mA)
• HPC 24, power output module with 24 outputs (max 7A / channel, half wave control technology) control the die bolt heaters.
• PT 16, input module, equipped with 16pcs of 3-wire PT 100 inputs
• TC 12, input module, equipped with 12 thermocouples inputs, type (K or J) can be adjusted
• VC02 / VC 04, input – output module, valve positioning controller modules with 2 or 4 channels

3 CAN Bus

3.1 CAN Bus, basics

The PCU use the CAN Bus for communication with remotes. Different bus segments are in use:

• PCU <> CANBE - closed hardware bus segment
  • no hardware setting required
• CANBE <> CANBC - closed hardware bus segment
  • termination at CANBE (depending which module is in use, with or without internal bus termination resistor)
  • address settings at all CANBC
  • termination at last CANBC
• CANBC <> I/O modules - closed hardware bus segment
  • no hardware setting required except at HPC
  • set termination jumper alt last HPC

3.2 CAN Bus, passive hardware

• CAN Bus cable type is a 2 x 0,64mm², with flexible wires. The overall length of 1 CAN Bus segment should not exceed 250m. The cable is used in combination with the 90° CAN Bus connectors manufacturer "EPIC" (=Lapp) with and without diagnostic connector (diagnostic connector only at both ends of the bus segment)
  The connection points for field CAN Bus are located at different modules:

• CANBE (repeater module, located right side of the PCU) links the CAN Bus to field
  2 can bus segments can be handled, each segment support the maximum cable length.
• BE (Bus connection module, extend the internal CAN Bus of the PCU to a sub –D plug)
  1 CAN bus segment can be connected by SUB-D.
• CANBC (uplink module, in field)
  here the field Can bus meet the remote I/O´s.

• CAN Bus special cable is a ribbon type cable, it is used to extend the internal backplane I/O module CAN Bus by using the BE-F module to the HPC modules.
  The BE-F is the interface module from the backplan bus to ribbon cable.
• CAN Bus Connection
  will be done by 90° connectors with screw terminals, on the CAN Bus cable sleeves need to be used
  
• CAN Bus speed
  default speed setting is 250k, no change required.
  
• CAN Bus addressing
  each device (excluding BE or BE-F) use a own CAN bus address for communication with PCU, this address is shown in the Flexotemp Manager project.
  The CAN Bus adresses need to be set at the CANBC modules only, all other modules receive the address at the bus initialisation procedure.

Template:Notice bmsTemplate:Notice bmsTemplate:Notice bms

• Rules for potential equalization and electrical noise discharging: (CAN bus will treated similar as other Fieldbus systems)

• A single wire, 16mm² ye-gr (multi conductor - flexible type) need to be routed with the bus cable to connect the 2 different bus locations (= independent shipping units, also in switchboard room).
• If multiple bus systems are connected parallel only 1 wire is required.

• Bus termination is required at both ends of the bus segment at the CAN Bus cable. Details see: CAN_Bus in field setup
• Bus termination is required the last HPC module.

• File:Flexotemp Doku Can Bus Plug 1.jpg
• File:Flexotemp Doku Can Bus Plug 2.jpg
• File:Flexotemp Doku Can Bus Plug 3.jpg

4 Communication

4.1 PCU / PLC / PVSS

TCP/IP + PNIO communication use one common Ethernet based uplink cable.
(scheme see "Hardware – bus- and communication structure")

• Cyclic Communication for the "generic controller " part
  • PCU and PLC communication use PNIO protocol
  • PLC and PVSS communication use TCP/IP standard BMS link procedure
    

File:Flexotemp PVSS Controller Parameters.png

• Acyclic Communication for the "specific controller" part
  PVSS and each PCU communicates on request directly by the TCP/IP protocol. After a request from PVSS has been sent to the PCU, the PCU response with a data stream which content the parameters of the zone.

4.2 Flexotemp Manager

• Basic address assignment to PCU will be handled by UDP protocol, no access through firewall possible, works only within the same network
  (only needed for 1st IP adress assignemet) see also: Precheck / Checkup / Commissioning - PCU Ethernet IP address_assignment
• Standard communication to the PCU is handled by TCP/IP protocol, port 5000

• for standard comissioning procedure use Flexotemp Manager at RMT station by Remote Desktop

4.3 Webinterface of PCU

Each PCU have his own internal webserver and webinterface. This Interface should be used only for maintanance issues only.
The Webserver response TCP/IP adress request in the browser. Template:Notice bms

File:Flexotemp Webinterface.png

5 Precheck / Checkup / Commissioning

5.1 Precheck

Follow this steps 1st: Precheck of positioning valve

5.1.1 CAN Bus setup

5.1.1.1 CAN Bus in field setup

• Option with internal termination resistor in CANBE module
  (no Label on fornt side of module)
  • Disconnect CAN bus connectors from all CAN bus members in the bus segment
  • Set the termination switch at all CAN bus connectors to "off" position
  • Measure resistance at pin 2/7 at end of the bus (opposite end to CANBE end), resistance mus be &infinitely;
  • Measure resistance at pin 2 > GND at end of the bus (opposite end to CANBE end), resistance mus be &infinitely;
  • Measure resistance at pin 7 > GND at end of the bus (opposite end to CANBE end), resistance mus be &infinitely;
  • Turn the termination switch at this end to "ON" position, measure resistance at pin 2/7 (= 120 Ohm)
  • Measure resistance at pin 2/7 at begin of the bus, resistance at pin 2/7 must be 120Ohm
  • reconnect can bus plugs to all stations
    

• Option without internal termination resistor in CANBE module
  (label on fornt side of module "Without terminating resistors")
  • Disconnect CAN bus connectors from all CAN bus members in the bus segment
  • set the termination switch at all CAN bus connectors to "off" position
  • Measure resistance at pin 2/7 at end of the bus (opposite end to CANBE end), resistance mus be &infinitely;
  • Measure resistance at pin 2 > GND at end of the bus (opposite end to CANBE end), resistance mus be &infinitely;
  • Measure resistance at pin 7 > GND at end of the bus (opposite end to CANBE end), resistance mus be &infinitely;
  • Turn the termination switch at this end to "ON" position, measure resistance at pin 2/7 (= 120 Ohm)
  • Measure resistance at pin 2/7 at begin of the bus, resistance at pin 2/7 must be 120Ohm
  • Turn the termination switch at this end to "ON" position, measure resistance at pin 2/7 (= 60 Ohm)
  • reconnect can bus plugs to all stationsTemplate:Notice bms

5.1.1.2 CAN Bus devices setup

• Set the termination jumper at the last HPC module to "TERM" position

5.1.1.3 CAN Bus address assignment:

• set CAN Bus addresses at CANBC modules in field according Flexotemp Manager project (should be similar E-drawings) by the 2 ID switches, the switches setting is in HEX format and is also shown in the Flexotemp Manager project.
• The default adress step between the header modules (CANBC) may be 8 or 16.
• After changing the address setting at CANBC a reconfiguration and new adress assignement to the submodules is requred, trigger it by pressing the CFG button for 5 sec.

5.2 PCU Ethernet IP address assignment

• use a 1:1 ethernet cable and connect the Template:KomNamRMT station directly to the PCU which you want to set the TCP/IP parameter
  

At lines with decentral electric you probably find the PCU's somewhere in the cabinets outside on the line. (eg. Die cabinet, TDO +TT1, MDO cabinet) There you just take a direct connection to the TCP/IP port of the PCU

• make sure you know:
  • PCU Name
  • TCP/IP address
  • Subnet mask
    

This information you can find in the Hardware configuration in the Simatic Manager

• Start Flexotemp Manager
• No Flexotemp Manager project required (you have no network access)
• start Ethernet scan

File:Flexotemp Manager empty Start Ethernet Scan.png

• check result of scan, you must see the connected PCU, if the scan result not successful, reboot PCU and try again
  

File:Flexotemp Manager Ethernet Scan Results.png

• If there is still no result try to reset the PCU with following steps

Flexotemp IP Adress Backdoor If you got problems in connecting to a Flexotemp PCU or it can't be recognized during the "Ethernet Scan", there is a trick to set it on a default IP. The two coding switches on the PCU must be set to "F" with which the default IP Adress 192.168.0.220 is set to the PCU. Then if you are in the same IP range with your notebook you should be able to connect and configure the PCU. After you have set the correct IP Adress via the Flexotemp Manager and downloaded it to the PCU, simply put the coding switches back to "0" and the communication takes place again over the "normal" configured IP range.

• • @PCU, use MSB and LSB to maintain a reset to factory settings:
    • set to MSB to F
    • set to LSB to E
    • wait 5 sec until LED´s are flashing
    • change back adress switch to origin

• enter "Change settings" button and modify required values
  • Device Name
  • Base IP address
  • Subnet mask

Template:Notice bms

• Change the Base IP Adress to the IP Adress of the Controller

File:Flexotemp Manager Ethernet Node Settings.png

5.3 PCU time server settings

File:PCU-FM-time server setting.jpg

5.4 Project download preparations

Overall CAN bus address scan, requirements:

• CAN Bus precheck finished
• all modules are supplied with control voltage

Different ways how to do are possible:

• @Flexotemp Manager, use menu command:
  • select target PCU
  • right mouse button
  • select item "Start address scan"

5.5 Project download

• Open Flexotemp Manager project from: Template:PathUncKomdata\temperatures\PSG\Template:KomNam.xml
  
• Make sure that Flexotemp Manager TCPIP communication to all modules is enabled

File:Flexotemp Firmware Update 1.png

• select PCU which you like to configure, select Parameters + project setup + PROFINET IO

File:Flexotemp Manager download complete Project.png

• store data to EEPROM

File:Flexotemp Manager date to EEPROM complete Project.png

5.6 Firmware update

Template:Notice bms

• Check for the actual Firmware on....
  • \\brueckner.de\dept\bms_ee_ext\PUBLIC\Firmware\PSG\Flexotemp
    
  • Retrieve firmware files from SVN KOM\data\temperatures\PSG\HEX\
    
  • or for older lines from VSS(Template:PathUncKomdata\temperatures\PSG\HEX)

Template:Notice bms For example...

PCU  128 10 46 19 A
    |   |  |  |  |z
    |   |  |  |  |I_____ Index
    |   |  |  |yy|           
    |   |  |  |  I______ year (02)
    |   |  |xx|  
    |   |  |I________ week (47)
    |   |kk|
    |   | I__________ Identifier for Hex file (10 = PROFINET IO / Standard Controller)
    |nnn|
    |  I____________ Number of Zones
 ABC|
   I______________ Controller Type

• Open Flexotemp Manager project from: Template:PathUncKomdata\temperatures\PSG\Template:KomNam.xml
  
• Make sure that Flexotemp Manager TCPIP communication to all modules is enabled

File:Flexotemp Firmware Update 1.png

• check firmware versions for all the modules in the project:

  File:Flexotemp Firmware Update 2.png

File:Flexotemp Firmware Update 3.png

• Check result, select components where firmware upgrade is required and start firmware update of selected components.
  

File:Flexotemp Firmware Update 4.png

• Confirm update:
  

File:Flexotemp Firmware Update 5.png

• Firmware update in progress:
  

File:Flexotemp Firmware Update 6.png

• After finish confirm with ok button, the automatic rescan should show now no more differences in firmware versions
  

File:Flexotemp Firmware Update 7.png

Template:Notice bms

When updating PCU firmware to Version 3616 an update of the boot-monitor is also required: Boot Monitor Update

6 Specific controller in PVSS

• PLC link and function call addresses information:
  

File:Flexotemp PVSS Controller Parameters.png

• Parameter view definition:

Favorites and from the view excluded parameters need to be defined and can be modified in the config file for PVSS (//Kom/config/config)

File:Flexotemp PVSS Parameters 2.png

• All controller specific parameter without the excluded parameters are shown here:
  

File:Flexotemp PVSS Parameters 3.png

• All controller specific parameter which are defined as favorites in the config file will be displayed here:

File:Flexotemp PVSS Parameters 4.png

• Differences between the project file and the online value of the controller are shown in yellow color:

File:Flexotemp PVSS Parameters 5.png

• After a parameter has been modified, this modification need to be stored in the project file with the

File:Flexotemp PVSS Parameters 6.png

button

• Several massages can be returned from the PVSS:
  • Differences between controller and file are found:

File:Flexotemp PVSS Parameters 7.png

• Store to parameter was successful:

File:Flexotemp PVSS Parameters 8.png

• Store to parameter was not possible: (File opened by another user by Flexotemp Manager)

File:Flexotemp PVSS Parameters 9.png

7 Flexotemp Manager settings and handling guidelines

7.1 General program settings

• Install only that program version which is released

Template:Notice bms

• Program settings
  • Deactivate automatic updates
  • Set "Safe project automatically in a interval of 5 min"
  • Switch to English language: Extras > Options > Language

7.2 Handling advices at site

• for standard comissioning procedure use Flexotemp Manager at RMT station by Remote Desktop
• Use Flexotemp Manager only for hardware checkup. In case the project is opened by the Flexotemp Manager, the file is locked and no writing access from PVSS possible.
• Close Flexotemp Manager project anytime you don’t need it

8 Valve positioning controller

8.1 Know how about different valve types and functions

make sure you are familiar with the function of each valve, check flow scheme
2 types and 2 different function variations are available:

8.1.1 Two way valve / straight way

File:Flexotemp 2Way Valve Symbol.png

File:Flexotemp 2Way Valve.png

2 Way Valve

Module output and potentiometer connections are straight, movement functions are direct (retracted = open, extended = close)

• Connections at VC modules:

O… = open

C… = close

• (module output / valve movement assignment)
  

P+… = 100%

P-… = 0%

8.1.1.1 Heating function

• controller output (y) = 0%
  • Poti measured voltage at module = 0…0,5 V
  • Poti actual value in Flexotemp Manager = low value
  • position of valve push rod = fully extend
  • valve gate closed
• controller output (y) = 100%
  • Poti measured voltage at module = 1,5…2 V
  • Poti actual value Flexotemp Manager = high value
  • position of valve push rod = fully retracted
  • valve gate fully opened

8.1.1.2 Cooling function

• controller output (y) = 0%
  • Poti measured voltage at module = 0…0,5 V
  • Poti actual value Flexotemp Manager = low value
  • position of valve push rod = fully extend
  • valve gate closed
• controller output (y) = - 100%
  • Poti measured voltage at module = 1,5…2 V
  • Poti actual value Flexotemp Manager = high value
  • position of valve push rod = fully retracted
  • valve gate fully opened

8.1.2 Three way valve

File:Flexotemp 3Way Valve Symbol.png

File:Flexotemp 3Way Valve.png

3 Way Valve

module output and potentiometer connections are cross over movement functions are inverse (extended = open, retracted = close)

• connections at VC modules:

O… = close

C… = open

(module output / valve movement assignment)
P…+ = 0%

P…- = 100%

(y output / position assignment)

8.1.2.1 Heating function

• controller output (y) = 0%
  • Poti measured voltage at module = 0…0,5 V
  • Poti actual value Flexotemp Manager = low value
  • position of valve push rod = fully retracted
  • Valve gate AB-B – open
  • Valve gate AB-A - closed
• controller output (y) = 100%
  • Poti measured voltage at module = 1,5…2 V
  • Poti actual value Flexotemp Manager = high value
  • position of valve push rod = fully extend
  • Valve gate AB-B – closed
  • Valve gate AB-A – open

8.1.2.2 Cooling function

• controller output (y) = 0%
  • Poti measured voltage at module = 0…0,5 V
  • Poti actual value Flexotemp Manager = low value
  • position of valve push rod = fully retracted
  • Valve gate AB-B – open
  • Valve gate AB-A - closed
• controller output (y) = 100%
  • Poti measured voltage at module = 1,5…2 V
  • Poti actual value Flexotemp Manager = high value
  • position of valve push rod = fully extend
  • Valve gate AB-B – closed
  • Valve gate AB-A – open

8.2 Technical data of valve positioning unites

Manufacturer	Type	Push force	Resistance of Motor	Resistance of Poti	Speed@50Hz	Electric load
		[kN]	[Ohm]	[Ohm]	[mm/sec]	[VA]
RTK	5106-60	15	~ 300	1000	0,9	180
RTK	3112-32	2,4	~ 2400	1000	0,26	11
RTK	5112-32	3	~ 2400	1000	0,26	11
ARI	Premio	2,2	~ 1600	1000	0,38	18
ARI	Paco0,85D	0,85	~ 3200	1000	0,11	4,1

8.3 Precheck of positioning valve

1. At the switchboard, before power on control voltage:
   Make sure VC02/04 module motor 230VAC control voltage supply fuse is off
2. At the valves:
   1. Open cover of all valves and remove Manuals
   2. Move valves with manual hand wheel away from a limit end position
3. At the VC02/VC04 position controller:
   1. Disconnect power and position indicator plug at module
   2. Check resistance of all motors between O to N and C to N. Details for resistance see here:
      Technical data of valve positioning unites
   3. Check resistance of all position indicators
   4. Reconnect power and signal plugs at modules
   5. Power on control voltage fuse

Template:Notice bms

8.4 Comissioning of positioning valve

• Finish Precheck of positioning valve
• Check module parameter settings in Project view of Flexotemp Manager:

File:Flexotemp Commissioning VC 1.png

• Activate 1^st channel in Flexotemp Manager project and write parameter to module:
  

File:Flexotemp Commissioning VC 2.png

File:Flexotemp Commissioning VC 3.png

• after writing to module the red mark in the module went away:
  

File:Flexotemp Commissioning VC 4.png

• Change to status view, set PCU online and check setting in module:
  

File:Flexotemp Commissioning VC 5.png

File:Flexotemp Commissioning VC 6.png

• change to tune and execute the tune process of the enabled valve

File:Flexotemp Commissioning VC 7.png

• check status of tune process in status view:
  

File:Flexotemp Commissioning VC 8.png

File:Flexotemp Commissioning VC 9.png

File:Flexotemp Commissioning VC 10.png

• check result of tune
  • MP value range is from low (left) to high (right)
    the default value (no tune was running) is XXXX MP / XXXX MP

File:Flexotemp Commissioning VC 11.png

• No tune error should come up

Enter PVSS, start Zone , set controller to manual mode and send manual controller output setpoint to valve

9 Practice + trouble shooting

9.1 Exchange of I/O module´s

• Power off affected stations including CAN Bus linking module (CANBC)
• Exchange module
• Power on modules
• Start local bus scan and module address by pressing the CFG button
• Open Flexotemp Manager
• check firmware version
• in case firmware is older version update module (Firmware update)
• Download module configuration to module

File:Flexotemp Download Module Parameters.png

• For VC02 / VC 04 only:
  press "Tune" button at module and check that tune process will be finished without an error

9.2 Set PCU to defined parameters

Set LSB + MSB to position FF

• PCU reboot automatically
• OK LED shows a continuous double flash

now a defined has been reached, following items are special:

• TCP/IP address is fix set to 192.168.0.220
• internally the project will not be startet
• now a new project can be downloaded

after finishing download following steps:

• set LSB + MSB back to original setting (00=default)
• PCU reboot automatically
• project start automatic

9.3 No communication by Ethernet from service network to PCU, (no webinterface, no Flexotemp Manager access)

check configuration of Ethernet interface of controller:

• Connect PG to plant network
• Start Ethernet scan (UDP protocol)
• Check settings of port 1, 2, 3:

File:Flexotemp Interface Settings.png

• Contact EECIBN@brueckner.com, request for firewall check for open ports for 1, 2, 3 on TCP as shown in the Ethernet setting

9.4 No communication by Ethernet from any network to PCU, (no webinterface, no Flexotemp Manager access, no scan result)

When the TCP/IP uplink is routed over the PCU onboard PNIO interface, connect PCU TCP/IP port (-X2) directly to plant network.

Background: in special PNIO interface panic situations, the PNIO interface may not forward the TCP/IP protocol

If the PCU is still not available with the flexotemp, you can try a communication without the CANBUS.
A failure in the CANBUS communication of the PCU or any other partner, can link to a miscommunication and the PCU can't be reached by the ProfiNet.

If the PCU (without CANBE Modul) can be reached by ping and the Flexotempmanager, you can reset the CANBus settings by pressing the "Config" button on each module in the loop for 5 seconds ( Reboot ).
File:PSG CANBC.jpg

9.5 Communication to remote device missing, or failure message

After finishing the firmware update or project download device shown in Flexotemp Manager error messages:

• as missing
• offline
• wrong firmware version
• wrong module type

Following steps to rebuild and show real state in Flexotemp Manager:

• run address scan from Flexotemp Manager (Project view) select header station (CANBC) of affected module and run address scan. A 2nd way to run the address scan is to trigger the process locally at CANBC by pressing the "CFG" button.

  File:Flexotemp IO Start Address scan.png

• interface test, check the communication from PCU to affected module
  • select Interface test

    File:Flexotemp IO interface test select.png

  • run interface test, check state + meessage in field "counter / status

    File:Flexotemp IO interface test run ok.png

9.6 Firmware update of remote I/O module failed

After running a firmware update of an remote I/O module from Flexotemp Manager main window an error occurred and this module will not respond any more, follow the this steps:

select assigned CANBC module of the affected module direct in the project and start "start address scan"

• check the response of affected I/O module: mark affected module in project view and perform "interface test"
• after get a successful response of affected I/O module select at the module the "Firmware update"

9.7 HPC 24 internal cooling fan control and heatsink alarm handling

• Internal heatsink cooling fan:

The internal cooling fan of the HPC 24 module can run with 3 different speed´s. The fan starts when the heatsink temperature rises above 40°C with speed stage 1. When heatsink tempereature rises higter 70°C the fan run with 100% speed. Between this value the speed will be controlled.

• Internal heatsink temperature observation:

The heatsink temperature will be observed, the 1st alert can be set manually in the project, default value = 60°. A second, maximum alert is set in the internal software to 90°C, this value can not be modified. After reaching this value the module stops.