Hi, I have problems to convert float and 32b (signed/unsigned) registers to obtain a result able to be sent to MQTT broker. The modbus device is a semaphore/Servelec Tbox unit. I use node-red modbustcp Example: I have a float register with a value of 22.362 in it. I want to pass that value to my MQTT broker. When I debug in node-red, I obtain an array: [16818,58720] but I'm stuck to convert this to a readable precise value of 22.362 (22.36 will be ok) I have no probs with int16 registers (because they are 16bits obviously but need to find a function to convert negative values to readable ones) I found here a function but the result seems weird (imprecise). *Edit: I made my test simple. That's the reason I set the value of 22.362 into register 22362 ! Easier to remember [NodeRed - float to value]

In the Change nodes where you extract the individual parts add another row that Sets msg.topic To the/topic/for/this/value

Hi Steve and thank you for the link. It seems that for me the code is not that difficult (...) because values on the array are not hex but plain decimal. With my first test, I put readFloatBE() and I obtained a usable value. However, very strange to me, the result varies with every poll (even the data in the register is fixed for my test). Stranger, with 2 polls with the same code, I obtain 2 sets of variable values... The value set in my modbus register is 35.174 and I have the right value (35.17) only once in a while. *Edit: here is the code I put. Ok, I'm a real newbie and I added what I found around here. I really don't know why those 2 lines are needed, but without: no results. const buf = Buffer.allocUnsafe(4); buf.writeUInt16BE(pay[0]); // high byte *Edit2: it seems, for unknown reasons, that LE displays now "correct" values (aka 0 because wrong type) instead of a replicated one. So Big Endian seems +/- ok, except the variability. How is it possible ? Thank you++ Mike [node-red float different results] [node-red float different results 2 and code] [node-red float readFloatBE()]

I suspect when you update msg.payload in function 1 you are affecting the object before it's processed in the 2nd function. It looks looks like the payload is an array/object so I world probably try returning a new object instead of updating msg.payload e.g... var msg2 = { payload : buf.readFloatBE(0) } return msg2; Try to remember the asynchronous nature of node-red and how object references work in JavaScript.

Can't really help more unless you post your flow and sample data.

[image] Steve-Mcl: I suspect when you update msg.payload in function 1 you are affecting the object before it's processed in the 2nd function. Assuming this is in a recent version of node-red (@PPz which version is it?) then I don't think that should happen as node-red should automatically clone the message for the second wire out of the node. @PPz in the functions use node.warn() to show the contents of pay after you have picked it up.

[image] Colin: node.warn() thank you both of you (@Steve-Mcl) for your kind help. My version is 1.0.3 the code of the function is : let pay = msg.payload; const buf = Buffer.allocUnsafe(4); // (4) is ok buf.writeUInt16BE(pay[0]); // high byte msg.payload = buf.readFloatBE(0); // 2 numbers after comma (string) // msg.payload = buf.readFloatBE(0).toFixed(2); // return msg; the float value into my plc is 22.362 the raw received data is an array [16818,58720] the result (after function) varies from 22.25 to 22.37 about node.warn(), I'm affraid that I'm a real newbie about node-red

[image] PPz: about node.warn(), I'm affraid that I'm a real newbie about node-red Have you tried searching for it?

[image] Colin: node.warn() Yes, but when I inject node.warn(pay); I receive exactly the same array value [16818,58720] as the raw debug message Update: when I inject node.warn(buf), I obtain a splitted array like this one: [65,178,98,5], or [65,178,125,3], or [65,178,0,0] (variable). Ok, 16818 = (256*65)+178 Update 2: for what I understand here, the 2 first values of the array [65,178] seems consistent and represent probably/certainly the value that doesn't change (22). Why the others are changing ? A real mystery for me. Update 3: maybe it will help you, but the weird thing about my plc is that the right value is in the array when dealing with 32b registers. If I poll a 32b register with a value of 22358, the node-red poll send me an array with [0,22358]. So it seems that's even not a hex value, just the plain decimal value...

[image] PPz: let pay = msg.payload; const buf = Buffer.allocUnsafe(4); // (4) is ok buf.writeUInt16BE(pay[0]); // high byte msg.payload = buf.readFloatBE(0); You are allocating a buffer of length 4 bytes. Then you use writeUInt16BE to write to the first two bytes. You have not written anything to the second two bytes so they are left with whatever happened to be lying around in that bit of memory. That is why they contain variable data. You then use readFloat to read all four bytes to give you the (veriable) result.

[image] Payload's number to two 16 bit register to be send via modbus General Hi ! U can use this code in function....after connect it to Modbus Flex Write function float32ToUint16(value) { var buffer = new ArrayBuffer(4); var intView = new Uint16Array(buffer); var floatView = new Float32Array(buffer); floatView[0] = value; return [intView[0], intView[1]]; } //var incoming = JSON.parse(msg.payload); //Compose ModBus message (Holding Registers) READ/WRITE var modbusHR = { payload : { 'value' : [ float32ToUint16(msg.payload)[0], float32ToUint16(msg.…

Node-RED

Node-RED Forum

Newbie: convert modbus float [array] register to float value

General

Steve-Mcl 14 January 2020 11:22 2

See this thread (read it all) there are some pointers in there that might help.

Topic		Replies	Views
Convert modbus float [array] register to value General	8	13533	29 June 2020
Working between Floating Point and Int. data types General	23	10851	26 March 2020
How to get modbus float from register? General	15	1785	8 July 2020
Modbus TCP float to value General	35	3650	16 February 2022
Modbus UINT16 to decimal? General modbus	34	1172	18 September 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Newbie: convert modbus float [array] register to float value

Related topics