Hello, I am currently facing difficulties in establishing communication with the Modicon TSX3721001 using the TSXcUSB485 cable I purchased from a Schneider distributor. Unfortunately, the distributor did not provide me with the necessary drivers on a CD. After downloading the drivers from the internet, I was able to resolve the driver issue, and the cable is now displaying as healthy in the device manager. I am operating on a Windows XP SP3 Virtual Machine and attempting to connect to the PLC through this virtual environment. Despite successfully establishing a connection, I encounter an error message stating "No remote ACK in function net_query! Stay connected?" When I select yes, the error reappears after a few seconds. If I choose no, the communication is lost. I am utilizing PL7 PRO V4.4 for the PLC, but unfortunately, I am unable to establish communication from there as well. I have been experiencing this issue for the past two days and would greatly appreciate any assistance in resolving it. Please refer to the attached files for the settings and error message snapshot. Thank you.
To troubleshoot the issue, begin by identifying the problem areas. Can you establish communication between the computer and another device via the serial port? Try connecting a different computer and using Windows HyperTerminal to see if there is any data transmission through the port. For more detailed guidance on PLC programming software tools, visit accautomation.ca/three-free-plc-programming-software-tools/. Have you attempted using a different computer for testing purposes? These are just a few suggestions to consider. Thank you.
The parity settings on your Windows port are currently set to none, but they should be set to odd for optimal performance. Additionally, it is unusual that the Unitelway setup does not display the cable part number next to the selected COM port. Have you made sure to configure the settings in the Unitelway setup for the driver to perform a reset as needed? See the image for reference.
Hello Chud, I recently switched the parity to Odd, but unfortunately, the issue still persists. In an attempt to resolve the problem, a friend suggested that I try communicating through a physical machine instead of a virtual one. I set up a desktop with Windows XP for this purpose, but encountered the same error message. I'm also intrigued by your mention of the cable name appearing alongside the COM port, which isn't happening in my situation. Could this indicate a problem with the installed driver? What steps do you recommend I take to troubleshoot and resolve this issue? Looking forward to your guidance on this matter.
Today, I successfully established communication with the PLC, uploaded the program, and accessed it online. My initial issue stemmed from difficulties with the USB and Unitelway drivers. I reached out to local support from Schneider, explained the problem, and requested links for the drivers to verify. Despite previously downloading the drivers from Schneider's official website, they were not working as expected. For those facing a similar issue, I have included links to the latest driver versions below: 1. https://schneider-electric.box.com/s/9wtvr55xz5f5ao0ney74zsnh55t1lsi0 2. https://schneider-electric.box.com/s/jyf6f6gma6vcl0blbttnugwl8a6ty2r1 Moreover, I successfully communicated using a dedicated system running Windows XP SP3 without the need for a virtual machine. After installing the driver successfully, you will see the TSXC485USB listed in the driver manager alongside the selected COM port, as mentioned by CHUD. I plan to test the new drivers on a virtual machine and share my findings.
Hello, could you please tell me the correct position for the TSXC485USB converter? (Perhaps facing directly?) Thank you for your help.
Hello! It appears you've checked all the obvious culprits like driver issues or cable health, which is great. However, sometimes this type of issue can arise due to a mismatch in the COM Port settings in both your system device manager and your PL7 PRO V4.4 configuration. Check to make sure they correspond. Also, you could try reducing the communication speed in your software settings, as a too high speed sometimes creates issues in establishing or maintaining a connection. Hope this helps and do please let us know if the issue persists!
Hey there, I've encountered a similar issue before and it typically arises because of Windows XP SP3's limitations and compatibility issues with the newer USB driver. You might want to try running it on a newer version of Windows, if possible. As for the "No remote ACK in function net_query" error, it could be due to improper timeout settings or issues with the network link between the PC and the PLC, and not just a driver problem. I would recommend double checking those network settings and try tweaking them a bit to see if that helps. Consider checking another forum member's post here about using PL7 PRO V4.4 on a Windows XP SP3 environment, it might provide you with more insights.
It sounds like you're dealing with a tricky situation here. From my experience, such issues can sometimes be related to latency or timing issues due to operating through a virtual machine. If possible, you might want to try direct connection using a physical machine. As for the "No remote ACK" error, it generally implies that your PLC is not confirming received commands, which may be due to incorrect addressing or an issue with your communication settings. Make sure your PLC's Unit-ID matches with the one in your PL7 Pro settings. I would also advise checking your baud rate, stop bits, and parity settings to ensure they match exactly with your PLC's.
It sounds frustrating to deal with connection issues like that, especially with an older operating system like Windows XP. Have you checked if the virtual machine’s port settings are correctly configured to link with the TSXcUSB485 cable? Sometimes, ensuring that the right COM port is selected in both the VM settings and PL7 PRO can make a huge difference. Also, it might be worth trying a different USB port or cable if you have one available, just to rule out any physical connection issues. Good luck, and I hope you sort it out soon!
It sounds like you're facing a frustrating situation with the Modicon PLC setup. Since you're operating on a Windows XP Virtual Machine, make sure that the COM port settings in your VM and the PL7 PRO software match the settings for the TSXcUSB485 cable. Sometimes, conflicts can arise if there are mismatches, so double-check the bitrate, parity, and stop bits. Additionally, have you tried running the software in compatibility mode or as an administrator? Those options can sometimes resolve communication issues. If all else fails, consider reaching out to Schneider's support directly—they might have specific insights or newer drivers that could help. 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: Answer: This error could indicate a communication problem between the software and the PLC. Ensure that the settings in your communication software match the settings of the PLC and the cable. Double-check the cable connections and try restarting both the software and the PLC.
Answer: Answer: Ensure that the necessary drivers for the TSXcUSB485 cable are correctly installed on the virtual machine. Check the compatibility of the drivers with Windows XP SP3. You may also want to consider using a different operating system or a physical machine for communication with the PLC.
Answer: Answer: Make sure that the settings in PL7 PRO V4.4 match the communication settings of the PLC. Verify the cable connections and ensure that the software has the correct permissions to communicate with the PLC. You may also want to try restarting the software and the PLC to see if that resolves the issue.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.