Frequently asked questions

Supported features

What kind of Coronis modules have been fully tested using JWaveLib ?

The following list of modules have been thoroughly tested and are active on production sites :

  1. WaveTherm? Dallas - 1 sensor
  2. WaveFlow? - 1 counter
  3. WaveTalk? 25 mW and 500 mW
  4. Serial WavePort? 25/500 mW

What is the list of all the supported Coronis modules ?

  1. WaveTherm? Dallas - 1 sensor
  2. WaveTherm? Pt100/Pt1000
  3. WaveFlow? - 1 counter
  4. WaveSense? 0-5V / 4-20mA
  5. WaveTank?
  6. WaveTalk? 25 mW and 500 mW
  7. Serial WavePort? 25/500 mW

What if the modules I want to use is not already supported by the JWaveLib ?

Our politic is to support all the Coronis modules. Thus if you plan to use a module that is not actually supported by the JWaveLib, contact the support and we will give you an estimated time to get full support on this module. Lots of modules just require a very small development to work with the current JWaveLib.

For example : you need to use a WaveFlow? with two counters (A and B). Dipole Consulting will provide you a JWaveLib version supporting this type of module within one month.

Does JWaveLib support automatic network configuration (SDP) ?

At the moment, JWaveLib does not support the SDP protocol. The feature is in the development process for milestone 2.0 but will be linked to the availability of the SDP protocol inside Coronis hardware.

Configuration

Coronis products related questions

How can we know if the module supports extended datalogging ?

This is not possible using the Wavenis protocol. If the module has a strange behaviour when asking for the extended datalogging measures, it does probably not support extended datalogging. Only the Coronis technical support can confirm it. Send an e-mail with the module id to technicalsupport@… to check that.

Waveport

Waveflow

WaveTherm?

Does my WaveTherm? support permanent loop mode for extended datalogging ?

WaveTherm? must use the 02.xx firmware to support permanent loop mode in ***extended datalogging***. Version 1.06 and lower did not support it and thus extended datalogging was always in stop memory full mode.