What do you think about making it two fold - one for making string
encoding settable optionally for connection and separately at the tag level?
With regard to syntax, field/tag patterns themselves (AFAIK) so far do
not use curly brackets anywhere, so its fine to begin with them.
Best,
Łukasz
On 18.02.2023 23:39, Christofer Dutz wrote:
Hi all,
As you know, I recently created a PR from the changes another github uses did
based on our work. He also changed the syntax of the String tags in some
drivers to include an encoding.
I didn’t like the format he chose (separating the encoding from the the rest
with a pipe symbol). But in general I think it would be good, if we allowed
specifying an encoding, if we want to use a non-default encoding.
So my proposal would be to add the encoding to all tags (not only strings) as I
could also imagine that it might be beneficial to provide different types of
integer, floating point, date and time encodings.
My proposal would be to have an additional encoding wrapped in curly braces at
the end of the tag address:
Example:
%DB120.DBX234:STRING(10){ASCII}
Espeically for protocols like Modbus, I think this could be pretty good to have.
What do you think?
Chris
