Odd format EGI Nexus 1500+ Meter

[HansZnarf]

I find this really and odd format. Tried playing around with what others have assisted with so far without success. Please see following right out of device manual.

3.7: Type F7- Secondary Voltage, Current, VA, VAR, Watts, Hz or Flicker
Length: 2 Registers (4 bytes)
Range: +32767 / -32768
Unit: 1/65536 V, A, VA, VAR, W or Hz
The registers together contain a four-byte signed (2's compliment) integer. Positive
values have the most significant bit clear, and have the same magnitude as an
unsigned integer. Negative values have the most significant bit set. The magnitude of a negative
value is found by complementing (inverting) all of the bits and adding 1.

[Colin]

@HansZnarf

The magnitude of a negative
value is found by complementing (inverting) all of the bits and adding 1.

That is the normal format for a signed integer. The buffer parser node should convert it for you.

[HansZnarf]

Colin:

Many thanks: NOTE - will we need to write any code in the buffer parser for this to work?

Thanks,

Hans

[dynamicdave]

Can I ask, is this thread a continuation of your previous one??
If it is, then we seem to be covering the same ground again.

Signed Integer showing 3 phase power factor for electrical metering

This is a signed three phase power factor value. The manual states the following "-100 to +1000 to +100 in 1000th. It is from a 16 bit register. The most significant bit is left as read and is the sign value. When "0" the number is positive. When a "1" it is negative. The most significant value bit is 512 in binary Example 0000_0011_1110_1000 = 1000 and 1000_0000_0000_0001 = -1. Thanks, Hans

[HansZnarf]

[
{
"id": "b9ea5d5227b5083a",
"type": "modbustcp-read",
"z": "ffde3f89549527d7",
"name": "",
"topic": "",
"dataType": "HoldingRegister",
"adr": "187",
"quantity": "2",
"rate": "10",
"rateUnit": "s",
"server": "c840a64164607c03",
"ieeeType": "off",
"ieeeBE": true,
"x": 110,
"y": 40,
"wires": [
[
"3a2182f4ea0b30d3",
"ee79504be1c1dbe3"
]
]
},
{
"id": "3a2182f4ea0b30d3",
"type": "debug",
"z": "ffde3f89549527d7",
"name": "Raw",
"active": true,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "payload",
"targetType": "msg",
"statusVal": "",
"statusType": "auto",
"x": 430,
"y": 100,
"wires":
},
{
"id": "66ba3472bad9425b",
"type": "debug",
"z": "ffde3f89549527d7",
"name": "Buffered",
"active": true,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "payload",
"targetType": "msg",
"statusVal": "",
"statusType": "auto",
"x": 440,
"y": 40,
"wires":
},
{
"id": "ee79504be1c1dbe3",
"type": "buffer-parser",
"z": "ffde3f89549527d7",
"name": "",
"data": "payload",
"dataType": "msg",
"specification": "",
"specificationType": "ui",
"items": [
{
"name": "item1",
"type": "int16be",
"offset": 0,
"length": 1,
"mask": ""
}
],
"swap1": "",
"swap2": "",
"swap3": "",
"swap1Type": "swap",
"swap2Type": "swap",
"swap3Type": "swap",
"msgProperty": "payload",
"msgPropertyType": "str",
"resultType": "keyvalue",
"resultTypeType": "return",
"multipleResult": false,
"fanOutMultipleResult": false,
"setTopic": true,
"outputs": 1,
"x": 290,
"y": 40,
"wires": [
[
"66ba3472bad9425b"
]
]
},
{
"id": "c840a64164607c03",
"type": "modbustcp-server",
"name": "N 1500+",
"host": "10.145.44.200",
"port": "502",
"unit_id": "1",
"reconnecttimeout": "5"
}
]

[HansZnarf]

Let me know if I exported this correctly. Note: The modbus read that I am using is listed 4X register minus one. If the published value is 188 I must start at 187. In "our" world the would be JBus.

[HansZnarf]