node-red-contrib-buffer-parser icon indicating copy to clipboard operation
node-red-contrib-buffer-parser copied to clipboard

A node-red node to convert values in a buffer, integer array or hex string into many different data type(s). Supports Big/Little Endian, BCD, byte swapping and much more.

Results 13 node-red-contrib-buffer-parser issues
Sort by recently updated
recently updated
newest added

In your documentation you refer to something called final value. Could you elaborate what a final value semtically is, please?

Ubuntu 22.04 Node-RED 3.1.3 node v20.10.0 I am parsing a buffer with lots of double values, which are 8-byte IEEE754Double. I add double(le) items to node buffer-parser, but it seems...

bug

It would be helpful to user to know, that this modifes the source buffer, when swapping, since the buffer might be sent to other nodes too, or shown in status...

Is the option to output an Int missing? I have an array of bytes: [13,28,2,65,0,0,0,1] The first two (13 and 28) represent an integer value of (13*265)+28 or 3473 The...

As far as I understand, the scale input box only allows one operation. According to my experience, there are many scenarios where it is necessary to carry out two operations...

enhancement

If I use the buffer node in dynam. spec and I want to extract a byte value - the UI spec works the dynam. spec. doesn`t. ![image](https://user-images.githubusercontent.com/58858526/212409074-fd96860e-53fa-4584-84da-a1733ae0d4c2.png) [buffer-parser.zip](https://github.com/Steve-Mcl/node-red-contrib-buffer-parser/files/10415011/buffer-parser.zip)

When using dynamic specs, it only seems to work when the option type is set to string. All other types return 0, which is incorrect. This behavior can be seen...

Unless I include `'mask': ""` in my `'items'` array the resulting payload is returned as zero. In the guide it says the `'mask'` property is optional and I would expect...

see https://discourse.nodered.org/t/updated-node-red-contrib-buffer-parser-v3-1-2/25879/61?u=steve-mcl

documentation

teltonika messages (gps info) are dynamic. That means internally some positions define length for other fields or number of repeated structure to parse. https://wiki.teltonika-gps.com/wikibase/index.php?title=Teltonika_AVL_Protocols&mobileaction=toggle_view_desktop#Codec_8 ![Captura desde 2022-09-17 12-25-58](https://user-images.githubusercontent.com/220968/190853565-702ad363-f84c-4e59-8f05-e47fed2617fb.png) Examples: For...