FAQ

Why don’t the water values match my JBL drop count test?

Each test has a fixed scale, which enables the allocation of the water values. For example the steps in a drop test are different to those of the ProScan. Therefore ProScan also has a scale to enter the values and to avoid jumps at repeated measurements. Bigger differences between the values mostly indicate an incorrect reading caused by shades/reflections. Best is to carry out the test near a window with bright light. Direct light from above casts shadows or reflections which can affect the colour rendering. Please remember ALWAYS to shake the water off the analysis strip sideways. “Puddles” can cause the colour fields to react with each other and to produce reflections.

Incorrect values can occur through expired drop tests too (i.e. tests which have been open for more than 9 months) or incorrect use (with air-filled drops and deviating water quantities). In this case please check your measurements once more.

One example:

The aquarium has the following water values: 18 mg/l NO3, 0.5 mg/l NO2, 5° dGH, 7 mg/l CO2, 1.5° dKH, 6.8 pH.

The measurements with the different systems give the following values:

The ProScan shows following values: 18 mg/l NO3, 0.5 mg/l NO2, > 4° dGH, < 15 mg/l CO2 (by way of calculation), 1.5° dKH, 6.8 pH.

The drop test shows the following values: 20 mg/l NO3, 0.6 mg/l NO2, 5° dGH, 10 mg/l CO2 (by way of calculation), 2°dKH, 6.8 pH

Both results are very precise and differ only slightly from each other. This has no negative effect on further statements and actions. Inaccuracies in the application have a greater effect on the results than jumps resulting from the scale. Finer scaling steps could result in an inability to allocate the results exactly to the same measuring points when there is some divergence of light and distance in the surroundings. This would cause the values to jump again in a repeated test.

A word about cookies before we continue

The JBL Homepage also uses several types of cookies to provide you with full functionality and many services: We require technical and functional cookies to ensure that everything works when you visit this website. We also use cookies for marketing purposes. This ensures that we recognise you when you visit our extensive site again, that we can measure the success of our campaigns and that the personalisation cookies allow us to address you individually and directly, adapted to your needs - even outside our website. You can determine at any time - even at a later date - which cookies you allow and which you do not allow (more on this under "Change settings").

The JBL website uses several types of cookies to provide you with full functionality and many services: Technical and functional cookies are absolutely necessary so that everything works when you visit this website. In addition, we use cookies for marketing purposes. You can determine at any time - even at a later date - which cookies you allow and which you do not (more on this under "Change settings").

Our data protection declaration tells you how we process personal data and what purposes we use the data processing for. tells you how we process personal data and what purposes we use the data processing for. Please confirm the use of all cookies by clicking "Accept" - and you're on your way.

Are you over 16 years old? Then confirm the use of all cookies with "Noticed" and you are ready to go.

Choose your cookie settings

Technical and functional cookies, so that everything works when you visit our website.
Marketing cookies, so that we recognize you on our pages and can measure the success of our campaigns.

PUSH messages from JBL

What are PUSH messages? As part of the W3C standard, web notifications define an API for end-user notifications that are sent to the user's desktop and/or mobile devices via the browser. Notifications appear on the end devices as they are familiar to the end user from apps installed on the device (e.g. emails). Notifications appear on the end user’s device, just like an app (e.g. for emails) installed on the device.

These notifications enable a website operator to contact its users whenever they have a browser open - it doesn’t matter whether the user is currently visiting the website or not.

To be able to send web push notifications, all you need is a website with a web push code installed. This allows brands without apps to take advantage of many of the benefits of push notifications (personalised real-time communications at just the right moment).

Web notifications are part of the W3C standard and define an API for end user notifications. A notification makes it possible to inform the user about an event, such as a new blog post, outside the context of a website.

JBL GmbH & Co. KG provides this service free of charge, and it is easy to activate or deactivate.