I have encountered a "COMM ERROR: 0x41" while attempting to control a Cloned FX3U PLC using SKTOOL 6.2 software. Despite trying various solutions such as using different PLCs, including an original Japanese-made Mitsubishi FX2N PLC, upgrading to Sktool 7.0, switching to a Windows XP machine, testing different USB to serial converter cables, and experimenting with various software programs, the issue persists. I am unsure of the root cause of this problem, let alone how to resolve it. Any assistance you can provide would be greatly valued.
Are you familiar with the interpretation of the error code?
Steve Bailey asked, "Are you familiar with the error code's meaning?" He expressed uncertainty about the issue, noting that the PLC can still be managed in monitor mode through GXworks 2 software. This suggests that the problem may not lie in communication. Additionally, he pointed out a message in the image saying "ERROR INFO: READ." Does this information prompt any insights or solutions to the issue at hand?
The baud rate for communication varies depending on the clones being used. While some clones are limited to 38400, genuine FX models can operate at speeds ranging from 9600 to 115000, with a default setting of 9600 upon startup. Beijers HMI's and Mitsubishi GXDev, GXworks have the capability to adjust the baud rate to your desired setting. However, there may be limitations with certain HMI's that do not allow for this customization. This was discovered when connecting a data capture system to an FX3U, where it initially worked at 115000 but later failed to communicate. Resetting it to 9600 resolved the issue. It seems that in some cases, if the system loses power, it defaults back to 9600 baud rate. Clones typically operate at 38400 baud rate, as tested with a Beijers HMI. If encountering issues, try connecting with GXDev or another Mitsubishi IDE to verify the baud rate and other settings without turning off the PLC.
The error message indicates a real-time reading failure due to the lack of data being received in response to a request. In other words, even though a request has been sent, no reply is being received.
It is important to verify if the communication settings on Channel 1 (CH1) PLC parameters align with the communication settings on your Human Machine Interface (HMI), including speed, bits, and parity. A possible issue could also be related to the cable. Mitsubishi tends to use custom pinouts for RS232, RS422, and RS485 connections.
It sounds like you've really covered a lot of ground trying to troubleshoot that COMM ERROR: 0x41 issue! One thing to consider is to double-check the communication settings like baud rate, parity, and stop bits in both your PLC and SKTOOL; sometimes, a mismatch can cause these kinds of errors. If everything looks correct, maybe try replacing the serial cable once more or testing with a different USB port or PC, just in case there’s a subtle hardware issue. It could also be worth looking into the PLC’s firmware version, as certain combinations of hardware and software can lead to compatibility problems. Good luck, and I hope you get it sorted out soon!
It sounds like you've already done quite a bit of troubleshooting! Since you've already swapped out PLCs and upgraded software, have you checked the communication settings in SKTOOL to make sure they're matched with your PLC's configuration? Sometimes even a small error in the baud rate or stop bits can lead to communication errors like this. Also, if possible, try using a different machine or operating system to rule out any compatibility issues with Windows XP. If none of that works, it might be worth reaching out to forums specific to Mitsubishi PLCs; there could be others who have faced similar issues and found a unique workaround. 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: 1. What does the "COMM ERROR: 0x41" indicate in the context of SKTOOL and Cloned FX3U PLC communication? - The "COMM ERROR: 0x41" typically signifies a communication error between SKTOOL software and the Cloned FX3U PLC.
Answer: - Various solutions have been tried, including using different PLCs, upgrading SKTOOL software, changing the operating system to Windows XP, testing different USB to serial converter cables, and experimenting with different software programs.
Answer: - The problem persisted even after switching to an original Japanese-made Mitsubishi FX2N PLC, suggesting that the issue may not be specific to the Cloned FX3U PLC.
Answer: - The root cause of the "COMM ERROR: 0x41" issue has not been identified yet, making it challenging to determine a definitive solution.
Answer: - Seeking help from technical support, forums, or contacting the software or hardware manufacturer for guidance could be beneficial in addressing the communication error.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.