CP1585 booting issues

Ask Questions Controls & Vision
, ,
1

Hi B&R community! First time posting here :grimacing:

My team uses a X20CP1585s in our test panels. I update the code on them fairly frequency, direct transfer or offline transfers to other compact flash cards and then swapping cards on site. I’ve never had any issues with the CPUs booting until now. We have a new test panel, equipped with a CP1585, that I’m trying to set up but it seems like the CPU won’t boot.

The only LED status lights that come up are the CF (green) and DC (yellow/orange), according to the spec sheet CF just means the card is loaded and detected and DC means the power supply is ok. Neither R/E or S/E even blink. Every ~20ish seconds both the CF and DC LEDs turn off and then back on.

Any ideas what’s causing this or steps I can try to figure out what’s going on? I’ve re-flashed the card/tried a different card which didn’t help and I even tried a different CP1585 which is doing the exact same thing…

I’ve tried turning the dial into BOOT or DIAG mode and then turning on the CPU but got the exact same behavior

I haven’t had any success connecting via ethernet/automation studio either.

Let me know what I should try :upside_down_face:

Thanks folks!

2

Hello and welcome in the Community,

I’d create a new empty project with only the X20CP1585 in it, generate a CF card, plug it in the PLC and disconnect all I/Os if there are any. Basically follow this post.

3

Hello,

If the BOOT-Mode does not Work it is most likely an Hardware Failture and the PLC should be send to B&R Repair.
Testing the PLC without any external connection is a good idea, even without CF (Boot-Mode should be possible).

Greetings
Michael

4

Thanks folks, I appreciate the responses.

On Pavel’s point - I haven’t tried loading a blank program yet because I assumed the PLC should be able to enter BOOT or DAIG mode without the compact flash card even installed.

The fact that I have two X20CP1585s on hand that are showing identical ‘non-responsive’ behavior made it seem less like a hardware issue but I suppose it is possible they both could be damaged.