E14 Community recommendation for ModBus TCP client

I'll necro post.
pymodbus tcp typically does fine.
My boss showed me another library recently that seems to work well... bu t I forgot what it is called.
typicaly, I start with a register map, then build out functions from there. dealing with modbus kinda sucks.
I typicaly build lists, or arrays, while my co-workers seem to like json files. thats a design choice, I favor application development, 
where they favor web development, though either could work. 

A specific application? lol IDK about that, I would just write it. 

out of curiosity, its that a touch screen? is button IO writable?
can you push (load) different screens remotely?
what is the display graphics programed in?
are there other interfaces for programing the display?

Screen is touch, that is about the extent of my knowledge.

It has network capabilities but we currently are not using it. The objective is to extract the scale data and move it to our ERP system.

ah sorry to hear thats not done yet. 
cms-prod.ricelake.com/media/yj4d03hi/m_156782_1280_modbustcp_enus_revh.pdf
that has a register map / controls / command list.  page 13 and on.
Ill look at making you a test script this evening maybe. 
if in between, now, and then, you say a little more detail about the steps in the process, like 
how the process goes, I can try to blast out a test script to get you your data.
what happens after that , where it goes, will be up to you.

I have a poor relationship with the vendor. When you: make promises and don't deliver. Make mistakes and not own up to them. Make mistakes and blame someone else. My patience wears thin. 

I explained to the owners that it is not a good idea for me to deal directly with the vendor. It will not be good for their relationship. I am only part-time. They need to vendor long after I am gone.

I can call out two or three times where the vendor has had issues and immediately suggested it was something on our end. At one point I released some scripts to track network performance. The scripts discovered a security hole, they said was never there. Eight hours after giving them my data to prove our network performance was not the issue my scripts failed. They fixed the security hole that never existed. No word said.

There was one line in the scope of work incorporating the modbus interface. Nothing more. The implementation of the ERP system has taken way longer than originally planned. The modbus interface is one of the final pieces.

At first they wanted the scales to port flap on the edge of the network. Not happening on my watch. Through the jigs and reels they settled on OpenVPN. Between the dev environment (my home basement) and production environment I established the OpenVPN connection, the firewall and the routing to fully test the environment for the scales. It works. Thanks in part to the help from E14 community.

The vendor doesn't use OpenVPN in their dev environment. I had to create last minute L2TP VPN tunnel so they could do development work on the scales. They struggled with that. Frustrated that password and secrets were not sent in emails but secure links. They had never worked with the scale before. They continuously told me in emails OpenVPN would not work. It was unstable, prone to resets. I assured them it was working and stable.

They requested all my documentation before they would start development. Like me, when I began this post, I believe they didn't have any knowledge of modbus. 

I gave them a test procedure that I had developed. The software and the test tools provided them insight into what they needed to do. Three days after they started development they indicated the requirement for a PC.

I have little details on the PC re-design. I am also not looking to get involved because I truly believe I would own it. Today I'm established a test laptop in the environment. I working through all the issues to meet requirements to ensure the network remains secure.

I hope to turn over to them a PC that I know is on a good footing. Then we scrap over what they want changed to get it working.

I am biased. I have little confidence in the vendor. They are sweet as apple pie when they want something but will dump all over you when given the opportunity. Take what I says with a grain of salt.

I have a poor relationship with the vendor. When you: make promises and don't deliver. Make mistakes and not own up to them. Make mistakes and blame someone else. My patience wears thin. 

I explained to the owners that it is not a good idea for me to deal directly with the vendor. It will not be good for their relationship. I am only part-time. They need to vendor long after I am gone.

I can call out two or three times where the vendor has had issues and immediately suggested it was something on our end. At one point I released some scripts to track network performance. The scripts discovered a security hole, they said was never there. Eight hours after giving them my data to prove our network performance was not the issue my scripts failed. They fixed the security hole that never existed. No word said.

There was one line in the scope of work incorporating the modbus interface. Nothing more. The implementation of the ERP system has taken way longer than originally planned. The modbus interface is one of the final pieces.

At first they wanted the scales to port flap on the edge of the network. Not happening on my watch. Through the jigs and reels they settled on OpenVPN. Between the dev environment (my home basement) and production environment I established the OpenVPN connection, the firewall and the routing to fully test the environment for the scales. It works. Thanks in part to the help from E14 community.

The vendor doesn't use OpenVPN in their dev environment. I had to create last minute L2TP VPN tunnel so they could do development work on the scales. They struggled with that. Frustrated that password and secrets were not sent in emails but secure links. They had never worked with the scale before. They continuously told me in emails OpenVPN would not work. It was unstable, prone to resets. I assured them it was working and stable.

They requested all my documentation before they would start development. Like me, when I began this post, I believe they didn't have any knowledge of modbus. 

I gave them a test procedure that I had developed. The software and the test tools provided them insight into what they needed to do. Three days after they started development they indicated the requirement for a PC.

I have little details on the PC re-design. I am also not looking to get involved because I truly believe I would own it. Today I'm established a test laptop in the environment. I working through all the issues to meet requirements to ensure the network remains secure.

I hope to turn over to them a PC that I know is on a good footing. Then we scrap over what they want changed to get it working.

I am biased. I have little confidence in the vendor. They are sweet as apple pie when they want something but will dump all over you when given the opportunity. Take what I says with a grain of salt.