Troubleshooting

For communication via Ethernet, the Bootloader must be connected to the CAN bus or supplied with power via a 12V power adaptor (special accessory CAN-NT).

Make sure that the Bootloader is connected via Ethernet to the PC or LAN network. An existing Ethernet connection is indicated by a green LED in the oval window on the lower side of the Bootloader. A crossed network cable must be used for direct connection with a PC.

With a direct Ethernet connection between BL-NET and a PC, the PC must be assigned a fixed IP address. If the PC has a WLAN (wireless network), it must be ensured that the network related part of the IP address differs from the WLAN part.

Check the Ethernet configuration of the BL-NET (see chapter „Connecting the BLNET to a LAN network“) and note the IP address and TA port of the Bootloader.

Make sure that the same IP address and TA port of the Bootloader are set in the Winsol setup.

Run „Test IP“ again. Note the displayed port status.

Make sure that the Bootloader is connected via USB to the PC.

In the Windows Device Manager), check that the USB driver was correctly installed
(Device Manager → Ports (COM und LPT)). In this case the virtual COM port appears in the list as “USB Serial Port“.

Run „Test Com“ again. Note the displayed status of the COM port assigned to the USB driver.

If no controller is connected to the BL-NET then a 9V battery must be used to provide power for the device.

If the Bootloader is connected to at least one device, check the data transfer from the controller to the Bootloader (see next point)..

Make sure that the Bootloader is connected to the controller via the DL data cable.

Check the wiring of the data cable and observe the correct polarity.

With the UVR1611 data output must be activated if logging over the data link (DL-bus) is to take place (output 14 defined as „data line“).

Ensure that, the BL-NET is configured for the corresponding data logging process (DL bus or CAN bus (see Winsol chapter).

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 (DL bus) or the CAN bus from each of the controllers one after another. It is important to disconnect the cable directly at the controller and not at the data input of the BL-NET, otherwise you may get ambiguous results!

To isolate data transfer problems with a single cable, test the link using a short cable (< 1 metre).

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!

When logging from an UVR1611 or UVR61-3, the timestamp is generated by the controller 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 an hour, and updates the timestamp internally. If the time in the controller is changed, the Bootloader must therefore be briefly powered off for a few seconds (remove DL) so that it immediately synchronises after a restart.

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.

Under certain circumstances, Windows 7 and Windows Vista, create the files in a „virtual program path“. In Windows Explorer, the searched for files are reached by pressing the button „Compatibility files“:

The files are then actually stored in the following path: C:\Users\USERNAME\AppData\Local\VirtualStore\Programs\Technische Alternative\ Winsol\…