Tag: PortAutomation

  • ⚾ Teamwork Moves the Port — Just Like Baseball

    different fields same Teamwork.

    There’s no “I” in team — and if you’ve worked the port, you know that’s the truth.

    When that ship ties up, it’s go time. The crane operators, UTR drivers, mechanics, and clerks — everyone’s locked in. Timing, trust, and focus keep it all moving. Every second matters, and every move counts.

    It’s a lot like baseball. The LA Dodgers didn’t become champions by luck — they win because they trust each other, stay ready, and handle the small details that no one else sees.

    Same thing out here on the docks — you can’t move cargo without a crew that’s got your back.

    The port runs like a field: communication, awareness, and precision are everything. Safety isn’t just a rule — it’s part of the rhythm.

    When the flow’s right, it’s like turning a double play — smooth, clean, and satisfying. You feel it when every person does their job right, and the operation moves like one heartbeat.

    These days, we’ve got more tech in the mix — smarter systems, better data, and faster decisions. But it still comes down to people — the ones who know the yard, feel the pace, and keep things running right.

    Just like the Dodgers, we all play different positions — but the goal’s the same:
    Win together. Move the world. 🌎

    Carlos Espinosa
    Field Automation & Cybersecurity Technician | Port of Los Angeles
    #PortLife #Teamwork #Automation #Dodgers #LosAngeles #WestCoast #Kalmar #Ports #SafetyFirst #Innovation

  • How I Diagnose a PLC with TIA Portal Using a Sanitized Laptop

    By Carlos Espinosa Saldana – Port of Los Angeles | Automation & Cybersecurity

    Kalmar PLC, TIA Portal,
    Siemens TIA PORTAL PLC

    Introduction

    Working at the Port of Los Angeles, surrounded by the sound of cranes, horns, and container stackers, I often catch myself thinking: “If one of these machines suddenly stopped working, how would I diagnose it?”

    That thought led me down a path into PLC diagnostics — the heart of automation that keeps terminals running. But diagnosing a PLC isn’t just about checking wires or code. It’s also about protecting the system from intrusions.

    Every time I connect my laptop to a PLC, I remind myself: a clean connection is a safe connection.

    In this post, I’ll share how I approach diagnosing a Siemens PLC using TIA Portal, and why using a sanitized, cybersecurity-safe laptop is key to keeping operations both efficient and secure.


    🧼 Step 1: Always Start with a Sanitized Laptop

    Before opening TIA Portal:

    • Use a dedicated service laptop — no personal use, browsing, or random USB drives.
    • Run a malware scan before every connection.
    • Disable Wi-Fi and Bluetooth to prevent outside interference.
    • Turn off cloud-sync apps like OneDrive or Google Drive.
    • Keep Windows and Siemens software fully updated.

    💡 In the port world, one infected laptop can halt operations for an entire shift.

    A sanitized laptop helps prevent malware, trojans, and ransomware that could target PLCs or SCADA systems. Treat your laptop like your most trusted tool — keep it clean and ready.


    🔌 Step 2: Identify the PLC and Connection Type

    Before connecting:

    • Model: Siemens S7-1200 or S7-1500
    • Connection: Ethernet, MPI, or PROFIBUS
    • Network info: Confirm IP address and subnet

    ⚠️ Never perform random network scans — OT systems are sensitive and unauthorized probing can cause faults.


    🧰 Step 3: Connect Your Laptop and Verify Communication

    1. Plug your Ethernet cable from laptop to PLC or switch.
    2. Set a static IP on your laptop (e.g., 192.168.0.100).
    3. Open Command Prompt and ping the PLC: ping 192.168.0.1
    4. Open TIA Portal → Online → Accessible Devices and search for the PLC.
    5. Once detected, go online and monitor diagnostics.

    If nothing appears, double-check the cable, adapter, and ensure the PLC is in RUN mode.


    🔎 Step 4: Diagnose with TIA Portal

    Inside TIA Portal:

    • Open the Diagnostic Buffer to see fault history and timestamps.
    • Review Module Information for hardware/network status.
    • Observe Program Blocks and logic changes in real time.
    • Use Watch Tables to monitor sensor inputs and actuator outputs.

    🧩 If a tag doesn’t change when it should — that’s your starting point.

    A repeating “Bus Fault” may point to a damaged cable, bad module, or wrong configuration.


    🛡️ Step 5: Practice Cyber Safety During and After Diagnostics

    Even when the job seems done, stay cautious:

    • Disconnect immediately after finishing.
    • Save projects on encrypted or offline drives — never public clouds.
    • Keep a log including:
      • Date / time
      • PLC type and IP
      • Faults found
      • Actions taken

    🧠 Documenting is part of cybersecurity — it proves accountability and traceability.


    ⚓ Final Thoughts

    Working around automation every day taught me this: diagnosing a PLC is as much about mindset as it is about skill.

    Using Siemens TIA Portal is only half the job — the other half is staying calm, patient, and secure, both physically and digitally.

    “At the end of the day, the best technicians aren’t just the ones who fix problems — they’re the ones who prevent them.”

    If you enjoyed this post, check out my other projects on cespsecure.com where I share my journey from the docks to cybersecurity and automation.

  • From the Docks to Diagnostics: How the Port Taught Me to Think Like an Engineer

    Carlos Espinosa Saldana "CespSecure"
    Carlos Espinosa

    I grew up around the Port of Los Angeles — the smell of diesel, the sound of cranes, and the steady rhythm of work. For me, the docks weren’t just a job; they were part of life. Being a longshoreman taught me discipline, pride, and the importance of having your crew’s back. Every shift was different, and every problem came with a deadline. You learn fast that when something breaks, people are counting on you to figure it out.

    One moment that sticks with me happened on a busy day when several UTR monitors went down. The drivers couldn’t connect to the system, and work stopped. Most folks were waiting for a mechanic to show up, but I couldn’t just stand there. I started checking the basics — power, cables, connections — and tried resetting the monitors. Within minutes, they synced back up, and the units were running again. It wasn’t fancy — just common sense and curiosity — but that quick fix saved hours of downtime. That day taught me that the best tool you can have is your brain.

    Over the years, I started realizing how much technology was changing the port. The same machines I worked around every day were becoming smarter — more sensors, more automation, more data. I’ve always been hands-on, but I wanted to understand what was happening inside the systems. That’s when I started studying PLCs, diagnostics, and cybersecurity. The deeper I got into it, the more it made sense — the same logic that runs a port also runs in the code behind those machines.

    I’m not just chasing certifications or titles. I’m learning how to bridge two worlds — the old-school hard work of the dock and the new age of automation and smart systems. Both matter. Without one, the other doesn’t run right.

    The port taught me to respect the grind, to stay humble, and to never stop learning. Those lessons built the foundation for everything I do today — whether I’m turning a wrench, running diagnostics, or just helping someone solve a problem. The way I see it, I’m still doing what I’ve always done: keeping things moving.

    My goal is to use my entire skill set — from hands-on port experience to technical training in automation, hydraulics, and cybersecurity — to be part of the big picture that keeps the world moving. I understand the value of safety, precision, and uptime because I’ve lived it on the docks. Now, I’m focused on bringing that same mindset into the future — using technology and problem-solving to help the cargo keep flowing and the port stay strong.