CPU224, flashing SF/DIAG and STOP lights

Hello, I have a S7 200 CPU224 which is flashing SF/DIAG and STOP lights.

I installed Microwin & SP9 V 4.0.9.25 into win 7

I use the USB - PPI  RS485 ( 2013) cable.

The cable shows as installed in WIN Device Manager and GREEN TX lights flash when I try to communicate with PLC

No RED RX lights.

Microwin reports error Communication timed out check port number, network address, baud rate and attached cable.

I have tried using the settings as per the manuals (2011) but cannot communicate with the PLC.

Help please.

------------------------------------------------------------------------------------------
Split from Step7 Microwin v4.0 SP9 Windows 7.

Hello,

as it looks your PG/PC interface PC/PPI to Microwin looks ok (TX Flash). Don't know what settings you have tested, in PG/PC properties in Local Connection -> USB, in PPI Station parameters Address -> 0, Timeout ->1, in Network parameters for first uncheck both Advanced PPI and multiple master network, transmission rate 9600 (std), Highest station address ->31. Start tests with this settings. If not success, change transmission rate, test it. Last can be checked box Advanced PPI and again test from rate 9600 to end. If you discover some strange error atach printscreen.

Edit: you have only one CPU, not connected with other?

Edit: pls can you specify full type CPU? S7............-0X..............   maybe CN?

Hello,

The settings are as follows:-

COM port 6 ( same as Device Manager )

Interface Parameter PC/PCI Cable

Local0

Remote 2

Protocol PPI

Mode 11 Bit highest HSA 126

Baud Rate search all

PLC is removed from cabinet and on the bench with power supply ( lights still flashing )

Full type is 214-18D23-OXBB     S7 200 CN

Hello,

you are using USB converter simulate COM port? Show picture of that converter. When you look at PG/PC interface, which protocol do you select ... PC-PPI cable(PPI)? Look at my posts before, what was my problem I can't communicate with converters (RS-485) on Win7 with simulated COM port! What is that (2013) from your converter name? CN mean China brand, try find in forum about CN CPUs, never used by me. Pls answer to all my questions and post picture of that converter.

Edit: now I remeber that I've solved taht problem on Win XP SP3, there that my own build converter works, on XP was not problem with COM port functionality.

Hi.

We use USB to RS232 serial converters without issue.. but getting the right type that works with the S7-200 program cable is a problematic.

I have a feeling the PLC is damaged and will not communicate with the PC. Is there anyway that we can confirm that the PLC is still able to communicate? For example.. was it connected to a HMI before and can it still link to it.

Also.. Is it possible to check the PC to PLC communication on a PLC that is working correctly... now we have two issues colliding - possible damaged PLC vs possible PC communication problems.

Your thought on the matter?
w

Hello brewmaster,

can you check that settings in PG/PC interface? If you can, try connect to that China on Win XP SP3, as I said, that old system Siemens PPI cables was only pure RS485 converters, I got one original, this isn't multimaster converter, can working only on Win XP, this was my problem. It only send reuests to CPU, but no responds. Give info pls about that lights on CPU, are blinking or still light?

brewmaster22

Hello William,

The PPI cable was specified and supplied by a company who sell, program and repair PLCs so I cannot comment on whether it is the right one.

I spoke to a Siemens Engineer who told me the PLC is quite rugged and usually it is the touch screen which is damaged before the PLC. Ours is not damaged.

He also said the SF system fail light indicates the program failed either due to program corruption or failure of the attached equipment.. We suspect program corruption because the day before it over ran a temperature limit.

We do not have any other PLCs to run tests on.

Agreed that the PLC is more rugged than the HMI.

The SF lamp indicating program failure?... I have doubt in that.
My "feeling" tells me you have an internal power supply issue.
But then again my "feeling" may be wrong.

To get all the elements to work in harmony on a Windows 7 machine to be able to communicate with the S7-200 PLC can be tricky. Without knowing if the PLC communication is okay, will always leave room for doubt.

Perhaps let  <Duris_I>  or someone help you through the cable settings and see where it leads to. Please make screen captures of all the configuration settings you are using to set up your system to have your PC talk to the PLC. Photos of all the hardware with dip switches and serial numbers will go a far way too.

Please remember this forum is users helping users. If you prefer  <professional support>  help, come in contact with Siemens directly.

Sorry for not being more helpful - - good luck!
w

Hello Duris,

Yes you are correct in your understanding of the settings.

Siemens Engineer told me the CN means it can be programmed with simplified Chinese characters otherwise it is a standard 200. It is not different.

2013 is the design date for the adapter. It  clearly supercedes drivers before October 2011 which is Siemens date for Win XP drivers. I think this means it needs a Win 7 driver. I tried it on Win XP but cannot install the cable at all.

Hello,

agree with William, but in that case of OS I think that this converter must work under Win XP, but if this is only really pure RS485 converter, it can't be usable with CPUs 22X, only with that old CPUs 21X. I got my own 2 pcs, S7-215 DP (firmw. 1.02) and S7-216 (firmw. 1.0.1???). With  this old CPUs can make connection via pure RS485 converter without problem but only in Win XP, not in Win7. But with that newest CPUs 22X (your case) I need multimaster cable. I must buy that PC Adapter which incorporate old system of communication and new multimaster system in case of S7-200 connection. In this your case probably this isn't multimaster cable, can you this info confirm? If not, no chance to connect to that CPUs 22X probably. Give info.