Hello:
Customer have one old machine with some X64.Now one X64 is defected, so they have to change it to one P64new.But now this one works abnormal. The error led works in “Single flash” and the STATUS led is constantly on.
This P64new is the first one after module IF1091, and its subsequent X64 can run normally. So the wiring is correct.
What other factors can cause the error light to single flash?
Thank you.
Hi Juncheng,
That error light is on the communication module for the drive rather than the drive itself. The 8I0IF109.400-2 is an X2X communication module, and you can see more information about the status LEDs here: LED status indicators.
A single flash on the Error LED indicates that the module is not communicating on the X2X network. I would suggest checking your wiring there and then seeing if you have any diagnostic information on the controller itself. Once the communication is working properly, I’d expect to see ModuleOk go true on the controller.
CP1382.logpkg (479.7 KB)
I think this is probably the issue:
The drive is configured as node 7 in Automation Studio but is actually node 13 on the X2X network. Assuming your wiring isn’t going to change, try dragging the drive to the node 13 spot in the Automation Studio Physical View, transfer, and power cycle (drive + PLC).
Hello Marcus:
There are 7 pcs inverter behind BT9100.And this P64new is the first module next to the BT9100.The customer is an end user and they do not have the source project for this machine.
This is a newly created empty project, and the hardware configuration is recognized by online identify.
Is there any configuration required for P64new to replace X64?
Thank you.
This is a little tricky without the SDM because I can’t tell what the software expects to see.
This is a newly created empty project, and the hardware configuration is recognized by online identify.
Does this mean that the node numbers in your screenshot may not actually match what was configured in the original Automation Studio project? If that’s the case, this is even trickier because I’m not sure what each node is supposed to be. The errors in the log are all related to Node 7. Do you know if the original project has a node 7? Based on your screenshot, there is no node 7 currently on the machine. But since there are only 6 drives, it could be that this new drive is node 7 and is just not communicating properly. What happens if you swap its position and say put it to the end of the communication chain? That could help you verify which node it actually is.
Another possibility is that the communication module is faulty. It’s hard to say that for sure, but if you have another drive you can temporarily swap out, you can see if that drive starts communicating right away.
Is there any configuration required for P64new to replace X64?
I haven’t personally replaced one of these before, but my understanding is that this can be a drop-in replacement in a lot of cases. That being said, the user manual lists some incompatibilities between the X64 and the P64new which would require software changes if certain features were used. Additionally, it’s always helpful to have an Automation Studio project so that you can diagnose communication issues like this one.
