I am experiencing difficulties with the PCM301 as it fails to start after downloading and running the PLC program. While the work LED Indicator "OK" is visible on the PCM, the LEDS Us1 and US2 do not start flashing. This issue occurred despite the successful operation of the same project on the same PLC a year ago, when it was resolved by a different engineer. Now, when I initiate the PLC in Run mode, I encounter fault loc 0.2 with the message "comm req bad task ID program." How can this problem be resolved?
When troubleshooting a PLC issue, it is important to consider various factors. One possibility to explore is whether the program was downloaded due to a prolonged power outage leading to a dead battery. It is crucial to ensure that both the program and hardware configuration are downloaded to prevent loss of data in such cases. Additionally, the PCM module's communication is essential to consider, as its program is also battery-powered for maintenance.
The last project in the PLC failed due to discharged batteries in the PWR and PCM slots, resulting in a power outage for some time. To resolve the issue, the engineer utilized a similar project from the same system, which worked for approximately 10 months. The engineer's process involved leaving the system without power and batteries overnight, disconnecting the unit from all connectors except for power and batteries, and then downloading the project to the controller to restart everything. However, it appears that the engineer may have missed downloading certain items such as hardware configuration, motion/logic settings, and initial force values. Currently facing a similar issue, although the batteries are in good condition, the PCM battery was disconnected upon diagnosis leading to the PLC malfunctioning. Regarding the PCM, it communicates with two converters KD485 (RS232/RS422) for data transmission and control panel operation. After connecting with the PCM, all necessary points were downloaded. There were no errors or warnings in the feedback zone, only in the diagnostics section. Using PME 7.0 with a firmware version of CPU350 at 10.74, built 23A1, it is likely that the previous engineer also used the same PME version. Despite this, there may be a mistake as the COMMREQ functional block cannot be found in the target during troubleshooting.
I am currently in the process of preparing some visuals, which may provide additional insight and details.
The PCM module operates a Megabasic program that was lost due to a drained battery and must be re-downloaded. This can be achieved through a serial connection using a terminal emulator program such as Hyperterminal. It is possible that the program was initially created using an add-on to Logicmaster software known as PCOP. To successfully configure the PCM module in the PLC hardware settings, a file named "UCDF.cdf" is required in addition to the Megabasic program. There are two modules in your setup that may utilize the COMMREQ instruction - the PCM module and the High Speed Counter module. If permitted by your company, feel free to share your PME project file for assistance with the COMMREQ issue. If privacy is a concern, send me a direct message for an alternative method of file sharing. At this point in troubleshooting, it is not necessary to focus on the memory allocation screen. The screen indicates that firmware version 9 or higher is needed for memory reallocation, whereas your version 7 firmware is restricted to the address ranges displayed on the screen. It is unlikely that the original programmer attempted to adjust the address limits.
Is it possible to download the emulator and connect it through the CPU? To download the PC software, I typically utilize a USB port along with a 485 converter to establish a connection to the CPU. How can I obtain the "UCDF.cdf" file? Alternatively, can I request to collect samples using a comparable system, similar to what was done with the PLC project? I am using windows 10 for these tasks - does Hyperterminal offer support for this operating system? Apologies for the multitude of inquiries.
This issue sounds related to a communication error in your PLC program. The error message "comm req bad task ID program" typically suggests a problem with the task identification somewhere in your communication setup. You might need to cross-verify the task ID in your PLC routines. One possible situation could be that your PLC is trying to execute a communication request to a task that doesn't exist or is currently inaccessible. Also, remember to check your device address settings, ensuring they match those in your PLC. In addition, if you recently updated your system or made software changes, do check for compatibility issues. It might be helpful to replicate the setup of the previous engineer who resolved this issue before, if those details are accessible.
It seems like the issue might be related to your PLC's communication setup. The fact that LEDS Us1 and US2 are not flashing could indicate a problem with your connection settings. Try to review your PLC's communication parameters and make sure they're properly set. Make sure to check the used communication port, baud rate, and its configuration (parities, stop bits etc). The error message you're receiving is commonly associated with these issues. If everything seems fine, try resetting your PLC or uploading the program again. Lastly, it might be a good call to reach out to the previous engineer for context if the problem persists.
It sounds like you're dealing with a frustrating situation! The "comm req bad task ID program" error usually indicates that the PLC is having trouble communicating with the program correctly. First, double-check that the program you're trying to run is properly loaded and that all task IDs and configurations match what the hardware expects, as sometimes updates or changes can lead to mismatches. If everything looks good on that end, it might be worth trying to reset the PLC and re-upload the program to see if that clears out any lingering issues. Additionally, reviewing any recent changes made in the software or firmware might provide some clues, as they can sometimes introduce compatibility problems. Good luck sorting it out!
It sounds like you're dealing with a frustrating issue! The "comm req bad task ID program" error suggests there might be a mismatch or corruption in the PLC program. First, double-check that the project you’re downloading matches the current configuration of the PCM301, as any changes in the task IDs or program structure since its last successful run could cause this. You might also want to try re-uploading the program from the PLC if you still have access to it. Lastly, ensure that all firmware and software are up to date, as compatibility issues can lead to these kinds of communication errors. 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: The issue with the PCM301 not starting could be due to various reasons such as incorrect program download, communication errors, faulty hardware components, or configuration settings.
Answer: Answer: The LEDS Us1 and Us2 not flashing could indicate a specific issue related to communication, task execution, or program functioning within the PLC system.
Answer: Answer: The fault loc 0.2 error message typically indicates a communication request issue with the task ID program. To resolve this, it is advisable to check the program configuration, task assignments, communication settings, and ensure proper program execution.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.