Seeking advice on instrument communication issues

It’s fine to talk about it in general terms – it’s about configuration software and 485 communication between instruments. If such instruments aren’t available in the configuration software, how can communication between the two parties be established based on the communication protocol?

The engineering configuration software I am working on uses ForceControl, and it needs to communicate with Tianyi’s integrator devices. These devices have 485 communication ports, and the communication protocol specified is SLF-30. What exactly needs to be done in order to establish this communication? How to set it in force control? I’ve never heard of its communication protocol SLF-30; it might be a proprietary protocol developed by the manufacturer. If the configuration software does not support it, that will be quite troublesome. You need to take a close look at the specific details of its communication protocol, such as the communication rate, data bits, stop bits, parity checking, data verification algorithm (whether it is CRC or LRC, etc.), and the specific command codes. Then write a communication program in C language by yourself and embed it in the configuration software. . . Of course, if there’s money available, it can also be done by someone with expertise in force control. Hehe!

In the force control software, it is necessary to add the driver for the corresponding model of instrument. Do you have a driver for Tianyi’s integrator?

The wiring must be correct, and communication interface parameters such as the baud rate should be set in accordance with the requirements of the instrument; communication takes place based on the communication protocol.

In ForceControl, there is no driver for such instruments; I am trying to develop one on my own (using the driver development kit provided by ForceControl), and it seems quite complicated. Are there any other alternative methods for communication?

I’ve never heard of the SLF-30 protocol; I called the manufacturer. If it’s MODBUS/RTU, as long as the address, baud rate, data bits, stop bits, and parity settings are configured so that the parameters of the master and slave devices match, communication should work without issues.

There is no other way; in fact, there are quite a number of instruments that support force control. If one wants to develop such instruments on their own, it is necessary to obtain the specific details of the SLF-30 communication protocol from the manufacturer. Summary: Fieldbus interfaces such as PROFIBUS, MODBUS, CAN 422/485, industrial Ethernet, and other communication-related information can be found at http://bbs.hcbbs.com/viewthread.php?tid=27&highlight=%CD%A8%D1%B6. This should be useful to you!

Force control software usually comes with drivers from well-known brands. Devices like celestial instruments certainly don’t have a drive mechanism, but the RS485 protocol can be programmed using VB or C languages; personally, I think VB is the better choice

This is really useful, thank you so much. But most of them are theoretical in nature. This post was last edited by lzhlchy on 2009-3-4 15:59.]

If the instrument manufacturers refuse to cooperate and do not disclose their internal addresses, I doubt it will work. Give it a try; if it works, please let me know. Thank you.

Simply put, you can ask the manufacturer for the rules for drafting such agreements, and then write them in C language yourself. And if you are using a Siemens 200 PLC, then you can take advantage of its free port communication, which makes things less complicated.

Thank you all for your help. I hope everyone will keep speaking, because I’ve seen former colleagues do it – it’s a pretty simple method, but I can no longer get in touch with them.