Search the Community
Showing results for tags 'modbus tcp'.
Found 2 results
I set up a Modbus/TCP server (slave) to share a mix of user input values and values calculated from a combination of those user inputs and process value channel readings. That works well. Kudos on how easy it is to set that up! The user inputs don't change often, so I persist them across sessions. When starting DF again, the persisted values are displayed and used correctly in the calcs, but DF doesn't seem to want to respond with the persisted values to Modbus requests. If the requests include only the calculated values it works OK, but if they include the persisted values, and those have not yet been set during the session, DF fails to respond to the query. If I then set the user input values, DF will respond as expected to requests, even if they include the user values. As a workaround, I can probably push the persisted value back into the channel on startup, but why would it be doing this in the first place?
Hi, I'm using DaqFactory to control pumps, valves, etc. of a small biological reactor. And, I've also a transmitter box (Liquiline CM448, Endress&Hauser) measuring pH, T, etc. connected to the same computer via an ethernet cable. Unfortunately, I'm struggling reading the data from the transmitter box in DaqFactory. The communication protocol of the box is ethernet/IP. Does it mean that I have to create my own protocol to read the data? And how difficult is that? I'm quite familiar with DaqFactory, but I've now experience with communication protocols. Would it be easier via Modbus TCP? Endress&Hauser sells Modbus TCP licences for their transmitter boxes?