Frequently Asked Question

• Delay time inconsequent.
  e.g. The delay is showing as 0.462 not 0.495 like the datasheet
  
  The visible delay-values are indicative. Due to rounding, there can be small differences. But as the rounding is only done for visualization on the PC screen, the real values in the sensor are stable and exact.
  If a customer tries to set the delay times, finding an optimum setting, and save the x.DIS file, this file contains the real sensor values in register 1330 en 1331. The value in our config file = 33, which means: Delay time = n x 15ms. So if n=33 à delay time = 495ms
  If the x.DIS file is sent to DIS, we can manufacture sensors with exactly the same values as the customer has defined
  
  
• SIL1 switch with firmware V3.0.0 shows completely different delay time and frequency.
  e.g. The delay time is 80ms in the datasheet, but the configurator shows 30ms. 
  
  The PC application V3.16 of the QG40 configurator uses different factors to calculate delay time and frequency for various sensors. As a result, the same register value may produce different visible delay times and frequencies depending on the sensor.
  
  In this case, a sensor with firmware version V2.0.0 uses a factor of 40 to calculate the delay time. For example, a register value of 2 corresponds to a delay time of 80ms. However, because the configurator does not recognize the new firmware, it applies an incorrect factor of 15 for the calculation, resulting in a displayed delay time of 30ms on the screen.

• Unknow sensor
  

If you get this error, it means the PC program can't read the sensor name. It can happen for example if your operating system is using a different decimal format than in the Netherlands.
For example, in the sensor name, you will see the max, measuring range such as 4,0 for an acceleration sensor. In some countries, "." is used instead of "," in decimal numbers. If the sensor name was changed to 4.0, the PC program will not recognize the sensor name and therefore show an Unknow sensor error.

• One wire communication unstable.
  sometimes, some of the sensor parameters cannot be read by the software. It is caused by the bad communication on one wire. This is improved in V3.15.

• Doesn't start in windows 11
  Try to install the attached driver for FT260chip which is used in the dongle. The driver was included in the windows before, but nowadays the new system doesn’t have this anymore.