The Truth About ASCII Protocols in 2022

Let’s be truthful. The whole world is talking about Smart Manufacturing, Industry 4.0, AWS, OPC UA and all that other stuff but not everyone is using those technologies. Those of us in the real world know that there are tons of older products in the marketplace that we are still using today that doesn’t have all that stuff. And truth is, WE STILL NEED TO USE THOSE OLD PRODUCTS.
Lots of old products still have an old RS485 or RS232 ASCII protocol. It might be that the product is just so old that the software for it doesn’t exist anymore. I know of one company that lost the software for 75 of their old products on a server upgrade so they can’t support anything new. But it might also be the case that the 485 protocol just works fine. There’s just no good reason to use something else.
But if you have some old command response product or you’re the manufacturer of some old product using command response, RTA can help you. We can take that old product and make it look like an EtherNet/IP adapter, a Modbus TCP Server or a Profinet end device or even an OPC UA server. Lots of options for you.
Give one of our application engineers a call on 262-436-9299 or leave your contact information here and an application engineer will get back to you: www.rtautomati...

[@fredsoda3034]

0:55 sounds like you wanted to say something else hahahaha

[@alonsohdzf]

I noticed that too 😂😂

[@SolidStateSoul]

Crazy they wrote a custom protocol back then, instead of using oldschool standard protocols like modbus or bacnet.

[@jucerago]

I have a Eagle volume corrector xartu1 and I'm not able to communicate with its protocol, It's not modbus I imagine, it only make answer when I write ascci commands but I don't know what protocol they use.