You'll need more than just what you've shown in your basic VI. I'd say it is 10 times more difficult to get this set up. It is the more difficult way to handle the communications. So the IP address in there of 10.92.56.38 is your PC's IP address? In which case this device does want to be the master and wants your PC to be the slave. It is the web portal to configure the communication module ( ) Is that software on the PC that is getting data from the Communication module? Or is that software that is to configure the communication module? It is also very likely there would be multiple modules out there and thus there would be multiple slaves. Is that software on the PC that is getting data from the Communication module? Or is that software that is to configure the communication the PC would be a master, the device is the slave. That is two different communication paths. The right side of it is talking to the PC using Modbus. But the left side of it is talking out to a heat pump on the CAN bus. I will check with him if there is way to set the comm. Maybe I didn't understand what you meant by that. In our case there is only one communication module. You can reverse those roles between the "master" and the PC, but that usually means the PC needs a service running on it, or a "daemon", that is constantly running waiting for the the "master" to send the data to the PC would be a master, the device is the slave. Server is roughly equivalent to the Slave, it is the one that hold the data and "serves" the data back to the client upon request. But the Client is roughly equivalent to Master, it is the one that does the data requesting. I find those terms make it harder to know which is in control and which is the responder. Your VI shows you are using Modbus TCP/IP. The names Master/Slave typically apply to serial communication. One other thing to throw in on terminology. So that "Master" in the middle would be the master to the CAN bus, but the slave to the Modbus bus. Typically, the PC would be the master and the device gathering the data, like Steven says, would be the slave. The Modbus comms are a different communication bus. That communications module called "Master", might be the master for the CAN bus. It's possible that from your picture, you have two different Bus communications going on and that changes things. Normally the PC would be a master, the device is the slave. It's possible that this person screwed up this terminology, or perhaps the actual implementation. Spoke to the person who will program this communication module today and he said that module is the Master (and cannot be changed).
0 Comments
Leave a Reply. |