| Issue ID | Issue | Workaround | Affects releases |
|---|---|---|---|
| CM-7921 |
The RFL100 data logger may get into low battery level and then quickly run out of batter before it has enough time to report the low battery level to AP10, and thus the low battery alarm is not received by the viewLinc.
|
As prevention, use lithium batteries only when needed in cold environments and with CO2.
|
1.4.0 onward |
| CM-1283 |
The RFL100 settings may be reset to their default values when the RFL100 joins a new AP10 or has been disconnected for at least 24 minutes from the same AP10. This can affect threshold limits, LED settings, display panel settings, and non-metric units. However, viewLinc will keep the settings and trigger the threshold alarms correctly.
|
As a workaround, you can re-apply the settings again from viewLinc. To do this, you can edit the device properties and channel properties, disable the settings, and then enable them again. This will restore the previously configured settings. | All releases |
| CM-3967, CM-6480 | In dual-probe mode (dual Temperature or Co2), if one of the probes is not connected, sending data to viewLinc may be blocked for both probes. | To resolve this, you can reconnect the missing probe and restart the RFL100 logger. This will allow all data in the RFL100 to be backfilled in viewLinc, and operation will resume normally. If you intend to change the setup to a single probe mode, you should follow the installation procedure to reconfigure the RFL100 accordingly. This will prevent any further issues with the missing probe and ensure that the data is being sent to viewLinc correctly. | 1.3.0 onward |
| CM-3252 |
When the RFL100 data logger restarts and connects to the system without probes connected, there is no missing channel or sensor failure alarm in viewLinc. This means that viewLinc users may not know that a probe is missing or broken in this case.
|
To detect this, you can check the logger display and it will show an error code 110. As a workaround, you can reconnect the probe(s) and restart the RFL100 data logger. This will resolve the issue and the system will be back to normal operation. It is important to make sure that all probes are connected and working properly before restarting the RFL100 data logger. | 1.3.0 onward |
| CM-3193, CM-7650 |
If one probe is missing in dual-probe mode, a sensor failure alarm will be triggered in both locations (the affected and non-affected one). This can be confusing as it does not clearly indicate which probe is missing.
|
As a workaround, you can check the RFL100 logger display to determine which probe is affected. This will allow you to identify the missing probe and take the necessary actions to resolve the issue. In this way, it is important to pay attention to the alarm and check the RFL100 logger display to identify the missing probe.
|
1.3.0 onward |
| CM-3256, CM-7057 | We have spotted an issue that occurs when changing a probe, for example, switching from a dual-T probe to a T+RH probe, without adhering to the specified probe replacement guidelines. Consequently, temperature and humidity data on channel 2 may become intertwined between the removal of the initial probe and the point at which the new probe becomes fully operational within viewLinc. This may manifest as temperature data being wrongly recorded as humidity data, or vice versa. | To prevent this issue, it is important to follow the instructions provided in the user manual on how to replace a probe of different parameters. This will ensure that the data is recorded correctly and that the new probe is properly set up and functional. | All releases |
| CM-7586, CM-7676 |
Measurement samples may have future timestamp after repeated reboot. This error is extremely rare. One situation where it was noticed is with exhausted (or wrong type) batteries in CO2-mode logger.
|
Make sure to use correct type of batteries and ensure the batteries are replaced before they become empty. | All releases |
| Issue | Workaround | Affects releases | Resolved in |
|---|---|---|---|
|
CM-7093: There may be a timestamp shift of 1 minute between RFL100 measurements timestamps as shown in the RFL100 log and viewLinc measurements timestamps. This issue is noticed after the RFL100 reboot. |
You can reboot the RFL100 to resolve this issue. | All RFL100 versions prior to v1.8.0 | 1.8.0 |
| CM-7554: An issue has been identified where a loss of USB power to a CO2 probe on one data logger triggers a "Low Battery" alarm in viewLinc, inadvertently causing all data loggers connected to the same AP10 Access Point to display the same alarm. While this alarm correctly indicates that the affected logger is utilizing backup battery power, it erroneously appears for unaffected loggers, potentially toggling on/off based on latest status communications to viewLinc. However, the actual battery level indications on both the data logger display and the viewLinc monitor remain accurate and reliable for all loggers. | Please restore USB power to the affected data logger to resolve the issue and eliminate the inaccurate "Low Battery" alarms on all loggers connected to the AP10. For true battery status, refer to the battery level indications on the data logger display or the viewLinc monitor. A comprehensive fix is in progress, and your patience is appreciated. | Found to affect AP10 v4.x to 5.00. Not RFL100 firmware related. | AP10 firmware version 5.1.0 |
| The RFL100 display measurement reading may be rounded differently from the viewLinc reading. For example, the RFL100 display may show 21.3C, while viewLinc, configured with one decimal resolution, will show 21.4C. Please note that the actual measurements without rounding are matching. This means that this difference is only in the display, and it is not affecting the accuracy of the measurement. | No workaround | All releases prior to 1.7.0 | 1.7.0 |
|
Measurement logs copied at separate times from RFL100 MTB USB may have non-matching timestamps of the measurement samples. It occurs with low probability, and the shift is up to 1 minute. It does not affect data sent to AP10/viewLinc. |
In applications where users copy measurement logs, use one copy of the file. | All releases prior to 1.5.0 | 1.5.0 |
| The software watchdog may reset the data logger. If the logger is USB powered and does not join to AP and viewLinc (for any reason), the logger gets reset every 3h 49min. Sometimes one measurement may be lost if a reset occurs at measurement time. | Ensure that the data logger is connected to AP10 and viewLinc. | 1.4.0, 1.4.1 | 1.5.0 |
| Upgrading logger with dual T mode to v1.4.0 results in empty channel 2. |
Before or after the software update, perform a factory reset. Then when v1.4.0 is installed (and factory reset done), re-install dual T probes.
|
1.4.0 | 1.4.1 |
| When connecting RFL100 with a USB cable to a PC, it can take a long time without any sign to the user that it is connecting. | When connecting RFL100 via USB to a PC, wait for the connection to be set up. It can take a couple of minutes. | 1.0.0, 1.1.0, 1.2.0 | 1.3.0 |