To transfer the data via CAN, all four CAN conductors (H, L, +, ⊥) must be connected. The battery is unimportant here.
Key to CAN symbols::
H…………..CAN high
L……………CAN low
+……………+12 Volt
⊥……………Mass

A cable is not required for infrared transfer, only a 9V battery is required. The infrared interface is primarily intended for service purposes. It is recommended that this only be used for transferring functional data! An operating system download requires the Bootloader to be held motionless on the controller for several minutes (if this is not successful, transfers can then only be done using a cable)!

Position of the BL-NET on the controller for infrared transfers:

• Upper edge of the BL-NET lies at the lower edge of the UVR display.
• Display side edges are marked with →|DISPLAYPOSITION UVR1611|← on the BL-NET.

Data transfer of the operating system and functional data is always performed by the Bootloader using node 63 of the CAN network.
This special node number is used exclusively for these data transfers and must not be assigned to any device in the CAN network.
The device waiting for data transfer with the Bootloader automatically uses node number 63 for this period of time.

The device that is to exchange data with the Bootloader must be prepared for the data transfer. Once the device is ready for communication, the data transfer is started by pressing the START button on the BL-NET. When the START button is pressed, the green LED on the front of the BL-NET begins to flash rapidly. This indicates that the BL-NET is attempting to establish communication with the controller (no data is transferred at this point!). If the red LED lights up cyclically during an infrared transfer then the battery voltage has reached a critical level and the battery must be replaced as soon as possible.

Data down- and upload to and from the controller are started at the controller. The Bootloader has 7 memory positions for functional data. These can be written with data from the controller or functional data from the PC (using the Memory Manager program). The functional data upload differs only in the selection of the transfer direction (CONTR. ⇒ BOOTLD.) and is not described here in detail.

Controller view	Comment
	Select Data Administration in the main menu of the UVR1611 controller
	select Download Data: BOOTLD. ⇒ CONTR.
	Select the desired storage point for the functional data at the BL-NET Overwrite the controller functional data? Adopt the functional data as the factory setting? The controller switches to transfer mode
	The controller is ready for the data transfer. When the START button on the Bootloader is pressed, the green LED begins flashing rapidly and the data transfer starts. ABORT = Last option for cancelling the data transfer (press right key)
	The transfer is running Name of the functional data Progress display
	The functional data was successfully loaded into the controller.

The latest operating system versions can be downloaded from the homepage at www.ta.co.at. The Bootloader can only manage one operating system. This download contains the boot sector and operating system for the controller. The boot sector can be compared with the BIOS on a PC. The boot sector can also change for technical reasons. In this case, when updating an operating system the boot sector is loaded first and the download of the actual operating system is then automatically started after this. If the boot sector is the same then only the new operating system is loaded.

Controller view	Comment
	Select Data Administration in the main menu of the UVR1611 controller
	select Download Oper.System: BOOTLD. ⇒ REGLER\\
	The controller switches to transfer mode A cable connection should normally be used for transferring the operating system!
	The controller is ready for the data transfer. When the START button on the Bootloader is pressed, the green LED begins flashing rapidly and the data transfer starts. ABORT = Last option for cancelling the data transfer (press right key)
	The transfer is running. Progress display
	The data was successfully transferred to the controller
	Note: if the boot sector and operating system are updated the steps 4 to 6 are repeated without the START button being pressed again After the operating system update is finished, the start page is displayed on the controller.

With the BL-NET it is also possible to start the data transfer using any desired web browser. A precondition for this is that an Ethernet connection has already been set up (see chapter „Data Amin. (Data administration)”). Procedure:

1. Select “Data Admin.” (Data administration) in the BL-NET main menu
2. Select the node (the controller with which communication is to occur)
3. Select the transfer direction
4. Select the data (functional data or operating system)
5. Start the transfer

When the transfer is finished, an appropriate message is displayed in the browser („…successful“ or “ Error during data transfer on the CAN bus “).

If an error occurs when transferring the operating system, after an automatic restart the controller continues to wait as „NODE 63“ for the operating system data transfer to begin again („READY FOR DOWNLOAD“). As long as the operating system has not been fully loaded into the UVR1611, the controller has no other functionality. Pressing the START button on the Bootloader starts the data transfer again.
For this reason, an operating system update should not be carried out by remote maintenance for security reasons.

If an error occurs when downloading functional data, the controller automatically performs a total reset of the configuration. The „Node No.“, „Enable“ and „Autooperat.“ network settings are not changed. The data transfer of the functional data must be performed again.

WARNING! If a transfer fault occurs in a network with multiple devices, a data transfer to a different device must not be started until the fault is fixed!

In general, an operating system should only be updated when functions that are only contained in the newer operating system are required (Never change a running system!). Similar to PC BIOS updates, an operating system update always represents a certain small risk.