Hi,

With the S7-1200 Wireless Signaling and Switching Set 32 (thanks Siemens) I’m onlyusingthe SMS Receiving function what is working very fine; the modem is always connected and receiving SMS.

But sometimes after a few hours or days the T_CON function returns always the same 8030 error code what means the ID is already used by another connection. (There is only one connection and -like descripted in the manual- the Set 32 does not call TC_DISCON when the TC-CON returns an error).

It doesn’t happen often; maybe the modem cannottemporaryconnect to the GSM provider... But the problem is I cannot automatically delete this error, when I restart the TC_CON the error is always coming back.So I need to Stop-Run the CPU and then the modem can connect immediately again with a provider and works correctly again for a few hours or days.

My question is why it is not possible to reset this error and is there another way to ev. reset the modem without make an stop-run of the CPU.

Thanks and best regards

Hi,

few questions/suggestions here:

1. Are you sure you don't trigger the "REQ" of the TC_CON block while it is still connected?
2. You might want to use the TC_DISCON to clear the (logical)connection ID and then connect again when this error apears.

The reason for not resetting the status code might be due to ongoing connection attempts while the ID ist still blocked. Again: check your "REQ".

Hope this helps.

Hello Owie and Kaulquappe,

Nice to you that you replied.

It is the first time that I use TC_CON/RECV/DISCON functions and therefore I use the nice Set32 that Siemens put available on their site.

That example Set32 is working with steps and only one step is valid at a time. Like you see in network 5 (see annexed, I hope this upload is allowed), when the TCON block reports an error (Step 3) TDISCON is not executed because TDISCON himself has a problem… and then like you write, TCON try again to connect and make error.

I was thinking that a Siemens Set 32 was ready to play, maybe it is necessary to put the general #REC input of the FB as a negative condition before the TDISCON to be sure that he will really (tried) disconnected.

Thanks and best regards

Perreke

Hello Owie and Kaulquappe,

Nice to you that you replied.

It is the first time that I use TC_CON/RECV/DISCON functions and therefore I use the nice Set32 that Siemens put available on their site.

That example Set32 is working with steps and only one step is valid at a time. Like you see in network 5 (see annexed, I hope this upload is allowed), when the TCON block reports an error (Step 3) TDISCON is not executed because TDISCON himself has a problem… and then like you write, TCON try again to connect and make error.

I was thinking that a Siemens Set 32 was ready to play, maybe it is necessary to put the general #REC input of the FB as a negative condition before the TDISCON to be sure that he will really (tried) disconnected.

Thanks and best regards

Perreke

(There is only one connection and -like descripted in the manual- the Set 32 does not call TC_DISCON when the TC-CON returns an error).

You’re right Sprawl, I didn’t read it in the Set32 manual but I read it in the manual S7-1200 Telecontrol CP 1242-7 version 08/2013 chapter 6.4.2: "Do not call up TC_DISCON if TC_CON indicates Error=1"

The CP 1242-7 has actually firmware 1.3.0. I uploaded to the latest firmware 1.3.6 like described in ID 86219570. The upload procedure had worked exactly like described in the ID, but in on-line diagnostics off the modem in TIA V12 SP1 I see that the modem stayed on 1.3.0… ?