← Back to site
CAMPOSLH · APPLIED ENGINEERING

CamposLH PLC Studio

Graphical ladder editor · IEC 61131-3 simulator · ST / PLCopen XML / SCL · Drive parameterization · V2.2

00. HOW DO YOU WANT TO START?
01. PROJECT IDENTIFICATION
Sets the address format (%IX0.0 IEC/CODESYS or %I0.0 Siemens) and ST code notes.
02. EXAMPLE LIBRARY

Click an example to open it: it replaces variables and networks (can be undone) and takes you straight to the simulation with the example guide.

03. SUMMARY
Educational and documentation tool. The simulation does not model hardware faults, real scan times, industrial networks or safety functions. Do not connect example outputs directly to machinery: review against manufacturer documentation with a qualified professional.
01. INPUT, OUTPUT AND MEMORY TABLE

This table is generated automatically from the ladder diagram. Here you can rename, change the device type or the address — changes show in the diagram, simulation and code.

QUICK COMPONENT ENTRY — click to add with automatic name and address:

Symbolic nameTypeDeviceAddressDescriptionRest signalActions

Names: letters, digits and underscores, starting with a letter (no ST reserved words, and not T_n / C_n / ET_n, which are used by generated instances). Addresses are a reference and must be confirmed in the vendor hardware configuration.

02. CROSS-REFERENCE

Where each variable is read (contacts, reset/load) and written (coils and blocks). An output without a coil or a memory never written means incomplete logic.

Symbolic nameAddressRead inWritten inStatus
01. LADDER DIAGRAM — BUILD BY CLICKING

1) Click a + point in the diagram (or use the one already marked). 2) Click a component in the palette: pushbuttons and sensors become contacts; motors, lamps and alarms become the network output coil. Each new component creates its variable and address automatically. Click any element in the drawing to edit it.

How to read ladder symbols
ContactsNO ⊣ ⊢ passes on 1 · NC ⊣/⊢ passes on 0 · P rising edge (R_TRIG) · N falling edge (F_TRIG).
CoilsNormal ( ) · Negated (/) · SET (S) latches 1 · RESET (R) forces 0.
TimersTON on-delay · TOF off-delay · TP fixed-length pulse.
CountersCTU up counter with R (reset) · CTD down counter with LD (load PV). Rising edges only.
01. LOGIC SIMULATOR

Run the scan and operate the machine from the panel or by clicking ladder contacts. Everything updates live: components, power flow, 0/1 values, timers and counters.

02. OPERATOR PANEL

Click buttons, switches and sensors as if you were at the panel. Momentary pushbuttons stay actuated only while held. The number in the corner shows the signal reaching the PLC (0 or 1).

03. ONLINE LADDER
power flowno flow· click input contacts to operate them
04. WATCH TABLE
Symbolic nameAddressDeviceValueUsed in
05. TIMERS AND COUNTERS
RBlock → outputINET / CVPT / PVQ
06. TIMING CHART
Last 24 s of the first 16 variables (blue = input, green = output, purple = memory).
The virtual clock advances 100 ms per scan (speed only accelerates execution). N edge detectors follow the IEC F_TRIG and may fire on the first scan. Interlocks here are logical only.
01. PLC CODE

Choose the format for your PLC software. The code comes from the same editor networks, with TON/TOF/TP, CTU/CTD and R_TRIG/F_TRIG as instances.


            
02. COMPATIBILITY — CAN THE FILE GO STRAIGHT TO THE EQUIPMENT?

Summary of what each software accepts, based on vendor documentation. Import was not tested here in each software; compile and bench-test before operating.

PlatformFileHow to useDirect use in the PLC?
Automatically generated reference code: compile, review and bench-test before energizing the machine. Safety functions (emergency stop, guards) must use safety devices and safety PLCs, not this logic.
01. ASSISTANT — WHAT WILL THE DRIVE DO?

Choose the manufacturer and answer the questions. Each answer sets the fields and builds the parameterization sequence with the parameters and values for the selected model.

02. MOTOR NAMEPLATE DATA

Copy from the motor nameplate. Values go straight into the parameterization sequence.

04. LIMITS AND RAMPS

Filled by the assistant for the application; adjust if needed.

Recalculates with nameplate data, limits and ramps and jumps to the table.
03. PARAMETERIZATION SEQUENCE

Key into the drive HMI in the order below. "✓ official guide" = code and value checked in the vendor guide for this model; "check" = confirm in the manual for your firmware before setting.

StepParameterValueWhat it doesSource

Sources checked: WEG CFW500 Quick Setup Guide; SIEMENS SINAMICS V20 Compact Operating Instructions (03/2021); Yaskawa GA500 Easy Start Guide. Other families: check the manual.

05. TERMINAL WIRING
Opens the "Drive control from the PLC" example with emergency stop, fault and reversing.
06. CALCULATED VALUES

Calculated from the nameplate: poles, synchronous speed, slip, rated torque (T = 9550·P/n), V/f ratio, apparent power and apparent efficiency (data consistency check).

The parameter map is a reference for the most common families and does NOT replace the manual: numbering, units and options change between models and firmware versions. Starting, braking, limits and safety functions require an application and risk assessment by a qualified professional.
07. COMMISSIONING CHECKLIST
01. CHECKS AND FILES

Review the items before printing. The report includes identification, I/O map with cross-reference, networks, ST code, drive worksheet and checklist; save as PDF from the print dialog.

02. SCOPE AND LIMITATIONS
Logic simulationRuns the logic in your browser with IEC block semantics. Does not model a real PLC, physical I/O or drive.
Exported codeReference ST; requires hardware configuration, validation and adaptation in the vendor IDE.
DrivesSurvey worksheet with calculations and a reference map — not a certified parameter database.
StorageData stays in this browser and in files you save. Nothing is sent to a server.
03. FREQUENTLY ASKED QUESTIONS
Does PLC Studio replace vendor software?

No. It is for learning, prototyping and documenting logic. The final program must be built and tested in TIA Portal, CODESYS, WPS, MotionWorks or your controller IDE.

Does the generated code go straight to the PLC?

It depends on the software: CODESYS imports the PLCopen XML; TIA Portal (S7-1200/1500) generates blocks from the .scl; WEG WPS does not import files. Always compile and bench-test before operating.

Are the drive parameters right for my model?

They are the usual codes of the families listed (WEG CFW, SINAMICS V20/G120, Yaskawa GA500/GA700/V1000). Numbering and options change with firmware — always check the manual for the installed revision.

How do I simulate a spring-return pushbutton?

Register the input as "Start pushbutton (NO)" or "Stop pushbutton (NC)". In simulation it is actuated only while held (mouse, touch or space bar), both on the panel and on the ladder symbol.

Are my projects saved?

The project is stored automatically in this browser. To move it to another computer or back it up, use "Save JSON" and then "Open JSON".