
21
4.
If no controller is connected to the BL-NET then a 9V battery must be used to provide
power for the device.
5.
If the bootloader is connected to at least one device, check the data transfer from the
controller to the bootloader (
see next point
).
The data transfer from the controller to the bootloader is not working.
(No measurements are shown in the
Winsol
display.)
1.
Make sure that the bootloader is connected to the controller via the DL data cable.
2.
Check the wiring of the data cable and observe the correct polarity.
3.
With a UVR1611, the data output must be activated (define output 14 as a data line).
4.
If two controllers are to be acquired with the bootloader, check the data connection with
each of them individually in order to isolate the problem. To do this, remove the data
cable from each of the controllers one after another. It is important to disconnect the
data cable directly at the controller and not at the data input of the BL-NET, otherwise
you may get ambiguous results!
4.1.
If the data transfer works with each of the two controllers individually, then the
problem is caused by crosstalk errors between the two data cables. In this case
the cables must be laid separately or at least one cable must be shielded.
5.
To isolate data transfer problems with a single cable, test the link using a short cable (<
1 metre).
5.1.
If the data transfer works with the short cable then the problem is caused by inter-
ference from an external source in the long cable. In this case, the cable must be
laid using a different path or a shielded cable must be used.
6.
If problems persist after all the above points have been checked then please consult
your dealer or directly contact the manufacturer. The problem can only be solved with
an
exact fault description!
The data is recorded with the wrong timestamp (date, time).
1.
When logging from an UVR1611 or UVR61-3, the timestamp is generated by the con-
troller and, in this case, the time information at the controller must be corrected.
Note
: To ensure a high time resolution, the bootloader synchronises its clock with the
controller during commissioning, or once a day, and updates the timestamp internally.
If the time in the controller is changed, the bootloader must therefore be briefly pow-
ered off for a few seconds (remove DL) so that it immediately synchronises after a re-
start.
2.
When logging data from controllers without internal clocks, the time on the PC, or the
time at which the bootloader was disconnected from the controller, is assigned to the
recorded data.