Dear all, I try to read an serial String and convert it to something "useful". Therefore I would need the HEX output of the serial String but all I get are these strange signs when I connect the Serial IN to my serial unput from the external device. payload: string ��1 $$V=�|wxr'n{zs�sy{��{}y…

So unfortunately is the split node not working as expected. In my opinion an issue should be raised. Originally I expected that the split node would work to analyse the data stream: [image] However the split not works not properly - so the data stream is splitted each time a byte with value 36 i…

No, I mean I want to ignore the serial stream until 0x24 0x24 0x56 shows up. After that I want to read 57 characters and then I want to ignore the stream again until the same pattern shows up again. Because this is the pattern that tells me: next 57 characters are of interest

To be honest I am unable to replicate your flow. You are not using the "serial-port" node which I use to read the "interesting" part of the stream. You said: "use LF" but I have no idea how to tell the serial-port to do so.

How you have created these strings in your second posting (4th post)? [image] Convert HEX to useful values? General Ok, now I get decimal or integer values ... they do not mean anything but ok, first step done slight_smile The serial input looks like this: 24 24 57 0F 0…

in this case I get rubbish symbols in strings with different lengths: [image]

I tried your solution to re-arragent the buffer but there is something broken with the offset ... I do not understand this part good enough to fix it myself :frowning: [image]

Can you change the fist buffer maker as follows: [image] remove the link first to the first buffer parser - and post the debug of the buffer maker output [image] [image]

the result is a set of 5 messages with buffers of different lengths ... continously repaeted [image]

That looks perfect . so the first string should be filtered out by the complete flow. - so in my opinion you can try the flow. [image] This looks to match the correct scheme.

sorry, no ... it is even more complicated: the length of the answer-string is quite variable: 5, 15, 16, 76 and 77 characters .... sometimes (seldom) only 66 [image]

So the compete flow should filter out the strings which starts with 36,36,86 [image] [image]

Node-RED

Node-RED Forum

Convert HEX to useful values?

General

Gawan 25 February 2022 07:15 37

It worked at the very first try

Topic		Replies	Views
Read serial and extract reading General	7	1426	24 December 2019
Splitting a Serial string in to individual packets General	19	336	12 December 2022
Serial Data Parser / Decoding General	20	1626	22 January 2022
Need assistance converting serial input buffer to numbers General	28	925	7 June 2021
Convert Bytes to integer General	14	6269	9 January 2021

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.

Convert HEX to useful values?

Related topics