Ethernet connection: The BL-NET is not recognised during "Test" of Winsol.
1. For communication over Ethernet, the Bootloader must be connected to the CAN bus or supplied with a 12V power pack (CAN-NT) via the CAN interface.
2. Ensure that the Bootloader is connected via Ethernet with the PC or LAN network. An existing connection via Ethernet is signalled via a green LED in the oval window on the bottom side of the Bootloader. For a direct connection with the PC a crossed network cable must be used.
3. For a direct connection of BL-NET and PC via Ethernet, a fixed IP address must be allocated to the PC. 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.
4. Check the Ethernet configuration of the BL-NET (see manual for the BL-NET) and note the IP address and TA-port of the Bootloader.
5. Ensure that the IP address and the TA-port of the Bootloader are set correctly in the Winsol setup.
Serial interface (USB, RS232): The data logger (BL-NET, D-LOGG) is not recognised during "Test" of Winsol.
1. Ensure that the data logger is connected to the PC via a USB connection.
2. Check that the power supply of the BL-NET or the switch setting of the slider switch of the D-LOGG. If no controller is connected to the data logger, the D-LOGG slider switch must be in the "USB" position or the Bootloader must have its own power supply (battery, power pack).
3. Check in the Windows Device Manager whether the USB driver has been correctly installed (Device Manager ðPorts (COM and LPT)). In this case, its virtual COM port appears in the list as "USB Serial Port".
3.1. If the driver has not yet been correctly installed, carry out the installation again (see Chapter "USB driver \ Installation" in the data logger manual).
4. If the data logger is provided with at least one controller, check the data transfer from the controller to the data logger (see the next point).
Data transfer from the controller to the data logger is not working.
(BL-NET, D-LOGG: No measured values are displayed in the "Current measured values" of Winsol.)
1. Ensure that the data logger is connected to the controller via the DL-bus or the CAN bus.
2. Check the connections and in particular ensure the polarity is correct.
3. 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 link"). On controller UVR16x2, data output must be enabled in “DL settings” in the menu “DL bus”.
4. Ensure that, the data logger is configured for the corresponding data logging process (DL-bus or CAN bus (see Setup dialogue chapter)
5. If several controllers are recorded using the data logger, check the data connections individually to limit the problem. To do this, connect the data link (DL-bus) or CAN bus as appropriate to the other controllers. When doing so it is important that the data link is connected directly to the controller and not to the data input of the data logger, as otherwise you will not receive useful results!
5.1. If data transfer functions over the DL-bus with each controller individually, then the cause of the error is crosstalk between the two data links of the DL-bus. In this case the two data links must be routed separately or at least one data link must be routed in a shielded cable.
5.2. If data transfer via the CAN bus functions with each controller individually, the cause of the fault may be the allocation of 2 identical network node numbers or an incorrect network terminating resistor.
6. To limit the cause of the error during data transfer to a single data link, carry this out as a test over a short cable (< 1 metre).
6.1. If data transfer functions over the short cable, then the error cause could be crosstalk caused by an external interference source in the data link (DL-bus). In this case, the data link must be routed in another way or a shielded cable must be used.
7. If, in spite of the testing of all listed points, incorrect behaviour still exists, please contact your dealer or contact the manufacturer directly. However the cause of the fault can only be found if a precise description of the fault is provided!
BL-NET, D-LOGG: The data are recorded with an incorrect timestamp (date, time).
1. As when data logging with the VR1611 or UVR61-3 the timestamp is generated by the controller, in this case the time indication in the controller must be corrected.
Warning: To be able to ensure a higher time resolution, the data logger synchronizes with the controller during startup and as a consequence updates its internal timestamp. Therefore the data logger must be switched off (zero volts state) for a few seconds after changing the time settings in the controller (pull out the DL and/or CAN bus), so that it immediately synchronises itself after the restart.
2. When data logging using controllers without an internal time, the time or the point-in-time at which the data logger was disconnected from the controller is taken from the PC, so that the time can be allocated to the recorded data.
The csv files are not displayed in the corresponding data path "C:\Programs\..." or the searched for subdirectory itself does not even exist.
Under certain circumstances, under Windows 8, Windows 7 and Windows Vista, the files are saved under a user-specific "virtual program path":
C:\Users\<USERNAME>\AppData\Local\VirtualStore\Programs\Technische Alternative\Winsol\...
The folder "AppData" is not displayed as a matter of course and must therefore be entered manually in the Input field.
This takes you to the searched for files.
It is generally recommended that the Winsol data path is chosen outside the Program folder (default installation path) (see Chapter "Basic Settings").