I am looking to establish communication between a Delta HMI DOP-107EV and a Mitsubishi FX3G PLC. The issue lies in the fact that the Delta HMI only has RS485 and RS232 ports, while the FX3G has RS422. Can a RS232 to RS422 converter be utilized to facilitate this communication? If so, what adjustments need to be made to the communication settings in DopSoft for this setup?
If you haven't had the chance to try it with a Delta HMI, consider using the SC09 232/422 cable typically used for programming. This should be effective, although be aware that when the PLC is re-booted or powered up, the programming port will revert to the default settings of 9600 baud rate, Even.7, 1. Some HMIs have the capability to switch the PLC to alternative formats like Beijers, but not many. It is recommended to stick with the default baud rate, or alternatively, consider obtaining a 232 BD add-on board that can be configured to the default programming protocol.
This programmable logic controller (PLC) features front-facing modules at an affordable price point. With the FX3G-232-BD, you can easily access RS232 directly from the PLC, while the FC3G-485-BD offers RS485 connectivity. These modules provide cost-effective solutions for integrating communication protocols into your automation system.
Hello everyone, thank you for the response. Currently, I have successfully set up communication between my PC and PLC using a USB to RS422 cable. The DOPSoft simulation is functioning well. Next, I plan to test the setup with a real DOP HMI 107EV using an RS232 TO RS422 cable. If the connection does not work with the RS232 TO RS422 cable, I will consider using modules for communication.
Hello everyone, I appreciate the response. Currently, the setup is functioning using a USB to RS422 cable connecting the PC to the PLC. The DopSoft simulation has been initiated and is performing well. Next, I plan to test it using an actual Dop HMI 107EV with an RS232 to RS422 cable. If the RS232 to RS422 cable does not yield the desired results, I will consider using modules.
Yes, you can definitely use a RS232-to-RS422 converter to establish the communication. Ensure that the baud rate, data bits, parity, and stop bits match on both ends. In DopSoft, you need to configure the COM port settings to match the PLC's. Also, remember to set the protocol to match the specific requirements of the Mitsubishi PLC. It can sometimes be tricky, though, so don't get discouraged if it doesn't work perfectly the first time.
Yes, you can definitely use an RS232 to RS422 converter to establish communication since it will accurately translate the signals between the Delta HMI and the Mitsubishi FX3G PLC. But keep in mind that proper setting up of the converter is crucial here. For DopSoft settings, you need to make sure the baud rate, stop bit, parity, and data bit match with the PLC settings. Also, remember to set the communication protocol to match with the PLC. Using a converter can sometimes introduce latency, but it's usually negligible for most applications.
Yes, an RS232 to RS422 converter should present a decent solution to your problem. In terms of the DopSoft settings, typically, the parameters you'd need to adjust would include the serial port (correlating to the location of the converter), baud rate, data bit, stop bit, and parity. Just make sure these settings match those of the FX3G PLC for seamless communication. Additionally, it would be advisable to check with the converter’s manufacturer for any specific configuration instructions to ensure accurate data transmission.
Yes, you can use an RS232 to RS422 converter to bridge the communication between your Delta HMI and Mitsubishi FX3G. The converter will serve as a middle ground to adapt the signalling between the two protocols effectively. For the settings in DopSoft, consider adjusting the baud rate, data bit, stop bit, parity, and the slave ID to match with your PLC and ensure successful communication. It might take a bit of trial and error, but the key is to be consistent with your PLC and HMI settings.
Yes, you can definitely use an RS232 to RS422 converter to establish communication between the Delta HMI and the Mitsubishi FX3G PLC. Just make sure to configure the baud rate, parity, stop bits, and data bits to match on both devices—this is crucial for successful communication. In DopSoft, you’ll want to select the appropriate serial port settings that correspond to the settings on the PLC side. Additionally, pay attention to the wiring configuration; since RS422 can have differential signaling, ensure the connections are made properly to avoid any signal issues. Good luck with your setup!
Yes, you can definitely use an RS232 to RS422 converter to facilitate communication between your Delta HMI and Mitsubishi FX3G PLC, as these converters handle the necessary signal level adjustments. When configuring DopSoft, you'll need to set the communication parameters (baud rate, parity, data bits, and stop bits) to match the settings on the FX3G PLC. Also, make sure that the converter's settings match the requirements of both devices; sometimes dip switches on the converter may need to be adjusted. Lastly, double-check the wiring to ensure that you're connecting the correct pins, as RS232 and RS422 have different pinouts.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: 1. Can I connect a Mitsubishi FX3G PLC with a Delta DOP-107EV HMI using a RS232 to RS422 converter? - Yes, you can use a RS232 to RS422 converter to establish communication between the Delta HMI DOP-107EV and the Mitsubishi FX3G PLC.
Answer: - The Delta HMI DOP-107EV has RS485 and RS232 ports.
Answer: - The Mitsubishi FX3G PLC has a RS422 port.
Answer: - Specific adjustments may vary, but typically you will need to configure the communication settings in DopSoft to match the protocol and baud rate of the converter.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.