Hello everyone, I am currently using an FX3U series PLC that comes with a built-in RS422 port and a USB-SC09-FX cable. I am trying to establish communication between my PC and the PLC using a HyperTerminal-like application. Despite confirming that the cable works fine when loading ladder programs from GX Works 2 to the PLC and when reading back, I am experiencing difficulties in communicating with the PLC. I have followed a simple ladder program example provided in the PLC manual for RS instruction with non-protocol communication. I have checked the baud rate and other relevant settings, but I have not been able to find a solution. Your assistance in resolving this issue would be greatly appreciated.
The RS command is not compatible with the Programming port.
I greatly appreciate your assistance. I was facing difficulties with this issue. Can anyone advise on which specific command is effective in resolving this problem?
The programming port protocol lacks documentation, but there may be code available in languages like VB or C that has been tested. Alternatively, installing the 232 BD board offers both straightforward 232 communications and programming capabilities.
I am unable to add any modules at the moment, but I came across a commercial automation system that utilizes the built-in port for programming and SCADA. Although the PLC is not exactly the FX3U-64 model, it belongs to the FX series. Parky, could you please direct me to those implementations in VB or C?
I am currently facing issues with a computer link dedicated protocol. Upon sending a message from the hyperterminal, I am receiving a NAK 15H response. Does this indicate progress towards establishing a connection? Can we infer that the PLC is responding? I must persist in troubleshooting this issue, as acquiring even a basic external communication module seems to be a challenging task.
It sounds like you've double-checked all the obvious things. One thing you might want to consider is the terminal software you're using. HyperTerminal has been known to have some compatibility issues with certain PLCs. What I might suggest is try using alternative software like PuTTY or RealTerm. Both are free and widely used in the industry. Also, ensure the communication parameters in the PLC exactly match those in your terminal software. Any little mismatch can lead to communication difficulties. Don't forget to verify elements like parity and stop bits. Good luck with your troubleshooting!
Hey there! Given that you've successfully loaded programs using GX Works 2, it indicates your PLC-to-PC connection is functioning correctly. Your issue might be with the communication settings in your HyperTerminal-like application. Are you sure that the communication parameters in your HyperTerminal (such as baud rate, data bits, stop bits, parity, and flow control) exactly match those configured in your PLC communication settings? If there's a mismatch, this could well be the root of your issue. Another thing to look at may be the program you're using in the PLC for communication. Make sure that it's designed to communicate on the channel you're attempting to use and that it's not producing any errors when run. Good luck!
Hey there, it seems you're battling with a tricky issue. First, ensure your cable is correctly wired for RS422 communication. The FX series PLC uses 2-wire RS422 (A, B) and not 4-wire which is more common (TX+, TX-, RX+, RX-). A common mistake is miswiring the A and B cables. Secondly, make sure you're using the right tool for non-protocol communication. GX Works 2 might not work for your case, so you may need to use a tool like GX Developer instead. If all that checks out, look for any advanced settings or features that your HyperTerminal-like app might have, sometimes it's an overlooked setting that's causing the issue. Best of luck!
It sounds like you’ve done a thorough job checking your setup, but sometimes communication issues can be tricky. Have you confirmed that the settings in your HyperTerminal-like application match those of the PLC exactly, including the data bits, stop bits, and parity? Also, consider whether your RS422 cable might have any specific pin configuration requirements, as that can sometimes lead to communication issues even if the cable is functioning in other scenarios. If possible, trying a different terminal program could also help isolate the issue. Good luck!
✅ 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: - Communication issues can arise due to various reasons such as incorrect baud rate settings, cable connection problems, software configuration errors, or incompatible communication protocols.
Answer: - Start by verifying the cable connection, ensuring the correct settings for baud rate, data bits, stop bits, and parity are configured on both the PC and PLC sides. Check for any software conflicts and ensure the communication protocol is supported by both devices.
Answer: - Ensure the USB-SC09-FX cable is securely connected to both the PC and PLC. Double-check the communication settings in both devices, including the correct COM port, baud rate, and protocol. Update drivers if necessary and consider testing communication using alternative software tools.
Answer: - Loading ladder programs may require a different communication setup compared to establishing real-time communication. Verify that the settings used for program loading are also suitable for general communication tasks and consider consulting the PLC manual for specific communication requirements.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.