S7-300 Remote Download: TeleService and SINEMA RC Setup
Remotely downloading a modified STEP 7 logic to an S7-300 CPU315DP that sits behind a CP343-1 Lean on a customer network is a routine service task. The plant floor has neither an engineer on-site nor a permanent VPN back to the office, but the controller must be updated. This reference covers the three practical paths that survive the realities of the field: legacy TeleService over PSTN/ISDN, TeleService over the public Internet via TS Adapter IE, and modern SINEMA RC remote access. The procedures assume STEP 7 V5.6 for legacy TeleService or TIA Portal V18/V19 for the equivalent S7-300 routes.
1. Hardware and Software Inventory
Confirm the rack content before you plan the remote path. A CPU315DP (e.g., 6ES7 315-2AG10, 6ES7 315-2AH14, or 6ES7 315-2EH14) with firmware version 2.x or 3.x is the controller in the original requirement. The CP343-1 Lean (6GK7 343-1CX00-0XE0 or 6GK7 343-1CX10-0XE0) provides Industrial Ethernet connectivity on the backplane bus. Remote download needs at minimum:
- S7-300 CPU with one of: MPI/Profibus DP port, or CP343-1 Lean with configured S7 connection.
- STEP 7 V5.6 + SP2 (or TIA Portal V18/V19 with S7-300 add-on) on the engineering station.
- Remote access gateway: TS Adapter II (6NH7 800-0BA00, PSTN), TS Adapter IE (6NH7 860-0AA00, Ethernet/ISDN), or SINEMA RC Server appliance/software.
- Static public IP, dynamic DNS service, or SIM card with cellular modem (for cellular variants of the modern adapter).
2. Remote Access Methods Compared
| Method | Hardware | Network | Throughput | Status (2025) | Typical Use |
|---|---|---|---|---|---|
| TeleService PSTN | TS Adapter II (6NH7800-0BA00) | Analog phone line | 33.6 kbps | Discontinued, stock only | Legacy sites without LAN |
| TeleService ISDN | TS Adapter IE (6NH7860-0AA00) | ISDN BRI / Ethernet | 64 kbps–2 Mbps | Discontinued, stock only | Legacy sites with ISDN |
| SINEMA RC | SINEMA RC Server (6GK1720-1AH01-0BV0) + Client | Ethernet / cellular / VPN | Up to line rate | Current | New installations, IPv4/IPv6 |
| PG remote desktop | On-site PC + AnyDesk/RDP/VPN | Customer LAN | Up to LAN rate | Current | Quickest fallback |
| Direct Internet + CP343-1 | CP343-1 Lean + firewall/VPN | Ethernet + VPN | Up to 100 Mbps | Current | Customer-controlled VPN |
3. Prerequisites
- Project archive. Export the STEP 7 project (S7P file) and have the hardware configuration (HW Config) in the offline blocks. Verify the offline blocks compile to match the online signature before you attempt any remote download; mismatched FB/FC/DB interfaces are the most common cause of abort during download.
- CP343-1 Lean IP and subnet. Note the CP's configured IP (e.g., 192.168.0.10/24). Confirm the CP has an S7 connection permitted to the CPU (this is the default for the Lean variant with active S7 communication).
- Public reachability. The remote adapter must be addressable from your engineering station. Use a static public IP, an OpenVPN or IPsec tunnel to the plant, or a managed cellular SIM with fixed private APN.
- Firewall openings. See Section 6 for the full port matrix. The default S7 port is TCP 102; SINEMA RC uses TCP 50000-50010 plus UDP 161/162 for SNMP if used.
- STEP 7 online capability. The PG/PC interface on the engineering station must include the TCP/IP ISO-on-TCP driver that targets the CP. Test this against the CP's IP from inside the plant network before exposing the adapter to the Internet.
4. Path A: TeleService with TS Adapter II (PSTN)
The TS Adapter II (Siemens order number 6NH7 800-0BA00) connects to the MPI/DP port of the CPU315DP and to an analog telephone line. It functions as a thin gateway: the engineering station dials the phone number, the adapter answers, and the TeleService software encapsulates STEP 7 MPI frames over the dial-up connection.
4.1 Hardware wiring
- Plug the supplied MPI cable from the TS Adapter II to the CPU315DP's MPI/DP port (X1). The adapter is a passive MPI node; set its MPI address via the rotary switch or the TeleService software to a free address (default 0 is reserved for the CPU, so use 1 or higher).
- Connect the adapter's RJ-11 jack to the site phone line. The adapter must be the only device on that line during a session, or it must be on a dedicated extension.
- Apply 24 VDC to the adapter's power terminals.
4.2 TeleService software setup
- Install TeleService from the CD bundled with the TS Adapter. License is tied to the adapter's serial number.
- Open the TeleService Editor, create a new connection, and select TS Adapter II.
- Enter the plant's dial-in number, COM port on the engineering PC (no longer used by the adapter itself, but the software references it for the local modem), and the adapter's MPI address.
- Define the partner MPI address (CPU315DP MPI address, default 2).
4.3 Download from STEP 7
- In STEP 7 V5.6, choose Options → TeleService → Connect to target system. The dial-up session is established first; then STEP 7 sees the CPU as if it were on a local MPI cable.
- Select the S7 program in SIMATIC Manager, right-click, and choose Download. STEP 7 first downloads the HW Config, then the blocks (OB, FB, FC, DB).
- Monitor the transfer window. Over 33.6 kbps PSTN, a 2 MB program takes roughly 8-12 minutes; over ISDN it takes under a minute.
5. Path B: TeleService with TS Adapter IE (ISDN/Internet)
The TS Adapter IE (6NH7 860-0AA00) accepts either an ISDN BRI line or a 10/100 Ethernet uplink. The ISDN variant dials in exactly like the TS Adapter II but uses the D-channel for call setup. The Ethernet variant sits on the plant LAN, shares the CP343-1's switch port (or a separate one), and accepts incoming TCP connections from the Internet via port forwarding or a VPN.
5.1 IP configuration
- Connect a PC to the adapter's configuration port (X2) and browse to
https://192.168.1.1. Default credentials areadmin / admin. - Set the LAN IP (e.g., 192.168.0.50), subnet mask, and default gateway. Disable the DHCP server if the plant already runs one.
- Under Remote Access, enable the TeleService mode and assign a node name (e.g.,
PLANT01-CP3431). - Configure dial-in number or, for Ethernet mode, the public IP/DDNS name of the customer router.
5.2 STEP 7 over Internet
- On the engineering PC, install the TeleService software and add a new connection of type TS Adapter IE via TCP/IP.
- Set the partner IP to the public address of the plant (or DDNS name). Set the local S7 partner address to the CP343-1's LAN IP.
- Activate S7 routing in STEP 7: Options → Set PG/PC Interface → TCP/IP (Auto) → Properties → S7 routing enabled. This allows STEP 7 to traverse the CP343-1 to the CPU.
- Test reachability with PLC → Accessible Nodes. The CP343-1 should appear, and beneath it the CPU315DP via S7 routing.
- Trigger the download as in Section 4.3.
6. Path C: SINEMA RC (Current Standard)
SINEMA RC is the modern replacement for TeleService. It is a client/server architecture that tunnels STEP 7 or TIA Portal traffic through an encrypted channel, supports IPv4/IPv6, and is the only path Siemens still ships new for the S7-300 product line. The server is a software appliance (Linux or Windows) installed at the plant or hosted in a DMZ. The client is a Windows application on the engineering station.
6.1 Server installation
- Install SINEMA RC Server (order number 6GK1 720-1AH01-0BV0) on a dedicated x86 host with two NICs: one for the plant network, one for the Internet uplink (or VLAN segmentation).
- Apply the license file from the USB dongle or Siemens License Server.
- In the web admin, create a user for the remote engineer with role Service (read/write to the S7 subnet only).
- Add the CP343-1 as a device, enabling the S7 channel and disabling the S7-1200/1500 channels you do not need.
6.2 Client configuration
- Install SINEMA RC Client on the engineering PC and import the server's address (public IP or VPN endpoint) and user credentials.
- Once logged in, the SINEMA RC client enumerates all reachable PLCs. The CP343-1 appears as an S7 device with the CPU315DP accessible behind it via S7 routing.
- Open TIA Portal or STEP 7, set the PG/PC interface to SINEMA RC → TCP/IP, and proceed with the standard download flow.
6.3 Firewall and ports
| Port | Protocol | Direction | Purpose |
|---|---|---|---|
| TCP 22 | SSH | Server ↔ Client | SINEMA RC control channel |
| TCP 102 | ISO-on-TCP (S7) | Server → PLC | S7 communication (S7Comm) |
| TCP 50000-50010 | SINEMA RC proprietary | Bidirectional | Tunneled STEP 7/TIA traffic |
| UDP 161/162 | SNMP | Optional | CP343-1 diagnostics |
| TCP 443 | HTTPS | Server admin | SINEMA RC Web UI |
7. PG/PC Interface and S7 Routing
S7 routing is the mechanism that lets a TCP/IP packet addressed to the CP343-1 be forwarded as a Profibus/MPI frame to the CPU315DP. Configure it once on the engineering PC:
- Open Set PG/PC Interface from the Control Panel or STEP 7 menu.
- Select the interface that matches your transport:
TCP/IP (Auto) → <your NIC>for direct LAN,SINEMA RC → TCP/IPfor the modern tunnel, or the TeleService adapter's virtual driver for legacy paths. - Click Properties → S7 Routing and tick Use S7 routing for this interface.
- In the Accessible Nodes view, the CP343-1 should appear, and the CPU should be visible under the CP with a small arrow icon indicating it is reached through routing.
8. STEP 7 Download Procedure (Common to All Paths)
- Open the project in SIMATIC Manager or TIA Portal.
- From Online → Accessible Nodes, verify the CPU is visible and reachable. Note the diagnostic buffer entry "Online: Connection established to partner".
- Compare the offline and online block list. Resolve any FB/FC/DB interface mismatches before continuing; STEP 7 will refuse the download otherwise.
- Set the CPU operating mode. For program changes only, leave it in RUN-P. For configuration changes, place the CPU in STOP first (use PLC → Operating Mode).
- Select the S7 Program → Blocks folder and press the download icon. STEP 7 prompts to download HW Config first if it has changed. Confirm.
- Monitor the transfer. The CPU's SF/BF LEDs should remain off, and the run LED should stay green (or flash for RUN-P, depending on version).
- After completion, the diagnostic buffer should contain a user-defined entry. If you have an OBl call to
SFC 6 "RD_SINFO"or a timestamped event, confirm the new logic is active.
9. Verification
- Online signature check: In PLC → Compare Online/Offline, all modified blocks must show identical content hashes.
- Diagnostic buffer: No events of class "communication error" or "module parameter assignment error" should appear after the download.
- Watch table smoke test: Force a known input and verify the output using a VAT table. Toggle force values in the VAT and confirm the physical output or the in-CPU tag changes accordingly.
- Process verification: With the line under the customer's permissive, exercise the changed logic path end-to-end.
- Session log: SINEMA RC stores session logs; TeleService stores them in the local project folder. Archive them to the project ticket for audit.
10. Troubleshooting Matrix
| Symptom | Likely Cause | Fix |
|---|---|---|
| Accessible Nodes shows no CP | Ethernet/VPN reachability failure | Ping the CP IP, check VLAN, check SINEMA RC tunnel status |
| CP appears, CPU does not | S7 routing disabled or CP has no S7 connection | Enable S7 routing in PG/PC interface; in HW Config confirm CP has an S7 connection to the CPU |
| Download aborts at HW Config | CP343-1 firmware mismatch or version conflict | Match CP firmware to the version in the offline HW Config; update CP firmware if needed (online via the same tunnel) |
| Download aborts at FB/FC/DB | Interface signature mismatch | Recompile blocks offline, do not edit blocks online after the offline/online divergence |
| SF LED on CPU after download | Stack overflow or DB length error | Read diagnostic buffer; check for recursive OB calls; verify DB lengths match the new code |
| TeleService dial-up fails | Phone line busy, adapter MPI address conflict | Use a dedicated line, change adapter's MPI address to a free value (rotate switch) |
| SINEMA RC tunnel drops mid-download | Cellular signal loss, idle timeout, NAT rebind | Raise server's TCP keepalive; switch to wired uplink; re-establish and resume (STEP 7 continues from the last successful block) |
| Connection refused on TCP 102 | ISP blocks port 102, or firewall rule missing | Confirm SINEMA RC tunnel is up; never expose TCP 102 directly to the Internet |
11. Security Hardening
- No direct S7 exposure. Never publish TCP 102 on a public IP. Use SINEMA RC, IPsec, or OpenVPN.
- Strong credentials. SINEMA RC supports RADIUS and LDAP; integrate with the customer's directory and enforce MFA where possible.
- Role-based access. Grant the service engineer only the S7 subnet he needs. Block PLC-to-PLC routes if the change does not require them.
- Audit trail. SINEMA RC records user, time, source IP, and session duration. Export the log per change ticket.
- Firmware hygiene. Keep CP343-1 and CPU315DP firmware on the latest released version for the product line. As of 2025, the S7-300 is in the extended product support phase; Siemens still ships corrections to known security issues.
12. Quick-Start Cheat Sheet
- Legacy plant, no LAN: TS Adapter II + TeleService over PSTN.
- Plant has Ethernet but no DMZ host: TS Adapter IE behind the existing firewall with IPsec back to your office.
- New build or major upgrade: SINEMA RC server on a hardened host, engineer connects via the SINEMA RC client over the Internet.
- One-off emergency and no time to deploy: install STEP 7 on any PC at the plant, then use AnyDesk/TeamViewer + VPN to drive it remotely. The CPU sees a local engineer; the network sees a remote desktop.
13. Field-Proven Caveats
- The CP343-1 Lean is half-duplex on its external port; full-duplex negotiation must be forced off on the connected switch or you will see late collisions and dropped S7 connections.
- S7-300 firmware older than V2.0 does not support S7 routing across the CP343-1. Upgrade the CPU firmware to V2.0 or higher before relying on routed downloads.
- SINEMA RC versions prior to V2.0 do not support ISO-on-TCP through a NAT. If you are behind a carrier-grade NAT, upgrade the server.
- STEP 7 V5.6 does not recognize the TIA Portal S7-300 project format. If the customer's project was migrated to TIA, you need TIA Portal V18 or V19 to download back, even if the controller is a legacy S7-300.
- A 2 MB STEP 7 program typically contains 1.5-2.0 MB of blocks; the rest is documentation/HMI. Over a 10 Mbps SINEMA RC tunnel, a full download takes 6-10 minutes. Over a 3G cellular uplink with 1 Mbps effective throughput, budget 25-40 minutes.
14. Related Siemens Documentation
- Download to CPU (S7-300, S7-400) - STEP 7 / TIA Portal V20
- SIMATIC S7-300 CPU 315-2 DP Manual
- SINEMA RC Server Operating Instructions
FAQ
Can I download to a CPU315DP remotely without TeleService hardware?
Yes. Install STEP 7 on a PC at the plant and remote-control that PC using AnyDesk, RDP, or a VPN. STEP 7 then sees the CPU on a local MPI/Profibus cable and the download is identical to a bench session. This is the fastest fallback when no dedicated remote gateway exists.
Which TCP port does STEP 7 use for S7 communication?
STEP 7 uses ISO-on-TCP (S7Comm) on TCP port 102 for both reading and writing blocks. Never expose this port directly to the Internet - S7 has no authentication, so an open 102 is trivially exploitable. Always tunnel through SINEMA RC, a VPN, or a stateful firewall with an explicit allow-list.
What is the difference between TS Adapter II and TS Adapter IE?
TS Adapter II (6NH7800-0BA00) connects to an analog phone line and the CPU's MPI port at 33.6 kbps. TS Adapter IE (6NH7860-0AA00) accepts an ISDN BRI line or 10/100 Ethernet and reaches 64 kbps to 2 Mbps. Both are now discontinued; the current standard is SINEMA RC, which is an Ethernet/IP-only solution with cellular and VPN support.
Do I need to stop the CPU before a remote download?
For pure block changes that do not alter the HW Config, leave the CPU in RUN-P and STEP 7 will hot-load the modified blocks. For HW Config changes, or for any download that changes the OB1 or creates/deletes blocks, place the CPU in STOP first. Always confirm with the customer that the process can tolerate the brief stop.
Why does my S7-300 say "Accessible nodes: CP only, CPU not visible"?
S7 routing is disabled on the PG/PC interface, or the CP343-1 has no S7 connection permitted to the CPU. Enable S7 routing in Set PG/PC Interface → TCP/IP Properties → S7 Routing, and in HW Config confirm the CP has an S7 connection to the CPU with operator rights for read/write.