I did a quick search and found a $99 product, I have no idea if it would work, It would not be an out of the box solution. See:
https://www.kincoautomation.com/products/hmi More research is needed.
The LF would be a basic problem for even a simple terminal because it would be list. I think you would want to strip the LF and only output the string IF it did not change from the previous value.
There may be something here:
https://comfiletech.com too.
The smart relay might be able to do what you want too. I did, once, download IDEC's simulator. It's a slight investment to start. See:
https://us.idec.com/CMSContent/SmartRelay/index.html
Here's a display too.
https://www.crystalfontz.com/product/cfa533tmiku-display-module-usb-16x2-character Note that pretty much they all have commands to control them, so a simple monitor is not likely to work.
In this one,
https://www.redlion.net/product/225-6-digit-led-serial-slave-display-rs-232rs-485 you need a specific format.
So, it depends on a lot of stuff. How fast you want to do it. Power supplies available. How many units. How much effort into packaging.
It seems like a pretty tough project. Here's
https://www.redlion.net/product/225-6-digit-led-serial-slave-display-rs-232rs-485 a company that specializes in CUSTOM.
Here's another company that makes SBC's.
www.picaxe.com is a small PIC that is programmable in BASIC
Find a display/displays that fit a basic footprint that you could substitute if necessary, e.g 1/2 DIN so your not locked in to one manufacturer. If you need mounting hardware or bezels, look at that too, What type of power is available?
I just see the basic structure of:
Power up: Display: *****.** or whatever.
Power up reading: On power up, look for a Line feed. Ignore the first stuff.
Now your synchonized.
I'd continue to make sure the data is valid. e.g. the right format until you program a "LF expected" state.
So, LF becomes the synchonization character.
You could make the routine a bit better by clearing the communications buffer on power up and start the state machine with is it a "+" or "-" then continue by processing as though you received a LF followed by a + and -.
So, this method effectively will allow the display of the first number. If there is junk in the buffer, you'll be looking for a LF to reset the state machine.
You could possibly display invalid digits as backwards question marks too.
I think to get a reliable display, there is a little more smarts needed, Sometimes power-up could leave a character in the buffer on a poorly designed system. let's say you disconnected the RS232 port while it was operating. You then need a way to recover.
There's likely no parity, checksum or other types of error checking.
So, you have to assume that the first read character can be:
Invalid
a "+" or a "-"
Then develop a state machine using your own functions:
issign(); checks for +-
iswhitespace() checks for space
isdigit() or isnotdigit()
isdecimal(); checks for decimal point
isCR()
isLF()
With fancier displays you could actually show the character received in reverse video.
Your testing might be easier too. e.g. power it up and use a terminal for input.
Press a 5; it would display a reverse video 5. and continue displaying reverse video for stuff that doesn;t fit in each position.
When a LF shows up; look at the attributes and numbers.
If you typed the same thing don't display anything, You could move the cursur.
There's a lot more involved if you want to eliminate flicker, make things easy to debug and not relay on what should happen.
With the display, it should happen fast enough that you won;t see anything, BUT if you typed characters slowly from a connected terminal emulator acting as your device, the error checking would be apparent.
So, I'm advocation a display and a small processor that makes the display robust.
Bold, reverse video, backwards question marks, question marks are all possible ways of indicating errors. reverse video of the character received can help determone if it's a bad baud rate or a loose cable. You don;t need the instrument while debugging and you can work faster that way.
I do remember when I managed a huge program development where in the final stage, it would require 2.5 minutes to interact with the hardware, So, if the hardware wasn't present, it would ask if you wanted to enter simulation mode.
It did analysis of those files too.
Although it was a little harder, the reading in of files would generally support values in the file out of order. They were just tags.