FLRU + Netris3

Description of the device
The model FLRU level transmitter with reed-chain technology in combination with the WIKA model NETRIS®3 radio unit is used wherever web-based remote monitoring of level measurement in liquid media is desired. Condition-based and preventive maintenance through centralised big data analysis is thus possible. Level transmitters of this model series work on the float principle with magnetic transmission and are used wherever centralised, web-based remote monitoring is required.The float's magnetic system in the guide tube actuates a resistance measuring chain that corresponds to a 3-wire potentiometer circuit. The measurement voltage generated by this is proportional to the fill level. The measurement voltage is very finely stepped due to the contact separation of the measuring chain and is thus virtually continuous.Depending on the requirements, several different contact separations are available. The FLRU reed level transmitter is part of the WIKA IIoT solution. With this, WIKA offers a holistic solution for your digitalisation strategy
For more information see product site.
FLRU + Netris3 Parser Quick Start
Parser API
All functions are pure (no global mutation) except adjustMeasuringRange which updates internal range configuration for subsequent decodes.
Types:
Input types:
interface UplinkInput {
fPort: number // LoRaWAN FPort
bytes: number[] // Raw payload as array of unsigned bytes (0-255)
recvTime?: string // Optional ISO timestamp (if your LNS provides it)
}
interface HexUplinkInput {
fPort: number // LoRaWAN FPort
bytes: string // Raw payload as hex-encoded string (case-insensitive, even length)
recvTime?: string // Optional ISO timestamp (if your LNS provides it)
}Return type (shared by all decode helpers):
type Result = {
data: Record<string, any> // Parsed key/value pairs
warnings?: string[] // Non-fatal anomalies
} | {
errors: string[] // Fatal or structural issues only
}To understand the data field, take a look at the examples and the schema definition.
Supported channels to identify different sensors by:
// Is used in the returned data
type ChannelName = 'level'Channels that support adjusting the measurement range:
type AdjustableChannelName = 'level'Channel Configuration
| Channel Name | Min Value | Max Value | Unit | Configurable |
|---|---|---|---|---|
| level | 0 | 1000 | mm / in | ✓ |
decodeUplink(input)
function decodeUplink(input: UplinkInput): ResultdecodeHexUplink(input)
function decodeHexUplink(input: HexUplinkInput): Resultbytes must have even length; case-insensitive.
adjustMeasuringRange(channel, range)
// Will throw on invalid channel name or if the channel disallows range updates
function adjustMeasuringRange(
channelName: AdjustableChannelName,
range: {
start: number
end: number
}
): voidApplies to future decodes only.
adjustRoundingDecimals(decimals)
// Smartly adjust number of decimals for rounded values
// Impacts all numeric values in all outputs
// Default is 4
function adjustRoundingDecimals(decimals: number): voidApplies to future decodes only.
Verifying Ranges
The level channel on the FLRU is configurable. You must verify the actual measurement range from your device specifications or identification frames. The parser default shown in the table above may not match your device configuration.
Using Identification Frames
This device supports both TULIP2 and TULIP3 protocols. Each sends identification frames containing channel configuration:
TULIP3 (Message Type 20):
{
"data": {
"messageType": 20,
"channelId": 0,
"channelName": "level",
"measurementRangeStart": 0,
"measurementRangeEnd": 1000
}
}TULIP2 (Message Type 6):
{
"data": {
"messageType": 6,
"channelId": 0,
"channelName": "level",
"measurementRangeStart": 0,
"measurementRangeEnd": 1000
}
}Use measurementRangeStart and measurementRangeEnd to configure the parser before decoding data messages.
Quick Start
- Check your device's actual measurement range from purchase configuration, device specifications, or identification frames (see above)
- Add configuration code below at the bottom of your parser file
- Add wrapper function if your network server is non-compliant:
function decode(input) { return decodeUplink(input) }
Configuration code (add at bottom of parser file):
// Replace values with your device's actual measurement range from specifications or identification frames
adjustMeasuringRange('level', { start: 0, end: 1000 })NPM Module Inclusion
| Device | Included | Factory function |
|---|---|---|
| FLRU+NETRIS3 | ❌ | ❌ |
